Overview of 1999 IAB Network Layer Workshop

Kaat, Marijke

doi:10.17487/rfc2956

Cited by 7 publications

(6 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…2(a) shows more than 20% of Tlong and 40% of Tdown events fluctuated for more than three minutes. We note that these observed latencies are an order of magnitude longer than those reported in [3], [16].…”

Section: A Routing Measurementscontrasting

confidence: 46%

See 1 more Smart Citation

Delayed Internet routing convergence

Labovitz

Ahuja²,

Bose

et al. 2001

IEEE/ACM Trans. Networking

272

155

View full text Add to dashboard Cite

This paper examines the latency in Internet path failure, failover, and repair due to the convergence properties of interdomain routing. Unlike circuit-switched paths which exhibit failover on the order of milliseconds, our experimental measurements show that interdomain routers in the packet-switched Internet may take tens of minutes to reach a consistent view of the network topology after a fault. These delays stem from temporary routing table fluctuations formed during the operation of the Border Gateway Protocol (BGP) path selection process on Internet backbone routers. During these periods of delayed convergence, we show that end-to-end Internet paths will experience intermittent loss of connectivity, as well as increased packet loss and latency. We present a two-year study of Internet routing convergence through the experimental instrumentation of key portions of the Internet infrastructure, including both passive data collection and fault-injection machines at major Internet exchange points. Based on data from the injection and measurement of several hundred thousand interdomain routing faults, we describe several unexpected properties of convergence and show that the measured upper bound on Internet interdomain routing convergence delay is an order of magnitude slower than previously thought. Our analysis also shows that the upper theoretic computational bound on the number of router states and control messages exchanged during the process of BGP convergence is factorial with respect to the number of autonomous systems in the Internet. Finally, we demonstrate that much of the observed convergence delay stems from specific router vendor implementation decisions and ambiguity in the BGP specification.

show abstract

Section: A Routing Measurementscontrasting

confidence: 46%

“…At least one report places the latency of interdomain Internet path failover on the order of 30 seconds or less based on qualitative end user experience [16]. These brief delays in interdomain failover are further believed to stem mainly from queuing and router CPU processing latencies [3, (message digests 11/98, 1/99)].…”

Section: Introductionmentioning

confidence: 99%

Delayed Internet routing convergence

Labovitz

Ahuja²,

Bose

et al. 2001

IEEE/ACM Trans. Networking

272

155

View full text Add to dashboard Cite

show abstract

“…In practice, the Internet retains some level of hierarchy and most providers implement some degree of customer route ltering. We note, however, that the choice of a full mesh re ects current trends in the evolution of the Internet towards less hierarchy a n d a more meshed topology 14,13]. We s h o w in Section 5.1 that a complete graph in the absence of ingress/egress lters provides the worst-case complexity of BGP convergence and, as such, signi cantly overestimates the average case.…”

Section: Bgp Convergence Modelmentioning

confidence: 99%

Delayed Internet routing convergence

Labovitz

Ahuja

Bose

et al. 2000

Proceedings of the Conference on Applications, Technologies, Architectures, and Protocols for Computer Communication

306

327

View full text Add to dashboard Cite

This paper examines the latency in Internet path failure, failover and repair due to the convergence properties of interdomain routing. Unlike s w i t c hes in the public telephony n e twork which exhibit failover on the order of milliseconds, our experimental measurements show t h a t i n ter-domain routers in the packet switched Internet may take tens of minutes to reach a consistent view of the network topology after a fault. These delays stem from temporary routing table oscillations formed during the operation of the BGP path selection process on Internet backbone routers. During these periodsofdelayed c onvergence, w e s h o w that end-to-end Internet paths will experience intermittent loss of connectivity, as well as increased packet loss and latency. We present a two-year study of Internet routing convergence through the experimental instrumentation of key portions of the Internet infrastructure, including both passive data collection and fault-injection machines at major Internet exchange points. Based on data from the injection and measurement o f s e v eral hundred thousand inter-domain routing faults, we describe several unexpected properties of convergence and show that the measured upper bound on Internet inter-domain routing convergence delay is an order of magnitude slower than previously thought. Our analysis also shows that the upper theoretic computational bound on the numberofrouter states and control messages exchanged during the process of BGP convergence is factorial with respect to the number of autonomous systems in the Internet. Finally, w e demonstrate that much o f the observed convergence delay s t e m s from speci c router vendor implementation decisions and ambiguity in the BGP speci cation.

show abstract

“…The IAB has been concerned about trends opposing the end-to-end principle for some time, for example RFC 2956 [9] and RFC 2775 [12]. The primary focus of concern in these documents is the reduction in transparency due to the introduction of NATs and other address translation mechanisms in the Internet, and the consequences to the end-to-end principle of various scenarios involving full, partial, or no deployment of IPv6.…”

Section: Trends Opposed To the End-to-end Principlementioning

confidence: 99%

“…These features are all based on end to end considerations. However, the need for the global routing proxy in the Home Agent in Mobile IPv6 is determined by the aliasing of the global node identifier with the routing identifier in the Internet routing architecture, a topic that was discussed in an IAB workshop and reported in RFC 2956 [9], and that hasn't changed in IPv6.…”

Section: Introductionmentioning

confidence: 99%

The Rise of the Middle and the Future of End-to-End: Reflections on the Evolution of the Internet Architecture

Kempf¹,

Austein²

2004

View full text Add to dashboard Cite

Overview of 1999 IAB Network Layer Workshop

Cited by 7 publications

References 10 publications

Delayed Internet routing convergence

Delayed Internet routing convergence

Delayed Internet routing convergence

The Rise of the Middle and the Future of End-to-End: Reflections on the Evolution of the Internet Architecture

Contact Info

Product

Resources

About