RFC 1930: Guidelines for creation, selection, and registration of an Autonomous System (AS)
In plain English — editorial summary, not part of the RFC
This memo discusses when it is appropriate to register and utilize an Autonomous System (AS), and lists criteria for such. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Document record
- Document ID
- RFC1930
- Published
- March 1996
- Authors
- J. Hawkinson; T. Bates
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- rtg
- Pages
- 10
- Also known as
- BCP6
Topics
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1863A BGP/IDRP Route Server alternative to a full mesh routingObsoleted
October 1995
- RFC 1745BGP4/IDRP for IP---OSPF InteractionCurrent
December 1994
- RFC 4223Reclassification of RFC 1863 to HistoricCurrent
October 2005
- RFC 1773Experience with the BGP-4 protocolCurrent
March 1995
- RFC 1656BGP-4 Protocol Document Roadmap and Implementation ExperienceObsoleted
July 1994
- RFC 1364BGP OSPF InteractionObsoleted
September 1992
- RFC 2519A Framework for Inter-Domain Route AggregationCurrent
February 1999
- RFC 3167Request to Move RFC 1745 to Historic StatusCurrent
August 2001
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?