[101743] in North American Network Operators' Group
Re: request for help w/ ATT and terminology
daemon@ATHENA.MIT.EDU (Kevin Loch)
Wed Jan 16 22:29:12 2008
Date: Wed, 16 Jan 2008 22:27:45 -0500
From: Kevin Loch <kloch@kl.net>
To: Mike Donahue <mdonahue@watg.com>
CC: nanog@merit.edu
In-Reply-To: <49900C758A716C499CE8C56BF0CB52710814D94B@newexch01.ohana.watg.com>
Errors-To: owner-nanog@merit.edu
Mike Donahue wrote:
> Hi. I'm by no means an ip/networking expert, and we're having some
> difficulty communicating with the boffins at AT&T. Any
> input/advice/translation would be appreciated.
>
> We own our own class C netblock. Our previous provider, Sprint, had no
> problem "adding" it to their network/advertising it (that circuit is now
> disconnected). We've started using an AT&T colo facility, and we're
> having a lot of trouble trying to get AT&T to do the same thing there
> that Sprint was able to do for us. AT&T is refusing to advertise our
> netblock/path it to our cabinet unless we have an AS number. ARIN has
> refused to give us one on the grounds (rightly so) that we're not
> multi-homed.
muli-homing is one way to justify an ASN, "unique routing policy" is
the other. Your directly assigned /24 could be a reason to have
a unique routing policy, especially if your upstreams are unwilling
to originate it from their ASN(s). You may want to re-apply for an
ASN and explain that you will be announcing your directly assigned
block in section 14 of the template.
- Kevin
