- Test - lists.nanog.org

Re: ARIN allocating /20 netblocks?
by owen＠DeLong.SJ.CA.US 17 May '98

17 May '98

> > Ok, so I only lose 16 T1 customers instead of 1024. > > If you lose 16 T1 customers during a renumbering of a /20, either you > don't know how to renumber, or they were already unhappy for some > other reason. > > If you tell your customers "You need to renumber because evil forces > are colluding against us," they won't be very amenable... try > explaining that they'll get better connectivity. > > The social and technical problems of renumbering a /20 are nonzero but > not large. > > I've done it. > -- > Shields, CrossLink. > Not always. I know of at least one case where a customer cannot (will not) renumber out of a /24 because they (without commenting on the intellectual prowess of this particular act) shipped a million CD's with the .128 IP address in that class C hard coded into their game. Sure, it's only one IP, one machine to renumber, but... Owen

1 0

Re: Spring (not t) 1998 NOC Contact Test Results
by Sean Donelan 17 May '98

17 May '98

Ignore the typo in the subject line. -- Sean Donelan, Data Research Associates, Inc, St. Louis, MO Affiliation given for identification not representation

2 1

Re: secure router access
by Tony Li 16 May '98

16 May '98

stevesk(a)sweden.hp.com (Kevin Steves) writes: > > SSH is officially on the Cisco "project list" AFAIK; I believe someone > > just has to take the project and actually /do/ it. > > There was a post recently to the SSH mailing list that stated that as > well; see http://www.cs.hut.fi/ssh-archive/messages/980515-083235-3456. ssh was on the Cisco wish list two years ago. Tony

1 0

Re: Wired Q: Embedded NT
by Lehrer, Neil 16 May '98

16 May '98

i saw something about a switch maker embedding nt. about layer 4 switches understanding application level info. it was recent, maybe network world, but i can't be sure. ``````` To: nanog(a)merit.edu From: James Glave <james(a)wired.com> Hi all, James Glave at Wired News again. This time around I am seeking opinions on behalf of a friend up at Wired (the print magazine) -- concerning embedded NT. I couldn't find any discussion in the nanog archive, so I'm wondering if anoyne here has any experience with, or knowledge of, embedding NT in networking hardware - if that even makes any sense....? >From: Jesse Freund <freund(a)wired.com> >i'm working on a piece about nt-embedded and i have a couple of questions. >i'm hoping you might be able to hook me up with a smart network operator or >someone else in the know or perhaps you know. basically, i'm curious why >the hell someone would want a version of nt embedded in a switch or router? >and who provides the custom solutions nt-embedded is meant to replace? Thanks, all! jtg James Glave, Senior Technology Writer Wired News http://www.wired.com (415) 276-8430 Unstoppable Force of the Week: "Gettin' jiggy wit' it!" Regards +++++++++++++++++++++++++++++++++++++++ + Neil Lehrer + U.S. Information Agency + Networks and Systems Support Division + + voice 202 619-0903 + fax 202 619-3883 + internet nlehrer(a)usia.gov + + "oh what a tangled net we weave + when we seek to retrieve." + +++++++++++++++++++++++++++++++++++++++

2 1

Re: Zone file access
by Manar Hussain 16 May '98

16 May '98

At 15:24 15/05/98 -0700, Ben Kirkpatrick wrote: > I believe this is why they cut off public access. The NIC was >flooded with requests for domains that had just been deleted. >People were hoping to make a buck. If you have a _legitimate_ need >for zone file access, you will get it. I certainly had no problem >after the NIC figured out their internal policy for granting access. Hmm: (a) *If* this is considered undesirable - draw up a charter and say so to avoid anyone from using it for these purposes (why should someone else be allowed to do this because they claimed/had a "legitimate" reasons "as well"). (b) We don't intend to register for ourselves any domains that we don't want to use, though I admit that we have considered having some form of public interface to the info that may allow people to look through the list of recently de-activated domains and then register them. But even if we were interested in registering lots of recently de-activated domains - what's the problem with this - they are available and moreover they are domains that people have let the payments on drop. At least we'd be intending to pay for these domain (I know someone with "legitimate" access to the info who uses it to notice when domains eh never had any intention of paying for drop out of DNS so that he can look to re-register it - I should say that this is an induhvidual and that the "company" may have not idea about this). (c) At least part of our interest was purely statistical - we thought it useful to have a stateful track of things so we could do stats on it (and if it was useful make it publically available). I'll re-phrase myself a little - there are several things I'd like to do and I object to not being able to do any one of those when others are perfectly at liberty to do so. I'm reasonably happy to be told that nobody can do x,y or z as long as it's reasonably fairly imposed/upheld etc. Manar >--Ben Kirkpatrick, ELI Data Products Enginneering > > >On Fri, 15 May 1998, Manar Hussain wrote: >)We want to use it to create an in house db of domains so we can track which >)domains are being released and do some stats stuff on it as well as do some >)degree of local domain querying without having to rely on internic's ropey >)whois) ... no desire to farm email addresses or anything. > > >

1 0

Re: 1.1.1.0/24
by Sean Donelan 16 May '98

16 May '98

>One item that is currently before the ARIN Advisory Council is a >suggestion that we publish a map of all currently allocated IP space and >keep that map up to date. If we do this then I think it solves this >problem if people keep verifying their filters against the map or if they >generate their filters based on the map. You mean like ftp://ftp.isi.edu/in-notes/iana/assignments/ipv4-address-space ???? One which may be usefull is registering the 'unassigned' IANA blocks in the IRR with a special AS number (e.g. AS0 or AS65535) so people can use the RtConfig tools to create filters by exception (e.g. NOT AS0) But there is already so much junk like 0.0.0.0/1 in there already, I hesitate doing it. -- Sean Donelan, Data Research Associates, Inc, St. Louis, MO Affiliation given for identification not representation

4 3

Sprint 1998 NOC Contact Test Results
by Sean Donelan 16 May '98

16 May '98

The Spring 1998 NOC contact test is over. Here are the results. 69 U.S. network contacts 'worked,' with an extremely liberal definition of worked 2 infrastructure (RSNG, InterNIC) contacts 'worked,' with an extremely liberal definition of worked 11 e-mail addresses changed 28 phone numbers changed 4 phone numbers disconnected, not in service, no answer or busy for 5 days 2 automated call system timeout 3 contacts unable or unwilling to confirm contact information 1 (maybe more) contact information missing from my records http://dranet.dra.com/verify-contact.html corrections may be sent to sean(a)dra.com -- Sean Donelan, Data Research Associates, Inc, St. Louis, MO Affiliation given for identification not representation

1 0

Re: Zone file access
by Paul Vixie 15 May '98

15 May '98

> > Dear Customer, > > > > Thank you for contacting Network Solutions, Inc., InterNIC > > Registration Services. > > > > We cannot give you access to our database for all records, other than > > what is in our whois database, is confidential and not available to the > > public. > > > > Best Regards, > > II > > Network Solutions, Inc. Network Solutions has never actually asked me to stop allowing full outbound zone transfers of all InterNIC TLD's from F.ROOT-SERVERS.NET. According to my logs, "dig @192.5.5.241 xxx axfr > xxx.zone" is a rather popular command: [dns1.pa:alpha] wc -l xfer.log* 1702 xfer.log 306 xfer.log.0 5560 xfer.log.1 3219 xfer.log.2 16859 xfer.log.3 12066 xfer.log.4 39712 total [dns1.pa:alpha] ls -l xfer.log* -rw-r--r-- 1 root system 162968 May 15 00:22 xfer.log -rw-r--r-- 1 root system 29856 May 7 17:00 xfer.log.0 -rw-r--r-- 1 root system 546016 May 6 22:01 xfer.log.1 -rw-r--r-- 1 root system 325942 Apr 15 21:05 xfer.log.2 -rw-r--r-- 1 root system 1724302 Apr 6 19:08 xfer.log.3 -rw-r--r-- 1 root system 1194194 Feb 28 11:35 xfer.log.4 If NSI should ask me to restrict outbound zone transfers, then I would of course immediately ask the IANA whether to comply with that request. And so now you all know why BIND-8's first development priority was to stop forking for outbound zone transfers -- I can export the COM zone 50 times in parallel (and I sometimes do) without changing the runtime profile of F.ROOT-SERVERS.NET. -- Paul Vixie La Honda, CA <paul(a)vix.com> "Many NANOG members have been around pacbell!vixie!paul longer than most." --Jim Fleming

5 4

Bork Bork Bork?
by Jeremy Johnson 15 May '98

15 May '98

So Tony Bates sends out the CIDR report as usual...222.222.222.0 possibly a bogus route...so I check out RADB...BORK BORK BORK...huh? route: 192.0.0.0/2 descr: QUARTER-DEFAULT-ONE descr: The Reasonable Default Route Project descr: This prefix is one of three which is designed descr: to accomplish several things. Firstly, ICM descr: will be offering a set of robust and hardened descr: default-oriented prefixes which will be made descr: reliably available to some of AS1800's peers and descr: things downstream from them. The routing announcements descr: will be supplemented with a box that sends back descr: appropriate ICMP messages; at some point we will descr: also make a view of the default-announcing box's descr: knowledge of global routing available to folks descr: who wish to accept the default announcement. descr: Secondly, this announcement is designed to assist descr: ANS in the transition away from advisories. We expect descr: that this will allow people to send in far fewer descr: advisory updates than is done currently, without descr: breaking reachability between ANS's customers and descr: the rest of the world. This is good for both ANS descr: and everyone else. descr: BORK BORK BORK FREE THE INTERNET BORK BORK BORK descr: Thirdly, ICM will be running some experiments on descr: sheer amount of traffic that follows an ultimate descr: default, although this must be done without descr: examining that traffic for content without explicit descr: permission from the originator. We expect that this descr: will help serve as a tool to identify and correct descr: problems in the global routing system. descr: questions, comments and flames to: smd(a)sprint.net, roll(a)stupi.se origin: AS1800 advisory: AS690 1:1800 2:1239 mnt-by: MAINT-AS1800 changed: frank.rizzo(a)sprint.net 980508 source: RADB -JERM

1 0

The Cidr Report
by Tony Bates 15 May '98

15 May '98

This is an auto-generated mail on Fri May 15 12:00:00 PDT 1998 It is not checked before it leaves my workstation. However, hopefully you will find this report interesting and will take the time to look through this to see if you can improve the amount of aggregation you perform. The report is split into sections: 0) General Status List the route table history for the last week, list any possibly bogus routes seen and give some status on ASes. 1) Gains by aggregating at the origin AS level This lists the "Top 30" players who if they decided to aggregate their announced classful prefixes at the origin AS level could make a significant difference in the reduction of the current size of the Internet routing table. This calculation does not take into account the inclusion of holes when forming an aggregate so it is possible even larger reduction should be possible. 2) Weekly Delta A summary of the last weeks changes in terms of withdrawn and added routes. Please note that this is only a snapshot but does give some indication of ASes participating in CIDR. Clearly, it is generally a good thing to see a large amont of withdrawls. 3) Interesting aggregates Interesting here means not an aggregate made as a set of classful routes. Thanks to xara.net for giving me access to their routing tables once a day. Please send any comments about this report directly to me. Check http://www.employees.org/~tbates/cidr-report.html for a daily update of this report. ------------------------------------------------------------------------------ CIDR REPORT for 15May98 0) General Status Table History ------------- Date Prefixes 080598 51559 090598 51630 100598 51503 110598 51419 120598 52655 130598 51474 140598 51492 150598 51370 Check http://www.employees.org/~tbates/cidr.plot.html for a plot of the table history. Possible Bogus Routes --------------------- *** Bogus 222.222.222.0 from AS701 AS Summary ---------- Number of ASes in routing system: 3564 Number of ASes announcing only one prefix: 1698 (890 cidr, 808 classful) Largest number of cidr routes: 367 announced by AS3561 Largest number of classful routes: 1069 announced by AS701 1) Gains by aggregating at the origin AS level --- 15May98 --- ASnum NetsNow NetsCIDR NetGain % Gain Description AS4293 464 239 225 48.5% IMCI AS816 697 474 223 32.0% UUNET Canada (ASN-UUNETCA-AS4) AS2493 535 315 220 41.1% iSTAR Internet, Inc. AS174 819 626 193 23.6% Performance Systems International AS3602 484 307 177 36.6% Sprint Canada Inc. AS701 1069 896 173 16.2% Alternet AS3749 219 64 155 70.8% TECNET AS2048 162 90 72 44.4% LaNet AS5668 115 46 69 60.0% Century Telephone Inc. AS3221 110 41 69 62.7% EENet Autonomous System AS3248 128 60 68 53.1% VIAnet AS4755 95 28 67 70.5% Videsh Sanchar Nigam Ltd. India AS10928 107 44 63 58.9% UNKNOWN AS7046 194 135 59 30.4% UUNET-CUSTOMER AS271 112 53 59 52.7% BCnet Backbone AS3804 200 142 58 29.0% Bell Solutions AS549 208 154 54 26.0% ONet Backbone AS1221 276 225 51 18.5% AARNET-AS AS72 85 37 48 56.5% Schlumberger Information Network AS1239 538 491 47 8.7% SprintLink Backbone AS4763 121 75 46 38.0% Telstra New Zealand AS4740 382 336 46 12.0% ASN-OZEMAIL (Ozemail Pty Ltd) AS7545 105 60 45 42.9% TPG Internet Pty Ltd AS852 157 117 40 25.5% AGT Advance Communication AS6335 64 24 40 62.5% NTRNET AS684 93 54 39 41.9% Manitoba Regional Network Backbon AS4200 127 88 39 30.7% AGIS (Apex Global Information Ser AS1982 154 115 39 25.3% Northwest Nexus, Inc. AS762 118 80 38 32.2% WELLFLEET-AS AS3493 164 126 38 23.2% INTERLINK For the rest of the previous weeks gain information please see http://www.employees.org:80/~tbates/cidr-report.html 2) Weekly Delta Please see http://www.employees.org:80/~tbates/cidr-report.html for this part of the report 3) Interesting aggregates Please see http://www.employees.org:80/~tbates/cidr-report.html for this part of the report

1 0