Proxy MPLS Echo Request
draft-ietf-mpls-proxy-lsp-ping-00
The information below is for an old version of the document.
Document | Type |
This is an older version of an Internet-Draft that was ultimately published as RFC 7555.
|
|
---|---|---|---|
Authors | George Swallow , Vanson Lim , Sam Aldrin | ||
Last updated | 2013-07-05 | ||
Replaces | draft-lim-mpls-proxy-lsp-ping | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Formats | |||
Reviews |
GENART Last Call review
(of
-03)
by Tom Taylor
Ready w/issues
|
||
Additional resources | Mailing list discussion | ||
Stream | WG state | WG Document | |
Associated WG milestone |
|
||
Document shepherd | (None) | ||
IESG | IESG state | Became RFC 7555 (Proposed Standard) | |
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
draft-ietf-mpls-proxy-lsp-ping-00
Swallow, et al. Expires January 06, 2014 [Page 19] Internet-Draft Proxy LSP Ping July 2013 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Upst Addr Type; Local Addr Type These two fields determine the type and length of the respective addresses. The codes are specified in the table below: Type Type of Address Length 0 No Address Supplied 0 1 IPv4 4 3 IPv6 16 Upstream Address The address of the immediate upstream neighbor for the topmost FEC in the FEC stack. If protocol adjacency exists by which the label for this FEC was exchanged, this address MUST be the address used in that protocol exchange. Local Address The local address used in the protocol adjacency exists by which the label for this FEC was exchanged. 5.4. Downstream Neighbor Address TLV 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |Dnst Addr Type |Local Addr Type| MUST be Zero | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | : Downstream Address : | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | : Local Address : | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Dnst Addr Type; Local Addr Type These two fields determine the type and length of the Swallow, et al. Expires January 06, 2014 [Page 20] Internet-Draft Proxy LSP Ping July 2013 respective addresses. The codes are specified in the table below: Type Type of Address Length 0 No Address Supplied 0 1 IPv4 4 3 IPv6 16 Downstream Address The address of a immediate downstream neighbor for the topmost FEC in the FEC stack. If protocol adjacency exists by which the label for this FEC was exchanged, this address MUST be the address used in that protocol exchange. Local Address The local address used in the protocol adjacency exists by which the label for this FEC was exchanged. 6. Security Considerations The mechanisms described in this document are intended to be used within a Service Provider network and to be initiated only under the authority of that administration. If such a network also carries internet traffic, or permits IP access from other administrations, MPLS proxy ping message SHOULD be discarded at those points. This can be accomplished by filtering on source address or by filtering all MPLS ping messages on UDP port. Any node which acts as a proxy node SHOULD validate requests against a set of valid source addresses. An implementation MUST provide such filtering capabilities. MPLS proxy ping request messages are IP addressed directly to the Proxy node. If a node which receives an MPLS proxy ping message via IP or Label TTL expiration, it MUST NOT be acted upon. MPLS proxy ping request messages are IP addressed directly to the Proxy node. If a MPLS Proxy ping request IP destination address is a Martian Address, it MUST NOT be acted upon. if a MPLS Proxy ping request IP source address is not IP reachable by the Proxy LSR, the Proxy request MUST NOT be acted upon. Swallow, et al. Expires January 06, 2014 [Page 21] Internet-Draft Proxy LSP Ping July 2013 MPLS proxy ping requests are limited to making their request via the specification of a FEC. This ensures that only valid MPLS echo request messages can be created. No label spoofing attacks are possible. 7. Acknowledgements The authors would like to thank Nobo Akiya for his detailed review and insightful comments. 8. IANA Considerations This document makes the following assignments (pending IANA action) LSP Ping Message Types Type Value Field ---- ----------- TBA-1 MPLS proxy ping request TBA-2 MPLS proxy ping reply TLVs and Sub-TLVs Type Sub-Type Value Field ---- -------- ----------- TBA-3 Proxy Echo Parameters 1 Next Hop TBA-4 Reply-to Address TBA-5 Upstream Neighbor Address TBA-6 Downstream Neighbor Address Return Code [pending IANA assignment] Value Meaning ----- ------- 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 ----- ------- Swallow, et al. Expires January 06, 2014 [Page 22] Internet-Draft Proxy LSP Ping July 2013 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 Performing Label Switched Path Ping (LSP Ping) over MPLS Tunnels", RFC 6424, November 2011. [RFC6425] Saxena, S., Swallow, G., Ali, Z., Farrel, A., Yasukawa, S., and T. Nadeau, "Detecting Data-Plane Failures in Point-to-Multipoint MPLS - Extensions to LSP Ping", RFC 6425, November 2011. 9.2. Informative References [RFC4875] Aggarwal, R., Papadimitriou, D., and S. Yasukawa, "Extensions to Resource Reservation Protocol - Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE Label Switched Paths (LSPs)", RFC 4875, May 2007. [RFC6388] Wijnands, IJ., Minei, I., Kompella, K., and B. Thomas, "Label Distribution Protocol Extensions for Point-to- Multipoint and Multipoint-to-Multipoint Label Switched Paths", RFC 6388, November 2011. Authors' Addresses George Swallow Cisco Systems 1414 Massachusetts Ave Boxborough, MA 01719 USA Email: swallow@cisco.com Swallow, et al. Expires January 06, 2014 [Page 23] Internet-Draft Proxy LSP Ping July 2013 Vanson Lim Cisco Systems 1414 Massachusetts Avenue Boxborough, MA 01719 USA Email: vlim@cisco.com Sam Aldrin Huawei Technologies 2330 Central Express Way Santa Clara, CA 95951 USA Email: aldrin.ietf@gmail.com Swallow, et al. Expires January 06, 2014 [Page 24]