RFC 8300: Network Service Header (NSH)

This document describes a Network Service Header (NSH) imposed on packets or frames to realize Service Function Paths (SFPs). The NSH also provides a…

Read RFC 8300 on the RFC Editor

Outgoing relationships (13 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 8126: Guidelines for Writing an IANA Considerations Section in RFCs
Normative reference — RFC 7665: Service Function Chaining (SFC) Architecture
Informative reference — RFC 2784: Generic Routing Encapsulation (GRE)
Informative reference — RFC 3552: Guidelines for Writing RFC Text on Security Considerations
Informative reference — RFC 3692: Assigning Experimental and Testing Numbers Considered Useful
Informative reference — RFC 8201: Path MTU Discovery for IP version 6
Informative reference — RFC 6291: Guidelines for the Use of the "OAM" Acronym in the IETF
Informative reference — RFC 7676: IPv6 Support for Generic Routing Encapsulation (GRE)
Informative reference — RFC 7498: Problem Statement for Service Function Chaining
Informative reference — RFC 6071: IP Security (IPsec) and Internet Key Exchange (IKE) Document Roadmap
Informative reference — RFC 7325: MPLS Forwarding Compliance and Performance Requirements
Informative reference — RFC 8165: Design Considerations for Metadata Insertion

Incoming relationships (19 related RFCs)

Updated by, Normatively referenced by — RFC 9451: Operations, Administration, and Maintenance (OAM) Packet and Behavior in the Network Service Header (NSH)
Normatively referenced by — RFC 9145: Integrity Protection for the Network Service Header (NSH) and Encryption of Sensitive Context Headers
Normatively referenced by — RFC 9263: Network Service Header (NSH) Metadata Type 2 Variable-Length Context Headers
Normatively referenced by — RFC 8979: Subscriber and Performance Policy Identifier Context Headers in the Network Service Header (NSH)
Normatively referenced by — RFC 9491: Integration of the Network Service Header (NSH) and Segment Routing for Service Function Chaining (SFC)
Normatively referenced by — RFC 9452: Network Service Header (NSH) Encapsulation for In Situ OAM (IOAM) Data
Normatively referenced by — RFC 8393: Operating the Network Service Header (NSH) with Next Protocol "None"
Normatively referenced by — RFC 9192: Network Service Header (NSH) Fixed-Length Context Header Allocation
Normatively referenced by — RFC 9516: Active Operations, Administration, and Maintenance (OAM) for Service Function Chaining (SFC)
Informatively referenced by — RFC 8404: Effects of Pervasive Encryption on Operators
Informatively referenced by — RFC 9543: A Framework for Network Slices in Networks Built from IETF Technologies
Informatively referenced by — RFC 8799: Limited Domains and Internet Protocols
Informatively referenced by — RFC 8924: Service Function Chaining (SFC) Operations, Administration, and Maintenance (OAM) Framework
Informatively referenced by — RFC 9599: Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP
Informatively referenced by — RFC 9601: Propagating Explicit Congestion Notification across IP Tunnel Headers Separated by a Shim
Informatively referenced by — RFC 9790: IANA Registry and Processing Recommendations for the First Nibble Following a Label Stack
Informatively referenced by — RFC 9791: Use Cases for MPLS Network Action Indicators and Ancillary Data
Informatively referenced by — RFC 9305: Locator/ID Separation Protocol (LISP) Generic Protocol Extension
Informatively referenced by — RFC 9689: Use Cases for a PCE as a Central Controller (PCECC)