[Cats] Re: Fw: New Version Notification for draft-fu-cats-oam-fw-06.txt

["[e-mail]" <[e-mail]>]

Hi Xiongquan,

    I have read draft-fu-cats-oam-fw-06 and would like to share some personal thoughts, hoping they might be helpful.

    The draft defines multiple OAM layers. While traditional networks already have Service-layer, Path-layer, and Link-layer OAM, the key addition here is Instance OAM.
    Although the draft mentions that these layers should correlate, there is no concrete example of how this cross-layer collaboration actually works. I suggest adding a simple workflow example to illustrate how they interact. This would significantly clarify the draft's objective. For example, if the Service-layer OAM detects a problem, would it trigger some underlayer OAM functions to locate the fault?

    I understand the draft intentionally avoids mandating specific technologies and lists several candidates. However, I believe we should explore how these technologies fit CATS requirements in practice:
        If we reuse existing protocols (e.g., BFD, TWAMP, IOAM), in which specific scenarios should they be used?
        On which network elements should they be deployed (Ingress/Egress Forwarder, or Service Instance)?
        Under what conditions should they be triggered?
        What parameters or configurations are required?

    Finally, a minor editorial question: Should M-REQ-4 actually be O-REQ-4 ?

Best Regards,
Zongpeng Du


[e-mail] & [e-mail] 

 
From: [e-mail]
Date: 2026-06-11 10:54
To: [e-mail]; [e-mail]
Subject: [Cats] Fw: New Version Notification for draft-fu-cats-oam-fw-06.txt
Hi All,

The authors have submitted a new version of the document to incorporate feedback received from the mailing list.

We would like to extend our thanks to Chuanyang Miao, Bin Zhang, Xueyan Mao, Jipeng Zhang, and Shuai Zhang for their review and valuable comments on this document.

The main updates in this version are as follows:
1, Updated references to their latest versions.
2, Revised the descriptions of Instance OAM and Service OAM to ensure consistency within the layering model and corresponding components.
3, Added a new requirement regarding Metric Freshness Handling.
4,Included OAM-specific security considerations.

We look forward to your continued feedback and discussion.Thanks!

Best regards,
Quan

Original
From: [e-mail] <[e-mail]>
To: Bo Liu <[e-mail]>;付华楷10336828;付华楷10336828;熊泉00091065;Zhenqiang Li <[e-mail]>;
Date: 2026年06月10日 21:04
Subject: New Version Notification for draft-fu-cats-oam-fw-06.txt
A new version of Internet-Draft draft-fu-cats-oam-fw-06.txt has been
successfully submitted by Huakai Fu and posted to the
IETF repository.

Name:     draft-fu-cats-oam-fw
Revision: 06
Title:    Computing-Aware Traffic Steering (CATS) Operations, Administration, and Maintenance (OAM) Framework
Date:     2026-06-10
Group:    Individual Submission
Pages:    14
URL:      https://www.ietf.org/archive/id/draft-fu-cats-oam-fw-06.txt
Status:   https://datatracker.ietf.org/doc/draft-fu-cats-oam-fw/
HTML:     https://www.ietf.org/archive/id/draft-fu-cats-oam-fw-06.html
HTMLized: https://datatracker.ietf.org/doc/html/draft-fu-cats-oam-fw
Diff:     https://author-tools.ietf.org/iddiff?url2=draft-fu-cats-oam-fw-06

Abstract:

   This document describes the Operations, Administration, and
   Maintenance (OAM) framework and requirements for Computing-Aware
   Traffic Steering (CATS).  The framework defines the CATS OAM layering
   model and functional components.  It also specifies the requirements
   to enable fault management and performance monitoring for CATS end-
   to-end connections encompassing clients, network paths, and service
   instances.



The IETF Secretariat