Guidelines for AS numbers

yakov@watson.ibm.com Wed, 01 February 1995 13:53 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa01569; 1 Feb 95 8:53 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa01565; 1 Feb 95 8:53 EST
Received: from interlock.ans.net by CNRI.Reston.VA.US id aa04618; 1 Feb 95 8:53 EST
Received: by interlock.ans.net id AA50077 (InterLock SMTP Gateway 1.1 for iwg-out@ans.net); Wed, 1 Feb 1995 08:38:48 -0500
Received: by interlock.ans.net (Internal Mail Agent-2); Wed, 1 Feb 1995 08:38:48 -0500
Message-Id: <199502011338.AA50073@interlock.ans.net>
Received: by interlock.ans.net (Internal Mail Agent-1); Wed, 1 Feb 1995 08:38:48 -0500
Date: Wed, 01 Feb 1995 08:38:43 -0500
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: yakov@watson.ibm.com
To: bgp@ans.net
Subject: Guidelines for AS numbers

Folks,
At the last BGP WG meeting we agreed to ask the IESG to advance
Guidelines for AS number to a Proposed Standard. Appended is
the announcement of the revised I-D. I'd like to put a two
weeks deadline for comments (2/15). After that I'll follow the
agreement we reached at the WG meeting.
Yakov.

******  The following is a COPY  *****************************
Received: from interlock.ans.net by watson.ibm.com (IBM VM SMTP V2R3) with TCP;
   Tue, 31 Jan 95 19:23:15 EST
Received: by interlock.ans.net id AA17988
  (InterLock SMTP Gateway 1.1 for iwg-out@ans.net);
  Tue, 31 Jan 1995 19:18:56 -0500
Received: by interlock.ans.net (Internal Mail Agent-2);
  Tue, 31 Jan 1995 19:18:56 -0500
Received: by interlock.ans.net (Internal Mail Agent-1);
  Tue, 31 Jan 1995 19:18:56 -0500
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: bgp@ans.net
From: Internet-Drafts@CNRI.Reston.VA.US
Reply-To: Internet-Drafts@CNRI.Reston.VA.US
Subject: I-D ACTION:draft-ietf-idr-autosys-guide-01.txt
Date: Tue, 31 Jan 95 17:41:00 -0500
Sender: cclark@CNRI.Reston.VA.US
Message-Id:  <9501311741.aa11080@IETF.CNRI.Reston.VA.US>

--NextPart

A Revised Internet-Draft is available from the on-line Internet-Drafts
directories. This draft is a work item of the Inter-Domain Routing Working
Group of the IETF.

       Title     : Guidelines for creation, selection, and registration
                   of an Autonomous System (AS)
       Author(s) : J. Hawkinson, T. Bates
       Filename  : draft-ietf-idr-autosys-guide-01.txt
       Pages     : 11
       Date      : 01/30/1995

This draft 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; see [BGP-4]), and IDRP (The
OSI Inter-Domain Routing Protocol, which the Internet will eventually adopt
when BGP becomes obsolete; see [IDRP]). It should be noted that the IDRP
equivalent of an AS is the RDI, or Routing Domain Identifier.

Internet-Drafts are available by anonymous FTP.  Login with the username
"anonymous" and a password of your e-mail address.  After logging in,
type "cd internet-drafts" and then
     "get draft-ietf-idr-autosys-guide-01.txt".
A URL for the Internet-Draft is:
ftp://ds.internic.net/internet-drafts/draft-ietf-idr-autosys-guide-01.txt

Internet-Drafts directories are located at:

     o  Africa
        Address:  ftp.is.co.za (196.4.160.2)

     o  Europe
        Address:  nic.nordu.net (192.36.148.17)

     o  Pacific Rim
        Address:  munnari.oz.au (128.250.1.21)

     o  US East Coast
        Address:  ds.internic.net (198.49.45.10)

     o  US West Coast
        Address:  ftp.isi.edu (128.9.0.32)

Internet-Drafts are also available by mail.

Send a message to:  mailserv@ds.internic.net. In the body type:
     "FILE /internet-drafts/draft-ietf-idr-autosys-guide-01.txt".

NOTE: The mail server at ds.internic.net can return the document in
      MIME-encoded form by using the "mpack" utility.  To use this
      feature, insert the command "ENCODING mime" before the "FILE"
      command.  To decode the response(s), you will need "munpack" or
      a MIME-compliant mail reader.  Different MIME-compliant mail readers
      exhibit different behavior, especially when dealing with
      "multipart" MIME messages (i.e., documents which have been split
      up into multiple messages), so check your local documentation on
      how to manipulate these messages.

For questions, please mail to Internet-Drafts@cnri.reston.va.us.


Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version
of the Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type:  Message/External-body;
        access-type="mail-server";
        server="mailserv@ds.internic.net"

Content-Type: text/plain
Content-ID: <19950130164425.I-D@CNRI.Reston.VA.US>

ENCODING mime
FILE /internet-drafts/draft-ietf-idr-autosys-guide-01.txt

--OtherAccess
Content-Type:   Message/External-body;
        name="draft-ietf-idr-autosys-guide-01.txt";
        site="ds.internic.net";
        access-type="anon-ftp";
        directory="internet-drafts"

Content-Type: text/plain
Content-ID: <19950130164425.I-D@CNRI.Reston.VA.US>

--OtherAccess--

--NextPart--