February 1997 - Test - lists.nanog.org

RE: Routing Loops
by Vernon Walker 10 Feb '97

10 Feb '97

Here is an example a Customer sent me. Sorry for the poor formating... trying to get from www.hyperchat.com to one of our dial up sites in Jacksonville, FL. Sat Feb 08 19:19:06 bd3u * seph said to Minnie: hi!.. *smile*.. it doesnt appear he is being blocked.. but..there does appear to be a routing problem preventing him from getting here... Below is a trace which shows the problem. He needs to send this trace to his provider...and ask them to followup and ask ANS to fix the problem... okay? Thanks...Seph Tracing route to d00016.jax.bellsouth.net [207.53.14.17] over a maximum of 30 hops: 1 10 ms 10 ms 10 ms usa-cisco.hyperchat.net[165.212.218.8] 2 10 ms 10 ms 10 ms 165.212.231.1 3 181 ms 120 ms 110 ms 192.156.196.252 4 100 ms 100 ms 121 ms 192.103.71.33 5 30 ms 50 ms 40 ms 140.222.96.221 6 60 ms 71 ms 50 ms h12.t8-0.San-Francisco.t3.ans.net[140.223.9.17] 7 * 90 ms 110 ms h13.t16-0.Los-Angeles.t3.ans.net[140.223.9.14] 8 80 ms 60 ms 50 ms h12.t8-0.San-Francisco.t3.ans.net[140.223.9.17] 9 101 ms 90 ms 80 ms h13.t16-0.Los-Angeles.t3.ans.net[140.223.9.14] 10 70 ms 90 ms 91 ms h12.t8-0.San-Francisco.t3.ans.net[140.223.9.17] 11 110 ms 160 ms 120 ms h13.t16-0.Los-Angeles.t3.ans.net[140.223.9.14] 12 120 ms 110 ms 100 ms h12.t8-0.San-Francisco.t3.ans.net[140.223.9.17] 13 140 ms 130 ms 120 ms h13.t16-0.Los-Angeles.t3.ans.net[140.223.9.14] 14 171 ms 180 ms 150 ms h12.t8-0.San-Francisco.t3.ans.net[140.223.9.17] 15 131 ms 150 ms 110 ms h13.t16-0.Los-Angeles.t3.ans.net[140.223.9.14] 16 120 ms 111 ms 130 ms h12.t8-0.San-Francisco.t3.ans.net[140.223.9.17] 17 180 ms 130 ms 131 ms h13.t16-0.Los-Angeles.t3.ans.net[140.223.9.14] 18 130 ms 120 ms 120 ms

3 2

Re: Routing Loops
by Michael Ramsey 09 Feb '97

09 Feb '97

>You missed a "u" - nitrous.digex.net. > >:) DOH!!! sorry about that. I hate being on the road and having to use this damn tiny keyboard. The proper URL is http://nitrous.digex.net

1 0

Re: Anything happening on Sunday
by Paul Ferguson 09 Feb '97

09 Feb '97

Yep, I'm sure there will be a Bar BoF after the BGP tutorial. :-0 - paul At 04:25 PM 2/9/97 -0600, Bob Collie wrote: >On Sun, 9 Feb 1997, Dorn Hetzel wrote: >> >>For those of us who are here a bit early, is anything happening in >>or around the Hyatt on Sunday? >> > >I think that there are NetSCARF and BGP tutorials/meetings later >this evening, and someone (I think Dillon) mentioned that the >ISP/C group was thinking about doing something afterwards. >But, beyond that, I've heard nothing. > >-Bob > > >-- >Bob Collie, Chief Technical Officer, Telalink Corporation >mailto:rmc@telalink.net >

1 0

Re: Anything happening on Sunday
by Paul Ferguson 09 Feb '97

09 Feb '97

Looks like CAIS has a reception on in the Bay View at 17:30. :-) - paul At 03:02 PM 2/9/97 -0500, Dorn Hetzel wrote: > >For those of us who are here a bit early, is anything happening in >or around the Hyatt on Sunday? > >Dorn Hetzel >Epoch Networks > > >Attachment Converted: "C:\DATA\EMAIL\ATTACH~1\Anything happening on Sunday" >

1 0

Routing Loops
by Vernon Walker 09 Feb '97

09 Feb '97

Maybe it's just me, but there seems to have been an increase in routing loops lately. Anyone else seen an increase or am I just paranoid?? Worried for no reason??? Vernon Walker Director - Network Operations Center BellSouth.net walkerv(a)bellsouth.net

2 1

Anything happening on Sunday
by dorn＠atl.eni.net 09 Feb '97

09 Feb '97

For those of us who are here a bit early, is anything happening in or around the Hyatt on Sunday? Dorn Hetzel Epoch Networks

2 1

Re: Unsubstantiated Rumor
by James R. Fisher 09 Feb '97

09 Feb '97

From: MX%"randy(a)psg.com" 9-FEB-1997 10:01:58.40 To: MX%"nanog(a)merit.edu" CC: Subj: Re: Unsubstantiated Rumor Return-Path: <owner-nanog(a)merit.edu> Received: from merit.edu by ISDMNL.WR.USGS.GOV (MX V4.1 VAX) with SMTP; Sun, 09 Feb 1997 10:01:52 PST Received: from localhost (daemon@localhost) by merit.edu (8.8.5/merit-2.0) with SMTP id MAA01011; Sun, 9 Feb 1997 12:59:46 -0500 (EST) Received: by merit.edu (bulk_mailer v1.5); Sun, 9 Feb 1997 12:55:06 -0500 Received: (from daemon@localhost) by merit.edu (8.8.5/merit-2.0) id MAA00936 for nanog-outgoing; Sun, 9 Feb 1997 12:55:06 -0500 (EST) Received: from rip.psg.com (root(a)rip.psg.com [147.28.0.39]) by merit.edu (8.8.5/merit-2.0) with SMTP id MAA00931 for <nanog(a)merit.edu>; Sun, 9 Feb 1997 12:55:03 -0500 (EST) Received: by rip.psg.com id m0vtdSv-000800C; Sun, 9 Feb 97 09:55 PST (Smail3.1.29.1#1) Message-ID: <m0vtdSv-000800C(a)rip.psg.com> Date: Sun, 9 Feb 97 09:55 PST From: randy(a)psg.com (Randy Bush) To: nanog(a)merit.edu Subject: Re: Unsubstantiated Rumor References: <01IF7FWWBUZMA23B63(a)OMEGA7.WR.USGS.GOV> <Pine.BSI.3.95q.970209124243.28620B-100000(a)cais2.cais.com> Sender: owner-nanog(a)merit.edu My intention was not to generate discussion, but to raise the flag and point out the supposed deadline date and the mail address for comments. -jrf ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ I think the proposed Access Tariff is a serious matter. But I think it might be better discussed elsewhere, as it is a business not an ops issue, and is likely to generate some volume for some time. randy

1 0

slides available: TCP and HTTP presentations
by Curtis Villamizar 08 Feb '97

08 Feb '97

Hi, I've talked to Bill Norton about shuffling the schedule a bit and dropping the "ANS use of the IRR for aggregation" and adding the time to the presentation of TCP, and splitting it back into two as we had considered earlier. The "ANS use of the IRR for aggregation" will be presented at a later NANOG. Slides are available for your reading enjoyment for the presentations on TCP and HTTP that will be given. Curtis The slides for the now two separte talks are in the directory: ftp://engr.ans.net/pub/slides/nanog/feb-1997/ the filenames, sizes, and time allocated to the presentations are: tcp-congested.ps 346k 20 slides (15 minutes) tcp-http.ps 459k 27 slides (30 minutes) The first slides in each introduce the topic. These are: tcp-congested.ps: TCP Response Under Loss Conditions It is useful to understand TCP's behavior and in particular, TCP's behavior in the presence of loss. This may help dispell some of the myth regarding emminent collapse of the Internet. This also provides background needed to understand how an application's behavior can affect their own performance, why variations in TCP's algorithms can dramaticly affect performance and how network equipment can affect TCP's performance. tcp-http.ps: What can be done about HTTP small TCP flows? It's well known that HTTP comprises the majority of traffic for most Internet service providers. It is also well known that HTTP as practiced today creates a large number of small TCP flows which do not take advantage of TCP's congestion avoidance due to frequently spending most of their time in TCP slow start. This presentation demonstrates the effects of tuning browser response and benefits of HTTP 1.1 persistent connections. HTTP proxy and other possible improvements are mentioned.

1 0

CASCADE IN BED WITH THE COMMIES!
by Jon Green 07 Feb '97

07 Feb '97

What do you think? Now we better boycott BOTH Bay and Cascade. ;) ------------------------------------------------------------------------- People's Republic of China Builds First Nationwide ATM Network Based on Cascade CBX 500 ATM Switches Major Chinese Win Underscores Growing Acceptance of Cascade ATM Solutions Westford, Mass. -- February 4, 1997 -- Cascade Communications Corp. (NASDAQ: CSCC) today announced it will provide the Chinese government with switches that will be used to build the country's first nationwide broadband digital network. [snip] ----------------------------------------------------------------------------

1 0

.COM auto-caching DNS server
by Jim Fleming 07 Feb '97

07 Feb '97

Despite the IAHC debates, despite the Office of the Inspector General (OIG) investigation of the National Science Foundation (NSF) and despite the moves by the IANA to deploy two TRUE Root Name Servers at Network Solutions, Inc. we still have to focus on software development. As I see it, one of the next major projects on the horizon is the... ".COM auto-caching DNS server" This server will appear to be a standard TLD Name Server for the .COM TLD. The one difference will be that it will cache .COM registration information from the popular Root Name Servers and will log this information. ISPs will be able to use this server to support their subscribers but also to log interest in the various .COM domains. This information can be used by the ISP to bill the owners of the .COM domains for domain services. Just as the NSF and Network Solutions, Inc. have arbitrarily set their domain registration service fees at $50 per year, ISPs should be free to set whatever fees they feel are fair and represent the market. Large ISPs may be able to demand larger fees from .COM owners because they can claim that they have more users that they provide access to the DNS mapping services. As noted in the past, countries and state governments can set up .COM TLD Name Servers as effectively "mirrors" of the 9 popular servers controlled by NSI, and can charge .COM owners to register each year in their servers. With the proposed "COM auto-caching DNS server". -- Jim Fleming Unir Corporation e-mail: JimFleming(a)unety.net JimFleming(a)unety.s0.g0 (EDNS/IPv8)

2 1