RFC 9263: Network Service Header (NSH) Metadata Type 2 Variable-Length Context Headers

Service Function Chaining (SFC) uses the Network Service Header (NSH) (RFC 8300) to steer and provide context metadata (MD) with each packet. Such metadata…

Read RFC 9263 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 8174: Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
Normative reference — RFC 3931: Layer Two Tunneling Protocol - Version 3 (L2TPv3)
Normative reference — RFC 8300: Network Service Header (NSH)
Normative reference — RFC 9145: Integrity Protection for the Network Service Header (NSH) and Encryption of Sensitive Context Headers
Informative reference — RFC 4364: BGP/MPLS IP Virtual Private Networks (VPNs)
Informative reference — RFC 8200: Internet Protocol, Version 6 (IPv6) Specification
Informative reference — RFC 3032: MPLS Label Stack Encoding
Informative reference — RFC 2890: Key and Sequence Number Extensions to GRE
Informative reference — RFC 7665: Service Function Chaining (SFC) Architecture
Informative reference — RFC 6790: The Use of Entropy Labels in MPLS Forwarding
Informative reference — RFC 8926: Geneve: Generic Network Virtualization Encapsulation
Informative reference — RFC 8979: Subscriber and Performance Policy Identifier Context Headers in the Network Service Header (NSH)

Incoming relationships (3 related RFCs)

Informatively referenced by — RFC 9451: Operations, Administration, and Maintenance (OAM) Packet and Behavior in the Network Service Header (NSH)
Informatively referenced by — RFC 9791: Use Cases for MPLS Network Action Indicators and Ancillary Data
Informatively referenced by — RFC 9516: Active Operations, Administration, and Maintenance (OAM) for Service Function Chaining (SFC)