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

Joel Halpern <jmh@joelhalpern.com> Sun, 25 February 2024 20:33 UTC

Return-Path: <jmh@joelhalpern.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 27FEBC14F5F2; Sun, 25 Feb 2024 12:33:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
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 AzzE5Xpd7NOA; Sun, 25 Feb 2024 12:33:33 -0800 (PST)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E4FBC14F5F8; Sun, 25 Feb 2024 12:33:33 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 4Tjb711PSLz1pLsF; Sun, 25 Feb 2024 12:33:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1708893213; bh=HKKHvqlisQLMZrXyTvC9oQV+bBQNu4roYS2L8fvWx3U=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=O5F3DeJKSgKttyPJYK7G/k/iuvmiiEuGVes1DEDQii7UFkoR+Kec3/bfLiB+alX+X 1um6KnLg/H3mjlqq3HnPD/eJDnzeVvQL18KH1cK6EteH2kbEAHZY7VFSXzlqgMZrrj /oJLa0Hc0akmqclnBKyzL29koA+hihzlKSJ2Qp2s=
X-Quarantine-ID: <sfpYo6yXxv-4>
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [192.168.20.146] (unknown [50.233.136.230]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 4Tjb7053WKz1p5jX; Sun, 25 Feb 2024 12:33:32 -0800 (PST)
Message-ID: <8ea03bdc-f11a-4482-8fd3-e733bb14a1b8@joelhalpern.com>
Date: Sun, 25 Feb 2024 15:33:30 -0500
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-US
To: 'cats' <cats@ietf.org>
Cc: draft-ldbc-cats-framework@ietf.org
References: <01ab01da6677$86be97f0$943bc7d0$@olddog.co.uk>
From: Joel Halpern <jmh@joelhalpern.com>
In-Reply-To: <01ab01da6677$86be97f0$943bc7d0$@olddog.co.uk>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/cats/e6yBBz4A0DD0RTAQoVrsrQ7Az1c>
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: Sun, 25 Feb 2024 20:33:38 -0000

I have reread the draft, and in my opinion it is ready for WG adoption.  
The following minor comments can be considered after adoption.

In the description of the CATS Service Metric Agent (C-SMA) it may make 
sense to note that it could be colocated with the Service Contact 
Instance.  (I presume that we are not trying to prohibit that.)

Section 3.4.7 uses the notation IP/MPLS.  The use of "/" is ambiguous as 
to whether it means "and", "or", or both in this context.  A slightly 
different use of the slash would be "IP and/or MPLS" which I believe 
would be clearer. (I believe that phrasing also allows for cases such as 
SRv6 infrastructure, so I do not think we need to get more elaborate in 
the wording.)

Should secction 4.4 on Sevice Access Processing note that per the4 CATS 
charter it is not anticipated at this time that solutions will mandate 
specific algorithms for the processing? (E.g. it is not merely out of 
scope for this document, but out of scope for current solution proposals.)

I think that the Security Considerations ection (5) should mention that 
CATS protocols MAY (or maybe MUST?) include support for encryption to 
address the disclosure risk that is described? This may in turn results 
in a slight rewording of the privacy considerations section?

Nit:

     Would it be helpful for the second paragraph of section 3.4.3 on 
the C-NMA to menion "may also participate directly in IGP(s)"?

     In section 3.6, the term "privileged option" is used.  I believe 
the meaning is better conveyed by "preferred option".

Yours,

Joel M. Halpern

On 2/23/2024 11:44 AM, Adrian Farrel wrote:
> 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)
>