draft-ietf-pim-bfd-p2mp-use-case-03.txt   draft-ietf-pim-bfd-p2mp-use-case-04.txt 
PIM Working Group G. Mirsky PIM Working Group G. Mirsky
Internet-Draft ZTE Corp. Internet-Draft ZTE Corp.
Intended status: Standards Track J. Xiaoli Intended status: Standards Track J. Xiaoli
Expires: July 25, 2020 ZTE Corporation Expires: January 26, 2021 ZTE Corporation
January 22, 2020 July 25, 2020
Bidirectional Forwarding Detection (BFD) for Multi-point Networks and Bidirectional Forwarding Detection (BFD) for Multi-point Networks and
Protocol Independent Multicast - Sparse Mode (PIM-SM) Use Case Protocol Independent Multicast - Sparse Mode (PIM-SM) Use Case
draft-ietf-pim-bfd-p2mp-use-case-03 draft-ietf-pim-bfd-p2mp-use-case-04
Abstract Abstract
This document discusses the use of Bidirectional Forwarding Detection This document discusses the use of Bidirectional Forwarding Detection
(BFD) for multi-point networks to provide nodes that participate in (BFD) for multi-point networks to provide nodes that participate in
Protocol Independent Multicast - Sparse Mode (PIM-SM) with the sub- Protocol Independent Multicast - Sparse Mode (PIM-SM) with the sub-
second convergence. Optional extension to PIM-SM Hello, as specified second convergence. Optional extension to PIM-SM Hello, as specified
in RFC 7761, to bootstrap point-to-multipoint BFD session. also in RFC 7761, to bootstrap point-to-multipoint BFD session. also
defined in this document. defined in this document.
skipping to change at page 1, line 37 skipping to change at page 1, line 37
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 July 25, 2020. This Internet-Draft will expire on January 26, 2021.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 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 5, line 34 skipping to change at page 5, line 34
start DR Election process as specified in Section 4.3.2 [RFC7761] or start DR Election process as specified in Section 4.3.2 [RFC7761] or
Section 4.1 [I-D.ietf-pim-dr-improvement] respectively. Section 4.1 [I-D.ietf-pim-dr-improvement] respectively.
If the head ceased to include BFD TLV in its PIM-Hello message, tails If the head ceased to include BFD TLV in its PIM-Hello message, tails
MUST close the corresponding MultipointTail BFD session. Thus the MUST close the corresponding MultipointTail BFD session. Thus the
tail stops using BFD to monitor the head and reverts to the tail stops using BFD to monitor the head and reverts to the
procedures defined in [RFC7761] and [I-D.ietf-pim-dr-improvement]. procedures defined in [RFC7761] and [I-D.ietf-pim-dr-improvement].
3.2. P2MP BFD in PIM DR Load Balancing 3.2. P2MP BFD in PIM DR Load Balancing
[I-D.ietf-pim-drlb] defined the modification, Designated Router Load [RFC8775] defined the modification, Designated Router Load Balancing
Balancing (DRLB), to the PIM-SM protocol that allows for distribution (DRLB), to the PIM-SM protocol that allows for distribution of PIM-SM
of PIM-SM DR responsibilities on a multi-access network segment. DR responsibilities on a multi-access network segment. [RFC8775]
[I-D.ietf-pim-drlb] introduced the new PIM Hello options - Load introduced the new PIM Hello options - Load Balancing Capability
Balancing Capability (DRLB-Cap) and DR Load Balancing List (DRLB- (DRLB-Cap) and DR Load Balancing List (DRLB-List). PIM router that
List). PIM router that includes DRLB-Cap Hello Option MAY include includes DRLB-Cap Hello Option MAY include BFD Discriminator PIM
BFD Discriminator PIM Hello Option (Figure 1). That router MUST Hello Option (Figure 1). That router MUST create a BFD session and
create a BFD session and set itself as MultipointHead [RFC8562]. The set itself as MultipointHead [RFC8562]. The router MUST set
router MUST set bfd.SessionState in the MultipointHead session to bfd.SessionState in the MultipointHead session to Down. If a PIM
Down. If a PIM router that includes BFD Discriminator Option in its router that includes BFD Discriminator Option in its Hello finds its
Hello finds its address in DRLB-List PIM Hello Option as Group address in DRLB-List PIM Hello Option as Group Designated Router
Designated Router (GDR) Candidate for the first time, the router MUST (GDR) Candidate for the first time, the router MUST set
set bfd.SessionState to Up and start periodically transmit BFD bfd.SessionState to Up and start periodically transmit BFD control
control messages. If the PIM router that was GDR Candidate doesn't messages. If the PIM router that was GDR Candidate doesn't find its
find its address in the most recent DRLB-List Option, the router MUST address in the most recent DRLB-List Option, the router MUST set
set bfd.SessionState to Down and cease transmitting BFD control bfd.SessionState to Down and cease transmitting BFD control messages.
messages. For each GDR Candidate that includes BFD Discriminator For each GDR Candidate that includes BFD Discriminator Option in its
Option in its PIM Hello, PIM DR creates a MultipointTail session PIM Hello, PIM DR creates a MultipointTail session [RFC8562]. PIM DR
demultiplexes BFD sessions based on the value in My Discriminator
[RFC8562]. PIM DR demultiplexes BFD sessions based on the value in field and the source IP address. If PIM DR detects a failure of one
My Discriminator field and the source IP address. If PIM DR detects of the sessions, it MUST remove that router from the GDR Candidate
a failure of one of the sessions, it MUST remove that router from the list and immediately transmit a new DRLB-List Option.
GDR Candidate list and immediately transmit a new DRLB-List Option.
3.3. Multipoint BFD Encapsulation 3.3. Multipoint BFD Encapsulation
The MultipointHead of p2mp BFD session when transmitting BFD control The MultipointHead of p2mp BFD session when transmitting BFD control
packet: packet:
MUST set TTL value to 1; MUST set TTL value to 1;
SHOULD use group address ALL-PIM-ROUTERS ('224.0.0.13' for IPv4 SHOULD use group address ALL-PIM-ROUTERS ('224.0.0.13' for IPv4
and 'ff02::d' for IPv6) as destination IP address and 'ff02::d' for IPv6) as destination IP address
skipping to change at page 7, line 14 skipping to change at page 7, line 14
7. References 7. References
7.1. Normative References 7.1. Normative References
[I-D.ietf-pim-dr-improvement] [I-D.ietf-pim-dr-improvement]
Zhang, Z., hu, f., Xu, B., and m. mishra, "PIM DR Zhang, Z., hu, f., Xu, B., and m. mishra, "PIM DR
Improvement", draft-ietf-pim-dr-improvement-09 (work in Improvement", draft-ietf-pim-dr-improvement-09 (work in
progress), October 2019. progress), October 2019.
[I-D.ietf-pim-drlb]
Cai, Y., Ou, H., Vallepalli, S., mishra, m., Venaas, S.,
and A. Green, "PIM Designated Router Load Balancing",
draft-ietf-pim-drlb-15 (work in progress), January 2020.
[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>.
[RFC5881] Katz, D. and D. Ward, "Bidirectional Forwarding Detection [RFC5881] Katz, D. and D. Ward, "Bidirectional Forwarding Detection
skipping to change at page 8, line 5 skipping to change at page 7, line 47
[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>.
[RFC8562] Katz, D., Ward, D., Pallagatti, S., Ed., and G. Mirsky, [RFC8562] Katz, D., Ward, D., Pallagatti, S., Ed., and G. Mirsky,
Ed., "Bidirectional Forwarding Detection (BFD) for Ed., "Bidirectional Forwarding Detection (BFD) for
Multipoint Networks", RFC 8562, DOI 10.17487/RFC8562, Multipoint Networks", RFC 8562, DOI 10.17487/RFC8562,
April 2019, <https://www.rfc-editor.org/info/rfc8562>. April 2019, <https://www.rfc-editor.org/info/rfc8562>.
[RFC8775] Cai, Y., Ou, H., Vallepalli, S., Mishra, M., Venaas, S.,
and A. Green, "PIM Designated Router Load Balancing",
RFC 8775, DOI 10.17487/RFC8775, April 2020,
<https://www.rfc-editor.org/info/rfc8775>.
7.2. Informative References 7.2. Informative References
[I-D.mankamana-pim-bdr] [I-D.mankamana-pim-bdr]
mishra, m., Goh, J., and G. Mishra, "PIM Backup Designated mishra, m., Goh, J., and G. Mishra, "PIM Backup Designated
Router Procedure", draft-mankamana-pim-bdr-03 (work in Router Procedure", draft-mankamana-pim-bdr-04 (work in
progress), October 2019. progress), April 2020.
Authors' Addresses Authors' Addresses
Greg Mirsky Greg Mirsky
ZTE Corp. ZTE Corp.
Email: gregimirsky@gmail.com Email: gregimirsky@gmail.com
Ji Xiaoli Ji Xiaoli
ZTE Corporation ZTE Corporation
 End of changes. 7 change blocks. 
34 lines changed or deleted 33 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/