[148549] in North American Network Operators' Group
Re: bgp question
daemon@ATHENA.MIT.EDU (Deric Kwok)
Wed Jan 18 08:59:09 2012
In-Reply-To: <Pine.LNX.4.64.1201101948430.3323@whammy.cluebyfour.org>
Date: Wed, 18 Jan 2012 08:58:09 -0500
From: Deric Kwok <deric.kwok2000@gmail.com>
To: "Justin M. Streiner" <streiner@cluebyfour.org>
Cc: nanog list <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Hi Justin
Thank you
Could you tell me more about "routing registries"?
I would like to learn it
2nd questions? Are you familiar to quagga?
ls it supporting equally multipath in different bgp connections?
Thank you so much
On Tue, Jan 10, 2012 at 7:58 PM, Justin M. Streiner
<streiner@cluebyfour.org> wrote:
> On Tue, 10 Jan 2012, Deric Kwok wrote:
>
>> When we get =A0newip, we should let the upstream know to expor it as
>> there should have rule in their side.
>
>
> Correct. =A0Ideally, two things happen:
> 1. You tell your upstreams and peers about the new space, and they update
> whatever prefix filters they have in place for your network.
> 2. You update you own outbound BGP filters wherever necessary so that you
> can announce the new prefix, aggregated to the extent possible, when you'=
re
> ready.
>
>
>> how about upstream provider, does they need to let their all bgp
>> interconnect to know those our newip?
>
>
> They might. =A0It depends on the relationship your upstreams have with th=
eir
> neighbors. =A0Different providers have different criteria for what they'l=
l
> accept and how they manage their filters.
>
> If your upstreams need to have their upstreams and/or peers update their =
BGP
> filters, it is their responsibility to notify them. =A0Note that this can=
add
> to the amount of time it will take before your direct upstreams are ready=
to
> accept and propagate your new prefix.
>
> Some providers might require that your new prefix be registered in one of
> several routing registries, and they'll update their filters based on you=
r
> new registry data.
>
> jms
>
