@techreport{song-ippm-ioam-ipv6-support-08,
    number =    {draft-song-ippm-ioam-ipv6-support-08},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-song-ippm-ioam-ipv6-support/08/},
    author =    {Haoyu Song and Zhenbin Li and Shuping Peng and Jim Guichard},
    title =     {{Supporting IOAM in IPv6}},
    pagetotal = 10,
    year =      2026,
    month =     aug,
    day =       3,
    abstract =  {IOAM pre-allocated trace option data fields can be encapsulated in the IPv6 Hop-by-Hop (HbH) Options header as described in RFC 9486. However, due to the potentially large size of the trace data and the location of the HbH Options header in the IPv6 packet, this scheme creates practical challenges for implementation, especially when other extension headers, such as a routing header, are also present and require on-path processing. In addition to IOAM Direct Export (DEX), this document proposes two alternative approaches to address this challenge: separating the IOAM incremental trace data from the IOAM instruction header, or applying the segment IOAM trace data export scheme, depending on the network scenario and application requirements. We discuss the pros and cons of each approach.},
}