[bess] Questions about the EVPN YANG data model draft
Alexander Vainshtein <Alexander.Vainshtein@ecitele.com> Sun, 21 October 2018 11:00 UTC
Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4E3A130F17 for <bess@ietfa.amsl.com>; Sun, 21 Oct 2018 04:00:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.699
X-Spam-Level:
X-Spam-Status: No, score=-1.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, 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: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (body has been altered)" header.d=eci365.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 m-CW-rW5gxwo for <bess@ietfa.amsl.com>; Sun, 21 Oct 2018 04:00:34 -0700 (PDT)
Received: from mail1.bemta26.messagelabs.com (mail1.bemta26.messagelabs.com [85.158.142.1]) (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 EFDEC128A6E for <bess@ietf.org>; Sun, 21 Oct 2018 04:00:33 -0700 (PDT)
Received: from [85.158.142.103] (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256 bits)) by server-1.bemta.az-a.eu-central-1.aws.symcld.net id E4/06-11786-F4C5CCB5; Sun, 21 Oct 2018 11:00:31 +0000
X-Brightmail-Tracker: H4sIAAAAAAAAA1WTfUwTdxjH+d1deydy82fB8djpotVpFFopkFi 3mZgYtYlRRkxMBM084Gi7tEfXlgjbsqARK/gSTawiEoqjm6RotIYRxGGUzTeob52ESATF4nAi xrE3FKze9Yov/zz55vv5Pc/v+1x+x5CqGlrN8CUu3iFwVo0ynsqcvWyTNmtjMDfNV6cwNFw+T BpaA43IcLfeTxs6R4/Tht7Rl0qD78dWyjB4rYFYRhuv3YlQxgNjAYXR53tOGEOP2pXG68+8tL F7Wxdt7O0JEV/QOQqLkFdUsllhLu9Zbm/1oJLmwDhVhurcqBLFMxT+gQRv0wBZiSYxKuwhoO+ MTQIqHEYQGnqCJKDES+F0Y69SAknYS8DgSFm0g8Rz4FfvDVrSiXgxBKpPRP0k/DlUnKwVGxhR 6+D2H4skm8KfwH3PZSTZLOZge59dshH+EP7vOE7IE5OhZ8Ab1YAx+H65Qcp6GvwZjijk83lw7 +FRJPuzoaqvhpb1TAh5d0UXA3yBhsiLY5QMtPDM44kNWgMt4VFaygBi/KZHm+TzvyMY3nsqdn EquA/VK2Rth8jY05j/PdSHdsVmfgz+Pf2U3NxFwr9ngjEwA3zV0gYSqFTCnjv/EPLnzYcrNX/ HOvaRsPevfnIfSql+Z21ZC+DecQtJmsVT4erhAUr2U6Hu7IhS1inw09EhckIHz4eJd/06RPvR kjyHxWR22TiLVatPS9Pq9RlavVafnqHjvtFyOr5Ym88LLgcnUh23xalzltryrQU6gXedRuKLL PgafduC+t2mdjSdITTTWC6jM1f1QV5RQamZc5q/dBRbeWc7msEwGmAjOcFc1VQHb+JLCi1W8V lPYGASNEnsHAmzTjtnc1pMMupAKxh/1c4qknkQrU+jtTlYIdYdD7urSBUlFAm8Opk154rNWGo 2FwtvRk/8NCE0U53Iori4OFWCnXfYLK73+WOUzCBNIlsoTUmwCK43CR6L4QgxXPf8aDgX9xap y9DSBbXPDxyxppw7prr00cKC9N9ebUeZ8YG5uN09eS07q234xRh5zmu8u3r3g5bk8MHarwrbN LjJ0FXfPMX/s3L/4vRLkzeWX/x0UK0Rbq3MahsKrBo/WDE8njR9eeVnJ9cNjGQeymkIJ67YWT G+fmvj2vKb8/5LDWyIA3v2d6Wdpo752RrKaeb0C0mHk3sNI1EJ4C8EAAA=
X-Env-Sender: Alexander.Vainshtein@ecitele.com
X-Msg-Ref: server-30.tower-228.messagelabs.com!1540119627!653936!1
X-Originating-IP: [52.33.64.93]
X-SYMC-ESS-Client-Auth: mailfrom-relay-check=pass
X-StarScan-Received:
X-StarScan-Version: 9.14.24; banners=ecitele.com,-,-
X-VirusChecked: Checked
Received: (qmail 3394 invoked from network); 21 Oct 2018 11:00:30 -0000
Received: from us-west-2b.mta.dlp.protect.symantec.com (HELO EUR04-VI1-obe.outbound.protection.outlook.com) (52.33.64.93) by server-30.tower-228.messagelabs.com with AES256-SHA256 encrypted SMTP; 21 Oct 2018 11:00:30 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ECI365.onmicrosoft.com; s=selector1-ecitele-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=vL5erCA2uEVMsczz0eIWKKXamgnNf+Q7FANxh/ftPYc=; b=hX0k1ZOFw/0rWnKiekwL36B/nhUujdawiN/7qgvuo+pEIpy5WnYr9O+V2TJwgLBoqATuQfIIVX6AUhTgMGVwHsoNMrLT+3niP2X+i2Ndfh8d8HrhT98UCXXT3QyWLmgbbfH5llRA24tgxdpNKY/5XPT97fsshjxSQnQFh14oacE=
Received: from DB5PR0301MB1909.eurprd03.prod.outlook.com (10.167.226.155) by DB5PR0301MB1927.eurprd03.prod.outlook.com (10.167.227.11) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1250.30; Sun, 21 Oct 2018 11:00:26 +0000
Received: from DB5PR0301MB1909.eurprd03.prod.outlook.com ([fe80::d0bc:f20c:94cf:f479]) by DB5PR0301MB1909.eurprd03.prod.outlook.com ([fe80::d0bc:f20c:94cf:f479%2]) with mapi id 15.20.1250.028; Sun, 21 Oct 2018 11:00:25 +0000
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: "pbrisset@cisco.com" <pbrisset@cisco.com>, "hshah@ciena.com" <hshah@ciena.com>, "jorge.rabadan@nokia.com" <jorge.rabadan@nokia.com>, "Ing-Wher_Chen@jabil.com" <Ing-Wher_Chen@jabil.com>, "ihussain@infinera.com" <ihussain@infinera.com>, "kishoret@juniper.net" <kishoret@juniper.net>
CC: "bess@ietf.org" <bess@ietf.org>
Thread-Topic: Questions about the EVPN YANG data model draft
Thread-Index: AdRpKBIaA0WQYnKPTxyQ1QKEypCDww==
Date: Sun, 21 Oct 2018 11:00:25 +0000
Message-ID: <DB5PR0301MB19093856CE4495B879CAFD299DFB0@DB5PR0301MB1909.eurprd03.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [147.234.241.1]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DB5PR0301MB1927; 6:BU5OyBzaiaxRNJY1ilameJkFEGXe9LI5ddKQ/3gyUL0XyJhwXFQatYkl9nFkpThjz8GCiKDfQ6H8sPvADdfjdovwsNfle3rASEw1HJLX+xT1v8GOXKCtO9aI71Y+GWluDBGPor9RbAy99vh5sog4RNGtasdXbx4mCMZ302zwqd7MHQBeMrrss2tKksBjWJW4TQRlnf6q/bc/6mSaEydiVUJsUfaDLkzvXb6tmhMtM8LkgCOlzN7o6WVVNv4PHG9vbM+quqI3ssUTjg5WQ/U0DLMyN2EFNqzlVCWEeHkMpWlWKL7HtD3hEaUTIEqaRXZ7hF+iVCMcHdnoLf+EkKGSi4YLDf4BOiWwiRqJ5D9oOyERrpEksSbiGpyyaZ9aiC5x9/6Mk92GX7hJRoPhyClrr4j8Y+zFkf1/M0D/9Speywj7WXMV4ErTWWdq2DZUK8tqdlJFjHGmOTuQx77lVPa8qQ==; 5:d0kjuGxD7dSc9Rc+opX9TXchVyhDQWjPnr97mCbireKj/E+UMiyV0D+QcZi7i48XqMX8tmib7OoQok3RhmYry05HjZLGVTdLgk+4ESVr1nmvQuwTn1Zo1QnuXLpIqPVCK6fZTw0iK+f0JMofBToygQIN2FIC4WQrWzjfI7EyMMA=; 7:b62ua2pNZzBCPydObPGH3xkUWKfRcmMAplKrjzN/TgY+gCKWmevWL4LfBHgr0zA7hbNjsi7ZSE95SeJoHAvWr/p/ke9WnZ4wn2l60W67eFN46O0pJSfAemy8+3PnjZunvKWLUxwqFTf42bU15yld/xrImKvZ4zQ93Su60D2zDjGvc4V0xs8vnw/S+G61tLQyBDumE4lOQOWoYZnvj/tDydezbsTv2ShwBODdgVQAGzYeRAj8vjwqfV6pQlvhKHU7
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 007c46b1-0865-4124-1eb4-08d6374467ae
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989299)(5600074)(711020)(4618075)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7153060)(7193020); SRVR:DB5PR0301MB1927;
x-ms-traffictypediagnostic: DB5PR0301MB1927:
x-microsoft-antispam-prvs: <DB5PR0301MB192722C7C583B916065021689DFB0@DB5PR0301MB1927.eurprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(279101305709854)(21748063052155)(28532068793085)(190501279198761)(227612066756510);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(5005006)(8121501046)(93006095)(93001095)(10201501046)(3002001)(3231355)(944501410)(52105095)(6055026)(148016)(149066)(150057)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123558120)(20161123562045)(20161123564045)(20161123560045)(201708071742011)(7699051)(76991095); SRVR:DB5PR0301MB1927; BCL:0; PCL:0; RULEID:; SRVR:DB5PR0301MB1927;
x-forefront-prvs: 083289FD26
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(366004)(346002)(376002)(136003)(396003)(39850400004)(252514010)(199004)(189003)(51874003)(105586002)(110136005)(74316002)(2900100001)(606006)(790700001)(6116002)(3846002)(33656002)(186003)(217873002)(106356001)(25786009)(4326008)(99286004)(7696005)(14444005)(256004)(476003)(8936002)(5250100002)(2501003)(486006)(66066001)(72206003)(6506007)(68736007)(97736004)(54896002)(2201001)(316002)(478600001)(2906002)(6306002)(6436002)(9686003)(14454004)(71190400001)(81166006)(71200400001)(55016002)(53936002)(81156014)(236005)(102836004)(8676002)(1941001)(7736002)(26005)(5660300001)(86362001); DIR:OUT; SFP:1102; SCL:1; SRVR:DB5PR0301MB1927; H:DB5PR0301MB1909.eurprd03.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: ecitele.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: J+h/ttEE4mumVrhq/mvkBeGe8PmhoNsNepPn1rdhMz30cebTa18nK9Z5PTE2fML0EjLV/UNUp8+AqdKbv7f6oDsfGTt5FtpOnHiXb9suoOAHFB/axwb/BhliT1iv2SQ2BkSp2npMT+ZE9QlfPEg+7/Z8UylaqwIPOTVEJambf0310cNDghQ3UCBJ9NUG3xW7F2Cernpueks40+DI3HazFeZGUFAzMQti38+lYM2CCMQvfmVpm6aAnbepLRFpQyp2JxkU7+171dwiDpr6uvF8AYg8tNKW3VVmUbB+zGVws1KX+9SEH5H4LkDWZX2GhYGL06zM8Nr/Ke3jnUkC/G5gD/SS3GYIBqnnhOQk4+/MQv4=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_DB5PR0301MB19093856CE4495B879CAFD299DFB0DB5PR0301MB1909_"
MIME-Version: 1.0
X-OriginatorOrg: ecitele.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 007c46b1-0865-4124-1eb4-08d6374467ae
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Oct 2018 11:00:25.3339 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 2c514a61-08de-4519-b4c0-921fef62c42a
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB5PR0301MB1927
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/IFc6XGVsRCJNrRsluWO-AQLcuY0>
Subject: [bess] Questions about the EVPN YANG data model draft
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 21 Oct 2018 11:00:37 -0000
Dear Editors of the EVPN YANG data model draft<https://tools.ietf.org/html/draft-ietf-bess-evpn-yang-05>, I have several questions regarding the draft, and would highly appreciated your responses. 1. The -05 version of the draft has expired almost two months ago. Do you plan to refresh it any time soon? 2. The draft consistently uses type uint32 for the Ethernet segment identifier (ESI), while RFC 7432 explicitly defines it as a 10-octet integer. Is this just a typo, or did I miss something substantial here? 3. The draft states that it covers Integrated Routing and Bridging in EVPN, but I could not find any traces of such coverage. Did I miss something, or is just a forward declaration for the future version of the draft? 4. RFC 7432 states that "When a customer site is connected to one or more PEs via a set of Ethernet links, then this set of Ethernet links constitutes an Ethernet segment". The Virtual Ethernet Segment draft<https://tools.ietf.org/html/draft-ietf-bess-evpn-virtual-eth-segment-00> expands this definition and, so that virtual Ethernet Segments can be comprised of: * Ethernet Virtual Circuits aggregated on an ENNI physical ports * Ethernet PWs or even MPLS LSPs. Can you please clarify the following: a. How does the proposed YANG data model differentiate between physical and virtual Ethernet Segments? b. Does this data model cover the scenario where the virtual Ethernet segments are represented by EVCs? 5. RFC 7432 includes recommendations for usage (or non-usage) of the Control Word in the EVPN encapsulation, and RFC 8214 (which is claimed to be covered by this draft) provides a control plane mechanism for exchanging the CW usage information. Can you please clarify whether the draft cover usage of the CW in the EVPN encapsulations? Your feedback will be highly appreciated. Regards, and lots of thanks in advance, Sasha Office: +972-39266302 Cell: +972-549266302 Email: Alexander.Vainshtein@ecitele.com ___________________________________________________________________________ This e-mail message is intended for the recipient only and contains information which is CONFIDENTIAL and which may be proprietary to ECI Telecom. If you have received this transmission in error, please inform us by e-mail, phone or fax, and then delete the original and all copies thereof. ___________________________________________________________________________
- [bess] Questions about the EVPN YANG data model d… Alexander Vainshtein
- Re: [bess] Questions about the EVPN YANG data mod… Patrice Brissette (pbrisset)
- Re: [bess] Questions about the EVPN YANG data mod… Alexander Vainshtein