%% You should probably cite draft-song-ippm-ioam-ipv6-support-03 instead of this revision.
@techreport{song-ippm-ioam-ipv6-support-02,
    number =    {draft-song-ippm-ioam-ipv6-support-02},
    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/02/},
    author =    {Haoyu Song and Zhenbin Li and Shuping Peng and Jim Guichard},
    title =     {{Approaches on Supporting IOAM in IPv6}},
    pagetotal = 11,
    year =      2021,
    month =     jan,
    day =       4,
    abstract =  {It has been proposed to encapsulate IOAM tracing option data fields in IPv6 HbH options header. However, due to size of the trace data and the extension header location in the IPv6 packets, the proposal creates practical challenges for implementation, especially when other extension headers, such as a routing header, also exist and require in-network processing. We propose several alternative approaches to address this challenge, including separating the IOAM trace data to a different extension header, using the postcard-based telemetry (e.g., IOAM DEX) instead, and applying the segment IOAM trace export scheme, based on the network scenario and application requirements. We discuss the pros and cons of each approach and hope to foster standard convergence and industry adoption.},
}