| < draft-chunduri-lsr-ospf-preferred-path-routing-01.txt | draft-chunduri-lsr-ospf-preferred-path-routing-02.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: January 3, 2019 R. White | Expires: August 18, 2019 R. White | |||
| Juniper Networks | ||||
| J. Tantsura | J. Tantsura | |||
| Nuage Networks | Apstra Inc. | |||
| L. Contreras | L. Contreras | |||
| Telefonica | Telefonica | |||
| July 2, 2018 | February 14, 2019 | |||
| Preferred Path Routing (PPR) in OSPF | Preferred Path Routing (PPR) in OSPF | |||
| draft-chunduri-lsr-ospf-preferred-path-routing-01 | draft-chunduri-lsr-ospf-preferred-path-routing-02 | |||
| Abstract | Abstract | |||
| This document specifies a Preferred Path Routing (PPR) mechanism to | This document specifies a Preferred Path Routing (PPR), a routing | |||
| simplify the path description of data plane traffic in Segment | protocol mechanism to simplify the path description of data plane | |||
| Routing (SR) deployments with OSPFv2 and OSPFv3 protocols. PPR aims | traffic in Segment Routing (SR) deployments with OSPFv2 and OSPFv3 | |||
| to mitigate the MTU and data plane processing issues that may result | protocols. PPR aims to mitigate the MTU and data plane processing | |||
| from SR packet overheads; and also supports traffic measurement, | issues that may result from SR packet overheads; and also supports | |||
| accounting statistics and further attribute extensions along the | traffic measurement, accounting statistics and further attribute | |||
| paths. Preferred Path Routing is achieved through the addition of | extensions along the paths. Preferred Path Routing is achieved | |||
| descriptions to OSPF advertised prefixes, and mapping those to a PPR | through the addition of descriptions to OSPF advertised prefixes, and | |||
| data-plane identifier. | mapping those to a PPR 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 | RFC8174 [RFC8174] when, and only when they appear in all capitals, as | |||
| shown here". | shown here". | |||
| Status of This Memo | Status of This Memo | |||
| skipping to change at page 2, line 7 ¶ | skipping to change at page 2, line 7 ¶ | |||
| 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 January 3, 2019. | This Internet-Draft will expire on August 18, 2019. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2018 IETF Trust and the persons identified as the | Copyright (c) 2019 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 19, line 46 ¶ | skipping to change at page 19, line 46 ¶ | |||
| [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC | [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC | |||
| 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, | 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, | |||
| May 2017, <https://www.rfc-editor.org/info/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-01 (work in | |||
| progress), June 2018. | progress), July 2018. | |||
| [I-D.ietf-6man-segment-routing-header] | [I-D.ietf-6man-segment-routing-header] | |||
| Filsfils, C., Previdi, S., 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-14 (work in | (SRH)", draft-ietf-6man-segment-routing-header-16 (work in | |||
| progress), June 2018. | progress), February 2019. | |||
| [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. and S. Previdi, "OSPFv3 Extensions for Segment | |||
| Shakir, R., Henderickx, W., and J. Tantsura, "OSPFv3 | Routing", draft-ietf-ospf-ospfv3-segment-routing- | |||
| Extensions for Segment Routing", draft-ietf-ospf-ospfv3- | extensions-23 (work in progress), January 2019. | |||
| segment-routing-extensions-13 (work in progress), May | ||||
| 2018. | ||||
| [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-25 (work in progress), April 2018. | routing-extensions-27 (work in progress), December 2018. | |||
| [I-D.ietf-spring-segment-routing] | [I-D.ietf-spring-segment-routing] | |||
| Filsfils, C., Previdi, S., Ginsberg, L., Decraene, B., | Filsfils, C., Previdi, S., Ginsberg, L., Decraene, B., | |||
| Litkowski, S., and R. Shakir, "Segment Routing | Litkowski, S., and R. Shakir, "Segment Routing | |||
| Architecture", draft-ietf-spring-segment-routing-15 (work | Architecture", draft-ietf-spring-segment-routing-15 (work | |||
| in progress), January 2018. | in progress), January 2018. | |||
| [I-D.li-ospf-ospfv3-srv6-extensions] | [I-D.li-ospf-ospfv3-srv6-extensions] | |||
| Li, Z., Hu, Z., Cheng, D., Talaulikar, K., and P. Psenak, | Li, Z., Hu, Z., Cheng, D., Talaulikar, K., and P. Psenak, | |||
| "OSPFv3 Extensions for SRv6", draft-li-ospf- | "OSPFv3 Extensions for SRv6", draft-li-ospf- | |||
| ospfv3-srv6-extensions-01 (work in progress), March 2018. | ospfv3-srv6-extensions-02 (work in progress), September | |||
| 2018. | ||||
| [RFC4915] Psenak, P., Mirtorabi, S., Roy, A., Nguyen, L., and P. | [RFC4915] Psenak, P., Mirtorabi, S., Roy, A., Nguyen, L., and P. | |||
| Pillay-Esnault, "Multi-Topology (MT) Routing in OSPF", | Pillay-Esnault, "Multi-Topology (MT) Routing in OSPF", | |||
| RFC 4915, DOI 10.17487/RFC4915, June 2007, | RFC 4915, DOI 10.17487/RFC4915, June 2007, | |||
| <https://www.rfc-editor.org/info/rfc4915>. | <https://www.rfc-editor.org/info/rfc4915>. | |||
| [RFC7474] Bhatia, M., Hartman, S., Zhang, D., and A. Lindem, Ed., | [RFC7474] Bhatia, M., Hartman, S., Zhang, D., and A. Lindem, Ed., | |||
| "Security Extension for OSPFv2 When Using Manual Key | "Security Extension for OSPFv2 When Using Manual Key | |||
| Management", RFC 7474, DOI 10.17487/RFC7474, April 2015, | Management", RFC 7474, DOI 10.17487/RFC7474, April 2015, | |||
| <https://www.rfc-editor.org/info/rfc7474>. | <https://www.rfc-editor.org/info/rfc7474>. | |||
| skipping to change at page 21, line 29 ¶ | skipping to change at page 21, line 24 ¶ | |||
| Yingzhen Qu | Yingzhen Qu | |||
| Huawei USA | Huawei USA | |||
| 2330 Central Expressway | 2330 Central Expressway | |||
| Santa Clara, CA 95050 | Santa Clara, CA 95050 | |||
| USA | USA | |||
| Email: yingzhen.qu@huawei.com | Email: yingzhen.qu@huawei.com | |||
| Russ White | Russ White | |||
| Juniper Networks | ||||
| Oak Island, NC 28465 | Oak Island, NC 28465 | |||
| USA | USA | |||
| Email: russ@riw.us | Email: russ@riw.us | |||
| Jeff Tantsura | Jeff Tantsura | |||
| Nuage Networks | Apstra Inc. | |||
| 755 Ravendale Drive | 333 Middlefield Road | |||
| Mountain View, CA 94043 | Menlo Park, CA 94025 | |||
| USA | USA | |||
| Email: jefftant.ietf@gmail.com | Email: jefftant.ietf@gmail.com | |||
| Luis M. Contreras | Luis M. Contreras | |||
| Telefonica | Telefonica | |||
| Sur-3 building, 3rd floor | Sur-3 building, 3rd floor | |||
| Madrid 28050 | Madrid 28050 | |||
| Spain | Spain | |||
| Email: luismiguel.contrerasmurillo@telefonica.com | Email: luismiguel.contrerasmurillo@telefonica.com | |||
| End of changes. 15 change blocks. | ||||
| 31 lines changed or deleted | 31 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/ | ||||