Re: [Bier] BIER IPv6 Requirement

Hi Xuesong

I am working on an update I will be posting to GitHub using Mikes version.

The main item I am updating is clarifying the BIER layers definition In the
drawing and verbiage with the three layers so it’s crystal clear that we
discussed in our understanding discussion.

Their were some comments that Alvaro mentioned so I am trying to address
some of those as well.

I will be completed tomorrow and then you can update the draft with
comments.

Mike has a -mm version that I am building on in GitHub link below.

 https://github.com/mmcbride7/bier-v6-requirements

Thanks

Gyan

On Thu, Aug 20, 2020 at 3:14 AM Gengxuesong (Geng Xuesong) <
gengxuesong@huawei.com> wrote:

>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Hi Mike, authors and WG,
>
>
>
>
>
> I have read through the existing version of
> draft-ietf-bier-ipv6-requirements and the comments in the mailing list.
> The concerns for this document mainly comes from three aspects:
>
>
>
>
> 1..
>
> The problem statement: why we need BIER IPv6 solution (which I think is
> straight forward: we need solution(s) to deploy BIER in an IPv6 domain)
>
>
>
>
> 2..
>
> The conceptual model for BIER IPv6 encapsulation (the existing model
> classification seems to be roughly agreed in the WG but the descriptions
> should be modified based on the comments)
>
>
>
>
> 3..
>
> The requirement items and classification
>
>
>
>
>
>
> I think the previous two points mainly request editing work and a document
> with some my personal recommended text could be found in the attachment
> just for your reference.
>
>
> For the third point, I list the requirement items based on the existing
> discussions in the WG as follows:
>
>
> *Mandatory:*
>
>
>
>
> Ÿ
>
> L2 Agnostic (may be removed)
>
>
>
>
> Ÿ
>
> Align to BIER architecture defined in RFC8279 (may be removed)
>
>
>
>
> Ÿ
>
> Support deployment with Non-BFR routers
>
>
>
>
> Ÿ
>
> Support OAM
>
>
>
>
> Ÿ
>
> Support overlay service, e.g., MVPN, EVPN
>
>
> *Optional:*
>
>
>
>
> Ÿ
>
> Support native IPv6 functions, e.g., IPSEC, Fragmentation
>
>
>
>
> Ÿ
>
> Support inter-AS multicast deployment
>
>
>
>
> Ÿ
>
> Provide necessary security methods (may be removed)
>
>
>
>
>
> I suggest to discuss and confirm these items in WG first, including what
> should be included/excluded, which one should be mandatory etc., then we
> could work on the detailed explanations for each
>
> item.
>
>
>
>
>
> Best Regards
>
>
> Xuesong
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
>
> BIER mailing list
>
> BIER@ietf.org
>
> https://www.ietf.org/mailman/listinfo/bier
>
> --

<http://www.verizon.com/>

*Gyan Mishra*

*Network Solutions A**rchitect *

*M 301 502-134713101 Columbia Pike *Silver Spring, MD