| < draft-bryant-rtgwg-plfa-03.txt | draft-bryant-rtgwg-plfa-04.txt > | |||
|---|---|---|---|---|
| Routing Area Working Group S. Bryant | Routing Area Working Group S. Bryant | |||
| Internet-Draft University of Surrey | Internet-Draft University of Surrey ICS | |||
| Intended status: Informational U. Chunduri | Intended status: Informational U. Chunduri | |||
| Expires: June 27, 2022 Intel | Expires: November 10, 2022 Intel | |||
| T. Eckert | T. Eckert | |||
| Futurewei Technologies Inc | Futurewei Technologies Inc | |||
| December 24, 2021 | May 09, 2022 | |||
| Preferred Path Loop-Free Alternate (pLFA) | Preferred Path Loop-Free Alternate (pLFA) | |||
| draft-bryant-rtgwg-plfa-03 | draft-bryant-rtgwg-plfa-04 | |||
| Abstract | Abstract | |||
| Fast re-route (FRR) is a technique that allows productive forwarding | Fast re-route (FRR) is a technique that allows productive forwarding | |||
| to continue in a network after a failure has occurred, but before the | to continue in a network after a failure has occurred, but before the | |||
| network has has time to re-converge. This is achieved by forwarding | network has has time to re-converge. This is achieved by forwarding | |||
| a packet on an alternate path that will not result in the packet | a packet on an alternate path that will not result in the packet | |||
| looping. Preferred Path Routing (PPR) provides a method of injecting | looping. Preferred Path Routing (PPR) provides a method of injecting | |||
| explicit paths into the routing protocol. The use of PPR to support | explicit paths into the routing protocol. The use of PPR to support | |||
| FRR has a number of advantages. This document describes the | FRR has a number of advantages. This document describes the | |||
| skipping to change at page 1, line 41 ¶ | skipping to change at page 1, line 41 ¶ | |||
| 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 June 27, 2022. | This Internet-Draft will expire on November 10, 2022. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2021 IETF Trust and the persons identified as the | Copyright (c) 2022 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 18, line 16 ¶ | skipping to change at page 18, line 16 ¶ | |||
| [I-D.bryant-ipfrr-tunnels] | [I-D.bryant-ipfrr-tunnels] | |||
| Bryant, S., Filsfils, C., Previdi, S., and M. Shand, "IP | Bryant, S., Filsfils, C., Previdi, S., and M. Shand, "IP | |||
| Fast Reroute using tunnels", draft-bryant-ipfrr-tunnels-03 | Fast Reroute using tunnels", draft-bryant-ipfrr-tunnels-03 | |||
| (work in progress), November 2007. | (work in progress), November 2007. | |||
| [I-D.ietf-rtgwg-segment-routing-ti-lfa] | [I-D.ietf-rtgwg-segment-routing-ti-lfa] | |||
| Litkowski, S., Bashandy, A., Filsfils, C., Francois, P., | Litkowski, S., Bashandy, A., Filsfils, C., Francois, P., | |||
| Decraene, B., and D. Voyer, "Topology Independent Fast | Decraene, B., and D. Voyer, "Topology Independent Fast | |||
| Reroute using Segment Routing", draft-ietf-rtgwg-segment- | Reroute using Segment Routing", draft-ietf-rtgwg-segment- | |||
| routing-ti-lfa-07 (work in progress), June 2021. | routing-ti-lfa-08 (work in progress), January 2022. | |||
| [I-D.xu-isis-encapsulation-cap] | [I-D.xu-isis-encapsulation-cap] | |||
| Xu, X., Decraene, B., Raszuk, R., Chunduri, U., Contreras, | Xu, X., Decraene, B., Raszuk, R., Chunduri, U., Contreras, | |||
| L. M., and L. Jalil, "Advertising Tunnelling Capability in | L. M., and L. Jalil, "Advertising Tunnelling Capability in | |||
| IS-IS", draft-xu-isis-encapsulation-cap-07 (work in | IS-IS", draft-xu-isis-encapsulation-cap-07 (work in | |||
| progress), October 2016. | progress), October 2016. | |||
| [RFC3936] Kompella, K. and J. Lang, "Procedures for Modifying the | [RFC3936] Kompella, K. and J. Lang, "Procedures for Modifying the | |||
| Resource reSerVation Protocol (RSVP)", BCP 96, RFC 3936, | Resource reSerVation Protocol (RSVP)", BCP 96, RFC 3936, | |||
| DOI 10.17487/RFC3936, October 2004, | DOI 10.17487/RFC3936, October 2004, | |||
| skipping to change at page 19, line 43 ¶ | skipping to change at page 19, line 43 ¶ | |||
| March 2019, <https://www.rfc-editor.org/info/rfc8518>. | March 2019, <https://www.rfc-editor.org/info/rfc8518>. | |||
| [RFC8754] Filsfils, C., Ed., Dukes, D., Ed., Previdi, S., Leddy, J., | [RFC8754] Filsfils, C., Ed., Dukes, D., Ed., Previdi, S., Leddy, J., | |||
| Matsushima, S., and D. Voyer, "IPv6 Segment Routing Header | Matsushima, S., and D. Voyer, "IPv6 Segment Routing Header | |||
| (SRH)", RFC 8754, DOI 10.17487/RFC8754, March 2020, | (SRH)", RFC 8754, DOI 10.17487/RFC8754, March 2020, | |||
| <https://www.rfc-editor.org/info/rfc8754>. | <https://www.rfc-editor.org/info/rfc8754>. | |||
| Authors' Addresses | Authors' Addresses | |||
| Stewart Bryant | Stewart Bryant | |||
| University of Surrey | University of Surrey ICS | |||
| Email: sb@stewartbryant.com | Email: sb@stewartbryant.com | |||
| Uma Chunduri | Uma Chunduri | |||
| Intel | Intel | |||
| Email: umac.ietf@gmail.com | Email: umac.ietf@gmail.com | |||
| Toerless Eckert | Toerless Eckert | |||
| Futurewei Technologies Inc | Futurewei Technologies Inc | |||
| End of changes. 8 change blocks. | ||||
| 8 lines changed or deleted | 8 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/ | ||||