- NANOG - lists.nanog.org

Re: New AS block allocated to the RIPE NCC
by Michael.Dillon＠radianz.com 02 Oct '03

02 Oct '03

>>The RIPE NCC received the AS Number block 30720 - 3174 >>from the IANA in September 2003. >I made a typo in my last message. The AS block is in fact 30720 - 31740. A good example of why we need to stop announcing these allocations by ad-hoc email techniques and force IANA to operate an authoritative whois directory that identifies the current status of all AS number blocks and the entire IPv4 and IPv6 address spaces. Whether this is done with LDAP or DNS hacks or a simple machine parseable CSV file via HTTP is irrelevant. The fact is that we need a definitive and authoritative and machine-parseable source for this information. --Michael Dillon

1 0

offlist: lucent springtide & hitachi an-1000 experience(s)
by Peter Galbavy 02 Oct '03

02 Oct '03

Can anyone who is knowledgeable and possibly willing to help with these devices please contact me off list ? A colleague acquired a small number in a dot.com sale and they sounds really cute / useful, but before even playing with them I would love to here from anyone with wanrings / tips / etc. Especially the BGP side (if these have that license - not checked yet). Peter

1 0

ICANN's SECSAC meeting on Verisign's Site Finder Service
by Russ Haynal 02 Oct '03

02 Oct '03

Just passing this along - some of you may want to attend to voice your opinion. - Russ >From: DCISOC <info(a)dcisoc.org> >Subject: DCISOC: SECSAC meeting on Verisign's Site Finder Service >This meeting, on one of the hottest Internet topics, will be held in >downtown D.C. next Tuesday. You're invited. > > >Special Meeting of ICANN's Security and Stability Advisory Committee >Regarding VeriSign's Deployment of Wildcard > >Marina del Rey, CA - 30 September 2003 - ICANN's Security and Stability >Advisory Committee (SECSAC) announced today that it will hold a special >meeting on 7 October 2003 to gather input regarding VeriSign's recent >change to the operation of the registry for the .com and .net Top Level >Domains. > >SECSAC is an ICANN advisory committee comprised of Internet pioneers and >technical experts including operators of Internet root servers, registrars, >and TLD registries. > >On 15 September 2003, VeriSign introduced a "wildcard" into the .com and >.net zones. The VeriSign wildcard redirects traffic that would otherwise >have resulted in a "no domain" response to a VeriSign-operated website with >search results and links to paid advertisements. > >Since the introduction of the wildcard, the Internet Architecture Board >(IAB), SECSAC and other groups have issued separate statements expressing >concerns over this change to the operation of the Internet's core >infrastructure and its impact on the stability of the Internet. > >Following this special meeting, SECSAC will issue a report intended to be >of use to ICANN, to the technical community, and to the community at large >who seek to understand the issues at hand and how the critical parts of the >Internet interact with each other. > >The meeting will be held on Tuesday, 7 October 2003, from 10 AM to 4 PM at: > >The Center for Strategic and International Studies ><www.csis.org> >1800 K Street NW >Washington, DC 20006 > >The meeting is free and open to the public. Please pre-register at ><http://register.icann.org>. >ICANN also plans to webcast the meeting live. >Further details including an agenda, background materials and webcast >arrangements are available at <http://secsac.icann.org>. > >In preparation for the meeting, ICANN and its SECSAC have issued a public >request for comments and reports to <secsac-comment(a)icann.org> relating to >the effects of the .com and .net wildcards. > >Additional information regarding SECSAC is available at ><http://www.icann.org/committees/security/>. >An information page on the .com and .net wildcards has been posted at ><http://www.icann.org/general/wildcard-history.htm>. _________________________________________________________________ Russ Haynal - Internet Instructor, Speaker and Paradigm Shaker "Helping organizations gain the most benefit from the Internet" russ(a)navigators.com http://navigators.com 703-729-1757

1 0

Need contact for ChoiceOne
by Robert Blayzor 01 Oct '03

01 Oct '03

Can someone with a clue in ChoiceOnes IP operations contact me off list please. -- Robert Blayzor, BOFH INOC, LLC rblayzor(a)inoc.net PGP: http://www.inoc.net/~dev/ Key fingerprint = A445 7D1E 3D4F A4EF 6875 21BB 1BAA 10FE 5748 CFE9 Quality assurance: A way to ensure you never deliver shoddy goods accidentally.

1 0

From Sprint's status page
by Nick Guy 01 Oct '03

01 Oct '03

.**************************************************************** .---------------------------------------------------------------- | Type: Outage | Purpose: Routing Issues | Network: SL | Ticket: 6505769 | Sprint Id: 16881 | .---------------------------------------------------------------- .**************************************************************** Sprint is currently experiencing an outage in Seattle, WA Tacoma, WA and Tokyo, Japan. Sprint is committed to providing an exceptional customer experience based on a portfolio of reliable products and services. Because we realize how important your network solution is to your business, Sprint makes every attempt to avoid interruptions to the quality service provided. While we attempt to limit our service interruptions to occur during scheduled maintenance windows, occasionally we experience an outage such as this which may impact your service outside of our maintenance window. We will attempt to minimize the impact to your service and strive to maintain our network to our high quality standards and to continually serve you, our valued customer. All of us at Sprint appreciate the opportunity to provide a network solution that meets your telecommunications needs. Your private line(s) impacted by this outage and/or router(s) associated with your service are listed below. Demand maintenance is underway to restore service from the outage caused by fiber outage. Customers whose only connection to the Sprintlink IP network is via this gateway router will experience loss of Internet connectivity for the duration of the emergency maintenance. Expected time to repair is Unknown. Please bear with us as we work to fix the problem. Thank you for your patronage. ----------------------------------------------- ---------------------------------------------------------------------- Tacoma, WA ROUTERS INVOLVED IN OUTAGE SL-GW10-TAC SL-GW1-TAC SL-GW9-TAC SL-GW5-TAC SL-GW5-TAC SL-GW11-TAC SL-GW3-TAC SL-GW8-TAC SL-GW6-TAC SL-GW6-TAC SL-GW4-TAC SL-GW12-TAC SL-GW2-TAC START TIME (local): 14:40 PDT 01-OCT-2003 START TIME (gmt ): 21:40 GMT 01-OCT-2003 ---------------------------------------------------------------------- ---------------------------------------------------------------------- Seattle, WA ROUTERS INVOLVED IN OUTAGE SL-GW1-SEA SL-GW15-SEA SL-GW8-SEA SL-GW3-SEA SL-GW3-SEA SL-GW13-SEA SL-GW6-SEA SL-GW10-SEA SL-GW4-SEA SL-GW4-SEA SL-GW9-SEA SL-GW11-SEA SL-GW5-SEA SL-GW7-SEA SL-GW7-SEA SL-GW14-SEA SL-GW2-SEA START TIME (local): 14:40 PDT 01-OCT-2003 START TIME (gmt ): 21:40 GMT 01-OCT-2003 ---------------------------------------------------------------------- ---------------------------------------------------------------------- Tokyo, Japan ROUTERS INVOLVED IN OUTAGE SL-GW21-TOK SL-GW20-TOK SL-GW10-TOK SL-GW1-TOK SL-GW1-TOK START TIME (local): 14:40 JST 01-OCT-2003 START TIME (gmt ): 05:40 GMT 01-OCT-2003 ---------------------------------------------------------------------- ___________________________________________ Nick Guy ---- Manager of Network Operations Semaphore Corporation 2001 6th Ave Suite 1700 , Seattle, WA 98121 nickguy(a)semaphore.com 206-905-5023 | 24/7 NOC: - 206-905-6000 ___________________________________________

1 0

Massive sprintlink problems?
by Michael Loftis 01 Oct '03

01 Oct '03

Anyone else seeing this:: (1sec+ delay to my idle DSL line across sprintlink...) traceroute is definitely taking an asymmetric path, since pings and tcp connections are consistent 1sec plus RTT starting somewhere in seattle or tacoma.....tok? tokyo? Anyway before I start rattling this around I wanted to see if anyone else is seeing this to/from other destinations. root@crazyhorse:~# traceroute shell.wgops.com traceroute to shell.wgops.com (66.92.192.108), 30 hops max, 38 byte packets 1 r1 (216.129.251.1) 0.196 ms 0.230 ms 0.257 ms 2 ag125.montanavision.com (216.220.20.125) 0.447 ms 0.300 ms 0.351 ms 3 ag102.montanavision.com (216.220.20.102) 8.643 ms 13.078 ms 8.646 ms 4 sl-gw10-che-2-0-TS1.sprintlink.net (144.223.8.57) 19.749 ms 17.973 ms 19.443 ms 5 sl-bb20-che-3-0.sprintlink.net (144.232.15.145) 19.545 ms 19.301 ms 19.513 ms 6 sl-bb23-chi-6-0.sprintlink.net (144.232.19.194) 37.906 ms 37.168 ms 37.574 ms 7 sl-bb24-chi-15-0.sprintlink.net (144.232.26.101) 36.751 ms 35.515 ms 35.890 ms 8 sl-bb21-sj-8-0.sprintlink.net (144.232.20.161) 153.128 ms 133.215 ms 272.201 ms 9 sl-bb22-sj-15-0.sprintlink.net (144.232.3.162) 84.783 ms 83.089 ms 83.520 ms 10 sl-bb20-tok-10-0.sprintlink.net (144.232.9.243) 207.685 ms 208.017 ms 209.261 ms 11 sl-bb21-tac-8-2.sprintlink.net (144.232.19.243) 449.450 ms 446.199 ms 447.872 ms 12 sl-bb22-tac-15-0.sprintlink.net (144.232.17.94) 463.037 ms 1243.175 ms 444.169 ms 13 sl-bb20-sea-0-0.sprintlink.net (144.232.9.150) 1300.127 ms 1245.757 ms 1247.772 ms 14 sl-gw11-sea-7-0.sprintlink.net (144.232.6.126) 1247.891 ms 1246.780 ms 1245.041 ms 15 sl-internap-89-0.sprintlink.net (144.228.94.118) 198.635 ms 196.617 ms 196.579 ms 16 border26s.ge2-1-bbnet2.sea.pnap.net (206.253.192.227) 196.374 ms 196.691 ms 196.872 ms 17 * * ge0-0-0.brd-1-sea.speakeasy.net (206.191.168.200) 206.800 ms 18 fe2-0.spk-2-sea.speakeasy.net (206.191.168.196) 198.894 ms 197.410 ms 197.248 ms 19 kurak.wgops.com (66.92.192.248) 228.267 ms 225.835 ms 226.328 ms 20 shell.wgops.com (66.92.192.108) 226.949 ms 223.640 ms 224.977 ms -- GPG/PGP --> 0xE736BD7E 5144 6A2D 977A 6651 DFBE 1462 E351 88B9 E736 BD7E

3 4

Pre/During NANOG Social Events!?
by Malayter, Christopher 01 Oct '03

01 Oct '03

Hello All, Lacking Ren and MDR for planning this NANOG, Ren asked myself and David Koch to hook up some unofficial events. We have a few ideas and are wondering if anyone would be interested in the following dates/times. Once we get a feel of when people are interested in doing things, we'll post some ideas and go from there. Please respond back to me off-list. Satuday October 18th. Night Sunday October 19th. After the sessions Thanks! Chris Malayter TDS Telecom - Network Services Advanced Data Network Support chris.malayter(a)tdstelecom.com

1 0

Re: ICMP Blocking Woes
by Kevin Oberman 01 Oct '03

01 Oct '03

> Date: Tue, 30 Sep 2003 19:36:23 -0500 > From: John Kristoff <jtk(a)depaul.edu> > Sender: owner-nanog(a)merit.edu > > > On Tue, Sep 30, 2003 at 05:22:25PM -0700, Crist Clark wrote: > > > Wasn't this based upon the premise that gear should not return ICMP > > > errors as a result of ICMP packet input as a precaution against error > > > loops? ie said dodgy router did the _right_ thing? > > > That would be disingenious. RFC1122 clearly lists which ICMP are error > > messages, > > The following from W. Richard Stevens' archive presents some additional > insight: > > <http://www.kohala.com/start/papers.others/vanj.99feb08.txt> But note the date of this (1988). Clearly, router vendors are handling this much better today, in light of 1122. Today tracert almost works as well as traceroute. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman(a)es.net Phone: +1 510 486-8634

1 0

POC at AOL for web flavored questions.
by Marc Goldberg 01 Oct '03

01 Oct '03

There was recently a thread regarding ability to access some SSL sites from the AOL service, so I thought I'd sign up here and reach out. If anyone has questions/problems regarding AOL's web access, please feel free to contact me at webmarc(a)aol.com or on the office phone at 703-265-0906 (please be gentle :-). Thanks, Marc -- Marc Goldberg, 703 265 0906 Technical Manager, AOL Internet Access Operations A single phone call is worth a thousand emails. So be really productive today, and call me :-)

2 1

Re: Annoying dynamic DNS updates
by Stewart, William C (Bill), RTSLS 01 Oct '03

01 Oct '03

Some cable user's machine running default-configured MS apps is sending Paul dynamic DNS queries that it shouldn't, because somehow it's decided he's got an interesting destination (I'm guessing f.root-servers.net ?) Paul wants the user to get an error popup about it. Well, default-configured Microsoft applications have an application that lets you send a machine popup dialog boxes; it's been discussed here recently because spammers abuse it and (related discussion) it uses Port 135, so it might or might not be blocked by Comcast.net. So the obvious thing to do is find whichever program it is you use to send those messages, and start sending popups, guessing that it might not be blocked. The user's unlikely to have a clue what to do about them, but if you include a URL, you may get their attention.

5 4