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

Joel Halpern <jmh@joelhalpern.com> Fri, 25 August 2023 14:28 UTC

Return-Path: <jmh@joelhalpern.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 178D4C1524AA; Fri, 25 Aug 2023 07:28:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.187
X-Spam-Level:
X-Spam-Status: No, score=-2.187 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, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.091, RCVD_IN_ZEN_BLOCKED_OPENDNS=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
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 M5caMpSEukqH; Fri, 25 Aug 2023 07:28:38 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (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 2F8FAC1522A0; Fri, 25 Aug 2023 07:28:38 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 4RXMks6R3lz6GyjQ; Fri, 25 Aug 2023 07:28:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1692973717; bh=JQPoRroBC3I0ndh3lQjJCvYjykYRGpbr/gLGf0X0pdI=; h=Date:Subject:To:References:From:In-Reply-To:From; b=X6eZiN5rD/YRR4ifa/RVnA6HgB+4yWGQ9M4V86Ct41wkNYxAVhWV5a3KFfnp8XRSE IsXBU5eVG4Zmowlxy9G1iU4Y60s/zHA8fUic/+NXa99TatfGkDwC6MEDywxUcHj3MX biC0kWxTSZg+sq8z3fGCdDojccg1rmq8HwKyr1zE=
X-Quarantine-ID: <4-bmwB1ipAIa>
X-Virus-Scanned: Debian amavisd-new at a2.tigertech.net
Received: from [192.168.20.19] (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 maila2.tigertech.net (Postfix) with ESMTPSA id 4RXMkp2Py9z6G7kV; Fri, 25 Aug 2023 07:28:31 -0700 (PDT)
Content-Type: multipart/alternative; boundary="------------boFdlNC00Wf2fA3BO9CMjCCB"
Message-ID: <85e38cc8-5afe-486e-1d06-ced74057ec07@joelhalpern.com>
Date: Fri, 25 Aug 2023 10:28:30 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.14.0
Content-Language: en-US
To: "Wubo (lana)" <lana.wubo@huawei.com>, tom petch <ietfa@btconnect.com>, Lou Berger <lberger@labn.net>, "draft-wdbsp-teas-nrp-yang@ietf.org" <draft-wdbsp-teas-nrp-yang@ietf.org>, "teas@ietf.org" <teas@ietf.org>
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> <38f027f4f46945d1a5e65caaddbafb99@huawei.com>
From: Joel Halpern <jmh@joelhalpern.com>
In-Reply-To: <38f027f4f46945d1a5e65caaddbafb99@huawei.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/pi6AibL2oG4fbOaYSKiOaG4_5PE>
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 14:28:42 -0000

Enhanced VPN explicitly says it is not tied to NRPs.  Sure, it could be 
used for NRPs.  I even expect to use it as one of the delivery 
mechanisms.   But at the very least we woul dneed to indicate in the 
description that we ar enot restricting it to those choices.

And that still leaves MPLS, which is very much up in the air as to how 
it will / should be representeding NRPs.  Will you replace the MPLS 
parts with a palceholder?

Yours,

Joel

On 8/25/2023 5:56 AM, Wubo (lana) wrote:
>
> 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/ 
> <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/ 
> <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 
> <https://www.ietf.org/mailman/listinfo/teas>
>
> > _______________________________________________
>
> > Teas mailing list
>
> > Teas@ietf.org <mailto:Teas@ietf.org>
>
> > https://www.ietf.org/mailman/listinfo/teas 
> <https://www.ietf.org/mailman/listinfo/teas>
>
> _______________________________________________
>
> Teas mailing list
>
> Teas@ietf.org <mailto:Teas@ietf.org>
>
> https://www.ietf.org/mailman/listinfo/teas 
> <https://www.ietf.org/mailman/listinfo/teas>
>
> _______________________________________________
>
> Teas mailing list
>
> Teas@ietf.org <mailto:Teas@ietf.org>
>
> https://www.ietf.org/mailman/listinfo/teas 
> <https://www.ietf.org/mailman/listinfo/teas>
>