Re: [v6ops] Operational Consensus on deployment

Owen DeLong <owen@delong.com> Tue, 05 August 2014 17:36 UTC

Return-Path: <owen@delong.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 B37941A005D for <v6ops@ietfa.amsl.com>; Tue, 5 Aug 2014 10:36:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.992
X-Spam-Level:
X-Spam-Status: No, score=-0.992 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=no
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 ZN57BSiWlDW6 for <v6ops@ietfa.amsl.com>; Tue, 5 Aug 2014 10:36:10 -0700 (PDT)
Received: from owen.delong.com (owen.delong.com [IPv6:2620:0:930::200:2]) by ietfa.amsl.com (Postfix) with ESMTP id AA4561A004E for <v6ops@ietf.org>; Tue, 5 Aug 2014 10:36:09 -0700 (PDT)
Received: from [172.26.26.231] ([65.113.17.1]) (authenticated bits=0) by owen.delong.com (8.14.2/8.14.2) with ESMTP id s75HUqKm016313 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 5 Aug 2014 10:30:53 -0700
X-DKIM: Sendmail DKIM Filter v2.8.3 owen.delong.com s75HUqKm016313
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=delong.com; s=mail; t=1407259854; bh=4AT6u65hV6R9F0Dpf5DP/cnXmWI=; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc: Content-Transfer-Encoding:Message-Id:References:To; b=NR08vMWeeBo3OlFfH2WySEsKC+Ie8BQW5tDGvIK5J8AmYWvF6mx6/0PISrQBjJKIB cmAimCoiCzwyu1Ojc61vX63vWpa+X0olgMyovRL+z8D+9rxKS997GDGlZgi0b7B+ZC VzFu5Jnavi0H9rGnjsbadDM7qTp/S8rNBwe0b0og=
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (1.0)
From: Owen DeLong <owen@delong.com>
X-Mailer: iPhone Mail (11D257)
In-Reply-To: <C5281716-DC04-42E6-AC82-0D53E5DA0284@nominum.com>
Date: Tue, 05 Aug 2014 10:30:48 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <CC58B514-54BD-4928-819F-9A286E8FD0E4@delong.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> <53E06AC9.9010908@fud.no> <4F7D76F6-BD81-453B-94DC-A3C3DFF68505@delong.com> <8600C096-37D0-4651-92C1-BCFDBA674433@nominum.com> <CAD6AjGTBfyT-zNDJtBKCNtRxd=Hi07678Sr_-HgSGYbjAiF3Tg@mail.gmail.com> <C5281716-DC04-42E6-AC82-0D53E5DA0284@nominum.com>
To: Ted Lemon <ted.lemon@nominum.com>
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0rc1 (owen.delong.com [192.159.10.2]); Tue, 05 Aug 2014 10:30:54 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/5rlaXsy3Jqi9hTH3NslYVttVN4M
Cc: Tore Anderson <tore@fud.no>, IPv6 Ops WG <v6ops@ietf.org>
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 17:36:11 -0000

While this is rare, I come rely agree with Ted here. 

Well said, Ted. 

Owen


> On Aug 5, 2014, at 9:53, Ted Lemon <ted.lemon@nominum.com> wrote:
> 
>> On Aug 5, 2014, at 12:00 PM, Ca By <cb.list6@gmail.com> wrote:
>> In summary, the premise of the daul stack transition for the Internet
>> is faulty.  It already failed.
> 
> With all due respect, I don't see how what you have said here benefits the discussion.   First of all, there's a great deal of evidence that what you've said isn't actually true, and secondly, even to the extent that it is true, it's not really actionable.  Of course there will be people who will do things the wrong way, and either limp along forever or eventually get bulldozed off the cliff.   So what?  
> 
> There are still mainframes in back offices running SNA, but that doesn't mean that IPv4 is irrelevant: quite the opposite--they are probably running SNA in IP tunnels, their 370 is probably an emulation running on an Intel box, and chances are that people are sshing in using a 3270 emulator.   So we don't care that they are still running SNA, and we don't care when they get rid of it, because it is not an "internet" protocol.   That is the future of IPv4 as well.
> 
> The question is, are there people who want to do a transition to IPv6 (or will want to), whether for altruistic or pragmatic reasons, and if so, is there additional help we can offer them, or is what we've done thus far sufficient?