--- 1/draft-smack-mpls-rfc4379bis-02.txt 2015-10-09 12:23:03.876161656 -0700 +++ 2/draft-smack-mpls-rfc4379bis-03.txt 2015-10-09 12:23:04.140168069 -0700 @@ -1,22 +1,22 @@ Network Working Group C. Pignataro Internet-Draft N. Kumar Obsoletes: 4379 (if approved) Cisco Intended status: Standards Track S. Aldrin -Expires: March 29, 2016 Google +Expires: March 31, 2016 Google M. Chen Huawei - September 26, 2015 + September 28, 2015 Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures - draft-smack-mpls-rfc4379bis-02 + draft-smack-mpls-rfc4379bis-03 Abstract This document describes a simple and efficient mechanism that can be used to detect data plane failures in Multi-Protocol Label Switching (MPLS) Label Switched Paths (LSPs). There are two parts to this document: information carried in an MPLS "echo request" and "echo reply" for the purposes of fault detection and isolation, and mechanisms for reliably sending the echo reply. @@ -30,21 +30,21 @@ 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 http://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 March 29, 2016. + This Internet-Draft will expire on March 31, 2016. Copyright Notice Copyright (c) 2015 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 @@ -186,29 +186,35 @@ [RFC4379] defines the basic mechanism for MPLS LSP validation that can be used for fault detection and isolation. The scope of this document also is to address various updates to MPLS LSP Ping, including: 1. Updates to all references and citations. Obsoleted RFCs 2434, 2030, and 3036 are respectively replaced with RFCs 5226, 5905, and 5036. Additionally, these three documents published as RFCs: RFCs 4447, 5085, and 4761. - 2. Incorporate all outstanding Errata. These include Errata with + 2. Incorporate all outstanding Errata. These include Erratum with IDs: 108, 1418, 1714, 1786, 3399, 742, and 2978. 1.5. ToDo - Please remove this ToDo prior to publication: + This section should be empty, and removed, prior to publication. + ToDos: - 1. Review IANA Allocations - 2. Fix pending figure mis-alignments + 1. Evaluation of which of the RFCs that updated RFC 4379 need to be + incorporated into this 4379bis document. Specifically, these + RFCs updated RFC 4379: 5462, 6424, 6425, 6426, 6829, 7506, and + 7537. RFCs that updated RFC 4379 and are incorporated into this + 4379bis, will be Obsoleted by 4379bis. + 2. Review IANA Allocations + 3. Fix pending figure mis-alignments 2. Motivation When an LSP fails to deliver user traffic, the failure cannot always be detected by the MPLS control plane. There is a need to provide a tool that would enable users to detect such traffic "black holes" or misrouting within a reasonable period of time, and a mechanism to isolate faults. In this document, we describe a mechanism that accomplishes these