[Cats] Re: some comments on draft-zhangb-cats-cmas-05
张宾 <zhangb@pcl.ac.cn> Tue, 04 August 2026 07:18 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 93C4012336018 for <cats@mail2.ietf.org>; Tue, 4 Aug 2026 00:18:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1785827917; bh=YAAW4HSLIBySvqRlKQCQsx46qoZkCR6OMUEo/jPwsWk=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=xz+6OTybuRA5POgkhNWRhuFrtx9qedeNThdtaX8pEgzJO1lQo2XgjOLFzcokUyHl7 3Kx9mjij6qe0tviM3Rhlu3PTvh2wPn+z2bvvWI0UboR/fauzimcVqxnJSXOk8OMahr eadQVEUzsRv5ezk9n1zWbTTlHsAn8LWrogTap81o=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.696
X-Spam-Level:
X-Spam-Status: No, score=-1.696 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, 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=no autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=pcl.ac.cn
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 Z2cw7S1K7bjH for <cats@mail2.ietf.org>; Tue, 4 Aug 2026 00:18:36 -0700 (PDT)
Received: from azure-sdnproxy.icoremail.net (azure-sdnproxy.icoremail.net [13.76.142.27]) by mail2.ietf.org (Postfix) with ESMTP id 060721233600F for <cats@ietf.org>; Tue, 4 Aug 2026 00:18:34 -0700 (PDT)
Received: from pcl.ac.cn (unknown [172.22.117.115]) by mtasvr (Coremail) with SMTP id _____wBXaCo3knFq29IAAA--.6871S3; Tue, 04 Aug 2026 15:18:16 +0800 (CST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pcl.ac.cn; s=dkim; h=Received:Date:From:To:Cc:Subject: In-Reply-To:References:Content-Type:MIME-Version:Message-ID; bh=YAAW4HSLIBySvqRlKQCQsx46qoZkCR6OMUEo/jPwsWk=; b=c5+9t+YfsnWQ5 7tsyx77WatSa0p+6YHP6qljjNH8Fz3v/A4/dFbYgpMfI8EReZh16n+4vnIqYVFeB zDqKAeFQrk7CwOZalA6m17NKKevOq8trlCNKOdG6YpM/G8w4qo5xJV8mcW/J6GUF 1FX+JDd2/RJOfv2J3Y0s6PM9kG1kPA=
Received: from zhangb$pcl.ac.cn ( [172.22.117.115] ) by ajax-webmail-coremail2 (Coremail) ; Tue, 4 Aug 2026 15:18:15 +0800 (GMT+08:00)
X-Originating-IP: [172.22.117.115]
Date: Tue, 04 Aug 2026 15:18:15 +0800
X-CM-HeaderCharset: UTF-8
From: 张宾 <zhangb@pcl.ac.cn>
To: miao.chuanyang@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: <20260804144006815PeN6odJowZGENelsc98sT@zte.com.cn>
References: 709795f2.5ec.19fa15597ef.Coremail.zhangb@pcl.ac.cn <20260804144006815PeN6odJowZGENelsc98sT@zte.com.cn>
X-CM-CTRLMSGS: =?B?15cj0DiH6nJ5xwDR7hwMki1N8jM=
Content-Type: multipart/alternative; boundary="----=_Part_18617_1562376255.1785827895267"
MIME-Version: 1.0
Message-ID: <298aaf9c.1010.19fcba327e3.Coremail.zhangb@pcl.ac.cn>
X-Coremail-Locale: zh_CN
X-CM-TRANSID: mwiowADHfy43knFqqf4BAA--.2968W
X-CM-SenderInfo: helqh6pkdqwqxsfohtffof0/1tbiAQEJBWpwog8LQgACsw
X-Coremail-Antispam: 1Uk129KBj93XoW7KF1xJrWDXw4DuFyrGrWfJFc_yoW8Gry7pF 1xKw1DCFn7tF18G3W0vw4xZryaqFZYqrWrJrnrGr18Aws8A34IgFy2ywn0v34UCrn7Zw1k Xry2q3s8uF1kArXCm3ZEXasCq-sJn29KB7ZKAUJUUUUU529EdanIXcx71UUUUU7KY7ZEXa sCq-sGcSsGvfJ3kc02F40EFcxC0VAKzVAqx4xG6I80ewAqx4xG6xAIxVCFxsxG0bIjqfuF e4nvWSU5nxnvy29KBjDU0xBIdaVrnRJUUUBIb4IE77IF4wAFF20E14v26r1j6r4UM7CY07 I20VC2zVCF04k26cxKx2IYs7xG6rWj6s0DM7CIcVAFz4kK6r1j6r18M28lY4IEw2IIxxk0 rwA2F7IY1VAKz4vEj48ve4kI8wA2z4x0Y4vE2Ix0cI8IcVAFwI0_Jr0_JF4l84ACjcxK6x IIjxv20xvEc7CjxVAFwI0_Jr0_Gr1l84ACjcxK6I8E87Iv67AKxVWxJVW8Jr1l84ACjcxK 6I8E87Iv6xkF7I0E14v26r4j6r4UJwAS0I0E0xvYzxvE52x082IY62kv0487Mc804VCY07 AIYIkI8VC2zVCFFI0UMc02F40EFcxC0VAKzVAqx4xG6I80ewAqx4xG6xAIxVCFxsxG0wAv 7VC0I7IYx2IY67AKxVWUJVWUGwAv7VC2z280aVAFwI0_Jr0_Gr1lOx8S6xCaFVCjc4AY6r 1j6r4UM4x0Y48IcxkI7VAKI48JM4xvF2IEb7IF0Fy264kE64k0F24lFcxC0VAYjxAxZF0E x2IqxwCF04k20xvY0x0EwIxGrwCFx2IqxVCFs4IE7xkEbVWUJVW8JwC20s026c02F40E14 v26r106r1rMI8I3I0E7480Y4vE14v26r106r1rMI8E67AF67kF1VAFwI0_Jrv_JF1lIxkG c2Ij64vIr41lIxAIcVC0I7IYx2IY67AKxVWUJVWUCwCI42IY6xIIjxv20xvEc7CjxVAFwI 0_Jr0_Gr1lIxAIcVCF04k26cxKx2IYs7xG6r1j6r1xMIIF0xvEx4A2jsIE14v26r1j6r4U MIIF0xvEx4A2jsIEc7CjxVAFwI0_Jr0_GrUvcSsGvfC2KfnxnUUI43ZEXa7IU81v3UUUUU U==
Message-ID-Hash: Z6YCBP2OBV36B3MWL5MQPKY5JRFGL6KV
X-Message-ID-Hash: Z6YCBP2OBV36B3MWL5MQPKY5JRFGL6KV
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: some comments on draft-zhangb-cats-cmas-05
List-Id: "Computing-Aware Traffic Steering (CATS)" <cats.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cats/b6sojo4pVDIQAFq2Lzzxhf28LSk>
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, Miao, OK，thank you for the suggestion. We will update the draft in the next revision in accordance with your suggestions. Regards Bin -----原始邮件----- 发件人:miao.chuanyang@zte.com.cn 发送时间:2026-08-04 14:40:06 (星期二) 收件人: zhangb@pcl.ac.cn 抄送: cats@ietf.org 主题: [Cats] some comments on draft-zhangb-cats-cmas-05 Hi Authors, I just reviewed your draft draft-zhangb-cats-cmas-05 "Public Service Platform for Computing-Aware Traffic Steering (CATS)". I have a few suggestions regarding the terminology and content in this document: Terminology adjustment: I believe "service resolution" or "service interpretation" would be more accurate than "service discovery" in this context. The current function is simply to retrieve CS-ID related information, rather than actively discovering concrete service instances. Moreover, using "discovery" may cause ambiguity with the existing "discovery" functionality within DAWN. Additional service information: I suggest including the service version number and other relevant service metadata alongside the existing information. Input description: I recommend renaming the "input description" field to "input schema" for better clarity and alignment with common API documentation practices. BG Miao