Re: [Bier] Call For Adoption: draft-zhang-bier-bierin6

Hi Fanghong, 

You misunderstand the update of BIERin6, please find my comments with Sandy> below.

Thanks,

Sandy

原始邮件

发件人：duanfanghong
收件人：gjshep@gmail.com;BIER WG;
日 期 ：2021年03月02日 09:23
主 题 ：Re: [Bier] Call For Adoption: draft-zhang-bier-bierin6

_______________________________________________
BIER mailing list
BIER@ietf.org
https://www.ietf.org/mailman/listinfo/bier

Hi,

I see this document proposes 2 options for MVPN/EVPN.

One is using the destination address to carry the ID of an MVPN/EVPN, but this means that every BFR have to be aware of the MVPN/EVPN instance, introducing state of MVPN/EVPN service and forwarding overhead in transit BFR nodes.

Sandy> No. BFR needs not to know MVPN/EVPN instance. Only BFIR and BFER need to know it. 

The other is to use an IPv6 address after a BIER header and before the customer IP packet, however it proposes a new Proto value and new process in forwarding plane. 

I think both of the options have obvious defects, and thus I do not support the adoption.

Sandy> As I said, only BFIR and BFER need to process the new proto value, it doesn't make affection on the intermediate forwarding plane.

Thanks !

Fanghong Duan

From: BIER [mailto:bier-bounces@ietf.org] On Behalf Of Greg Shepherd
 Sent: Friday, February 26, 2021 12:37 AM
 To: BIER WG <bier@ietf.org>
 Subject: [Bier] Call For Adoption: draft-zhang-bier-bierin6

Thank you all for the active discussion that brought us to consensus. This draft now addresses all of the points of discussion for the solution. 

https://datatracker.ietf.org/doc/draft-zhang-bier-bierin6/

Please reply to this thread with your support/opposition of WG adoption of the draft.

Thanks,

Shep

(Chairs)