Re: [Teas] Status update on draft-ietf-teas-yang-l3-te-topo

tom petch <ietfa@btconnect.com> Wed, 25 November 2020 12:37 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 5A0973A113A for <teas@ietfa.amsl.com>; Wed, 25 Nov 2020 04:37:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 cXye_G7nhFKx for <teas@ietfa.amsl.com>; Wed, 25 Nov 2020 04:37:50 -0800 (PST)
Received: from EUR05-VI1-obe.outbound.protection.outlook.com (mail-vi1eur05on2096.outbound.protection.outlook.com [40.107.21.96]) (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 B9FB93A1139 for <teas@ietf.org>; Wed, 25 Nov 2020 04:37:49 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=DsEKL9hTAm306UKwr8sBzEhmYIi5VNlupgRwKWG7i9vPGXl6evXldY/Avl1g2r9KPsOoD1sW2xx5y6HXh4apNupzVEUcI0phrsOmzFBLrrWQyqFUjTlBe7vmssf8vMUsFXG6A4hV5nN0azNkPJR9KkqAscTQyuGuvJ/7q/e8Ew/Ae4xt/I5nTjXyyVbpMRbrvCZ7rb7eQSMCzwaMS0xqmmpYTe86SR94AAVyZNkZ1t6Q5b++wHozhG+LQ4Osp4u25UuU6AgayDQEclsOIGyDqR8xMsjYjk/aBZmeD/hUh3kfdiX8wbz/xZDWHtdIoorTngZFJDNdoJaztonHGUsDtA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=LbKEfAiY70sfz6zyK3SbYusFk9jez/CT8VkY2m5DBdU=; b=WYYt9b+80PUdx9LSVXmsXFYWxWsg8jpFHU01o8cR0Bk6D2+5McPeI81HsrdZro8OGgr1OkyjeWQ1jIPv9pCR/1kBG0QCKETzvHolRw0Pkz/KpsVRg4a2jlB1XEe1dZiLYVFw+uPdwW1Sturx2Mmg8Sv6GIa0RLEa0o6kQrI84xOWKxpNRQaLaWRpTeXrn2S469boao0IYRyluGArfQzKjxqRXuaiYmyse6KZ8V5ZCFVYQl8pBr1sc7NmmsNBqjyF2PBi1yLBL2Cp5DtDh5XgNNl9cMYMIVhKkFJ+CbSX5eps0sMElSswiXkNfR9Yv0CvoJ4m26RFVp6sP/MpohWkVg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=btconnect.com; dmarc=pass action=none header.from=btconnect.com; dkim=pass header.d=btconnect.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector2-btconnect-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=LbKEfAiY70sfz6zyK3SbYusFk9jez/CT8VkY2m5DBdU=; b=nDv/Qd/ySgE0zuzHdIFnrYFmkWerAJW2QKMyXdHQrLJomIMS1NUZtERS7vF63F5kEKD2bWUgUZC8ErW9YAi8Bkef5qCorzzzMgH5CjZtV3utrdKB2hT8ldn65zMaRmsMXFzaXVan1E4vRJnC0mrd8YZRzeDpAK4EY/Cs5UosZC0=
Received: from AM6PR07MB5784.eurprd07.prod.outlook.com (2603:10a6:20b:95::29) by AM5PR0701MB2788.eurprd07.prod.outlook.com (2603:10a6:203:77::10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3632.6; Wed, 25 Nov 2020 12:37:47 +0000
Received: from AM6PR07MB5784.eurprd07.prod.outlook.com ([fe80::15d0:d260:35ea:7c9b]) by AM6PR07MB5784.eurprd07.prod.outlook.com ([fe80::15d0:d260:35ea:7c9b%6]) with mapi id 15.20.3611.021; Wed, 25 Nov 2020 12:37:47 +0000
From: tom petch <ietfa@btconnect.com>
To: Xufeng Liu <xufeng.liu.ietf@gmail.com>
CC: TEAS WG <teas@ietf.org>
Thread-Topic: [Teas] Status update on draft-ietf-teas-yang-l3-te-topo
Thread-Index: AQHWGBjZqBIQHbOU4kWdbmKNe1eMVKiTGetTgAiwUYCAAkI8PYBoB1qAgAFg5L+Ay32UgIAHKRA+
Date: Wed, 25 Nov 2020 12:37:46 +0000
Message-ID: <AM6PR07MB57845C2B8B47030CFA3AC6FCA2FA0@AM6PR07MB5784.eurprd07.prod.outlook.com>
References: <CAEz6PPQC8NUnTimMVXBXzbd9+FxdeTDV8NXPuLDASBF=1YUR_A@mail.gmail.com> <DB7PR07MB53406ABD74B3CEE15B5952BDA2AB0@DB7PR07MB5340.eurprd07.prod.outlook.com> <CAEz6PPS-ZWSb7cubv2jB05ZCb9kyyGXDPd5KpAQ05iHmtpMpCw@mail.gmail.com> <DB7PR07MB5340DFF664791762E1F082F6A2A20@DB7PR07MB5340.eurprd07.prod.outlook.com> <CAEz6PPT6N0a3FNtseRFzuXEAJoBvnBRBtwzg4vi+ZDLHxUZCrQ@mail.gmail.com> <DB7PR07MB534098BD42E7C079288A20B5A2610@DB7PR07MB5340.eurprd07.prod.outlook.com>, <CAEz6PPRByqJ46E4aCv-v=mtX9BoLZPCgo4tx-2zaHjOxELMgqQ@mail.gmail.com>
In-Reply-To: <CAEz6PPRByqJ46E4aCv-v=mtX9BoLZPCgo4tx-2zaHjOxELMgqQ@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=btconnect.com;
x-originating-ip: [86.146.121.140]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: c8b3689c-2feb-412e-7e71-08d8913ee9da
x-ms-traffictypediagnostic: AM5PR0701MB2788:
x-microsoft-antispam-prvs: <AM5PR0701MB278826F158AE85F1E24EDDEEA2FA0@AM5PR0701MB2788.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:6790;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: Lzsxsc2+Q2lJAQOqlN9eOvyn1IAjJQ6ikF3lYpsgR2XnuUkHU85yEt2MKBTh06mOTtGcROtlItgmT2ydC1ldeNvyNU6vkgZSeMzD5Z/NacHgif9PlsKzXG6jHi1L5+++18Q+5dyARoiw+Uhuw+zhssxe6/fI50AS8HGt6CdWRq98R552mIm/ePKmexdyGM2Dv0xW/4Mzp3Cdu0y9mhPc5zIsMRH4edPmOr5y90pwxj0opjttji8zdlTrN0k8HJmkuEwkgWItjDtkuft8Vq1vkSykGHw+X4ks949WbPQF3VLHd0d4qjLaWuXGyGFndSjTuNw5LvNE023Kwi9xZ1X7DCCcY/WwmY19bUZl1/lv/s6NOlMy4rkzV/zkHksMyOQAJKiKZYz7GVLA0i6MiUuTLQ==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:AM6PR07MB5784.eurprd07.prod.outlook.com; PTR:; CAT:NONE; SFS:(39860400002)(376002)(396003)(366004)(136003)(346002)(186003)(316002)(7696005)(26005)(2906002)(66946007)(91956017)(83380400001)(8936002)(76116006)(4326008)(966005)(478600001)(86362001)(6506007)(71200400001)(53546011)(15650500001)(5660300002)(55016002)(8676002)(66446008)(64756008)(66476007)(52536014)(9686003)(66556008)(33656002)(6916009); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata: =?Windows-1252?Q?dGIo3GIB+mE1JePKFkBrMoT6JmgixNcVQsoBUy21Gpx8tQY4ikKVtE8H?= =?Windows-1252?Q?dBx0qv9d+x20gh6W0JY4nlfeGfaojnE4xN6PVddBWzXmfsZAdKmD8z7X?= =?Windows-1252?Q?EXbB7k6CprxNEy5EJKUW2aDNvZRikEhatU6brSzFzOBggg329To2OZ3i?= =?Windows-1252?Q?k0s9L/9raIwXclm/qdrH0EkhLmfm9ZIDo0P4KKsOSNCNfnuFTv9t9v35?= =?Windows-1252?Q?rMe0/5BjuIbCrQ0BxkDNxNPIOqEhRx+MFYvH0VkobOwBXIsyFQRmSNbn?= =?Windows-1252?Q?mtIulP2yFwjvS+eKFOu7KWeB7zrpoMbI+zSfDz8XWweMTJzSjBS7+72C?= =?Windows-1252?Q?HmTtPlIbocVdr7+MqLdsNHN6txERcvSsqOTgVcdutSj7upmSbr0zNKpU?= =?Windows-1252?Q?LXA+6SXQ4ohtWJiOBAVbwFU9Lau6CcTnbxYnySaORTRkPTKmZcAajWLi?= =?Windows-1252?Q?HBm7QeyXZ2UE6taPSnPe6hz2lv2g+rGUz30rPHEcfd1YmNyaqwfTuiOc?= =?Windows-1252?Q?/za+9K2+oo3RGkrDeZCV/En6MZNTcxQ0GSFynBBT1TWDpohykE6bBhJu?= =?Windows-1252?Q?BD+yXdzcxToyBCuh6s+crnU/WM6PAytq5ZToQXymWwd4OeBmukp3EbZa?= =?Windows-1252?Q?ADR550MeiVVeblQwVtCeDCAYQCq5vhgRsuYxDFjl5dAtuO94MfkYJIhB?= =?Windows-1252?Q?FYhlx+Xfnxhd3HadXXpjkGLQPXg9GWPWlDpA1TpxZHmpRn12PXGy1B7R?= =?Windows-1252?Q?Gcdv41UL9ULNA93BTrm3jq6cllyU2UP1ClePcaXLeEf/de1HmKpWlctD?= =?Windows-1252?Q?L4pTL3/KG1QBVsYIkvH0bkm3wacZuxYWhpuke4Mdx+PyyUiP47+LO4FY?= =?Windows-1252?Q?h6Po+yfJQl7tvdGrthPztag+43heAqIoqUsDgMTLLVmGA8rTipr2Nqj4?= =?Windows-1252?Q?TX3E5HCM9ICwr23C+A+Wr7W8zn/7gkDvuwhN1CbykmlogyfP0+Q08548?= =?Windows-1252?Q?GcblF1pzMIV3HKHPk71Y9J5aEWOkWNbAz7KdNOdlEyIKRjI8+TY=3D?=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: AM6PR07MB5784.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: c8b3689c-2feb-412e-7e71-08d8913ee9da
X-MS-Exchange-CrossTenant-originalarrivaltime: 25 Nov 2020 12:37:46.9636 (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: YPBEp3iDvJ3ev8LR9Tdnf32E4iKZOLFVMopf9Q3GscTZ2FCSRe5YGTa0ibWFaTsh2PV+ODQhe/kyWg87FZzgnQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM5PR0701MB2788
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/ycTd9NxgtTlOcAZ4qXby8CnbttU>
Subject: Re: [Teas] Status update on draft-ietf-teas-yang-l3-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, 25 Nov 2020 12:37:52 -0000

From: Xufeng Liu <xufeng.liu.ietf@gmail.com>
Sent: 20 November 2020 23:02

Hi Tom,
Thank you much for your further comments. We have posted https://datatracker.ietf.org/doc/html/draft-ietf-teas-yang-l3-te-topo-09, hoping to address some of your comments below.

<tp>
I have had a second go at -09 and have some more thoughts.

Figure 3 I like, especially as you have achieved it in ASCII.

s.2.2.3
Can a termination point be reference with tp-id or do you have to use node+link as here?

s.2 talks of two YANG modules when there are four; ok two are PSC but I think that that might be spelt out here in this section.

congruent is 'with' something not 'to' something, I believe

between the one modeling element in the layer 3 unicast topology /to/and/

This YANG data model /allows/supports/ both cases.

associated /to/with/ the objects in one /corresponding/corresponding
[corresponding is what adulterers do!]

Tom Petch







Thanks,
- Xufeng

On Tue, Jul 14, 2020 at 7:34 AM tom petch <ietfa@btconnect.com<mailto:ietfa@btconnect.com>> wrote:
From: Xufeng Liu <xufeng.liu.ietf@gmail.com<mailto:xufeng.liu.ietf@gmail.com>>
Sent: 13 July 2020 15:29

Hi Tom,

Thanks for further reviewing. We have posted an updated version https://datatracker.ietf.org/doc/html/draft-ietf-teas-yang-l3-te-topo-08. Some rewording has been made, with the hope of making the document more comprehensible. Please let us know for anything that is still confusing (for such an unconventional modeling approach).

<tp>
I still find some of the terminology in this a challenge.

2.1   o  The multiplicity of such an association is: 0..1 to 0..1.
the following sentence suggests it is '1 to 0..1'

[Xufeng]: The next sentence describes the relation on an object, but such a description is relevant only if such an object exists. When such an object has not been created in the ietf-l3-te-topology, the corresponding layer 3 TE topology may already contain an object that can be potentially associated with the to-be-created object. In this case, 0 in ietf-l3-te-topology, and 1 in ietf-te-topology. Therefore, I’d say that multiplicity is still 0..1 to 0..1.



'associated to the objects in a coresponding TE topology'
'a' suggests there can be more than one which the YANG does not seem to
and 2.2.1 has 'the' not 'a'

[Xufeng]: Changed ‘a’ to ‘one’, hoping that “associated to the objects in one corresponding TE topology" would avoid the possibility of “more than one”.

in passing 'associated with' and 'corresponding'

'   Since ietf-te-topology augments ietf-network-topology defined in
[RFC8345] [I-D.ietf-teas-yang-te-topo], the referenced leaf
   /nw:networks/network/network-id identifies an instance of TE topology
   by inheritance. '
No and no!  ietf-network-topology is in one document so there should be
only one reference or else the module name is wrong or ....
And the referenced leaf does not identify an instance of TE Topology -
it identifies a network of any type.  As the next sentence makes clear,
this module has to ensure it is of the correct type and does so.

[Xufeng]: Reworded the section, trying to clarify the leafref relationship. Please let us know if it is better.

'   If the TE topology is congruent to the layer 3 unicast topology, the
   above reference can still be used to specified TE parameters defined
   in the TE topology model.
I do not understand.  What parameters? I do not see any and if they were
to be defined in TE Topology then they should not be specified here or
anywhere else.

[Xufeng]: One example of the TE parameters is te-delay-metric. Such parameters are defined in the TE Topology model. They are not specified in l3-te-topology, but they can be configured in the corresponding te-topology instance.


s.2.2.2
'a node in the layer 3 TE topology may have a reference to the
corresponding TE node.'
perhaps clearer as
'a node in the layer  3 TE topology may have a reference to the
corresponding node in the TE Topology.'

[Xufeng]: Yes. Reworded as suggested.

s.2.2.3 s.2.2.4 ditto mutatis mutandi

[Xufeng]: Fixed too.

More technically this I-D seems confused about prefix and inconsistent
elsewhere
.
module
     namespace "urn:ietf:params:xml:ns:yang:ietf-l3-te-topology";
     prefix "l3tet";
IANA
   name:         ietf-l3-te-topology
   namespace:    urn:ietf:params:xml:ns:yang:ietf-l3-te-topology
   prefix:       l3te

[Xufeng]: Fixed the IANA section.

YANG
       container l3-te {
         presence "Indicates L3 TE Topology";

   augment /nw:networks/nw:network/nw:network-types
             /l3t:l3-unicast-topology:
     +--rw l3-te!

[Xufeng]: Is there anything wrong here? l3-te is the name of a container and is not the prefix.

In passing, 'congruent with' in many places (at least in English
English)

[Xufeng]: Is it not correct? Or “congruent to” is preferred? Did a brief search, it seems that “congruent with” is more popular.



s.3
The YANG data  model defined in this document ...
This document specifies two YANG modules ..
actually three!

[Xufeng]: Is the above paragraph in Sec 2: “Modeling Considerations for L3 TE Topologies”? If so, the the description is intended to be scoped to Sec 2. We have two modules for L3 TE Topologies, and the other two modules are for Packet Switching Technology Extensions.



Tom Petch


Best regards,
- Xufeng

On Fri, May 8, 2020 at 6:06 AM tom petch <ietfa@btconnect.com<mailto:ietfa@btconnect.com><mailto:ietfa@btconnect.com<mailto:ietfa@btconnect.com>>> wrote:
From: Xufeng Liu <xufeng.liu.ietf@gmail.com<mailto:xufeng.liu.ietf@gmail.com><mailto:xufeng.liu.ietf@gmail.com<mailto:xufeng.liu.ietf@gmail.com>>>
Sent: 07 May 2020 00:22

Hi Tom,

Thanks for reviewing and sorry about the errors. We have posted an updated version https://tools.ietf.org/html/draft-ietf-teas-yang-l3-te-topo-07, to fix the errors about the augmentation description and to rephrase a couple of sections to explain the relations between the related models and their objects. Please let us know for anything that is not clear enough.

<tp>
Thanks for the update.  I now find s.2 s.2.1 clear but still struggle thereafter.  When you use layer 3 topology I find it ambiguous.  Is it layer 3 unicast topology or layer 3 te topology?  Thus in s.2.2.1
"When TE is enabled on a layer 3 topology .. " implies unicast
"congruent to the layer 3 topology .."
implies unicast
" the layer 3 topology will have a reference.."
 ah, no, must be layer 3 te topology
and this is the case throughout the rest of s.2.  I would like to see those references to layer 3 topology clarified, unicast or te.  You may want to say that layer 3 topology means ... while layer 3 ... topology will be spelt out in full or some such, I am easy, but do think that you need to use two distinct terms.
[Xufeng]: Reworded. Please let us know if anything is confusing.

As you may infer, I like to work top down, start with Abstract, then Introduction, then s.2 s.3 making sense of them before seeing if the module does what these sections say, so when I get stuck in s.2, I do not make it to details of the YANG module.
[Xufeng]: Thank you much for looking at it. We are striving to get your review unstuck.

Tom Petch

Thanks,
- Xufeng

On Fri, May 1, 2020 at 6:56 AM tom petch <ietfa@btconnect.com<mailto:ietfa@btconnect.com><mailto:ietfa@btconnect.com<mailto:ietfa@btconnect.com>><mailto:ietfa@btconnect.com<mailto:ietfa@btconnect.com><mailto:ietfa@btconnect.com<mailto:ietfa@btconnect.com>>>> wrote:
From: Teas <teas-bounces@ietf.org<mailto:teas-bounces@ietf.org><mailto:teas-bounces@ietf.org<mailto:teas-bounces@ietf.org>><mailto:teas-bounces@ietf.org<mailto:teas-bounces@ietf.org><mailto: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><mailto:xufeng.liu.ietf@gmail.com<mailto:xufeng.liu.ietf@gmail.com>><mailto:xufeng.liu.ietf@gmail.com<mailto:xufeng.liu.ietf@gmail.com><mailto:xufeng.liu.ietf@gmail.com<mailto:xufeng.liu.ietf@gmail.com>>>>
Sent: 21 April 2020 21:09


Status update on draft-ietf-teas-yang-l3-te-topo

Current Status:

  *  The updated revision -06 was posted on March 8, 2020:
     - Editorial changes.
  *  Corordinated with ietf-eth-te-topology and ietf-te-mpls-tp-topo
     for the augmentation of ietf-te-topology
     - ietf-te-topology does not need to be changed.
  *  Answered YANG doctor's review comments.

Open Issues:

  *   None.

<tp>

I started  to review this and have given up,  I cannot make sense of section 2, which I see as fundamental to understanding the I-D.
 Thus
The YANG modulues  ietf-l3-te-topology ...
These two modules augment ietf-l3-te topology
No they don't!  This augments
ietf-l3-unicast-topology
which is quite different and I find this confusion elsewhere in section two. Thus
Relationship  between Layer 3 Topology and TE Topology
Is that Layer 3 TE Topology or ietf-network-topology?  I think that many if not most  references to TE Topology are ambiguous and need clarifying - is the reference to Layer 3 TE Topology to  ietf-network-topology?

Some of the words are quirky and this website is determined not to let me put them into an e-mail but here goes.

modulues
topoology
moducment
Local ink

Tom Petch
Next Steps:


  *  Update the model to sync with the referenced models like draft-ietf-teas-yang-te-types if there are any changes.
  *  Welcome further reviews and suggestions.
  *  Working Group Last Call after completing the above.

Thanks,
- Xufeng