[193941] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: google ipv6 routes via cogent

daemon@ATHENA.MIT.EDU (Nick Hilliard)
Fri Mar 3 07:01:22 2017

X-Original-To: nanog@nanog.org
X-Envelope-To: <nanog@nanog.org>
Date: Fri, 03 Mar 2017 12:00:28 +0000
From: Nick Hilliard <nick@foobar.org>
To: nanog@nanog.org
In-Reply-To: <20170303115601.GE86663@excession.tpb.net>
Errors-To: nanog-bounces@nanog.org

Niels Bakker wrote:
> As I explained in the rest of my email that you conveniently didn't
> quote, it's so that you can selectively import routes from all your
> providers in situations where your router cannot handle a full table.

it can also break horribly in situations where the provider is providing
"transit" but doesn't provide full transit.

OTOH, if you are single-homed, it is highly advisable to accept a
default, the reason being that most transit providers provide bgp
communities with "don't advertise to customers" semantics.  So if you're
single-homed and use a full dfz feed without default route, you will not
have full connectivity to all the routes available from the transit
provider.

Nick

home help back first fref pref prev next nref lref last post