Commentary on Inter-Domain Routing in the Internet
draft-iab-bgparch-02
This document is an Internet-Draft (I-D) that has been submitted to the Internet Architecture Board (IAB) stream.
This I-D is not endorsed by the IETF and has no formal standing in the
IETF standards process.
The information below is for an old version of the document that is already published as an RFC.
Document | Type |
This is an older version of an Internet-Draft that was ultimately published as RFC 3221.
|
|
---|---|---|---|
Author | Geoff Huston | ||
Last updated | 2013-03-02 (Latest revision 2001-09-25) | ||
RFC stream | Internet Architecture Board (IAB) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | IAB state | (None) | |
Consensus boilerplate | Unknown | ||
IAB shepherd | (None) |
draft-iab-bgparch-02
A new Request for Comments is now available in online RFC libraries. RFC 3221 Title: Commentary on Inter-Domain Routing in the Internet Author(s): G. Huston Status: Informational Date: December 2001 Mailbox: gih@telstra.net Pages: 25 Characters: 66580 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-iab-bgparch-02.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3221.txt This document examines the various longer term trends visible within the characteristics of the Internet's BGP table and identifies a number of operational practices and protocol factors that contribute to these trends. The potential impacts of these practices and protocol properties on the scaling properties of the inter-domain routing space are examined. This document is the outcome of a collaborative exercise on the part of the Internet Architecture Board. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information.