New template.net form

Tue May 19 02:11:05 UTC 1992

Regional techs,

Greetings. There is a new template.net form available nis.nsf.net
in the nsfnet/announced.networks directory. (I've appended a copy
below for your convenience). It is version 5.2 dated May 18, 1992
and is by far the hippest version to date. I'm just kidding; the 
primary change is that you have the option of 'T1', 'T3', or 'both'
for network type. 

There are also more helpful hints on how to submit NACRs as well
as information on when the config deadlines are and when the 
config installation windows are.

Enjoy. Please send feedback to nsfnet-admin at merit.edu.

Thanks,
-B. Sue Blair
 Merit Network Operations

-------------------------
 [nis.nsf.net:nsfnet/announced.networks/template.net]

 Version 5.2                                                18 May 1992

                 NSFNET Configuration Request Template
             for the NSFNET policy-based routing data base
             ---- Network Announcement Change Request ---- 

 This template is to request announcement of networks to the NSFNET 
 backbone.

 Configuration requests may only be submitted by the designated Routing
 contacts for the Autonomous Systems of the NSFNET. 

 Configuration requests should be submitted to nsfnet-admin at merit.edu.

 Please read the explanation at the bottom of this form if you are
 unfamiliar with its contents.

 *****************************************************************************

                ---- Network Announcement Change Request ----

 The networks which request access to the NSFNET backbone agree that traffic
 from the networks that will transit the NSFNET backbone comply with the
 "NSFNET BACKBONE SERVICES ACCEPTABLE USE POLICY" dated February 1992.

                                Inbound Announcements     Add/Del 
                     Network:         to NSFNET          or Change 
                     T1, T3    -----------------------   ---------
Network Number/Name  or both   1st AS# 2nd AS# 3rd AS#     A/D/C     Country
-------------------  --------  ------- ------- -------   ---------   -------

 Network Name:
 Organization Name:
 Organization Address:

 Additional Comments (optional):

 *****************************************************************************

 EXAMPLE:

 Suppose network 141.214 (UMNET4), wishes to be announced to the NSFNET.
 Furthermore, they wish to have AS 233 as their PRIORITY 1 path and AS 177 as
 their PRIORITY 2 path on both the T1 and T3 networks.

 Their network announcement change request would be filled in as follows:

 *****************************************************************************

                ---- Network Announcement Change Request ----

 The networks which request access to the NSFNET backbone agree that traffic
 from the networks that will transit the NSFNET backbone comply with the
 "NSFNET BACKBONE SERVICES ACCEPTABLE USE POLICY" dated February 1992.

                                Inbound Announcements     Add/Del 
                     Network:         to NSFNET          or Change 
                     T1, T3,   -----------------------   ---------
Network Number/Name  or both   1st AS# 2nd AS# 3rd AS#     A/D/C     Country
-------------------  --------  ------- ------- -------   ---------   -------
 141.214     	       both      233     177                 A        USA

 Network Name: (UMNET4)
 Organization Name: University of Michigan
 Organization Address: 1075 Beal Avenue, Ann Arbor, MI 48109

If the announcements on the T1 and T3 sides of the network were going 
to be different, the form would be filled out:

                                Inbound Announcements     Add/Del
                     Network:         to NSFNET          or Change
                     T1, T3,   -----------------------   ---------
Network Number/Name  or both   1st AS# 2nd AS# 3rd AS#     A/D/C     Country
-------------------  --------  ------- ------- -------   ---------   -------
 141.214               T1        233     177                 A        USA
                       T3        233     177     266

Also, in this example, Merit would like AS 266 to act as a backup 
on the T3 side. Merit could copy the as266 at merit.edu mailgroup on
the addition request to nsfnet-admin at merit.edu. This would aid in
faster approval response time from the AS 266 admin folks.

 *********************************************************************** 
                     ***** Explanation of this form *****

 Network Addition Request:

 PLEASE NOTE:

         (1) The individual submitting this request affirms that 
             traffic from the networks recommended for inclusion
             in the NSFNET routing tables conforms to the "NSFNET
             BACKBONE SERVICES ACCEPTABLE USE POLICY." 

         (2) An Internet network number must have been assigned by the
             NIC.DDN.MIL prior to its addition to the NSFNET routing 
             database.  If it was not assigned by the time of this
             request, a message will be sent by Merit to the requestor
             stating that the network has not been added to the NSFNET
             policy-based routing database.  It is then up to the 
             requestor to resubmit the application after registration
             with NIC.DDN.MIL.

         (3) Merit has to request a separate authorization from the
             National Science Foundation on a per-net basis to allow
             foreign network numbers to be added. Additions of foreign 
             networks therefore may result in additional delays.

 Configurations are typically done by Merit on Tuesday and Friday mornings
 of every week. The installation of new configuration files is performed 
 Tuesday and Friday mornings from 05:00-08:00 (Eastern time), so some
 backbone instability may be experienced during this timeframe.
 Requests should be received by noon on Monday (for Tuesday morning configs)
 and noon on Thursday (for Friday morning configs).

 The columns headed '1st AS#', '2nd AS#' and '3rd AS#' should be filled with
 the Autonomous System numbers which are to have priorities (or path weights)
 1, 2 and 3 respectively. Please note that these are inbound routing
 announcements TO the NSFNET backbone; which means that the specified priority
 impacts the path of how packets are routed towards the specified network.
 It is possible to have more than three priorities. The offical name of the 
 network, as it is registered at the NIC.DDN.MIL, should appear on the line
 following the network number.  Finally, the name and address of the 
 organizaion to which the network belongs should be listed following the
 network name.