RE: ISP BGP change processes and non-aggregate announcements

First off, your upstream provider is not "required" to accept or
advertise anything.  This is completely dependent of the agreement
(contract?) you have with them.

Having said that there are a lot of things here that could influence
your question.  Is your netblock your own PI space or is it PA space you
got from one or the other provider?  Most BGP providers will advertise
down to a /24 on a special request.  I have done so with AT&T and with
Sprint.  Virtually nobody will advertise smaller than a /24, and even if
they did it would not be widely accepted.  

There should be no problem at all if you are getting your netblock from
one of your providers.  They should accept anything you wish to
advertise.  Bear in mind that they will aggregate their outgoing
announcements.

You can always register your ASN with Merit's RADB (radb.net) to get
around the altdb issue.  

Kevin

:$s/worry/happy/g 





> -----Original Message-----
> From: [email protected] 
> [mailto:[email protected]] On Behalf Of Higham, Josh
> Sent: Friday, September 21, 2007 10:52 AM
> To: [email protected]
> Subject: ISP BGP change processes and non-aggregate announcements
> 
> I have a question for the ISP people out there regarding BGP 
> announcements.  I used to be on the ISP side, but am not on 
> the enterprise side and having problems with one of our providers.
> 
> First, does anyone have specifics on what level3 and cogent 
> (our ISP's upstream providers) require to accept a new 
> announcement?  I have asked for the flexibility to announce 
> anything within our ARIN allocation (down to a /24) with a 
> max-prefix cap (not that I want to regularily do so, but 
> because I want to be able to do so in an emergency).
> 
> Our provider says that level3 requires any routes be listed 
> in altdb as objects (as opposed to ARIN), and it sounds like 
> adding is a manual process (during which level3 will verify 
> against altdb).  For cogent they said they have to list the 
> specific route announcement, and cannot allow longer-prefixes.
> 
> Is this how the providers work, or is my ISP just not willing 
> to make the necessary requests?  I am trying to announce both 
> our aggregate and a smaller block as a temporary fix for an 
> external BGP problem, and I think they are just trying to 
> keep me from doing something 'bad'.
> 
> Thanks,
> Josh
> _______________________________________________
> "Eat sushi frequently". - Avi
> [email protected] is the human contact address.
> [email protected] is the list posting address.
> See below URL for subscribe/unsubscribe and list options:
> http://inet-access.net/mailman/listinfo/list
> 
_______________________________________________
"Eat sushi frequently". - Avi
[email protected] is the human contact address.
[email protected] is the list posting address.
See below URL for subscribe/unsubscribe and list options:
http://inet-access.net/mailman/listinfo/list