A new Request for Comments is now available in online RFC libraries.


        BCP 6:
        RFC 1930:

        Title:      Guidelines for creation, selection, and
                    registration of an Autonomous System (AS)
        Author:     J. Hawkinson & T. Bates
        Date:       March 1996
        Mailbox:    jhawk@bbnplanet.com, Tony.Bates@mci.net
        Pages:      10
        Characters: 22,073
        Updates/Obsoletes:  none

        URL:        ftp://ds.internic.net/rfc/rfc1930.txt


This memo discusses when it is appropriate to register and utilize an
Autonomous System (AS), and lists criteria for such.  ASes are the
unit of routing policy in the modern world of exterior routing, and
are specifically applicable to protocols like EGP (Exterior Gateway
Protocol, now at historical status; see [EGP]), BGP (Border Gateway
Protocol, the current de facto standard for inter-AS routing, and IDRP
(The OSI Inter-Domain Routing Protocol, which the Internet is expected
to adopt when BGP becomes obsolete.  It should be noted that the IDRP
equivalent of an AS is the RDI, or Routing Domain Identifier.  This
RFC is the product of the Inter-Domain Routing Working Group of the
IETF.  

This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements.  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@CNRI.RESTON.VA.US.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@ISI.EDU.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@ISI.EDU with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@ISI.EDU
        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 admin@DS.INTERNIC.NET.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU.  Please consult RFC 1543, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds
USC/Information Sciences Institute