[193947] 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 (Jeremy Austin)
Fri Mar 3 23:01:06 2017

X-Original-To: nanog@nanog.org
In-Reply-To: <20170304020515.GH1029@Vurt.local>
From: Jeremy Austin <jhaustin@gmail.com>
Date: Fri, 3 Mar 2017 18:59:20 -0900
To: Job Snijders <job@instituut.net>
Cc: NANOG list <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

On Fri, Mar 3, 2017 at 5:05 PM, Job Snijders <job@instituut.net> wrote:

> > There are, of course, corner cases. But in general, single-homed
> > people shouldn=E2=80=99t be using BGP.
>
> There are numerous reasons to use BGP when single-homed:
>
>     - as preparation to multi-home in the (near) future
>     - ability to quickly change providers
>     - to use BGP based blackholing features
>     - to save time on provisioning work (adding new prefixes becomes a
>       matter of just announcing and updating IRR/RPKI).
>     - loadbalanacing / loadsharing across multiple links
>     - ability to use bgp communities for traffic engineering
>
> In other words, if you have your own IP space, I'd recommend to get your
> own ASN and use BGP.


I concur with Job.

If you are single-homed but care about having proper L3 redundancy (not
just VRRP or equivalent), BGP is a must.

ARIN has a policy to allow this, but it is not spelled out with an excess
of clarity. I suspect it is not often used; see NRPM section 5.

--=20
Jeremy Austin

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