RFC 3221: Commentary on Inter-Domain Routing in the Internet
In plain English — editorial summary, not part of the RFC
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 memo provides information for the Internet community.
Document record
- Document ID
- RFC3221
- Published
- December 2001
- Authors
- G. Huston
- Status
- INFORMATIONAL
- Stream
- IAB
- Area
- —
- Pages
- 25
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2519A Framework for Inter-Domain Route AggregationCurrent
February 1999
- RFC 1930Guidelines for creation, selection, and registration of an Autonomous System (AS)Updated
March 1996
- RFC 3167Request to Move RFC 1745 to Historic StatusCurrent
August 2001
- RFC 2858Multiprotocol Extensions for BGP-4Obsoleted
June 2000
- RFC 2842Capabilities Advertisement with BGP-4Obsoleted
May 2000
- RFC 2547BGP/MPLS VPNsObsoleted
March 1999
- RFC 2283Multiprotocol Extensions for BGP-4Obsoleted
February 1998
- RFC 2270Using a Dedicated AS for Sites Homed to a Single ProviderCurrent
January 1998
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?