metasystema.org
CurrentINFORMATIONALINDEPENDENT stream

RFC 9192: Network Service Header (NSH) Fixed-Length Context Header Allocation

In plain English — editorial summary, not part of the RFC

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.

Document record

Document ID
RFC9192
Published
February 2022
Authors
T. Mizrahi; I. Yerushalmi; D. Melman; R. Browne
Status
INFORMATIONAL
Stream
INDEPENDENT
Area
—
Pages
10
Also known as
—

Topics

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/9192-network-service-header-nsh-fixed-length-context-header-allocation