Re: [bess] Poll for early allocation request for draft-ietf-bess-mvpn-evpn-aggregation-label

Xiejingrong <> Wed, 12 December 2018 01:13 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 72A37127598 for <>; Tue, 11 Dec 2018 17:13:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id HnOrqF0YYBq1 for <>; Tue, 11 Dec 2018 17:13:49 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 3999E130F63 for <>; Tue, 11 Dec 2018 17:13:49 -0800 (PST)
Received: from (unknown []) by Forcepoint Email with ESMTP id 18E561CDCCEE3 for <>; Wed, 12 Dec 2018 01:13:45 +0000 (GMT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 12 Dec 2018 01:13:45 +0000
Received: from ([fe80::40a8:f0d:c0f3:2ca5]) by ([]) with mapi id 14.03.0415.000; Wed, 12 Dec 2018 09:13:33 +0800
From: Xiejingrong <>
To: "" <>, "" <>
Thread-Topic: Poll for early allocation request for draft-ietf-bess-mvpn-evpn-aggregation-label
Thread-Index: AdSRY0PBVt0YG9tEQjai9rg/QSu3AAAU/xjQ
Date: Wed, 12 Dec 2018 01:13:32 +0000
Message-ID: <>
References: <30268_1544540975_5C0FD32F_30268_272_1_9E32478DFA9976438E7A22F69B08FF924B780A07@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
In-Reply-To: <30268_1544540975_5C0FD32F_30268_272_1_9E32478DFA9976438E7A22F69B08FF924B780A07@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_16253F7987E4F346823E305D08F9115AAB7DB407nkgeml514mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <>
Subject: Re: [bess] Poll for early allocation request for draft-ietf-bess-mvpn-evpn-aggregation-label
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 12 Dec 2018 01:13:51 -0000


I remember I have raised my concerns, but I didn't find the response.

Copy the concerns I have listed before:
1.      The problem stated by this draft is valid, and the proposed method is useful for some of the listed problem. For example, EVPN BUM who uses MPLS identification and dataplane.
2.      EVPN BUM using vxlan/vni identification may not need a MPLS label to identify the vpn/tenant.
3.      For MVPN who has a UMH(Upstream Multicast Hop) selection procedure, the exist using of upstream-assigned VpnLabel can be optimized to only populate to forwarding-state when there are c-multicast flows selecting the specific UMH PE.
4.      For an End-to-End deployment of MVPN who spans multi-ASes as the way stated in <draft-geng-bier-sr-multicast-deployment>, the allocation of a global-unique label is useful and possible. But operators may need to be very careful to allocate the very limited MPLS labels. Because, MPLS labels has been divided to SRLB and SRGB, and SRGB may have been again divided by SR-domains according to <draft-filsfils-spring-large-scale-interconnect-12>.
5.      For segmented MVPN deployment, the further divide of the MPLS Label is also difficult when thinking of the above.
6.      For BIER, is the BIER proto=1 indicating a BIER-specific unique VpnLabel ? or a Per-platform (RFC5331) downstream-assigned unique label ?  if it is the later one, how about adding a new BIER proto value to indicating a BIER-specific unique VpnLabel ?  And then a static Context (BIER) can be optional to the dynamic advertising of a Context ?


From: BESS [] On Behalf Of
Sent: Tuesday, December 11, 2018 11:10 PM
Subject: [bess] Poll for early allocation request for draft-ietf-bess-mvpn-evpn-aggregation-label

Hi WG,

We have received an early allocation request for the draft-ietf-bess-mvpn-evpn-aggregation-label.

Please raise your concerns if you object to this request and if you think that the document is not mature enough.
Feel also free to support this request.

We will wait until next Monday (12/17) to gather feedbacks.




Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.

Thank you.