Network Service Header (NSH) Fixed-Length Context Header Allocation
RFC 9192
Revision differences
Document history
Date | By | Action |
---|---|---|
2022-02-17
|
(System) | Received changes through RFC Editor sync (created alias RFC 9192, changed title to 'Network Service Header (NSH) Fixed-Length Context Header Allocation', changed abstract to … Received changes through RFC Editor sync (created alias RFC 9192, changed title to 'Network Service Header (NSH) Fixed-Length Context Header Allocation', changed abstract to '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.', changed pages to 10, changed standardization level to Informational, changed state to RFC, added RFC published event at 2022-02-17, changed ISE state to Published RFC) |
2022-02-17
|
(System) | RFC published |