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

The IESG <iesg-secretary@CNRI.Reston.VA.US> Tue, 27 February 1996 20:21 UTC

Received: from p-o.ans.net by ftp.ans.net with SMTP id AA16708 (5.65c/IDA-1.4.4 for <archive-iwg@ftp.ans.net>); Tue, 27 Feb 1996 15:21:08 -0500
Received: by p-o.ans.net id AA11254 (5.65c/IDA-1.4.4 for bgp-outgoing); Tue, 27 Feb 1996 20:21:05 GMT
To: IETF-Announce:;
Cc: RFC Editor <rfc-editor@isi.edu>
Cc: Internet Architecture Board <iab@isi.edu>
Cc: bgp@ans.net
From: The IESG <iesg-secretary@CNRI.Reston.VA.US>
Subject: Document Action: Guidelines for creation, selection, and registration of an Autonomous System (AS) to BCP
Date: Tue, 27 Feb 1996 14:59:55 -0500
Message-Id: <9602271500.aa29585@IETF.CNRI.Reston.VA.US>
Sender: bgp-owner@ans.net
Precedence: bulk
Reply-To: bgp@ans.net

  The IESG has approved the Internet-Draft "Guidelines for creation,
  selection, and registration of an Autonomous System (AS)"
  <draft-ietf-idr-autosys-guide-04.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.

Document Action: Guidelines for creation, selecti… The IESG