| < draft-ietf-mpls-entropy-lsp-ping-01.txt | draft-ietf-mpls-entropy-lsp-ping-02.txt > | |||
|---|---|---|---|---|
| Internet Engineering Task Force N. Akiya | Internet Engineering Task Force N. Akiya | |||
| Internet-Draft Big Switch Networks | Internet-Draft Big Switch Networks | |||
| Updates: 4379,6424,6790 (if approved) G. Swallow | Updates: 4379, 6424, 6790 (if approved) G. Swallow | |||
| Intended status: Standards Track C. Pignataro | Intended status: Standards Track C. Pignataro | |||
| Expires: December 13, 2015 Cisco Systems | Expires: July 7, 2016 Cisco | |||
| A. Malis | A. Malis | |||
| Huawei Technologies | Huawei Technologies | |||
| S. Aldrin | S. Aldrin | |||
| June 11, 2015 | January 4, 2016 | |||
| Label Switched Path (LSP) and Pseudowire (PW) Ping/Trace over | Label Switched Path (LSP) and Pseudowire (PW) Ping/Trace over | |||
| MPLS Network using Entropy Labels (EL) | MPLS Network using Entropy Labels (EL) | |||
| draft-ietf-mpls-entropy-lsp-ping-01 | draft-ietf-mpls-entropy-lsp-ping-02 | |||
| Abstract | Abstract | |||
| The Multiprotocol Label Switching (MPLS) Label Switched Path (LSP) | The Multiprotocol Label Switching (MPLS) Label Switched Path (LSP) | |||
| Ping and Traceroute are used to exercise specific paths of Equal-Cost | Ping and Traceroute are used to exercise specific paths of Equal-Cost | |||
| Multipath (ECMP). When LSP is signaled to use Entropy Label (EL) | Multipath (ECMP). When LSP is signaled to use Entropy Label (EL) | |||
| described in RFC6790, the ability for LSP Ping and Traceroute | described in RFC 6790, the ability for LSP Ping and Traceroute | |||
| operation to discover and exercise ECMP paths has been lost in | operation to discover and exercise ECMP paths has been lost in | |||
| scenarios which LSRs apply deviating load balance techniques. One | scenarios which LSRs apply deviating load balance techniques. One | |||
| such scenario is when some LSRs apply EL based load balancing while | such scenario is when some LSRs apply EL based load balancing while | |||
| other LSRs apply non-EL based load balancing (ex: IP). Another | other LSRs apply non-EL based load balancing (ex: IP). Another | |||
| scenario is when EL based LSP is stitched with another LSP which can | scenario is when EL based LSP is stitched with another LSP which can | |||
| be EL based or non-EL based. | be EL based or non-EL based. | |||
| This document extends the MPLS LSP Ping and Traceroute mechanisms to | This document extends the MPLS LSP Ping and Traceroute mechanisms to | |||
| restore the ability of exercising specific paths of ECMP over LSP | restore the ability of exercising specific paths of ECMP over LSP | |||
| which make use of Entropy Label. This document updates RFC4379, | which make use of the Entropy Label. This document updates RFC 4379, | |||
| RFC6424 and RFC6790. | RFC 6424, and RFC 6790. | |||
| Requirements Language | Requirements Language | |||
| The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", | The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", | |||
| "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this | "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this | |||
| document are to be interpreted as described in RFC 2119 [RFC2119]. | document are to be interpreted as described in RFC 2119 [RFC2119]. | |||
| Status of This Memo | Status of This Memo | |||
| This Internet-Draft is submitted in full conformance with the | This Internet-Draft is submitted in full conformance with the | |||
| skipping to change at page 2, line 12 ¶ | skipping to change at page 2, line 12 ¶ | |||
| Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
| Task Force (IETF). Note that other groups may also distribute | Task Force (IETF). Note that other groups may also distribute | |||
| working documents as Internet-Drafts. The list of current Internet- | working documents as Internet-Drafts. The list of current Internet- | |||
| Drafts is at http://datatracker.ietf.org/drafts/current/. | Drafts is at http://datatracker.ietf.org/drafts/current/. | |||
| Internet-Drafts are draft documents valid for a maximum of six months | Internet-Drafts are draft documents valid for a maximum of six months | |||
| and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
| time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
| material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
| This Internet-Draft will expire on December 13, 2015. | This Internet-Draft will expire on July 7, 2016. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2015 IETF Trust and the persons identified as the | Copyright (c) 2016 IETF Trust and the persons identified as the | |||
| document authors. All rights reserved. | document authors. All rights reserved. | |||
| This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
| Provisions Relating to IETF Documents | Provisions Relating to IETF Documents | |||
| (http://trustee.ietf.org/license-info) in effect on the date of | (http://trustee.ietf.org/license-info) in effect on the date of | |||
| publication of this document. Please review these documents | publication of this document. Please review these documents | |||
| carefully, as they describe your rights and restrictions with respect | carefully, as they describe your rights and restrictions with respect | |||
| to this document. Code Components extracted from this document must | to this document. Code Components extracted from this document must | |||
| include Simplified BSD License text as described in Section 4.e of | include Simplified BSD License text as described in Section 4.e of | |||
| the Trust Legal Provisions and are provided without warranty as | the Trust Legal Provisions and are provided without warranty as | |||
| skipping to change at page 20, line 8 ¶ | skipping to change at page 20, line 8 ¶ | |||
| 13. Acknowledgements | 13. Acknowledgements | |||
| Authors would like to thank Loa Andersson, Curtis Villamizar, Daniel | Authors would like to thank Loa Andersson, Curtis Villamizar, Daniel | |||
| King, Sriganesh Kini and Victor Ji for performing thorough review and | King, Sriganesh Kini and Victor Ji for performing thorough review and | |||
| providing valuable comments. | providing valuable comments. | |||
| 14. Contributing Authors | 14. Contributing Authors | |||
| Nagendra Kumar | Nagendra Kumar | |||
| Cisco Systems | Cisco Systems, Inc. | |||
| Email: naikumar@cisco.com | Email: naikumar@cisco.com | |||
| 15. References | 15. References | |||
| 15.1. Normative References | 15.1. Normative References | |||
| [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | |||
| Requirement Levels", BCP 14, RFC 2119, March 1997. | Requirement Levels", BCP 14, RFC 2119, | |||
| DOI 10.17487/RFC2119, March 1997, | ||||
| <http://www.rfc-editor.org/info/rfc2119>. | ||||
| [RFC4379] Kompella, K. and G. Swallow, "Detecting Multi-Protocol | [RFC4379] Kompella, K. and G. Swallow, "Detecting Multi-Protocol | |||
| Label Switched (MPLS) Data Plane Failures", RFC 4379, | Label Switched (MPLS) Data Plane Failures", RFC 4379, | |||
| February 2006. | DOI 10.17487/RFC4379, February 2006, | |||
| <http://www.rfc-editor.org/info/rfc4379>. | ||||
| [RFC6790] Kompella, K., Drake, J., Amante, S., Henderickx, W., and | [RFC6790] Kompella, K., Drake, J., Amante, S., Henderickx, W., and | |||
| L. Yong, "The Use of Entropy Labels in MPLS Forwarding", | L. Yong, "The Use of Entropy Labels in MPLS Forwarding", | |||
| RFC 6790, November 2012. | RFC 6790, DOI 10.17487/RFC6790, November 2012, | |||
| <http://www.rfc-editor.org/info/rfc6790>. | ||||
| [RFC7537] Decraene, B., Akiya, N., Pignataro, C., Andersson, L., and | [RFC7537] Decraene, B., Akiya, N., Pignataro, C., Andersson, L., and | |||
| S. Aldrin, "IANA Registries for LSP Ping Code Points", RFC | S. Aldrin, "IANA Registries for LSP Ping Code Points", | |||
| 7537, May 2015. | RFC 7537, DOI 10.17487/RFC7537, May 2015, | |||
| <http://www.rfc-editor.org/info/rfc7537>. | ||||
| 15.2. Informative References | 15.2. Informative References | |||
| [I-D.ravisingh-mpls-el-for-seamless-mpls] | [I-D.ravisingh-mpls-el-for-seamless-mpls] | |||
| Singh, R., Shen, Y., and J. Drake, "Entropy label for | Singh, R., Shen, Y., and J. Drake, "Entropy label for | |||
| seamless MPLS", draft-ravisingh-mpls-el-for-seamless- | seamless MPLS", draft-ravisingh-mpls-el-for-seamless- | |||
| mpls-04 (work in progress), October 2014. | mpls-04 (work in progress), October 2014. | |||
| [IANA-MPLS-LSP-PING] | [IANA-MPLS-LSP-PING] | |||
| IANA, "Multi-Protocol Label Switching (MPLS) Label | IANA, "Multi-Protocol Label Switching (MPLS) Label | |||
| Switched Paths (LSPs) Ping Parameters", | Switched Paths (LSPs) Ping Parameters", | |||
| <http://www.iana.org/assignments/mpls-lsp-ping-parameters/ | <http://www.iana.org/assignments/mpls-lsp-ping-parameters/ | |||
| mpls-lsp-ping-parameters.xhtml>. | mpls-lsp-ping-parameters.xhtml>. | |||
| [RFC6391] Bryant, S., Filsfils, C., Drafz, U., Kompella, V., Regan, | [RFC6391] Bryant, S., Ed., Filsfils, C., Drafz, U., Kompella, V., | |||
| J., and S. Amante, "Flow-Aware Transport of Pseudowires | Regan, J., and S. Amante, "Flow-Aware Transport of | |||
| over an MPLS Packet Switched Network", RFC 6391, November | Pseudowires over an MPLS Packet Switched Network", | |||
| 2011. | RFC 6391, DOI 10.17487/RFC6391, November 2011, | |||
| <http://www.rfc-editor.org/info/rfc6391>. | ||||
| [RFC6424] Bahadur, N., Kompella, K., and G. Swallow, "Mechanism for | [RFC6424] Bahadur, N., Kompella, K., and G. Swallow, "Mechanism for | |||
| Performing Label Switched Path Ping (LSP Ping) over MPLS | Performing Label Switched Path Ping (LSP Ping) over MPLS | |||
| Tunnels", RFC 6424, November 2011. | Tunnels", RFC 6424, DOI 10.17487/RFC6424, November 2011, | |||
| <http://www.rfc-editor.org/info/rfc6424>. | ||||
| [RFC7325] Villamizar, C., Kompella, K., Amante, S., Malis, A., and | [RFC7325] Villamizar, C., Ed., Kompella, K., Amante, S., Malis, A., | |||
| C. Pignataro, "MPLS Forwarding Compliance and Performance | and C. Pignataro, "MPLS Forwarding Compliance and | |||
| Requirements", RFC 7325, August 2014. | Performance Requirements", RFC 7325, DOI 10.17487/RFC7325, | |||
| August 2014, <http://www.rfc-editor.org/info/rfc7325>. | ||||
| Authors' Addresses | Authors' Addresses | |||
| Nobo Akiya | Nobo Akiya | |||
| Big Switch Networks | Big Switch Networks | |||
| Email: nobo.akiya.dev@gmail.com | Email: nobo.akiya.dev@gmail.com | |||
| George Swallow | George Swallow | |||
| Cisco Systems | Cisco Systems, Inc. | |||
| Email: swallow@cisco.com | Email: swallow@cisco.com | |||
| Carlos Pignataro | Carlos Pignataro | |||
| Cisco Systems | Cisco Systems, Inc. | |||
| Email: cpignata@cisco.com | Email: cpignata@cisco.com | |||
| Andrew G. Malis | Andrew G. Malis | |||
| Huawei Technologies | Huawei Technologies | |||
| Email: agmalis@gmail.com | Email: agmalis@gmail.com | |||
| Sam Aldrin | Sam Aldrin | |||
| End of changes. 18 change blocks. | ||||
| 25 lines changed or deleted | 33 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||