Re: [Bier] New Version Notification for draft-xie-bier-ipv6-encapsulation-07.txt

["Gengxuesong (Geng Xuesong)" <[e-mail]>]

Hi Tianran,

Thank you for reviewing the draft! Your description is precise: IPv6 DoH with bitstring is parsed to find the next BIER Forwarding Nodes.

Best Regards
Xuesong

From: Tianran Zhou
Sent: Tuesday, July 7, 2020 6:00 PM
To: Gengxuesong (Geng Xuesong) <[e-mail]>; 6man WG <[e-mail]>
Cc: BIER WG <[e-mail]>
Subject: RE: New Version Notification for draft-xie-bier-ipv6-encapsulation-07.txt

Hi Xuesong,

I’ve read this draft, and find it’s an interesting design.
WRT to the IPv6 transport, you proposed the DoH to take the BIER information. So the header is not processed until the packet reaches the destination node. And then change destination address according to the indication of BIER Header.
I think it’s straight forward.

Cheers,
Tianran

From: ipv6 [mailto:[e-mail]] On Behalf Of Gengxuesong (Geng Xuesong)
Sent: Monday, June 29, 2020 5:29 PM
To: 6man WG <[e-mail]<mailto:[e-mail]>>
Cc: BIER WG <[e-mail]<mailto:[e-mail]>>
Subject: FW: New Version Notification for draft-xie-bier-ipv6-encapsulation-07.txt

Hi 6MAN people,

We have updated draft-xie-bier-ipv6-encapsulation-07. This draft defines a multicast solution which enables BIER (RFC 8279 & 8296) forwarding in an IPv6 domain.
The BIER architecture (RFC 8279 & 8296) is maximum reused, with the following 2 additional IPv6 extensions in this document:

Ÿ   Define IPv6 address indicating BIERv6 forwarding, which is called End.BIER.

Ÿ   Define new Destination Options Header, used for carrying BIER Header(bitstring included), which is called BIERv6 DOH.
In the new version of the draft:
Ÿ   Terminologies like “BIERv6 domain” are added or updated.
Ÿ   The use of “Proto” field in BIER header and IPv6 “Next Header” field is revised (main technical improvement in this document).
Ÿ   Editorial changes including wording in security considerations.
Ÿ   Issues raised by IDnits tool are fixed.
Ÿ   Co-authors are added.
It will be great that 6man people could review the document and provide feedback/guidance from IPv6 expert perspective. Particularly:
1) If this document conforms to IPv6 core rule and IPv6 EH mechanism.
2) if this document has any security impacts from the view of IPv6.

Thanks!
Xuesong





> -----Original Message-----

> From: [e-mail]<mailto:[e-mail]> [mailto:[e-mail]]

> Sent: Monday, June 29, 2020 5:23 PM

> To: Mike McBride <[e-mail]<mailto:[e-mail]>>; Yongqing Zhu

> <[e-mail]<mailto:[e-mail]>>; Zhuangzhuang Qin

> <[e-mail]<mailto:[e-mail]>>; Senthil Dhanaraj

> <[e-mail]<mailto:[e-mail]>>; Gengxuesong (Geng Xuesong)

> <[e-mail]<mailto:[e-mail]>>; Xiejingrong (Jingrong)

> <[e-mail]<mailto:[e-mail]>>; Liang Geng <[e-mail]<mailto:[e-mail]>>;

> MooChang Shin <[e-mail]<mailto:[e-mail]>>; Rajiv Asati <[e-mail]<mailto:[e-mail]>>

> Subject: New Version Notification for draft-xie-bier-ipv6-encapsulation-07.txt

>

>

> A new version of I-D, draft-xie-bier-ipv6-encapsulation-07.txt

> has been successfully submitted by Xuesong Geng and posted to the IETF

> repository.

>

> Name:            draft-xie-bier-ipv6-encapsulation

> Revision:        07

> Title:               Encapsulation for BIER in Non-MPLS IPv6 Networks

> Document date:   2020-06-29

> Group:            Individual Submission

> Pages:            19

> URL:

> https://www.ietf.org/internet-drafts/draft-xie-bier-ipv6-encapsulation-07.txt

> Status:

> https://datatracker.ietf.org/doc/draft-xie-bier-ipv6-encapsulation/

> Htmlized:

> https://tools.ietf.org/html/draft-xie-bier-ipv6-encapsulation-07

> Htmlized:

> https://datatracker.ietf.org/doc/html/draft-xie-bier-ipv6-encapsulation

> Diff:

> https://www.ietf.org/rfcdiff?url2=draft-xie-bier-ipv6-encapsulation-07

>

> Abstract:

>    This document proposes a BIER IPv6 (BIERv6) encapsulation for Non-

>    MPLS IPv6 Networks using the IPv6 Destination Option extension

>    header.  This document updates RFC 8296.

>

>

>

>

>

> Please note that it may take a couple of minutes from the time of submission

> until the htmlized version and diff are available at tools.ietf.org.

>

> The IETF Secretariat

>