[101756] in North American Network Operators' Group
Re: request for help w/ ATT and terminology
daemon@ATHENA.MIT.EDU (John Payne)
Thu Jan 17 11:01:54 2008
In-Reply-To: <49900C758A716C499CE8C56BF0CB52710814D94B@newexch01.ohana.watg.com>
Cc: <nanog@merit.edu>
From: John Payne <john@sackheads.org>
Date: Thu, 17 Jan 2008 10:49:49 -0500
To: Mike Donahue <mdonahue@watg.com>
Errors-To: owner-nanog@merit.edu
On Jan 16, 2008, at 4:37 PM, Mike Donahue wrote:
> 2. What's the technical terminology for the request for AT&T to
> simply
> start advertising our netblock called? I'm wondering if they're not
> understanding our request.
According to the cached copy of AT&T's bgp4policy.doc at:
http://www.onesc.net/communities/as7018/bgp4policy.pdf
You should just be able to setup BGP with a private ASN. It's not
quite what you asked for, but it should be "in policy" at AT&T.
I know we've run into providers that absolutely insist on a customer
router even inside the provider's colo, and plenty more that don't.
"Their network, their rules".
I'm assuming you have a switch connected to the ethernet handoff. A
lot of 1U switches now will do a little bit of layer 3 (including
BGP) so it shouldn't necessarily add any equipment to your setup to
accomplish this.
Ethernet handoff on one VLAN, your servers on the other... BGP
session announcing your /24 with a private-as, and accepting default
only (or dropping all routes and running with a static default,
whatever floats your boat).
