Re: Provider backbone engineering [7:44778]

I'm responding to dre. >""Howard C. Berkowitz"" wrote in message >[EMAIL PROTECTED]">news:[EMAIL PROTECTED]... >> At 11:27 PM -0400 5/22/02, dre wrote: >> >> The first key question to ask here: what is the broad routing >> >> paradigm? Cold potato/closest exit or hot potato/best exit? >>

Re: Provider backbone engineering [7:44778]

> ""Howard C. Berkowitz"" wrote in message > [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... Two more things (going back to more original topics I want to cover again). > > The first key question to ask here: what is the broad routing > > paradigm? Cold potato/closest exit or hot potato/best exi

Re: Provider backbone engineering [7:44778]

""Howard C. Berkowitz"" wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > At 11:27 PM -0400 5/22/02, dre wrote: > >> The first key question to ask here: what is the broad routing > >> paradigm? Cold potato/closest exit or hot potato/best exit? > > > >For a "peering routes" examp

Re: Provider backbone engineering [7:44778]

At 11:27 PM -0400 5/22/02, dre wrote: >""Howard C. Berkowitz"" wrote in message >[EMAIL PROTECTED]">news:[EMAIL PROTECTED]... >> >> -- in the real world, it's VERY rare to redistribute between a dynamic >> >> IGP and BGP. Sure, there are exceptions, but they are VERY carefully >> >> chosen. >

Re: Provider backbone engineering [7:44778]

""Howard C. Berkowitz"" wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > >> -- in the real world, it's VERY rare to redistribute between a dynamic > >> IGP and BGP. Sure, there are exceptions, but they are VERY carefully > >> chosen. > >> A provider backbone CANNOT survive having

Re: Provider backbone engineering [7:44778]

At 7:58 PM -0400 5/22/02, dre wrote: >""Howard C. Berkowitz"" wrote in message >[EMAIL PROTECTED]">news:[EMAIL PROTECTED]... >> >> :-) well, my book on the subject, "Building Service Provider >> Networks," should be about to ship. >> >> Seriously, let's talk about several areas, beginning with