Re: [v6ops] Operational Consensus on deployment

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 05 August 2014 03:25 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F9821B27D8 for <v6ops@ietfa.amsl.com>; Mon, 4 Aug 2014 20:25:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3r73Dhzv36Wv for <v6ops@ietfa.amsl.com>; Mon, 4 Aug 2014 20:25:19 -0700 (PDT)
Received: from mail-pd0-x22c.google.com (mail-pd0-x22c.google.com [IPv6:2607:f8b0:400e:c02::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E30B51B27B9 for <v6ops@ietf.org>; Mon, 4 Aug 2014 20:25:18 -0700 (PDT)
Received: by mail-pd0-f172.google.com with SMTP id ft15so496571pdb.17 for <v6ops@ietf.org>; Mon, 04 Aug 2014 20:25:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=tMawuvCvMZEkWNGEQaCzXUwN8xyN3ppvwmEhAVDsFXQ=; b=beWPwUd7ut0LqlAFDDY4JTJ83AAvsrQpGAJv8j7V7EmF6be4SdgAPZM3C5s9MBv4jJ p0WpQMF5Vc9WTi6lVXjpw6Z+KQAc/TLYIUR34jlm0M3HrJlA37mHS7c6RdSJbnFTtPFO WNvFn3Msu8cLiQIkLAy6u73EW2oOmwOQ+sOPSdouuEVvs2VQUCrtUL5jjUcYh1Abye8o DhbNS0d/ZsTcr7Pyd+D0DRlO3OCwE16i0gJFiIFE0EnxYkb6X5qZ8xe50xawV+FdV+O8 ujD+6kGb8uclmNv1H7PSFCe3RcX6fX3ztGRUsbVQpqyAk5/yCUCJPtK7iWcdhd5j5XSK h/FQ==
X-Received: by 10.70.50.230 with SMTP id f6mr1053470pdo.84.1407209118508; Mon, 04 Aug 2014 20:25:18 -0700 (PDT)
Received: from [192.168.178.23] (202.195.69.111.dynamic.snap.net.nz. [111.69.195.202]) by mx.google.com with ESMTPSA id oy12sm336310pbb.27.2014.08.04.20.25.16 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 04 Aug 2014 20:25:17 -0700 (PDT)
Message-ID: <53E04E9D.6060302@gmail.com>
Date: Tue, 05 Aug 2014 15:25:17 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Ca By <cb.list6@gmail.com>
References: <256EAE0B-5C11-42C7-BCA1-CEC7EE6713A7@cisco.com> <53DFD634.4020304@fud.no> <DE860EBC-171E-46E7-A3B6-5E8B79A453CC@cisco.com> <53DFEC6C.3010707@gmail.com> <CAD6AjGRUWxT5XiNxMi_S5VgYtGMLb_FVHXN-ZfGpcY=geix15g@mail.gmail.com>
In-Reply-To: <CAD6AjGRUWxT5XiNxMi_S5VgYtGMLb_FVHXN-ZfGpcY=geix15g@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/wIZeIeDc9gB_lrO28i56-VnWsKI
Cc: IPv6 Ops WG <v6ops@ietf.org>, Tore Anderson <tore@fud.no>
Subject: Re: [v6ops] Operational Consensus on deployment
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Aug 2014 03:25:21 -0000

On 05/08/2014 15:09, Ca By wrote:
> On Aug 4, 2014 1:26 PM, "Brian E Carpenter" <brian.e.carpenter@gmail.com>
> wrote:
>>
>>> My point in bringing this up is not that it is “useful in an IPv6
> network” that might also be running IPv4 in parallel. It is that it seems
> useful to me in moving toward and IPv6-*only* network. Ross suggests that
> he sees conceptual movement - First they ignore you, then they laugh at
> you, then they fight you, and then you win. We may, Ross suggests, be
> approaching stage 4. It may be useful for us as a working group to lay out
> the game plan for that movement - not just to document IPv6 operational
> practice, but to help the IETF determine whether the dual stack consensus
> has changed or is changing, and help operators figure out how to turn IPv4
> off without individually shooting their toes off. This would be part of
> that game plan.
>> Well, I think the operators that moved early into genuine dual
>> stack operation have no reason to regret it. I'm a happy customer
>> of one such. On the other hand it seems that other operators are of
>> the opinion (probably unprovable) that providing the illusion of dual
>> stack service to the customer over an IPv6 infrastructure is cheaper.
>> In any case the customer ends up with NATted IPv4 service in most
>> cases, so at user level it doesn't really matter.
>>
>> I think we should probably not express a preference either way. It
>> seems like a decision for each operator to make individually. What we
>> probably should do is stop inventing more solutions.
>>
> 
> Why?
> 
> I was told the same thing about 464xlat, we did not need another solution.
> If the ietf held the line against double translation i believe there would
> be exactly 1 ipv6 cellular provider in the world (verizon).
> 
> With 464xlat, afaik, there are globally 3 cellular providers that offer
> default ipv6 (464xlat at tmobile us and Orange PL and DS at VZ).

OK, but beyond a certain point vendors will want to stop adding options
and operators will want finite choices. We must be very close to that point
now.

> It does not matter if the cat is white or black, it matters that it catches
> mice.

The pragmatist in me agrees with you. The former software team leader in
me is stressed out with the choices.

    Brian

> 
> CB
> 
>> (In parenthesis, I've never seen sunsetting IPv4 as a real problem.
>> One day somebody will notice that there are no more IPv4 packets. But
>> that is many years in the future.)
>>
>>     Brian
>>
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
>