< draft-wang-bier-rh-bier-04.txt   draft-wang-bier-rh-bier-05.txt >
BIER Working Group W. Wang BIER Working Group W. Wang
Internet-Draft A. Wang Internet-Draft A. Wang
Intended status: Standards Track China Telecom Intended status: Standards Track China Telecom
Expires: September 8, 2022 H. Chen Expires: September 22, 2022 H. Chen
Futurewei Futurewei
G. Mishra G. Mishra
Verizon Inc. Verizon Inc.
March 7, 2022 B. Xu
Huawei Technologies (2012Lab)
March 21, 2022
Routing Header Based BIER Information Encapsulation Routing Header Based BIER Information Encapsulation
draft-wang-bier-rh-bier-04 draft-wang-bier-rh-bier-05
Abstract Abstract
This draft proposes one new encapsulation schema of Bit Index This draft proposes one new encapsulation schema of Bit Index
Explicit Replication (BIER) information to transfer the multicast Explicit Replication (BIER) information to transfer the multicast
packets within the IPv6 network. By using a new type of IPv6 Routing packets within the IPv6 network. By using a new type of IPv6 Routing
Header to forward the packet, the original source address and Header to forward the packet, the original source address and
destination address of the multicast packet is kept unchanged along destination address of the multicast packet is kept unchanged along
the forwarding path. Such encapsulation schema can make full use of the forwarding path. Such encapsulation schema can make full use of
the existing IPv6 quality assurance solutions to provide high-quality the existing IPv6 quality assurance solutions to provide high-quality
skipping to change at page 1, line 41 skipping to change at page 1, line 43
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 8, 2022. This Internet-Draft will expire on September 22, 2022.
Copyright Notice Copyright Notice
Copyright (c) 2022 IETF Trust and the persons identified as the Copyright (c) 2022 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 17 skipping to change at page 2, line 20
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions used in this document . . . . . . . . . . . . . . 3 2. Conventions used in this document . . . . . . . . . . . . . . 3
3. BIER Routing Header . . . . . . . . . . . . . . . . . . . . . 3 3. BIER Routing Header . . . . . . . . . . . . . . . . . . . . . 3
4. Multicast Packet Forwarding Procedures . . . . . . . . . . . 5 4. Multicast Packet Forwarding Procedures . . . . . . . . . . . 4
4.1. All nodes in BIER domain support BIER Routing Header . . 6 4.1. All nodes in BIER domain support BIER Routing Header . . 5
4.2. Some nodes in BIER domain do not support BIER Routing 4.2. Some nodes in BIER domain do not support BIER Routing
Header . . . . . . . . . . . . . . . . . . . . . . . . . 8 Header . . . . . . . . . . . . . . . . . . . . . . . . . 7
5. Security Considerations . . . . . . . . . . . . . . . . . . . 10 5. Security Considerations . . . . . . . . . . . . . . . . . . . 9
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 10 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
7.1. Normative References . . . . . . . . . . . . . . . . . . 10 7.1. Normative References . . . . . . . . . . . . . . . . . . 9
7.2. Informative References . . . . . . . . . . . . . . . . . 10 7.2. Informative References . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction 1. Introduction
Bit Index Explicit Replication (BIER) is a new multicast technology Bit Index Explicit Replication (BIER) is a new multicast technology
based on IPv6 defined in [RFC8279]. In BIER domain, the set of based on IPv6 defined in [RFC8279]. In BIER domain, the set of
destination nodes of multicast message is mapped into a BitString and destination nodes of multicast message is mapped into a BitString and
encapsulated into the BIER header. The position of each bit in the encapsulated into the BIER header. The position of each bit in the
BitString represents an BFER. Compared with the traditional BitString represents an BFER. Compared with the traditional
multicast technologies, the nodes in BIER domain do not need to multicast technologies, the nodes in BIER domain do not need to
maintain a multicast tree and keep the multicast flow state for each maintain a multicast tree and keep the multicast flow state for each
skipping to change at page 4, line 8 skipping to change at page 3, line 41
document are to be interpreted as described in [RFC2119] . document are to be interpreted as described in [RFC2119] .
3. BIER Routing Header 3. BIER Routing Header
One new type of IPv6 Routing Header is defined according to One new type of IPv6 Routing Header is defined according to
[RFC8200]. The message format is shown in Figure 1. [RFC8200]. The message format is shown in Figure 1.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Next Header | Hdr Ext Len | Routing Type | Segment Left | | Next Header | Hdr Ext Len | Routing Type | BIER-TE Algo |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BIFT-id | TC |S| TTL |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Nibble | Ver | BSL | Entropy |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|OAM|Rsv| DSCP | Proto | BFIR-id |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BitString (first 32 bits) ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ BitString (last 32 bits) | | BIER-TE Algorithm specified part |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: The format of BIER Routing Header Figure 1: The format of BIER Routing Header
Where: Where:
o Next Header(8 bits): indicating the message header type o Next Header (8 bits): indicating the message header type
immediately after the routing header. immediately after the Routing Header.
o HDR Ext Len(8 bits): indicating the length of the routing header. o HDR Ext Len (8 bits): indicating the length of the Routing Header.
o Routing Type(8 bits): TBD. Identifying the newly defined Routing o Routing Type (8 bits): TBD. Identifying the newly defined Routing
Header to encode BIER information. Header to encode BIER information.
o Segments Left(8 bits): indicating the number of explicitly listed o BIER-TE Algo (8 bits): indicating the BIER-TE Algorithm for RH-
intermediate nodes to be accessed before reaching the final BIER packets. Different values of this field refer to different
destination. It is not used here for the time being, and all are BIER-TE Algorithm:
set to 0.
o BIFT-id(20 bits): each < SD, Si, BSL > is assigned a BIFT-id.
o TC(3 bits): see [RFC8296]. This field is set to 0.
o S(1 bit): see [RFC8296]. This field is set to 0.
o TTL(8 bits): indicating the lifetime of the message. It is used
to prevent ring. The processing process is the same as that in
non MPLS networks.
o Nibble(4 bits): see [RFC8296]. This field is set to 0.
o Ver(4 bits): identifying the version of the BIER header. When an * Value 0: reserved.
unsupported BIER header version is received, the BFR needs to
discard the packet and record the error.
o BSL(4 bits): indicating the length of BitString. * Value 1: IGP
o Entropy(20 bits): this field specifies an "entropy" for ECMP. * Value 2: CGM2 (see [I-D.eckert-bier-cgm2-rbs])
o OAM(2 bits): by default, this value will be set to 0 by BFIR, and * Value 3: MRH (see [I-D.chen-pim-mrh6])
other BFRs will not be modified. Whether to use this field is
optional.
o Rsv(2 bits): unused, set to 0. * Value 4-127: Expert Reviews
o DSCP(6 bits): this field is used to support different service * Value 128-255: Flexible Algorithms
codes.
o Proto(6 bits): see [RFC8296]. This field is set to 0. o BIER-TE Algorithm specified part (variable): the encoding of this
part depends on the value of BIER-TE Algo field:
o BFIR-id(16 bits): indicating BFR ID of BFIR. * Value 1: The BIER-TE Algorithm is IGP, the encoding format of
this part is described in [RFC8296].
o Reserved (14 bits): reserved field, set to 0. * Value 2: The BIER-TE Algorithm is CGM2, the encoding format of
this part is described in [I-D.eckert-bier-cgm2-rbs].
o BitString(variable): the length must be reflected in the BSL * Value 3: The BIER-TE Algorithm is MRH6, the encoding format of
field. The string saved in this field is used to identify the this part is described in [I-D.chen-pim-mrh6].
destination BFER of the packet.
4. Multicast Packet Forwarding Procedures 4. Multicast Packet Forwarding Procedures
Based on the newly defined BIER Routing Header, the nodes support Based on the newly defined BIER Routing Header, the nodes support
BIER Routing Header will perform the following steps to forward the BIER Routing Header will perform the following steps to forward the
multicast packets: multicast packets:
1) When a BFIR receive a multicast packet, it will find out the 1) When a BFIR receive a multicast packet, it will find out the
destination address and RD that relate to the source interface of the destination address and RD that relate to the source interface of the
packet. BFIR looks up its End.MVPN mapping table to find the packet. BFIR looks up its End.MVPN mapping table to find the
skipping to change at page 10, line 44 skipping to change at page 9, line 44
<https://www.rfc-editor.org/info/rfc8279>. <https://www.rfc-editor.org/info/rfc8279>.
[RFC8296] Wijnands, IJ., Ed., Rosen, E., Ed., Dolganow, A., [RFC8296] Wijnands, IJ., Ed., Rosen, E., Ed., Dolganow, A.,
Tantsura, J., Aldrin, S., and I. Meilik, "Encapsulation Tantsura, J., Aldrin, S., and I. Meilik, "Encapsulation
for Bit Index Explicit Replication (BIER) in MPLS and Non- for Bit Index Explicit Replication (BIER) in MPLS and Non-
MPLS Networks", RFC 8296, DOI 10.17487/RFC8296, January MPLS Networks", RFC 8296, DOI 10.17487/RFC8296, January
2018, <https://www.rfc-editor.org/info/rfc8296>. 2018, <https://www.rfc-editor.org/info/rfc8296>.
7.2. Informative References 7.2. Informative References
[I-D.chen-pim-mrh6]
Chen, H., McBride, M., Fan, Y., Li, Z., Geng, X., Toy, M.,
Mishra, G. S., Liu, Y., Wang, A., Liu, L., and X. Liu,
"Multicast using Multicast Routing Header", draft-chen-
pim-mrh6-01 (work in progress), March 2022.
[I-D.eckert-bier-cgm2-rbs]
Eckert, T. and B. (. Xu, "Carrier Grade Minimalist
Multicast (CGM2) using Bit Index Explicit Replication
(BIER) with Recursive BitString Structure (RBS)
Addresses", draft-eckert-bier-cgm2-rbs-01 (work in
progress), February 2022.
[I-D.ietf-bier-bierin6] [I-D.ietf-bier-bierin6]
Zhang, Z., Zhang, Z., Wijnands, I., Mishra, M., Bidgoli, Zhang, Z., Zhang, Z., Wijnands, I., Mishra, M., Bidgoli,
H., and G. Mishra, "Supporting BIER in IPv6 Networks H., and G. Mishra, "Supporting BIER in IPv6 Networks
(BIERin6)", draft-ietf-bier-bierin6-04 (work in progress), (BIERin6)", draft-ietf-bier-bierin6-04 (work in progress),
March 2022. March 2022.
[I-D.xie-bier-ipv6-encapsulation] [I-D.xie-bier-ipv6-encapsulation]
Xie, J., Geng, L., McBride, M., Asati, R., Dhanaraj, S., Xie, J., Geng, L., McBride, M., Asati, R., Dhanaraj, S.,
Zhu, Y., Qin, Z., Shin, M., Mishra, G., and X. Geng, Zhu, Y., Qin, Z., Shin, M., Mishra, G., and X. Geng,
"Encapsulation for BIER in Non-MPLS IPv6 Networks", draft- "Encapsulation for BIER in Non-MPLS IPv6 Networks", draft-
skipping to change at page 11, line 37 skipping to change at page 11, line 4
Email: wangaj3@chinatelecom.cn Email: wangaj3@chinatelecom.cn
Huaimo Chen Huaimo Chen
Futurewei Futurewei
Beiqijia Town, Changping District Beiqijia Town, Changping District
Boston, MA Boston, MA
USA USA
Email: Huaimo.chen@futurewei.com Email: Huaimo.chen@futurewei.com
Gyan S. Mishra Gyan S. Mishra
Verizon Inc. Verizon Inc.
13101 Columbia Pike 13101 Columbia Pike
Silver Spring MD 20904 Silver Spring MD 20904
United States of America United States of America
Phone: 301 502-1347 Phone: 301 502-1347
Email: gyan.s.mishra@verizon.com Email: gyan.s.mishra@verizon.com
Bing (Robin) Xu
Huawei Technologies (2012Lab)
Huawei Building, No.156 Beiqing Rd.
Beijing, Beijing 100095
China
Email: bing.xu@huawei.com
 End of changes. 25 change blocks. 
63 lines changed or deleted 51 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/