Re: [v6ops] The need for local-ipv4 socket transition solutions -- NAT64/DNS64 remains insufficient

Ca By <cb.list6@gmail.com> Wed, 22 April 2015 15:12 UTC

Return-Path: <cb.list6@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 BCB611A1A6D for <v6ops@ietfa.amsl.com>; Wed, 22 Apr 2015 08:12:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 w7YDnTUVGiUt for <v6ops@ietfa.amsl.com>; Wed, 22 Apr 2015 08:12:54 -0700 (PDT)
Received: from mail-wg0-x230.google.com (mail-wg0-x230.google.com [IPv6:2a00:1450:400c:c00::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 263F81A1A62 for <v6ops@ietf.org>; Wed, 22 Apr 2015 08:12:54 -0700 (PDT)
Received: by wgyo15 with SMTP id o15so250486380wgy.2 for <v6ops@ietf.org>; Wed, 22 Apr 2015 08:12:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=PNbzHwkDAx5J3bfHMKMx6kMRzt018Xf8sWbUdQrESbY=; b=SjCf4u4n22rfsPc7U1OFbETe3kPfQJXuUIR6KPib6sAueFOg3P/GIR4KRUgimtsc4U 2/2uGr+JJvT/ayIvRn0rDvdMmGOAKnlYJSddIukJF4fVWZKsY+7VGpoCJxlG3iiynQz1 M68cf2I6qQHoi+eTIABic0hzWmxF6AWRpvHK9K4PCGKQ5T7sZymkd3B/6GiNkQr96EHk YN74Zalmx2HmL3+Oc/y/2wjc9N8xTqqZCW8/ZcWzsl/nrIllxIH5zyoCsn65/6vhCssO 5Xt8hxfpP/uJObQurRyOFqnlffMZZyJGiyx5RSJBwZ0rD7G5iLA4INKavbs1LwFRIeHc A4qQ==
MIME-Version: 1.0
X-Received: by 10.180.102.34 with SMTP id fl2mr6669121wib.73.1429715572832; Wed, 22 Apr 2015 08:12:52 -0700 (PDT)
Received: by 10.194.40.231 with HTTP; Wed, 22 Apr 2015 08:12:52 -0700 (PDT)
In-Reply-To: <20D5E991-C6E9-4679-8331-AF0D6BF60213@lists.zabbadoz.net>
References: <CAD6AjGT-hG-uvRQvRosrZtfrf0Nb8ne9jy=tD9oh=5zNM42Xsg@mail.gmail.com> <CAD6AjGTcKgK8W+VB1H5EQpHaYiKVYXqOz_2RS-w_CiTf9kL2CQ@mail.gmail.com> <CADhXe530+OVZrFZVaYh1-zoRDvJhUd0rf4sx6a2nO8SvKmm6zg@mail.gmail.com> <CAPi140PQ+TF0rED_bQPeS=Fj415qt0-zE2RdGnEL34PAzHyx6Q@mail.gmail.com> <CAD6AjGTjXAeMF6pw5MO2Jrf9B8LJ48D3m1YTVkdBe=_OHjtroQ@mail.gmail.com> <CADhXe51TCqU2eMP4LS3DooZxQDAPD95OVJDXbiU7qvuvKCMq+w@mail.gmail.com> <CAKD1Yr2=zc57+pOA9TFs+0azw0ZR1g67+08T=9eZPHjGXBvgFQ@mail.gmail.com> <CADhXe53T_30pj7xxwNs=mWEnd=do6oiq3KgN=U-gHLrLF-gG7Q@mail.gmail.com> <D1441574.4C168%wesley.george@twcable.com> <CAD6AjGQrzoBJrqQfKO0N8Ji=oJ-ZP6Sn88sXf=opJ6bYVmTDZg@mail.gmail.com> <552102B0.6070904@cernet.edu.cn> <35D97B17-8E83-43CF-ABEF-122572F1321A@eircom.net> <552369C8.5000801@cernet.edu.cn> <CADhXe51BDuPhc8wdKGmRiBfSnrz7PMtqYXaoDO+5cwLx_xW2tw@mail.gmail.com> <55290E26.8080500@cernet.edu.cn> <CADhXe50zz9EtNtifMh+tN9XT-jKCTJB=vsQ6uG515iddOo7f2Q@mail.gmail.com> <67A2A6E4-0603-4E84-8534-EA6C706C6D5D@lists.zabbadoz.net> <6536E263028723489CCD5B6821D4B21303E8CBAB@UK30S005EXS06.EEAD.EEINT.CO.UK> <0C3D10F1-B8AF-4097-91C6-D92CDDD5978D@nominum.com> <CAD6AjGR65jtZN4NV62p1XnUgoQRC+h=ELmsLcQaFTdrToMtwRA@mail.gmail.com> <20D5E991-C6E9-4679-8331-AF0D6BF60213@lists.zabbadoz.net>
Date: Wed, 22 Apr 2015 08:12:52 -0700
Message-ID: <CAD6AjGTULcAkZCQDQvh0UJ76uFH-uV9dQC6G+RP=utM1yKThag@mail.gmail.com>
From: Ca By <cb.list6@gmail.com>
To: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>
Content-Type: multipart/alternative; boundary="f46d04451809d9427005145198eb"
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/fu0xdQ331j8Y349Qo2KdoWuFRdA>
Cc: IPv6 Ops WG <v6ops@ietf.org>
Subject: Re: [v6ops] The need for local-ipv4 socket transition solutions -- NAT64/DNS64 remains insufficient
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: Wed, 22 Apr 2015 15:12:55 -0000

>
>
> > 2) Any solution that involves creating a negative customer experience
> (xyz website or abc app does not work), is a non-starter.  Please stop
> suggesting pain on paying customers, no network operator will do it. No
> appstore will do it (with teeth, in the near term)
>
> The way no major content provider wanted to turn IPv6 on.  Then they did
> for a day, and then they did it permanently.
>
>
I am fully open to the  next generation of iThingies  being IPv6-only
mandatory on all networks in the USA, this would achieve a lot in one
stroke.  The USA market is huge, and would shock the entire internet / web
/ apps into compliance "with this one weird trick."

The key is that a unified front is presented by all operators and enforced
by the owner of the ecosystem.  They can kill off IPv4 just like they
killed off Flash.  But, we cannot have free-riders that avoid the
requirement.

My honest opinion is that this alliance cannot be formed.  That said, mark
me as first in line for accepting this requirement if and only if all other
USA networks accept the requirement as well.


CB