Operating the Network Service Header with Next Protocol "None"
RFC 8393, “Operating the Network Service Header with Next Protocol "None"”, is a Proposed Standard document published in May 2018 by A. Farrel, J. Drake. The canonical text is published by the RFC Editor.
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.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 8393 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 8392 CBOR Web Token
- RFC 8394 Split Network Virtualization Edge Control-Plane Requirements
- RFC 8391 XMSS: eXtended Merkle Signature Scheme
- RFC 8395 Extensions to BGP-Signaled Pseudowires to Support Flow-Aware Transport Labels
- RFC 8390 RSVP-TE Path Diversity Using Exclude Route
- RFC 8396 Managing, Ordering, Distributing, Exposing, and Registering Telephone Numbers : Problem Statement, Use Cases, and Framework
- RFC 8389 Definitions of Managed Objects for Mapping of Address and Port with Encapsulation
- RFC 8397 Transparent Interconnection of Lots of Links Multilevel Using Unique Nicknames