Re: [Teas] Some stray thoughts on draft-wdbsp-teas-nrp-yang was ....

"Wubo (lana)" <lana.wubo@huawei.com> Fri, 25 August 2023 09:56 UTC

Return-Path: <lana.wubo@huawei.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A669C1516E0; Fri, 25 Aug 2023 02:56:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.892
X-Spam-Level:
X-Spam-Status: No, score=-1.892 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, 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_KAM_HTML_FONT_INVALID=0.01, 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 kiHm2mRkkqHh; Fri, 25 Aug 2023 02:56:35 -0700 (PDT)
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 A28F6C15108D; Fri, 25 Aug 2023 02:56:34 -0700 (PDT)
Received: from lhrpeml100004.china.huawei.com (unknown [172.18.147.207]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4RXFc43tcCz67k9Y; Fri, 25 Aug 2023 17:52:20 +0800 (CST)
Received: from kwepemi500011.china.huawei.com (7.221.188.124) by lhrpeml100004.china.huawei.com (7.191.162.219) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.31; Fri, 25 Aug 2023 10:56:32 +0100
Received: from kwepemi500014.china.huawei.com (7.221.188.232) by kwepemi500011.china.huawei.com (7.221.188.124) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.31; Fri, 25 Aug 2023 17:56:30 +0800
Received: from kwepemi500014.china.huawei.com ([7.221.188.232]) by kwepemi500014.china.huawei.com ([7.221.188.232]) with mapi id 15.01.2507.031; Fri, 25 Aug 2023 17:56:30 +0800
From: "Wubo (lana)" <lana.wubo@huawei.com>
To: tom petch <ietfa@btconnect.com>, Lou Berger <lberger@labn.net>, Joel Halpern <jmh@joelhalpern.com>, "draft-wdbsp-teas-nrp-yang@ietf.org" <draft-wdbsp-teas-nrp-yang@ietf.org>, "teas@ietf.org" <teas@ietf.org>
Thread-Topic: Some stray thoughts on draft-wdbsp-teas-nrp-yang was ....
Thread-Index: AQHZ1a1krg2XPnNBT0mI7O/AxnFkb6/3r4d6gAMQdoA=
Date: Fri, 25 Aug 2023 09:56:30 +0000
Message-ID: <38f027f4f46945d1a5e65caaddbafb99@huawei.com>
References: <169270869438.18635.883672878255246067@ietfa.amsl.com> <7ae4f391-a9c3-2c3e-a253-5aa12f8fb586@joelhalpern.com> <1d0495f8-fcf3-44b9-c078-4d460a5374d5@labn.net> <DB7PR07MB55462A48AD61D908E3EE490BA21CA@DB7PR07MB5546.eurprd07.prod.outlook.com> <DB7PR07MB5546FF2065D800A65E8A3336A21CA@DB7PR07MB5546.eurprd07.prod.outlook.com>
In-Reply-To: <DB7PR07MB5546FF2065D800A65E8A3336A21CA@DB7PR07MB5546.eurprd07.prod.outlook.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.136.114.167]
Content-Type: multipart/alternative; boundary="_000_38f027f4f46945d1a5e65caaddbafb99huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/hsTH-Kvd1IQ7b-u8rJ-xUuNB18E>
Subject: Re: [Teas] Some stray thoughts on draft-wdbsp-teas-nrp-yang was ....
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Aug 2023 09:56:39 -0000

Hi Tom,



Many thanks for your review. Please see inline with [Bo Wu].



Thanks,

Bo Wu



-----Original Message-----
From: tom petch <ietfa@btconnect.com>
Sent: Wednesday, August 23, 2023 6:45 PM
To: Lou Berger <lberger@labn.net>; Joel Halpern <jmh@joelhalpern.com>; draft-wdbsp-teas-nrp-yang@ietf.org; teas@ietf.org
Subject: Re: Some stray thoughts on draft-wdbsp-teas-nrp-yang was ....



mmm no it was not me that sent this prematurely, doubtless AI at work:-(

completions (I hope) below



________________________________________

From: Teas <teas-bounces@ietf.org<mailto:teas-bounces@ietf.org>> on behalf of tom petch <ietfa@btconnect.com<mailto:ietfa@btconnect.com>>

Sent: 23 August 2023 11:33



I share Joel's concern - it does seem premature with the undecided or unresolved issues relating to NRP (or whatever name emerges)

[Bo Wu] For the NPR selector , we will include the following references of the drafts to the encapsulation of SRv6 and IPv6 hop-by-hop option:

a)        draft-ietf-spring-sr-for-enhanced-vpn

b)        draft-ietf-6man-enhanced-vpn-vtn-id



Meanwhile, I looked at the YANG



Normative references are required for

6991 -

8294 -

8519 -

8776 -

draft-bestbar-teas-yang-topology-filter



[Bo Wu] Thanks. Will add.



and for whatever contains srv6-types which is not a module I can find in IANA

[Bo Wu] The reference of draft-ietf-spring-srv6-yang will be added.



'This draft defines ...'

perhaps 'document'

[Bo Wu] Will update.



The document title is sometimes spelt as a plural but more often in the singular

[Bo Wu] We will clean up the text to go with a plural.



NRP would benefit from a reference where it first appears.

[Bo Wu] OK. Will clarify this.



SLO SLE need expanding on first use

[Bo Wu] Will do per your suggestion.



        WG Web: <http://tools.ietf.org/wg/teas/> is out of date twice

[Bo Wu] Will fix.



         "RFC XXX: A YANG Data Model for Network Resource Partition"; perhaps

         "RFC XXXX: A YANG Data Model for Network Resource Partitions";

[Bo Wu] Thanks. Fixed.



             leaf maximum-bandwidth {

what are the units?

[Bo Wu] Will change to units "bits/second".



         presence "indicates NRP IGP congruent"; I think that congruence needs defining.  If two triangles are congruent, then I know what must be the same, what must be different.  I do not have that understanding for network topology

[Bo Wu] "igp-congruent" indicates the NRP instance use same IGP topology as the "multi-topology-id"and "flex-algo-id"specified. We will clarify this.



         units "bps";

bits or bytes?

[Bo Wu] Will change to units "bits/second".



         "Introduces new network type for NRP topology"; reminds me of a decrepit and rusty sign  on the road near me that announces a new road layout, dating from over a decade ago.

[Bo Wu] We will change to "Indicates the network type of NRP" if this is clearer.



   The following individuals, authors of

   [I-D.bestbar-teas-yang-nrp-policy] and [I-D.wd-teas-nrp-yang],

   contributed to this consolidated document:



Should that also include

draft-wd-teas-vtn-network-yang-00.txt 6jun21 22pp If only to point out another name change in the predecessors?

[Bo Wu] We hope that all the authors and contributors have been acknowledged, considering the data tracker has a history, we did not include all thel historical files.



Tom Petch

(who  will now press send)



________________________________________

From: Teas <teas-bounces@ietf.org<mailto:teas-bounces@ietf.org>> on behalf of Lou Berger <lberger@labn.net<mailto:lberger@labn.net>>

Sent: 22 August 2023 18:02

To: Joel Halpern; draft-wdbsp-teas-nrp-yang@ietf.org<mailto:draft-wdbsp-teas-nrp-yang@ietf.org>; teas@ietf.org<mailto:teas@ietf.org>

Subject: Re: [Teas] The TEAS WG has placed draft-wdbsp-teas-nrp-yang in state "Candidate for WG Adoption"



FWIW the adoption call will start once we have all IPR declarations...



On 8/22/2023 12:57 PM, Joel Halpern wrote:

> While this mostly looks like a good start, I am concerned that

> adopting it would presume that we know what the correct representation

> for NRP identification is for the various cases (IPv6, SRv6, and

> MPLS.)  As none of those are as far as I know adopted by the

> respective working groups, it seems premature to adopt that.

>

> It seems to me that we can either adopt this with placeholders for

> identification (indicating that we will work on it later), or defer

> adoption.

>

> Yours,

>

> Joel

>

> On 8/22/2023 8:51 AM, IETF Secretariat wrote:

>> The TEAS WG has placed draft-wdbsp-teas-nrp-yang in state Candidate

>> for WG Adoption (entered by Lou Berger)

>>

>> The document is available at

>> https://datatracker.ietf.org/doc/draft-wdbsp-teas-nrp-yang/

>>

>>

>> _______________________________________________

>> Teas mailing list

>> Teas@ietf.org<mailto:Teas@ietf.org>

>> https://www.ietf.org/mailman/listinfo/teas

> _______________________________________________

> Teas mailing list

> Teas@ietf.org<mailto:Teas@ietf.org>

> https://www.ietf.org/mailman/listinfo/teas



_______________________________________________

Teas mailing list

Teas@ietf.org<mailto:Teas@ietf.org>

https://www.ietf.org/mailman/listinfo/teas



_______________________________________________

Teas mailing list

Teas@ietf.org<mailto:Teas@ietf.org>

https://www.ietf.org/mailman/listinfo/teas