[178239] in North American Network Operators' Group
Re: [j-nsp] draft-ietf-mpls-ldp-ipv6-16
daemon@ATHENA.MIT.EDU (Tim Durack)
Fri Feb 20 19:44:28 2015
X-Original-To: nanog@nanog.org
In-Reply-To: <627266B72B856946BCD625D4B34B1916A3215B@INF-EXCH-MB-02.gammatelecom.com>
Date: Fri, 20 Feb 2015 19:44:25 -0500
From: Tim Durack <tdurack@gmail.com>
To: Adam Vitkovsky <Adam.Vitkovsky@gamma.co.uk>
Cc: Juniper-Nsp <juniper-nsp@puck.nether.net>,
"nanog@nanog.org" <nanog@nanog.org>,
"cisco-nsp@puck.nether.net" <cisco-nsp@puck.nether.net>
Errors-To: nanog-bounces@nanog.org
On Fri, Feb 20, 2015 at 6:02 PM, Adam Vitkovsky <Adam.Vitkovsky@gamma.co.uk>
wrote:
> Alright so would you mind sharing the business drivers that would make
> you migrate your current production infrastructure to this new unproven
> possibly buggy LDPv6 and 4PE/4VPE setup please?
>
>
>
> adam
>
Businesses bigger than me think there is a business driver for IPv6:
http://meetings.ripe.net/ripe-54/presentations/IPv6_management.pdf
http://www.internetsociety.org/deploy360/wp-content/uploads/2014/04/WorldIPv6Congress-IPv6_LH-v2.pdf
IPv6 management of equipment is relatively easy. Once you've started down
that path, you start looking at the protocol stuff, and wondering what to
do about that.
Maybe I should leave it alone until the business people figure it out for
me :-)
Tim:>
