Subject: BIERv6 source-routing multicast -- BIER in IPv6

From: "Xiejingrong (Jingrong)" <[email-masked]>
Date: Wed, 18 Mar 2020 06:51:19 +0000

Hi 6man WG,

Appreciated for your comments for this draft (BIERv6 for short) on this specific topic.
https://datatracker.ietf.org/doc/draft-xie-bier-ipv6-encapsulation/

For ease of understanding, I can shortly introduce this behavior we proposed:
(1) An encapsulation named BIER IPv6 encapsulation, looks like {IPv6 hdr, DOH<with BIER header as Option Data>, Inner IP-multicast-packet}. The BIER header [RFC8279] contains a BitString, and each bit of the BitString represents an ultimate destination of a router in a limited-domain called BIER domain.
(2) Router A send a packet as depicted above to B (with packet's destination address being B's address), and then B send to C and D according to the BitString, with packet's destination address being C's address and D's address respectively, and BitString being changed per the BIER procedures (RFC8279).

Best regards,
Jingrong

From: ipv6 [mailto:[email-masked]] On Behalf Of Michael McBride
Sent: Wednesday, March 18, 2020 12:19 PM
To: [email-masked]
Subject: BIER in IPv6

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