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

tom petch <ietfa@btconnect.com> Tue, 26 March 2019 10:06 UTC

Return-Path: <ietfa@btconnect.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 D71431202A1 for <teas@ietfa.amsl.com>; Tue, 26 Mar 2019 03:06:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.247
X-Spam-Level:
X-Spam-Status: No, score=0.247 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RATWARE_MS_HASH=2.148, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.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 K-OS_kNe4ApR for <teas@ietfa.amsl.com>; Tue, 26 Mar 2019 03:06:01 -0700 (PDT)
Received: from EUR01-VE1-obe.outbound.protection.outlook.com (mail-eopbgr140093.outbound.protection.outlook.com [40.107.14.93]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4E6E9120282 for <teas@ietf.org>; Tue, 26 Mar 2019 03:06:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector1-btconnect-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=3VSiUEgLezSSPMfu/XdAXza0UX7BdV4eCK8aGmpPf1o=; b=hMK9AkrAMX+u/cwzr09gTuV3jLNnZpfKDo7VK2xmqU6CX2QwxQqKeHoTaspfR0gX/k5dSTkLY1174wkFaHQEbGh7bdo+1bm1yn2xgJx+wKXzO2Oe7LDQrRVTMV8Ya6OdfQ3x2dFDf/k3F/+Yelb7Gwz1fDwbavYWLMVAQwsvHUg=
Received: from VI1PR07MB4480.eurprd07.prod.outlook.com (20.177.57.76) by VI1PR07MB4413.eurprd07.prod.outlook.com (20.176.7.138) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1750.12; Tue, 26 Mar 2019 10:05:59 +0000
Received: from VI1PR07MB4480.eurprd07.prod.outlook.com ([fe80::9d64:eef4:45b4:441e]) by VI1PR07MB4480.eurprd07.prod.outlook.com ([fe80::9d64:eef4:45b4:441e%5]) with mapi id 15.20.1750.013; Tue, 26 Mar 2019 10:05:58 +0000
From: tom petch <ietfa@btconnect.com>
To: Xufeng Liu <xufeng.liu.ietf@gmail.com>, TEAS WG <teas@ietf.org>
Thread-Topic: [Teas] Status update on draft-ietf-teas-sf-aware-topo-model
Thread-Index: AQHU47uCu4vCPIdoU02dfsaQIzhTxw==
Date: Tue, 26 Mar 2019 10:05:58 +0000
Message-ID: <030801d4e3bb$26523be0$4001a8c0@gateway.2wire.net>
References: <CAEz6PPRNjcZZ+m9ZHX7zCyD7VqueftpZCW_UuyBdozfmzSik-g@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-clientproxiedby: LO2P265CA0047.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:61::35) To VI1PR07MB4480.eurprd07.prod.outlook.com (2603:10a6:803:75::12)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=ietfa@btconnect.com;
x-ms-exchange-messagesentrepresentingtype: 1
x-mailer: Microsoft Outlook Express 6.00.2800.1106
x-originating-ip: [86.139.215.234]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 9174ca76-82df-495e-ea23-08d6b1d2a4c6
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600127)(711020)(4605104)(2017052603328)(7193020); SRVR:VI1PR07MB4413;
x-ms-traffictypediagnostic: VI1PR07MB4413:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <VI1PR07MB441329E3C639E585883C85ACA25F0@VI1PR07MB4413.eurprd07.prod.outlook.com>
x-forefront-prvs: 09888BC01D
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(346002)(396003)(366004)(136003)(39860400002)(376002)(51444003)(199004)(189003)(13464003)(45074003)(6486002)(6506007)(386003)(44736005)(256004)(25786009)(68736007)(305945005)(14444005)(7736002)(99286004)(5660300002)(81686011)(6116002)(229853002)(52116002)(26005)(102836004)(81816011)(76176011)(4720700003)(61296003)(14496001)(6436002)(53936002)(486006)(81166006)(105586002)(6246003)(44716002)(2906002)(476003)(6512007)(6306002)(66066001)(9686003)(106356001)(446003)(15650500001)(316002)(3846002)(62236002)(53546011)(71190400001)(71200400001)(86362001)(1556002)(84392002)(110136005)(966005)(8676002)(50226002)(186003)(81156014)(478600001)(8936002)(86152003)(97736004)(14454004)(74416001)(7726001); DIR:OUT; SFP:1102; SCL:1; SRVR:VI1PR07MB4413; H:VI1PR07MB4480.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:0; MX:1;
received-spf: None (protection.outlook.com: btconnect.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: u4xaIJJy6URIqNAb6fhXyfbQq8uyaDxBSOqQhxRubasLQvJxgtw9SRdHRsIDJ2Hk7lwx+YiNHsK6AVKlPMB0S87pSpIFWw7MYMlhL8aLM0QruUv7d2n5ratF3DyFthn/FNMr0+px/44mmIwHfuFm4Y/ayEGZxMkSV0gTcKCogoN/JGvDALAiWm2T3oIxjYS2BvsY8DP6/qant/6Ur0odP+KAJy1EvzMeYUsj3QDeJihbHRa7lELASKU5NTdm9B3HZj+TNq2IqnYCh36/NZTwlqURTP9cXZLBsnOp4ED78sx56Vo44wPkv042VEFbHcJVNXbWSYjQGvP0/ETMVPZXAXCYpPICget9M85J4GCuBiyvJhxvkLAQ8niFs779a9lOPkIZLaKzw7k7cr9eCt/yynHc3cGGbgxkofF6uXTn6Fs=
Content-Type: text/plain; charset="utf-8"
Content-ID: <276920516801004595BC084D6AE20824@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 9174ca76-82df-495e-ea23-08d6b1d2a4c6
X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Mar 2019 10:05:58.8434 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB4413
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/kAbEHuEFtaauj0JEibIwyOZHRX4>
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: Tue, 26 Mar 2019 10:06:04 -0000

Xufeng

Some quirks.

Introduction/Abstract do not mention support or lack thereof  for NMDA
(which the IESG have been calling for).

Introduction does not have a reference for YANG leaving the question of
version number uncertain

Terminology fails to reference RFC8174

Expand on first use, perhaps in Terminology, is helpful - TOSCA, SF2LTP,
SF2SF, SF2TTP, CSO

yang-version 1 is rather limiting

YANG import statements lack references (which YANG 1.1 allows)

/       reference "TBD";/
       reference "RFC XXXX - SF Aware TE Topology YANG Model"; /

   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!

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)

RFC6020 is a better reference for the IANA Considerations

   [I-D.ietf-netmod-revised-datastores]
RFC8342

   [I-D.ietf-netmod-yang-tree-diagrams]
RFC8340

   [I-D.ietf-i2rs-yang-network-topo]
RFC8345

     import ietf-actn-vn {
does not appear in section 1.3

Tom Petch

----- Original Message -----
From: "Xufeng Liu" <xufeng.liu.ietf@gmail.com>
To: "TEAS WG" <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
> https://www.ietf.org/mailman/listinfo/teas
>