Network Service Header Fixed-Length Context Header Allocation
RFC 9192, “Network Service Header Fixed-Length Context Header Allocation”, is an Informational document published in February 2022 by T. Mizrahi, I. Yerushalmi, D. Melman, R. Browne. The canonical text is published by the RFC Editor.
Abstract
The Network Service Header (NSH) specification defines two possible methods of including metadata (MD): MD Type 0x1 and MD Type 0x2. MD Type 0x1 uses a fixed-length Context Header. The allocation of this Context Header, i.e., its structure and semantics, has not been standardized. This memo defines the Timestamp Context Header, which is an NSH fixed-length Context Header that incorporates the packet's timestamp, a sequence number, and a source interface identifier.
Although the definition of the Context Header presented in this document has not been standardized by the IETF, it has been implemented in silicon by several manufacturers and is published here to facilitate interoperability.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 9192 is hosted at rfc-editor.org. Available in HTML,TXT,PDF,XML.
- RFC 9191 Handling Large Certificates and Long Certificate Chains in TLS-Based EAP Methods
- RFC 9193 Sensor Measurement Lists Fields for Indicating Data Value Content-Format
- RFC 9190 EAP-TLS 1.3: Using the Extensible Authentication Protocol with TLS 1.3
- RFC 9194 A YANG Module for IS-IS Reverse Metric
- RFC 9189 GOST Cipher Suites for Transport Layer Security Protocol Version 1.2
- RFC 9195 A File Format for YANG Instance Data
- RFC 9188 Generic Multi-Access Encapsulation Protocol
- RFC 9196 YANG Modules Describing Capabilities for Systems and Datastore Update Notifications