%% You should probably cite draft-mizrahi-ippm-ioam-profile-06 instead of this revision.
@techreport{mizrahi-ippm-ioam-profile-04,
    number =    {draft-mizrahi-ippm-ioam-profile-04},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-mizrahi-ippm-ioam-profile/04/},
    author =    {Tal Mizrahi and Frank Brockners and Shwetha Bhandari and Ramesh Sivakolundu and Carlos Pignataro and Aviv Kfir and Barak Gafni and Mickey Spiegel and Tianran Zhou and Jennifer Lemon},
    title =     {{In Situ OAM Profiles}},
    pagetotal = 9,
    year =      2021,
    month =     feb,
    day =       17,
    abstract =  {In Situ Operations, Administration and Maintenance (IOAM) is used for monitoring network performance and for detecting traffic bottlenecks and anomalies. This is achieved by incorporating IOAM data into in- flight data packets. This document introduces the concept of use case-driven IOAM profiles. An IOAM profile defines a use case or a set of use cases for IOAM, and an associated set of rules that restrict the scope and features of the IOAM specification, thereby limiting it to a subset of the full functionality. The motivation for defining profiles is to limit the scope of IOAM features, allowing simpler implementation, verification, and interoperability testing in the context of specific use cases that do not require the full functionality of IOAM.},
}