[99931] in North American Network Operators' Group
Re: How Not to Multihome
daemon@ATHENA.MIT.EDU (Bill Stewart)
Tue Oct 9 13:58:56 2007
Date: Tue, 9 Oct 2007 10:57:05 -0700
From: "Bill Stewart" <nonobvious@gmail.com>
To: "Keegan.Holley@sungard.com" <Keegan.Holley@sungard.com>
Cc: nanog <nanog@merit.edu>
In-Reply-To: <OFA24BA2E6.2628DE6D-ON8525736E.0079B378-8525736E.007A3633@sungard.com>
Errors-To: owner-nanog@merit.edu
------=_Part_8219_11607144.1191952625839
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
On 10/8/07, Keegan.Holley@sungard.com <Keegan.Holley@sungard.com> wrote:
>
> That brings up an interesing point. My biggest fear was that one of my
> other customers could possible be closer to me that the ISP that provides
> the primary link and it would cause them to favor the backup link because of
> AS path. I think they are going to fight me on this and telling them to
> multihome to their original ISP would probably be frowned upon at this
> point. I was hoping that there was an RFC for multihoming that I could use
> to bail myself out.
What they're asking to do is really Just Fine. It may or may not accomplish
what they want, depending on how they do it, e.g. whether traffic will go
through their other ISP or yours. The main reason it's a Not Best Practice
is that it often doesn't get what the user wants, e.g. the user only has a
/29, so only the aggregate advertisement from their primary ISP works
anyway, or it's PA space so they'll still have to give it up if they change
ISPs. But if they've got a /24, that's big enough that most carriers will
see it these days, and there's no need to clutter up the BGP ASN space if
your user doesn't need the extra flexibility.
There may even be a market for ISPs to do multihoming on a cabal basis, e.g.
Carrier X and Carrier Y get a /20 that they assign routes from to customers
that use both of them, but only advertise the aggregate to the rest of the
net. They'd still need to handle the more specific routes internally and
exchange them across their peering link, but wouldn't have to bother the
rest of the net with that level of detail.
--
----
Thanks; Bill
Note that this isn't my regular email account - It's still experimental so
far.
And Google probably logs and indexes everything you send it.
------=_Part_8219_11607144.1191952625839
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
<br><br><div><span class="gmail_quote">On 10/8/07, <b class="gmail_sendername"><a href="mailto:Keegan.Holley@sungard.com">Keegan.Holley@sungard.com</a></b> <<a href="mailto:Keegan.Holley@sungard.com">Keegan.Holley@sungard.com
</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<font face="sans-serif" size="2">That brings up an interesing point.
My biggest fear was that one of my other customers could possible
be closer to me that the ISP that provides the primary link and it would
cause them to favor the backup link because of AS path. I think they
are going to fight me on this and telling them to multihome to their original
ISP would probably be frowned upon at this point. I was hoping that
there was an RFC for multihoming that I could use to bail myself out.</font></blockquote><div><br>
What they're asking to do is really Just Fine. It may or may not
accomplish what they want, depending on how they do it, e.g. whether
traffic will go through their other ISP or yours. The main reason it's
a Not Best Practice is that it often doesn't get what the user wants,
e.g. the user only has a /29, so only the aggregate advertisement from
their primary ISP works anyway, or it's PA space so they'll still have
to give it up if they change ISPs. But if they've got a /24,
that's big enough that most carriers will see it these days, and
there's no need to clutter up the BGP ASN space if your user doesn't
need the extra flexibility.<br>
<br>
There may even be a market for ISPs to do multihoming on a cabal basis,
e.g. Carrier X and Carrier Y get a /20 that they assign routes from to
customers that use both of them, but only advertise the aggregate to
the rest of the net. They'd still need to handle the more
specific routes internally and exchange them across their peering link,
but wouldn't have to bother the rest of the net with that level of
detail.<br>
</div><br></div><br>-- <br>----<br> Thanks; Bill<br><br>Note that this isn't my regular email account - It's still experimental so far.<br>And Google probably logs and indexes everything you send it.
<br>
------=_Part_8219_11607144.1191952625839--
