|
|
|
|
|
|
|
|
|
|
| Last Update: May 26, 2010
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| | |
RFC4264
11/2005
(10 p.)
pdf(2p)
|
T. Griffin
G. Huston |
|
BGP Wedgies |
|
It has commonly been assumed that the Border Gateway Protocol (BGP)
is a tool for distributing reachability information in a manner that
creates forwarding paths in a deterministic manner. In this memo we
will describe a class of BGP configurations for which there is more
than one potential outcome, and where forwarding states other than
the intended state are equally stable. Also, the stable state where
BGP converges may be selected by BGP in a non-deterministic manner.
These stable, but unintended, BGP states are termed here "BGP
Wedgies".
|
|
|
| |
| List |
Status: | Informational |
|
|
|
|
|
|
|
|
| | |
RFC4384
02/2006
(12 p.)
pdf(2p)
|
D. Meyer |
|
BGP Communities for Data Collection |
|
BGP communities (RFC 1997) are used by service providers for many
purposes, including tagging of customer, peer, and geographically
originated routes. Such tagging is typically used to control the
scope of redistribution of routes within a provider's network and to
its peers and customers. With the advent of large-scale BGP data
collection (and associated research), it has become clear that the
information carried in such communities is essential for a deeper
understanding of the global routing system. This memo defines
standard (outbound) communities and their encodings for export to BGP
route collectors.
|
|
|
|
|
|
|
|
|
|
|
| | |
RFC4451
03/2006
(13 p.)
pdf(2p)
|
D. McPherson
V. Gill |
|
BGP MULTI_EXIT_DISC (MED) Considerations |
The BGP MULTI_EXIT_DISC (MED) attribute provides a mechanism for BGP
speakers to convey to an adjacent AS the optimal entry point into the
local AS. While BGP MEDs function correctly in many scenarios, a
number of issues may arise when utilizing MEDs in dynamic or complex
topologies.
This document discusses implementation and deployment considerations
regarding BGP MEDs and provides information with which implementers
and network operators should be familiar.
|
|
|
| |
| List |
Status: | Informational |
|
|
|
|
|
|
|
|
| | |
RFC4632
08/2006
(27 p.)
pdf(2p)
|
V. Fuller
T. Li |
|
Classless Inter-domain Routing (CIDR): The Internet Address Assignment and Aggregation Plan |
|
This memo discusses the strategy for address assignment of the
existing 32-bit IPv4 address space with a view toward conserving the
address space and limiting the growth rate of global routing state.
This document obsoletes the original Classless Inter-domain Routing
(CIDR) spec in RFC 1519, with changes made both to clarify the
concepts it introduced and, after more than twelve years, to update
the Internet community on the results of deploying the technology
described.
|
|
|
|
|
|
|
|
|
|
|
| | |
RFC4786
12/2006
(24 p.)
pdf(2p)
|
J. Abley
K. Lindqvist |
|
Operation of Anycast Services |
As the Internet has grown, and as systems and networked services
within enterprises have become more pervasive, many services with
high availability requirements have emerged. These requirements have
increased the demands on the reliability of the infrastructure on
which those services rely.
Various techniques have been employed to increase the availability of
services deployed on the Internet. This document presents commentary
and recommendations for distribution of services using anycast.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
