[193432] in North American Network Operators' Group
Re: Questions on IPv6 deployment
daemon@ATHENA.MIT.EDU (Michael Still)
Tue Jan 17 15:16:44 2017
X-Original-To: nanog@nanog.org
In-Reply-To: <742C49EB-205D-4C96-BF96-DD61B361BE21@corp.crocker.com>
From: Michael Still <stillwaxin@gmail.com>
Date: Tue, 17 Jan 2017 12:48:02 -0500
To: Matthew Crocker <matthew@corp.crocker.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
Hi, a few years back some in the community got together to write this:
On Mon, Jan 16, 2017 at 10:11 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
>
--=20
[stillwaxin@gmail.com ~]$ cat .signature
cat: .signature: No such file or directory
[stillwaxin@gmail.com ~]$
