[Bier] Question regarding BIER Proto value 1 and Comments on draft-pengzhang-bier-global-vpnid

[Xiejingrong <[e-mail]>]

Hi BIERs,

Just to clarify in text about my point on the ietf103 mic.


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 ?  the proposal of < draft-pengzhang-bier-global-vnid> is useful then.



If it is the former one, then there is no need to add another BIER proto value.




From: BESS [mailto:[e-mail]] On Behalf Of Xiejingrong
Sent: Sunday, November 4, 2018 10:33 PM
To: [e-mail]; [e-mail]
Cc: [e-mail]
Subject: Re: [bess] WG adoption poll for draft-zzhang-bess-mvpn-evpn-aggregation-label-01

+1 support the adoption.

My comments:

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 [mailto:[e-mail]] On Behalf Of [e-mail]<mailto:[e-mail]>
Sent: Tuesday, October 30, 2018 4:22 PM
To: [e-mail]<mailto:[e-mail]>
Subject: [bess] WG adoption poll for draft-zzhang-bess-mvpn-evpn-aggregation-label-01

Hi WG,

This email begins a two-week poll for BESS working group adoption draft-zzhang-bess-mvpn-evpn-aggregation-label-01 [1]

Please review the draft and post any comments to the BESS working group list, stating whether or not you support adoption.

We are also polling for knowledge of any undisclosed IPR that applies to this Document, to ensure that IPR has been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details).
If you are listed as an author or a contributor of this document, please respond to this email and indicate whether or not you are aware of any relevant undisclosed IPR, copying the BESS mailing list. The document won't progress without answers from all the authors and contributors.

If you are not listed as an author or a contributor, then please explicitly respond only if you are aware of any IPR that has not yet been disclosed in conformance with IETF rules.

The poll for working group adoption closes on Tue 13th November.

Regards,
Stéphane and Matthew

[1] https://datatracker.ietf.org/doc/draft-zzhang-bess-mvpn-evpn-aggregation-label/





[Orange logo]<http://www.orange.com/>

Stephane Litkowski
Network Architect
Orange/SCE/EQUANT/OINIS/NET
Orange Expert Future Networks
phone: [phone] <https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%202%2023%2028%2049%2083%20>  NEW !
mobile: [phone] <https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%206%2037%2086%2097%2052%20>  NEW !
[e-mail]<mailto:[e-mail]>


_________________________________________________________________________________________________________________________



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.