Search RFCs

RFC Editor

File formats:

Also available:XML file for editing

 

Status:

INFORMATIONAL

Authors:

T. Mizrahi
I. Yerushalmi
D. Melman
R. Browne

Stream:

INDEPENDENT

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC9192

Discuss this RFC: Send questions or comments to the mailing listrfc-ise@rfc-editor.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 9192

Abstract

The Network Service Header (NSH) specification defines two possiblemethods of including metadata (MD): MD Type 0x1 and MD Type 0x2. MDType 0x1 uses a fixed-length Context Header. The allocation of thisContext Header, i.e., its structure and semantics, has not beenstandardized. This memo defines the Timestamp Context Header, whichis an NSH fixed-length Context Header that incorporates the packet'stimestamp, a sequence number, and a source interface identifier.

Although the definition of the Context Header presented in thisdocument has not been standardized by the IETF, it has beenimplemented in silicon by several manufacturers and is published hereto facilitate interoperability.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.