Document Action: Guidelines for creation, selection, and registration of an Autonomous System (AS) to BCP

IESG Secretary <iesg-secretary@CNRI.Reston.VA.US> Mon, 16 October 1995 23:05 UTC

Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa18684; 16 Oct 95 19:05 EDT
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa22552; 16 Oct 95 19:05 EDT
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa18663; 16 Oct 95 19:05 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa18616; 16 Oct 95 19:01 EDT
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa22480; 16 Oct 95 19:01 EDT
Received: from [127.0.0.1] by IETF.CNRI.Reston.VA.US id aa18611; 16 Oct 95 19:01 EDT
To: IETF-Announce:;
Cc: RFC Editor <rfc-editor@isi.edu>
Cc: Internet Architecture Board <iab@isi.edu>
Cc: bgp@ans.net
Sender: ietf-announce-request@IETF.CNRI.Reston.VA.US
From: IESG Secretary <iesg-secretary@CNRI.Reston.VA.US>
Subject: Document Action: Guidelines for creation, selection, and registration of an Autonomous System (AS) to BCP
Date: Mon, 16 Oct 1995 19:01:45 -0400
X-Orig-Sender: scoya@CNRI.Reston.VA.US
Message-ID: <9510161901.aa18611@IETF.CNRI.Reston.VA.US>


  The IESG has approved the Internet-Draft "Guidelines for creation,
  selection, and registration of an Autonomous System (AS)"
  <draft-ietf-idr-autosys-guide-03.txt> for publication as a Best Current
  Practices RFC. This document is the product of the Inter-Domain Routing
  Working Group. The IESG contact person is Joel Halpern.


Technical Summary

 This document clarifies the definition of an Autonomous System.  It
 then provides clear guidelines for when AS numbers should be assigned,
 and explanations for when they are NOT needed.  This is intended to
 help control the unnecessary assignment of AS numbers, while clearly
 providing for the assignemnet of numbers when necessary.

Working Group Summary

 There was strong support in the working group for this document.

Protocol Quality

 This document was reviewed by Joel M. Halpern, the Routing Area
 Director for the IESG.  While there are no "implementations", the
 document does reflect the practices that many services providers are
 either using or endevouring to put into place.