| < draft-chunduri-lsr-ospf-preferred-path-routing-00.txt | draft-chunduri-lsr-ospf-preferred-path-routing-01.txt > | |||
|---|---|---|---|---|
| LSR Working Group U. Chunduri | LSR Working Group U. Chunduri | |||
| Internet-Draft Y. Qu | Internet-Draft Y. Qu | |||
| Intended status: Standards Track Huawei USA | Intended status: Standards Track Huawei USA | |||
| Expires: December 21, 2018 R. White | Expires: January 3, 2019 R. White | |||
| J. Tantsura | J. Tantsura | |||
| Nuage Networks | Nuage Networks | |||
| L. Contreras | L. Contreras | |||
| Telefonica | Telefonica | |||
| June 19, 2018 | July 2, 2018 | |||
| Preferred Path Routing (PPR) in OSPF | Preferred Path Routing (PPR) in OSPF | |||
| draft-chunduri-lsr-ospf-preferred-path-routing-00 | draft-chunduri-lsr-ospf-preferred-path-routing-01 | |||
| Abstract | Abstract | |||
| This document specifies a Preferred Path Routing (PPR) mechanism to | This document specifies a Preferred Path Routing (PPR) mechanism to | |||
| simplify the path description of data plane traffic in Segment | simplify the path description of data plane traffic in Segment | |||
| Routing (SR) deployments with OSPFv2 and OSPFv3 protocols. PPR aims | Routing (SR) deployments with OSPFv2 and OSPFv3 protocols. PPR aims | |||
| to mitigate the MTU and data plane processing issues that may result | to mitigate the MTU and data plane processing issues that may result | |||
| from SR packet overheads; and also supports traffic measurement, | from SR packet overheads; and also supports traffic measurement, | |||
| accounting statistics and further attribute extensions along the | accounting statistics and further attribute extensions along the | |||
| paths. Preferred Path Routing is achieved through the addition of | paths. Preferred Path Routing is achieved through the addition of | |||
| descriptions to OSPF advertised prefixes, and mapping those to a PPR | descriptions to OSPF advertised prefixes, and mapping those to a PPR | |||
| data-plane identifier. | data-plane identifier. | |||
| 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 RFC2119 [RFC2119]. | document are to be interpreted as described in RFC2119 [RFC2119], | |||
| RFC8174 [RFC8174] when, and only when they appear in all capitals, as | ||||
| shown here". | ||||
| 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 | |||
| provisions of BCP 78 and BCP 79. | provisions of BCP 78 and BCP 79. | |||
| 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 December 21, 2018. | ||||
| This Internet-Draft will expire on January 3, 2019. | ||||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2018 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 | |||
| described in the Simplified BSD License. | described in the Simplified BSD License. | |||
| Table of Contents | Table of Contents | |||
| 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 | 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 | |||
| 1.1. Acronyms . . . . . . . . . . . . . . . . . . . . . . . . 3 | 1.1. Acronyms . . . . . . . . . . . . . . . . . . . . . . . . 3 | |||
| 2. OSPFv2 PPR TLV . . . . . . . . . . . . . . . . . . . . . . . 4 | 2. OSPFv2 PPR TLV . . . . . . . . . . . . . . . . . . . . . . . 4 | |||
| 2.1. PPR-Flags . . . . . . . . . . . . . . . . . . . . . . . . 5 | 2.1. PPR-Flags . . . . . . . . . . . . . . . . . . . . . . . . 6 | |||
| 2.2. PPR-Prefix Sub-TLV . . . . . . . . . . . . . . . . . . . 6 | 2.2. PPR-Prefix Sub-TLV . . . . . . . . . . . . . . . . . . . 6 | |||
| 2.3. PPR-ID Sub-TLV . . . . . . . . . . . . . . . . . . . . . 7 | 2.3. PPR-ID Sub-TLV . . . . . . . . . . . . . . . . . . . . . 7 | |||
| 2.4. PPR-PDE Sub-TLV . . . . . . . . . . . . . . . . . . . . . 8 | 2.4. PPR-PDE Sub-TLV . . . . . . . . . . . . . . . . . . . . . 9 | |||
| 2.5. PPR-Attributes Sub-TLV . . . . . . . . . . . . . . . . . 10 | 2.5. PPR-Attributes Sub-TLV . . . . . . . . . . . . . . . . . 10 | |||
| 3. OSPFv3 PPR TLV . . . . . . . . . . . . . . . . . . . . . . . 11 | 3. OSPFv3 PPR TLV . . . . . . . . . . . . . . . . . . . . . . . 11 | |||
| 3.1. OSPFv3 PPR-Prefix Sub-TLV . . . . . . . . . . . . . . . . 12 | 3.1. OSPFv3 PPR-Prefix Sub-TLV . . . . . . . . . . . . . . . . 13 | |||
| 3.2. OSPFv3 PPR-ID Sub-TLVs . . . . . . . . . . . . . . . . . 13 | 3.2. OSPFv3 PPR-ID Sub-TLVs . . . . . . . . . . . . . . . . . 13 | |||
| 3.3. OSPFv3 PPR-PDE Sub-TLV . . . . . . . . . . . . . . . . . 15 | 3.3. OSPFv3 PPR-PDE Sub-TLV . . . . . . . . . . . . . . . . . 15 | |||
| 3.4. OSPFv3 PPR-Attributes Sub-TLV . . . . . . . . . . . . . . 17 | 3.4. OSPFv3 PPR-Attributes Sub-TLV . . . . . . . . . . . . . . 17 | |||
| 4. Other Considerations . . . . . . . . . . . . . . . . . . . . 18 | 4. Other Considerations . . . . . . . . . . . . . . . . . . . . 18 | |||
| 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 18 | 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 18 | |||
| 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 | 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 | |||
| 7. Security Considerations . . . . . . . . . . . . . . . . . . . 19 | 7. Security Considerations . . . . . . . . . . . . . . . . . . . 19 | |||
| 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 19 | 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 19 | |||
| 8.1. Normative References . . . . . . . . . . . . . . . . . . 19 | 8.1. Normative References . . . . . . . . . . . . . . . . . . 19 | |||
| 8.2. Informative References . . . . . . . . . . . . . . . . . 19 | 8.2. Informative References . . . . . . . . . . . . . . . . . 19 | |||
| skipping to change at page 18, line 26 ¶ | skipping to change at page 18, line 26 ¶ | |||
| o Type 3 (Suggested Value - IANA TBD): PPR-Metric Sub-TLV. Length 4 | o Type 3 (Suggested Value - IANA TBD): PPR-Metric Sub-TLV. Length 4 | |||
| bytes, and Value is metric of this path represented through the | bytes, and Value is metric of this path represented through the | |||
| PPR-ID. Different nodes can advertise the same PPR-ID for the | PPR-ID. Different nodes can advertise the same PPR-ID for the | |||
| same Prefix with a different set of PPR-PDE Sub-TLVs and the | same Prefix with a different set of PPR-PDE Sub-TLVs and the | |||
| receiving node MUST consider the lowest metric value (TBD more, on | receiving node MUST consider the lowest metric value (TBD more, on | |||
| what happens when metric is same for two different set of PPR-PDE | what happens when metric is same for two different set of PPR-PDE | |||
| Sub-TLVs). | Sub-TLVs). | |||
| 4. Other Considerations | 4. Other Considerations | |||
| Please refer to [I-D.chunduri-isis-preferred-path-routing] section 3, | Please refer to [I-D.chunduri-isis-preferred-path-routing] section 4, | |||
| 4 and 5. | 5, 6 and 7. | |||
| 5. Acknowledgements | 5. Acknowledgements | |||
| Thanks to Richard Li, Alex Clemm, Padma Pillay-Esnault, Toerless | Thanks to Richard Li, Alex Clemm, Padma Pillay-Esnault, Toerless | |||
| Eckert, Kiran Makhijani and Lin Han for initial discussions on this | Eckert, Kiran Makhijani and Lin Han for initial discussions on this | |||
| topic. Thanks to Kevin Smith and Stephen Johnson for various | topic. Thanks to Kevin Smith and Stephen Johnson for various | |||
| deployment scenarios applicability from ETSI WGs perspective. | deployment scenarios applicability from ETSI WGs perspective. | |||
| Authors also acknowledge Alexander Vainshtein for detailed | Authors also acknowledge Alexander Vainshtein for detailed | |||
| discussions and suggestions on this topic. | discussions and suggestions on this topic. | |||
| skipping to change at page 19, line 12 ¶ | skipping to change at page 19, line 12 ¶ | |||
| ----- -------------- | ----- -------------- | |||
| TBD PPR TLV | TBD PPR TLV | |||
| This document also requests IANA to create new registries for PPR TLV | This document also requests IANA to create new registries for PPR TLV | |||
| Flags field, PPR Flags, and PPR Sub-TLVs in PPR TLV as described in | Flags field, PPR Flags, and PPR Sub-TLVs in PPR TLV as described in | |||
| Section 2 and Section 3. | Section 2 and Section 3. | |||
| 7. Security Considerations | 7. Security Considerations | |||
| Existing security extensions as described in [RFC2328] and [RFC7684] | Existing security extensions as described in [RFC2328] and [RFC7684] | |||
| apply to these segment routing extensions. While OSPF is under a | apply to the extensions specified in this document. While OSPF is | |||
| single administrative domain, there can be deployments where | under a single administrative domain, there can be deployments where | |||
| potential attackers have access to one or more networks in the OSPF | potential attackers have access to one or more networks in the OSPF | |||
| routing domain. In these deployments, stronger authentication | routing domain. In these deployments, stronger authentication | |||
| mechanisms such as those specified in [RFC7474] SHOULD be used. | mechanisms such as those specified in [RFC7474] SHOULD be used. | |||
| Advertisement of the additional information defined in this document | Advertisement of the additional information defined in this document | |||
| introduces no new security concerns in OSPF protocol. However as | introduces no new security concerns in OSPF protocol. However as | |||
| this extension is related to SR-MPLS and SRH data planes as defined | this extension is related to SR-MPLS and SRH data planes as defined | |||
| in [I-D.ietf-spring-segment-routing], those particular data plane | in [I-D.ietf-spring-segment-routing], those particular data plane | |||
| security considerations does apply here. | security considerations does apply here. | |||
| skipping to change at page 19, line 37 ¶ | skipping to change at page 19, line 37 ¶ | |||
| [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, | Requirement Levels", BCP 14, RFC 2119, | |||
| DOI 10.17487/RFC2119, March 1997, | DOI 10.17487/RFC2119, March 1997, | |||
| <https://www.rfc-editor.org/info/rfc2119>. | <https://www.rfc-editor.org/info/rfc2119>. | |||
| [RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328, | [RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328, | |||
| DOI 10.17487/RFC2328, April 1998, | DOI 10.17487/RFC2328, April 1998, | |||
| <https://www.rfc-editor.org/info/rfc2328>. | <https://www.rfc-editor.org/info/rfc2328>. | |||
| [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>. | ||||
| 8.2. Informative References | 8.2. Informative References | |||
| [I-D.chunduri-lsr-isis-preferred-path-routing] | [I-D.chunduri-lsr-isis-preferred-path-routing] | |||
| Chunduri, U., Li, R., White, R., Tantsura, J., Contreras, | Chunduri, U., Li, R., White, R., Tantsura, J., Contreras, | |||
| L., and Y. Qu, "Preferred Path Routing (PPR) in IS-IS", | L., and Y. Qu, "Preferred Path Routing (PPR) in IS-IS", | |||
| draft-chunduri-lsr-isis-preferred-path-routing-00 (work in | draft-chunduri-lsr-isis-preferred-path-routing-00 (work in | |||
| progress), June 2018. | progress), June 2018. | |||
| [I-D.ietf-6man-segment-routing-header] | [I-D.ietf-6man-segment-routing-header] | |||
| Previdi, S., Filsfils, C., Leddy, J., Matsushima, S., and | Filsfils, C., Previdi, S., Leddy, J., Matsushima, S., and | |||
| d. daniel.voyer@bell.ca, "IPv6 Segment Routing Header | d. daniel.voyer@bell.ca, "IPv6 Segment Routing Header | |||
| (SRH)", draft-ietf-6man-segment-routing-header-13 (work in | (SRH)", draft-ietf-6man-segment-routing-header-14 (work in | |||
| progress), May 2018. | progress), June 2018. | |||
| [I-D.ietf-ospf-ospfv3-lsa-extend] | [I-D.ietf-ospf-ospfv3-lsa-extend] | |||
| Lindem, A., Roy, A., Goethals, D., Vallem, V., and F. | Lindem, A., Roy, A., Goethals, D., Vallem, V., and F. | |||
| Baker, "OSPFv3 LSA Extendibility", draft-ietf-ospf-ospfv3- | Baker, "OSPFv3 LSA Extendibility", draft-ietf-ospf-ospfv3- | |||
| lsa-extend-23 (work in progress), January 2018. | lsa-extend-23 (work in progress), January 2018. | |||
| [I-D.ietf-ospf-ospfv3-segment-routing-extensions] | [I-D.ietf-ospf-ospfv3-segment-routing-extensions] | |||
| Psenak, P., Filsfils, C., Previdi, S., Gredler, H., | Psenak, P., Filsfils, C., Previdi, S., Gredler, H., | |||
| Shakir, R., Henderickx, W., and J. Tantsura, "OSPFv3 | Shakir, R., Henderickx, W., and J. Tantsura, "OSPFv3 | |||
| Extensions for Segment Routing", draft-ietf-ospf-ospfv3- | Extensions for Segment Routing", draft-ietf-ospf-ospfv3- | |||
| End of changes. 14 change blocks. | ||||
| 16 lines changed or deleted | 23 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/ | ||||