BFD for Multipoint Networks over Point-to-Multi-Point MPLS LSP
draft-mirsky-mpls-p2mp-bfd-07
|
| Document |
Type |
|
Active Internet-Draft (mpls WG)
|
|
Last updated |
|
2019-06-04
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
pdf
htmlized
bibtex
|
| Stream |
WG state
|
|
Candidate for WG Adoption
|
|
Document shepherd |
|
Loa Andersson
|
| IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
Loa Andersson <loa@pi.nu>
|
MPLS Working Group G. Mirsky
Internet-Draft ZTE Corp.
Intended status: Standards Track June 4, 2019
Expires: December 6, 2019
BFD for Multipoint Networks over Point-to-Multi-Point MPLS LSP
draft-mirsky-mpls-p2mp-bfd-07
Abstract
This document describes procedures for using Bidirectional Forwarding
Detection (BFD) for multipoint networks to detect data plane failures
in Multiprotocol Label Switching (MPLS) point-to-multipoint (p2mp)
Label Switched Paths (LSPs). It also describes the applicability of
LSP Ping, as in-band, and the control plane, as out-band, solutions
to bootstrap a BFD session in this environment.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on December 6, 2019.
Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
Mirsky Expires December 6, 2019 [Page 1]
Internet-Draft Multi-Point BFD over P2MP MPLS LSP June 2019
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions used in this document . . . . . . . . . . . . . . 2
2.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2
2.2. Requirements Language . . . . . . . . . . . . . . . . . . 3
3. Multipoint BFD Encapsulation . . . . . . . . . . . . . . . . 3
3.1. IP Encapsulation of Multipoint BFD . . . . . . . . . . . 3
3.2. Non-IP Encapsulation of Multipoint BFD . . . . . . . . . 4
4. Bootstrapping Multipoint BFD . . . . . . . . . . . . . . . . 4
4.1. LSP Ping . . . . . . . . . . . . . . . . . . . . . . . . 4
4.2. Control Plane . . . . . . . . . . . . . . . . . . . . . . 5
5. Security Considerations . . . . . . . . . . . . . . . . . . . 5
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
6.1. Multipoint BFD over MPLS LSP Associated Channel Type . . 6
6.2. Source MEP ID IP Address Type . . . . . . . . . . . . . . 6
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
8.1. Normative References . . . . . . . . . . . . . . . . . . 6
8.2. Informative References . . . . . . . . . . . . . . . . . 8
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction
[RFC8562] defines a method of using Bidirectional Detection (BFD)
[RFC5880] to monitor and detect unicast failures between the sender
(head) and one or more receivers (tails) in multipoint or multicast
networks. This document describes procedures for using such mode of
BFD protocol to detect data plane failures in Multiprotocol Label
Switching (MPLS) point-to-multipoint (p2mp) Label Switched Paths
(LSPs). The document also describes the applicability of out-band
solutions to bootstrap a BFD session in this environment.
2. Conventions used in this document
2.1. Terminology
MPLS: Multiprotocol Label Switching
LSP: Label Switched Path
BFD: Bidirectional Forwarding Detection
p2mp: Point-to-Multipoint
Mirsky Expires December 6, 2019 [Page 2]
Internet-Draft Multi-Point BFD over P2MP MPLS LSP June 2019
FEC: Forwarding Equivalence Class
G-ACh: Generic Associated Channel
ACH: Associated Channel Header
GAL: G-ACh Label
2.2. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP
Show full document text