Re:BIER in IPv6 --- draft-zhang-bier-bierin6-04

Hi,

As co-author of BIERin6 (draft-zhang-bier-bierin6-04), before you read the draft, please let me introduce BIER technology to you at first:

BIER technology, as defined in RFC8279, it's a new multicast technology. The principle is achieving multicast forwarding by hop-by-hop execution.

BIER is a transport protocol, not just a function. As defined in RFC8296, BIER has it's own ethernet encapsulation with ethernet type 0xAB37, and also it can be travelled by MPLS encapsulation.

BIER has it's own OAM function, ECMP function and traceability. etc. through BIER header defined in RFC8296.

For travelling through IPv6 only enviroment, we'd like to travel BIER packet by IPv6 encapsulation.

In draft-zhang-bier-bierin6-04, we want to just use a new Next Header type for BIER header carrying.

We want to bring the minimum impact on IPv6 existed execution, and the maximum flexibility for header interoperability.

So if you have any question about draft-zhang-bier-bierin6-04, or about BIER technology itself, please tell me. I'am glad to explain them to you.

Thanks,

Sandy

原始邮件

发件人：TonyPrzygienda <tonysietf@gmail.com>
收件人：Michael McBride <michael.mcbride@futurewei.com>;
抄送人：6man@ietf.org <6man@ietf.org>;
日 期 ：2020年03月19日 01:12
主 题 ：Re: BIER in IPv6

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

<BIER WG chair hat on> 

The specific ask here is for the 6man to look over both drafts, i.e. 

draft-zhang-bier-bierin6

and 

draft-xie-bier-ipv6-encapsulation

and verify whether they conform to published IPv6 standards or raise objections/concerns.

The requirements document is currently under active work/comments and does not represent any final or wide-consensus state so an opinion on its state is appreciated but it should not be used as any final or binding list of requirements as to the targeted solution in BIER WG

thanks 

--- tony 

On Tue, Mar 17, 2020 at 9:20 PM Michael McBride <michael.mcbride@futurewei.com> wrote:

Hello,

The bier wg could use your ipv6 recommendations. We’ve worked on various solutions to transport a bier header in ipv6. We decided to pause and create a requirements document (draft-ietf-bier-ipv6-requirements) to help steer us towards the
 right solution(s). In that drafts appendix we have a fairly good summary of the various solutions.

We’ve started to rally behind two solutions which meet the majority of the requirements: draft-xie-bier-ipv6-encapsulation (bier header in ipv6 EH) and draft-zhang-bier-bierin6 (bier header as payload using ipv6 NH). The bier chairs today
 asked to punt the bierv6 topic to 6man for advice before adopting any of these solutions.

So here we are seeking your advice. The most simple approach would probably be to give  https://datatracker.ietf.org/doc/draft-ietf-bier-ipv6-requirements/
 a look and scroll down to the appendix to see a summary of the various solutions we’ve been considering.

thanks!

mike

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------