Mostrar el registro sencillo del ítem
Loop-free convergence using oFIB
| dc.contributor.author | Shand, Mike | |
| dc.contributor.author | Bryant, Stewart | |
| dc.contributor.author | Previdi, Stefano | |
| dc.contributor.author | Filsfils, Clarence | |
| dc.contributor.author | Francois, Pierre | |
| dc.contributor.author | Bonaventure, Olivier | |
| dc.date.accessioned | 2021-07-13T10:00:12Z | |
| dc.date.available | 2021-07-13T10:00:12Z | |
| dc.date.issued | 2012-09-07 | |
| dc.identifier.citation | “Loopfree convergence using oFIB”, M. Shand, S. Bryant, S. Previdi, C. Filsfils, P. Francois, O. Bonaventure, IETF RTGWG Working Group document, draft-ietf-rtgwg-ordered-fib-07, September 2012 - Evolution of draft-ietf-rtgwg-ordered-fib-06, June 2012 | |
| dc.identifier.uri | http://hdl.handle.net/20.500.12761/1154 | |
| dc.description | OFIB: With link-state protocols, such as IS-IS and OSPF, each time the network topology changes, some routers need to modify their forwarding information base (FIB) to take into account the new topology. Each topology change causes a convergence phase. During this phase, routers may transiently have inconsistent FIBs, which may lead to packet loops and losses, even if the reachability of the destinations is not compromised after the topology change. Packet losses and transient loops can also occur in the case of a link down event implied by a maintenance operation, even if this operation is predictable and not urgent. The goal of this work is to define a mechanism that sequences the router FIB updates to maintain consistency throughout the network. By correctly setting the FIB change order no looping or packet loss can occur. This mechanism may be applied to the case of managed link-state changes, i.e. link metric change, manual link down/up, manual router down/up, and managed state changes of a set of links attached to one router. | |
| dc.description.abstract | This document describes a mechanism for use in conjunction with link state routing protocols which prevents the transient loops which would otherwise occur during topology changes. It does this by correctly sequencing the forwarding information base (FIB) updates on the routers. This mechanism can be used in the case of non-urgent link or node shutdowns and restarts or link metric changes. It can also be used in conjunction with a fast re-route mechanism which converts a sudden link or node failure into a non-urgent topology change. This is possible where a complete repair path is provided for all affected destinations. After a non-urgent topology change, each router computes a rank that defines the time at which it can safely update its FIB. A method for accelerating this loop-free convergence process by the use of completion messages is also described. The technology described in this document has been subject to extensive simulation using real network topologies and costs, and pathological convergence behaviour. | |
| dc.language.iso | eng | |
| dc.publisher | Internet Engineering Task Force (IEFT) | |
| dc.subject.lcc | Q Science::Q Science (General) | |
| dc.subject.lcc | Q Science::QA Mathematics::QA75 Electronic computers. Computer science | |
| dc.subject.lcc | T Technology::T Technology (General) | |
| dc.subject.lcc | T Technology::TA Engineering (General). Civil engineering (General) | |
| dc.subject.lcc | T Technology::TK Electrical engineering. Electronics Nuclear engineering | |
| dc.title | Loop-free convergence using oFIB | en |
| dc.type | technical documentation | |
| dc.type.hasVersion | VoR | |
| dc.rights.accessRights | open access | |
| dc.description.institution | Internet Engineering Task Force (IEFT) | |
| dc.identifier.doi | draft-ietf-rtgwg-ordered-fib-07 | |
| dc.monograph.type | discussion_paper | |
| dc.standardization.type | ietf_internetdraft | |
| dc.description.status | pub | |
| dc.eprint.id | http://eprints.networks.imdea.org/id/eprint/499 |
