Bidirectional Forwarding Detection (BFD) in Segment Routing Networks Using MPLS Dataplane
draft-mirsky-spring-bfd-05
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2018-03-02
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
pdf
html
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: September 2, 2018 Nuage Networks
I. Varlashkin
Google
M. Chen
Huawei
March 1, 2018
Bidirectional Forwarding Detection (BFD) in Segment Routing Networks
Using MPLS Dataplane
draft-mirsky-spring-bfd-05
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 kind of paths between systems. This document
defines how to use Label Switched Path Ping to bootstrap and control
path in reverse direction of a BFD session on the Segment Routing
static MPLS tunnel and applicability of BFD Demand mode to SR-MPLS
domain.
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 September 2, 2018.
Mirsky, et al. Expires September 2, 2018 [Page 1]
Internet-Draft BFD in SPRING MPLS March 2018
Copyright Notice
Copyright (c) 2018 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 used in this document . . . . . . . . . . . . 3
1.1.1. Terminology . . . . . . . . . . . . . . . . . . . . . 3
1.1.2. Requirements Language . . . . . . . . . . . . . . . . 3
2. Bootstrapping BFD session over Segment Routed tunnel . . . . 3
3. Use BFD Reverse Path TLV over Segment Routed MPLS Tunnel . . 4
4. Use Non-FEC Path TLV . . . . . . . . . . . . . . . . . . . . 4
5. BFD Reverse Path TLV over Segment Routed MPLS Tunnel with
Dynamic Control Plane . . . . . . . . . . . . . . . . . . . . 6
6. Applicability of BFD Demand Mode in SR-MPLS Domain . . . . . 6
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
7.1. Non-FEC Path TLV . . . . . . . . . . . . . . . . . . . . 7
7.2. Return Code . . . . . . . . . . . . . . . . . . . . . . . 8
8. Security Considerations . . . . . . . . . . . . . . . . . . . 8
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
10.1. Normative References . . . . . . . . . . . . . . . . . . 8
10.2. Informative References . . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction
[RFC5880], [RFC5881], and [RFC5883] established the Bidirectional
Forwarding Detection (BFD) protocol for IP networks. [RFC5884] and
[RFC7726] set rules of using BFD Asynchronous mode over Multiprotocol
Label Switching (MPLS) Label Switched Path (LSP). These latter
standards implicitly assume that the egress BFD peer, which is the
egress Label Edge Router (LER), will use the shortest path route
regardless of the path the ingress LER uses to send BFD control
packets towards it.
Mirsky, et al. Expires September 2, 2018 [Page 2]
Show full document text