[Cats] Re: Introduction to the status of draft-fu-cats-oam-fw-05 and encourage more discussions

张宾 <zhangb@pcl.ac.cn> Tue, 02 June 2026 03:04 UTC

Return-Path: <zhangb@pcl.ac.cn>
X-Original-To: cats@mail2.ietf.org
Delivered-To: cats@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 14A73F90297E for <cats@mail2.ietf.org>; Mon, 1 Jun 2026 20:04:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1780369460; bh=tJqkm0De9/jGmPBCRmJB1vDFzVQxTa6dKpvfCb9N27M=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=YQfqPJIRsyrt77uiE6kGdqCGdnxCmED74obEiE0hzOglEopTZb9c4N9zuL2b87DBK IjZoNr8NqLtLiXx2MD4znS5rGNIJNiIxlOANJtU/sy2IiqEbyLoenCuHoh5Oy7z/8I O5KR9DiWovdtWjtXL8UNey9G/R45Omus4vecCjYw=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DHQISCrMRJTM for <cats@mail2.ietf.org>; Mon, 1 Jun 2026 20:04:19 -0700 (PDT)
Received: from azure-sdnproxy.icoremail.net (azure-sdnproxy.icoremail.net [52.229.205.26]) by mail2.ietf.org (Postfix) with ESMTP id 7A7FEF902949 for <cats@ietf.org>; Mon, 1 Jun 2026 20:04:14 -0700 (PDT)
Received: from pcl.ac.cn (unknown [172.22.117.115]) by mtasvr (Coremail) with SMTP id _____wBnb0cqSB5qXlsVAA--.147S3; Tue, 02 Jun 2026 11:04:11 +0800 (CST)
Received: from zhangb$pcl.ac.cn ( [172.22.117.115] ) by ajax-webmail-coremail2 (Coremail) ; Tue, 2 Jun 2026 11:04:10 +0800 (GMT+08:00)
X-Originating-IP: [172.22.117.115]
Date: Tue, 02 Jun 2026 11:04:10 +0800
X-CM-HeaderCharset: UTF-8
From: 张宾 <zhangb@pcl.ac.cn>
To: xiong.quan@zte.com.cn
X-Priority: 3
X-Mailer: Coremail Webmail Server Version 2025.1-cmXT6 build 20250605(d51350d6) Copyright (c) 2002-2026 www.mailtech.cn mispb-4f335c7f-b286-4f72-8ea6-7b7dec0a589b-pcl.ac.cn
In-Reply-To: <20260602100638193JLw9Cr427tB2xvqHhvUo2@zte.com.cn>
References: 20260528153635825uJYyBHQCz0sR3-OTJ1w9P@zte.com.cn,30e7f19f.6cb6.19e81ffaae5.Coremail.zhangb@pcl.ac.cn <20260602100638193JLw9Cr427tB2xvqHhvUo2@zte.com.cn>
X-CM-CTRLMSGS: =?B?nS2HgjiH6nJ5xwDR7hwMki1N8jM=
Content-Type: multipart/alternative; boundary="----=_Part_124307_689437978.1780369450228"
MIME-Version: 1.0
Message-ID: <3fadcec4.6dd7.19e8649e4f4.Coremail.zhangb@pcl.ac.cn>
X-Coremail-Locale: zh_CN
X-CM-TRANSID: mwiowABXg_wqSB5qyaoVAA--.25028W
X-CM-SenderInfo: helqh6pkdqwqxsfohtffof0/1tbiAQEGBWodeX0EgwABs2
X-Coremail-Antispam: 1Uk129KBj93XoWxGw18Aw4fZrWfWrWDAr17twc_yoWrCFW8pa y2grWftF4qyF1xGayxZw1xZr1a9a9agFW3G3WkKryUZw15KF92yFyxKa45XFyUWrykAF1a qw4jvry5Za17AagCm3ZEXasCq-sJn29KB7ZKAUJUUUU8529EdanIXcx71UUUUU7KY7ZEXa sCq-sGcSsGvfJ3kc02F40EFcxC0VAKzVAqx4xG6I80ewAqx4xG6xAIxVCFxsxG0bIjqfuF e4nvWSU5nxnvy29KBjDU0xBIdaVrnRJUUUB2b4IE77IF4wAFF20E14v26r1j6r4UM7CY07 I20VC2zVCF04k26cxKx2IYs7xG6rWj6s0DM7CIcVAFz4kK6r1j6r18M28lY4IEw2IIxxk0 rwA2F7IY1VAKz4vEj48ve4kI8wA2z4x0Y4vE2Ix0cI8IcVAFwI0_Jr0_JF4l84ACjcxK6x IIjxv20xvEc7CjxVAFwI0_Jr0_Gr1l84ACjcxK6I8E87Iv67AKxVW8JVWxJwA2z4x0Y4vE x4A2jsIEc7CjxVAFwI0_Gr0_Gr1UM2AIxVAIcxkEcVAq07x20xvEncxIr21l57IF6xkI12 xvs2x26I8E6xACxx1l5I8CrVACY4xI64kE6c02F40Ex7xfMc02F40E42I26xC2a48xMcIj 6xIIjxv20xvE14v26r1j6r18McIj6I8E87Iv67AKxVWUJVW8JwAm72CE4IkC6x0Yz7v_Jr 0_Gr1lF7xvr2IYc2Ij64vIr41lFcxC0VAYjxAxZF0Ew4CEw7xC0wACY4xI67k04243AVC2 0s07MxAIw28IcxkI7VAKI48JMxC20s026xCaFVCjc4AY6r1j6r4UMI8I3I0E5I8CrVAFwI 0_JrI_JrWlx2IqxVCjr7xvwVAFwI0_JrI_JrWlx4CE17CEb7AF67AKxVWUXVWUAwCIc40Y 0x0EwIxGrwCI42IY6xIIjxv20xvE14v26r1j6r1xMIIF0xvE2Ix0cI8IcVCY1x0267AKxV WUJVW8JwCI42IY6xAIw20EY4v20xvaj40_Jr0_JF4lIxAIcVC2z280aVAFwI0_Jr0_Gr1l IxAIcVC2z280aVCY1x0267AKxVWUJVW8JbIYCTnIWIevJa73UjIFyTuYvjxU7wIDUUUUU
Message-ID-Hash: 2HUSJ537TT6AQUK5WDB6T4N6S6WHDX4C
X-Message-ID-Hash: 2HUSJ537TT6AQUK5WDB6T4N6S6WHDX4C
X-MailFrom: zhangb@pcl.ac.cn
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: cats@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Cats] Re: Introduction to the status of draft-fu-cats-oam-fw-05 and encourage more discussions
List-Id: "Computing-Aware Traffic Steering (CATS)" <cats.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cats/EKqY3kOiTql4zhJGuZNNATE_rVc>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cats>
List-Help: <mailto:cats-request@ietf.org?subject=help>
List-Owner: <mailto:cats-owner@ietf.org>
List-Post: <mailto:cats@ietf.org>
List-Subscribe: <mailto:cats-join@ietf.org>
List-Unsubscribe: <mailto:cats-leave@ietf.org>

Hi Quan,


Thank you for clarifying the scope of your document. We will take this scope boundary into account in our ongoing work and ensure proper coordination to avoid overlap.


Best Regards,
Bin 

  








-----原始邮件-----
发件人:xiong.quan@zte.com.cn
发送时间:2026-06-02 10:06:38 (星期二)

收件人: zhangb@pcl.ac.cn
抄送: cats@ietf.org
主题: Re: [Cats] Introduction to the status of draft-fu-cats-oam-fw-05 and encourage more discussions







Hi Bin,




Thanks for your review and support!




This document just specifies the CATS OAM layering model including new CATS OAM components based on the CATS framework as per draft-ietf-cats-framework.

It also proposed the metric collection function in the instance OAM layer and SI-OAM component but the metric definition and corresponding special policy is out of the scope of this document.




Thanks,

Quan










Original
From: 张宾 <zhangb@pcl.ac.cn>
To: 熊泉00091065;
Cc: cats@ietf.org <cats@ietf.org>;
Date: 2026年06月01日 15:04
Subject: Re: [Cats] Introduction to the status of draft-fu-cats-oam-fw-05 and encourage more discussions

Dear Quan,

 

  Through reading this document, I think SI-OAM Component is fit for the service metrics collection defined in draft-zhangb-cats-service-metrics-op-01 - Computing Service Metric Definitions and Operation under CATS. Also I think the update policy of our proposed service-oriented metrics in large-scale deployments as you put forward is more proper to be formulated and Standardized in this document, which we can give some suggestions if our proposal can be supported by the WG in the future. We also note that the SI-OAM Component described in your draft represents a service-oriented metrics construct that is fundamentally aligned with the core principles underlying our service metrics definition.







Best Regards,

Bin 








-----原始邮件-----
发件人:xiong.quan@zte.com.cn
发送时间:2026-05-28 15:36:35 (星期四)

收件人: cats-chairs@ietf.org, cats@ietf.org
主题: [Cats] Introduction to the status of draft-fu-cats-oam-fw-05 and encourage more discussions







Dear All,





As suggested by the chairs, I'd like to provide a brief introduction to the status of this document to help everyone to better understand its content and encourage further feedback in the mailing list.




https://datatracker.ietf.org/doc/draft-fu-cats-oam-fw/05/




This document (draft-fu-cats-oam-fw-05) proposes an Operations, Administration, and Maintenance (OAM) framework for Computing-Aware Traffic Steering (CATS) systems. It addresses the limitations of traditional network-centric OAM by introducing a multidimensional approach that integrates both network and computing resource monitoring.




Motivation and Problem Statement:

The framework is designed to prevent "service black-holing," where traffic is directed to service instances that are network-reachable but computationally unresponsive. It enables real-time correlation of network metrics with computing metrics to support accurate steering decisions and ensure services are both reachable and performing as expected.




Key Components:

A four-layer OAM model: Link OAM (physical connectivity), Path OAM (transport paths), Instance OAM (service instance liveness and computing metrics), and Service OAM (end-to-end service delivery)

Two functional components: SI-OAM for service instance monitoring and SVC-OAM for end-to-end service verification

Comprehensive OAM requirements: aligned with the operational and management guidelines in [I-D.draft-opsarea-rfc5706bis]




This document has been presented at IETF #124 and #125. We sincerely appreciate the valuable feedback and suggestions received from Adrian Farrel, Erum Welling, Cheng Li, Peng Liu, Haomian Zheng, and other participants. The authors have revised the draft through multiple versions (00 to 05) to incorporate this feedback. Since the last presentation at IETF 125, no further comments have been raised.




The authors welcome additional review and constructive discussion, and we look forward to your feedback as we consider this draft for potential adoption by the CATS working group.Thanks!




Best Regards,

Quan