Re: [Teas] FW: I-D Action: draft-ietf-teas-actn-vn-yang-05.txt

tom petch <ietfa@btconnect.com> Thu, 20 June 2019 16:24 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 8A46712011D for <teas@ietfa.amsl.com>; Thu, 20 Jun 2019 09:24:51 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RATWARE_MS_HASH=2.148, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 ruMJAiOvcIeq for <teas@ietfa.amsl.com>; Thu, 20 Jun 2019 09:24:49 -0700 (PDT)
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-eopbgr150097.outbound.protection.outlook.com [40.107.15.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E99A120019 for <teas@ietf.org>; Thu, 20 Jun 2019 09:24:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector1-btconnect-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=IGOWRmJ0+HMviAJLdDot/S6iBZEfjpmGOESkilU3d7A=; b=B68m5iFp4gdMF4m+zh9PyrbF0t48ZY9LCORNEvO0AnsSkNTCWLOdBIZA3UyczxDxwFdt1PUR1MG8rX/V8w4PeVAgUh0KuTJb+KEehzVXalZT+fcECJOAL02oj1UEoPdsWNpfr5cTzIZ8XmOIPWa1iIREfPKurRz7FMvNBYeg4W8=
Received: from VI1PR07MB5646.eurprd07.prod.outlook.com (20.178.81.26) by VI1PR07MB4784.eurprd07.prod.outlook.com (20.177.57.159) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2008.5; Thu, 20 Jun 2019 16:24:46 +0000
Received: from VI1PR07MB5646.eurprd07.prod.outlook.com ([fe80::ed4f:a89a:d1e:4aef]) by VI1PR07MB5646.eurprd07.prod.outlook.com ([fe80::ed4f:a89a:d1e:4aef%6]) with mapi id 15.20.2008.007; Thu, 20 Jun 2019 16:24:46 +0000
From: tom petch <ietfa@btconnect.com>
To: Young Lee <leeyoung@futurewei.com>, "teas@ietf.org" <teas@ietf.org>
Thread-Topic: [Teas] FW: I-D Action: draft-ietf-teas-actn-vn-yang-05.txt
Thread-Index: AQHVJ4SsXRtvkfDwGUSTOsTxhShohQ==
Date: Thu, 20 Jun 2019 16:24:46 +0000
Message-ID: <013901d52784$b2e64760$4001a8c0@gateway.2wire.net>
References: <156053688596.31607.5836614263862645600@ietfa.amsl.com> <CH2PR13MB3383C817E18092E6BA92A2A6CDEE0@CH2PR13MB3383.namprd13.prod.outlook.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-clientproxiedby: LO2P265CA0324.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:a4::24) To VI1PR07MB5646.eurprd07.prod.outlook.com (2603:10a6:803:c4::26)
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: 1da75dcf-b0c3-4766-1b6f-08d6f59bcf0a
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:VI1PR07MB4784;
x-ms-traffictypediagnostic: VI1PR07MB4784:
x-microsoft-antispam-prvs: <VI1PR07MB478418CE805C9B142D830A98A2E40@VI1PR07MB4784.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0074BBE012
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(39850400004)(136003)(376002)(346002)(366004)(199004)(189003)(13464003)(6506007)(446003)(81816011)(476003)(62236002)(44716002)(53936002)(6486002)(66066001)(6246003)(1556002)(66946007)(25786009)(6116002)(3846002)(6512007)(2906002)(9686003)(229853002)(14454004)(5660300002)(71200400001)(71190400001)(66574012)(6436002)(4720700003)(66476007)(66446008)(73956011)(64756008)(66556008)(14496001)(478600001)(486006)(110136005)(2501003)(316002)(84392002)(256004)(68736007)(81686011)(52116002)(81156014)(81166006)(8936002)(26005)(50226002)(186003)(102836004)(386003)(305945005)(86362001)(8676002)(61296003)(53546011)(44736005)(99286004)(76176011)(7736002)(74416001)(7726001); DIR:OUT; SFP:1102; SCL:1; SRVR:VI1PR07MB4784; H:VI1PR07MB5646.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: anuCnfNxjDmNT9q16xUzze6D//8j7x3aMeJ3LvkhiJuLfdhbd0on2fdqUxWIDiHasIzZ1GizbuK00W5PgDOfqdg85W0UzfKz7Sp1RKNqRvy0CrZAEplm9fSRN6gN+3zJrXtcuaVi+qnISqRhiwiq0b6Dt4JqZn6YpPx80uAbwsVswmjH1GoQGQU/5rcj9x7MUd8Nv6wN+gJsVmzIAUWVsGalytfhJ3JGFyHRrGvUAfNCXnzfPkAGiYu7fH6AKy1lY7y7AtVflEqQBQskua2vBF4iS+yJ/ZuVdezRudGpQ1yqrPV/29/ese3rYhOj+fSmOK8t3TbHbkEBbyY6EYTOrBjWPxmTgetLEhUGY1IMsXZepJ8fwPizxQJflsBj9AisTJUb8KkuteZbqgrCzB8racpWkTEvsdeYeBjrfp4OzKk=
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <D3272D98FDB0504482B038B24426BD57@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 1da75dcf-b0c3-4766-1b6f-08d6f59bcf0a
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Jun 2019 16:24:46.4664 (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-CrossTenant-userprincipalname: ietfa@btconnect.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB4784
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/N9yfs1M2NlObCwhGzka6ixQUYP0>
Subject: Re: [Teas] FW: I-D Action: draft-ietf-teas-actn-vn-yang-05.txt
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: Thu, 20 Jun 2019 16:24:52 -0000

----- Original Message -----
From: "Young Lee" <leeyoung@futurewei.com>
To: <teas@ietf.org>
Sent: Friday, June 14, 2019 7:44 PM

> Hi WG,
>
> The changes for this revision are as follows:
>
> - Added in Introduction Section on how the VN model can support 5G
transport context.
> - in Section 3.2: case 2 --- clarified how VN model is used along with
TE-topo Connectivity matrices construct and added a paragraph to
introduce the JSON example of the models (in Section 7)
> - For YANG model: converted "ltp" from configurable parameter to
leafref type; added references for imported modules.
> - Editorial: affiliation changes for a co-author; Compliant with five
front page authors' list.

As I said of -03, rather short on references and some that are seem
wrong.
Look, for example, at
draft-ietf-pim-igmp-mld-yang-15.
to see the sort of level of reference that a YANG module benefits from.

Several of the existing references should be Normative, according to
YANG Guidelines.

You have
       import ietf-te-types { prefix "te-types";
           reference"I-D.ietf-teas-yang-te-types: Traffic Engineering

but in the list of prefixes, always a good thing to have, is
      | te-types| ietf-te-types  | [TE-Tunnel]     |

while the I-D References has
   [TE-tunnel] T. Saad, et al., "A YANG Data Model for Traffic
             Engineering Tunnels and Interfaces", work in progress:
             draft-ietf-teas-yang-te.
which looks like a mismatch.

VN is expanded in the text but I think needs expanding in the Title of
the I-D and in the YANG module; others need expanding on first use;
L3SM,  L2SM  and L1CSM

And I think you should provide a reference for VN up front, something
along the lines of
"For more information on Virtual Networks, see [RFC8453]"
in the Introduction, first paragraph. (I don't think that RFC8453 is a
brilliant reference for VN but I cannot find a better one).

Tom Petch

> Thanks.
> Young & Dhruv
>
> -----Original Message-----
> From: Teas [mailto:teas-bounces@ietf.org] On Behalf Of
internet-drafts@ietf.org
> Sent: Friday, June 14, 2019 1:28 PM
> To: i-d-announce@ietf.org
> Cc: teas@ietf.org
> Subject: [Teas] I-D Action: draft-ietf-teas-actn-vn-yang-05.txt
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts
directories.
> This draft is a work item of the Traffic Engineering Architecture and
Signaling WG of the IETF.
>
>         Title           : A Yang Data Model for VN Operation
>         Authors         : Young Lee
>                           Dhruv Dhody
>                           Daniele Ceccarelli
>                           Igor Bryskin
>                           Bin Yeong Yoon
> Filename        : draft-ietf-teas-actn-vn-yang-05.txt
> Pages           : 56
> Date            : 2019-06-14
>
> Abstract:
>    This document provides a YANG data model generally applicable to
any
>    mode of Virtual Network (VN) operation.
>