How Not to Multihome

Mon Oct 8 22:17:46 UTC 2007

The only thing that sounds worse would be to give them address space and 
tell them to NAT the traffic based on the path it takes.

Keegan Holley
Network Engineer, Network Managed Services
SunGard Availability Services
Mezzanine Level MC-95
401 N. Broad St.
Philadelphia, PA 19108
215.446.1242 (office)
609.670.2149 (cell)
Keegan.Holley at sungard.com
___________________________________________
Keeping People and Information Connected®
http://www.availability.sungard.com 

"Wayne E. Bouchard" <web at typo.org> 
10/08/2007 05:53 PM

To
Keegan.Holley at sungard.com
cc
nanog <nanog at merit.edu>, owner-nanog at merit.edu
Subject
Re: How Not to Multihome

Slightly different approach... Needing to multihome is justification
for requesting an ASN. Is this strictly necessary? No. You can source
the block on his behalf but that creates various routing
inconsistancies. There are other even more unpleasant ways of doing
this that are perfectly feasible. (I'd be willing to use them if I was
the client since I know what I'm doing but I would not be willing to
have a client of mine use them because it would scare the hell out of
me.)

-Wayne

On Mon, Oct 08, 2007 at 05:43:03PM -0400, Keegan.Holley at sungard.com wrote:
> I have a client that wants us to advertise an IP block assigned by 
another 
> ISP.  I know that the best practice is to have them request an AS number 

> from ARIN and peer with us, etc.  However, I cannot find any information 

> that states as law.  Does anyone know of a document or RFC that states 
> this?
> 
> Thanks,
> 
> Keegan
---
Wayne Bouchard
web at typo.org
Network Dude
http://www.typo.org/~web/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20071008/fd436b5c/attachment.html>