Return-Path: X-Original-To: i2rs@ietfa.amsl.com Delivered-To: i2rs@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6EA73A07D7; Thu, 9 Jul 2020 00:05:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no 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 CZNB_kB8NccP; Thu, 9 Jul 2020 00:05:02 -0700 (PDT) Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 A265D3A07C2; Thu, 9 Jul 2020 00:05:02 -0700 (PDT) Received: from lhreml705-chm.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 97F95A538BB3BA22B4E1; Thu, 9 Jul 2020 08:05:00 +0100 (IST) Received: from lhreml705-chm.china.huawei.com (10.201.108.54) by lhreml705-chm.china.huawei.com (10.201.108.54) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1913.5; Thu, 9 Jul 2020 08:05:00 +0100 Received: from DGGEML404-HUB.china.huawei.com (10.3.17.39) by lhreml705-chm.china.huawei.com (10.201.108.54) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.1913.5 via Frontend Transport; Thu, 9 Jul 2020 08:04:59 +0100 Received: from DGGEML531-MBS.china.huawei.com ([169.254.5.228]) by DGGEML404-HUB.china.huawei.com ([fe80::b177:a243:7a69:5ab8%31]) with mapi id 14.03.0487.000; Thu, 9 Jul 2020 15:04:50 +0800 From: Qin Wu To: Stephen Cheng , "i2rs@ietf.org" , "draft-ietf-i2rs-yang-l2-network-topology@ietf.org" CC: "Dongjie (Jimmy)" Thread-Topic: Mail regarding draft-ietf-i2rs-yang-l2-network-topology Thread-Index: AdZVvRh/ZO+M1pP2SJ2dSF/cQTqkUg== Date: Thu, 9 Jul 2020 07:04:49 +0000 Message-ID: Accept-Language: zh-CN, en-US Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.164.123.162] Content-Type: multipart/alternative; boundary="_000_B8F9A780D330094D99AF023C5877DABAAD8192E3dggeml531mbschi_" MIME-Version: 1.0 X-CFilter-Loop: Reflected Archived-At: Subject: Re: [i2rs] Mail regarding draft-ietf-i2rs-yang-l2-network-topology X-BeenThere: i2rs@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Interface to The Internet Routing System \(IRS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jul 2020 07:05:05 -0000 --_000_B8F9A780D330094D99AF023C5877DABAAD8192E3dggeml531mbschi_ Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 SGkgU3RlcGhlbjoNCg0Kt6K8/sjLOiBTdGVwaGVuIENoZW5nIFttYWlsdG86U3RlcGhlbi5DaGVu Z0BBdmlhdG5ldC5jb21dDQq3osvNyrG85DogMjAyMMTqN9TCOcjVIDEyOjUzDQrK1bz+yMs6IGky cnNAaWV0Zi5vcmc7IGRyYWZ0LWlldGYtaTJycy15YW5nLWwyLW5ldHdvcmstdG9wb2xvZ3lAaWV0 Zi5vcmcNCtb3zOI6IE1haWwgcmVnYXJkaW5nIGRyYWZ0LWlldGYtaTJycy15YW5nLWwyLW5ldHdv cmstdG9wb2xvZ3kNCg0KRGVhciBhdXRob3JzLA0KDQpJIGhhdmUgYSBudW1iZXIgb2YgcXVlc3Rp b25zIHJlZ2FyZGluZyB0aGlzIEwyIHRvcG9sb2d5IFlBTkcuDQoNCg0KICAxLiAgRG9lcyBkcmFm dC1pZXRmLWkycnMteWFuZy1sMi1uZXR3b3JrLXRvcG9sb2d5IHN1cHBvcnQgdGhlIG1vZGVsbGlu ZyBvZiBhIHRlcm1pbmF0aW9uIHBvaW50IHRoYXQgbWFwcyB0byBhIFZMQU4gc3ViLWludGVyZmFj ZT8NClRoaXMgY2FwYWJpbGl0eSB3b3VsZCBmYWNpbGl0YXRlIHRoZSBjcmVhdGlvbiBvZiBhIHRv cG9sb2d5IHN0YWNrIGZvciB0aGUgZm9sbG93aW5nIHVzZSBjYXNlczoNCg0KICAgICAqICAgTWFw cGluZyBhIGlldGYtbDMtdG9wb2xvZ3kgVFAgb3ZlciBhIHZsYW4gc3ViLWludGVyZmFjZQ0KSW4g dGhpcyBjYXNlIGEgVFAgaW4gaWV0Zi1sMy10b3BvbG9neSBpbnN0YW5jZSB3b3VsZCBiZSBzdXBw b3J0ZWQgYnkgYSBWTEFOIHN1Yi1pbnRlcmZhY2UgVFAgaW4gdGhlIGwyLXRvcG9sb2d5DQogICAg ICogICBNYXBwaW5nIGRpZmZlcmVudCBWTEFOIElEcyBpbiBhIEwyIHBvcnRzIHRvIGRpZmZlcmVu dCBzZXJ2aWNlcw0KDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICBpLiAgICAgIEZvciBleGFtcGxlLCBvbiBhIHBhcnRpY3VsYXIg TDIgcG9ydCwgVkxBTiAyMyBtaWdodCBiZSBhbiBhdHRhY2htZW50IGNpcmN1aXQgZm9yIFZQTFMg Izc4LCB3aGVyZSBhcyBWTEFOIDk5IG1pZ2h0IGJlIGFuIGF0dGFjaG1lbnQgY2lyY3VpdCBmb3Ig TDNWUE4gIzk5OQ0KDQpJZiBkcmFmdC1pZXRmLWkycnMteWFuZy1sMi1uZXR3b3JrLXRvcG9sb2d5 IGRvZXMgbm90IGhhdmUgdGhlIGNhcGFiaWxpdHkgdG8gbW9kZWwgVkxBTiBzdWItaW50ZXJmYWNl IGFzIGEgVFAsIGlzIHRoZXJlIGEgZGlmZmVyZW50IHdheSBmb3IgZHJhZnQtaWV0Zi1pMnJzLXlh bmctbDItbmV0d29yay10b3BvbG9neSB0byBzdXBwb3J0IHRoZSBhYm92ZSB1c2UgY2FzZXM/DQoN CltRaW5dOiBHb29kIHF1ZXN0aW9uLCB0aGlzIGNvdWxkIGJlIGRvY3VtZW50ZWQgaW4gYW5vdGhl ciBuZXcgZHJhZnQuICBBbHNvIHNlZSA0LjQuMiAoVW5kZXJsYXkgSGllcmFyY2hpZXMgYW5kIE1h cHBpbmdzKSBvZiBSRkM4MzQ1IGZvciBndWlkZWxpbmUuDQoNCiAgMS4gIFRoZSBWTEFOIHN1Yi1p bnRlcmZhY2UgWUFORyAoaHR0cHM6Ly90b29scy5pZXRmLm9yZy9wZGYvZHJhZnQtaWV0Zi1uZXRt b2Qtc3ViLWludGYtdmxhbi1tb2RlbC0wNi5wZGYpIGJlaW5nIGRldmVsb3BlZCBoYXMgc29tZSBv dmVybGFwIHdpdGggZHJhZnQtaWV0Zi1pMnJzLXlhbmctbDItbmV0d29yay10b3BvbG9neS4gSXQg d291bGQgYmUgZ29vZCBpZiB0aGVyZSB3b3VsZCBiZSBiZXR0ZXIgYWxpZ25tZW50IGJldHdlZW4g dGhlIHR3bzoNCiAgICAgKiAgIFVzZSBzaW1pbGFyIGRlZmluaXRpb24vZmllbGRzIHdoZXJlIHBv c3NpYmxlOyBldmVuIGJldHRlciB1c2Ugc2hhcmVkIGdyb3VwaW5nIGRlZmluaXRpb24NCg0KICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgaS4gICAgICBGb3IgZXhhbXBsZSBvdXRlci10YWcgYW5kIGlubmVyLXRhZw0KDQogICAgICog ICBWTEFOIHN1Yi1pbnRlcmZhY2UgWUFORyAoaHR0cHM6Ly90b29scy5pZXRmLm9yZy9wZGYvZHJh ZnQtaWV0Zi1uZXRtb2Qtc3ViLWludGYtdmxhbi1tb2RlbC0wNi5wZGYpIGZsZXhpYmxlIGVuY2Fw c3VsYXRpb24gc3VwcG9ydHMgc3ltbWV0cmljIGFuZCBhc3ltbWV0cmljIHJld3JpdGVzLCB3aGlj aCBkb2VzIG5vdCBhcHBlYXIgdG8gYmUgc3VwcG9ydGVkIGJ5IGRyYWZ0LWlldGYtaTJycy15YW5n LWwyLW5ldHdvcmstdG9wb2xvZ3kuDQogICAgICAgICAgICBbUWluXTogQm90aCBkcmFmdHMgaW1w b3J0IGllZWU4MDItZG90MXEtdHlwZXMsIHRoaXMgaXMgaG93IHdlIGFsaWduIHdpdGggZWFjaCBv dGhlci4gVGhlIGJpZyBkaWZmZXJlbmNlIGJldHdlZW4gdGhlIG1vZGVsIHByb3Bvc2VkIGJ5IGJv dGggZHJhZnRzIGlzIG9uZSBpcyBkZXZpY2UgbW9kZWwsIHRoZSBvdGhlciBpcyBuZXR3b3JrIG1v ZGVsLg0KDQogIDEuICBDb25zaWRlciB0aGUgc2NlbmFyaW8gd2hlcmUgYSBkb21haW4gY29udHJv bGxlciBpbXBsZW1lbnRpbmcgZHJhZnQtaWV0Zi1pMnJzLXlhbmctbDItbmV0d29yay10b3BvbG9n eSBpcyBhbHNvIGltcGxlbWVudGluZyBzY2hlbWEgbW91bnRlZCBpZXRmLWludGVyZmFjZSB0byBt b2RlbCB0aGUgaW50ZXJmYWNlIHN0YWNrcyBvZiB0aGUgbWFuYWdlZCBkZXZpY2VzOg0KLSAgICAg ICAgICBJcyB0aGVyZSBhIG1lY2hhbmlzbSBpbiBkcmFmdC1pZXRmLWkycnMteWFuZy1sMi1uZXR3 b3JrLXRvcG9sb2d5IHRvIGFzc29jaWF0ZSBhIEwyIFRQIHdpdGggdGhlIGNvcnJlc3BvbmRpbmcg aW50ZXJmYWNlIGVudHJ5IGluIHRoZSBzY2hlbWEgbW91bnRlZCBpZXRmLWludGVyZmFjZT8NCiAg ICAgICAgICBbUWluXTogVGhpcyBpcyB0aGUgYmFzZSBtb2RlbCwgaWYgeW91IHdhbnQgdG8gc3Vw cG9ydCB0aGlzIGNvbXBsaWNhdGUgY2FzZSwgSSB0aGluayBiYXNlIG1vZGVsIGV4dGVuc2lvbiBp cyBuZWVkZWQuDQoNCiAgMS4gIEZvciBhIExBRyBsaW5rLCB3b3VsZCB0aGUgTEFHIFRQIGJlIGV4 cGVjdGVkIHRvIGJlIGFsc28gcmVwcmVzZW50ZWQgYnkgL253Om5ldHdvcmtzL253Om5ldHdvcmsv bnc6bm9kZTp0ZXJtaW5hdGlvbi1wb2ludC90cC1pZC9zdXBwb3J0aW5nLXRlcm1pbmF0aW9uLXBv aW50IHRvIGl0cyBtZW1iZXJzaGlwIFRQcz8NCkl0IHdvdWxkIGJlIHVzZWZ1bCB0byBjbGFyaWZ5 IGZvciB1bmlmb3JtIGltcGxlbWVudGF0aW9uIGFjcm9zcyBkaWZmZXJlbnQgdmVuZG9ycy4NCiAg ICAgICAgICAgW1Fpbl0gTGFnIGFuZCBtZW1iZXItbGluay10cCB1bmRlciBsMi10ZXJtaW5hdGlv bi1wb2ludC10eXBlIGNob2ljZSBjYW4gYmUgdXNlZCB0byBzdXBwb3J0IHRoZSBjYXNlIHlvdSBt ZW50aW9uZWQgYmVsb3cuIFNlZSB0aGUgZGVmaW5pdGlvbiBvZiBMYWcgYW5kIG1lbWJlci1saW5r IGZvciBtb3JlIGRldGFpbHMuDQpBc2xvIFNlZSBzZWN0aW9uIDQuNC42IE11bHRpaG9taW5nIGFu ZCBsaW5rIGFnZ3JlZ2F0aW9uIG9mIFJGQzgzNDUgZm9yIGd1aWRlbGluZS4NClRoYW5rIHlvdS4N Cg0KV2FybSByZWdhcmRzLA0KU3RlcGhlbiBDaGVuZw0KQXZpYXQgTmV0d29ya3MNCg== --_000_B8F9A780D330094D99AF023C5877DABAAD8192E3dggeml531mbschi_ Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: quoted-printable

Hi Stephen:

 

=B7=A2=BC=FE=C8=CB:= Stephen Cheng [mailto:Stephen.Cheng@Aviatnet.c= om]
=B7=A2=CB=CD=CA=B1=BC=E4:= 2020=C4=EA7=D4=C29=C8=D5 12:53
=CA=D5=BC=FE=C8=CB: i2rs@ietf.org; draft-ietf-i2rs-yang-l2-network-topology@ietf.org =D6=F7=CC=E2: Mail regarding draft-ietf-i2rs-yang-l2-network-topology=

 

Dear authors,=

 

I have a number of questions re= garding this L2 topology YANG.

 

  1. Does draft-ietf-i2rs-yang-l2-network-topology support the modelling of = a termination point that maps to a VLAN sub-interface?

Th= is capability would facilitate the creation of a topology stack for the fol= lowing use cases:

    1. Mapping a ietf-l3-topology TP over a vlan sub-interface
      In this case a TP in ietf-l3-topology instance would be supported by a VLAN= sub-interface TP in the l2-topology
    2. Mapping diff= erent VLAN IDs in a L2 ports to different services

    <= span style=3D"font:7.0pt "Times New Roman"">   &nb= sp;            =             &nb= sp;            =             &nb= sp;         i.  = ;    For= example, on a particular L2 port, VLAN 23 might be an attachment circuit f= or VPLS #78, where as VLAN 99 might be an attachment circuit for L3VPN #999

    If draft-ietf-i2rs-yang-= l2-network-topology does not have the capability to model VLAN sub-interfac= e as a TP, is there a different way for draft-ietf-i2rs-yang-l2-network-top= ology to support the above use cases?

    = [Qin]: Good question, this could be documented in another new draft.  = Also see 4.4.2 (Underlay Hierarchies and Mappings) of RFC8345 for guideline= .

    1. The VLAN sub-interface YANG (https://tools.ietf.org/pdf/draft-= ietf-netmod-sub-intf-vlan-model-06.pdf) being developed has some overlap with draft-ietf-i2rs-yang-l2-network-topo= logy. It would be good if there would be better alignment between the two:<= o:p>
      1. Use similar definition/fields where possible; even better use shared gr= ouping definition

    <= span style=3D"font:7.0pt "Times New Roman"">   &nb= sp;            =             &nb= sp;            =             &nb= sp;         i.  = ;    For= example outer-tag and inner-tag

      1. VLAN sub-interface YANG (https://tools.ietf.org/pdf/draft-ietf= -netmod-sub-intf-vlan-model-06.pdf) flexible encapsulation supports symmetric and asymmetric rewrites, which d= oes not appear to be supported by draft-ietf-i2rs-yang-l2-network-topology.

     &= nbsp;          [Qin]: Bot= h drafts import ieee802-dot1q-types, this is how we align with each other. = The big difference between the model proposed by both drafts is one is devi= ce model, the other is network model.

    1. Consider the scenario where a domain controller implementing draft-ietf= -i2rs-yang-l2-network-topology is also implementing schema mounted ietf-int= erface to model the interface stacks of the managed devices:

    -=    &n= bsp;      Is there a mechanism in= draft-ietf-i2rs-yang-l2-network-topology to associate a L2 TP with the cor= responding interface entry in the schema mounted ietf-interface?=

     &= nbsp;        [Qin]: This is the bas= e model, if you want to support this complicate case, I think base model ex= tension is needed.

    1. For a LAG link, would the LAG TP be expected to be also represented by = /nw:networks/nw:network/nw:node:termination-point/tp-id/supporting-terminat= ion-point to its membership TPs?

    It= would be useful to clarify for uniform implementation across different ven= dors.

     &= nbsp;         [Qin] Lag and me= mber-link-tp under l2-termination-point-type choice can be used to support = the case you mentioned below. See the definition of Lag and member-link for= more details.

    Aslo See section 4.4.6 Multihoming and link aggregati= on of RFC8345 for guideline.<= /p>

    Thank you.

     

    Warm regards,=

    Stephen Cheng=

    Aviat Networks

--_000_B8F9A780D330094D99AF023C5877DABAAD8192E3dggeml531mbschi_--