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

Young Lee <> Tue, 02 July 2019 14:49 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 9B77D1200EB for <>; Tue, 2 Jul 2019 07:49:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -0.999
X-Spam-Status: No, score=-0.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=0.999, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id yQlwwJFwR0fF for <>; Tue, 2 Jul 2019 07:49:38 -0700 (PDT)
Received: from ( [IPv6:2a01:111:f400:fe50::724]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id ECD121200F3 for <>; Tue, 2 Jul 2019 07:49:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=iWCTGCIB0u8xRjv5VugktSlDKQen4BF7szOVYFJS3nQ=; b=QJiIM0eZCf7kZ65HEbzutdIKEEGVrjDHRVMvk94lEUZ9nQWVNV968AMIer0DtBC/Wm+V0BXNGakviQVWSxzFKvvaKvDKUgBlQWRrufAOUxLaJaFypdwmAFiVzMloE9w/CO/0bPDa79QCsbtNEfQy96K9bH5SLo319eSMxubbbk8=
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2052.13; Tue, 2 Jul 2019 14:49:35 +0000
Received: from ([fe80::3c9c:d019:cde:aae]) by ([fe80::3c9c:d019:cde:aae%6]) with mapi id 15.20.2052.010; Tue, 2 Jul 2019 14:49:35 +0000
From: Young Lee <>
To: tom petch <>, "" <>
Thread-Topic: [Teas] FW: I-D Action: draft-ietf-teas-actn-vn-yang-05.txt
Thread-Index: AQHVJ4SvAJoSRFV6A0msGR0cG2e0HKa3eX2g
Date: Tue, 2 Jul 2019 14:49:35 +0000
Message-ID: <>
References: <> <> <013901d52784$b2e64760$>
In-Reply-To: <013901d52784$b2e64760$>
Accept-Language: en-US
Content-Language: en-US
authentication-results: spf=none (sender IP is );
x-originating-ip: []
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 0a3b4e97-c1f5-481f-e8c0-08d6fefc8042
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:CH2PR13MB3352;
x-ms-traffictypediagnostic: CH2PR13MB3352:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 008663486A
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(396003)(136003)(346002)(376002)(366004)(39850400004)(13464003)(199004)(189003)(2501003)(6306002)(74316002)(6246003)(54896002)(66476007)(81166006)(476003)(55016002)(256004)(9686003)(229853002)(6436002)(71190400001)(66066001)(7736002)(296002)(486006)(316002)(68736007)(110136005)(3846002)(53546011)(2906002)(6506007)(8676002)(73956011)(5660300002)(71200400001)(53936002)(76116006)(25786009)(790700001)(6116002)(7696005)(102836004)(66446008)(26005)(9326002)(52536014)(76176011)(99286004)(66946007)(8936002)(86362001)(478600001)(11346002)(64756008)(446003)(81156014)(66574012)(33656002)(66556008)(14454004)(186003); DIR:OUT; SFP:1102; SCL:1; SRVR:CH2PR13MB3352;; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None ( does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: 8/otsChR0ZzPwFT4xWMf5IEFoErR6AF4KWVVWu87w5/QuTUU2bcBQVDi5wCXalAdsCkk78Zot5gF7Pvpn6RUeEGYL6vVrVsvQkmedVdQ3vNmnq9OkzSHhGfFyglHsN7zNoEEdMCMiaC/mEfgfKJVQQGP9tfzHupse98mwTWHyw1LnM7Uxwofq90AJY35+HzScBRetAaziJM65mB0I6Scc5RL7uTrRYZTR/IAiBtkYP0IMnN77NFd2vtmeG5RgyJG6VxVM0TA33S06h2Z5RbrClnA5qEXkiZODOMKzdl2NUIU0dFmr5tWiuK+DbLhdK7kmdkT/iqe0H5knhTul5ZfnLq9BY+5lWPkg12spNql49nJW0IFsg2l9Bd4IDShkXt5fHkmBcWv3gElGjftFGMAG5gTXBf/iysQbSQHbY2JMsU=
Content-Type: multipart/alternative; boundary="_000_CH2PR13MB3383CD21D23221A6518804EBCDF80CH2PR13MB3383namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 0a3b4e97-c1f5-481f-e8c0-08d6fefc8042
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Jul 2019 14:49:35.5226 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 0fee8ff2-a3b2-4018-9c75-3a1d5591fedc
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CH2PR13MB3352
Archived-At: <>
Subject: Re: [Teas] FW: I-D Action: draft-ietf-teas-actn-vn-yang-05.txt
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 02 Jul 2019 14:49:41 -0000

Hi Tom,

Thanks for your comments. My apology for a delayed response. Please see inline for my comment.



-----Original Message-----

From: tom petch []

Sent: Thursday, June 20, 2019 11:25 AM

To: Young Lee <>om>;

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

----- Original Message -----

From: "Young Lee" <>

To: <>

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


to see the sort of level of reference that a YANG module benefits from.

YL>> It will be good to be specific on which references are wrong and what needs to be added.

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

YL>> Again, can you point which ones you think Normative?

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:


which looks like a mismatch.

YL>> Yes, you're right. The reference should be TE-type as TE-type was separated out from TE-tunnel model. Will correct this in the revision.

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

YL>> OK. Agreed.

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).

YL>> Agree. Will add the VN reference up front.

Tom Petch

> Thanks.

> Young & Dhruv


> -----Original Message-----

> From: Teas [] On Behalf Of

> Sent: Friday, June 14, 2019 1:28 PM

> To:

> Cc:

> 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


> 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


>    mode of Virtual Network (VN) operation.