| < draft-ietf-mpls-spring-entropy-label-07.txt | draft-ietf-mpls-spring-entropy-label-08.txt > | |||
|---|---|---|---|---|
| Network Working Group S. Kini | Network Working Group S. Kini | |||
| Internet-Draft | Internet-Draft | |||
| Intended status: Informational K. Kompella | Intended status: Informational K. Kompella | |||
| Expires: April 20, 2018 Juniper | Expires: August 3, 2018 Juniper | |||
| S. Sivabalan | S. Sivabalan | |||
| Cisco | Cisco | |||
| S. Litkowski | S. Litkowski | |||
| Orange | Orange | |||
| R. Shakir | R. Shakir | |||
| J. Tantsura | J. Tantsura | |||
| October 17, 2017 | January 30, 2018 | |||
| Entropy label for SPRING tunnels | Entropy label for SPRING tunnels | |||
| draft-ietf-mpls-spring-entropy-label-07 | draft-ietf-mpls-spring-entropy-label-08 | |||
| Abstract | Abstract | |||
| Segment Routing (SR) leverages the source routing paradigm. A node | Segment Routing (SR) leverages the source routing paradigm. A node | |||
| steers a packet through an ordered list of instructions, called | steers a packet through an ordered list of instructions, called | |||
| segments. Segment Routing can be applied to the Multi Protocol Label | segments. Segment Routing can be applied to the Multi Protocol Label | |||
| Switching (MPLS) data plane. Entropy label (EL) is a technique used | Switching (MPLS) data plane. Entropy label (EL) is a technique used | |||
| in MPLS to improve load-balancing. This document examines and | in MPLS to improve load-balancing. This document examines and | |||
| describes how ELs are to be applied to Segment Routing when applied | describes how ELs are to be applied to Segment Routing when applied | |||
| to the MPLS dataplane. | to the MPLS dataplane. | |||
| skipping to change at page 1, line 44 ¶ | skipping to change at page 1, line 44 ¶ | |||
| 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 https://datatracker.ietf.org/drafts/current/. | Drafts is at https://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 April 20, 2018. | This Internet-Draft will expire on August 3, 2018. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2017 IETF Trust and the persons identified as the | Copyright (c) 2018 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 | |||
| (https://trustee.ietf.org/license-info) in effect on the date of | (https://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 3, line 12 ¶ | skipping to change at page 3, line 12 ¶ | |||
| 10.3. A re-usable EL for a stack of tunnels . . . . . . . . . 19 | 10.3. A re-usable EL for a stack of tunnels . . . . . . . . . 19 | |||
| 10.4. EL at top of stack . . . . . . . . . . . . . . . . . . . 19 | 10.4. EL at top of stack . . . . . . . . . . . . . . . . . . . 19 | |||
| 10.5. ELs at readable label stack depths . . . . . . . . . . . 20 | 10.5. ELs at readable label stack depths . . . . . . . . . . . 20 | |||
| 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 20 | 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 20 | |||
| 12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 20 | 12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 20 | |||
| 13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21 | 13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21 | |||
| 14. Security Considerations . . . . . . . . . . . . . . . . . . . 21 | 14. Security Considerations . . . . . . . . . . . . . . . . . . . 21 | |||
| 15. References . . . . . . . . . . . . . . . . . . . . . . . . . 21 | 15. References . . . . . . . . . . . . . . . . . . . . . . . . . 21 | |||
| 15.1. Normative References . . . . . . . . . . . . . . . . . . 21 | 15.1. Normative References . . . . . . . . . . . . . . . . . . 21 | |||
| 15.2. Informative References . . . . . . . . . . . . . . . . . 22 | 15.2. Informative References . . . . . . . . . . . . . . . . . 22 | |||
| Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23 | Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22 | |||
| 1. Introduction | 1. Introduction | |||
| Segment Routing [I-D.ietf-spring-segment-routing] is based on source | Segment Routing [I-D.ietf-spring-segment-routing] is based on source | |||
| routed tunnels to steer a packet along a particular path. This path | routed tunnels to steer a packet along a particular path. This path | |||
| is encoded as an ordered list of segments. When applied to the MPLS | is encoded as an ordered list of segments. When applied to the MPLS | |||
| dataplane [I-D.ietf-spring-segment-routing-mpls], each segment is an | dataplane [I-D.ietf-spring-segment-routing-mpls], each segment is an | |||
| LSP with an associated MPLS label value. Hence, label stacking is | LSP with an associated MPLS label value. Hence, label stacking is | |||
| used to represent the ordered list of segments and the label stack | used to represent the ordered list of segments and the label stack | |||
| associated with an SR tunnel can be seen as nested LSPs (LSP | associated with an SR tunnel can be seen as nested LSPs (LSP | |||
| skipping to change at page 3, line 44 ¶ | skipping to change at page 3, line 44 ¶ | |||
| A use-case requiring load-balancing with SR is given in Section 3. A | A use-case requiring load-balancing with SR is given in Section 3. A | |||
| recommended solution is described in Section 7 keeping in | recommended solution is described in Section 7 keeping in | |||
| consideration the limitations of implementations when applying | consideration the limitations of implementations when applying | |||
| [RFC6790] to deeper label stacks. Options that were considered to | [RFC6790] to deeper label stacks. Options that were considered to | |||
| arrive at the recommended solution are documented for historical | arrive at the recommended solution are documented for historical | |||
| purposes in Section 10. | purposes in Section 10. | |||
| 1.1. Requirements Language | 1.1. 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", "NOT RECOMMENDED", "MAY", and | |||
| document are to be interpreted as described in [RFC2119]. | "OPTIONAL" in this document are to be interpreted as described in BCP | |||
| 14 [RFC2119] [RFC8174] when, and only when, they appear in all | ||||
| Although this document is not a protocol specification, the use of | capitals, as shown here. | |||
| this language clarifies the instructions to protocol designers | ||||
| producing solutions that satisfy the requirements set out in this | ||||
| document. | ||||
| 2. Abbreviations and Terminology | 2. Abbreviations and Terminology | |||
| EL - Entropy Label | EL - Entropy Label | |||
| ELI - Entropy Label Identifier | ELI - Entropy Label Identifier | |||
| ELC - Entropy Label Capability | ELC - Entropy Label Capability | |||
| ERLD - Entropy Readable Label Depth | ERLD - Entropy Readable Label Depth | |||
| skipping to change at page 22, line 11 ¶ | skipping to change at page 22, line 11 ¶ | |||
| L. Yong, "The Use of Entropy Labels in MPLS Forwarding", | L. Yong, "The Use of Entropy Labels in MPLS Forwarding", | |||
| RFC 6790, DOI 10.17487/RFC6790, November 2012, | RFC 6790, DOI 10.17487/RFC6790, November 2012, | |||
| <https://www.rfc-editor.org/info/rfc6790>. | <https://www.rfc-editor.org/info/rfc6790>. | |||
| [RFC7855] Previdi, S., Ed., Filsfils, C., Ed., Decraene, B., | [RFC7855] Previdi, S., Ed., Filsfils, C., Ed., Decraene, B., | |||
| Litkowski, S., Horneffer, M., and R. Shakir, "Source | Litkowski, S., Horneffer, M., and R. Shakir, "Source | |||
| Packet Routing in Networking (SPRING) Problem Statement | Packet Routing in Networking (SPRING) Problem Statement | |||
| and Requirements", RFC 7855, DOI 10.17487/RFC7855, May | and Requirements", RFC 7855, DOI 10.17487/RFC7855, May | |||
| 2016, <https://www.rfc-editor.org/info/rfc7855>. | 2016, <https://www.rfc-editor.org/info/rfc7855>. | |||
| [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC | ||||
| 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, | ||||
| May 2017, <https://www.rfc-editor.org/info/rfc8174>. | ||||
| [I-D.ietf-spring-segment-routing] | [I-D.ietf-spring-segment-routing] | |||
| Filsfils, C., Previdi, S., Decraene, B., Litkowski, S., | Filsfils, C., Previdi, S., Ginsberg, L., Decraene, B., | |||
| and R. Shakir, "Segment Routing Architecture", draft-ietf- | Litkowski, S., and R. Shakir, "Segment Routing | |||
| spring-segment-routing-12 (work in progress), June 2017. | Architecture", draft-ietf-spring-segment-routing-15 (work | |||
| in progress), January 2018. | ||||
| [I-D.ietf-spring-segment-routing-mpls] | [I-D.ietf-spring-segment-routing-mpls] | |||
| Filsfils, C., Previdi, S., Bashandy, A., Decraene, B., | Filsfils, C., Previdi, S., Bashandy, A., Decraene, B., | |||
| Litkowski, S., and R. Shakir, "Segment Routing with MPLS | Litkowski, S., and R. Shakir, "Segment Routing with MPLS | |||
| data plane", draft-ietf-spring-segment-routing-mpls-10 | data plane", draft-ietf-spring-segment-routing-mpls-11 | |||
| (work in progress), June 2017. | (work in progress), October 2017. | |||
| 15.2. Informative References | 15.2. Informative References | |||
| [RFC4206] Kompella, K. and Y. Rekhter, "Label Switched Paths (LSP) | ||||
| Hierarchy with Generalized Multi-Protocol Label Switching | ||||
| (GMPLS) Traffic Engineering (TE)", RFC 4206, | ||||
| DOI 10.17487/RFC4206, October 2005, | ||||
| <https://www.rfc-editor.org/info/rfc4206>. | ||||
| [RFC7325] Villamizar, C., Ed., Kompella, K., Amante, S., Malis, A., | ||||
| and C. Pignataro, "MPLS Forwarding Compliance and | ||||
| Performance Requirements", RFC 7325, DOI 10.17487/RFC7325, | ||||
| August 2014, <https://www.rfc-editor.org/info/rfc7325>. | ||||
| [I-D.ietf-isis-mpls-elc] | [I-D.ietf-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 and | |||
| IS", draft-ietf-isis-mpls-elc-02 (work in progress), | Readable Label-stack Depth Using IS-IS", draft-ietf-isis- | |||
| October 2016. | mpls-elc-03 (work in progress), January 2018. | |||
| [I-D.ietf-ospf-mpls-elc] | [I-D.ietf-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 and | |||
| OSPF", draft-ietf-ospf-mpls-elc-04 (work in progress), | Readable Label-stack Depth Using OSPF", draft-ietf-ospf- | |||
| November 2016. | mpls-elc-05 (work in progress), January 2018. | |||
| [I-D.ietf-isis-l2bundles] | [I-D.ietf-isis-l2bundles] | |||
| Ginsberg, L., Bashandy, A., Filsfils, C., Nanduri, M., and | Ginsberg, L., Bashandy, A., Filsfils, C., Nanduri, M., and | |||
| E. Aries, "Advertising L2 Bundle Member Link Attributes in | E. Aries, "Advertising L2 Bundle Member Link Attributes in | |||
| IS-IS", draft-ietf-isis-l2bundles-07 (work in progress), | IS-IS", draft-ietf-isis-l2bundles-07 (work in progress), | |||
| May 2017. | May 2017. | |||
| Authors' Addresses | Authors' Addresses | |||
| Sriganesh Kini | Sriganesh Kini | |||
| End of changes. 13 change blocks. | ||||
| 35 lines changed or deleted | 26 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/ | ||||