[c-nsp] BGP Propigation

[Gert Doering]

Hi,

On Wed, May 16, 2007 at 07:18:35AM -0400, Richey wrote:
> Typically, how long should it take to propagate a /24 across the net?   This
> isn't a new /24 from arin so it should not be filtered.   It's supposedly
> being announced but route-server.ip.att.net does not have the slightest clue
> about this /24 and we connect to AT&T.  I'm wondering how long I should wait
> before I should gripe.  I was given the /24 a week ago and it's still not
> useable today.  I opened a ticket at the end of last week and it's still not
> working.  Before I start pestering everyone I want to make sure I am not
> acting too soon.

Normal propagation time (regarding BGP timers) should be in the order
of "15 minutes".  If the prefix isn't visible, chances are high that your
upstream isn't taking it from you - make sure you actually send it, and
that they have adapted their filters to accept it.

I don't know about AT&T, but over here, the usual requirement is "entering
documentation in the RIPE DB" - in form of a route: object that declares
that you're going to announce that prefix.

Some upstreams require manual filter updating, read "send them a mail and
let them know" (which is easily spoofed - and slower than necessary).

gert

-- 
USENET is *not* the non-clickable part of WWW!
                                                           //www.muc.de/~gert/
Gert Doering - Munich, Germany                             gert at greenie.muc.de
fax: +49-89-35655025                        gert at net.informatik.tu-muenchen.de