Re: [Teas] Status update on draft-ietf-teas-sf-aware-topo-model

Xufeng Liu <xufeng.liu.ietf@gmail.com> Fri, 20 November 2020 01:26 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 2DF2E3A14AF for <teas@ietfa.amsl.com>; Thu, 19 Nov 2020 17:26:28 -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 Yx56_KpSzvDj for <teas@ietfa.amsl.com>; Thu, 19 Nov 2020 17:26:26 -0800 (PST)
Received: from mail-ej1-x62e.google.com (mail-ej1-x62e.google.com [IPv6:2a00:1450:4864:20::62e]) (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 ED5043A14AE for <teas@ietf.org>; Thu, 19 Nov 2020 17:26:25 -0800 (PST)
Received: by mail-ej1-x62e.google.com with SMTP id f20so10642342ejz.4 for <teas@ietf.org>; Thu, 19 Nov 2020 17:26:25 -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=d/T9B3iTpMcQvmnibKwMydqDKQuZVBl2xgUpepr4Yr0=; b=O1KQYZ3E7Gnxk0ql9uFG62+4h5S9vTIYC3jZvCAp3T0SVYX8riaqO0183PRtz+2Fuk gg1knkdfRqECDW0nz96JX/V5TwLNwYPfPZweaANsAdd1T3MASqqCf16p+YOGclAi/kCO 55ajWeo6NEVvlxDlc0vscBYemyBRaW9MzUpJNytl+j7o25ltojNJAQxMMZfEg4ClZmFx qXXro07Rh9t1F4DQ08dnCvUrzri4aYI7rmJW6dXcm0m9u8HiOPrJvMiEeeAWhT4V3Xfx Y9yB1sqM2SZXSg07oeNwVrGAk2apyJJRwy1TvZZD6EhcZzOOnIoVUoFMQzaXAcUS95Lg byww==
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=d/T9B3iTpMcQvmnibKwMydqDKQuZVBl2xgUpepr4Yr0=; b=KZdu3QhEjN054wDKQ9PDLVFEhJsS0L77vxbkBctiTG9wLx64XV5YKZXjDCUiyg1q24 lqBe7Vwl0xcJdDFx6oKzAC68tQjE1QlxwP+flvuZThC+dhZOzIHkkAPB3UNbInogOu5b iKlSUhITM15RHyAkXEbPt227d1XdbyBj4NZVG7DYLJWoNeY5UNGQvVgr4n+R6i/6PUOM 3VWIwFjvHWJCBD7UtNTo3c0NAtoudG7VAAFFmB/WQzpe/bHcMYMF7nRae+PEhQnPTvOy OO1ttdyNwvVq0ILQXidODhSrMU6AgXP7SvUfIj6GEAp4ott3N8osVb3szgxm6ozJMvQg eRIQ==
X-Gm-Message-State: AOAM5322NmSAKb9SHIjcnv7Dk2PbydwlJV+xRBNLXq+3NgYgsCSO5sib HvNhuwAn5TyMGv5ggs1iBCfy21XxSh/48p++8w0wc6G0StQ=
X-Google-Smtp-Source: ABdhPJyScamTNljY2LyuMFN57fpIN6koHzY0NAXseXWeB1DqySW/sJpRCvbPHo+xgU4198xk/RCN3sNDjSlgO0j/P14=
X-Received: by 2002:a17:906:4753:: with SMTP id j19mr28965754ejs.65.1605835584401; Thu, 19 Nov 2020 17:26:24 -0800 (PST)
MIME-Version: 1.0
References: <CAEz6PPRNjcZZ+m9ZHX7zCyD7VqueftpZCW_UuyBdozfmzSik-g@mail.gmail.com> <030801d4e3bb$26523be0$4001a8c0@gateway.2wire.net> <CAEz6PPSih7=g4oZDWypP0+MX5T_h+8SPpdb98sg_RE9jfsw-GA@mail.gmail.com> <DB7PR07MB5340C9405DC5569447F664EBA2C10@DB7PR07MB5340.eurprd07.prod.outlook.com>
In-Reply-To: <DB7PR07MB5340C9405DC5569447F664EBA2C10@DB7PR07MB5340.eurprd07.prod.outlook.com>
From: Xufeng Liu <xufeng.liu.ietf@gmail.com>
Date: Thu, 19 Nov 2020 20:26:13 -0500
Message-ID: <CAEz6PPQOzBU6UH1z6+DXe0Fk1=N0iURbuQeQVX_-E=2YRVXTVw@mail.gmail.com>
To: tom petch <ietfa@btconnect.com>
Cc: TEAS WG <teas@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000093738205b47fbbac"
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/clh-VRIwzfvQ8nK7W-kAuUX0ki4>
Subject: Re: [Teas] Status update on draft-ietf-teas-sf-aware-topo-model
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: Fri, 20 Nov 2020 01:26:28 -0000

Hi Tom,

We have posted an updated version
https://tools.ietf.org/html/draft-ietf-teas-sf-aware-topo-model-06, to
address the two additional items below.

Thanks,
- Xufeng

On Thu, Apr 9, 2020 at 7:08 AM <ietfa@btconnect.com> wrote:

> From: Xufeng Liu <xufeng.liu.ietf@gmail.com>
> Sent: 12 March 2020 21:57
>
> We have posted the updated version (
> https://tools.ietf.org/html/draft-ietf-teas-sf-aware-topo-model-05 ) to
> fix the issues that you raised.
> Thanks a lot,
>
> <tp>
> Xufeng,
>
> looks better and apologies for being slow to respond.
>
> C.12 IANA, C.13 Security look odd and contradict s.5, s.6.  Is there any
> reason for them to exist?
>
> Security s.6 does not conform to the boiler plate referenced in RFC8407.
> This asks that sensitive nodes be called out and I would think that at
> least the enable nodes for connectivity matrix and link terminations would
> qualify for that.
>
[Xufeng]: Fixed. C.13 is now following RFC8407. s.5, s.6. were mistakenly
merged from a different draft (
https://tools.ietf.org/html/draft-ietf-teas-use-cases-sf-aware-topo-model-00).
These two sections have now been removed.

>
> Tom Petch
>
> - Xufeng
>
> On Tue, Mar 26, 2019 at 6:05 AM tom petch <ietfa@btconnect.com<mailtomailto:
> ietfa@btconnect.com>> wrote:
> Xufeng
>
> Some quirks.
>
> Introduction/Abstract do not mention support or lack thereof  for NMDA
> (which the IESG have been calling for).
> [Xufeng]: Added.
>
> Introduction does not have a reference for YANG leaving the question of
> version number uncertain
> [Xufeng]: Added.
>
> Terminology fails to reference RFC8174
> [Xufeng]: Fixed
>
> Expand on first use, perhaps in Terminology, is helpful - TOSCA, SF2LTP,
> SF2SF, SF2TTP,
> [Xufeng]: Fixed
>
> CSO
> [Xufeng]: Authors and contributors discussed CSO and decided to remove it
> from this document and put it into a separate document.
>
> yang-version 1 is rather limiting
> [Xufeng]: Use 1.1 now.
>
> YANG import statements lack references (which YANG 1.1 allows)
>
> /       reference "TBD";/
>        reference "RFC XXXX - SF Aware TE Topology YANG Model"; /
> [Xufeng]: Fixed these statements.
>
>    module ietf-cso-dc
> no version
> no copyright
> no reference to the I-D
> no description clauses
> no reference clauses
> somewhat short of ready IMHO- I think that this needs a lot of work!
> [Xufeng]: As mentioned above, CSO is removed from this document and
> planned to be put into a separate document.
>
> IANA Considerations
>    RFC Ed.: In this section, replace all occurrences of 'XXXX' with the
>    actual RFC number (and remove this note).
> I suggest that this apply throughout the I-D and that the Note is placed
> at the start, before the Introduction (the RFC Editor are happy with
> just the one note)
> [Xufeng]: Changed as suggeted.
>
> RFC6020 is a better reference for the IANA Considerations
> [Xufeng]: Right. Use  RFC6020 now.
>
>    [I-D.ietf-netmod-revised-datastores]
> RFC8342
> [Xufeng]: Fixed.
>
>    [I-D.ietf-netmod-yang-tree-diagrams]
> RFC8340
> [Xufeng]:  Fixed.
>
>    [I-D.ietf-i2rs-yang-network-topo]
> RFC8345
> [Xufeng]: Fixed.
>
>      import ietf-actn-vn {
> does not appear in section 1.3
> [Xufeng]: Added.
>
> Tom Petch
>
> ----- Original Message -----
> From: "Xufeng Liu" <xufeng.liu.ietf@gmail.com<mailtomailto:
> xufeng.liu.ietf@gmail.com>>
> To: "TEAS WG" <teas@ietf.org<mailto:teas@ietf.org>>
> Sent: Saturday, March 23, 2019 12:02 PM
> Subject: [Teas] Status update on draft-ietf-teas-sf-aware-topo-model
>
>
> > Current Status:
> >
> >   *  The updated revision -03 was posted on Mar 11, 2019:
> >
> >      > Editorial fixes.
> >
> > Open Issues:
> >
> >   *   None.
> >
> > Next Steps:
> >
> >   *  Update the document to align with the latest versions of
> >      referenced documents, including draft-ietf-teas-yang-te-topo,
> >      RFC8340, RFC8342, RFC8345, and RFC8459.
> >   *  Update the section of Security Considerations according to latest
> >      guidelines.
> >   *  Get further reviews.
> >   *  YANG doctor's review.
> >   *  Working Group Last Call after completing above.
> >
> > Thanks,
> > - Xufeng
> >
>
>
> ------------------------------------------------------------------------
> --------
>
>
> > _______________________________________________
> > Teas mailing list
> > Teas@ietf.org<mailto:Teas@ietf.org>
> > https://www.ietf.org/mailman/listinfo/teas
> >
>
>