< draft-ietf-bier-bierin6-00.txt   draft-ietf-bier-bierin6-01.txt >
BIER Z. Zhang BIER Z. Zhang
Internet-Draft ZTE Corporation Internet-Draft ZTE Corporation
Intended status: Standards Track Z. Zhang, Ed. Intended status: Standards Track Z. Zhang, Ed.
Expires: December 16, 2021 Juniper Networks Expires: 11 June 2022 Juniper Networks
I. Wijnands I. Wijnands
Individual Individual
M. Mishra M. Mishra
Cisco Systems Cisco Systems
H. Bidgoli H. Bidgoli
Nokia Nokia
G. Mishra, Ed. G. Mishra
Verizon Verizon
June 14, 2021 8 December 2021
Supporting BIER in IPv6 Networks (BIERin6) Supporting BIER in IPv6 Networks (BIERin6)
draft-ietf-bier-bierin6-00 draft-ietf-bier-bierin6-01
Abstract Abstract
BIER is a new architecture for the forwarding of multicast data BIER is a new architecture for the forwarding of multicast data
packets without requiring per-flow state inside the network. This packets without requiring per-flow state inside the network. This
document describes how the existing BIER encapsulation specified in document describes how the existing BIER encapsulation specified in
RFC 8296 works in an IPv6 non-MPLS network, referred to as BIERin6. RFC 8296 works in an IPv6 non-MPLS network, referred to as BIERin6.
Specifically, like in an IPv4 network, BIER can work over L2 links Specifically, like in an IPv4 network, BIER can work over L2 links
directly or over tunnels. In case of IPv6 tunneling, a new IP "Next directly or over tunnels. In case of IPv6 tunneling, a new IP "Next
Header" type is to be assigned for BIER. Header" type is to be assigned for BIER.
skipping to change at page 2, line 7 skipping to change at page 2, line 10
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 December 16, 2021. This Internet-Draft will expire on 11 June 2022.
Copyright Notice Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the Copyright (c) 2021 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/
(https://trustee.ietf.org/license-info) in effect on the date of license-info) in effect on the date of publication of this document.
publication of this document. Please review these documents Please review these documents carefully, as they describe your rights
carefully, as they describe your rights and restrictions with respect and restrictions with respect to this document. Code Components
to this document. Code Components extracted from this document must extracted from this document must include Revised BSD License text as
include Simplified BSD License text as described in Section 4.e of described in Section 4.e of the Trust Legal Provisions and are
the Trust Legal Provisions and are provided without warranty as provided without warranty as described in the Revised BSD License.
described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. BIER over L2/Tunnels . . . . . . . . . . . . . . . . . . 3 1.1. BIER over L2/Tunnels . . . . . . . . . . . . . . . . . . 3
1.2. Considerations of Requirements for BIER in IPv6 Networks 3 1.2. Considerations of Requirements for BIER in IPv6
Networks . . . . . . . . . . . . . . . . . . . . . . . . 4
2. IPv6 Header . . . . . . . . . . . . . . . . . . . . . . . . . 5 2. IPv6 Header . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1. IPv6 Options Considerations . . . . . . . . . . . . . . . 5 2.1. IPv6 Options Considerations . . . . . . . . . . . . . . . 6
3. BIER Header . . . . . . . . . . . . . . . . . . . . . . . . . 6 3. BIER Header . . . . . . . . . . . . . . . . . . . . . . . . . 6
4. IPv6 Encapsulation Advertisement . . . . . . . . . . . . . . 6 4. IPv6 Encapsulation Advertisement . . . . . . . . . . . . . . 6
4.1. Format . . . . . . . . . . . . . . . . . . . . . . . . . 6 4.1. Format . . . . . . . . . . . . . . . . . . . . . . . . . 6
4.2. Inter-area prefix redistribution . . . . . . . . . . . . 7 4.2. Inter-area prefix redistribution . . . . . . . . . . . . 7
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
6. Security Considerations . . . . . . . . . . . . . . . . . . . 7 6. Security Considerations . . . . . . . . . . . . . . . . . . . 7
7. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 7 7. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 8
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
8.1. Normative References . . . . . . . . . . . . . . . . . . 8 8.1. Normative References . . . . . . . . . . . . . . . . . . 8
8.2. Informative References . . . . . . . . . . . . . . . . . 8 8.2. Informative References . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11
1. Introduction 1. Introduction
BIER [RFC8279] is a new architecture for the forwarding of multicast BIER [RFC8279] is a new architecture for the forwarding of multicast
data packets. It provides optimal forwarding through a "multicast data packets. It provides optimal forwarding through a "multicast
domain" and it does not precondition construction of a multicast domain" and it does not precondition construction of a multicast
distribution tree, nor does it require intermediate nodes to maintain distribution tree, nor does it require intermediate nodes to maintain
any per-flow state. any per-flow state.
This document specifies non-MPLS BIER forwarding in an IPv6 [RFC8200] This document specifies non-MPLS BIER forwarding in an IPv6 [RFC8200]
skipping to change at page 3, line 41 skipping to change at page 3, line 41
| Next Header = | | Next Header = |
| BIER | | BIER |
+---------------+------------------------ +---------------+------------------------
Between two directly connected BFRs, a BIER header can directly Between two directly connected BFRs, a BIER header can directly
follow link layer header, e.g., an Ethernet header (with the follow link layer header, e.g., an Ethernet header (with the
Ethertype set to 0xAB37). Optionally, IPv6 encapsulation can be used Ethertype set to 0xAB37). Optionally, IPv6 encapsulation can be used
even between directly connected BFRs (i.e. one-hop IPv6 tunneling) in even between directly connected BFRs (i.e. one-hop IPv6 tunneling) in
the following two cases: the following two cases:
o An operator mandates all traffic to be carried in IPv6. * An operator mandates all traffic to be carried in IPv6.
o A BFR does not have BIER support in its "fast forwarding path" and * A BFR does not have BIER support in its "fast forwarding path" and
relies on "slow/software forwarding path", e.g. in environments relies on "slow/software forwarding path", e.g. in environments
like [RFC7368] where high throughput multicast forwarding like [RFC7368] where high throughput multicast forwarding
performance is not critical. performance is not critical.
1.2. Considerations of Requirements for BIER in IPv6 Networks 1.2. Considerations of Requirements for BIER in IPv6 Networks
[draft-ietf-bier-ipv6-requirements] lists mandatory and optional [draft-ietf-bier-ipv6-requirements] lists mandatory and optional
requirements for BIER in IPv6 Networks. As a solution based on the requirements for BIER in IPv6 Networks. As a solution based on the
BIER over L2/tunnel model [RFC8296], BIERin6 satisfies all the BIER over L2/tunnel model [RFC8296], BIERin6 satisfies all the
mandatory requirements. mandatory requirements.
For the two optional requirements for fragmentation and Encapsulating For the two optional requirements for fragmentation and Encapsulating
Security Payload (ESP), they can be satisfied by one of two ways: Security Payload (ESP), they can be satisfied by one of two ways:
o IPv6 based fragmentation/ESP: a BFIR encapsulates the payload in * IPv6 based fragmentation/ESP: a BFIR encapsulates the payload in
IPv6 with fragmentation and/or ESP header, and then the IPv6 IPv6 with fragmentation and/or ESP header, and then the IPv6
packets are treated as BIER payload. packets are treated as BIER payload.
o Generic Fragmentation/ESP * Generic Fragmentation/ESP
[I-D.zzhang-tsvwg-generic-transport-functions]: a BFIR does [I-D.zzhang-tsvwg-generic-transport-functions]: a BFIR does
generic fragmentation and/or ESP (without using IPv6 generic fragmentation and/or ESP (without using IPv6
encapsulation) and the resulting packets are treated as BIER encapsulation) and the resulting packets are treated as BIER
payload. payload.
Either way, the fragmentation/ESP is handled by a layer outside of Either way, the fragmentation/ESP is handled by a layer outside of
BIER and then the resulting packets are treated as BIER payload. BIER and then the resulting packets are treated as BIER payload.
BIERin6 does support SRv6 based overlay services (e.g. MVPN/EVPN). BIERin6 does support SRv6 based overlay services (e.g. MVPN/EVPN).
One of the following methods can be used (relevant overlay signaling One of the following methods can be used (relevant overlay signaling
will be specified separately): will be specified separately):
o An ingress PE (which is a BFIR) can encapsulate customer packets * An ingress PE (which is a BFIR) can encapsulate customer packets
with an IPv6 header (with optional fragmentation and ESP extension with an IPv6 header (with optional fragmentation and ESP extension
headers). The destination address is a multicast locator plus the headers). The destination address is a multicast locator plus the
Fucn/Arg portion that identifies the service. That IPv6 packet is Fucn/Arg portion that identifies the service. That IPv6 packet is
then treated as BIER payload. An egress PE (which is a BFER) uses then treated as BIER payload. An egress PE (which is a BFER) uses
the standard SRv6 procedures to forward the IPv6 packet that is the standard SRv6 procedures to forward the IPv6 packet that is
exposed after the BIER header is decapsulated. exposed after the BIER header is decapsulated.
o Alternatively, since only the destination IPv6 address in the * Alternatively, since only the destination IPv6 address in the
above-mentioned IPv6 header is used for service delimiting above-mentioned IPv6 header is used for service delimiting
purpose, a new value can be assigned for the Proto field in the purpose, a new value can be assigned for the Proto field in the
BIER header to indicate that an IPv6 address (instead of an entire BIER header to indicate that an IPv6 address (instead of an entire
IPv6 header) is added between the BIER header and original IPv6 header) is added between the BIER header and original
payload. payload.
BIERin6 being a solution based on [RFC8279] [RFC8296], ECMP is BIERin6 being a solution based on [RFC8279] [RFC8296], ECMP is
inherently supported by BFRs using the the 20-bit entropy field in inherently supported by BFRs using the the 20-bit entropy field in
the BIER header for the load balancing hash. When a BIER packet is the BIER header for the load balancing hash. When a BIER packet is
transported over an IPv6 tunnel, the entropy value is copied into the transported over an IPv6 tunnel, the entropy value is copied into the
skipping to change at page 5, line 15 skipping to change at page 5, line 19
the BIER header as an IP header so no misordering should happen. the BIER header as an IP header so no misordering should happen.
BIER has its own OAM functions independent of those related to the BIER has its own OAM functions independent of those related to the
underlying links or tunnels. With BIERin6 following the "BIER over underlying links or tunnels. With BIERin6 following the "BIER over
L2/tunnel" model, IPv6 OAM function and BIER OAM functions are used L2/tunnel" model, IPv6 OAM function and BIER OAM functions are used
independently for their own purposes. independently for their own purposes.
Specifically, BIERin6 works with all of the following OAM methods, or Specifically, BIERin6 works with all of the following OAM methods, or
any future methods that are based on the "BIER over L2/tunnel" model: any future methods that are based on the "BIER over L2/tunnel" model:
o BIER OAM specified in [I-D.ietf-bier-ping] * BIER OAM specified in [I-D.ietf-bier-ping]
o BIER BFD specified in [I-D.ietf-bier-bfd] * BIER BFD specified in [I-D.ietf-bier-bfd]
o BIER Performance Measurement specified in [I-D.ietf-bier-pmmm-oam] * BIER Performance Measurement specified in [I-D.ietf-bier-pmmm-oam]
o BIER Path Maximum Transmission Unit Discovery specified in * BIER Path Maximum Transmission Unit Discovery specified in
[I-D.ietf-bier-path-mtu-discovery] [I-D.ietf-bier-path-mtu-discovery]
o BIER IOAM specified in [I-D.xzlnp-bier-ioam] * BIER IOAM specified in [I-D.xzlnp-bier-ioam]
2. IPv6 Header 2. IPv6 Header
Whenever IPv6 encapsulation is used for BIER forwarding, The Next Whenever IPv6 encapsulation is used for BIER forwarding, The Next
Header field in the IPv6 Header (if there are no extension headers), Header field in the IPv6 Header (if there are no extension headers),
or the Next Header field in the last extension header is set to TBD, or the Next Header field in the last extension header is set to TBD,
indicating that the payload is a BIER packet. indicating that the payload is a BIER packet.
If the neighbor is directly connected, The destination address in If the neighbor is directly connected, The destination address in
IPv6 header SHOULD be the neighbor's link-local address on this IPv6 header SHOULD be the neighbor's link-local address on this
skipping to change at page 7, line 5 skipping to change at page 7, line 11
Encapsulation sub-TLV defined in OSPFv3, and a new sub-sub-sub-TLV of Encapsulation sub-TLV defined in OSPFv3, and a new sub-sub-sub-TLV of
BIER Ethernet Encapsulation sub-sub-TLV defined in ISIS, as per BIER Ethernet Encapsulation sub-sub-TLV defined in ISIS, as per
[I-D.ietf-bier-lsr-ethernet-extensions]. [I-D.ietf-bier-lsr-ethernet-extensions].
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | | Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o Type: For OSPF, value TBD1 (prefer 1) is used to indicate it is * Type: For OSPF, value TBD1 (prefer 1) is used to indicate it is
the IPv6 transportation sub-TLV. For ISIS, value TBD2 (prefer 1) the IPv6 transportation sub-TLV. For ISIS, value TBD2 (prefer 1)
is used to indicate it is the IPv6 transportation sub-sub-TLV. is used to indicate it is the IPv6 transportation sub-sub-TLV.
o Length: 0. * Length: 0.
4.2. Inter-area prefix redistribution 4.2. Inter-area prefix redistribution
When BFR-prefixes are advertised across IGP areas per When BFR-prefixes are advertised across IGP areas per
[I-D.ietf-bier-lsr-ethernet-extensions] or redistributed across [I-D.ietf-bier-lsr-ethernet-extensions] or redistributed across
protocol boundaries per [I-D.ietf-bier-prefix-redistribute], the BIER protocol boundaries per [I-D.ietf-bier-prefix-redistribute], the BIER
IPv6 transportation sub-sub-TLV or sub-sub-sub-TLV MAY be re- IPv6 transportation sub-sub-TLV or sub-sub-sub-TLV MAY be re-
advertised/re-distributed as well. advertised/re-distributed as well.
5. IANA Considerations 5. IANA Considerations
skipping to change at page 8, line 47 skipping to change at page 9, line 8
[RFC8401] Ginsberg, L., Ed., Przygienda, T., Aldrin, S., and Z. [RFC8401] Ginsberg, L., Ed., Przygienda, T., Aldrin, S., and Z.
Zhang, "Bit Index Explicit Replication (BIER) Support via Zhang, "Bit Index Explicit Replication (BIER) Support via
IS-IS", RFC 8401, DOI 10.17487/RFC8401, June 2018, IS-IS", RFC 8401, DOI 10.17487/RFC8401, June 2018,
<https://www.rfc-editor.org/info/rfc8401>. <https://www.rfc-editor.org/info/rfc8401>.
8.2. Informative References 8.2. Informative References
[I-D.ietf-bier-bar-ipa] [I-D.ietf-bier-bar-ipa]
Zhang, Z., Przygienda, A., Dolganow, A., Bidgoli, H., Zhang, Z., Przygienda, A., Dolganow, A., Bidgoli, H.,
Wijnands, I., and A. Gulko, "BIER Underlay Path Wijnands, I., and A. Gulko, "BIER Underlay Path
Calculation Algorithm and Constraints", draft-ietf-bier- Calculation Algorithm and Constraints", Work in Progress,
bar-ipa-07 (work in progress), September 2020. Internet-Draft, draft-ietf-bier-bar-ipa-09, 24 October
2021, <https://www.ietf.org/archive/id/draft-ietf-bier-
bar-ipa-09.txt>.
[I-D.ietf-bier-bfd] [I-D.ietf-bier-bfd]
Xiong, Q., Mirsky, G., Hu, F., and C. Liu, "BIER BFD", Xiong, Q., Mirsky, G., Hu, F., and C. Liu, "BIER BFD",
draft-ietf-bier-bfd-01 (work in progress), April 2021. Work in Progress, Internet-Draft, draft-ietf-bier-bfd-01,
8 April 2021, <https://www.ietf.org/archive/id/draft-ietf-
bier-bfd-01.txt>.
[I-D.ietf-bier-idr-extensions] [I-D.ietf-bier-idr-extensions]
Xu, X., Chen, M., Patel, K., Wijnands, I., and A. Xu, X., Chen, M., Patel, K., Wijnands, I., and A.
Przygienda, "BGP Extensions for BIER", draft-ietf-bier- Przygienda, "BGP Extensions for BIER", Work in Progress,
idr-extensions-07 (work in progress), September 2019. Internet-Draft, draft-ietf-bier-idr-extensions-07, 6
September 2019, <https://www.ietf.org/archive/id/draft-
ietf-bier-idr-extensions-07.txt>.
[I-D.ietf-bier-ipv6-requirements] [I-D.ietf-bier-ipv6-requirements]
McBride, M., Xie, J., Geng, X., Dhanaraj, S., Asati, R., McBride, M., Xie, J., Geng, X., Dhanaraj, S., Asati, R.,
Zhu, Y., Mishra, G., and Z. Zhang, "BIER IPv6 Zhu, Y., Mishra, G., and Z. Zhang, "BIER IPv6
Requirements", draft-ietf-bier-ipv6-requirements-09 (work Requirements", Work in Progress, Internet-Draft, draft-
in progress), September 2020. ietf-bier-ipv6-requirements-09, 28 September 2020,
<https://www.ietf.org/archive/id/draft-ietf-bier-ipv6-
requirements-09.txt>.
[I-D.ietf-bier-lsr-ethernet-extensions] [I-D.ietf-bier-lsr-ethernet-extensions]
Dhanaraj, S., Yan, G., Wijnands, I., Psenak, P., Zhang, Dhanaraj, S., Yan, G., Wijnands, I., Psenak, P., Zhang,
Z., and J. Xie, "LSR Extensions for BIER over Ethernet", Z., and J. Xie, "LSR Extensions for BIER over Ethernet",
draft-ietf-bier-lsr-ethernet-extensions-02 (work in Work in Progress, Internet-Draft, draft-ietf-bier-lsr-
progress), December 2020. ethernet-extensions-02, 2 December 2020,
<https://www.ietf.org/archive/id/draft-ietf-bier-lsr-
ethernet-extensions-02.txt>.
[I-D.ietf-bier-non-mpls-bift-encoding] [I-D.ietf-bier-non-mpls-bift-encoding]
Wijnands, I., Mishra, M., Xu, X., and H. Bidgoli, "An Wijnands, I., Mishra, M., Xu, X., and H. Bidgoli, "An
Optional Encoding of the BIFT-id Field in the non-MPLS Optional Encoding of the BIFT-id Field in the non-MPLS
BIER Encapsulation", draft-ietf-bier-non-mpls-bift- BIER Encapsulation", Work in Progress, Internet-Draft,
encoding-03 (work in progress), November 2020. draft-ietf-bier-non-mpls-bift-encoding-04, 30 May 2021,
<https://www.ietf.org/archive/id/draft-ietf-bier-non-mpls-
bift-encoding-04.txt>.
[I-D.ietf-bier-ospfv3-extensions] [I-D.ietf-bier-ospfv3-extensions]
Psenak, P., Nainar, N. K., and I. Wijnands, "OSPFv3 Psenak, P., Nainar, N. K., and I. Wijnands, "OSPFv3
Extensions for BIER", draft-ietf-bier-ospfv3-extensions-03 Extensions for BIER", Work in Progress, Internet-Draft,
(work in progress), November 2020. draft-ietf-bier-ospfv3-extensions-05, 19 November 2021,
<https://www.ietf.org/archive/id/draft-ietf-bier-ospfv3-
extensions-05.txt>.
[I-D.ietf-bier-path-mtu-discovery] [I-D.ietf-bier-path-mtu-discovery]
Mirsky, G., Przygienda, T., and A. Dolganow, "Path Maximum Mirsky, G., Przygienda, T., and A. Dolganow, "Path Maximum
Transmission Unit Discovery (PMTUD) for Bit Index Explicit Transmission Unit Discovery (PMTUD) for Bit Index Explicit
Replication (BIER) Layer", draft-ietf-bier-path-mtu- Replication (BIER) Layer", Work in Progress, Internet-
discovery-10 (work in progress), March 2021. Draft, draft-ietf-bier-path-mtu-discovery-11, 4 October
2021, <https://www.ietf.org/archive/id/draft-ietf-bier-
path-mtu-discovery-11.txt>.
[I-D.ietf-bier-ping] [I-D.ietf-bier-ping]
Kumar, N., Pignataro, C., Akiya, N., Zheng, L., Chen, M., Kumar, N., Pignataro, C., Akiya, N., Zheng, L., Chen, M.,
and G. Mirsky, "BIER Ping and Trace", draft-ietf-bier- and G. Mirsky, "BIER Ping and Trace", Work in Progress,
ping-07 (work in progress), May 2020. Internet-Draft, draft-ietf-bier-ping-07, 11 May 2020,
<https://www.ietf.org/archive/id/draft-ietf-bier-ping-
07.txt>.
[I-D.ietf-bier-pmmm-oam] [I-D.ietf-bier-pmmm-oam]
Mirsky, G., Zheng, L., Chen, M., and G. Fioccola, Mirsky, G., Zheng, L., Chen, M., and G. Fioccola,
"Performance Measurement (PM) with Marking Method in Bit "Performance Measurement (PM) with Marking Method in Bit
Index Explicit Replication (BIER) Layer", draft-ietf-bier- Index Explicit Replication (BIER) Layer", Work in
pmmm-oam-10 (work in progress), March 2021. Progress, Internet-Draft, draft-ietf-bier-pmmm-oam-11, 4
October 2021, <https://www.ietf.org/archive/id/draft-ietf-
bier-pmmm-oam-11.txt>.
[I-D.ietf-bier-prefix-redistribute] [I-D.ietf-bier-prefix-redistribute]
Zhang, Z., Wu, B., Zhang, Z., Wijnands, I., and Y. Liu, Zhang, Z., Wu, B., Zhang, Z., Wijnands, I., and Y. Liu,
"BIER Prefix Redistribute", draft-ietf-bier-prefix- "BIER Prefix Redistribute", Work in Progress, Internet-
redistribute-00 (work in progress), August 2020. Draft, draft-ietf-bier-prefix-redistribute-00, 4 August
2020, <https://www.ietf.org/archive/id/draft-ietf-bier-
prefix-redistribute-00.txt>.
[I-D.xzlnp-bier-ioam] [I-D.xzlnp-bier-ioam]
Min, X., Zhang, Z., Liu, Y., Nainar, N. K., and C. Min, X., Zhang, Z., Liu, Y., Nainar, N. K., and C.
Pignataro, "Bit Index Explicit Replication (BIER) Pignataro, "Bit Index Explicit Replication (BIER)
Encapsulation for In-situ OAM (IOAM) Data", draft-xzlnp- Encapsulation for In-situ OAM (IOAM) Data", Work in
bier-ioam-01 (work in progress), January 2021. Progress, Internet-Draft, draft-xzlnp-bier-ioam-02, 11
July 2021, <https://www.ietf.org/archive/id/draft-xzlnp-
bier-ioam-02.txt>.
[I-D.zhang-bier-babel-extensions] [I-D.zhang-bier-babel-extensions]
Zhang, Z. and T. Przygienda, "BIER in BABEL", draft-zhang- Zhang, Z. and T. Przygienda, "BIER in BABEL", Work in
bier-babel-extensions-04 (work in progress), November Progress, Internet-Draft, draft-zhang-bier-babel-
2020. extensions-06, 7 November 2021,
<https://www.ietf.org/archive/id/draft-zhang-bier-babel-
extensions-06.txt>.
[I-D.zzhang-tsvwg-generic-transport-functions] [I-D.zzhang-tsvwg-generic-transport-functions]
Zhang, Z., Bonica, R., and K. Kompella, "Generic Transport Zhang, Z., Bonica, R., and K. Kompella, "Generic Transport
Functions", draft-zzhang-tsvwg-generic-transport- Functions", Work in Progress, Internet-Draft, draft-
functions-00 (work in progress), November 2020. zzhang-tsvwg-generic-transport-functions-00, 1 November
2020, <https://www.ietf.org/archive/id/draft-zzhang-tsvwg-
generic-transport-functions-00.txt>.
[RFC7368] Chown, T., Ed., Arkko, J., Brandt, A., Troan, O., and J. [RFC7368] Chown, T., Ed., Arkko, J., Brandt, A., Troan, O., and J.
Weil, "IPv6 Home Networking Architecture Principles", Weil, "IPv6 Home Networking Architecture Principles",
RFC 7368, DOI 10.17487/RFC7368, October 2014, RFC 7368, DOI 10.17487/RFC7368, October 2014,
<https://www.rfc-editor.org/info/rfc7368>. <https://www.rfc-editor.org/info/rfc7368>.
Authors' Addresses Authors' Addresses
Zheng(Sandy) Zhang Zheng(Sandy) Zhang
ZTE Corporation ZTE Corporation
EMail: zhang.zheng@zte.com.cn Email: zhang.zheng@zte.com.cn
Zhaohui Zhang (editor) Zhaohui Zhang (editor)
Juniper Networks Juniper Networks
EMail: zzhang@juniper.net Email: zzhang@juniper.net
IJsbrand Wijnands IJsbrand Wijnands
Individual Individual
EMail: ice@braindump.be Email: ice@braindump.be
Mankamana Mishra Mankamana Mishra
Cisco Systems Cisco Systems
EMail: mankamis@cisco.com Email: mankamis@cisco.com
Hooman Bidgoli Hooman Bidgoli
Nokia Nokia
EMail: hooman.bidgoli@nokia.com Email: hooman.bidgoli@nokia.com
Gyan Mishra (editor) Gyan Mishra
Verizon Verizon
EMail: gyan.s.mishra@verizon.com Email: gyan.s.mishra@verizon.com
 End of changes. 44 change blocks. 
65 lines changed or deleted 94 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/