- Test - lists.nanog.org

RE: jumbo frames
by Rowland, Alan D 27 Apr '01

27 Apr '01

I am not an EE but maybe if you rephrased the question as Which is greater, the cpu cycles to assemble/dissemble jumbo frames or the additional cycles/bandwidth of more numerous ACK packets? Then again, I may be way out of my depth here. -Al -----Original Message----- From: Kurt Kayser [mailto:kurt@noris.de] Sent: Friday, April 27, 2001 8:07 AM To: Tony Hain Cc: Roeland Meyer; John Fraizer; Paul Lantinga; nanog(a)merit.edu Subject: Re: jumbo frames Hi, Isn't it a lot more cpu-intensive to 'collect' some 1500-byte frames into some larger bucket, reassemble it into a jumbo-frame when the next box has to chop it in order to send it out on a Sonet/PPP/etc interface which might have a smaller MTU again? Doesn't make too much sense to me. I guess that was Tony's aim as well.. Kurt > Roeland you are talking about jumbo frames from the end system lan, while > John is talking about only using the jumbo frames between the routers. My > point was that in John's environment the packets will all be 1500 since the > packets are restricted to that size just to get to the router with the GE > interface. I understand that there are perf gains as long as the entire path > supports the larger packets, but I don't understand the claim that having a > bigger pipe in the middle helps. > > Tony > -- noris network AG * tel +49 911 93 52-0 * internet Kilianstraße 142 * fax +49 911 93 52-100 * solution 90425 Nürnberg * http://www.noris.net * provider

1 0

RE: commonly accepted prefix length filters?
by Segal, Mark 27 Apr '01

27 Apr '01

You saw 110,000 from Teleglobe this morning as well? Mark -- Mark Segal Director, Data and Internet Planning Axxent Corp. Tel: (416)907-2858 > -----Original Message----- > From: Jim Mercer [mailto:jim@reptiles.org] > Sent: Friday, April 27, 2001 10:54 AM > To: nanog(a)merit.edu > Subject: commonly accepted prefix length filters? > > > > > our bgp tables are starting (?) to get out of hand. > > we are thinking maybe we should start nuking some routes in > order to reduce > the size of the tables. > > is there a list of commonly accepted aggregating prefix filters? > > > -- > [ Jim Mercer > jim(a)pneumonoultramicroscopicsilicovolcanoconiosis.ca ] > [ Reptilian Research -- Longer Life through Colder > Blood ] > [ aka jim(a)reptiles.org +1 > 416 410-5633 ] >

1 0

commonly accepted prefix length filters?
by Jim Mercer 27 Apr '01

27 Apr '01

our bgp tables are starting (?) to get out of hand. we are thinking maybe we should start nuking some routes in order to reduce the size of the tables. is there a list of commonly accepted aggregating prefix filters? -- [ Jim Mercer jim(a)pneumonoultramicroscopicsilicovolcanoconiosis.ca ] [ Reptilian Research -- Longer Life through Colder Blood ] [ aka jim(a)reptiles.org +1 416 410-5633 ]

3 2

Re: RIP and RIPv2, "The glue that makes the internet work"
by rs＠seastrom.com 27 Apr '01

27 Apr '01

> On the other hand, reports of large, multinational networks > running static routing in their cores seem to indicate a > desire to have routing in the core more stable than any dynamic > protocol will allow. Or lack of sufficient clue in their IT departments to implement anything but static routing (sadly, very often the case in my experience). Which of course is preferable to the four-router thirty-route OSPF "designs" I have seen that put each router in its own area (!). ---rob

1 0

Re: RIP and RIPv2, "The glue that makes the internet work"
by Sean Donelan 27 Apr '01

27 Apr '01

On Thu, 26 April 2001, bmanning(a)vacation.karoshi.com wrote: > On the other hand, reports of large, multinational networks > running static routing in their cores seem to indicate a > desire to have routing in the core more stable than any dynamic > protocol will allow. You only need a dynamic routing protocol if there are alternate paths in your network. If don't have more than one way to get from point A to point B, static routing may be acceptable.

1 0

Spring planting season - Stockton CA fiber cut
by Sean Donelan 27 Apr '01

27 Apr '01

It must be spring-time, folks are digging things up again. There is another fiber cut near Stockton CA affecting several carriers.

1 0

RE: cerf/att.net peering and or transit issues?
by Daniel L. Golding 27 Apr '01

27 Apr '01

The downtime was considerable. It was described as a "catastrophic failure". No exact details of exactly what happened, but appearently something more significant than the average fiber cut, to judge by the length of time between techs arriving on site, and the eventual repair. Daniel Golding NetRail,Inc. "Do Not Taunt Happy Fun Ball" On Thu, 26 Apr 2001, Seth H Holmes wrote: > FYI: They've given a 7PM EDT repair. And I'm seeing our fiber with them > coming up right about now. > > On Thu, 26 Apr 2001, Daniel Golding wrote: > > > > > This was (and is) a major Broadwing fiber cut. > > > > - Daniel Golding > > > > > -----Original Message----- > > > From: owner-nanog(a)merit.edu [mailto:owner-nanog@merit.edu]On Behalf Of > > > Sean Donelan > > > Sent: Thursday, April 26, 2001 6:24 PM > > > To: jade.deane(a)HelloNetwork.com > > > Cc: nanog(a)merit.edu > > > Subject: Re: cerf/att.net peering and or transit issues? > > > > > > > > > > > > There was a fiber cut about that time, which may be affecting > > > routing and transit in various cross-country networks. > > > > > > > > > On Thu, 26 April 2001, "Jade E. Deane" wrote: > > > > Anyone experiencing issues transiting or peering with legacy cerf.net? > > > > > > > > Started noticing issues around 2:30pm PDT > > > > > > > > Jade > > > > > > > > Jade E. Deane > > > > Sr. Network Engineer > > > > helloNetwork > > > > Las Vegas, Nevada > > > > > > > > > > > > > ------------------------------------- > Seth H Holmes > sholmes(a)route-fu.net ICQ# 10085439 > http://www.route-fu.net > > "I believe a self-righteous liberal with a cause is more dangerous > than a Hell's Angel with an attitude." -- author unknown > > | /"\ > | \ / ASCII RIBBON CAMPAIGN > | X AGAINST HTML MAIL > | / \ AND POSTINGS >

1 0

Re: cerf/att.net peering and or transit issues?
by Sean Donelan 26 Apr '01

26 Apr '01

There was a fiber cut about that time, which may be affecting routing and transit in various cross-country networks. On Thu, 26 April 2001, "Jade E. Deane" wrote: > Anyone experiencing issues transiting or peering with legacy cerf.net? > > Started noticing issues around 2:30pm PDT > > Jade > > Jade E. Deane > Sr. Network Engineer > helloNetwork > Las Vegas, Nevada

2 1

cerf/att.net peering and or transit issues?
by Jade E. Deane 26 Apr '01

26 Apr '01

Anyone experiencing issues transiting or peering with legacy cerf.net? Started noticing issues around 2:30pm PDT Jade Jade E. Deane Sr. Network Engineer helloNetwork Las Vegas, Nevada

3 2

RE: Why? Because ICANN
by Cerqua, Toby 26 Apr '01

26 Apr '01

Nevermind! I take it back! I'd never have imagined the amount of traffic that would generate, heh. Sorry to disappoint, but I have to keep my webserver from keeling over dead. -----Original Message----- From: Cerqua, Toby [mailto:tcerqua@platinumsystems.net] Sent: Thursday, April 26, 2001 2:59 PM To: 'nanog(a)merit.edu' Subject: RE: Why? Because ICANN For those of you who can't get through to it, I've provided a temporary alternate locale: http://www.blarf.com/media/icann/icannstage.asp

3 2