January 1995 - Test - lists.nanog.org

MAP of Boulder
by Pam Ciesla 08 Feb '95

08 Feb '95

I found an old map from the last meeting in Boulder. it is available by ftp://home.merit.edu/pub/nanog/bouldermap.ps. Pam

2 1

Re: Test Route
by Robert E. Seastrom 01 Feb '95

01 Feb '95

> From: David R Conrad <davidc(a)iij.ad.jp> > > Yeah, there are 2^32 bits of address space, after all. There are? I always thought there were 32 bits of address space, not 2^32, and the code that I wrote even worked... :) > >After all, if we all do our jobs right, maybe someday we can make > >the firewalls go away.... > > If we all do our jobs right, it won't matter if someone uses 1597 > space. Firewalls will never go away -- they're too useful. Firewalls are a kludge; they're necessitated only by the lack of strong authentication in the stack. I daresay that if the current level of threat continues to escalate (to quote a friend, "it's a bad neighborhood out there"), I foresee that the need for Joe Everyman to run a firewall will diminish or disappear, and sooner - not later. Now, I won't dispute that there will be some places where either because of legacy systems in house or paranoia they continue to run a firewall. But the 95% solution will be in place, and if they previously chose to use 1597-style addresses, the 95% of the world who decided they didn't need firewalls anymore because of strong authentication will be forced to renumber. I am more than willing to admit that 1597 has its uses, and people who find rfcs 1597 and 1627 on their own, read them, and figure out whether they want to bear the risks and consequences should feel free to use the addresses. That *doesn't* mean, however, that it should be promoted or upgraded from "informational" to "recommended", and I no longer recommend it to "casual" IP users. The concept of globally unique addressing is simply far too powerful and far too useful for us to summarily and without further thought assert that firewalls are a fact of life that will be with us forever. ---Rob

3 2

Re: Test Route
by Robert E. Seastrom 31 Jan '95

31 Jan '95

> From: bmanning(a)ISI.EDU > > Hi, > Much as I like to debate RFC 1597 and Firewalls... That is not > the topic of this thread. > > I was pointing out a useful (to me) hack to verify BGP peering > and route generation w/o the need to "expose" routes that > I might not be authoritative for. > > I would like to know if others think this was/is worthwhile? If you don't propagate the route, why does it matter? ---Rob

2 1

Test Route
by bmanning＠ISI.EDU 31 Jan '95

31 Jan '95

Hi, I have recently come across the need to test BGP peering with a number of people and have found that it is occasionally useful to establish a peer and then send a test route. There were a number of options here: 1- Use a route that I should correctly source. 2- Send the loopback address 3- Use an RFC 1597 address 4- Use the TestNetwork address Due to certain vendors/ISPs desire to (correctly) squash RFC 1597 advertisments and my inability to verify routing correctness if I propogated via third-party my internal routes, I chose to use the TestNetwork. What is the TestNetwork? zed 30% whois 192.0.2.0 [No name] (NET-TEST) Netname: AMEX Netnumber: 192.0.2.0 Coordinator: Reynolds, Joyce K. (JKR1) JKRey(a)ISI.EDU (310) 822-1511 Record last updated on 24-Oct-94. This was a number allocated prior to RFC 1597 to assist people in correctly documenting how to configure IP in their documentation. (a fix for the infamous defaults SUN had in the config scripts for so many years) It's usefullness in testing devolves from its not being included in the RFC 1597 ban on forwarding. It seems to me that we should encourage any/all NSP/ISP types to block the following networks: 127.0.0/8 10.0.0/8 172.16.0/20 192.168.0/16 --bill

4 6

Re: Test Route
by postel＠ISI.EDU 31 Jan '95

31 Jan '95

Excuse me. This seems brain dead. I think the intent of 1597 was to say here are some numbers you can go play with privately. Since they are private they should never appear on the public Internet, anywhere, ever. If any router on the public Internet sees a packet to (or from) a 1597 network it can throw it in the bit bucket and forget it. It would be possible for some private experiment to use some 1597 addresses to exchange packets over a "wire". Such a wire could be implemented by some pretty complicated arrangements with conventional public Internet service providers -- but any packets with 1597 addresses would have to be encapsulated inside packets with acceptable addresses for the public Internet to go through public Internet exchange points. --jon.

5 4

Tentative NANOG agenda
by Susan R. Harris 31 Jan '95

31 Jan '95

Here's a draft of the NANOG agenda, to give you an idea of what we're planning. --Susan R. Harris, Merit -------------------------------------------------------------------- NANOG Agenda Thursday, February 9 Time Topic Presenter(s) ---- ----- ------------ 9:00 a.m. Welcome, Introductions, Elise Gerich Future Meetings 9:15 a.m. Transition Updates: NorthWestNet Steve Corbato CERFnet Pushpendra Mohta MichNet Mark Driscoll BARRNET Vince Fuller MCInet Sean Doran SprintLink Jack Waters 10:30 a.m. Break 10:45 a.m. ATM Testbeds: Kentrox ADSU status Rolf Hahn AADS Andy Schmidt PacBell Chin Yuan/Frank Liu Bellcore/ANS Curtis Villamizar MCI/ANS testing at Hayward Abir Ahnidi 12:15 p.m. Lunch 1:30 p.m Status of AADS Contingency NAP Mark Knopper 2:00 p.m. MAE-West Update Milo Medin 2:30 p.m. Traceroute for ATM PVC Topology Taso Devetzis 3:00 p.m. Break 3:15 p.m. InterNIC Update Mark Kosters 3:45 p.m. CIDR/Aggregation/Allocation Policies Sean Doran Friday, February 10 9:00 a.m. Route Server Status Yakov Rekhter 10:00 a.m. PRDB -> RADB Transition John Scudder 10:45 a.m. Break 11:00 a.m. Testing of IDRP Implementation Sue Hares/ Craig Labovitz 11:15 a.m. Route Flap Damping Algorithm Curtis Villamizer 11:30 p.m. End-to-end Problem Resolution Eric Carroll/ John Curran 12:00 p.m. Adjourn

5 6

Re: Test Route
by John Curran 31 Jan '95

31 Jan '95

At 7:15 PM 1/30/95, Jon Postel wrote: >Excuse me. > >This seems brain dead. I think the intent of 1597 was to say here >are some numbers you can go play with privately. Since they are >private they should never appear on the public Internet, anywhere, >ever. If any router on the public Internet sees a packet to (or >from) a 1597 network it can throw it in the bit bucket and forget it. > >It would be possible for some private experiment to use some 1597 >addresses to exchange packets over a "wire". Such a wire could be >implemented by some pretty complicated arrangements with conventional >public Internet service providers -- but any packets with 1597 addresses >would have to be encapsulated inside packets with acceptable addresses >for the public Internet to go through public Internet exchange points. RFC1597 addresses are those addresses whose routes do not have to be accepted from anything outside of the "local" scope. If you consider "local" to be your site, then great. If I consider "local" to be my network infrastructure (excluding your renegade site :-) that's also fine. Just as a site's network is "private" (and hence can use RFC1597 addresses), a provider's infrastructure is also "private" for those packets which do not leave their network. /John

1 0

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

30 Jan '95

------------------------------------------------------------------------------ The PRDB and this "NWG report" will be retired very soon. 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 46318 = 30 5245 38481 2562 Configured Networks 43280 = 30 5188 35564 2498 Added Networks 110 = 0 3 88 19 Deleted Networks 4 = 0 0 4 0 IP address Net name Country Priority:AS ---------- -------- ------- ----------- 137.78/15 JPL-NET2 C:US 1:3561(11) 2:3561(218) 3:1740 144.45/16 TEXAS-DOT C:US 1:1800 2:1240 3:1239 161.209/16 USSCGC01 C:US 1:1740(218) 2:1740(135) 162.71/16 SCHNETWORK C:US 1:114 192.33.129/24 ENERGETIC C:US 1:3561(11) 2:3561(218) 3:200(128) 4:200(144) 192.104.69/24 SHEPARDS C:US 1:1332 192.134.161/24 FR-OMPTPLA C:FR 1:1800 2:1240 3:1133 4:1674 192.134.162/24 FR-OMPTGEO C:FR 1:1800 2:1240 3:1133 4:1674 192.135.181/24 BRYANT2 C:US 1:97 192.239.171/24 FDE-PAN-FL-US C:US 1:3561(218) 2:3561(11) 3:279 4:86 192.239.175/24 FDE-STA-FL-US C:US 1:3561(218) 2:3561(11) 3:279 4:86 192.239.183/24 FDE-STA-FL-US C:US 1:3561(218) 2:3561(11) 3:279 4:86 193.49.157/24 FR-CNES-R1 C:FR 1:1800 2:1240 3:1133 4:1674 193.50.228/24 FR-INSAT4 C:FR 1:1800 2:1240 3:1133 4:1674 193.50.229/24 FR-INSAT5 C:FR 1:1800 2:1240 3:1133 4:1674 193.50.231/24 FR-NY-PLG-E C:FR 1:1800 2:1240 3:1133 4:1674 193.51.171/24 INRA-NUMERIS C:FR 1:1800 2:1240 3:1133 4:1674 193.52.225/24 FR-OMPTAS C:FR 1:1800 2:1240 3:1133 4:1674 193.54.153/24 FR-UP8-INFO C:FR 1:1800 2:1240 3:1133 4:1674 193.96.241/24 CC-DEVNET C:DE 1:701(136) 2:701(134) 3:1800 193.97.251/24 EUNET-DE2 C:DE 1:701(136) 2:701(134) 3:1800 193.162.145/24 LANLINK C:DK 1:1800 2:1879 3:1133 4:1240 193.162.146/24 LANLINK C:DK 1:1800 2:1879 3:1133 4:1240 194.41.63/24 IPROLINK C:CH 1:1800 2:1879 3:1133 4:1240 194.44.14/24 TOPAZ C:UA 1:701(136) 2:701(134) 3:1800 194.57.128/24 FR-DRCNRS C:FR 1:1800 2:1240 3:1133 4:1674 194.58.157/24 RELCOM-NET C:RU 1:701(136) 2:701(134) 3:1800 194.58.212/24 CHCI-NET C:RU 1:701(136) 2:701(134) 3:1800 194.58.213/24 BNOVY-NET C:RU 1:701(136) 2:701(134) 3:1800 198.79.104/24 ARMADILLO-NET C:US 1:3561(218) 2:3561(11) 3:279 4:86 198.139.143/24 SCJOHNSON8 C:US 1:97 198.139.144/24 SCJOHNSON9 C:US 1:97 198.139.145/24 SCJOHNSON10 C:US 1:97 198.139.146/24 SCJOHNSON11 C:US 1:97 198.139.147/24 SCJOHNSON12 C:US 1:97 198.139.148/24 SCJOHNSON13 C:US 1:97 198.139.149/24 SCJOHNSON14 C:US 1:97 198.139.150/24 SCJOHNSON15 C:US 1:97 198.146.160/24 TEN-K12-TN-US-1 C:US 1:3561(218) 2:3561(11) 3:279 4:86 198.146.161/24 TEN-K12-TN-US-1 C:US 1:3561(218) 2:3561(11) 3:279 4:86 198.146.162/24 TEN-K12-TN-US-1 C:US 1:3561(218) 2:3561(11) 3:279 4:86 198.146.163/24 TEN-K12-TN-US-1 C:US 1:3561(218) 2:3561(11) 3:279 4:86 198.146.164/24 TEN-K12-TN-US-1 C:US 1:3561(218) 2:3561(11) 3:279 4:86 198.146.165/24 TEN-K12-TN-US-1 C:US 1:3561(218) 2:3561(11) 3:279 4:86 198.147.162/24 NET-AEA-9 C:US 1:93 198.160.194/24 OASAS C:US 1:1324 198.161.164/24 AB-ISM-CA-C-161-164 C:CA 1:577(143) 2:577(133) 3:577(137) 4:3561(11) 5:3561(218) 198.161.165/24 AB-ISM-CA-C-161-165 C:CA 1:577(143) 2:577(133) 3:577(137) 4:3561(11) 5:3561(218) 198.161.166/24 AB-ISM-CA-C-161-166 C:CA 1:577(143) 2:577(133) 3:577(137) 4:3561(11) 5:3561(218) 198.161.167/24 AB-ISM-CA-C-161-167 C:CA 1:577(143) 2:577(133) 3:577(137) 4:3561(11) 5:3561(218) 198.161.168/24 AB-ISM-CA-C-161-168 C:CA 1:577(143) 2:577(133) 3:577(137) 4:3561(11) 5:3561(218) 198.161.169/24 AB-ISM-CA-C-161-169 C:CA 1:577(143) 2:577(133) 3:577(137) 4:3561(11) 5:3561(218) 198.161.170/24 AB-ISM-CA-C-161-170 C:CA 1:577(143) 2:577(133) 3:577(137) 4:3561(11) 5:3561(218) 198.161.171/24 AB-ISM-CA-C-161-171 C:CA 1:577(143) 2:577(133) 3:577(137) 4:3561(11) 5:3561(218) 198.166.64/18 CA-NS-GOV C:CA 1:1239 2:1800 3:1240 198.166.128/18 CA-NS-GOV C:CA 1:1239 2:1800 3:1240 198.166.192/20 CA-NS-GOV C:CA 1:1239 2:1800 3:1240 198.166.208/21 CA-NS-GOV C:CA 1:1239 2:1800 3:1240 199.38.2/24 NETBLK-ALC-FUJIKURA2 C:US 1:2149 2:174 199.75.164/24 USPRO-FAIRFAX-VA-US C:US 1:3561(218) 2:3561(11) 3:86 4:279 199.75.192/20 HARFORD-CC-MD-US C:US 1:3561(218) 2:3561(11) 3:86 4:279 199.77.76/23 EPC-CO-HILLSBOROUGH-F C:US 1:3561(218) 2:3561(11) 3:279 4:86 199.77.78/24 SEM-COLUMBIA-SC-US C:US 1:3561(218) 2:3561(11) 3:279 4:86 199.89.235/24 MDN-LAF-NET00 C:US 1:701(136) 2:701(134) 199.95.33/24 STPAUL-33 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.95.34/24 STPAUL-34 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.95.35/24 STPAUL-35 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.95.36/24 STPAUL-36 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.95.37/24 STPAUL-37 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.95.38/24 STPAUL-38 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.95.39/24 STPAUL-39 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.95.40/24 STPAUL-40 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.95.41/24 STPAUL-41 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.95.42/24 STPAUL-42 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.95.43/24 STPAUL-43 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.95.44/24 STPAUL-44 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.95.45/24 STPAUL-45 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.95.46/24 STPAUL-46 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.95.47/24 STPAUL-47 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.170.23/24 CONVENE-NET C:US 1:701(136) 2:701(134) 199.203.0/17 NET-ELRON C:US 1:1239 2:1800 3:1240 202.42.154/24 SONY-SG C:SG 1:97 204.19.188/24 CAM-NET C:CA 1:1324 2:2493(35) 3:2493(91) 204.19.189/24 CAM-NET C:CA 1:1324 2:2493(35) 3:2493(91) 204.19.190/24 CAM-NET C:CA 1:1324 2:2493(35) 3:2493(91) 204.19.191/24 CAM-NET C:CA 1:1324 2:2493(35) 3:2493(91) 204.19.238/24 NUKE C:CA 1:1324 2:2493(35) 3:2493(91) 204.19.239/24 NUKE C:CA 1:1324 2:2493(35) 3:2493(91) 204.62.25/24 OKLAOSF2 C:US 1:93 204.71.36/23 NETBLK-MCMASTER C:US 1:3561(11) 2:3561(218) 204.107.242/24 NET-OKLA-HEALTH C:US 1:701(136) 2:701(134) 204.120.206/24 NET-MISHA C:US 1:1239 2:1800 3:1240 204.128.64/18 BREVARD-K12-FL-US C:US 1:3561(218) 2:3561(11) 3:279 4:86 204.154.176/21 EXAR-NETWORK C:US 1:3561(11) 2:3561(218) 3:200(128) 4:200(144) 204.168.124/23 NET-WNET C:US 1:1239 2:1800 3:1240 204.176.6/24 DAVA-NET C:US 1:701(136) 2:701(134) 204.177.120/23 ORKAND C:US 1:701(136) 2:701(134) 204.178.64/21 WORX C:US 1:701(136) 2:701(134) 204.178.184/24 INTELLIMATCH-NET C:US 1:1957 204.179.94/24 DATALAN-NET C:US 1:701(136) 2:701(134) 204.179.95/24 ORITOOLS C:US 1:701(136) 2:701(134) 204.187.76/24 IDR-COM C:CA 1:2493(35) 2:2493(91) 204.188.32/20 NETBLK-RGNET C:US 1:3561(11) 3:3561(218) 4:86 5:279 6:1879 7:3561(136) 204.198.148/24 HOMECOM-COM C:US 1:3561(218) 2:3561(11) 3:279 4:86 204.198.160/19 FCCJ-CC-FL-US C:US 1:3561(218) 2:3561(11) 3:279 4:86 204.198.192/19 FGCU-EDU C:US 1:3561(218) 2:3561(11) 3:279 4:86 204.199.64/20 TALLAHASSEE-CC-FL-US C:US 1:279 2:86 204.214.6/24 NET-ONPROD C:US 1:1239 2:1800 3:1240 204.214.16/21 NET-AEGIS C:US 1:1239 2:1800 3:1240 204.215.1/24 NET-OAKTREEHLTH.COM C:US 1:1800 2:1239 3:1240 Deletions: --204.177.152/24 RIGHT C:US 1:701(136) 2:701(134) --204.177.153/24 CALYX-NET C:US 1:701(136) 2:701(134) --204.177.154/24 CALYX-NET C:US 1:701(136) 2:701(134) --204.177.155/24 CALYX-NET C:US 1:701(136) 2:701(134) 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. ========================================================== The following Midlevel/Regional peering sessions have also been added: AS 1692 - Supercomputing_94 - CNSS 25 Peer: 140.222.24.197 - ANS - cnss29.Chicago.t3.ans.net AS 2885 - NAP-FOUR - ENSS 136 Peer: 192.41.177.166 - Merit - rs1.mfs.mae-east.ra.net AS690 CIDR Squeezings Report: 9940 Nets, 172 ASs, 2708 Aggregates ------------------------------------------------------------------ 9940 (86%) of the ever-announced more-specific routes within aggregates have been withdrawn. 202 of those were withdrawn within the last week. 239 the week before that. 288 the week before that. 172 ASs have registered aggregates in the PRDB. 149 of those are announcing aggregates. 80 have withdrawn at least one more specific route. 2708 Aggregates are configured. 1937 of these were Top-Level Aggregates (not nested in another aggregate). 1472 of these are being announced to AS690. 1035 of those have at least one subnet configured (the other 437 may be saving the Internet future subnet announcements). 856 have stopped announcing at least one configured more specific route. 832 have stopped announcing half of their configured more specific routes. 774 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 January 19, 1994) As of 1/19/95, ACKs and NAKs will no loger be required (or even read) in the processing of NACRs. In early 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)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 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 to the NSFNET policy-based routing database
by smm＠twain.merit.edu 30 Jan '95

30 Jan '95

------------------------------------------------------------------------------ The PRDB and this "NWG report" will be retired very soon. 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 46318 = 30 5245 38481 2562 Configured Networks 43280 = 30 5188 35564 2498 Added Networks 110 = 0 3 88 19 Deleted Networks 4 = 0 0 4 0 IP address Net name Country Priority:AS ---------- -------- ------- ----------- 137.78/15 JPL-NET2 C:US 1:3561(11) 2:3561(218) 3:1740 144.45/16 TEXAS-DOT C:US 1:1800 2:1240 3:1239 161.209/16 USSCGC01 C:US 1:1740(218) 2:1740(135) 162.71/16 SCHNETWORK C:US 1:114 192.33.129/24 ENERGETIC C:US 1:3561(11) 2:3561(218) 3:200(128) 4:200(144) 192.104.69/24 SHEPARDS C:US 1:1332 192.134.161/24 FR-OMPTPLA C:FR 1:1800 2:1240 3:1133 4:1674 192.134.162/24 FR-OMPTGEO C:FR 1:1800 2:1240 3:1133 4:1674 192.135.181/24 BRYANT2 C:US 1:97 192.239.171/24 FDE-PAN-FL-US C:US 1:3561(218) 2:3561(11) 3:279 4:86 192.239.175/24 FDE-STA-FL-US C:US 1:3561(218) 2:3561(11) 3:279 4:86 192.239.183/24 FDE-STA-FL-US C:US 1:3561(218) 2:3561(11) 3:279 4:86 193.49.157/24 FR-CNES-R1 C:FR 1:1800 2:1240 3:1133 4:1674 193.50.228/24 FR-INSAT4 C:FR 1:1800 2:1240 3:1133 4:1674 193.50.229/24 FR-INSAT5 C:FR 1:1800 2:1240 3:1133 4:1674 193.50.231/24 FR-NY-PLG-E C:FR 1:1800 2:1240 3:1133 4:1674 193.51.171/24 INRA-NUMERIS C:FR 1:1800 2:1240 3:1133 4:1674 193.52.225/24 FR-OMPTAS C:FR 1:1800 2:1240 3:1133 4:1674 193.54.153/24 FR-UP8-INFO C:FR 1:1800 2:1240 3:1133 4:1674 193.96.241/24 CC-DEVNET C:DE 1:701(136) 2:701(134) 3:1800 193.97.251/24 EUNET-DE2 C:DE 1:701(136) 2:701(134) 3:1800 193.162.145/24 LANLINK C:DK 1:1800 2:1879 3:1133 4:1240 193.162.146/24 LANLINK C:DK 1:1800 2:1879 3:1133 4:1240 194.41.63/24 IPROLINK C:CH 1:1800 2:1879 3:1133 4:1240 194.44.14/24 TOPAZ C:UA 1:701(136) 2:701(134) 3:1800 194.57.128/24 FR-DRCNRS C:FR 1:1800 2:1240 3:1133 4:1674 194.58.157/24 RELCOM-NET C:RU 1:701(136) 2:701(134) 3:1800 194.58.212/24 CHCI-NET C:RU 1:701(136) 2:701(134) 3:1800 194.58.213/24 BNOVY-NET C:RU 1:701(136) 2:701(134) 3:1800 198.79.104/24 ARMADILLO-NET C:US 1:3561(218) 2:3561(11) 3:279 4:86 198.139.143/24 SCJOHNSON8 C:US 1:97 198.139.144/24 SCJOHNSON9 C:US 1:97 198.139.145/24 SCJOHNSON10 C:US 1:97 198.139.146/24 SCJOHNSON11 C:US 1:97 198.139.147/24 SCJOHNSON12 C:US 1:97 198.139.148/24 SCJOHNSON13 C:US 1:97 198.139.149/24 SCJOHNSON14 C:US 1:97 198.139.150/24 SCJOHNSON15 C:US 1:97 198.146.160/24 TEN-K12-TN-US-1 C:US 1:3561(218) 2:3561(11) 3:279 4:86 198.146.161/24 TEN-K12-TN-US-1 C:US 1:3561(218) 2:3561(11) 3:279 4:86 198.146.162/24 TEN-K12-TN-US-1 C:US 1:3561(218) 2:3561(11) 3:279 4:86 198.146.163/24 TEN-K12-TN-US-1 C:US 1:3561(218) 2:3561(11) 3:279 4:86 198.146.164/24 TEN-K12-TN-US-1 C:US 1:3561(218) 2:3561(11) 3:279 4:86 198.146.165/24 TEN-K12-TN-US-1 C:US 1:3561(218) 2:3561(11) 3:279 4:86 198.147.162/24 NET-AEA-9 C:US 1:93 198.160.194/24 OASAS C:US 1:1324 198.161.164/24 AB-ISM-CA-C-161-164 C:CA 1:577(143) 2:577(133) 3:577(137) 4:3561(11) 5:3561(218) 198.161.165/24 AB-ISM-CA-C-161-165 C:CA 1:577(143) 2:577(133) 3:577(137) 4:3561(11) 5:3561(218) 198.161.166/24 AB-ISM-CA-C-161-166 C:CA 1:577(143) 2:577(133) 3:577(137) 4:3561(11) 5:3561(218) 198.161.167/24 AB-ISM-CA-C-161-167 C:CA 1:577(143) 2:577(133) 3:577(137) 4:3561(11) 5:3561(218) 198.161.168/24 AB-ISM-CA-C-161-168 C:CA 1:577(143) 2:577(133) 3:577(137) 4:3561(11) 5:3561(218) 198.161.169/24 AB-ISM-CA-C-161-169 C:CA 1:577(143) 2:577(133) 3:577(137) 4:3561(11) 5:3561(218) 198.161.170/24 AB-ISM-CA-C-161-170 C:CA 1:577(143) 2:577(133) 3:577(137) 4:3561(11) 5:3561(218) 198.161.171/24 AB-ISM-CA-C-161-171 C:CA 1:577(143) 2:577(133) 3:577(137) 4:3561(11) 5:3561(218) 198.166.64/18 CA-NS-GOV C:CA 1:1239 2:1800 3:1240 198.166.128/18 CA-NS-GOV C:CA 1:1239 2:1800 3:1240 198.166.192/20 CA-NS-GOV C:CA 1:1239 2:1800 3:1240 198.166.208/21 CA-NS-GOV C:CA 1:1239 2:1800 3:1240 199.38.2/24 NETBLK-ALC-FUJIKURA2 C:US 1:2149 2:174 199.75.164/24 USPRO-FAIRFAX-VA-US C:US 1:3561(218) 2:3561(11) 3:86 4:279 199.75.192/20 HARFORD-CC-MD-US C:US 1:3561(218) 2:3561(11) 3:86 4:279 199.77.76/23 EPC-CO-HILLSBOROUGH-F C:US 1:3561(218) 2:3561(11) 3:279 4:86 199.77.78/24 SEM-COLUMBIA-SC-US C:US 1:3561(218) 2:3561(11) 3:279 4:86 199.89.235/24 MDN-LAF-NET00 C:US 1:701(136) 2:701(134) 199.95.33/24 STPAUL-33 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.95.34/24 STPAUL-34 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.95.35/24 STPAUL-35 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.95.36/24 STPAUL-36 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.95.37/24 STPAUL-37 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.95.38/24 STPAUL-38 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.95.39/24 STPAUL-39 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.95.40/24 STPAUL-40 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.95.41/24 STPAUL-41 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.95.42/24 STPAUL-42 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.95.43/24 STPAUL-43 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.95.44/24 STPAUL-44 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.95.45/24 STPAUL-45 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.95.46/24 STPAUL-46 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.95.47/24 STPAUL-47 C:US 1:3561(218) 2:3561(11) 3:560 4:701(136) 5:701(134) 199.170.23/24 CONVENE-NET C:US 1:701(136) 2:701(134) 199.203.0/17 NET-ELRON C:US 1:1239 2:1800 3:1240 202.42.154/24 SONY-SG C:SG 1:97 204.19.188/24 CAM-NET C:CA 1:1324 2:2493(35) 3:2493(91) 204.19.189/24 CAM-NET C:CA 1:1324 2:2493(35) 3:2493(91) 204.19.190/24 CAM-NET C:CA 1:1324 2:2493(35) 3:2493(91) 204.19.191/24 CAM-NET C:CA 1:1324 2:2493(35) 3:2493(91) 204.19.238/24 NUKE C:CA 1:1324 2:2493(35) 3:2493(91) 204.19.239/24 NUKE C:CA 1:1324 2:2493(35) 3:2493(91) 204.62.25/24 OKLAOSF2 C:US 1:93 204.71.36/23 NETBLK-MCMASTER C:US 1:3561(11) 2:3561(218) 204.107.242/24 NET-OKLA-HEALTH C:US 1:701(136) 2:701(134) 204.120.206/24 NET-MISHA C:US 1:1239 2:1800 3:1240 204.128.64/18 BREVARD-K12-FL-US C:US 1:3561(218) 2:3561(11) 3:279 4:86 204.154.176/21 EXAR-NETWORK C:US 1:3561(11) 2:3561(218) 3:200(128) 4:200(144) 204.168.124/23 NET-WNET C:US 1:1239 2:1800 3:1240 204.176.6/24 DAVA-NET C:US 1:701(136) 2:701(134) 204.177.120/23 ORKAND C:US 1:701(136) 2:701(134) 204.178.64/21 WORX C:US 1:701(136) 2:701(134) 204.178.184/24 INTELLIMATCH-NET C:US 1:1957 204.179.94/24 DATALAN-NET C:US 1:701(136) 2:701(134) 204.179.95/24 ORITOOLS C:US 1:701(136) 2:701(134) 204.187.76/24 IDR-COM C:CA 1:2493(35) 2:2493(91) 204.188.32/20 NETBLK-RGNET C:US 1:3561(11) 3:3561(218) 4:86 5:279 6:1879 7:3561(136) 204.198.148/24 HOMECOM-COM C:US 1:3561(218) 2:3561(11) 3:279 4:86 204.198.160/19 FCCJ-CC-FL-US C:US 1:3561(218) 2:3561(11) 3:279 4:86 204.198.192/19 FGCU-EDU C:US 1:3561(218) 2:3561(11) 3:279 4:86 204.199.64/20 TALLAHASSEE-CC-FL-US C:US 1:279 2:86 204.214.6/24 NET-ONPROD C:US 1:1239 2:1800 3:1240 204.214.16/21 NET-AEGIS C:US 1:1239 2:1800 3:1240 204.215.1/24 NET-OAKTREEHLTH.COM C:US 1:1800 2:1239 3:1240 Deletions: --204.177.152/24 RIGHT C:US 1:701(136) 2:701(134) --204.177.153/24 CALYX-NET C:US 1:701(136) 2:701(134) --204.177.154/24 CALYX-NET C:US 1:701(136) 2:701(134) --204.177.155/24 CALYX-NET C:US 1:701(136) 2:701(134) 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. ========================================================== The following Midlevel/Regional peering sessions have also been added: AS 1692 - Supercomputing_94 - CNSS 25 Peer: 140.222.24.197 - ANS - cnss29.Chicago.t3.ans.net AS 2885 - NAP-FOUR - ENSS 136 Peer: 192.41.177.166 - Merit - rs1.mfs.mae-east.ra.net AS690 CIDR Squeezings Report: 9940 Nets, 172 ASs, 2708 Aggregates ------------------------------------------------------------------ 9940 (86%) of the ever-announced more-specific routes within aggregates have been withdrawn. 202 of those were withdrawn within the last week. 239 the week before that. 288 the week before that. 172 ASs have registered aggregates in the PRDB. 149 of those are announcing aggregates. 80 have withdrawn at least one more specific route. 2708 Aggregates are configured. 1937 of these were Top-Level Aggregates (not nested in another aggregate). 1472 of these are being announced to AS690. 1035 of those have at least one subnet configured (the other 437 may be saving the Internet future subnet announcements). 856 have stopped announcing at least one configured more specific route. 832 have stopped announcing half of their configured more specific routes. 774 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 January 19, 1994) As of 1/19/95, ACKs and NAKs will no loger be required (or even read) in the processing of NACRs. In early 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)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 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

CIDR/Aggregation/Allocation Policies
by Sean Doran 29 Jan '95

29 Jan '95

Does anyone know if anybody from Network Solutions is going to be at NANOG? The CIDR/Aggregation talk looks like it's going to focus a bunch of thought at allocation policies and strategies. (drc, are you going to be there? :) ) Aslo, after a talk with Yakov Rekhter yesterday, I think we certainly can use two hours for the CIDR/Aggregation talk instead of just one (they don't have to be contiguous, and maybe a break between each hour could be useful). Sean.

4 3