[193416] in North American Network Operators' Group

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

Re: Questions on IPv6 deployment

daemon@ATHENA.MIT.EDU (Ca By)
Mon Jan 16 12:17:21 2017

X-Original-To: nanog@nanog.org
In-Reply-To: <742C49EB-205D-4C96-BF96-DD61B361BE21@corp.crocker.com>
From: Ca By <cb.list6@gmail.com>
Date: Mon, 16 Jan 2017 17:17:06 +0000
To: Matthew Crocker <matthew@corp.crocker.com>,
 "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org

 Why do not you feel compelled to ask this question?

Did you ask this question when you deployed ipv4?

AFAIK, everyone deploys ipv4 in a unique way. Same for ipv6. IPv6 is not
exotic or filled with unique pitfalls.  A lot of networks have deployed
production networks with ipv6, each one unique, so you don't need to watch
out for that one weird bug ( at least any more than ipv4). So, just like
ipv4, read about the standards, read about vendor implementation that are
close to you, make informed decisions.

My only nugget of advice is to deploy ipv6 in such a way it is not forever
coupled with ipv4.  There will be a day when you deploy ipv6 without ipv4,
this day already came for  Facebook, Comast, T-mobile and others.

I have not read this, but you may find the discussion helpful

https://tools.ietf.org/html/draft-ietf-v6ops-design-choices-12




On Mon, Jan 16, 2017 at 7:13 AM Matthew Crocker <matthew@corp.crocker.com>
wrote:

>
>
> Hello,
>
>
>
> I=E2=80=99m AS7849 and I have an IP problem.
>
>
>
> I=E2=80=99m running IPv4 ( /16 legacy + /20) and have enough space to las=
t me for
> a while,  multi-homed, BGP4 full tables + peering, ect.
>
> I have some new shiny Juniper MX480s (RE-S-2X00x6, 64MB RAM) in my core.
>
>
>
> I want to start building my IPv6 infrastructure.
>
>
>
> I have a /32 assigned from ARIN (2001:4918::/32)
>
>
>
> I=E2=80=99m looking for some direction/reading list of how to properly co=
nfigure
> IPv6.  I=E2=80=99ve read to use a /64 for PtP interfaces and I=E2=80=99ve=
 read use a /128
> instead.    Assign all loopbacks from the same /64, use a different /64 f=
or
> each loopback. Ect, ect.
>
>
>
> I=E2=80=99m trying not to light a religious war but what is the current b=
est
> practice for IPv6 deployment in a service provider network?
>
>
>
> PS.  I=E2=80=99ll be at NANOG69 in DC next month,  1st NANOG for me after=
 22
> years.  =E2=98=BA
>
>
>
> -Matt
>
>
>
> --
>
> Matthew Crocker
>
> Crocker Communications, Inc.
>
> President
>
>

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