- Test - lists.nanog.org

Note Taking
by sob＠academ.com 17 Jan '95

17 Jan '95

1 0

NANOG Meeting Feb. 9 & 10
by Pam Ciesla 17 Jan '95

17 Jan '95

The NANOG Meeting will be held in Boulder CO, at the NCAR Mesa site, in the Main Seminar Room. Please reply to nsf-seminar if you are planning on attending. Send your full name and the organization you will represent. This information is needed for a head count and for name tags, there is no cost for registering. I will pass on hotel and other info as it becomes available. Pam Ciesla

2 1

Re: Change in NACR procedures
by Dale S. Johnson 17 Jan '95

17 Jan '95

Done. > In <199501131816.NAA04899(a)home.merit.edu>, <epg(a)merit.edu> wrote: > > > To update the designated email addresses for an Autonomous > > System, send email to DB-admin(a)ra.net. > > Please can you change the contact info for AS1849 from: > > 1849 Keith Mitchell keith(a)pipex.net +44 223 250122 > 1849 PIPEX Support Desk support(a)pipex.net +44 223 250122 > 1849 Tim Goodwin tim(a)pipex.net +44 223 250122 > > to include one more person, markt(a)pipex.net, i.e. > > 1849 Keith Mitchell keith(a)pipex.net +44 223 250122 > 1849 PIPEX Support Desk support(a)pipex.net +44 223 250122 > 1849 Tim Goodwin tim(a)pipex.net +44 223 250122 > 1849 Mark Turner markt(a)pipex.net +44 223 250122 > > I have asked for this change to be made more than once under the old > scheme, but I think it has got lost in the transition somewhere. > > If you prefer the data in RIPE-181 format, it is: > > person: Mark Turner > nic-hdl: MT104 > address: PIPEX > address: 216 Cambridge Science Park > address: Milton Road > address: Cambridge > address: CB4 4WA > address: England, GB > phone: +44 223 250122 > fax-no: +44 223 250121 > e-mail: markt(a)pipex.net > changed: keith(a)pipex.net 950117 > > mntner: AS1849-MNT > descr: PIPEX, Public IP EXchange Ltd > admin-c: KM133 > tech-c: TG46 > tech-c: MT104 > upd-to: support(a)pipex.net > auth: CRYPT-PW PzRsMi3OZ1roU > notify: support(a)pipex.net > mnt-by: AS1849-MNT > changed: keith(a)pipex.net 950117 > source: RIPE > > Please let me know as soon as you can if there are any problems with > making this change, it is becoming quite important to us that we can > make use of it. > > Thanks, > > Keith >

1 0

Change in NACR procedures
by Elise Gerich 17 Jan '95

17 Jan '95

In preparation for the retirement of the PRDB and the move to the Routing Arbiter (RA) architecture, Merit proposes to change our NACR-handling procedures to more closely mimic the registration procedures of the Internet Routing Registries. We propose to implement these changes on January 20, 1995. Please send any comments regarding the changes to merit-ie(a)merit.edu as soon as possible. Procedural changes: 1. NACRs for a given net will only be accepted from designated email addresses from the net's home AS or from the AS which is currently listed as the primary path according to the PRDB. To verify what the designated email addresses are for your Autonomous System number, use the whois client: whois -h prdb.merit.edu contact <as number> To update the designated email addresses for an Autonomous System, send email to DB-admin(a)ra.net. Please register the exact email address which will be used to add or change information in the PRDB. For example, if the designated email address is epg(a)merit.edu and the NACR is received from epg(a)pepper.merit.edu, it will be bounced. In general we anticipate that this change should pose little or no problem. In the event that a net changes providers, one of the following two procedures will have to be followed. Either (a) the administration of the net's home AS sends a NACR specifying the new provider as primary (and possibly deleting the old), or (b) the administration of the old provider sends the NACR. If the new provider wants to submit the NACR, they will need to send it to the administration of the home AS for forwarding to Merit. Very few administrators of home ASs which are behind ASs that peer directly with AS 690 have designated individuals and their associated email addresses as authorized to update the PRDB. For more information in establishing an aslist with Merit, please send a message to DB-admin(a)merit.edu. 2. ACKs/NACKs for NACRs will no longer be required, and in fact, will be ignored if received. 3. Copies of accepted NACRs will be sent to all associated ASs. This includes notification of changes to nets already in the PRDB. Typically, we would expect that all the ASs which are associated with a net would be aware of any change in routing preferences. However, this notification procedure will alert ASs that a change has taken place even if they had not previously been informed about the change. NACR Processing As of January 20, 1995, Merit will begin to implement this change. If mail to nsfnet-admin(a)merit.edu contains a NACR originated from an authorized account as described in procedural change (1), it will be processed. If it didn't, the mail will be bounced. If for some reason you want your NACR to be read even if it would otherwise be deemed unacceptable, include a non-null comment: field in the NACR. Summary: This is the first step in providing a transition to the RA architecture. We have been experiencing an increase in the number of NACRs which are being submitted to the NSFNET Backbone Service, many of which pertain to the movement of networks from one provider to another. For the month of December, nsfnet-admin(a)merit.edu received more than 4200 messages. More than 1200 changes were made to the PRDB on January 13, 1995. These new procedures will help to make the registration process more manageable. For those organizations which are in the process of changing to another provider (autonomous system), the organization can improve its chances of having changes to the PRDB made in a timely fashion and to protect itself against loss of reachability by: a. sending NACRs in advance of your cutover (at least one week) b. adding the new provider as secondary (tertiary, etc) c. having the new provider start announcing the route d. testing the route by having previous provider stop announcing the route e. sending a NACR deleting the previous provider Please check that you have designated correct email addresses for your Autonomous System prior to January 20,1995. Mail to nsfnet-admin(a)merit.edu which is a valid template and originates from an undesignated email address will be bounced back to the originator of the message starting on January 20, 1995. Thank you in advance for your cooperation. --Elise

3 2

Additions to the NSFNET policy-based routing database
by smm＠twain.merit.edu 16 Jan '95

16 Jan '95

------------------------------------------------------------------------------ The PRDB and this "NWG report" will be retired in January. Details below. ------------------------------------------------------------------------------ The following changes have been made to the NSFNET policy-based routing database and will be installed on the backbone by 08:00 EST : Total = As + Bs + Cs + Aggs Registered Networks 45353 = 30 5224 37501 2598 Configured Networks 42331 = 30 5167 34579 2555 Added Networks 320 = 0 1 268 51 Deleted Networks 74 = 0 0 72 2 IP address Net name Country Priority:AS ---------- -------- ------- ----------- 163.248/16 JORDAN-SD C:US 1:1800 2:1240 3:1239 4:210 5:209 192.83.253/24 NET-BARD2 C:US 1:2149 2:174 3:1239 4:1800 5:1240 192.243.192/20 TIPS192 C:US 1:1240 2:1800 3:1239 4:209 5:210 193.100.112/22 TLC-NET C:DE 1:1800 2:1240 3:1133 193.232.112/20 MSUNET C:RU 1:1800 2:1133 3:1674 4:1240 196.1.138/23 INFOCHAN-NET C:JM 1:1800 2:1240 3:1239 4:2386 5:1321 196.7.64/24 AZTEC-64 C:ZA 1:701(136) 2:701(134) 3:3561(11) 4:3561(218) 5:1240 196.7.70/24 AZTEC2 C:ZA 1:701(136) 2:701(134) 3:3561(11) 4:3561(218) 5:1240 196.7.193/24 AZTEC-193 C:ZA 1:701(136) 2:701(134) 3:3561(11) 4:3561(218) 5:1240 199.71.120/24 HCL-NOT-ETHER C:CA 1:701(136) 2:701(134) 199.76.208/20(U) SJCSD C:US 1:3561(218) 2:3561(11) 3:279 4:86 199.99.248/21 CHEMEK-C-0 C:US 1:3561(11) 2:3561(218) 3:1240 4:1239 5:1800 6:2149 7:174 199.101.8/21 CHEMEK-C-1 C:US 1:3561(11) 2:3561(218) 3:1240 4:1239 5:1800 6:2149 7:174 199.203.70/24 ELRON-C-BLK1 C:US 1:1324 2:1660 199.203.71/24 ELRON-C-BLK1 C:US 1:1324 2:1660 199.203.72/24 ELRON-C-BLK1 C:US 1:1324 2:1660 199.203.73/24 ELRON-C-BLK1 C:US 1:1324 2:1660 199.203.74/24 ELRON-C-BLK1 C:US 1:1324 2:1660 199.203.75/24 ELRON-C-BLK1 C:US 1:1324 2:1660 199.203.76/24 ELRON-C-BLK1 C:US 1:1324 2:1660 199.203.77/24 ELRON-C-BLK1 C:US 1:1324 2:1660 199.203.78/24 ELRON-C-BLK1 C:US 1:1324 2:1660 199.203.79/24 ELRON-C-BLK1 C:US 1:1324 2:1660 199.203.80/24 ELRON-C-BLK1 C:US 1:1324 2:1660 199.203.81/24 ELRON-C-BLK1 C:US 1:1324 2:1660 199.203.82/24 ELRON-C-BLK1 C:US 1:1324 2:1660 199.203.83/24 ELRON-C-BLK1 C:US 1:1324 2:1660 199.203.84/24 ELRON-C-BLK1 C:US 1:1324 2:1660 199.234.176/24(U) WHSD-CIDR C:US 1:3577 2:1324 199.234.177/24(U) WHSD-CIDR C:US 1:3577 2:1324 202.19.144/21 NETBLK-SHIGAMEDINET C:JP 1:1240 2:1800 3:1239 202.31.208/22 APNIC-CIDR-BLK C:KR 1:1800 2:1240 202.42.195/24 IME-SG C:SG 1:97 202.42.196/24 TRITECH-SG C:SG 1:97 202.42.197/24 TECHPARKS-SG C:SG 1:97 202.42.198/24 ACS-SG C:SG 1:97 202.42.199/24 FUJITSU-SG C:SG 1:97 202.42.200/24 IMEDIA-SG C:SG 1:97 202.42.201/24 NEC-SG C:SG 1:97 202.42.202/24 SCOMINDEF-SG C:SG 1:97 202.42.203/24 MITA-SG C:SG 1:97 202.42.204/24 TECHNET-SG-C-42-204 C:SG 1:97 202.42.205/24 TECHNET-SG-C-42-205 C:SG 1:97 202.42.206/24 YOKOGAWA-SG C:SG 1:97 202.42.208/24 MRTC-SG-C-42-208 C:SG 1:97 202.42.209/24 MRTC-SG-C-42-209 C:SG 1:97 202.42.240/24 SNS-SG-C-42-240 C:SG 1:97 202.42.241/24 SNS-SG-C-42-241 C:SG 1:97 202.42.242/24 SNS-SG-C-42-242 C:SG 1:97 202.42.243/24 SNS-SG-C-42-243 C:SG 1:97 202.42.244/24 SNS-SG-C-42-244 C:SG 1:97 202.42.245/24 SNS-SG-C-42-245 C:SG 1:97 202.42.246/24 SNS-SG-C-42-246 C:SG 1:97 202.42.247/24 SNS-SG-C-42-247 C:SG 1:97 202.42.249/24 SGH2-SG-C-42-249 C:SG 1:97 202.42.250/24 SGH2-SG-C-42-250 C:SG 1:97 202.42.251/24 SGH2-SG-C-42-251 C:SG 1:97 202.42.252/24 SGH2-SG-C-42-252 C:SG 1:97 202.42.253/24 SGH2-SG-C-42-253 C:SG 1:97 202.42.254/24 SGH2-SG-C-42-254 C:SG 1:97 202.42.255/24 SGH2-SG-C-42-255 C:SG 1:97 202.253.248/22 KPUMNET C:JP 1:1240 2:1800 3:1239 203.255.64/19 APNIC-CIDR-BLK C:KR 1:1800 2:1240 204.6.39/24 PSINET-C4 C:US 1:2149 2:174 204.6.52/24 PSINET-C4 C:US 1:2149 2:174 204.6.53/24 PSINET-C5 C:US 1:2149 2:174 204.19.211/24 STARBER C:CA 1:2493(35) 2:2493(91) 204.19.228/24 SESTECH C:CA 1:2493(35) 2:2493(91) 204.19.229/24 ANIQ-NET C:CA 1:2493(35) 2:2493(91) 204.27.195/24 INFOANALYTIC C:US 1:1239 2:1800 3:1240 204.27.255/24 NET-MUSA-CAD C:US 1:1740(218) 2:1740(135) 204.29.70/24 TALLADEGA-NET C:US 1:3561(218) 2:3561(11) 3:279 4:86 204.40.150/24 RCBE C:CA 1:577(133) 2:577(137) 3:577(143) 4:3561(218) 5:3561(11) 204.41.11/24 SCAR-C-41-11 C:CA 1:577(133) 2:577(137) 3:577(143) 4:3561(218) 5:3561(11) 204.41.12/24 SCAR-C-41-12 C:CA 1:577(133) 2:577(137) 3:577(143) 4:3561(218) 5:3561(11) 204.41.29/24 SCAR C:CA 1:577(133) 2:577(137) 3:577(143) 4:3561(218) 5:3561(11) 204.50.41/24 NET-TST-MEDHAT C:CA 1:1240 2:1800 3:1239 204.50.42/24 NET-NETSHOP1 C:CA 1:1240 2:1800 3:1239 204.50.43/24 NET-NETSHOP2 C:CA 1:1240 2:1800 3:1239 204.52.215/24 RUTGERS-UMDNJ C:US 1:97 2:701(136) 3:701(134) 204.52.237/24 PRC C:US 1:1240 2:1800 3:1239 204.62.233/24 PROGRESS2 C:US 1:1240 2:1800 3:1239 204.63.16/20 NETBLK-FL-LEG C:US 1:1800 2:1239 3:1240 204.73.184/22 CTSCREATIVE C:US 1:1225(130) 2:1225(129) 3:1225(131) 4:1239 5:1240 6:1800 204.73.188/22 CTSCREATIVE1 C:US 1:1225(130) 2:1225(129) 3:1225(131) 4:1239 5:1240 6:1800 204.73.218/24 KAVOURAS1 C:US 1:1225(130) 2:1225(129) 3:1225(131) 4:1239 5:1240 6:1800 204.74.65/24 IMN C:US : 204.74.66/24 ANTIOCH C:US : 204.74.127/24 IMN C:US : 204.75.207/24 NET-ERAU-AZ-2 C:US 1:1240 2:1800 3:1239 4:210 5:209 204.80.96/19 METAWIRE C:US 1:1740(218) 2:1740(135) 204.92.4/22 IO-NET6 C:CA 1:701(136) 2:701(134) 204.92.8/24 IO-NET6 C:CA 1:701(136) 2:701(134) 204.94.52/24 WHIDBEY C:US 1:1240 2:1800 3:1239 204.96.4/22 NET-UNICOMP C:US 1:1800 2:1239 3:1240 204.97.252/23 NET-ICI C:US 1:1239 2:1800 3:1240 204.101.47/24 QUETEL C:CA 1:1239 2:1800 3:1240 204.116/16 NET-SBN-CIDR-1 C:US 1:1800 2:1240 3:1239 204.120.144/20 STATE C:US 1:1239 2:1800 3:1240 204.120.160/22 NET-NETFACTORY C:US 1:1239 2:1800 3:1240 204.120.180/22 NET-ATHENET C:US 1:1239 2:1800 3:1240 204.126.102/24 KIRO-C-126-102 C:US 1:73 2:685 3:101 204.126.103/24 KIRO-C-126-103 C:US 1:73 2:685 3:101 204.130.218/24 KENTLAW3 C:US 1:1225(130) 2:1225(129) 3:1225(131) 204.134.77/24 CSN-BLOCK-6 C:US 1:1334 204.134.78/24 CSN-BLOCK-6 C:US 1:1334 204.142.39/24 NETBLK-RIDER2 C:US 1:97 204.142.40/24 NETBLK-RIDER3 C:US 1:97 204.145.147/24 NETGATE-NET C:US 1:3830 204.153.192/22 NETBLK-ISP C:US 1:3561(11) 2:3561(218) 3:1240 4:1239 5:1800 204.164.16/24 SURETY-NET1 C:US 1:560 2:701(136) 3:701(134) 204.164.17/24 SURETY-NET2 C:US 1:560 2:701(136) 3:701(134) 204.164.80/24 NEPS-80 C:US 1:560 2:701(136) 3:701(134) 204.164.82/24 CAMBRIDGE-82 C:US 1:560 2:701(136) 3:701(134) 204.164.84/24 SRTC-84 C:US 1:560 2:701(136) 3:701(134) 204.164.88/24 DATAWARE-1 C:US 1:560 2:701(136) 3:701(134) 204.164.89/24 DATAWARE-2 C:US 1:560 2:701(136) 3:701(134) 204.168.82/24 NET-NAZ C:US 1:1239 2:1800 3:1240 204.170.1/24(U) MEDCOLPA-CIDR C:US 1:1324 2:3577 204.170.2/24(U) MEDCOLPA-CIDR C:US 1:1324 2:3577 204.170.3/24(U) MEDCOLPA-CIDR C:US 1:1324 2:3577 204.170.4/24(U) MEDCOLPA-CIDR C:US 1:1324 2:3577 204.170.5/24(U) MEDCOLPA-CIDR C:US 1:1324 2:3577 204.170.6/24(U) MEDCOLPA-CIDR C:US 1:1324 2:3577 204.170.7/24(U) MEDCOLPA-CIDR C:US 1:1324 2:3577 204.170.8/24(U) MEDCOLPA-CIDR C:US 1:1324 2:3577 204.170.9/24(U) MEDCOLPA-CIDR C:US 1:1324 2:3577 204.170.10/24(U) MEDCOLPA-CIDR C:US 1:1324 2:3577 204.170.11/24(U) MEDCOLPA-CIDR C:US 1:1324 2:3577 204.170.12/24(U) MEDCOLPA-CIDR C:US 1:1324 2:3577 204.170.13/24(U) MEDCOLPA-CIDR C:US 1:1324 2:3577 204.170.14/24(U) MEDCOLPA-CIDR C:US 1:1324 2:3577 204.170.15/24(U) MEDCOLPA-CIDR C:US 1:1324 2:3577 204.170.16/23 BELL-ATL-CIDR C:US 1:1324 2:3576 204.170.16/24(U) BELL-ATL-CIDR C:US 1:1324 2:3576 204.170.17/24(U) BELL-ATL-CIDR C:US 1:1324 2:3576 204.170.18/23 SUNGARD-CIDR C:US 1:1324 2:3577 204.170.18/24(U) SUNGARD-CIDR C:US 1:1324 2:3577 204.170.19/24(U) SUNGARD-CIDR C:US 1:1324 2:3577 204.170.20/23 SHSL-CIDR C:US 1:1324 2:3577 204.170.20/24(U) SHSL-CIDR C:US 1:1324 2:3577 204.170.58/23 LEBANET-CIDR C:US 1:3577 2:1324 204.170.58/24(U) LEBANET-CIDR C:US 1:3577 2:1324 204.170.59/24(U) LEBANET-CIDR C:US 1:3577 2:1324 204.171.1/24(U) WESTMINSTER-CIDR C:US 1:3577 2:1324 204.171.2/24(U) WESTMINSTER-CIDR C:US 1:3577 2:1324 204.171.3/24(U) WESTMINSTER-CIDR C:US 1:3577 2:1324 204.171.4/24(U) WESTMINSTER-CIDR C:US 1:3577 2:1324 204.171.5/24(U) WESTMINSTER-CIDR C:US 1:3577 2:1324 204.171.6/24(U) WESTMINSTER-CIDR C:US 1:3577 2:1324 204.171.7/24(U) WESTMINSTER-CIDR C:US 1:3577 2:1324 204.171.8/24(U) WESTMINSTER-CIDR C:US 1:3577 2:1324 204.171.9/24(U) WESTMINSTER-CIDR C:US 1:3577 2:1324 204.171.10/24(U) WESTMINSTER-CIDR C:US 1:3577 2:1324 204.171.11/24(U) WESTMINSTER-CIDR C:US 1:3577 2:1324 204.171.12/24(U) WESTMINSTER-CIDR C:US 1:3577 2:1324 204.171.13/24(U) WESTMINSTER-CIDR C:US 1:3577 2:1324 204.171.14/24(U) WESTMINSTER-CIDR C:US 1:3577 2:1324 204.171.15/24(U) WESTMINSTER-CIDR C:US 1:3577 2:1324 204.171.16/22 STARGATE-CIDR C:US 1:3577 2:1324 204.171.16/24(U) NET-STARGATE C:US 1:3577 2:1324 204.171.17/24(U) NET-STARGATE C:US 1:3577 2:1324 204.171.18/24(U) NET-STARGATE C:US 1:3577 2:1324 204.171.19/24(U) NET-STARGATE C:US 1:3577 2:1324 204.171.20/23 COMPCEN-CIDR C:US 1:3577 2:1324 204.171.20/24(U) COMPCEN-CIDR C:US 1:3577 2:1324 204.171.32/21 TELERAMA-CIDR C:US 1:3577 2:1324 204.171.32/24 TELERAMA-CIDR C:US 1:3577 2:1324 204.171.33/24(U) TELERAMA-CIDR C:US 1:3577 2:1324 204.171.34/24(U) TELERAMA-CIDR C:US 1:3577 2:1324 204.171.35/24(U) TELERAMA-CIDR C:US 1:3577 2:1324 204.171.36/24(U) TELERAMA-CIDR C:US 1:3577 2:1324 204.171.37/24(U) TELERAMA-CIDR C:US 1:3577 2:1324 204.171.38/24(U) TELERAMA-CIDR C:US 1:3577 2:1324 204.171.39/24(U) TELERAMA-CIDR C:US 1:3577 2:1324 204.171.40/24(U) TELERAMA-CIDR C:US 1:3577 2:1324 204.171.41/24(U) TELERAMA-CIDR C:US 1:3577 2:1324 204.171.42/24(U) TELERAMA-CIDR C:US 1:3577 2:1324 204.171.43/24(U) TELERAMA-CIDR C:US 1:3577 2:1324 204.171.44/24(U) TELERAMA-CIDR C:US 1:3577 2:1324 204.171.45/24(U) TELERAMA-CIDR C:US 1:3577 2:1324 204.171.46/24(U) TELERAMA-CIDR C:US 1:3577 2:1324 204.171.47/24(U) TELERAMA-CIDR C:US 1:3577 2:1324 204.171.48/21 PENNET-CIDR C:US 1:3577 204.171.48/23 TELERAMA-CIDR C:US 1:3577 2:1324 204.171.49/24(U) TELERAMA-CIDR C:US 1:3577 2:1324 204.171.50/24 PENNET-CIDR C:US 1:3577 204.171.51/24 PENNET-CIDR C:US 1:3577 204.171.52/24 PENNET-CIDR C:US 1:3577 204.171.53/24 PENNET-CIDR C:US 1:3577 204.171.54/24 PENNET-CIDR C:US 1:3577 204.171.55/24 PENNET-CIDR C:US 1:3577 204.171.60/23 BELL-ATL-CIDR C:US 1:1324 2:3577 204.171.60/24 BELL-ATL-CIDR C:US 1:1324 2:3577 204.171.61/24 BELL-ATL-CIDR C:US 1:1324 2:3577 204.171.62/23 PGH-PG-CIDR C:US 1:3577 2:1324 204.171.62/24 PGH-PG-CIDR C:US 1:3577 2:1324 204.174.4/24 PR-COC-COM C:CA 1:577(143) 2:577(133) 3:577(137) 4:3561(11) 5:3561(218) 204.174.5/24 PR-COC-COM C:CA 1:577(143) 2:577(133) 3:577(137) 4:3561(11) 5:3561(218) 204.174.37/24 STELLARSYS C:CA 1:577(143) 2:577(133) 3:577(137) 4:3561(11) 5:3561(218) 204.176.68/24 RIFM-NET C:US 1:701(136) 2:701(134) 204.176.88/24 SIDEWINDER-NET C:US 1:701(136) 2:701(134) 204.176.90/24 EVENTIDE-NET C:US 1:701(136) 2:701(134) 204.176.111/24 LUCKMAN C:US 1:701(136) 2:701(134) 204.176.124/24 EXCELTEL-NET C:US 1:1957 204.176.148/24 THEPOINT-NET C:US 1:701(136) 2:701(134) 204.176.149/24 THEPOINT-NET C:US 1:701(136) 2:701(134) 204.176.150/24 THEPOINT-NET C:US 1:701(136) 2:701(134) 204.176.151/24 THEPOINT-NET C:US 1:701(136) 2:701(134) 204.176.154/24 MICRION-NET C:US 1:701(136) 2:701(134) 204.176.155/24 SNIDER-NET C:US 1:701(136) 2:701(134) 204.176.213/24 BWY-NET C:US 1:701(136) 2:701(134) 204.176.216/24 PPS-NETBLK C:US 1:701(136) 2:701(134) 204.176.217/24 PPS-NETBLK C:US 1:701(136) 2:701(134) 204.176.218/24 PPS-NETBLK C:US 1:701(136) 2:701(134) 204.176.219/24 PPS-NETBLK C:US 1:701(136) 2:701(134) 204.177.122/24 CLIPPER C:US 1:701(136) 2:701(134) 204.177.219/24 NEWBRIDGE-NET C:US 1:701(136) 2:701(134) 204.177.228/24 MINDBANK C:US 1:701(136) 2:701(134) 204.177.232/24 ARNET C:US 1:701(136) 2:701(134) 204.178.32/24 INCH C:US 1:701(136) 2:701(134) 204.178.35/24 PICNET-NET C:US 1:701(136) 2:701(134) 204.178.38/24 SCIFI-NET C:US 1:701(136) 2:701(134) 204.178.40/21 ANALOGIC-NETBLK C:US 1:701(136) 2:701(134) 204.178.57/24 TADPOLE2 C:US 1:701(136) 2:701(134) 204.178.96/19 NETBLK-PLATCO C:US 1:701(136) 2:701(134) 204.178.128/20 ECHONYC C:US 1:701(136) 2:701(134) 204.181.80/24 AUSDATA C:US 1:1800 2:1240 3:1239 204.182.224/24 SPRINT-BLKC C:US 1:1800 2:1239 3:1240 204.183.218/23 NET-INTERCOM C:US 1:1800 2:1239 3:1240 204.188.64/18 MCI-PROVIDER2-HAY C:US 1:3561(11) 3:3561(218) 4:86 5:279 6:1879 7:3561(136) 204.188.128/19 MCI-PROVIDER2-HAY2 C:US 1:3561(11) 3:3561(218) 4:86 5:279 6:1879 7:3561(136) 204.188.192/18 MARIN-SCHOOL C:US 1:3561(11) 2:3561(218) 3:1240 4:1800 5:1239 204.189.0/18 MCI-PROVIDER3-HAY C:US 1:3561(11) 3:3561(218) 4:86 5:279 6:1879 7:3561(136) 204.191.1/24 FONOROLA2 C:CA 1:2493(35) 2:2493(91) 204.191.4/24 FONOROLA2 C:CA 1:2493(35) 2:2493(91) 204.191.5/24 FONOROLA2 C:CA 1:2493(35) 2:2493(91) 204.191.6/24 FONOROLA2 C:CA 1:2493(35) 2:2493(91) 204.191.7/24 FONOROLA2 C:CA 1:2493(35) 2:2493(91) 204.191.8/24 FONOROLA2 C:CA 1:2493(35) 2:2493(91) 204.191.9/24 FONOROLA2 C:CA 1:2493(35) 2:2493(91) 204.191.10/24 FONOROLA2 C:CA 1:2493(35) 2:2493(91) 204.191.11/24 FONOROLA2 C:CA 1:2493(35) 2:2493(91) 204.191.32/24 FONOROLA2 C:CA 1:2493(35) 2:2493(91) 204.191.33/24 FONOROLA2 C:CA 1:2493(35) 2:2493(91) 204.191.34/24 FONOROLA2 C:CA 1:2493(35) 2:2493(91) 204.191.35/24 FONOROLA2 C:CA 1:2493(35) 2:2493(91) 204.191.40/24 FONOROLA2 C:CA 1:2493(35) 2:2493(91) 204.191.41/24 FONOROLA2 C:CA 1:2493(35) 2:2493(91) 204.191.42/24 FONOROLA2 C:CA 1:2493(35) 2:2493(91) 204.191.43/24 FONOROLA2 C:CA 1:2493(35) 2:2493(91) 204.191.48/24 FONOROLA2 C:CA 1:2493(35) 2:2493(91) 204.191.49/24 FONOROLA2 C:CA 1:2493(35) 2:2493(91) 204.191.50/24 FONOROLA2 C:CA 1:2493(35) 2:2493(91) 204.191.51/24 FONOROLA2 C:CA 1:2493(35) 2:2493(91) 204.191.64/24 FONOROLA2 C:CA 1:2493(35) 2:2493(91) 204.191.65/24 FONOROLA2 C:CA 1:2493(35) 2:2493(91) 204.191.66/24 FONOROLA2 C:CA 1:2493(35) 2:2493(91) 204.191.67/24 FONOROLA2 C:CA 1:2493(35) 2:2493(91) 204.191.68/24 FONOROLA2 C:CA 1:2493(35) 2:2493(91) 204.191.69/24 FONOROLA2 C:CA 1:2493(35) 2:2493(91) 204.191.70/24 FONOROLA2 C:CA 1:2493(35) 2:2493(91) 204.191.71/24 FONOROLA2 C:CA 1:2493(35) 2:2493(91) 204.191.72/24 FONOROLA2 C:CA 1:2493(35) 2:2493(91) 204.191.73/24 FONOROLA2 C:CA 1:2493(35) 2:2493(91) 204.191.74/24 FONOROLA2 C:CA 1:2493(35) 2:2493(91) 204.191.75/24 FONOROLA2 C:CA 1:2493(35) 2:2493(91) 204.191.76/24 FONOROLA2 C:CA 1:2493(35) 2:2493(91) 204.191.77/24 FONOROLA2 C:CA 1:2493(35) 2:2493(91) 204.191.78/24 FONOROLA2 C:CA 1:2493(35) 2:2493(91) 204.191.79/24 FONOROLA2 C:CA 1:2493(35) 2:2493(91) 204.191.176/24 FONOROLA2 C:CA 1:2493(91) 2:2493(35) 204.191.177/24 FONOROLA2 C:CA 1:2493(91) 2:2493(35) 204.191.178/24 FONOROLA2 C:CA 1:2493(91) 2:2493(35) 204.191.179/24 FONOROLA2 C:CA 1:2493(91) 2:2493(35) 204.191.180/24 FONOROLA2 C:CA 1:2493(91) 2:2493(35) 204.191.181/24 FONOROLA2 C:CA 1:2493(91) 2:2493(35) 204.191.182/24 FONOROLA2 C:CA 1:2493(91) 2:2493(35) 204.191.183/24 FONOROLA2 C:CA 1:2493(91) 2:2493(35) 204.191.184/24 FONOROLA2 C:CA 1:2493(91) 2:2493(35) 204.191.185/24 FONOROLA2 C:CA 1:2493(91) 2:2493(35) 204.191.186/24 FONOROLA2 C:CA 1:2493(91) 2:2493(35) 204.191.187/24 FONOROLA2 C:CA 1:2493(91) 2:2493(35) 204.191.188/24 FONOROLA2 C:CA 1:2493(91) 2:2493(35) 204.191.189/24 FONOROLA2 C:CA 1:2493(91) 2:2493(35) 204.191.190/24 FONOROLA2 C:CA 1:2493(91) 2:2493(35) 204.191.191/24 FONOROLA2 C:CA 1:2493(91) 2:2493(35) 204.191.196/24 FONOROLA2 C:CA 1:2493(91) 2:2493(35) 204.191.197/24 FONOROLA2 C:CA 1:2493(91) 2:2493(35) 204.191.198/24 FONOROLA2 C:CA 1:2493(91) 2:2493(35) 204.191.199/24 FONOROLA2 C:CA 1:2493(91) 2:2493(35) 204.191.208/24 FONOROLA2 C:CA 1:2493(91) 2:2493(35) 204.191.209/24 FONOROLA2 C:CA 1:2493(91) 2:2493(35) 204.191.210/24 FONOROLA2 C:CA 1:2493(91) 2:2493(35) 204.191.211/24 FONOROLA2 C:CA 1:2493(91) 2:2493(35) 204.191.220/24 FONOROLA2 C:CA 1:2493(91) 2:2493(35) 204.191.221/24 FONOROLA2 C:CA 1:2493(91) 2:2493(35) 204.191.222/24 FONOROLA2 C:CA 1:2493(91) 2:2493(35) 204.191.223/24 FONOROLA2 C:CA 1:2493(91) 2:2493(35) 204.191.240/24 FONOROLA2 C:CA 1:2493(91) 2:2493(35) 204.191.241/24 FONOROLA2 C:CA 1:2493(91) 2:2493(35) 204.191.242/24 FONOROLA2 C:CA 1:2493(91) 2:2493(35) 204.191.243/24 FONOROLA2 C:CA 1:2493(91) 2:2493(35) 204.191.248/24 FONOROLA2 C:CA 1:2493(91) 2:2493(35) 204.191.249/24 FONOROLA2 C:CA 1:2493(91) 2:2493(35) 204.191.250/24 FONOROLA2 C:CA 1:2493(91) 2:2493(35) 204.191.251/24 FONOROLA2 C:CA 1:2493(91) 2:2493(35) 204.196/16 NETBLK-SURA-CIDR-4 C:US 1:3561(218) 2:3561(11) 3:86 4:279 204.197/16 NETBLK-SURA-CIDR-4 C:US 1:3561(218) 2:3561(11) 3:86 4:279 204.197.0/19 LARC-NET C:US 1:3561(218) 2:3561(11) 3:86 4:279 204.198/16 NETBLK-SURA-CIDR-4 C:US 1:3561(218) 2:3561(11) 3:279 4:86 204.198.32/21(U) TIMES-ST-PETE-FL-US C:US 1:3561(218) 2:3561(11) 3:279 4:86 204.198.40/22(U) CO-ALACHUA-FL-US C:US 1:3561(218) 2:3561(11) 3:279 4:86 204.199/16 NETBLK-SURA-CIDR-4 C:US 1:3561(218) 2:3561(11) 3:279 4:86 204.212.41/24 NET-INFOSERVER C:US 1:1240 2:1800 3:1239 204.212.42/24 SPEED2 C:US 2:1800 3:1239 204.212.43/24 NET-VEGAS C:US 1:1240 2:1800 3:1239 204.220.4/24 CRAY-C2 C:US 1:1225(130) 2:1225(129) 3:1225(131) 4:1239 5:1240 6:1800 204.220.8/22 EFJOHNSON C:US 1:1225(130) 2:1225(129) 3:1225(131) 4:1239 5:1240 6:1800 204.220.32/22 WAVEFRONT C:US 1:1225(130) 2:1225(129) 3:1225(131) 4:1239 5:1240 6:1800 Deletions: --199.4.64/24 NBN-NET-C-4-64 C:US 1:1240 2:1800 --199.4.65/24 NBN-NET-C-4-65 C:US 1:1240 2:1800 --199.4.66/24 NBN-NET-C-4-66 C:US 1:1240 2:1800 --199.4.67/24 NBN-NET-C-4-67 C:US 1:1240 2:1800 --199.4.68/24 NBN-NET-C-4-68 C:US 1:1240 2:1800 --199.4.69/24 NBN-NET-C-4-69 C:US 1:1240 2:1800 --199.4.70/24 NBN-NET-C-4-70 C:US 1:1240 2:1800 --199.4.71/24 NBN-NET-C-4-71 C:US 1:1240 2:1800 --199.4.72/24 NBN-NET-C-4-72 C:US 1:1240 2:1800 --199.4.73/24 NBN-NET-C-4-73 C:US 1:1240 2:1800 --199.4.74/24 NBN-NET-C-4-74 C:US 1:1240 2:1800 --199.4.75/24 NBN-NET-C-4-75 C:US 1:1240 2:1800 --199.4.76/24 NBN-NET-C-4-76 C:US 1:1240 2:1800 --199.4.77/24 NBN-NET-C-4-77 C:US 1:1240 2:1800 --199.4.78/24 NBN-NET-C-4-78 C:US 1:1240 2:1800 --199.4.79/24 NBN-NET-C-4-79 C:US 1:1240 2:1800 --199.4.80/24 NBN-NET-C-4-80 C:US 1:1240 2:1800 --199.4.81/24 NBN-NET-C-4-81 C:US 1:1240 2:1800 --199.4.82/24 NBN-NET-C-4-82 C:US 1:1240 2:1800 --199.4.83/24 NBN-NET-C-4-83 C:US 1:1240 2:1800 --199.4.84/24 NBN-NET-C-4-84 C:US 1:1240 2:1800 --199.4.85/24 NBN-NET-C-4-85 C:US 1:1240 2:1800 --199.4.86/24 NBN-NET-C-4-86 C:US 1:1240 2:1800 --199.4.87/24 NBN-NET-C-4-87 C:US 1:1240 2:1800 --199.4.88/24 NBN-NET-C-4-88 C:US 1:1240 2:1800 --199.4.89/24 NBN-NET-C-4-89 C:US 1:1240 2:1800 --199.4.90/24 NBN-NET-C-4-90 C:US 1:1240 2:1800 --199.4.91/24 NBN-NET-C-4-91 C:US 1:1240 2:1800 --199.4.92/24 NBN-NET-C-4-92 C:US 1:1240 2:1800 --199.4.93/24 NBN-NET-C-4-93 C:US 1:1240 2:1800 --199.4.94/24 NBN-NET-C-4-94 C:US 1:1240 2:1800 --199.4.95/24 NBN-NET-C-4-95 C:US 1:1240 2:1800 --199.4.96/24 NBN-NET-C-4-96 C:US 1:1240 2:1800 --199.4.97/24 NBN-NET-C-4-97 C:US 1:1240 2:1800 --199.4.98/24 NBN-NET-C-4-98 C:US 1:1240 2:1800 --199.4.99/24 NBN-NET-C-4-99 C:US 1:1240 2:1800 --199.4.100/24 NBN-NET-C-4-100 C:US 1:1240 2:1800 --199.4.101/24 NBN-NET-C-4-101 C:US 1:1240 2:1800 --199.4.102/24 NBN-NET-C-4-102 C:US 1:1240 2:1800 --199.4.103/24 NBN-NET-C-4-103 C:US 1:1240 2:1800 --199.4.104/24 NBN-NET-C-4-104 C:US 1:1240 2:1800 --199.4.105/24 NBN-NET-C-4-105 C:US 1:1240 2:1800 --199.4.106/24 NBN-NET-C-4-106 C:US 1:1240 2:1800 --199.4.107/24 NBN-NET-C-4-107 C:US 1:1240 2:1800 --199.4.108/24 NBN-NET-C-4-108 C:US 1:1240 2:1800 --199.4.109/24 NBN-NET-C-4-109 C:US 1:1240 2:1800 --199.4.110/24 NBN-NET-C-4-110 C:US 1:1240 2:1800 --199.4.111/24 NBN-NET-C-4-111 C:US 1:1240 2:1800 --199.4.112/24 NBN-NET-C-4-112 C:US 1:1240 2:1800 --199.4.113/24 NBN-NET-C-4-113 C:US 1:1240 2:1800 --199.4.114/24 NBN-NET-C-4-114 C:US 1:1240 2:1800 --199.4.115/24 NBN-NET-C-4-115 C:US 1:1240 2:1800 --199.4.116/24 NBN-NET-C-4-116 C:US 1:1240 2:1800 --199.4.117/24 NBN-NET-C-4-117 C:US 1:1240 2:1800 --199.4.118/24 NBN-NET-C-4-118 C:US 1:1240 2:1800 --199.4.119/24 NBN-NET-C-4-119 C:US 1:1240 2:1800 --199.4.120/24 NBN-NET-C-4-120 C:US 1:1240 2:1800 --199.4.121/24 NBN-NET-C-4-121 C:US 1:1240 2:1800 --199.4.122/24 NBN-NET-C-4-122 C:US 1:1240 2:1800 --199.4.123/24 NBN-NET-C-4-123 C:US 1:1240 2:1800 --199.4.124/24 NBN-NET-C-4-124 C:US 1:1240 2:1800 --199.4.125/24 NBN-NET-C-4-125 C:US 1:1240 2:1800 --199.4.126/24 NBN-NET-C-4-126 C:US 1:1240 2:1800 --199.4.127/24 NBN-NET-C-4-127 C:US 1:1240 2:1800 --202.19.144/24 SHIGAMEDINET1 C:JP 1:297(144) 2:372 3:297(145) --202.19.145/24 SHIGAMEDINET2 C:JP 1:297(144) 2:372 3:297(145) --202.19.146/24 SHIGAMEDINET3 C:JP 1:297(144) 2:372 3:297(145) --202.19.147/24 SHIGAMEDINET4 C:JP 1:297(144) 2:372 3:297(145) --202.19.148/24 SHIGAMEDINET5 C:JP 1:297(144) 2:372 3:297(145) --202.19.149/24 SHIGAMEDINET6 C:JP 1:297(144) 2:372 3:297(145) --202.19.150/24 SHIGAMEDINET7 C:JP 1:297(144) 2:372 3:297(145) --202.19.151/24 SHIGAMEDINET8 C:JP 1:297(144) 2:372 3:297(145) --204.116.0/18 NET-SBN-CIDR-1 C:US 1:1800 2:1240 3:1239 4:1329 --204.216/16 NETBLK-PSI-C C:US 1:2149 2:174 Expanded listing, sorted by country, then by organization: ========================================================== The "Expanded Listings" section of this NWG report has been retired since it is sorted by countries and network organization addresses. The replacement configuration generation system is based on the Internet Routing Registry (briefly called the "Global Routing Registry"). See the file ftp.ra.net:pub/radb/OVERVIEW for more information. The remainder of this report will also be retired shortly. AS690 CIDR Squeezings Report: 9873 Nets, 164 ASs, 2563 Aggregates ------------------------------------------------------------------ 9873 (85%) of the ever-announced more-specific routes within aggregates have been withdrawn. 374 of those were withdrawn within the last week. 175 the week before that. 53 the week before that. 164 ASs have registered aggregates in the PRDB. 101 of those are announcing aggregates. 79 have withdrawn at least one more specific route. 2563 Aggregates are configured. 1848 of these were Top-Level Aggregates (not nested in another aggregate). 1414 of these are being announced to AS690. 1012 of those have at least one subnet configured (the other 402 may be saving the Internet future subnet announcements). 852 have stopped announcing at least one configured more specific route. 826 have stopped announcing half of their configured more specific routes. 768 have stopped announcing most (80%) of their more specific routes. See merit.edu:pub/nsfnet/cidr/cidr_savings for more detail. ----------------------------------------------------------- ========================================================== The configuration reports which reflect today's update will be available for anonymous ftp on nic.merit.edu by 08:00 EST : configuration reports -- nic.merit.edu:nsfnet/announced.networks: as-as.now as-gw.now ans_core.now country.now net-comp.now nets.doc nets.non-classful nets.tag.now nets.unl.now NSS routing software configuration files -- nic.merit.edu:nsfnet/backbone.configuration: gated.nss<NSS number>.t3p Information is also avaiable through the PRDB whois server. Type "whois -h prdb.merit.edu help" for details. -------------------------------------------------------------------------- PRDB CHANGES: (Updated December 16, 1994) In January 1995, as part of the transition to the new Internet Routing Registry (IRR), the Policy Routing Database (PRDB) will be retired. Many of the functions of the PRDB (including generation of router configurations for NSFNET) will be produced based on data from the Global Routing Registry. This change to the NSFNET Backbone service will involve the following changes: - The method for submitting new nets to be routed over AS690 will change. Instead of submitting a NACR to nsfnet-admin(a)merit.edu, you will need to submit a "route template" to auto-dbm(a)radb.ra.net . - Additions and entries to the new registry will be made by the Home AS which creates the route for each net, rather than being submitted by a AS690 peer AS. - Most of the PRDB reports (listed above) will no longer be produced. Equivalent information for most of these reports is available from the global Routing Registry. These are major changes to the system. These changes are being made in order to migrate NSFNET customers and the global user community to a global Internet Routing Registry system, which will be more capable of supporting user needs after the termination of the NSFNET Backbone services in April 1995. For more information, set your web browser to http://www.ra.net/rrinfo.html , or use anonymous ftp to obtain the files "OVERVIEW" and "transition.plan" from the directory "ftp.ra.net:pub/radb". Merit would like to minimize the number of problems that this transition may cause you. In order to help us help you through the transition, please send your concerns, your needs, and suggestions on how we can make this happen smoothly to merit-ie(a)merit.edu. The archived discussion list "db-disc(a)merit.edu" also exists for discussion of PRDB and RADB issues. Send a message to "db-disc-request(a)merit.edu" to subscribe. --Dale Johnson (dsj(a)merit.edu) -------------------------------------------------------------------------- Please send all requests for configuration changes to nsfnet-admin(a)merit.edu using the NSFNET configuration forms. The forms are available on-line from the nic.merit.edu machine. Use ftp and the anonymous login to get on the machine. Do a "cd nsfnet/announced.networks" and get the files template.net, template.net.README, template.gate, and template.as. *** Note: As of March 1, 1994, NSFNET AUP NACRs must use the template.net *** (NACR) version 7.1, or the NACR will be returned unprocessed. ******************************* --Steven J. Richardson Merit/NSFNET sjr(a)merit.edu

1 0

Additions
by smm＠twain.merit.edu 16 Jan '95

16 Jan '95

1 0

Additions
by smm＠twain.merit.edu 16 Jan '95

16 Jan '95

1 0

Re: Draft NETSTAT Minutes for 7 Dec. 1995
by Tired of the Information Superhype 15 Jan '95

15 Jan '95

>I have some ASCII pictures here and there I could >forward you and anyone else who's interested and who >didn't see them on whatever newsfroup I posted them to >(ba.internet or alt.internet.services, I can't remember) >not long before IETF. Thank you for the corrections... very reassuring since we are scheduled to switch to SprintLink soon. May I recommend that you provide information about your network on a web server, say the one at www.sprintlink.net, which currently has only a little advertising blurb? Many of us are finding web servers convenient to disseminate this type of information. I have attempted to start describing the network in our area via http://mon.cc.utah.edu, but I'm afraid it's still an inadequate model, I'm sure you could do better. Thanks -- Walt -------

1 0

Re: Draft NETSTAT Minutes for 7 Dec. 1995
by Sean Doran 14 Jan '95

14 Jan '95

| SprintLink, Sean Doran <smd(a)sprint.net> | Sprintlink's T1 backbone is melting down. They're converting to DS- | 3s or parallel T1s in the next few weeks.[see diagram]. T3 customers | feed directly into BB routers to avoid saturating local FDDI rings | For trans-US international connectivity, ICM has 2 T3 between | Stockton, CA and DC. The design goal in separation of SprintLink and | ICM was the assurance of symmetry of routing. | [Context?] preservation of next hop in routing is critical feature | (could not wait for IDRP) | Q: What about fears of an ASpath explosion in routing tables? Sean: | Too late. Already here! Now, admittedly, I haven't gotten slides to you yet (sorry, sorry, firefighting...), but this is a very strange summary. I'm wondering if my accent threw you or something. Our T1 backbone was long gone and dead when I spoke. The last remaining backbone T1s (at that point 3xT1 in parallel between D.C. and Pennsauken and Pennsauken and Chicago) were to be replaced by T3s that week (and they were). The current engineering plan is to build some bandwidth for ICM traffic between D.C. and Stockton, however it won't be T3 and certainly not 2xT3. My slide (again, sorry for not getting you the copy you had asked for; the full colour hand-drawn slides are now in Sweden) showed 10Mbps. There were lots of other things that got elided from the summary, alas, like the fact that THENET and NYSERNET, OARNET and others had started preferring SprintLink over the NSFNET backbone service already, that we had more than 600 operational lines and were providing access in more than 50 countries as of the IETF conference, and the general technical rationale behind "Standard U.S. T3 Backbone Design Number One-B", including the lengthy talk by Peter Lothberg about why we have satellite customer-access ASes rather than one AS for our entire routing domain, and quite alot of discussion about routing symmetry. Fortunately, I tend to keep repeating myself at various conferences, so if I was really that difficult to follow, you can beat me over the head at the Feb. 7-9 NANOG. I have some ASCII pictures here and there I could forward you and anyone else who's interested and who didn't see them on whatever newsfroup I posted them to (ba.internet or alt.internet.services, I can't remember) not long before IETF. Sean.

1 0

Change in NACR procedures
by Elise Gerich 13 Jan '95

13 Jan '95

Some of you may receive this message twice, but I wanted to make sure that everyone who might be affected by this change received the message at least once. --Elise ---------------- Date: Fri, 13 Jan 1995 13:16:12 -0500 From: Elise Gerich <epg(a)merit.edu> Message-Id: <199501131816.NAA04899(a)home.merit.edu> To: nwg(a)home.merit.edu Subject: Change in NACR procedures In preparation for the retirement of the PRDB and the move to the Routing Arbiter (RA) architecture, Merit proposes to change our NACR-handling procedures to more closely mimic the registration procedures of the Internet Routing Registries. We propose to implement these changes on January 20, 1995. Please send any comments regarding the changes to merit-ie(a)merit.edu as soon as possible. Procedural changes: 1. NACRs for a given net will only be accepted from designated email addresses from the net's home AS or from the AS which is currently listed as the primary path according to the PRDB. To verify what the designated email addresses are for your Autonomous System number, use the whois client: whois -h prdb.merit.edu contact <as number> To update the designated email addresses for an Autonomous System, send email to DB-admin(a)ra.net. Please register the exact email address which will be used to add or change information in the PRDB. For example, if the designated email address is epg(a)merit.edu and the NACR is received from epg(a)pepper.merit.edu, it will be bounced. In general we anticipate that this change should pose little or no problem. In the event that a net changes providers, one of the following two procedures will have to be followed. Either (a) the administration of the net's home AS sends a NACR specifying the new provider as primary (and possibly deleting the old), or (b) the administration of the old provider sends the NACR. If the new provider wants to submit the NACR, they will need to send it to the administration of the home AS for forwarding to Merit. Very few administrators of home ASs which are behind ASs that peer directly with AS 690 have designated individuals and their associated email addresses as authorized to update the PRDB. For more information in establishing an aslist with Merit, please send a message to DB-admin(a)merit.edu. 2. ACKs/NACKs for NACRs will no longer be required, and in fact, will be ignored if received. 3. Copies of accepted NACRs will be sent to all associated ASs. This includes notification of changes to nets already in the PRDB. Typically, we would expect that all the ASs which are associated with a net would be aware of any change in routing preferences. However, this notification procedure will alert ASs that a change has taken place even if they had not previously been informed about the change. NACR Processing As of January 20, 1995, Merit will begin to implement this change. If mail to nsfnet-admin(a)merit.edu contains a NACR originated from an authorized account as described in procedural change (1), it will be processed. If it didn't, the mail will be bounced. If for some reason you want your NACR to be read even if it would otherwise be deemed unacceptable, include a non-null comment: field in the NACR. Summary: This is the first step in providing a transition to the RA architecture. We have been experiencing an increase in the number of NACRs which are being submitted to the NSFNET Backbone Service, many of which pertain to the movement of networks from one provider to another. For the month of December, nsfnet-admin(a)merit.edu received more than 4200 messages. More than 1200 changes were made to the PRDB on January 13, 1995. These new procedures will help to make the registration process more manageable. For those organizations which are in the process of changing to another provider (autonomous system), the organization can improve its chances of having changes to the PRDB made in a timely fashion and to protect itself against loss of reachability by: a. sending NACRs in advance of your cutover (at least one week) b. adding the new provider as secondary (tertiary, etc) c. having the new provider start announcing the route d. testing the route by having previous provider stop announcing the route e. sending a NACR deleting the previous provider Please check that you have designated correct email addresses for your Autonomous System prior to January 20,1995. Mail to nsfnet-admin(a)merit.edu which is a valid template and originates from an undesignated email address will be bounced back to the originator of the message starting on January 20, 1995. Thank you in advance for your cooperation. --Elise

1 0