@techreport{li-ippm-ioam-common-encap-procedures-00,
    number =    {draft-li-ippm-ioam-common-encap-procedures-00},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-li-ippm-ioam-common-encap-procedures/00/},
    author =    {Zhiqiang Li and Zongpeng Du and Junjie Wang and Wei Cheng and Guoying Zhang and Xun Sun and Chunhao Zhao},
    title =     {{Common Procedures for Encapsulating IOAM Data Fields in Transport Protocols}},
    pagetotal = 13,
    year =      2026,
    month =     jul,
    day =       4,
    abstract =  {In Situ Operations, Administration, and Maintenance (IOAM) enables on-path telemetry by inserting operational metadata into data packets as they traverse a network path. IOAM Data-Fields, as defined in RFC 9197, are designed to be independent of the encapsulating transport protocol. However, the procedures for inserting, updating, and removing IOAM Data-Fields are currently specified separately for each transport protocol (e.g., IPv6, NSH, GRE, Geneve), leading to redundant specification effort and inconsistent implementation behavior. This document defines a set of common encapsulation procedures for IOAM Data-Fields that are applicable across multiple transport protocols. The insertion point for IOAM Data-Fields is expressed as a configurable byte offset from a well-defined reference position in the encapsulating header, enabling a uniform insertion procedure that does not require protocol-specific parsing logic. The document specifies the general steps for identifying the insertion point, validating transport-layer constraints, performing the insertion of IOAM Option-Types, and updating affected header fields to maintain protocol compliance.},
}