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