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

Dirk Trossen <dirk.trossen@huawei.com> Mon, 26 February 2024 15:35 UTC

Return-Path: <dirk.trossen@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 59134C14CE24; Mon, 26 Feb 2024 07:35:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.904
X-Spam-Level:
X-Spam-Status: No, score=-1.904 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 wM0Lw6QeA9EX; Mon, 26 Feb 2024 07:35:13 -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 B63E4C151981; Mon, 26 Feb 2024 07:34:58 -0800 (PST)
Received: from mail.maildlp.com (unknown [172.18.186.216]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4Tk4M10Kdxz6K6Wg; Mon, 26 Feb 2024 23:30:37 +0800 (CST)
Received: from lhrpeml500004.china.huawei.com (unknown [7.191.163.9]) by mail.maildlp.com (Postfix) with ESMTPS id EAD1E1400DB; Mon, 26 Feb 2024 23:34:55 +0800 (CST)
Received: from lhrpeml500003.china.huawei.com (7.191.162.67) by lhrpeml500004.china.huawei.com (7.191.163.9) 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 15:34:55 +0000
Received: from lhrpeml500003.china.huawei.com ([7.191.162.67]) by lhrpeml500003.china.huawei.com ([7.191.162.67]) with mapi id 15.01.2507.035; Mon, 26 Feb 2024 15:34:55 +0000
From: Dirk Trossen <dirk.trossen@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: AdpmdjfuYgJOeHzERbaqW70ldzhSIACUdYmA
Date: Mon, 26 Feb 2024 15:34:55 +0000
Message-ID: <260afcc0421343a18133a1cfe30504ac@huawei.com>
References: <01ab01da6677$86be97f0$943bc7d0$@olddog.co.uk>
In-Reply-To: <01ab01da6677$86be97f0$943bc7d0$@olddog.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.52.137.247]
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/D5TX8rCfOn3mOSqkLid-paxZzU4>
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 15:35:15 -0000

All,

As a contributor to initial versions of this document and its iterations later on, I support WG adoption of this draft. 

Building on previously made comments (specifically by Joel and Hang), I would like to also turn the attention to the objective function (or specific algorithm for processing). While the definition of specific algorithms is deemed out of scope for this document (and as Joel points out, for current solution proposals overall), I still wonder how the sentence "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" may look in real life? Is this an out-of-scope config issue (it 'somehow' makes it into the C-PS?)? Or could we see the definition of the objective function part of the metric distribution itself (if I distribute metrics, wouldn't I want to somehow link those to the usage within an objective function?). Given that this is a framework document, some words on this may be useful to add - note here that allowing to explicitly link metrics to objective functions (as part of the framework) is somehow the opposite of mandating specific algorithms being used (which I would not support, either, to avoid narrowing the solution space to a small set of such functions). 

Anyhow, beyond this comment, I see this document capturing the evolving discussion and consensus in the wider WG quite well and would like it to progress more!

Best,

Dirk 

-----Original Message-----
From: Cats <cats-bounces@ietf.org> On Behalf Of Adrian Farrel
Sent: 23 February 2024 17:44
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