< draft-ietf-bier-bierin6-02.txt   draft-ietf-bier-bierin6-03.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: 10 July 2022 Juniper Networks Expires: 7 August 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 G. Mishra
Verizon Verizon
6 January 2022 3 February 2022
Supporting BIER in IPv6 Networks (BIERin6) Supporting BIER in IPv6 Networks (BIERin6)
draft-ietf-bier-bierin6-02 draft-ietf-bier-bierin6-03
Abstract Abstract
BIER is a new architecture for the forwarding of multicast data BIER is a multicast forwarding architecture that does not require
packets without requiring per-flow state inside the network. This per-flow state inside the network yet still provides optimal
document describes how the existing BIER encapsulation specified in replication. This document describes how the existing BIER
RFC 8296 works in an IPv6 non-MPLS network, referred to as BIERin6. encapsulation specified in RFC 8296 works in a non-MPLS IPv6 network,
Specifically, like in an IPv4 network, BIER can work over L2 links which is referred to as BIERin6. Specifically, like in an IPv4
directly or over tunnels. In case of IPv6 tunneling, a new IP "Next network, BIER can work over L2 links directly or over tunnels. In
Header" type is to be assigned for BIER. case of IPv6 tunneling, a new IP "Next Header" type is to be assigned
for BIER.
Requirements Language Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
Status of This Memo Status of This Memo
skipping to change at page 2, line 10 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 10 July 2022. This Internet-Draft will expire on 7 August 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 (https://trustee.ietf.org/ Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document. license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
skipping to change at page 2, line 33 skipping to change at page 2, line 33
described in Section 4.e of the Trust Legal Provisions and are described in Section 4.e of the Trust Legal Provisions and are
provided without warranty as described in the Revised BSD License. provided without warranty as described in the Revised 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 1.2. Considerations of Requirements for BIER in IPv6
Networks . . . . . . . . . . . . . . . . . . . . . . . . 4 Networks . . . . . . . . . . . . . . . . . . . . . . . . 4
2. IPv6 Header . . . . . . . . . . . . . . . . . . . . . . . . . 5 2. IPv6 Header . . . . . . . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . . . . . . . 8 7. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 7
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 8 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
8.1. Normative References . . . . . . . . . . . . . . . . . . 8 8.1. Normative References . . . . . . . . . . . . . . . . . . 7
8.2. Informative References . . . . . . . . . . . . . . . . . 9 8.2. Informative References . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11
1. Introduction 1. Introduction
BIER [RFC8279] is a new architecture for the forwarding of multicast BIER [RFC8279] is a multicast forwarding architecture that does not
data packets. It provides optimal forwarding through a "multicast require per-flow state inside the network yet still provides optimal
domain" and it does not precondition construction of a multicast replication.
distribution tree, nor does it require intermediate nodes to maintain
any per-flow state.
This document specifies non-MPLS BIER forwarding in an IPv6 [RFC8200]
environment, referred to as BIERin6, using non-MPLS BIER
encapsulation specified in [RFC8296].
MPLS BIER forwarding in IPv6 is outside the scope of this document. BIER forwarding with MPLS is IPv4/IPv6 agnostic. This document
describes how BIER works in a non-MPLS IPv6 [RFC8200] environment
using non-MPLS BIER encapsulation [RFC8296], with optional procedures
specified for IPv6 specific features.
This document uses terminology defined in [RFC8279] and [RFC8296]. This document uses terminology defined in [RFC8279] and [RFC8296].
1.1. BIER over L2/Tunnels 1.1. BIER over L2/Tunnels
[RFC8296] defines the BIER encapsulation format in MPLS and non-MPLS [RFC8296] defines the BIER encapsulation format for MPLS and non-MPLS
environment. In case of non-MPLS environment, a BIER packet is the data planes. With a non-MPLS data plane, a BIER packet is the
payload of an "outer" encapsulation, which has a "next header" payload of an "outer" encapsulation, which could be a L2 link or a
codepoint that is set to a value that means "non-MPLS BIER". This tunnel. The outer encapsulation has a "next header" field that is
"BIER over L2/Tunnel" model can be used as is in an IPv6 non-mpls set to a value for "non-MPLS BIER". This "BIER over L2/Tunnel" model
environment, and is referred to as BIERin6. can be used as is in an IPv6 non-mpls environment, and is referred to
as BIERin6.
If a BFR needs to tunnel BIER packets to another BFR, e.g. per If a BFR needs to tunnel BIER packets to another BFR, e.g. per
[RFC8279] Section 6.9, while any type of tunnel will work, for best [RFC8279] Section 6.9, while any type of tunnel will work, for best
efficiency native IPv6 encapsulation can be used with the destination efficiency native IPv6 encapsulation can be used with the destination
address being the downstream BFR and the Next Header field set to a address being the downstream BFR and the Next Header field set to a
to-be-assigned value for "non-MPLS BIER". to-be-assigned value for BIER.
+---------------+------------------------ +---------------+------------------------
| IPv6 header | BIER header + data | IPv6 header | BIER header + data
| | | |
| 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:
* An operator mandates all traffic to be carried in IPv6. * An operator mandates all traffic to be carried in IPv6.
* 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 IPv6 Home
like [RFC7368] where high throughput multicast forwarding Networking [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
skipping to change at page 4, line 26 skipping to change at page 4, line 26
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.
* Generic Fragmentation/ESP * Generic Fragmentation/ESP
[I-D.zzhang-intarea-generic-delivery-functions]: a BFIR does [I-D.zzhang-intarea-generic-delivery-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. The
details are outside the scope of this document.
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):
* 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
skipping to change at page 5, line 5 skipping to change at page 5, line 9
srv6-services] (instead of an entire IPv6 header) is added between srv6-services] (instead of an entire IPv6 header) is added between
the BIER header and original payload. The service SID serves the the BIER header and original payload. The service SID serves the
same purpose as a service-indicating MPLS label does. For same purpose as a service-indicating MPLS label does. For
example, an End.DT2/4/6 service SID could be used to route the example, an End.DT2/4/6 service SID could be used to route the
original payload in a corresponding VRF. original payload in a corresponding VRF.
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
20-bit IPv6 Flow Label (instead of using local 5-tuple input key to a 20-bit IPv6 Flow Label so that routers along the tunnel can do ECMP
hash function to locally generate the stateless 20-bit flow label) so based on Flow Labels (instead of hashing based on 5-tuple of an IP
that routers along the tunnel can do ECMP based on Flow Labels. For packet). For a router along the tunnel doing deep packet inspection
a router along the tunnel doing deep packet inspection for ECMP for ECMP purpose, if it understands BIER header it can go past the
purpose, if it understands BIER header it can go past the BIER header BIER header to look for the 5-tuple input key to a hash function.
to look for the 5-tuple input key to a hash function, otherwise it Otherwise, it stops at the BIER header. In either case the router
stops at the BIER header. In either case the router will not mistake will not mistake the BIER header as an IP header so no misordering
the BIER header as an IP header so no misordering should happen. 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:
* BIER OAM specified in [I-D.ietf-bier-ping] * BIER OAM specified in [I-D.ietf-bier-ping]
skipping to change at page 5, line 35 skipping to change at page 5, line 39
* BIER Performance Measurement specified in [I-D.ietf-bier-pmmm-oam] * BIER Performance Measurement specified in [I-D.ietf-bier-pmmm-oam]
* 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]
* 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 If IPv6 encapsulation is used to tunnel BIER packets (whether to a
Header field in the IPv6 Header (if there are no extension headers), direct or indirect BIER neighbor), the Next Header field in the IPv6
or the Next Header field in the last extension header is set to TBD, Header (if there are no extension headers), or the Next Header field
indicating that the payload is a BIER packet. in the last extension header is set to TBD, 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
router's outgoing interface, the source destination address SHOULD be router's outgoing interface. The source destination address SHOULD
this router's link-local address on the outgoing interface, and the be this router's link-local address on the outgoing interface, and
IPv6 TTL MUST be set to 1. Otherwise, the destination address SHOULD the TTL MUST be set to 1.
be the BIER prefix of the BFR neighbor, the source address SHOULD be
this router's BIER prefix, and the TTL MUST be large enough to get If the neighbor is not directly connected, the destination address
the packet to the BFR neighbor. SHOULD be the BIER prefix of the BFR neighbor. The source address
SHOULD be this router's BIER prefix, and the TTL MUST be large enough
to get the packet to the BFR neighbor.
The "Flow label" field in the IPv6 packet SHOULD be copied from the The "Flow label" field in the IPv6 packet SHOULD be copied from the
entropy field in the BIER encapsulation. entropy field in the BIER encapsulation.
2.1. IPv6 Options Considerations
For directly connected BIER routers, IPv6 Hop-by-Hop or Destination
options are irrelevant and SHOULD NOT be inserted by BFIR on the
BIERin6 packet. In this case IPv6 header, Next Header field should
be set to TBD. Any IPv6 packet arriving on BFRs and BFERs, with
multiple extension header where the last extension header has a Next
Header field set to TBD, SHOULD be discard and the node should
transmit an ICMP Parameter Problem message to the source of the
packet (BFIR) with an ICMP code value of TBD10 ('invalid options for
BIERin6').
This also indicates that for disjoint BIER routers using IPv6
encapsulation, there SHOULD NOT be any IPv6 Hop-by-Hop or Destination
options be present in a BIERin6 packet. In this case, if additional
traffic engineering is required, IPv6 tunneling (i.e. BIERin6 over
SRv6) can be implemented.
3. BIER Header 3. BIER Header
The BIER header MUST be encoded per Section 2.2 of [RFC8296]. The BIER header MUST be encoded per Section 2.2 of [RFC8296].
The BIFT-id is either encoded per The BIFT-id is either encoded per
[I-D.ietf-bier-non-mpls-bift-encoding] or per advertised by BFRs, as [I-D.ietf-bier-non-mpls-bift-encoding] or per advertised by BFRs, as
specified in [I-D.ietf-bier-lsr-ethernet-extensions]. specified in [I-D.ietf-bier-lsr-ethernet-extensions].
4. IPv6 Encapsulation Advertisement 4. IPv6 Encapsulation Advertisement
When IPv6 encapsulation is not required between directly connected When IPv6 encapsulation is not required between directly connected
BFRs, no signaling in addition to that specified in BFRs, no signaling in addition to that specified in
[I-D.ietf-bier-lsr-ethernet-extensions] is needed. [I-D.ietf-bier-lsr-ethernet-extensions] is needed.
Otherwise, a node that requires IPv6 encapsulation MUST advertise the Otherwise, a node that requires IPv6 encapsulation MUST advertise the
BIER IPv6 transportation sub-sub-sub-TLV/sub-sub-TLV according to BIER IPv6 encapsulation sub-sub-sub-TLV/sub-sub-TLV according to
local configuration or policy in the BIER domain to request other local configuration or policy in the BIER domain to request other
BFRs to always use IPv6 encapsulation. BFRs to always use IPv6 encapsulation.
In presence of multiple encapsulation possibilities hop-by-hop it is
a matter of local policy which encapsulation is imposed and the
receiving router MUST accept all encapsulations that it advertised.
4.1. Format 4.1. Format
The BIER IPv6 transportation is a new sub-sub-TLV of BIER Ethernet The BIER IPv6 Encapsulation is a new sub-sub-TLV of OSPFv3 BIER
Encapsulation sub-TLV defined in OSPFv3, and a new sub-sub-sub-TLV of Ethernet Encapsulation sub-TLV, and a new sub-sub-sub-TLV of ISIS
BIER Ethernet Encapsulation sub-sub-TLV defined in ISIS, as per BIER Ethernet Encapsulation sub-sub-TLV 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
* Type: For OSPF, value TBD1 (prefer 1) is used to indicate it is * Type: For OSPF, value TBD1 indicates it is the IPv6 Encapsulation
the IPv6 transportation sub-TLV. For ISIS, value TBD2 (prefer 1) sub-TLV. For ISIS, value TBD2 indicates it is the IPv6
is used to indicate it is the IPv6 transportation sub-sub-TLV. encapsulation sub-sub-TLV.
* 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 encapsulation 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
IANA is requested to assign a new "BIER" type for "Next Header" in IANA is requested to assign a "BIER" type for "Next Header" in the
the "Assigned Internet Protocol Numbers" registry. "Assigned Internet Protocol Numbers" registry.
IANA is requested to assign a new "BIERin6" type for "invalid
options" in the "ICMP code value" registry.
IANA is requested to assign a new "BIER IPv6 transportation Sub-sub- IANA is requested to assign a "BIER IPv6 encapsulation Sub-sub-TLV"
TLV" type in the "OSPFv3 BIER Ethernet Encapsulation sub-TLV" type in the "OSPFv3 BIER Ethernet Encapsulation sub-TLV" Registry.
Registry.
IANA is requested to set up a new "BIER IPv6 transportation Sub-sub- IANA is requested to assign a "BIER IPv6 encapsulation Sub-sub-sub-
sub-TLV" type in the "IS-IS BIER Ethernet Encapsulation sub-sub-TLV" TLV" type in the "IS-IS BIER Ethernet Encapsulation sub-sub-TLV"
Registry. Registry.
IANA is requested to allocate a new value "SRv6 Service" from "BIER IANA is requested to allocate a value "SRv6 Service" from "BIER Next
Next Protocol Identifiers" registry to indicate that BIER payload Protocol Identifiers" registry to indicate that BIER payload starts
starts with an SRv6 Service SID. with an SRv6 Service SID.
6. Security Considerations 6. Security Considerations
General IPv6 and BIER security considerations apply. General IPv6 and BIER security considerations apply.
7. Acknowledgement 7. Acknowledgement
The authors would like to thank Tony Przygienda, Nagendra Kumar for The authors would like to thank Tony Przygienda, Nagendra Kumar for
their review and valuable comments. their review and valuable comments.
8. References 8. References
8.1. Normative References 8.1. Normative References
[I-D.ietf-bess-srv6-services] [I-D.ietf-bess-srv6-services]
Dawra, G., Filsfils, C., Talaulikar, K., Raszuk, R., Dawra, G., Filsfils, C., Talaulikar, K., Raszuk, R.,
Decraene, B., Zhuang, S., and J. Rabadan, "SRv6 BGP based Decraene, B., Zhuang, S., and J. Rabadan, "SRv6 BGP based
Overlay Services", Work in Progress, Internet-Draft, Overlay Services", Work in Progress, Internet-Draft,
draft-ietf-bess-srv6-services-08, 10 November 2021, draft-ietf-bess-srv6-services-09, 26 January 2022,
<https://www.ietf.org/archive/id/draft-ietf-bess-srv6- <https://www.ietf.org/archive/id/draft-ietf-bess-srv6-
services-08.txt>. services-09.txt>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC6437] Amante, S., Carpenter, B., Jiang, S., and J. Rajahalme, [RFC6437] Amante, S., Carpenter, B., Jiang, S., and J. Rajahalme,
"IPv6 Flow Label Specification", RFC 6437, "IPv6 Flow Label Specification", RFC 6437,
DOI 10.17487/RFC6437, November 2011, DOI 10.17487/RFC6437, November 2011,
<https://www.rfc-editor.org/info/rfc6437>. <https://www.rfc-editor.org/info/rfc6437>.
skipping to change at page 9, line 16 skipping to change at page 8, line 47
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", Work in Progress, Calculation Algorithm and Constraints", Work in Progress,
Internet-Draft, draft-ietf-bier-bar-ipa-09, 24 October Internet-Draft, draft-ietf-bier-bar-ipa-10, 1 February
2021, <https://www.ietf.org/archive/id/draft-ietf-bier- 2022, <https://www.ietf.org/archive/id/draft-ietf-bier-
bar-ipa-09.txt>. bar-ipa-10.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",
Work in Progress, Internet-Draft, draft-ietf-bier-bfd-01, Work in Progress, Internet-Draft, draft-ietf-bier-bfd-01,
8 April 2021, <https://www.ietf.org/archive/id/draft-ietf- 8 April 2021, <https://www.ietf.org/archive/id/draft-ietf-
bier-bfd-01.txt>. 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", Work in Progress, Przygienda, "BGP Extensions for BIER", Work in Progress,
skipping to change at page 9, line 45 skipping to change at page 9, line 30
Zhu, Y., Mishra, G., and Z. Zhang, "BIER IPv6 Zhu, Y., Mishra, G., and Z. Zhang, "BIER IPv6
Requirements", Work in Progress, Internet-Draft, draft- Requirements", Work in Progress, Internet-Draft, draft-
ietf-bier-ipv6-requirements-09, 28 September 2020, ietf-bier-ipv6-requirements-09, 28 September 2020,
<https://www.ietf.org/archive/id/draft-ietf-bier-ipv6- <https://www.ietf.org/archive/id/draft-ietf-bier-ipv6-
requirements-09.txt>. 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",
Work in Progress, Internet-Draft, draft-ietf-bier-lsr- Work in Progress, Internet-Draft, draft-ietf-bier-lsr-
ethernet-extensions-02, 2 December 2020, ethernet-extensions-03, 30 January 2022,
<https://www.ietf.org/archive/id/draft-ietf-bier-lsr- <https://www.ietf.org/archive/id/draft-ietf-bier-lsr-
ethernet-extensions-02.txt>. ethernet-extensions-03.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", Work in Progress, Internet-Draft, BIER Encapsulation", Work in Progress, Internet-Draft,
draft-ietf-bier-non-mpls-bift-encoding-04, 30 May 2021, draft-ietf-bier-non-mpls-bift-encoding-04, 30 May 2021,
<https://www.ietf.org/archive/id/draft-ietf-bier-non-mpls- <https://www.ietf.org/archive/id/draft-ietf-bier-non-mpls-
bift-encoding-04.txt>. bift-encoding-04.txt>.
[I-D.ietf-bier-ospfv3-extensions] [I-D.ietf-bier-ospfv3-extensions]
skipping to change at page 10, line 49 skipping to change at page 10, line 34
Zhang, Z., Wu, B., Zhang, Z., Wijnands, I., Liu, Y., and Zhang, Z., Wu, B., Zhang, Z., Wijnands, I., Liu, Y., and
H. Bidgoli, "BIER Prefix Redistribute", Work in Progress, H. Bidgoli, "BIER Prefix Redistribute", Work in Progress,
Internet-Draft, draft-ietf-bier-prefix-redistribute-01, 23 Internet-Draft, draft-ietf-bier-prefix-redistribute-01, 23
December 2021, <https://www.ietf.org/archive/id/draft- December 2021, <https://www.ietf.org/archive/id/draft-
ietf-bier-prefix-redistribute-01.txt>. ietf-bier-prefix-redistribute-01.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", Work in Encapsulation for In-situ OAM (IOAM) Data", Work in
Progress, Internet-Draft, draft-xzlnp-bier-ioam-02, 11 Progress, Internet-Draft, draft-xzlnp-bier-ioam-03, 12
July 2021, <https://www.ietf.org/archive/id/draft-xzlnp- January 2022, <https://www.ietf.org/archive/id/draft-
bier-ioam-02.txt>. xzlnp-bier-ioam-03.txt>.
[I-D.zhang-bier-babel-extensions] [I-D.zhang-bier-babel-extensions]
Zhang, Z. and T. Przygienda, "BIER in BABEL", Work in Zhang, Z. and T. Przygienda, "BIER in BABEL", Work in
Progress, Internet-Draft, draft-zhang-bier-babel- Progress, Internet-Draft, draft-zhang-bier-babel-
extensions-06, 7 November 2021, extensions-06, 7 November 2021,
<https://www.ietf.org/archive/id/draft-zhang-bier-babel- <https://www.ietf.org/archive/id/draft-zhang-bier-babel-
extensions-06.txt>. extensions-06.txt>.
[I-D.zzhang-intarea-generic-delivery-functions] [I-D.zzhang-intarea-generic-delivery-functions]
Zhang, Z., Bonica, R., Kompella, K., and G. Mirsky, Zhang, Z., Bonica, R., Kompella, K., and G. Mirsky,
 End of changes. 32 change blocks. 
107 lines changed or deleted 83 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/