|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |
Date: Thu, 14 Sep 2000 23:47:41 -0700 From: Austin Schutz <tex@off.org> To: Tony Tauber <ttauber@genuity.net> Cc: "Roeland M.J. Meyer" <rmeyer@MHSC.com>, David Lott <dlott@msncomm.com>, nanog@merit.edu Message-ID: <20000914234741.F28153@gblx.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <Pine.GSO.4.21.0009141804360.14064-100000@mesa.bbnplanet.com>; from ttauber@genuity.net on Thu, Sep 14, 2000 at 06:09:41PM -0400 Errors-To: owner-nanog-outgoing@merit.edu > > Yep, this has been a topic here before...no real resolution. You didn't > > really need to prove the case, it has already been proven. > > No. From a post I made to this list on 6/22/2000: > > ++> Here's the deal. If you number out of Provider1's CIDR block > ++> but advertise your more-specific to Provider2 and the two Providers > ++> touch and Provider1 accepts the more-specific route from Provider2, > ++> you should have no problem reaching anyone. > ++> > ++> Here's the reason: Everyone accepts Provider1's announcement of the block. > ++> When your link to P1 is up, any traffic they recieve for your prefix > ++> gets routed over that link since they carry your more-specific internally. > ++> However, if other providers here the more-specific from P2, they'll > ++> send directly via P2 who sends it over the link to you. But if your chunk of space is greater than /20, the other providers will filter P2's announcement of your space and you are back to square one. Well, at least you won't be cut off from the entire Internet, I guess that's something. Square 1.5. Austin
|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |