Re: [Teas] Status update on draft-ietf-teas-yang-sr-te-topo
Xufeng Liu <xufeng.liu.ietf@gmail.com> Wed, 11 November 2020 19:22 UTC
Return-Path: <xufeng.liu.ietf@gmail.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 DDC343A0DAB for <teas@ietfa.amsl.com>; Wed, 11 Nov 2020 11:22:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5OvYmds20tat for <teas@ietfa.amsl.com>; Wed, 11 Nov 2020 11:22:56 -0800 (PST)
Received: from mail-ej1-x631.google.com (mail-ej1-x631.google.com [IPv6:2a00:1450:4864:20::631]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2EE0D3A0E83 for <teas@ietf.org>; Wed, 11 Nov 2020 11:22:56 -0800 (PST)
Received: by mail-ej1-x631.google.com with SMTP id 7so4317847ejm.0 for <teas@ietf.org>; Wed, 11 Nov 2020 11:22:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=zKuWt9Z33LlYuw4Rp6D6qh7iIJFMCTnD1ikKn7H86sA=; b=mThJteJXTleaYV+/4Z5RpuUJfknQhE8mG78HctKwKXLnQV5WjiErcXD2HCt9ymSSkD D/m6lfgXLDwLZ30E4dKnh926T5SukpgF/WTSUqLrOKCybyAe5THYUn6ahT6lx6lgRiYS RJN+JR76wVYdCkTorLjzfn9zvcapTtGSxMgKkLq6CWbtx49pBQ6VNrqS865ACrHtZtwa LmKDH5EGoMGqk3PzJBNVcbEjKW80aMmeUN+7ik2ZYCxVGZVbkeYwwiIA0XP+3EBD4ZL/ jcbEU6sDuFxsKaFPSrdZRjHkuef53ms3AEMB62god+YNY1CoAC2++ErrWrRDePrI86mw 0ZvQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=zKuWt9Z33LlYuw4Rp6D6qh7iIJFMCTnD1ikKn7H86sA=; b=mSPxOw2tQkAY65uu1Ik9JjYMohrd9g5Zah3zfdRce8RUnXLizT0IaclQ1RS50M+zVr aUG4TvneDuKex8wn9Bofrfas5SBxmbK2tASHwpLLErFAqHUfo8Ule7El69zWp49s5NK1 mbXV37IDMeBU9mNMZCEELU3nCkWUYnw3FQ7RoRRqa/UxQyNYAmCVaYCdMYkgEoS5CxjT 9MTJf3iZgty/IGrR/yrK9ifr8u/JK8ceaNp3mM1nEBRzVqhpvrY86JeYND/HMjRsgOpJ wV5KmhAfNJXRUfK+UmTk0DNp36xsW/xEwZf5fNJQDatwP8P2baSMemOr4UjBYvW+5YFy kuSQ==
X-Gm-Message-State: AOAM530O2uU0w3J/9OYxpnkMi8KrAzS+jSpw+AAtCLKmCogr2dAhslRM JGaMJXEnUOAsY5OGvgJPZyxGB451FIOwj9wvLc8=
X-Google-Smtp-Source: ABdhPJz3+Ba/ypj+OBXyCwvp4jcApO5XJwPdVYF4mxeAYidr/5S839i0kVFW326AeW6k4x2LIRrdPD/+bYjvxHO0YWA=
X-Received: by 2002:a17:906:944f:: with SMTP id z15mr28057254ejx.111.1605122574435; Wed, 11 Nov 2020 11:22:54 -0800 (PST)
MIME-Version: 1.0
References: <CAEz6PPTm0vW+6HLjTv-dQQu7ccuRPcTN5jP4D5HtZt5nQwROYw@mail.gmail.com> <DB7PR07MB53401963CB478EA84CE0FEE1A2A80@DB7PR07MB5340.eurprd07.prod.outlook.com> <DB7PR07MB53400D95E243D7ACE86352DAA2A90@DB7PR07MB5340.eurprd07.prod.outlook.com> <CAEz6PPRpsnO_eJiKUmCP5u8o9WwVKj4xkx9K2BsOkZsZMFscKg@mail.gmail.com> <AM0PR07MB53297327553E9048BC697554A27E0@AM0PR07MB5329.eurprd07.prod.outlook.com>
In-Reply-To: <AM0PR07MB53297327553E9048BC697554A27E0@AM0PR07MB5329.eurprd07.prod.outlook.com>
From: Xufeng Liu <xufeng.liu.ietf@gmail.com>
Date: Wed, 11 Nov 2020 14:22:43 -0500
Message-ID: <CAEz6PPRK+JrYieYue6hWhZ5g5nPJ_A5fWqpjh9RiUC08fM9+Og@mail.gmail.com>
To: tom petch <ietfa@btconnect.com>
Cc: TEAS WG <teas@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000deca5505b3d9b899"
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/GSa85cACU_1EREmEKR2qdBcLJhA>
Subject: Re: [Teas] Status update on draft-ietf-teas-yang-sr-te-topo
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 11 Nov 2020 19:22:59 -0000
Hi Tom, Thanks for your further comments. We are trying to address them with an updated draft https://tools.ietf.org/html/draft-ietf-teas-yang-sr-te-topo-08. Some of the answers and discussions are in-line below. Regards, - Xufeng On Wed, Jul 15, 2020 at 7:14 AM tom petch <ietfa@btconnect.com> wrote: > From: Xufeng Liu <xufeng.liu.ietf@gmail.com> > Sent: 13 July 2020 02:11 > > Hi Tom, > > Thank you much for the much-needed review. We have posted the updated > revision > https://datatracker.ietf.org/doc/html/draft-ietf-teas-yang-sr-te-topo-07, > trying to address these comments. Please also see the replies in-line below. > Best regards, > > <tp> > Yes, clearer. > > IANA needs updating with the amended prefix > [Xufeng]: Fixed (Thanks for noticing) > > A recent YANG doctor review said that all feature should have reference > which sounds right. Perhaps RFC8476, RFC8491 along with RFC7752 for msd > [Xufeng]: Added the references. > > Diagrams are useful but .. > these seem the opposite to e.g. yang-l3-te-topo > Does A---> B mean A augments B or B augments A? Would be nice to be > consistent. Perhaps one for the YANG Doctors list. > [Xufeng]: Thanks for bringing it up in the netmod WG. I agree with your instinct, but the arrow direction used in this diagram originally came from RFC8345, so I’m not sure how we can fix the consistency here. > > Another common practice in most TEAS Yang I-D is to have a table in the > text of prefix used and the corresponding module and reference. > [Xufeng]: Added such a section. > > Tom Petch > > - Xufeng > > On Sun, May 3, 2020 at 11:46 AM tom petch <ietfa@btconnect.com<mailto: > ietfa@btconnect.com>> wrote: > And while you are at it .. > > I don't understand quite a lot of this I-D. > > In places it is explicit - MPLS data plane only. Elsewhere it seems to > claim to be for all SR as with the choice of prefix srt module name or with > container SR or with the Abstract. If this is MPLS data plane only. then I > think that that needs spelling out in more places starting with the Abstract > [Xufeng]: As suggested, used MPLS throughout the document and the model, > including module name, prefixes, and container names. > > 2.1 references unicast-igp-topology - I know of no such module > [Xufeng]: Fixed the typo. > > 2.7 Both IGP and BGP are supported ...is this BGP or BGP-LS? > [Xufeng]: Right. This is BGP-LS. Fixed the term and added some references. > > feature msd > what if one IGP supports msd and another does not, say OSPFv2 does and > OSPFv3 does not? I don't know if that will happen or if it should be > supported but, for once, YANG does have good support for such an approach > [Xufeng] msd is a device feature, independent of the protocols. In case > that one particular protocol does not support msd, the corresponding leaf > msd in the operational datastore will not have a value. Since the user > knows which protocol provides the information based on the > information-source, he will understand the reason for it. > > grouping sr topology type > a presence container for SR-MPLS - good > But how about > sr node prefix attributes > a presence container which indicates SR is enabled and > [Xufeng]: Since a prefix may or may not be configured with a Prefix-SID, > the "presence" statement will allow such an option. > sr link attributes > a presence container which indicates SR is enabled. > [Xufeng]: Since an L3 link may or may not be configured with an Adj-SID, > the "presence" statement will allow such an option. > That is eight possible combinations of presence containers with eight > different interpretations - I do not understand what they mean. I do > realise that the groupings have different roles. > [Xufeng]: Two "presence" side effects relevant here are: (1) to assign a > semantic meaning (non-presence container can be ignored); (2) to stop > propagating the "mandatory" requirement to the parent container. > > > RFC 7752 is the reference for BGP-LS but > needs to be in the I-D references. > [Xufeng]: Added. > And how about references for OSPFv2 etc? > [Xufeng]: Also added. > Currently BGP-LS may be new and different and people want to know where to > find it but in a year or two they may be wondering what OSPFv2 is or was. > > Since you import sr-routing-cmn I cannot see how that can fail to be a > Normative Reference - I cannot understand the I-D without it! > [Xufeng]: Fixed. > > Tom Petch > ________________________________________ > From: Teas <teas-bounces@ietf.org<mailto:teas-bounces@ietf.org>> on > behalf of tom petch <ietfa@btconnect.com<mailto:ietfa@btconnect.com>> > Sent: 02 May 2020 12:16 > To: Xufeng Liu; TEAS WG > Subject: Re: [Teas] Status update on draft-ietf-teas-yang-sr-te-topo > > Xufeng > > I suggest you respin this I-D lest it expires in four days time. > > Tom Petch > > ________________________________________ > From: Teas <teas-bounces@ietf.org<mailto:teas-bounces@ietf.org>> on > behalf of Xufeng Liu <xufeng.liu.ietf@gmail.com<mailto: > xufeng.liu.ietf@gmail.com>> > Sent: 21 April 2020 21:10 > > Current Status: > > * No update since IETF106 with last post on November 3, 2019. > * Answered YANG doctor's review comments. > > Open Issues: > > * None. > > Next Steps: > > * Update the model to sync with the referenced models like > draft-ietf-spring-sr-yang if there are any changes. > * Welcome further reviews and suggestions. > * Working Group Last Call after completing the above. > > Thanks, > - Xufeng > > > _______________________________________________ > Teas mailing list > Teas@ietf.org<mailto:Teas@ietf.org> > https://www.ietf.org/mailman/listinfo/teas >
- [Teas] Status update on draft-ietf-teas-yang-sr-t… Xufeng Liu
- Re: [Teas] Status update on draft-ietf-teas-yang-… tom petch
- Re: [Teas] Status update on draft-ietf-teas-yang-… tom petch
- Re: [Teas] Status update on draft-ietf-teas-yang-… Xufeng Liu
- Re: [Teas] Status update on draft-ietf-teas-yang-… tom petch
- Re: [Teas] Status update on draft-ietf-teas-yang-… Xufeng Liu