Re: [Cats] CATS WG Adoption poll for draft-ldbc-cats-framework

"Shihang(Vincent)" <shihang9@huawei.com> Mon, 26 February 2024 14:11 UTC

Return-Path: <shihang9@huawei.com>
X-Original-To: cats@ietfa.amsl.com
Delivered-To: cats@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44E4DC16A128; Mon, 26 Feb 2024 06:11:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.904
X-Spam-Level:
X-Spam-Status: No, score=-6.904 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3Oc8E7GP7bOv; Mon, 26 Feb 2024 06:11:46 -0800 (PST)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B219CC169506; Mon, 26 Feb 2024 06:11:45 -0800 (PST)
Received: from mail.maildlp.com (unknown [172.18.186.231]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4Tk2Vj5ST2z6JBTl; Mon, 26 Feb 2024 22:07:09 +0800 (CST)
Received: from lhrpeml500006.china.huawei.com (unknown [7.191.161.198]) by mail.maildlp.com (Postfix) with ESMTPS id 97759140A9C; Mon, 26 Feb 2024 22:11:43 +0800 (CST)
Received: from kwepemd500008.china.huawei.com (7.221.188.231) by lhrpeml500006.china.huawei.com (7.191.161.198) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.35; Mon, 26 Feb 2024 14:11:42 +0000
Received: from kwepemd100007.china.huawei.com (7.221.188.221) by kwepemd500008.china.huawei.com (7.221.188.231) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1258.28; Mon, 26 Feb 2024 22:11:41 +0800
Received: from kwepemd100007.china.huawei.com ([7.221.188.221]) by kwepemd100007.china.huawei.com ([7.221.188.221]) with mapi id 15.02.1258.028; Mon, 26 Feb 2024 22:11:41 +0800
From: "Shihang(Vincent)" <shihang9@huawei.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, 'cats' <cats@ietf.org>
CC: "draft-ldbc-cats-framework@ietf.org" <draft-ldbc-cats-framework@ietf.org>, "cats-chairs@ietf.org" <cats-chairs@ietf.org>
Thread-Topic: [Cats] CATS WG Adoption poll for draft-ldbc-cats-framework
Thread-Index: AdpmdjfuYgJOeHzERbaqW70ldzhSIACRPPFQ
Date: Mon, 26 Feb 2024 14:11:41 +0000
Message-ID: <4e6925b3b6ff4b39b15a7a537a65f013@huawei.com>
References: <01ab01da6677$86be97f0$943bc7d0$@olddog.co.uk>
In-Reply-To: <01ab01da6677$86be97f0$943bc7d0$@olddog.co.uk>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.112.41.128]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/cats/vO2bvda_E8Mfb9RSm9nQrYZWPzw>
Subject: Re: [Cats] CATS WG Adoption poll for draft-ldbc-cats-framework
X-BeenThere: cats@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Computing-Aware Traffic Steering \(CATS\)" <cats.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cats>, <mailto:cats-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cats/>
List-Post: <mailto:cats@ietf.org>
List-Help: <mailto:cats-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cats>, <mailto:cats-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Feb 2024 14:11:50 -0000

Yes, as a contributor who participates in the refinement of the document multiple times in github, I support the adoption.

Yes I have reviewed the document(again with refreshed eyes) and have some comments:

1. Section 2 Terminology: "CATS Instance Selector ID (CIS-ID):  An identifier of a specific service contact instance."

It looks like we are using two terms (Instance Selector and service contact instance) to refer to the same thing.

2. Section 3.4.1 Is service sites and service contact instance 1:1? If yes, why do we need the concept of the service site? And the service site in this section looks  different with the term defined in Section 2:

Section 2: Service site:  A location that hosts the resources that are required to offer a service.

      A service site may be a node or a set of nodes.

      A CATS-serviced site is a service site that is connected to a CATS-Forwarder.

VS:

Section 3.4.1: Service sites are the premises that host a set of computing resources.

3. Section 4.4: However, it is expected that a 
   service request or local policy may feed the C-PS computation logic
   with Objective Functions that provide some information about the path
   characteristics (e.g., in terms of maximum latency) and the selected
   service contact instance.

Is the objective function supposed to give the goal of the scheduling such as min(latency), min(standard deviation of site load) etc? If so, the information of the path and service contact instance is the input of the function not the function itself, right?

Yes, I think the document is the right document to meet the milestone. It merges some content from other drafts. I think it reflects the community consensus of the CATS framework.

Thanks,
Hang
 
-----Original Message-----
From: Cats <cats-bounces@ietf.org> On Behalf Of Adrian Farrel
Sent: Saturday, February 24, 2024 12:44 AM
To: 'cats' <cats@ietf.org>
Cc: draft-ldbc-cats-framework@ietf.org; cats-chairs@ietf.org
Subject: [Cats] CATS WG Adoption poll for draft-ldbc-cats-framework

Hi CATS,

We have had IPR disclosure responses from all authors and contributors.
All but one have indicated "no IPR", with the remaining one stating that there is IPR, but the company is doing a detailed analysis before filing a disclosure.

The working group has a milestone for "Adopt the CATS Framework and Architecture document"

So, we are going to start a two week adoption poll for the draft. This will end on 9th March at 9am GMT.

Please state your opinions on whether or not this document should be adopted. Authors and Contributors are also welcome to state their opinions.
Recall that the document does not have to be perfect at this point: we are looking for a starting point that can be taken up by the WG and edited until it is complete and ready.

A simple yes or no is helpful, but doesn't carry much weight.

So, if "yes":
- have you reviewed the document?
- do you have any comments or editorial suggestions?
- do you think this is the right document to meet the milestone?
- why do you think this is a good document?

And, if "no":
- what are your concerns?
- what is your proposal to meet the milestone?

If the current IPR situation is a significant concern to you, you are welcome to state that.

Thanks,
Adrian (for the chairs)

--
Cats mailing list
Cats@ietf.org
https://www.ietf.org/mailman/listinfo/cats