--- 1/draft-ietf-mpls-proxy-lsp-ping-00.txt 2014-01-02 17:14:32.662045928 -0800 +++ 2/draft-ietf-mpls-proxy-lsp-ping-01.txt 2014-01-02 17:14:32.710047061 -0800 @@ -1,20 +1,20 @@ Network Working Group G. Swallow Internet-Draft V. Lim Intended status: Standards Track Cisco Systems -Expires: January 06, 2014 S. Aldrin +Expires: July 6, 2014 S. Aldrin Huawei Technologies - July 05, 2013 + January 02, 2014 Proxy MPLS Echo Request - draft-ietf-mpls-proxy-lsp-ping-00 + draft-ietf-mpls-proxy-lsp-ping-01 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,25 +27,25 @@ 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 January 06, 2014. + This Internet-Draft will expire on July 6, 2014. Copyright Notice - Copyright (c) 2013 IETF Trust and the persons identified as the + Copyright (c) 2014 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 @@ -60,47 +60,47 @@ 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. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 4 - 2. Proxy Ping Overview . . . . . . . . . . . . . . . . . . . . . 4 + 2. Proxy Ping Overview . . . . . . . . . . . . . . . . . . . . . 5 3. Proxy MPLS Echo Request / Reply Procedures . . . . . . . . . 6 3.1. Procedures for the initiator . . . . . . . . . . . . . . 6 3.2. Procedures for the proxy LSR . . . . . . . . . . . . . . 7 3.2.1. Proxy LSR Handling when it is Egress for FEC . . . . 9 3.2.2. Downstream Detailed/Downstream Maps in Proxy Reply . 10 3.2.3. Sending an MPLS proxy ping reply . . . . . . . . . . 10 3.2.4. Sending the MPLS echo requests . . . . . . . . . . . 10 3.2.4.1. Forming the base MPLS echo request . . . . . . . 11 3.2.4.2. Per interface sending procedures . . . . . . . . 12 4. Proxy Ping Request / Reply Messages . . . . . . . . . . . . . 12 4.1. Proxy Ping Request / Reply Message formats . . . . . . . 12 4.2. Proxy Ping Request Message contents . . . . . . . . . . . 13 4.3. Proxy Ping Reply Message Contents . . . . . . . . . . . . 14 - 5. TLV formats . . . . . . . . . . . . . . . . . . . . . . . . . 14 - 5.1. Proxy Echo Parameters TLV . . . . . . . . . . . . . . . . 14 + 5. TLV formats . . . . . . . . . . . . . . . . . . . . . . . . . 15 + 5.1. Proxy Echo Parameters TLV . . . . . . . . . . . . . . . . 15 5.1.1. Next Hop sub-TLV . . . . . . . . . . . . . . . . . . 18 5.2. Reply-to Address TLV . . . . . . . . . . . . . . . . . . 19 - 5.3. Upstream Neighbor Address TLV . . . . . . . . . . . . . . 19 - 5.4. Downstream Neighbor Address TLV . . . . . . . . . . . . . 20 + 5.3. Upstream Neighbor Address TLV . . . . . . . . . . . . . . 20 + 5.4. Downstream Neighbor Address TLV . . . . . . . . . . . . . 21 6. Security Considerations . . . . . . . . . . . . . . . . . . . 21 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 22 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 23 9.1. Normative References . . . . . . . . . . . . . . . . . . 23 9.2. Informative References . . . . . . . . . . . . . . . . . 23 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 24 1. Introduction This document is motivated by two broad issues in connection with diagnosing Point-to-Multipoint (P2MP) Label Switched Paths (LSPs). The first is scalability due to the automatic replication of Multiprotocol Label Switching (MPLS) Echo Request Messages as they proceed down the tree. The second, which is primarily motivated by Multicast Label Distribution Protocol (mLDP), is the ability to trace a sub-LSP from leaf node to root node. @@ -680,91 +681,89 @@ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | : : : Sub-TLVs : : : | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Address Type - The type and length of the address found in the in the - Destination IP Address and Next Hop IP Addresses fields. - The values are shared with the Downstream Mapping Address - Type Registry. + The type and length of the address found in the in the Destination + IP Address and Next Hop IP Addresses fields. The values are + shared with the Downstream Mapping Address Type Registry. The type codes applicable in this case appear in the table below: Address Family Type Length IPv4 1 4 IPv6 3 16 Reply mode The reply mode to be sent in the MPLS Echo Request message; the values are as specified in [RFC4379]. Proxy Flags - The Proxy Request Initiator sets zero, one or more of these - flags to request actions at the Proxy LSR. - Request for FEC Neighbor Address info 0x01 + The Proxy Request Initiator sets zero, one or more of these flags + to request actions at the Proxy LSR. + + 0x01 Request for FEC Neighbor Address info When set this requests that the proxy LSR supply the Upstream and Downstream neighbor address information in the MPLS proxy ping reply message. This flag is only applicable for the topmost FEC in the FEC stack if the FEC types corresponds with a P2MP or MP2MP LSPs. The Proxy LSR MUST - respond as applicable with a Upstream Neighbor Address - TLV and Downstream Neighbor Address TLV(s) in the MPLS - Proxy ping reply message. Upstream Neighbor Address TLV - needs be included only if there is an upstream neighbor. - Similarly, one Downstream Neighbor Address TLV needs to - be included for each Downstream Neighbor for which the LSR - learned bindings from. + respond as applicable with a Upstream Neighbor Address TLV + and Downstream Neighbor Address TLV(s) in the MPLS Proxy + ping reply message. Upstream Neighbor Address TLV needs be + included only if there is an upstream neighbor. Similarly, + one Downstream Neighbor Address TLV needs to be included for + each Downstream Neighbor for which the LSR learned bindings + from. Setting this flag will cause the proxy LSR to cancel sending an Echo request. Information learned with such proxy reply may be used by the proxy initiator to generate subsequent proxy requests. - Request for Downstream Mapping 0x02 + 0x02 Request for Downstream Mapping When set this requests that the proxy LSR supply a - Downstream Mapping TLV see [RFC4379] in the MPLS - proxy ping reply message. It's not valid - to have Request for Downstream Detailed Mapping flag set - when this flag is set. + Downstream Mapping TLV see [RFC4379] in the MPLS proxy ping + reply message. It's not valid to have Request for + Downstream Detailed Mapping flag set when this flag is set. Setting this flag will cause the proxy LSR to cancel sending an Echo request. Information learned with such proxy reply may be used by the proxy initiator to generate subsequent proxy requests. - Request for Downstream Detailed Mapping 0x04 + 0x04 Request for Downstream Detailed Mapping When set this requests that the proxy LSR supply a - Downstream Detailed Mapping TLV see [RFC6424] in the - MPLS proxy ping reply message. It's not valid - to have Request for Downstream Mapping flag set - when this flag is set. + Downstream Detailed Mapping TLV see [RFC6424] in the MPLS + proxy ping reply message. It's not valid to have Request + for Downstream Mapping flag set when this flag is set. Setting this flag will cause the proxy LSR to cancel sending an Echo request. Information learned with such proxy reply may be used by the proxy initiator to generate subsequent proxy requests. - Explicit DSCP Request 0x08 + 0x08 Explicit DSCP Request - When set this requests that the proxy LSR use - the supplied "Rqst'd DSCP" byte in the echo request message + When set this requests that the proxy LSR use the supplied + "Rqst'd DSCP" byte in the echo request message TTL The TTL to be used in the label stack entry corresponding to the topmost FEC in the in the MPLS Echo Request packet. Valid values are in the range [1,255]. A setting of 0 should be ignored by the Proxy LSR. Requested DSCP @@ -776,33 +775,31 @@ Source UDP Port The source UDP port to be sent in the MPLS Echo Request packet Global Flags The Global Flags to be sent in the MPLS Echo Request message MPLS Payload Size - Used to request that the MPLS payload (IP header + UDP header - + MPLS echo request) be padded using a zero filled Pad TLV - so that the IP header, UDP header nad MPLS echo request total - the specified size. Field set to zero means no - size request is being made. If the requested size is less - than the minimum size required to form the MPLS echo request, - the request will be treated as a best effort request with - the Proxy LSR building the smallest possible packet (ie - not using a Pad TLV). The IP header DF bit should be set - when this field is non zero. + Used to request that the MPLS payload (IP header + UDP header + + MPLS echo request) be padded using a zero filled Pad TLV so + that the IP header, UDP header nad MPLS echo request total the + specified size. Field set to zero means no size request is + being made. If the requested size is less than the minimum + size required to form the MPLS echo request, the request will + be treated as a best effort request with the Proxy LSR building + the smallest possible packet (ie not using a Pad TLV). The IP + header DF bit should be set when this field is non zero. Destination IP Address - If the Address Type is IPv4, an address from the range 127/8; If the Address Type is IPv6, an address from the range ::FFFF:7F00:0/104 Sub-TLVs A TLV encoded list of sub-TLVs. Currently one is defined. Sub-Type Length Value Field -------- ------ ----------- @@ -834,21 +830,22 @@ 3 IPv6 Numbered 16 16 4 IPv6 Unnumbered 16 4 5 IPv4 Protocol Adj 4 0 6 IPv6 Protocol Adj 16 0 Note: Types 1-4 correspond to the types in the DS Mapping TLV. They are expected to populated with information obtained through a previously returned DS Mapping TLV. Types 5 and 6 are intended to be populated from the local address information obtained from a previously returned - Downstream Neighbor Address TLV(s)/Upstream Neighbor Address TLV. + Downstream Neighbor Address TLV(s)/Upstream Neighbor + Address TLV. Next Hop IP Address A next hop address that the echo request message is to be sent towards Next Hop Interface Identifier of the interface through which the echo request message is to be sent. For Addr Type 5, and 6, the Next Hop