%% You should probably cite rfc9197 instead of this I-D.
@techreport{ietf-ippm-ioam-data-09,
    number =    {draft-ietf-ippm-ioam-data-09},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-ippm-ioam-data/09/},
    author =    {Frank Brockners and Shwetha Bhandari and Carlos Pignataro and Hannes Gredler and John Leddy and Stephen Youell and Tal Mizrahi and David Mozes and Petr Lapukhov and remy@barefootnetworks.com and Daniel Bernier and Jennifer Lemon},
    title =     {{Data Fields for In-situ OAM}},
    pagetotal = 43,
    year =      2020,
    month =     mar,
    day =       9,
    abstract =  {In-situ Operations, Administration, and Maintenance (IOAM) records operational and telemetry information in the packet while the packet traverses a path between two points in the network. This document discusses the data fields and associated data types for in-situ OAM. In-situ OAM data fields can be encapsulated into a variety of protocols such as NSH, Segment Routing, Geneve, IPv6 (via extension header), or IPv4. In-situ OAM can be used to complement OAM mechanisms based on e.g. ICMP or other types of probe packets.},
}