< draft-hu-bier-bfd-03.txt   draft-hu-bier-bfd-04.txt >
BIER WG Quan Xiong BIER WG Quan Xiong
Internet-Draft Greg Mirsky Internet-Draft Greg Mirsky
Intended status: Standards Track Fangwei Hu Intended status: Standards Track ZTE Corporation
Expires: September 2, 2019 ZTE Corporation Expires: January 4, 2020 Fangwei Hu
Individual
Chang Liu Chang Liu
China Unicom China Unicom
March 1, 2019 July 3, 2019
BIER BFD BIER BFD
draft-hu-bier-bfd-03.txt draft-hu-bier-bfd-04.txt
Abstract Abstract
Point to multipoint (P2MP) BFD is designed to verify multipoint Point to multipoint (P2MP) BFD is designed to verify multipoint
connectivity. This document specifies the application of P2MP BFD in connectivity. This document specifies the application of P2MP BFD in
BIER network. BIER network.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 35 skipping to change at page 1, line 36
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 2, 2019. This Internet-Draft will expire on January 4, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 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 14 skipping to change at page 2, line 14
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
2.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 2.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
2.2. Requirements Language . . . . . . . . . . . . . . . . . . 3 2.2. Requirements Language . . . . . . . . . . . . . . . . . . 3
3. BIER BFD Encapsulation . . . . . . . . . . . . . . . . . . . 3 3. BIER BFD Encapsulation . . . . . . . . . . . . . . . . . . . 3
4. Bootstrapping BIER BFD . . . . . . . . . . . . . . . . . . . 3 4. BIER BFD Session Bootstrapping . . . . . . . . . . . . . . . 3
4.1. BIER OAM Ping Bootstrap . . . . . . . . . . . . . . . . . 3 4.1. BIER OAM Bootstrapping . . . . . . . . . . . . . . . . . 3
4.2. IGP protocol Bootstrap . . . . . . . . . . . . . . . . . 4 4.2. IGP protocol Bootstrapping . . . . . . . . . . . . . . . 4
4.2.1. IS-IS extension for BIER BFD . . . . . . . . . . . . 4 4.2.1. IS-IS extension for BIER BFD . . . . . . . . . . . . 4
4.2.2. OSPF extension for BIER BFD . . . . . . . . . . . . . 5 4.2.2. OSPF extension for BIER BFD . . . . . . . . . . . . . 5
5. Discriminators and Packet Demultiplexing . . . . . . . . . . 5 5. Discriminators and Packet Demultiplexing . . . . . . . . . . 6
6. Active Tail in BIER BFD . . . . . . . . . . . . . . . . . . . 5 6. Active Tail in BIER BFD . . . . . . . . . . . . . . . . . . . 6
7. Security Considerations . . . . . . . . . . . . . . . . . . . 6 7. Security Considerations . . . . . . . . . . . . . . . . . . . 7
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
10.1. Normative References . . . . . . . . . . . . . . . . . . 6 10.1. Normative References . . . . . . . . . . . . . . . . . . 7
10.2. Informative References . . . . . . . . . . . . . . . . . 7 10.2. Informative References . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction 1. Introduction
Bit Index Explicit Replication (BIER) [RFC8279] provides optimal Bit Index Explicit Replication (BIER) [RFC8279] provides forwarding
forwarding of multicast data packets through a multicast domain. It of multicast data packets through a multicast domain. It does so
does so without requiring any explicit tree-building protocol and without requiring any explicit tree-building protocol and without
without requiring intermediate nodes to maintain any per-flow state. requiring intermediate nodes to maintain any per-flow state.
BIER resilience use cases are described in
[I-D.xiong-bier-resilience] including End-to-End 1+1 and 1:1
Protection and the failure detection mechanisms MAY use P2MP BFD and
P2MP active tail detection method respectively.
[I-D.ietf-bfd-multipoint] defines a method of using Bidirectional [RFC8562] defines a method of using Bidirectional Forwarding
Forwarding Detection(BFD) to monitor and detect unicast failures Detection (BFD) to monitor and detect unicast failures between the
between the sender (head) and one or more receivers (tails) in sender (head) and one or more receivers (tails) in multipoint or
multipoint or multicast networks. multicast networks. [RFC8563] describes active tail extensions to
[I-D.ietf-bfd-multipoint-active-tail] describes active tail the BFD protocol for multipoint networks.
extensions to the BFD protocol for multipoint networks.
This document describes the procedures for using such mode of BFD This document describes the procedures for using such mode of BFD
protocol to verify multipoint or multicast connectivity between a protocol to monitor connectivity between a multipoint sender, Bit-
multipoint sender (the "head", Bit-Forwarding Ingress Routers(BFIRs)) Forwarding Ingress Router (BFIR), and a set of one or more multipoint
and a set of one or more multipoint receivers (the"tails", Bit- receivers,Bit-Forwarding Egress Routers (BFERs). The BIER BFD only
Forwarding Egress Routers(BFERs)). The BIER BFD only supports the supports the unidirectional multicast. This document defines the use
unidirectional multicast. This document defines the use of P2MP BFD of P2MP BFD as per [RFC8562], and active tail as per [RFC8563] for
as per [I-D.ietf-bfd-multipoint], and active tail as per BIER-specific domain.
[I-D.ietf-bfd-multipoint-active-tail] for BIER-specific domain.
2. Conventions used in this document 2. Conventions used in this document
2.1. Terminology 2.1. Terminology
This document uses the acronyms defined in [RFC8279] along with the This document uses the acronyms defined in [RFC8279] along with the
following: following:
BFD: Bidirectional Forwarding Detection. BFD: Bidirectional Forwarding Detection.
skipping to change at page 3, line 33 skipping to change at page 3, line 30
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.
3. BIER BFD Encapsulation 3. BIER BFD Encapsulation
BIER BFD encapsulation uses the BIER OAM packet format defined in BIER BFD encapsulation uses the BIER OAM packet format defined in
[I-D.ietf-bier-ping]. The value of the Msg Type field MUST be set to [I-D.ietf-bier-ping]. The value of the Msg Type field MUST be set to
BIER BFD (TBD1 by IANA ). BFD Control packet, defined in Section 4 BIER BFD (TBD1 by IANA ). BFD Control Packet, defined in Section 4
[RFC5880] immediately follows the BIER OAM header. [RFC5880] immediately follows the BIER OAM header. The operation of
Multipoint BFD with the BFD Control Packet is described in [RFC8562].
4. Bootstrapping BIER BFD 4. BIER BFD Session Bootstrapping
4.1. BIER OAM Ping Bootstrap As defined in [RFC8562], BIER BFD session MAY be established to
monitor the state of the multipoint path. The BIER BFD session could
be created for each multipoint path and the set of BFERs over which
the BFIR wishes to run BIER BFD. The BFIR MUST advertise the BFD
Discriminator along with the corresponding multipoint path to the set
of BFERs. Bootstrapping a BIER BFD session MAY use BIER OAM message
section 4.1 or the control plane section 4.2.
The BIER OAM ping could be used for BIER BFD bootstrap. The BFIR The BIER BFD bootstrapping MUST be repeated when the value of this
sends the BIER OAM ping Echo request messages carring a BFD discriminator being changed.
4.1. BIER OAM Bootstrapping
The BIER OAM could be used for bootstrapping the BIER BFD session.
The BFIR sends the BIER OAM Echo request message carrying a BFD
discriminator TLV which immediately follows the Target SI-Bitstring discriminator TLV which immediately follows the Target SI-Bitstring
TLV (section 3.3.2 [I-D.ietf-bier-ping]) which MUST be included to TLV (section 3.3.2 [I-D.ietf-bier-ping]).
carry the set of BFER information (Sub-domain-id, Set ID, BS Len,
Bitstring) for the purpose of session establishment. The Target SI-Bitstring TLV MUST be used to carry the set of BFER
information (including Sub-domain-id, Set ID, BS Len, Bitstring) for
the purpose of session establishment.
The BFD discriminator TLV is a new TLV for BIER OAM TLV with the type The BFD discriminator TLV is a new TLV for BIER OAM TLV with the type
(TBD2 by IANA) and the length of 4. The value contains the 4-byte (TBD2 by IANA) and the length of 4. The value contains the 4-byte
local discriminator generated by BFIR for this session. local discriminator generated by BFIR for this session. This
discriminator MUST subsequently be used as the My Discriminator field
in the BIER BFD session packets sent by BFIR. The format is as
follows.
4.2. IGP protocol Bootstrap 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type=TBD2 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| My Discriminator |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: BFD discriminator TLV
4.2. IGP protocol Bootstrapping
An alternative option to bootstrap the BIER BFD is to advertise the An alternative option to bootstrap the BIER BFD is to advertise the
BFD information IGP protocol in control plane. This document defines BFD information in control plane. This document defines a new BIER
a new BIER BFD Sub-TLV carried in IS-IS and OSPF capaibility to BFD Sub-sub-TLV carried in IS-IS and OSPF protocol.
advertise My Discriminator for BFIR.
The BFIR generates the My Discriminator value for each multicast flow
and advertises it to the expecting BFERs which is indicated by the
Bitstring which is carried in BIER BFD sub-sub-TLV. The
corresponding BFERs SHOULD store the My Discriminator value for
packet Demultiplexing.
4.2.1. IS-IS extension for BIER BFD 4.2.1. IS-IS extension for BIER BFD
The new BIER BFD Sub-TLV is carried in the ISIS router capaiblity The new BIER BFD Sub-sub-TLV is carried within the BIER Info sub-TLV
TLV. The format is as follows. defined in [RFC8401]. The format is as follows.
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| My Discriminator | | My Discriminator |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| RESERVED | BIFT-id | | RESERVED | BIFT-id |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BitString (first 32 bits) ~ | BitString (first 32 bits) ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ ~ ~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ BitString (last 32 bits) | ~ BitString (last 32 bits) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: BIER BFD Sub-TLV for IS-IS extension Figure 2: BIER BFD Sub-sub-TLV for IS-IS extension
Type : TBD3 by IANA. Type: TBD3 by IANA.
Length : Length of the BIER BFD Sub-TLV for IS-IS extension, in Length: Length of the BIER BFD Sub-sub-TLV for IS-IS extension, in
bytes. bytes.
My Discriminator : A unique, nonzero discriminator value generated by My Discriminator: A unique, nonzero discriminator value generated by
BFIR for each multipoint path. BFIR for each multipoint path.
The BitString field carries the set of BFR-IDs of BFER(s) that the The BitString field carries the set of BFR-IDs of BFER(s) that the
BFIR expects to establish BIER BFD session. BFIR expects to establish BIER BFD session.
The BIFT-id represents a particular Bit Index Forwarding Table (BIFT) The BIFT-id represents a particular Bit Index Forwarding Table (BIFT)
as per [RFC8279]. as per [RFC8279].
4.2.2. OSPF extension for BIER BFD 4.2.2. OSPF extension for BIER BFD
The new BIER BFD Sub-TLV is carried in the Router Information Link The new BIER BFD Sub-TLV is a sub-TLV of the BIER Sub-TLV defined in
State Advertisement (LSA). The format is as follows. [RFC8444]. The format is as follows.
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| My Discriminator | | My Discriminator |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| RESERVED | BIFT-id | | RESERVED | BIFT-id |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BitString (first 32 bits) ~ | BitString (first 32 bits) ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ ~ ~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ BitString (last 32 bits) | ~ BitString (last 32 bits) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2: BIER BFD Sub-TLV for OSPF extension Figure 3: BIER BFD Sub-TLV for OSPF extension
Type : TBD4 by IANA. Type: TBD4 by IANA.
Length : Length of the BIER BFD Sub-TLV for OSPF extension, in bytes. Length: Length of the BIER BFD Sub-TLV for OSPF extension, in bytes.
Other fields in BIER BFD Sub-TLV is the same with section 4.2.1. Other fields in BIER BFD Sub-TLV is the same with section 4.2.1.
5. Discriminators and Packet Demultiplexing 5. Discriminators and Packet Demultiplexing
The tail(BFER) demultiplexes incoming BFD packets based on a As defined in [RFC8562], the BFIR sends BFD Control packets over the
combination of the source address and My discriminator as specified multipoint path via the BIER BFD session with My Discriminator set to
in [I-D.ietf-bfd-multipoint]. The source address is BFIR-id and BIER the value assigned by the BFIR and the value of the Your
MPLS Label (MPLS network) or BFIR-id and BIFT-id (Non-MPLS network) Discriminator set to zero. The set of BFERs MUST demultiplex BFD
for BIER BFD. packets based on a combination of the source address, My
Discriminator value. The source address is BFIR-id and BIER MPLS
Label (MPLS network) or BFIR-id and BIFT-id (Non-MPLS network) for
BIER BFD. The My Discriminator value is advertised in BIER BFD
bootstrapping using one of options described in section 4.
6. Active Tail in BIER BFD 6. Active Tail in BIER BFD
[I-D.ietf-bfd-multipoint-active-tail] defined an extension for [RFC8563] defined an extension for Multipoint BFD, which allows the
Multipoint BFD, which allows tails to notify the head of the lack of head to discover the state of a multicast distribution tree for any
multipoint connectivity. For BIER BFD in active tail mode, the BFIR sub-set of tails. For BIER BFD in active tail mode, the BFIR may
may learn the state and connectivity of the BFERs. As per learn the state and connectivity of the BFERs. As per [RFC8563], the
[I-D.ietf-bfd-multipoint-active-tail], the BFIR can send the Poll BFIR uses a combination of multicast Poll sequence messages and
sequence messages in combination with the unicast BFD over the unicast Poll messages. The unicast messages must be sent over the
monitored BFERs. path which is disjoint from the multicast distribution tree.
7. Security Considerations 7. Security Considerations
For BIER OAM packet procssing security considerations, see For BIER OAM packet procssing security considerations, see
[I-D.ietf-bier-ping]. [I-D.ietf-bier-ping].
For general multipoint BFD security considerations, see For general multipoint BFD security considerations, see [RFC8562].
[I-D.ietf-bfd-multipoint].
No additional security issues are raised in this document beyond No additional security issues are raised in this document beyond
those that exist in the referenced BFD documents. those that exist in the referenced BFD documents.
8. Acknowledgements 8. Acknowledgements
Authors would like to thank the comments and suggestions from Jeffrey Authors would like to thank the comments and suggestions from Sandy
(Zhaohui) Zhang, Donald Eastlake 3rd. Zhang, Jeffrey (Zhaohui) Zhang, Donald Eastlake 3rd.
9. IANA Considerations 9. IANA Considerations
IANA is requested to assign new type from the BIER OAM Message Type IANA is requested to assign new type from the BIER OAM Message Type
registry as follows: registry as follows:
+--------+-----------------------------+------------------+ +--------+---------------------------------+------------------+
| Value | Description | Reference | | Value | Description | Reference |
+--------+-----------------------------+------------------+ +--------+---------------------------------+------------------+
| TBD1 | BIER BFD | [this document] | | TBD1 | BIER BFD | [this document] |
| TBD2 | BFD discriminator TLV | [this document] | | TBD2 | BFD discriminator TLV | [this document] |
| TBD3 | BIER BFD Sub-TLV for IS-IS | [this document] | | TBD3 | BIER BFD Sub-sub-TLV for IS-IS | [this document] |
| TBD4 | BIER BFD Sub-TLV for OSPF | [this document] | | TBD4 | BIER BFD Sub-TLV for OSPF | [this document] |
+--------+-----------------------------+------------------+ +--------+---------------------------------+------------------+
Table 1 Table 1
10. References 10. References
10.1. Normative References 10.1. Normative References
[I-D.ietf-bfd-multipoint]
Katz, D., Ward, D., Networks, J., and G. Mirsky, "BFD for
Multipoint Networks", draft-ietf-bfd-multipoint-19 (work
in progress), December 2018.
[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", draft-ietf-bier-
ping-04 (work in progress), October 2018. ping-05 (work in progress), April 2019.
[I-D.xiong-bier-resilience]
Xiong, Q., hu, f., and G. Mirsky, "The Resilience for
BIER", draft-xiong-bier-resilience-01 (work in progress),
October 2018.
[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>.
[RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection [RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection
(BFD)", RFC 5880, DOI 10.17487/RFC5880, June 2010, (BFD)", RFC 5880, DOI 10.17487/RFC5880, June 2010,
<https://www.rfc-editor.org/info/rfc5880>. <https://www.rfc-editor.org/info/rfc5880>.
[RFC6213] Hopps, C. and L. Ginsberg, "IS-IS BFD-Enabled TLV",
RFC 6213, DOI 10.17487/RFC6213, April 2011,
<https://www.rfc-editor.org/info/rfc6213>.
[RFC6328] Eastlake 3rd, D., "IANA Considerations for Network Layer
Protocol Identifiers", BCP 164, RFC 6328,
DOI 10.17487/RFC6328, July 2011,
<https://www.rfc-editor.org/info/rfc6328>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8279] Wijnands, IJ., Ed., Rosen, E., Ed., Dolganow, A., [RFC8279] Wijnands, IJ., Ed., Rosen, E., Ed., Dolganow, A.,
Przygienda, T., and S. Aldrin, "Multicast Using Bit Index Przygienda, T., and S. Aldrin, "Multicast Using Bit Index
Explicit Replication (BIER)", RFC 8279, Explicit Replication (BIER)", RFC 8279,
DOI 10.17487/RFC8279, November 2017, DOI 10.17487/RFC8279, November 2017,
<https://www.rfc-editor.org/info/rfc8279>. <https://www.rfc-editor.org/info/rfc8279>.
10.2. Informative References [RFC8401] Ginsberg, L., Ed., Przygienda, T., Aldrin, S., and Z.
Zhang, "Bit Index Explicit Replication (BIER) Support via
IS-IS", RFC 8401, DOI 10.17487/RFC8401, June 2018,
<https://www.rfc-editor.org/info/rfc8401>.
[I-D.ietf-bfd-multipoint-active-tail] [RFC8444] Psenak, P., Ed., Kumar, N., Wijnands, IJ., Dolganow, A.,
Katz, D., Ward, D., Networks, J., and G. Mirsky, "BFD Przygienda, T., Zhang, J., and S. Aldrin, "OSPFv2
Multipoint Active Tails.", draft-ietf-bfd-multipoint- Extensions for Bit Index Explicit Replication (BIER)",
active-tail-10 (work in progress), November 2018. RFC 8444, DOI 10.17487/RFC8444, November 2018,
<https://www.rfc-editor.org/info/rfc8444>.
[RFC8562] Katz, D., Ward, D., Pallagatti, S., Ed., and G. Mirsky,
Ed., "Bidirectional Forwarding Detection (BFD) for
Multipoint Networks", RFC 8562, DOI 10.17487/RFC8562,
April 2019, <https://www.rfc-editor.org/info/rfc8562>.
[RFC8563] Katz, D., Ward, D., Pallagatti, S., Ed., and G. Mirsky,
Ed., "Bidirectional Forwarding Detection (BFD) Multipoint
Active Tails", RFC 8563, DOI 10.17487/RFC8563, April 2019,
<https://www.rfc-editor.org/info/rfc8563>.
10.2. Informative References
[ISO9577] ISO/IEC TR 9577:1999,, "International Organization for [ISO9577] ISO/IEC TR 9577:1999,, "International Organization for
Standardization "Information technology - Standardization "Information technology -
Telecommunications and Information exchange between Telecommunications and Information exchange between
systems - Protocol identification in the network layer"", systems - Protocol identification in the network layer"",
1999. 1999.
Authors' Addresses Authors' Addresses
Quan Xiong Quan Xiong
ZTE Corporation ZTE Corporation
No.6 Huashi Park Rd No.6 Huashi Park Rd
Wuhan, Hubei 430223 Wuhan, Hubei 430223
China China
Phone: +86 27 83531060 Phone: +86 27 83531060
Email: xiong.quan@zte.com.cn Email: xiong.quan@zte.com.cn
Greg Mirsky Greg Mirsky
skipping to change at page 8, line 23 skipping to change at page 9, line 20
Phone: +86 27 83531060 Phone: +86 27 83531060
Email: xiong.quan@zte.com.cn Email: xiong.quan@zte.com.cn
Greg Mirsky Greg Mirsky
ZTE Corporation ZTE Corporation
USA USA
Email: gregimirsky@gmail.com Email: gregimirsky@gmail.com
Fangwei Hu Fangwei Hu
ZTE Corporation Individual
No.889 Bibo Rd
Shanghai 201203
China
Phone: +86 21 68896273 Email: hufwei@gmail.com
Email: hu.fangwei@zte.com.cn
Chang Liu Chang Liu
China Unicom China Unicom
No.9 Shouti Nanlu No.9 Shouti Nanlu
Beijing 100048 Beijing 100048
China China
Phone: +86-010-68799999-7294 Phone: +86-010-68799999-7294
Email: liuc131@chinaunicom.cn Email: liuc131@chinaunicom.cn
 End of changes. 39 change blocks. 
118 lines changed or deleted 140 lines changed or added

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