--- 1/draft-ietf-mpls-remote-lsp-ping-00.txt 2007-11-19 21:14:53.000000000 +0100 +++ 2/draft-ietf-mpls-remote-lsp-ping-01.txt 2007-11-19 21:14:53.000000000 +0100 @@ -1,21 +1,22 @@ Network Working Group George Swallow Internet Draft Cisco Systems, Inc. Category: Standards Track -Expiration Date: October 2007 Vanson Lim Cisco Systems, Inc. + November 2007 + Proxy LSP Ping - draft-ietf-mpls-remote-lsp-ping-00.txt + draft-ietf-mpls-remote-lsp-ping-01.txt Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that @@ -52,29 +53,30 @@ 3.1 Procedures for the initiator .............................. 5 3.2 Procedures for the proxy LSR .............................. 6 3.2.1 Sending an MPLS proxy ping reply .......................... 7 3.2.2 Sending the MPLS echo requests ............................ 7 4 Proxy Ping Request / Reply Messages ....................... 8 4.1 Proxy Ping Request / Reply Message formats ................ 9 4.2 Proxy Ping Request Message contents ....................... 10 4.3 Proxy Ping Reply Message Contents ......................... 10 5 Object formats ............................................ 11 5.1 Proxy Echo Parameters Object .............................. 11 - 5.2 Previous Hop Object ....................................... 13 + 5.2 Reply-to Address Object ................................... 12 + 5.3 Previous Hop Address Object ............................... 13 6 Security Considerations ................................... 13 7 IANA Considerations ....................................... 13 - 7.1 Message and Object Type Assignments ....................... 13 + 7.1 Message and Object Type Assignments ....................... 14 7.2 Return Code Assignments ................................... 14 8 Acknowledgments ........................................... 14 9 References ................................................ 14 9.1 Normative References ...................................... 14 - 9.2 Informative References .................................... 14 + 9.2 Informative References .................................... 15 10 Authors' Addresses ........................................ 15 1. Introduction It is anticipated that very large Point-to-Multipoint (P2MP) Label Switched Paths (LSPs) will exist. Further it is anticipated that many of the applications for P2MP tunnels will require OAM that is both rigorous and scalable. Suppose one wishes to trace a P2MP LSP to localize a fault which is @@ -150,22 +152,22 @@ The proxy LSR validates that it has a label mapping for the specified FEC and that it is authorized to send the specified MPLS echo request on behalf of the initiator. Depending on the Reply Mode carried in the header of the proxy ping request message and the above results an MPLS remote echo reply message might be sent back to the initiator. This message may also communicate the address of the previous hop. If the proxy LSR has a label mapping for the FEC and and all autho- rization check have passed, the proxy LSR formats an MPLS echo request. If the source address of the IP packet is not the initia- - tor, it includes a ReplyTo object containing the initiator's address. - It then sends it inband of the LSP. + tor, it includes a Reply-to Address object containing the initiator's + address. It then sends it inband of the LSP. The receivers process the MPLS echo request as normal, sending their MPLS echo replies back to the initiator. 3. Remote Echo / Reply Pprocedures 3.1. Procedures for the initiator The initiator creates an MPLS proxy ping request message. @@ -239,24 +241,24 @@ The proxy LSR then determines if it is authorized to send the speci- fied MPLS echo request on behalf of the initiator. An LSR MUST be capable of filtering addresses to validate initiators. Other filters on FECs or MPLS echo request contents MAY be applied. If a filter has been invoked (i.e. configured) and an address does not pass the filter, then an MPLS echo request message MUST NOT be sent, and the event SHOULD be logged. An MPLS proxy ping reply message may be sent with a Return Code of , "Remote Ping not authorized". - If the "Request for Previous Hop" flag is set, a PHOP Address Object - is formatted for inclusion in the MPLS proxy ping reply. If the pre- - vious HOP is unknown or ambiguous the Address Type is set to "No - Address Supplied". + If the "Request for Previous Hop" flag is set, a Previous Hop Address + Object is formatted for inclusion in the MPLS proxy ping reply. If + the previous HOP is unknown or ambiguous the Address Type is set to + "No Address Supplied". If there is a list of Next Hop addresses in the Proxy Echo Parameters object, each address is examined to determine if it is a next hop for this FEC. If any are not, those addresses are deleted from the list. The updated Proxy Echo Parameters object is included in the MPLS proxy ping reply. If the "Request for Downstream Mapping" flag is set the LSR formats a Downstream Mapping object for each interface that the MPLS echo request will be sent out. @@ -292,22 +294,22 @@ Flags and Reply Mode are copied from the Proxy Echo Parameters object. The Return Code and Return Subcode are set to zero. The Sender's Handle and Sequence Number are copied from the remote echo request message. The TimeStamp Sent is set to the time-of-day (in seconds and microseconds) that the echo request is sent. The TimeStamp Received is set to zero. - A ReplyTo object (see [SelfTest]) containing the initiator's address - is included. + A Reply-to Address object containing the initiator's address is + included. The following objects are copied from the MPLS proxy ping request message. Note that of these, only the Target FEC Stack is REQUIRED to appear in the MPLS proxy ping request message. Target FEC Stack Pad Vendor Enterprise Number Reply TOS Byte P2MP Egress Identifier [McstPing] @@ -407,37 +409,36 @@ objects: Type Object ---- ----------- 1 Target FEC Stack 2 Downstream Mapping 3 Pad 5 Vendor Enterprise Number 10 Reply TOS Byte tba Proxy Echo Parameters - tba PHOP Address tba P2MP Egress Identifier [McstPing] tba Echo Jitter TLV [McstPing] Vendor Private TLVs 4.3. Proxy Ping Reply Message Contents The MPLS proxy ping reply message MAY contain the following objects: Type Object ---- ----------- 1 Target FEC Stack 2 Downstream Mapping 5 Vendor Enterprise Number 9 Errored TLVs tba Proxy Echo Parameters - tba PHOP Address + tba Previous Hop Address Vendor Private objects 5. Object formats 5.1. Proxy Echo Parameters Object 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Address Type | Flags | Reply mode | TTL | @@ -458,33 +459,33 @@ Address Type The type of address found in the in the Destination IP Address and Next Hop IP Addresses fields. The type codes appear in the table below: Address Family Type IPv4 Numbered 1 IPv6 Numbered 3 + Flags Request for Previous Hop 0x01 - When set this requests that the proxy LSR supply the PHOP + When set this requests that the proxy LSR supply the previous hop address in the MPLS proxy ping reply message Request for Downstream Mapping 0x02 When set this requests that the proxy LSR supply a Downstream Mapping object in the MPLS proxy ping reply message - Reply mode The reply mode to be sent in the MPLS Echo Request message; the values are as specified in [RFC4379] TTL The TTL to be used in the label corresponding to the FEC in the MPLS Echo Request packet @@ -500,27 +501,45 @@ If the Address Type is IPv4, an address from the range 127/8; If the Address Type is IPv6, an address from the range 0:0:0:0:0:FFFF:127/104 Next Hop IP Addresses A list of next hop address that the echo request message is to be sent towards -5.2. Previous Hop Object +5.2. Reply-to Address Object +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Address Type | MUST be Zero | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | - : Previous Hop IP Address : + : Reply-to Address : + | | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + Address Type + + A type code as specified in the table below: + + Type Type of Address + + 1 IPv4 + 3 IPv6 + +5.3. Previous Hop Address Object + + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | Address Type | MUST be Zero | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | | + : Previous Hop Address : | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Address Type A type code as specified in the table below: Type Type of Address 0 No Address Supplied @@ -539,42 +558,39 @@ This document makes the following codepoint assigments (pending IANA action): Registry Codepoint Purpose LSP Ping Message Type tba MPLS proxy ping request message tba MPLS proxy ping reply LSP Ping Object Type tba Proxy Echo Parameters - tba PHOP Address + tba Reply-to Address + tba Previous Hop Address 7.2. Return Code Assignments Value Meaning tba Remote Ping not authorized - tba Failed Next Hops 8. Acknowledgments 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. - [SelfTest] Swallow, G. et al., "LSR Self Test", - draft-ietf-mpls-lsr-self-test-06.txt, October 2005. - [KeyWords] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [McstPing] Farrel, A. et al, "Detecting Data Plane Failures in Point-to-Multipoint MPLS Traffic Engineering - Extensions to LSP Ping", draft-ietf-mpls-p2mp-lsp-ping-02.txt, September 2006. 9.2. Informative References @@ -633,79 +649,10 @@ rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. - - Notes: - - Indication leaf, bud etc. Look at [McstPing] need to discuss with - Adrian. New Downstream mapping thingy - - Inclusion of multiple Downstream Mapping - - Multiple FECs in FEC Stack - - partial rules for FEC processing - - Node must recognize top FEC; - Must recognize FEC subsequent FECs if the previous operation was - POP - - PHOP/Downstream only request??? - - Specification of TOS byte for MPLS proxy ping reply??? - - Container for other objects? - - Multiple DS maps; grouping by nexthop. - - proxy echo parameters - change MBZ to Global Flags with none defined? - - version number should be added to message description. - - TTL values for additional labels - - IANA Registry name is hopelessly confusing! - - "Label Switched Paths (LSPs) Parameters - Message Types" - - Flags MAY be set to request use of either the ingress' source address - or the initiators source address. - - If the "Ingress Source Address" flag is set and the proxy LSR is con- - figured to allow to use the ingress address, the proxy LSR determines - the ingress LSR. If the address is found, it is used as the source - address of the MPLS echo request. Otherwise the Return Code is set - to , "Unable to use ingress source address". If the Reply Mode - of the message header is not 0, an MPLS proxy ping reply message - SHOULD be sent as described below. - - If either the "Initiator Source Address" or "Initiator Source - Address" flags is set, the source address is set as specified. Oth- - erwise - - If the "Initiator Source Address" flag is set and the proxy LSR is - configured to allow to use the iniator's address it is used as the - source address of the MPLS echo request. Otherwise the Return Code - is set to , "Unable to use intiator source address". If the - Reply Mode of the message header is not 0, an MPLS proxy ping reply - message SHOULD be sent as described below. - - Ingress Source Address 0x04 - - When set this requests that the address of the ingress of - the LSP be used as the source address of the MPLS echo - request packet - - Initiator Source Address 0x08 - - When set this requests that the address of the initiator be - used as the source address of the MPLS echo request packet - - tba Unable to use ingress source address - tba Unable to use initiator source address