| < draft-ietf-mpls-spring-entropy-label-00.txt | draft-ietf-mpls-spring-entropy-label-01.txt > | |||
|---|---|---|---|---|
| Network Working Group S. Kini, Ed. | Network Working Group S. Kini, Ed. | |||
| Internet-Draft Ericsson | Internet-Draft Ericsson | |||
| Intended status: Informational K. Kompella | Intended status: Informational K. Kompella | |||
| Expires: September 6, 2015 Juniper | Expires: March 9, 2016 Juniper | |||
| S. Sivabalan | S. Sivabalan | |||
| Cisco | Cisco | |||
| S. Litkowski | S. Litkowski | |||
| Orange | Orange | |||
| R. Shakir | R. Shakir | |||
| B.T. | ||||
| X. Xu | X. Xu | |||
| Huawei | Huawei | |||
| W. Hendrickx | W. Hendrickx | |||
| Alcatel-Lucent | Alcatel-Lucent | |||
| J. Tantsura | J. Tantsura | |||
| Ericsson | Ericsson | |||
| March 5, 2015 | September 6, 2015 | |||
| Entropy labels for source routed stacked tunnels | Entropy labels for source routed stacked tunnels | |||
| draft-ietf-mpls-spring-entropy-label-00 | draft-ietf-mpls-spring-entropy-label-01 | |||
| Abstract | Abstract | |||
| Source routed tunnel stacking is a technique that can be leveraged to | Source routed tunnel stacking is a technique that can be leveraged to | |||
| provide a method to steer a packet through a controlled set of | provide a method to steer a packet through a controlled set of | |||
| segments. This can be applied to the Multi Protocol Label Switching | segments. This can be applied to the Multi Protocol Label Switching | |||
| (MPLS) data plane. Entropy label (EL) is a technique used in MPLS to | (MPLS) data plane. Entropy label (EL) is a technique used in MPLS to | |||
| improve load balancing. This document examines and describes how ELs | improve load balancing. This document examines and describes how ELs | |||
| are to be applied to source routed stacked tunnels. | are to be applied to source routed stacked tunnels. | |||
| skipping to change at page 1, line 48 ¶ | skipping to change at page 1, line 48 ¶ | |||
| 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 September 6, 2015. | This Internet-Draft will expire on March 9, 2016. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2015 IETF Trust and the persons identified as the | Copyright (c) 2015 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 | |||
| skipping to change at page 2, line 52 ¶ | skipping to change at page 3, line 4 ¶ | |||
| 1. Introduction | 1. Introduction | |||
| The source routed stacked tunnels paradigm is leveraged by techniques | The source routed stacked tunnels paradigm is leveraged by techniques | |||
| such as Segment Routing (SR) [I-D.filsfils-spring-segment-routing] to | such as Segment Routing (SR) [I-D.filsfils-spring-segment-routing] to | |||
| steer a packet through a set of segments. This can be directly | steer a packet through a set of segments. This can be directly | |||
| applied to the MPLS data plane, but it has implications on label | applied to the MPLS data plane, but it has implications on label | |||
| stack depth. | stack depth. | |||
| Clarifying statements on label stack depth have been provided in | Clarifying statements on label stack depth have been provided in | |||
| [RFC7325] but they do not address the case of source routed stacked | [RFC7325] but they do not address the case of source routed stacked | |||
| MPLS tunnels as described in [I-D.gredler-spring-mpls] or | MPLS tunnels as described in [I-D.filsfils-spring-segment-routing] | |||
| where deeper label stacks are more prevalent. | ||||
| [I-D.filsfils-spring-segment-routing] where deeper label stacks are | ||||
| more prevalent. | ||||
| Entropy label (EL) [RFC6790] is a technique used in the MPLS data | Entropy label (EL) [RFC6790] is a technique used in the MPLS data | |||
| plane to provide entropy for load balancing. When using LSP | plane to provide entropy for load balancing. When using LSP | |||
| hierarchies there are implications on how [RFC6790] should be | hierarchies there are implications on how [RFC6790] should be | |||
| applied. One such issue is addressed by | applied. One such issue is addressed by | |||
| [I-D.ravisingh-mpls-el-for-seamless-mpls] but that is when different | [I-D.ravisingh-mpls-el-for-seamless-mpls] but that is when different | |||
| levels of the hierarchy are created at different LSRs. The current | levels of the hierarchy are created at different LSRs. The current | |||
| document addresses the case where the hierarchy is created at a | document addresses the case where the hierarchy is created at a | |||
| single LSR as required by source stacked tunnels. | single LSR as required by source stacked tunnels. | |||
| skipping to change at page 9, line 40 ¶ | skipping to change at page 9, line 40 ¶ | |||
| 9.1. Normative References | 9.1. Normative References | |||
| [I-D.filsfils-spring-segment-routing] | [I-D.filsfils-spring-segment-routing] | |||
| Filsfils, C., Previdi, S., Bashandy, A., Decraene, B., | Filsfils, C., Previdi, S., Bashandy, A., Decraene, B., | |||
| Litkowski, S., Horneffer, M., Milojevic, I., Shakir, R., | Litkowski, S., Horneffer, M., Milojevic, I., Shakir, R., | |||
| Ytti, S., Henderickx, W., Tantsura, J., and E. Crabbe, | Ytti, S., Henderickx, W., Tantsura, J., and E. Crabbe, | |||
| "Segment Routing Architecture", draft-filsfils-spring- | "Segment Routing Architecture", draft-filsfils-spring- | |||
| segment-routing-04 (work in progress), July 2014. | segment-routing-04 (work in progress), July 2014. | |||
| [I-D.gredler-spring-mpls] | ||||
| Gredler, H., Rekhter, Y., Jalil, L., Kini, S., and X. Xu, | ||||
| "Supporting Source/Explicitly Routed Tunnels via Stacked | ||||
| LSPs", draft-gredler-spring-mpls-06 (work in progress), | ||||
| May 2014. | ||||
| [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. | |||
| [I-D.xu-isis-mpls-elc] | [I-D.xu-isis-mpls-elc] | |||
| Xu, X., Kini, S., Sivabalan, S., Filsfils, C., and S. | Xu, X., Kini, S., Sivabalan, S., Filsfils, C., and S. | |||
| Litkowski, "Signaling Entropy Label Capability Using IS- | Litkowski, "Signaling Entropy Label Capability Using IS- | |||
| IS", draft-xu-isis-mpls-elc-01 (work in progress), | IS", draft-xu-isis-mpls-elc-02 (work in progress), April | |||
| September 2014. | 2015. | |||
| [I-D.xu-ospf-mpls-elc] | [I-D.xu-ospf-mpls-elc] | |||
| Xu, X., Kini, S., Sivabalan, S., Filsfils, C., and S. | Xu, X., Kini, S., Sivabalan, S., Filsfils, C., and S. | |||
| Litkowski, "Signaling Entropy Label Capability Using | Litkowski, "Signaling Entropy Label Capability Using | |||
| OSPF", draft-xu-ospf-mpls-elc-01 (work in progress), | OSPF", draft-xu-ospf-mpls-elc-01 (work in progress), | |||
| October 2014. | October 2014. | |||
| [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>. | ||||
| [RFC4206] Kompella, K. and Y. Rekhter, "Label Switched Paths (LSP) | [RFC4206] Kompella, K. and Y. Rekhter, "Label Switched Paths (LSP) | |||
| Hierarchy with Generalized Multi-Protocol Label Switching | Hierarchy with Generalized Multi-Protocol Label Switching | |||
| (GMPLS) Traffic Engineering (TE)", RFC 4206, October 2005. | (GMPLS) Traffic Engineering (TE)", RFC 4206, | |||
| DOI 10.17487/RFC4206, October 2005, | ||||
| <http://www.rfc-editor.org/info/rfc4206>. | ||||
| [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>. | ||||
| 9.2. Informative References | 9.2. Informative References | |||
| [I-D.filsfils-spring-segment-routing-use-cases] | [I-D.filsfils-spring-segment-routing-use-cases] | |||
| Filsfils, C., Francois, P., Previdi, S., Decraene, B., | Filsfils, C., Francois, P., Previdi, S., Decraene, B., | |||
| Litkowski, S., Horneffer, M., Milojevic, I., Shakir, R., | Litkowski, S., Horneffer, M., Milojevic, I., Shakir, R., | |||
| Ytti, S., Henderickx, W., Tantsura, J., Kini, S., and E. | Ytti, S., Henderickx, W., Tantsura, J., Kini, S., and E. | |||
| Crabbe, "Segment Routing Use Cases", draft-filsfils- | Crabbe, "Segment Routing Use Cases", draft-filsfils- | |||
| spring-segment-routing-use-cases-01 (work in progress), | spring-segment-routing-use-cases-01 (work in progress), | |||
| October 2014. | October 2014. | |||
| [I-D.ietf-isis-segment-routing-extensions] | [I-D.ietf-isis-segment-routing-extensions] | |||
| Previdi, S., Filsfils, C., Bashandy, A., Gredler, H., | Previdi, S., Filsfils, C., Bashandy, A., Gredler, H., | |||
| Litkowski, S., Decraene, B., and J. Tantsura, "IS-IS | Litkowski, S., Decraene, B., and J. Tantsura, "IS-IS | |||
| Extensions for Segment Routing", draft-ietf-isis-segment- | Extensions for Segment Routing", draft-ietf-isis-segment- | |||
| routing-extensions-03 (work in progress), October 2014. | routing-extensions-05 (work in progress), June 2015. | |||
| [I-D.ietf-ospf-segment-routing-extensions] | [I-D.ietf-ospf-segment-routing-extensions] | |||
| Psenak, P., Previdi, S., Filsfils, C., Gredler, H., | Psenak, P., Previdi, S., Filsfils, C., Gredler, H., | |||
| Shakir, R., Henderickx, W., and J. Tantsura, "OSPF | Shakir, R., Henderickx, W., and J. Tantsura, "OSPF | |||
| Extensions for Segment Routing", draft-ietf-ospf-segment- | Extensions for Segment Routing", draft-ietf-ospf-segment- | |||
| routing-extensions-04 (work in progress), February 2015. | routing-extensions-05 (work in progress), June 2015. | |||
| [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 | |||
| Sriganesh Kini (editor) | Sriganesh Kini (editor) | |||
| Ericsson | Ericsson | |||
| Email: sriganesh.kini@ericsson.com | Email: sriganesh.kini@ericsson.com | |||
| Kireeti Kompella | Kireeti Kompella | |||
| Juniper | Juniper | |||
| skipping to change at page 11, line 28 ¶ | skipping to change at page 11, line 28 ¶ | |||
| Cisco | Cisco | |||
| Email: msiva@cisco.com | Email: msiva@cisco.com | |||
| Stephane Litkowski | Stephane Litkowski | |||
| Orange | Orange | |||
| Email: stephane.litkowski@orange.com | Email: stephane.litkowski@orange.com | |||
| Rob Shakir | Rob Shakir | |||
| B.T. | ||||
| Email: rob.shakir@bt.com | Email: rjs@rob.sh | |||
| Xiaohu Xu | Xiaohu Xu | |||
| Huawei | Huawei | |||
| Email: xuxiaohu@huawei.com | Email: xuxiaohu@huawei.com | |||
| Wim Hendrickx | Wim Hendrickx | |||
| Alcatel-Lucent | Alcatel-Lucent | |||
| Email: wim.henderickx@alcatel-lucent.com | Email: wim.henderickx@alcatel-lucent.com | |||
| End of changes. 16 change blocks. | ||||
| 27 lines changed or deleted | 24 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/ | ||||