RFC 8393

Operating the Network Service Header (NSH) with Next Protocol "None", May 2018

File formats:
icon for text file icon for PDF icon for HTML
Status:
PROPOSED STANDARD
Authors:
A. Farrel
J. Drake
Stream:
IETF
Source:
sfc (rtg)

Cite this RFC: TXT  |  XML  |   BibTeX

DOI:  https://doi.org/10.17487/RFC8393

Discuss this RFC: Send questions or comments to the mailing list sfc@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC 8393


Abstract

This document describes a network that supports Service Function Chaining (SFC) using the Network Service Header (NSH) with no payload data and carrying only metadata. This is achieved by defining a new NSH "Next Protocol" type value of "None".

This document illustrates some of the functions that may be achieved or enhanced by this mechanism, but it does not provide an exhaustive list of use cases, nor is it intended to be definitive about the functions it describes. It is expected that other documents will describe specific use cases in more detail and will define the protocol mechanics for each use case.


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.




Advanced Search