Re: [bess] A question regarding draft-wang-bess-evepn-control-word

Alexander Vainshtein <Alexander.Vainshtein@ecitele.com> Tue, 23 October 2018 10:09 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 DBBE4130DF9; Tue, 23 Oct 2018 03:09:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.689
X-Spam-Level:
X-Spam-Status: No, score=-1.689 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, T_FILL_THIS_FORM_SHORT=0.01, 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 n0RemqjeCmTs; Tue, 23 Oct 2018 03:09:01 -0700 (PDT)
Received: from mail1.bemta26.messagelabs.com (mail1.bemta26.messagelabs.com [85.158.142.115]) (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 CDFFC130E25; Tue, 23 Oct 2018 03:09:00 -0700 (PDT)
Received: from [85.158.142.193] (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256 bits)) by server-4.bemta.az-b.eu-central-1.aws.symcld.net id 0B/C4-08788-A33FECB5; Tue, 23 Oct 2018 10:08:58 +0000
X-Brightmail-Tracker: H4sIAAAAAAAAA1WTeUgUURzHfTOzu1M4Na2Zv8yuLemcxS2hTYg CCyoLjEAh6Zh1p92NdbTdkTYh2Si13C6zQkW01CQ7zMLADjsWOxQtso0l6dCyMtPQJCosaWfe dv3z+Lzf9/s73uM9mtT2qSNpwSUJDpG369SjqdhJ9S4ubuhhSszNNsJ45n4xaaytbaSMPZ0Py GXkyr1N/aqVVVXfiURig8ommtJdW1RW7/Xb6gz/Y+TqbM8l3ailCeWj0TTFVpDgHShRNlr2BA F3LhZSePMGwbXcaiIfjaLV7BK4fO6FWubx7CKoyy1QMkj2CILu3HxSFsLY5VA71KHBphVw5t5 hEnMcNLy/ohSi2Gio3+9T4gzLQ2HBxWC38wi8PbeQLIxik+Fqab3SDbET4GvLeSWZZCOgo7tc YWBZqLrxiMQcDh/ejKiw3wSv3p5COD4dil6WajBPhvZyjzI1sHc08L6/LWjiYOD48WChtXCgu zLQgA7wDKjv2Yj9TxDklJ5GOD4f6nbPwfYMyKktozBnQ2W7J8hT4OzBLgrnPiVhZOhjsFcUuB tOqLHwQA013n7iCOJK/jkcZhGGS5pRiXJL46C5uJvC8blQ5h4OeqbDMU+XBvMc8BV6gzwPqk9 9JE8izVm02OSwWaxSGm+zc4aYGM5gWMjFcobYBXo+izPphUwuVRAlBx9Q9fwOp965My3VbtaL gnQZBd6ZeTt1qAEN5lm8aCJN6MKZ59cfpmjHmNLNO62807rZkWkXnF4URdM6YKI+B7RxDsEiu Lba7IHH+lsGOlQ3nomXZcaZwac5bRYstaCl9OuifUUk/UlZO4vl1de6v4jUUmK6KERGMGPlNF ZOs2aKf4r+/gTtaHJkGINCQkK0oRmCI80m/a/3ogga6cKY1XKVUJso/endGxiLCIzln9UqjyX xf6VIN3LdIqBim6fAl6TN+9Rf3je/ms1i3I0pj/2V28ZeKljwYlrzGmndYM2zu8OLzcl31zdN O1poNOcPGGsuHPxJTe1Qff5Sd3VT/BZ/S8KjVV2tvuhsvyd+T9ymhLKRzcVSzM1dM7/l/Bi0Z P9Mevd99o/EfYdPZuVRqb2ttON+X3VjabSOclp5w1zS4eR/Aezx5tT/AwAA
X-Env-Sender: Alexander.Vainshtein@ecitele.com
X-Msg-Ref: server-3.tower-238.messagelabs.com!1540289334!619593!1
X-Originating-IP: [52.27.180.120]
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 3926 invoked from network); 23 Oct 2018 10:08:57 -0000
Received: from us-west-2c.mta.dlp.protect.symantec.com (HELO EUR03-DB5-obe.outbound.protection.outlook.com) (52.27.180.120) by server-3.tower-238.messagelabs.com with AES256-SHA256 encrypted SMTP; 23 Oct 2018 10:08:57 -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=UPgDUUW2mgvkpj5hJXw9UQ6mliP8ZbAAHbT01SqUdmM=; b=Qk+KNsvUQX0U/8+dEzZWwQ+ZhaI1/60mnxTUZmRH+XWYLFpilqVra/czwpS8/WfxCSx0kK2D/BheyZQwCZGvPEqs4vBe/9ZmYZgcrM1cuvbfr0s1ZpSc78VMW4BQ5gANB0sp8Wj9Sbe5BB5aL7x+QZS/iZ9NCIWeO3YevbXsd7g=
Received: from DB5PR0301MB1909.eurprd03.prod.outlook.com (10.167.226.155) by DB5PR0301MB2021.eurprd03.prod.outlook.com (10.167.227.139) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1250.30; Tue, 23 Oct 2018 10:08:52 +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.1273.014; Tue, 23 Oct 2018 10:08:52 +0000
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: "Wanghaibo (Rainsword)" <rainsword.wang@huawei.com>
CC: "bess@ietf.org" <bess@ietf.org>, "draft-wang-bess-evpn-control-word.authors@ietf.org" <draft-wang-bess-evpn-control-word.authors@ietf.org>
Thread-Topic: A question regarding draft-wang-bess-evepn-control-word
Thread-Index: AdRqrNk+JB1I7psBRa+73/QNemWcWQAALOQwAAKSsZA=
Date: Tue, 23 Oct 2018 10:08:52 +0000
Message-ID: <DB5PR0301MB190960ECA1045D82A0146F0A9DF50@DB5PR0301MB1909.eurprd03.prod.outlook.com>
References: <DB5PR0301MB19090FA060B80CCF658B8EC79DF50@DB5PR0301MB1909.eurprd03.prod.outlook.com> <1E61161D6E31D849BEA887261DB609348C770DEE@nkgeml514-mbx.china.huawei.com>
In-Reply-To: <1E61161D6E31D849BEA887261DB609348C770DEE@nkgeml514-mbx.china.huawei.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; DB5PR0301MB2021; 6:YrFUHtLhIf61tgiMGrhQp82AuxYnu17ftT/Fbdiot5uzHIXV3/1F48aTH0qnLOMkcuRDEwhobO4zlbHFpWHQZ+sQWh9XPETxyUOXXRUGaVCcpdjgHtuVMQidCRw5SkxqWOm8isMwkfHTP4cyFKqEzjXWyf+v5pPM5yxyRCN/mCDR7JgBnP9ZKm1jTw/OpXzpBhFbpZ9ULGOmwE+fMgskcOulB2K39T4KFpcKfSwjQlHICqJTrzVXMtEnINkwbXC7MEZfFI6REIprNC3omi2B3cGsjidnWN540EtpKyJziDqc1HjwnHi19oXleUdv7my0OkmVwRcGaf9CWwq6hz9i1VidPHsorTEXeSFjrngi5Aq26SaSNexOGyaj5Us3mWOPd6pMIfyc7Cw8pQREtmq/qoCLdC95Ct7Fab0xd7dEBWruSEY3KG04mxza4zITa4TSTOOXFfN3r6UPhzj45DIOEw==; 5:/8otIGPCTBo1rgdw5ix09HnDlDKrg7Cnq+kS7+RWUcjEdTnJjLCokK/ulYj9CBhm3lNatiIlLEX+1SFINs/b/fhzT8j/AqR+quXMf1WuMxGEJ9MmwCfiywWiBe27/FLCyE+vJlkdkNGIAuPcKz7KZjz/fNxAic+cRivaPnWbxxg=; 7:tR5RtCKfVbMFKC6mg/e9yeLmMRHgQN1y2EXoN7YVjW5GyDxumSIKjMfsvagjTzS7D53Nf/GWDxfbs7LdbrNdUgLlRpMcs3YAay/wQSM66ihBnnc7zqO7I/SNu9+neOmJiLYwXbTcpwmty/X3zgi2NGGEG62O3QOv6F8S3vRq++ybGffB7d2FexwdOfwWv9cnYJPxUj555MbrRx7UIqSLHWU0Zk8Y5UrZt9yYemCTqGfznUgOkI9l25Kp79MXLLLc
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: ca43818d-2eed-4b16-b36c-08d638cf8906
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600074)(711020)(4618075)(2017052603328)(7153060)(7193020); SRVR:DB5PR0301MB2021;
x-ms-traffictypediagnostic: DB5PR0301MB2021:
x-microsoft-antispam-prvs: <DB5PR0301MB2021AA669C0E9EA4591771799DF50@DB5PR0301MB2021.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)(10201501046)(93006095)(93001095)(3002001)(3231355)(944501410)(52105095)(6055026)(148016)(149066)(150057)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123558120)(20161123564045)(20161123560045)(20161123562045)(201708071742011)(7699051)(76991095); SRVR:DB5PR0301MB2021; BCL:0; PCL:0; RULEID:; SRVR:DB5PR0301MB2021;
x-forefront-prvs: 0834BAF534
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(366004)(136003)(376002)(346002)(39860400002)(252514010)(199004)(65514003)(189003)(51874003)(5250100002)(102836004)(81156014)(97736004)(14454004)(68736007)(2906002)(99286004)(71200400001)(71190400001)(81166006)(106356001)(11346002)(7696005)(53546011)(606006)(26005)(256004)(6916009)(476003)(486006)(6506007)(7736002)(229853002)(105586002)(76176011)(74316002)(186003)(5660300001)(8936002)(8676002)(14444005)(16234385003)(446003)(3846002)(6246003)(66066001)(25786009)(72206003)(413944005)(6116002)(54906003)(55016002)(236005)(790700001)(6306002)(4326008)(6436002)(53936002)(316002)(54896002)(33656002)(9686003)(2900100001)(478600001)(86362001); DIR:OUT; SFP:1102; SCL:1; SRVR:DB5PR0301MB2021; 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: smSfrCjciVunDv75FGLEkEm/1AmgbYcvnDp4N5M2WcFd0N3gkxpSEfC/XcgRW1/pYmWTEHPiLwZnZz7NGGNd2EJ9jPT7K2P0Gl3zSd0qji3Ds/oyaVCQoemeUkS54jfoKtPXjrFSiT8tpkXRjj1OjaZPvfdJQuOOOuArUrM0sHZyJ85ds83O+YFZIhJj456Wxt96wfplY/Jj27Z0c+8tMoxNBfip7/5BNr9r7FIo8U2lyxZ8YYKmdhTFzJgQ4XrLLuVQGweq4q2TL9zgyuZKnNz8jrWHSg/v0E0fAYScfrjfrE68nTQjSL4MKHUfxU3Q30lvU19YRjtVNCSv/PPsRecTiMmo1NvIoACIBdPtef8=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_DB5PR0301MB190960ECA1045D82A0146F0A9DF50DB5PR0301MB1909_"
MIME-Version: 1.0
X-OriginatorOrg: ecitele.com
X-MS-Exchange-CrossTenant-Network-Message-Id: ca43818d-2eed-4b16-b36c-08d638cf8906
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 Oct 2018 10:08:52.6596 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 2c514a61-08de-4519-b4c0-921fef62c42a
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB5PR0301MB2021
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/dfXLLDAGfMD-YXudaL1ZzY5L3-A>
Subject: Re: [bess] A question regarding draft-wang-bess-evepn-control-word
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: Tue, 23 Oct 2018 10:09:05 -0000

Dear Haibo,
Lots of thanks for an extra-prompt response to my question.

There may be some misunderstanding here.

The draft says (the important text is highlighted):

      There are two methods to specified the control word indicator label:

      The first method is to apply for a reserved label to indicate
      whether the packet contains a control word;

      The second method is to apply for a new label when the sending
      router advertises the control word capability, which is used to
      indicate whether the control word is included in the packet.

My question referred just to the 2nd method, while your response seems to deal with the 1st one.

Did I miss something?

Regards,
Sasha

Office: +972-39266302
Cell:      +972-549266302
Email:   Alexander.Vainshtein@ecitele.com

From: BESS [mailto:bess-bounces@ietf.org] On Behalf Of Wanghaibo (Rainsword)
Sent: Tuesday, October 23, 2018 12:03 PM
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>om>; draft-wang-bess-evpn-control-word.authors@ietf.org
Cc: bess@ietf.org
Subject: [bess] 答复: A question regarding draft-wang-bess-evepn-control-word

Hi Alexander,

The number of routes advertised by the Sender router in our solution will not change, but only carries a next hop capability attribute with control word capability
The Receiver router determines whether to carry the control word when forwarding packets according to its own capabilities.

The following figure is an example.:
PE1----------PE2
|-----------PE3
When PE1 advertises a route, it carries the next hop attribute of the control word capability. The routes received by PE2 and PE3 are the same.

If  PE2 do not support the control word, it will not carry the control word when forwarding packets to PE1.
PE1 cannot find the control word indication label when parsing the PE2 packet. PE1 will treat the packet as normal.

If  PE3 support the control word, it can add a control word when forwarding the packet to the PE1, and add the control word indication label specified by the PE1.
When the PE1 receives the packet and finds the control word indication label in the packet. PE1 will correctly process the control word.

Thanks
Haibo

发件人: Alexander Vainshtein [mailto:Alexander.Vainshtein@ecitele.com]
发送时间: 2018年10月23日 16:46
收件人: draft-wang-bess-evpn-control-word.authors@ietf.org<mailto:draft-wang-bess-evpn-control-word.authors@ietf.org>
抄送: bess@ietf.org<mailto:bess@ietf.org>
主题: A question regarding draft-wang-bess-evepn-control-word

Dear authors of draft-wang-bess-evpn-control-word<https://tools.ietf.org/html/draft-wang-bess-evpn-control-word-00>00>,
I have doubts regarding at least one of the approaches for negotiating the CW usage in the EVPN encapsulation between egress and ingress PE that is defined in the draft.

In the case when the egress PE can receive EVPN-encapsulated packets both with and without CW, the draft seems to propose (as one of the possibilities) advertisement of two EVPN routes for each ES or MAC/IP pair:

-          One of these routes would use the CW Capability to indicate that it refers to the EVPN encapsulation that uses the CW, and would carry the appropriate label in its NLRI

-          The other route would not use the CW Capability to indicate that it refers to the EVPN encapsulation that does not use the CW, and carry a different label in its NLRI

The ingress PE that accepts these routes would then use one of them based on its own ability to use the CW (or lack thereof), and use the corresponding label it its EVPN encapsulation, while  the DP in the egress PW would infer presence or absence of the CW from the received EVPN application label.

Unfortunately, I do not think that this can work because, as per RFC 7432<https://tools.ietf.org/html/rfc7432>32>, labels in the labeled NLRI of EVPN routes are not part of the route key for the purpose of the BGP route key processing, while the label is treated just as the BGP attribute. This means that, unless some form of BGP multi-path is enabled in the ingress PE (and in all RRs on the way between the egress PE and ingress PE) for the L2VPN/EVPN  AFI/SAFI, only one of these routes will be selected by the BGP selection process.

Did I miss something substantial here?

Regards, and lots of thanks in advance,
Sasha

Office: +972-39266302
Cell:      +972-549266302
Email:   Alexander.Vainshtein@ecitele.com<mailto: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.
___________________________________________________________________________

___________________________________________________________________________

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