| < draft-ietf-rtgwg-bgp-pic-16.txt | draft-ietf-rtgwg-bgp-pic-17.txt > | |||
|---|---|---|---|---|
| Network Working Group A. Bashandy, Ed. | Network Working Group A. Bashandy, Ed. | |||
| Internet Draft Individual Contributor | Internet Draft Individual Contributor | |||
| Intended status: Informational C. Filsfils | Intended status: Informational C. Filsfils | |||
| Expires: March 2022 Cisco Systems | Expires: April 2022 Cisco Systems | |||
| P. Mohapatra | P. Mohapatra | |||
| Sproute Networks | Sproute Networks | |||
| September 26, 2021 | October 12, 2021 | |||
| BGP Prefix Independent Convergence | BGP Prefix Independent Convergence | |||
| draft-ietf-rtgwg-bgp-pic-16.txt | draft-ietf-rtgwg-bgp-pic-17.txt | |||
| Abstract | Abstract | |||
| In a network comprising thousands of BGP peers exchanging millions of | In a network comprising thousands of BGP peers exchanging millions of | |||
| routes, many routes are reachable via more than one next-hop. Given | routes, many routes are reachable via more than one next-hop. Given | |||
| the large scaling targets, it is desirable to restore traffic after | the large scaling targets, it is desirable to restore traffic after | |||
| failure in a time period that does not depend on the number of BGP | failure in a time period that does not depend on the number of BGP | |||
| prefixes. In this document we proposed an architecture by which | prefixes. In this document we proposed an architecture by which | |||
| traffic can be re-routed to ECMP or pre-calculated backup paths in a | traffic can be re-routed to ECMP or pre-calculated backup paths in a | |||
| timeframe that does not depend on the number of BGP prefixes. The | timeframe that does not depend on the number of BGP prefixes. The | |||
| skipping to change at page 2, line 7 ¶ | skipping to change at page 2, line 7 ¶ | |||
| months and may be updated, replaced, or obsoleted by other | months and may be updated, replaced, or obsoleted by other | |||
| documents at any time. It is inappropriate to use Internet-Drafts | documents at any time. It is inappropriate to use Internet-Drafts | |||
| as reference material or to cite them other than as "work in | as reference material or to cite them other than as "work in | |||
| progress." | progress." | |||
| The list of current Internet-Drafts can be accessed at | The list of current Internet-Drafts can be accessed at | |||
| http://www.ietf.org/ietf/1id-abstracts.txt | http://www.ietf.org/ietf/1id-abstracts.txt | |||
| The list of Internet-Draft Shadow Directories can be accessed at | The list of Internet-Draft Shadow Directories can be accessed at | |||
| http://www.ietf.org/shadow.html | http://www.ietf.org/shadow.html | |||
| This Internet-Draft will expire on March 26, 2022. | This Internet-Draft will expire on April 12, 2022. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2021 IETF Trust and the persons identified as the | Copyright (c) 2021 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 9, line 28 ¶ | skipping to change at page 9, line 28 ¶ | |||
| minimizes the re-convergence time on topology change, there will | minimizes the re-convergence time on topology change, there will | |||
| always exist platforms with limited capabilities and hence imposing | always exist platforms with limited capabilities and hence imposing | |||
| a limit on the depth of the forwarding chain. Section 5 describes | a limit on the depth of the forwarding chain. Section 5 describes | |||
| how to gracefully trade off convergence speed with the number of | how to gracefully trade off convergence speed with the number of | |||
| hierarchical levels to support platforms with different | hierarchical levels to support platforms with different | |||
| capabilities. | capabilities. | |||
| Another example using IPv6 addresses can be something like the | Another example using IPv6 addresses can be something like the | |||
| following | following | |||
| 65000: 2003:DBB:1::/48 | 65000: 2001:DB8:1::/48 | |||
| via ePE1 (192::1), VPN Label: VPN6-L11 | via ePE1 (192::1), VPN Label: VPN6-L11 | |||
| via ePE2 (192::2), VPN Label: VPN6-L21 | via ePE2 (192::2), VPN Label: VPN6-L21 | |||
| 65000: 2003:DBB:2:/48 | 65000: 2001:DB8:2:/48 | |||
| via ePE1 (192::1), VPN Label: VPN6-L12 | via ePE1 (192::1), VPN Label: VPN6-L12 | |||
| via ePE2 (192::2), VPN Label: VPN6-L22 | via ePE2 (192::2), VPN Label: VPN6-L22 | |||
| 192::1/128 | 192::1/128 | |||
| via Core, Label: IGP6-L11 | via Core, Label: IGP6-L11 | |||
| via Core, Label: IGP6-L12 | via Core, Label: IGP6-L12 | |||
| 192::2/128 | 192::2/128 | |||
| via Core, Label: IGP6-L21 | via Core, Label: IGP6-L21 | |||
| via Core, Label: IGP6-L22 | via Core, Label: IGP6-L22 | |||
| End of changes. 6 change blocks. | ||||
| 6 lines changed or deleted | 6 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/ | ||||