[URL ftp://rs.internic.net/templates/asn-template.txt ]               [01/96]

******************** PLEASE DO NOT REMOVE Version Number ********************

ASN Version Number: 1.0

**************** Please see attached detailed instructions ******************

One of the following conditions must be satisfied before receiving an
Autonomous System Number:

a) Unique Routing Policy

   Please explain how your routing policy is different from your provider.

b) Multi-homed Site

   If your organization is currently multi-homed, please explain exactly
   how you are connected to the Internet.



0.  (N)ew (M)odify (D)elete.:

1.  Autonomous System Name..:

Organization Using ASN
2a. Organization Name.......:
2b. Street address..........:
2c. City....................:
2d. State...................:
2e. Postal Code.............:
2f. Country.................:

Technical Contact
3a. NIC handle (if known)...:
3b. Name (Last, First)......:
3c. Street address..........:
3d. City....................:
3e. State...................:
3f. Postal Code.............:
3g. Country.................:
3h. Phone Number............:
3i. E-Mailbox...............:



--------------------------------CUT HERE-------------------------------------



                         GENERAL INSTRUCTIONS


An Autonomous System (AS) is used for exchanging external routing information
with other ASes through an exterior routing protocol.  It is a connected
group of IP networks which has a single and clearly defined routing policy.

Unique Autonomous System Numbers (ASNs) are required for specific ASes.
However, due to the finite number of available ASNs, care must be taken to
determine which sites require unique ASNs and which do not.

Those requests that do not require a unique AS should utilize one or more
of the ASNs reserved by the Internet Assigned Numbers Authority (IANA) for
private use.  Those numbers are: 64512 through 65535.

The following conditions must be met before being assigned a unique
Autonomous System Number:

Unique Routing Policy

An AS is only needed when you have a routing policy which differs from your
border gateway peers.

Multi-homed Site

If you are connected to more than one Internet Service Provider, you would
need a unique AS.  If the site is single-homed, a unique ASN would not be
needed, the prefixes would be placed in the AS of the site's single
Internet Service Provider.

Section 0 - Registration Action Type

If the request is for a new ASN, type an N.  If modifying a current ASN
record, type an M.  Please note, organization name can not be modified
through the template.  Also, the authorized point of contact should be
the one requesting the modification.  If you wish to delete the ASN record,
type a D.

Section 1 - Autonomous System Name

A unique Autonomous System Name is required in item 1.  This name should be
no more than 21 characters.

Section 2 - Organization using the ASN
   
The name of the organization to receive the ASN should be listed in item 2a. 
   
Item 2b may be copied as many times as necessary to reflect different
lines of the Street Address.  If item 2c, 2d, or 2e is not applicable
for your country, leave that item blank.
   
Section 3 - Technical Contact

The technical point of contact is the person who tends to the technical
aspects of maintaining an Autonomous System.
   
Each person in the InterNIC database is assigned a "handle" - a unique
tag consisting of the person's initials and a serial number.  This tag
is used on records in the database to indicate a point of contact for
a domain name, network, name server or other entity.  Each person should
have only one handle.
   
If the persons handle is known, insert just the handle in item 3a and
leave the rest of section 3 blank.  If the persons handle is unknown 
or the person has never been registered, leave item 3a blank.  The user's
database record will be updated with any new information on the template.
   
Item 3c may be copied as many times as necessary to reflect different
lines of the Street Address.  If item 3d, 3e, or 3f is not applicable
for your country, leave that item blank.



RECOMMENDED READING


RFC 1771   Y. Rekhter, T. Li, "A Border Gateway Protocol 4 (BGP-4)",
           03/21/1995. (Pages=57)  (Obsoletes RFC1654)
           (DS.INTERNIC.NET  RFC1771.TXT)

RFC 1772   Y. Rekhter, P. Gross, "Application of the Border Gateway Protocol
           in the Internet", 03/21/1995. (Pages=19) (Obsoletes  RFC1655)
	   (DS.INTERNIC.NET  RFC1772.TXT)

RFC 1773   P. Traina, "Experience with the BGP-4 protocol", 03/21/1995.
           (Pages=9) (Obsoletes RFC1656) (DS.INTERNIC.NET  RFC1773.TXT)