<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.dikshit-cats-oam-usecases" target="https://datatracker.ietf.org/doc/html/draft-dikshit-cats-oam-usecases-00">
   <front>
      <title>Use Cases and Requirements for Computing-Aware Traffic Steering (CATS) Operations, Administration, and Maintenance (OAM)</title>
      <author initials="D." surname="Dikshit" fullname="Saumya Dikshit">
         <organization>Aruba Networks</organization>
      </author>
      <date month="July" day="31" year="2026" />
      <abstract>
	 <t>   [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].

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-dikshit-cats-oam-usecases-00" />
   
</reference>
