--- 1/draft-lim-mpls-proxy-lsp-ping-02.txt 2013-07-04 21:14:25.875261566 -0700 +++ 2/draft-lim-mpls-proxy-lsp-ping-03.txt 2013-07-04 21:14:25.927262988 -0700 @@ -1,20 +1,20 @@ Network Working Group G. Swallow Internet-Draft V. Lim Intended status: Standards Track Cisco Systems -Expires: November 08, 2013 S. Aldrin +Expires: January 06, 2014 S. Aldrin Huawei Technologies - May 07, 2013 + July 05, 2013 Proxy MPLS Echo Request - draft-lim-mpls-proxy-lsp-ping-02 + draft-lim-mpls-proxy-lsp-ping-03 Abstract This document defines a means of remotely initiating Multiprotocol Label Switched Protocol Pings on Label Switched Paths. A proxy ping request is sent to any Label Switching Routers along a Label Switched Path. The primary motivations for this facility are first to limit the number of messages and related processing when using LSP Ping in large Point-to-Multipoint LSPs, and second to enable leaf to leaf/ root tracing. @@ -27,21 +27,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 November 08, 2013. + This Internet-Draft will expire on January 06, 2014. Copyright Notice Copyright (c) 2013 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 @@ -594,61 +594,62 @@ MPLS echo request/reply. These changes include any syntactic or semantic changes made to any of the fixed fields, or to any TLV or sub-TLV assignment or format that is defined at a certain version number. The Version Number may not need to be changed if an optional TLV or sub-TLV is added.) Message Type Type Message ---- ------- - 3 MPLS proxy ping request + TBA-1 MPLS proxy ping request (Pending IANA assignment) - 4 MPLS proxy ping reply + TBA-2 MPLS proxy ping reply (Pending IANA assignment) 4.2. Proxy Ping Request Message contents The MPLS proxy ping request message MAY contain the following TLVs: Type TLV ---- ----------- 1 Target FEC Stack 2 Downstream Mapping 3 Pad 5 Vendor Enterprise Number 10 Reply TOS Byte 11 P2MP Responder Identifier [RFC6425] 12 Echo Jitter TLV [RFC6425] 20 Downstream Detailed Mapping - tba Proxy Echo Parameters (Pending IANA assignment) + TBA-3 Proxy Echo Parameters (Pending IANA assignment) + TBA-4 Reply-to-Address TLV * Vendor Private TLVs * TLVs types in the Vendor Private TLV Space MUST be ignored if not understood 4.3. Proxy Ping Reply Message Contents The MPLS proxy ping reply message MAY contain the following TLVs: Type TLV ---- ----------- 1 Target FEC Stack 2 Downstream Mapping 5 Vendor Enterprise Number 9 Errored TLVs 20 Downstream Detailed Mapping - tba Proxy Echo Parameters (Pending IANA assignment) - tba Upstream Neighbor Address (Pending IANA assignment) - tba Downstream Neighbor Address (0 or more) + TBA-3 Proxy Echo Parameters (Pending IANA assignment) + TBA-5 Upstream Neighbor Address (Pending IANA assignment) + TBA-6 Downstream Neighbor Address (0 or more) (Pending IANA assignment) * Vendor Private TLVs * TLVs types in the Vendor Private TLV Space MUST be ignored if not understood 5. TLV formats 5.1. Proxy Echo Parameters TLV @@ -993,48 +997,48 @@ and insightful comments. 8. IANA Considerations This document makes the following assignments (pending IANA action) LSP Ping Message Types Type Value Field ---- ----------- - 03(tba) MPLS proxy ping request - 04(tba) MPLS proxy ping reply + TBA-1 MPLS proxy ping request + TBA-2 MPLS proxy ping reply TLVs and Sub-TLVs Type Sub-Type Value Field ---- -------- ----------- - 22(tba) Proxy Echo Parameters + TBA-3 Proxy Echo Parameters 1 Next Hop - 23(tba) Reply-to Address - 24(tba) Upstream Neighbor Address - 25(tba) Downstream Neighbor Address + TBA-4 Reply-to Address + TBA-5 Upstream Neighbor Address + TBA-6 Downstream Neighbor Address Return Code [pending IANA assignment] Value Meaning ----- ------- - 16(tba) Proxy ping not authorized. - 17(tba) Proxy ping parameters need to be modified. - 18(tba) MPLS Echo Request Could not be sent. - 18(tba) Replying router has FEC mapping for topmost FEC. + TBA-7 Proxy ping not authorized. + TBA-8 Proxy ping parameters need to be modified. + TBA-9 MPLS Echo Request Could not be sent. + TBA-10 Replying router has FEC mapping for topmost FEC. Downstream Address Mapping Registry [pending IANA assignment] Value Meaning ----- ------- - 5(tba) IPv4 Protocol Adj - 6(tba) IPv6 Protocol Adj + TBA-11 IPv4 Protocol Adj + TBA-12 IPv6 Protocol Adj 9. References 9.1. Normative References [RFC4379] Kompella, K. and G. Swallow, "Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures", RFC 4379, February 2006. [RFC6424] Bahadur, N., Kompella, K., and G. Swallow, "Mechanism for