@techreport{dikshit-cats-oam-usecases-00,
    number =    {draft-dikshit-cats-oam-usecases-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-dikshit-cats-oam-usecases/00/},
    author =    {Saumya Dikshit},
    title =     {{Use Cases and Requirements for Computing-Aware Traffic Steering (CATS) Operations, Administration, and Maintenance (OAM)}},
    pagetotal = 2,
    year =      2026,
    month =     jul,
    day =       31,
    abstract =  {{[}I-D.ietf-cats-oam-fw{]} defines a framework for Operations, Administration, and Maintenance (OAM) in Computing-Aware Traffic Steering (CATS) networks, introducing Instance OAM and Service OAM as new components alongside traditional Link and Path OAM, and specifying high-level requirements (O-REQ, A-REQ, M-REQ) for each. As with the base CATS work, where {[}I-D.ietf-cats-usecases-requirements{]} separately catalogued problem statement, use cases, and requirements alongside {[}I-D.ietf-cats-framework{]}, the OAM framework similarly benefits from a companion document grounding its requirements in concrete operator scenarios. This document fills that gap. It presents five use cases for CATS OAM -- multi-domain compute-node failure detection, SLA verification that closes the loop with metric-driven traffic- steering decisions, demarcation of network-path faults from compute-instance faults, OAM-triggered fallback steering, and multi-vendor Compute-Service Metric Agent (C-SMA) interoperability verification -- and maps each to the Link/Path/Instance/Service OAM layering and O-REQ/A-REQ/M-REQ requirement categories defined in {[}I-D.ietf-cats-oam-fw{]}.},
}