Detecting Multiprotocol Label Switched (MPLS) Data-Plane Failures
RFC 8029
Document | Type |
RFC - Proposed Standard
(March 2017; Errata)
Updated by RFC 8611
Updates RFC 1122
|
|
---|---|---|---|
Authors | Kireeti Kompella , George Swallow , Carlos Pignataro , Nagendra Nainar , Sam Aldrin , Mach Chen | ||
Last updated | 2018-12-20 | ||
Replaces | draft-smack-mpls-rfc4379bis | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Reviews | |||
Stream | WG state | Submitted to IESG for Publication | |
Document shepherd | Loa Andersson | ||
Shepherd write-up | Show (last changed 2016-10-04) | ||
IESG | IESG state | RFC 8029 (Proposed Standard) | |
Consensus Boilerplate | Yes | ||
Telechat date | |||
Responsible AD | Deborah Brungard | ||
Send notices to | "Loa Andersson" <loa@pi.nu> | ||
IANA | IANA review state | Version Changed - Review Needed | |
IANA action state | RFC-Ed-Ack |
Internet Engineering Task Force (IETF) K. Kompella Request for Comments: 8029 Juniper Networks, Inc. Obsoletes: 4379, 6424, 6829, 7537 G. Swallow Updates: 1122 C. Pignataro, Ed. Category: Standards Track N. Kumar ISSN: 2070-1721 Cisco S. Aldrin Google M. Chen Huawei March 2017 Detecting Multiprotocol Label Switched (MPLS) Data-Plane Failures Abstract This document describes a simple and efficient mechanism to detect data-plane failures in Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs). It defines a probe message called an "MPLS echo request" and a response message called an "MPLS echo reply" for returning the result of the probe. The MPLS echo request is intended to contain sufficient information to check correct operation of the data plane and to verify the data plane against the control plane, thereby localizing faults. This document obsoletes RFCs 4379, 6424, 6829, and 7537, and updates RFC 1122. Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc8029. Kompella, et al. Standards Track [Page 1] RFC 8029 Detecting MPLS Data-Plane Failures March 2017 Copyright Notice Copyright (c) 2017 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 (http://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. This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English. Kompella, et al. Standards Track [Page 2] RFC 8029 Detecting MPLS Data-Plane Failures March 2017 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 5 1.1. Conventions . . . . . . . . . . . . . . . . . . . . . . . 5 1.2. Structure of This Document . . . . . . . . . . . . . . . 6 1.3. Scope of This Specification . . . . . . . . . . . . . . . 6 2. Motivation . . . . . . . . . . . . . . . . . . . . . . . . . 7 2.1. Use of Address Range 127/8 . . . . . . . . . . . . . . . 8 2.2. Router Alert Option . . . . . . . . . . . . . . . . . . . 10 3. Packet Format . . . . . . . . . . . . . . . . . . . . . . . . 11 3.1. Return Codes . . . . . . . . . . . . . . . . . . . . . . 16 3.2. Target FEC Stack . . . . . . . . . . . . . . . . . . . . 17 3.2.1. LDP IPv4 Prefix . . . . . . . . . . . . . . . . . . . 19 3.2.2. LDP IPv6 Prefix . . . . . . . . . . . . . . . . . . . 19 3.2.3. RSVP IPv4 LSP . . . . . . . . . . . . . . . . . . . . 20 3.2.4. RSVP IPv6 LSP . . . . . . . . . . . . . . . . . . . . 20 3.2.5. VPN IPv4 Prefix . . . . . . . . . . . . . . . . . . . 21 3.2.6. VPN IPv6 Prefix . . . . . . . . . . . . . . . . . . . 22Show full document text