Bidirectional Forwarding Detection (BFD) in Segment Routing Networks Using MPLS Dataplane
draft-mirsky-spring-bfd-10
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2020-04-26
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
pdf
htmlized (tools)
htmlized
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
SPRING Working Group G. Mirsky
Internet-Draft ZTE Corp.
Intended status: Standards Track J. Tantsura
Expires: October 28, 2020 Apstra, Inc.
I. Varlashkin
Google
M. Chen
Huawei
J. Wenying
CMCC
April 26, 2020
Bidirectional Forwarding Detection (BFD) in Segment Routing Networks
Using MPLS Dataplane
draft-mirsky-spring-bfd-10
Abstract
Segment Routing (SR) architecture leverages the paradigm of source
routing. It can be realized in the Multiprotocol Label Switching
(MPLS) network without any change to the data plane. A segment is
encoded as an MPLS label, and an ordered list of segments is encoded
as a stack of labels. Bidirectional Forwarding Detection (BFD) is
expected to monitor any existing path between systems. This document
defines how to use Label Switched Path Ping to bootstrap a BFD
session, control an SR Policy in the reverse direction of the SR-MPLS
tunnel, and applicability of BFD Demand mode in the SR-MPLS domain.
Also, the document describes the use of BFD Echo with BFD Control
packet payload.
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 October 28, 2020.
Mirsky, et al. Expires October 28, 2020 [Page 1]
Internet-Draft BFD in SPRING MPLS April 2020
Copyright Notice
Copyright (c) 2020 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
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Conventions . . . . . . . . . . . . . . . . . . . . . . . 3
1.1.1. Terminology . . . . . . . . . . . . . . . . . . . . . 3
1.1.2. Requirements Language . . . . . . . . . . . . . . . . 3
2. Bootstrapping BFD Session over Segment Routed Tunnel with
MPLS Data Plane . . . . . . . . . . . . . . . . . . . . . . . 4
3. Use BFD Reverse Path TLV over Segment Routed MPLS Tunnel . . 5
4. Use Non-FEC Path TLV . . . . . . . . . . . . . . . . . . . . 5
5. BFD Reverse Path TLV over Segment Routed MPLS Tunnel with
Dynamic Control Plane . . . . . . . . . . . . . . . . . . . . 7
6. Applicability of BFD Demand Mode in SR-MPLS Domain . . . . . 7
7. Using BFD to Monitor Point-to-Multipoint SR Policy . . . . . 7
8. Use of Echo BFD in SR-MPLS . . . . . . . . . . . . . . . . . 8
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
9.1. Non-FEC Path TLV . . . . . . . . . . . . . . . . . . . . 8
9.2. Return Code . . . . . . . . . . . . . . . . . . . . . . . 9
10. Implementation Status . . . . . . . . . . . . . . . . . . . . 10
11. Security Considerations . . . . . . . . . . . . . . . . . . . 10
12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 11
13. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 11
14. References . . . . . . . . . . . . . . . . . . . . . . . . . 11
14.1. Normative References . . . . . . . . . . . . . . . . . . 11
14.2. Informative References . . . . . . . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13
Show full document text