draft-ietf-pim-bfd-p2mp-use-case-01.txt   draft-ietf-pim-bfd-p2mp-use-case-02.txt 
PIM Working Group G. Mirsky PIM Working Group G. Mirsky
Internet-Draft ZTE Corp. Internet-Draft ZTE Corp.
Updates: 7761 (if approved) J. Xiaoli Intended status: Standards Track J. Xiaoli
Intended status: Standards Track ZTE Corporation Expires: January 26, 2020 ZTE Corporation
Expires: December 19, 2019 June 17, 2019 July 25, 2019
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-01 draft-ietf-pim-bfd-p2mp-use-case-02
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 December 19, 2019. This Internet-Draft will expire on January 26, 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 18 skipping to change at page 2, line 18
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Conventions used in this document . . . . . . . . . . . . 3 1.1. Conventions used in this document . . . . . . . . . . . . 3
1.1.1. Terminology . . . . . . . . . . . . . . . . . . . . . 3 1.1.1. Terminology . . . . . . . . . . . . . . . . . . . . . 3
1.1.2. Requirements Language . . . . . . . . . . . . . . . . 3 1.1.2. Requirements Language . . . . . . . . . . . . . . . . 3
2. Problem Statement . . . . . . . . . . . . . . . . . . . . . . 3 2. Problem Statement . . . . . . . . . . . . . . . . . . . . . . 3
3. Applicability of p2mp BFD . . . . . . . . . . . . . . . . . . 3 3. Applicability of p2mp BFD . . . . . . . . . . . . . . . . . . 3
3.1. Multipoint BFD Encapsulation . . . . . . . . . . . . . . 5 3.1. Multipoint BFD Encapsulation . . . . . . . . . . . . . . 5
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
5. Security Considerations . . . . . . . . . . . . . . . . . . . 5 5. Security Considerations . . . . . . . . . . . . . . . . . . . 6
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 6 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 6
7. Normative References . . . . . . . . . . . . . . . . . . . . 6 7. Normative References . . . . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7
1. Introduction 1. Introduction
Faster convergence in the control plane, in general, is beneficial Faster convergence in the control plane, in general, is beneficial
and allows minimizing periods of traffic blackholing, transient and allows minimizing periods of traffic blackholing, transient
routing loops, and other scenarios that may negatively affect service routing loops, and other scenarios that may negatively affect service
data flow. That equally applies to unicast and multicast routing data flow. That equally applies to unicast and multicast routing
skipping to change at page 4, line 29 skipping to change at page 4, line 29
OptionLength value is always 4 OptionLength value is always 4
My Discriminator - My Discriminator value allocated by the root of My Discriminator - My Discriminator value allocated by the root of
the p2mp BFD session. the p2mp BFD session.
If PIM-SM routers that support this specification are configured to If PIM-SM routers that support this specification are configured to
use p2mp BFD for faster convergence, then the router to be monitored, use p2mp BFD for faster convergence, then the router to be monitored,
referred to as 'head', MUST create BFD session of type referred to as 'head', MUST create BFD session of type
MultipointHead, as defined in [RFC8562]. If the head doesn't support MultipointHead, as defined in [RFC8562]. If the head doesn't support
[I-D.ietf-pim-dr-improvement], then it MUST include BFD TLV in its [I-D.ietf-pim-dr-improvement], but, for example, uses procedures
PIM-Hello message. If the head uses extensions defined in defined in [I-D.mankamana-pim-bdr], then it MUST include BFD TLV in
its PIM-Hello message. If the head uses extensions defined in
[I-D.ietf-pim-dr-improvement], then DR MUST include BFD TLV in its [I-D.ietf-pim-dr-improvement], then DR MUST include BFD TLV in its
Hello message after the DR Address TLV. For a BDR it is RECOMMENDED Hello message. The DR Address TLV also MUST be included in the Hello
to include BFD TLV in its Hello message. If BDR includes BFD TLV, message. For a BDR it is RECOMMENDED to include BFD TLV in its Hello
then it MUST be after the BDR Address TLV. Then the head MUST begin message. If BDR includes BFD TLV, then the BDR Address TLV also MUST
periodic transmission of BFD control packets. Source IP address of be present in the Hello message. Then the head MUST begin periodic
the BFD control packet MUST be the same as the source IP address of transmission of BFD control packets. Source IP address of the BFD
the PIM-Hello with BFD TLV messages being transmitted by the head. control packet MUST be the same as the source IP address of the PIM-
The values of My Discriminator in the BFD control packet and My Hello with BFD TLV messages being transmitted by the head. The
values of My Discriminator in the BFD control packet and My
Discriminator field of the BFD TLV in PIM-Hello, transmitted by the Discriminator field of the BFD TLV in PIM-Hello, transmitted by the
head MUST be the same. When a PIM-SM router is configured to monitor head MUST be the same. When a PIM-SM router is configured to monitor
the head by using p2p BFD, referred to through this document as the head by using p2p BFD, referred to through this document as
'tail', receives PIM-Hello packet with BFD TLV it MAY create p2mp BFD 'tail', receives PIM-Hello packet with BFD TLV it MAY create p2mp BFD
session of type MultipointTail, as defined in [RFC8562]. session of type MultipointTail, as defined in [RFC8562].
Because p2mp BFD doesn't use the three-way handshake and the head Because p2mp BFD doesn't use the three-way handshake and the head
transmits BFD control packets with the value of Your Discriminator transmits BFD control packets with the value of Your Discriminator
field set to zero, [RFC8562] modified how a BFD system demultiplexes field set to zero, [RFC8562] modified how a BFD system demultiplexes
received BFD control packet. The tail demultiplexes p2mp BFD test received BFD control packet. The tail demultiplexes p2mp BFD test
skipping to change at page 6, line 21 skipping to change at page 6, line 26
Authors cannot say enough to express their appreciation of comments Authors cannot say enough to express their appreciation of comments
and suggestions we received from Stig Venaas. and suggestions we received from Stig Venaas.
7. Normative References 7. 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-07 (work in Improvement", draft-ietf-pim-dr-improvement-07 (work in
progress), January 2019. progress), January 2019.
[I-D.mankamana-pim-bdr]
mishra, m., "PIM Backup Designated Router Procedure",
draft-mankamana-pim-bdr-02 (work in progress), April 2019.
[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
 End of changes. 7 change blocks. 
15 lines changed or deleted 21 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/