Re: [bess] SHL label

Alexander Vainshtein <Alexander.Vainshtein@ecitele.com> Tue, 04 June 2019 15:03 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 D138A120073 for <bess@ietfa.amsl.com>; Tue, 4 Jun 2019 08:03:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.115
X-Spam-Level:
X-Spam-Status: No, score=-2.115 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, RCVD_IN_MSPIKE_H2=-0.415, SPF_PASS=-0.001] autolearn=ham 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 3OkMr-4E6gdm for <bess@ietfa.amsl.com>; Tue, 4 Jun 2019 08:02:58 -0700 (PDT)
Received: from mail1.bemta25.messagelabs.com (mail1.bemta25.messagelabs.com [195.245.230.67]) (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 26918120090 for <bess@ietf.org>; Tue, 4 Jun 2019 08:02:57 -0700 (PDT)
Received: from [46.226.52.199] (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256 bits)) by server-3.bemta.az-b.eu-west-1.aws.symcld.net id 53/33-21465-02886FC5; Tue, 04 Jun 2019 15:02:56 +0000
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrBJsWRWlGSWpSXmKPExsViougQqyvX8S3 G4GqrksWK4zOZLe7++Mtm8WzBY0YHZo+ds+6yeyxZ8pPJ4+6tS0wBzFGsmXlJ+RUJrBnXtp5k K2gJqthx8y9bA+NMty5GLg4WgbXMEm9XTGQGcYQEJjBJnF5yixXCucco0TxhD1CGk4NNwFZi0 +q7bCAJEYEFjBKnjs0BquLgEBYQk9g9pbyLkR0oLi5xPQ2kWkTASOLvhkUsIDaLgIpEc88cJh CbVyBW4mdfHxPE+CZGiWcz7rKCJDiBxu/5MJcNxGYEmvj91BqwBmagkbeezAezJQQEJJbsOc8 MYYtKvHz8jxWiPkni/tOFjBBxRYmra35D1ctKXJrfDRX3ldhxawYLyMUSAsoSW17EgtwgIfCY UWL1hS6oGi2JXTv+sEHYORKzjv9kh7DVJN4vu8AE0Ssj8fByEkR4DZvExOnmILaQQLLEiTmfW SDichKreh+yQMy/wCzRv+gKI0gvs0CexI0DqpBwEJQ4OfMJywRGzVlIvpyFUDULSRVEiYHE+3 PzmSFsbYllC19D2foSG7+cZUQWX8DIvorRIqkoMz2jJDcxM0fX0MBA19DQSNfQ0kLX0MhCL7F KN0kvtVS3PLW4RNdQL7G8WK+4Mjc5J0UvL7VkEyMwiaUUHGvYwdh54LXeIUZJDiYlUV7Xpm8x QnxJ+SmVGYnFGfFFpTmpxYcYZTg4lCR4E9qBcoJFqempFWmZOcCECpOW4OBREuH1aQNK8xYXJ OYWZ6ZDpE4x2nMcWPRwLjPHlvvPgOQuMDlz5vO5zEIsefl5qVLivI0gbQIgbRmleXBDYRngEq OslDAvIwMDgxBPQWpRbmYJqvwrRnEORiVhXkeQ23gy80rgdr8COosJ6Cz/259AzipJREhJNTD NW2I1x/f0uQmn1q48Wia61+eYzup+NflpXA4f7b6FzlpqWlot9nOPlPeJXY1JGZW87EHGbWnN IuFaXwJlVhZe+JPQE/nviHZ03JqXVUpMb56dSflcFiC5Ue9PhUjJtOup09dsev9An//wDyG90 D/TtofULHt577XMb4OvMTc0I++asjfkz7sw3YD34MekPQ9s/x+5lD3fOP6Y8rfUX8VZ/q02sv oiYhu1HTqE16W8cDtdoemaz8Zbr90sqt5vLf3zO9e0VsZrbjINzUtfNDBHtBvtTrt+stdvvUT 8OpmnXazyrRre4RU5T/9fuDivcZPw9t8nFhSfjDkzoWbF9CjvT2pfLsTsY1+orJKgw6DEUpyR aKjFXFScCAAX9NdkewQAAA==
X-Env-Sender: Alexander.Vainshtein@ecitele.com
X-Msg-Ref: server-13.tower-287.messagelabs.com!1559660571!10095676!1
X-Originating-IP: [52.33.64.93]
X-SYMC-ESS-Client-Auth: mailfrom-relay-check=pass
X-StarScan-Received:
X-StarScan-Version: 9.31.5; banners=ecitele.com,-,-
X-VirusChecked: Checked
Received: (qmail 32178 invoked from network); 4 Jun 2019 15:02:53 -0000
Received: from us-west-2b.mta.dlp.protect.symantec.com (HELO EUR01-DB5-obe.outbound.protection.outlook.com) (52.33.64.93) by server-13.tower-287.messagelabs.com with AES256-SHA256 encrypted SMTP; 4 Jun 2019 15:02:53 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ECI365.onmicrosoft.com; s=selector1-ECI365-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=tn27qvlMaUYuOPWJEzZiZJWmOW3aomIpxrkSXsAVtxM=; b=byiBSQkgX/FWREIx4he2OS6rP4ygELFdJ3RhIrb3INkwJ2jISQ2xoZ+I5nROF3cuPd9XHR5mmfT1QqYkb69g7wDkV9SqyRsxp8P5U26Mkp2W18IFeotF/EXFETWFYtQLf/qa6KjWXqunLKCHV2wkxcAqyWV/Z5uBHMnw4VW5ZF4=
Received: from AM0PR03MB3828.eurprd03.prod.outlook.com (52.135.146.159) by AM0PR03MB5075.eurprd03.prod.outlook.com (20.178.21.209) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1943.21; Tue, 4 Jun 2019 15:02:49 +0000
Received: from AM0PR03MB3828.eurprd03.prod.outlook.com ([fe80::91f3:6bd1:1631:9b4a]) by AM0PR03MB3828.eurprd03.prod.outlook.com ([fe80::91f3:6bd1:1631:9b4a%6]) with mapi id 15.20.1943.018; Tue, 4 Jun 2019 15:02:49 +0000
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: gangadhara reddy chavva <meetgangadhara@gmail.com>, "bess@ietf.org" <bess@ietf.org>, "Rabadan, Jorge (Nokia - US/Mountain View)" <jorge.rabadan@nokia.com>
Thread-Topic: SHL label
Thread-Index: AQHVGtJ3oNv6u48nfEiZCciS3bCI8KaLl4CR
Date: Tue, 04 Jun 2019 15:02:48 +0000
Message-ID: <AM0PR03MB38286DCF7007B81EC60D3F539D150@AM0PR03MB3828.eurprd03.prod.outlook.com>
References: <CAAG_SC-_P53HzYYPBTwag2bN6WOk+xbOM88E6A1Zfg73Aa_Apw@mail.gmail.com>, <0307BA53-B141-4D65-9BD8-0BC0D63BBD4D@nokia.com>
In-Reply-To: <0307BA53-B141-4D65-9BD8-0BC0D63BBD4D@nokia.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [40.67.249.252]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: f4f9a6d1-11f6-474e-cfa8-08d6e8fdb596
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(4618075)(2017052603328)(7193020); SRVR:AM0PR03MB5075;
x-ms-traffictypediagnostic: AM0PR03MB5075:
x-microsoft-antispam-prvs: <AM0PR03MB5075FB88F310D457BA7B508A9D150@AM0PR03MB5075.eurprd03.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:5797;
x-forefront-prvs: 0058ABBBC7
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(376002)(396003)(136003)(346002)(366004)(39860400002)(53754006)(189003)(199004)(221733001)(54896002)(66066001)(14454004)(229853002)(52536014)(446003)(68736007)(72206003)(508600001)(6436002)(71200400001)(9686003)(5024004)(256004)(2501003)(71190400001)(6246003)(33656002)(55016002)(66556008)(76116006)(5660300002)(316002)(486006)(6506007)(76176011)(7696005)(86362001)(6116002)(25786009)(53936002)(11346002)(53546011)(476003)(102836004)(8676002)(110136005)(74316002)(7736002)(7116003)(186003)(64756008)(2906002)(99286004)(3480700005)(66946007)(73956011)(91956017)(81166006)(3846002)(66446008)(26005)(8936002)(66476007)(81156014); DIR:OUT; SFP:1102; SCL:1; SRVR:AM0PR03MB5075; H:AM0PR03MB3828.eurprd03.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: ecitele.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: ouXDH1EqpnUDKogJHstBGPWQdmhMHU+XR6sVB5N7QeugaBEFCMDAnC1tZEgtICWElKhkAho3xv9rmRmV908T8mWAMi/sKtt1SR/cWGVOF6xbiAODva30AVCTyNXhgfhVHRaClkkv04NO+K7xXqG3zgRpq3FhamZ6lQrMzyi3w7lGSLfJ86YqzSzZLYSKWl9lIqmCv79ikM/kK4OL1aTfntxJeX23530v1txq/G72IA3unoERUdfghgZ++NoshquFR+hwNR9J4NPaXrRe1HjCuA9Z7dZFPm9NN6uGkCSZhBiw72FQLXJop7jflwIa/dyik2hldwiG/uRlAbRyAS3UNjn9MICzC32YkaI/Vi36Y/6l6f5ulmBlL1TmacUHPmsiOPZgFJMdvGsu2YnIlMmVbGar1VmSk1upx1CLp3qP7K4=
Content-Type: multipart/alternative; boundary="_000_AM0PR03MB38286DCF7007B81EC60D3F539D150AM0PR03MB3828eurp_"
MIME-Version: 1.0
X-OriginatorOrg: ecitele.com
X-MS-Exchange-CrossTenant-Network-Message-Id: f4f9a6d1-11f6-474e-cfa8-08d6e8fdb596
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Jun 2019 15:02:48.9204 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 2c514a61-08de-4519-b4c0-921fef62c42a
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: alexvain@ecitele.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM0PR03MB5075
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/mDaeuJ46igdToEu9xZw8oNz-_S0>
Subject: Re: [bess] SHL label
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, 04 Jun 2019 15:03:01 -0000

Hi all,
I concur with Jorge.

The ESI label is allocated per MH ES and does not depend on the service or on the method by which BUM frames are deliverd. This method only affects the way in which it is used:
- in the case of ingress replication a copy that is sent to the specific LE attached to a given MH ES uses the label this PE has advertised for this ES. I.e. it is used as downstream-allocated
- In the case of P2MP LSPs (where all PEs receive the same copy) the transmitter uses the ESI label it has allocated for the ES (it is upstream-allocated), and each receiver uses the label(s) that identify the transmitter PE  as the context labels for its correct processing.

RFC 7474 is quite clear in this regard from my POV.


Thumb typed by Sasha Vainshtein



From: Rabadan, Jorge (Nokia - US/Mountain View)
Sent: Tuesday, June 4, 15:38
Subject: Re: [bess] SHL label
To: gangadhara reddy chavva, bess@ietf.org


Hi,

The ESI label is signaled in the A-D per ES route(s), and those routes are (should be) service agnostic.
Also as you can see in RFC7432, the ESI label is downstream allocated for ingress replication but upstream allocated for p2mp - So it’s not that you allocate different ESI label per service, but the label that you use has different owner.

I think RFC7432 is pretty clear about this. Not sure where the confusion is.

Thanks.
Jorge

From: gangadhara reddy chavva <meetgangadhara@gmail.com>
Date: Monday, June 3, 2019 at 2:05 PM
To: "bess@ietf.org" <bess@ietf.org>, "Rabadan, Jorge (Nokia - US/Mountain View)" <jorge.rabadan@nokia.com>
Subject: SHL label

Hi Jorge,

I have a Question on EVPN MH SHL(split horizon label).

Can ESI share the different SHL label for the same ESI?

case 1: in the same ESI one customer EVPN VPN can have ingress replication for the BUM traffic and second EVPN VPN ine the same ESI can do P2MP? in this case SHL label should be different.

case 2: can VPLS allocate one SHL and VPWS can allocate diffrent SHL label? or SHL should be same per ESI irrespective of number of applications enabled in that ESI.

Thanks,
Gangadhar




___________________________________________________________________________

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