New template.net NACR proposed

Fri Dec 18 07:13:10 UTC 1992

Hi. We have substantially revised the Network Announcement Change
Request (NACR) template, as part of our effort to automate the
policy routing data base update and configuration process. Please
give us your comments on this new template, and we would like to
start using it on January 1.
	Mark

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

 Version 6.5 								
                                                       18 Dec 1992 

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

This document contains information needed for NSFNET regionals,
midlevels, and peer networks to add or modify network numbers and
routing information in Merit's NSFNET policy-based routing data base.
Due to the rapid increase of network numbers in the database, it has
become necessary to design and implement a system where requests are
automatically parsed to eliminate the need for a similarly increasing
labor pool to do the data entry! The template form contained in this
document represents the first in a series steps that are planned to
streamline the database entry process.

While we believe this automation will make the database process
for network number registration more efficient, it is also our
intention that it remains a cooperative process between Merit and the
regional technical network administrators. If you have comments
on this document or the template it contains, please send them
to ie at merit.edu, the Merit/NSFNET Internet Engineering group.
General discussion of this template or other NSFNET routing issues
can be carried out on the list regional-techs at merit.edu. 

Real-time immediate problems should be reported to trouble at noc.ans.net.
General feedback to Merit for NSFNET service issues or problem
escalation should be sent to nsfnet at merit.edu.

	The Merit/NSFNET Internet Engineering Group

1.0 GENERAL INSTRUCTIONS 
------------------------

  1.1 Configuration Instructions
      --------------------------

      Configuration requests should be submitted by e-mail to
      nsfnet-admin at merit.edu by the designated Routing Administrators
      for the Autonomous Systems of the NSFNET.

      The text of the message should contain the template given in
      section 2.0 of this document.  The first word of the subject line
      of the message should be the first IP number for which you are
      requestiong action.

      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 period.  
      Requests should be received by noon (Eastern time) on Monday (for 
      Tuesday morning configs) and noon (Eastern time) on Thursday (for 
      Friday morning configs).

      Merit will request separate authorization from the National
      Science Foundation on a per-net basis to allow non-US network numbers
      to be added. Additions of non-US networks therefore may result in
      additional delays.

      Merit maintains mail lists for each Autonomous System (AS)
      announced on the backbone in the syntax: as<number>@merit.edu.
      In the interest of improving turnaround time for configuration
      requests that involve inbound announcements from multiple
      organizations, we ask that all of the appropriate AS mailing
      groups be copied when you submit the original request to
      nsfnet-admin at merit.edu.  We also ask that the copied Routing
      Administrators reply to all with their approvals or denials of
      the requested addition(s) or change(s).

      An Internet network number must have been assigned by the Network
      Information Center (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 the NIC.

  1.2 Template Instructions
      ---------------------

      This form will be read by an automatic parser and bounced back to
      you if it is unparsable or if required data is missing.  Thus, if
      you wish to add a comment or for other reasons have your request
      read by a human please replace the word "Yes" with "No" in the
      "Autoparse:" line at the beginning of the NACR.

      The organizational information you supply with this form will be
      checked against that held by the NIC in an attempt to keep our
      network information synchronized with the NIC.

      The NACR template information consists of global NACR information
      followed by one or more network number entries. The global NACR
      information applies to each network number entry that follows
      it.  However, any line of the global information can be
      overridden for a particular network by specifying that line in
      the net number entry.  For example, the global information may
      indicate "Net_Country Code: US" but one net you are submitting
      might be located in Canada.  Thus, you may overide US by
      including the line:  "Net_Country_Code: CA" in the net number
      entry.  See example 4, below (in section 3.0).

2.0 NACR TEMPLATE 
-----------------

 ******************************* CUT HERE ********************************** 

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

 The administrators of the following networks for which access is requested
 to the NSFNET backbone service agree that traffic from these networks that 
 will transit the NSFNET backbone service complies with the "NSFNET BACKBONE 
 SERVICES ACCEPTABLE USE POLICY" dated June 1992.

 %begin nsfnet nacr v6.5%
 Autoparse: Yes

 %global nacr info%
 Organization_Name:
 Street_Address_1:
 Street_Address_2:
 Street_Address_3:
 City: 
 State_or_Province:
 Postal_Code:
 Org_Country_Code: 
 Net_Country_Code: 
 Intended_Use_of_Network(C,E,G,M,R,O):
 Educational_Organization_Type(4year,4year+,2year,K-12):
 Backbone: T3 
 Action_being_requested(A/D/C):
 Inbound_Announcements_to_NSFNET: 
 Comments:
 %end global nacr info%

 %begin network entries%
 Network_Number: 
 Network_Name:
 %end network entries%

 %end nsfnet nacr%
 ******************************* CUT HERE ********************************** 

3.0  EXPLANATION OF SPECIFIC FIELDS IN THE TEMPLATE
---------------------------------------------------

 Organization responsible for network:  The name and address of the 
   organization to which the network belongs should be listed under this 
   section.  The country code requested should comply with the two letter 
   ISO 3166 codes.

 Net_Country Code:   This is the country where the network is located
   (vs. the organization that is responsible for the net).  If the net
   spans multiple countries please try to pick the one which you feel
   best represents the net.  The country code requested on this line
   must comply with the two letter ISO 3166 codes.  A listing of these
   codes may be ftp'ed from
   nis.nsf.net:nsfnet/announced.networks/country.codes.

 Intended Use of Network:   Indicate type from this list:
   Commercial (C), Education (E), Government - non-military (G),
   Government - military (M), Research (R), Other (O).

 Educational Organization Type:   If the intended use type is Educational,
   specify the type of educational organization.  It is preferred that
   the Carnegie Classification code be specified here, but if that is
   not known, indicate broad type: 4year, 4year+, 2year, K-12.  The
   Carnegie Classification codes are included below.

 Backbone: T3. (Just to avoid any ambiguity. ;-)

 Action being requested (A/D/C):  This line must indicate if the inbound 
   announcements you are requesting for this network will be a change to 
   existing inbound announcements to the NSFNET (C), a compete deletion of 
   all inbound announcements to the NSFNET (D), or if this request is to 
   add a network that is not currently being announced to the NSFNET (A).

 Inbound Announcements to NSFNET:  This input line(s) should be filled out
   with the Autonomous System numbers which will announce the
   network(s).  Any number of ASes may be listed on this line; at least
   one is required.  The ASes should be listed in order of preference,
   with the most highly preferred AS listed first, as in 233 177 266.
   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 toward the specified network.

 Comments: Comment lines are most useful when the autoparse option is
   not in use, though the routing consultants will generally read these
   comments in the normal process of approving database updates.
   Please see the first paragraph of the NACR for information on
   bypassing the parser.  Please precede EACH comment line with the
   "Comments:" string.

 Network Name:  The offical name of the network, as it is registered at the 
   NIC (see whois server), should appear on this input line.

4.0 EXAMPLES
------------

EXAMPLE 1:    SINGLE NET
              ========== 

 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 the T3 network.

 Their Network Announcement Change Request follows:
 -----------------------------------------------------------------------------

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