IETF Logo Mail Archive

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

Ca By <cb.list6@gmail.com> Thu, 26 March 2015 01:21 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 8C8E91ACDD5 for <v6ops@ietfa.amsl.com>; Wed, 25 Mar 2015 18:21:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.449
X-Spam-Level:
X-Spam-Status: No, score=-1.449 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, MIME_8BIT_HEADER=0.3, 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 0bIWAmfEc0ia for <v6ops@ietfa.amsl.com>; Wed, 25 Mar 2015 18:21:55 -0700 (PDT)
Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com [IPv6:2a00:1450:400c:c05::229]) (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 783241A1B76 for <v6ops@ietf.org>; Wed, 25 Mar 2015 18:21:54 -0700 (PDT)
Received: by wibbg6 with SMTP id bg6so46283965wib.0 for <v6ops@ietf.org>; Wed, 25 Mar 2015 18:21:53 -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=Ydsb6LDCe9L7WgSZThh1rbZUOX1BdSL/jx710SMtt50=; b=er66dnRFzg1h1zo7CuW8yG8yUJA58VFtxeyvy/9MWg4g1Ypd4TjRA1iTi6CZMhaINY LtWCzd6FbryMx4I/XVzbQ2HpuWkjh5CAhs3PR3AgV5RyoIKBMYEqMSiW4r1WRk0iw+0R mgmDwQGSunp0KHxLCB6hXUmG1CbkG6VBzzptyN/qsLhjl5nx9cYVbxyQa7kJvDGPgEeC ANDzEgMDRDkG+ESx77B7OHJjgctGhYzCRawRGbjSUfipq9ggnKwuWnJL7JMr9dVWOCkZ OZGFd9Q2xSIqcMFxJoO42YF1TrHEN7s0puRFcKLipR+/xpKe/H0WLqmmFvThBWao6//V Plhg==
MIME-Version: 1.0
X-Received: by 10.194.77.230 with SMTP id v6mr23662881wjw.25.1427332913279; Wed, 25 Mar 2015 18:21:53 -0700 (PDT)
Received: by 10.194.93.164 with HTTP; Wed, 25 Mar 2015 18:21:53 -0700 (PDT)
In-Reply-To: <CAPi140PQ+TF0rED_bQPeS=Fj415qt0-zE2RdGnEL34PAzHyx6Q@mail.gmail.com>
References: <CAD6AjGT-hG-uvRQvRosrZtfrf0Nb8ne9jy=tD9oh=5zNM42Xsg@mail.gmail.com> <alpine.DEB.2.02.1503200639340.20507@uplift.swm.pp.se> <20150320134204.32af9c67@echo.ms.redpill-linpro.com> <A0BB7AD89EA705449C486BDB5FDCBC7B28518DD8@OPE10MB06.tp.gk.corp.tepenet> <550F1F1F.3060703@cernet.edu.cn> <CAD6AjGSxk-Hrf_NBOjpV-jvraG+xSA4p1j-AO+FQFcVGzuf1Lg@mail.gmail.com> <CAKD1Yr3ywVy_00GYuw4Eq6cW_ZeL16bxpquaWWDMgSz44LagAg@mail.gmail.com> <CAD6AjGS-QMi+3oVGWDxnSMhEJH=VymwcF=PwKLdwFRxwHpp_-Q@mail.gmail.com> <CAKD1Yr3Fhnx3XaXouK57gupGOzodKGb0quhQxaf76NjWxSp3WA@mail.gmail.com> <CADhXe51MUB-czeCtpc63E0cHPpb_39Vv0o2Y57EVU2w_makP5Q@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>
Date: Wed, 25 Mar 2015 18:21:53 -0700
Message-ID: <CAD6AjGTjXAeMF6pw5MO2Jrf9B8LJ48D3m1YTVkdBe=_OHjtroQ@mail.gmail.com>
From: Ca By <cb.list6@gmail.com>
To: Andrew šŸ‘½ Yourtchenko <ayourtch@gmail.com>
Content-Type: multipart/alternative; boundary="047d7bfd028c45baad051226d7e7"
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/puys5EjGfOuULqBIGIkJt_1vHXI>
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: Thu, 26 Mar 2015 01:21:56 -0000

On Wednesday, March 25, 2015, Andrew šŸ‘½ Yourtchenko <ayourtch@gmail.com>
wrote:

> On 3/24/15, James Woodyatt <jhw@nestlabs.com <javascript:;>> wrote:
> > Cameron, Lorenzoā€”
>
>
> > Cameron writes, "IPv4 dependence is hurting the internet and allows for
> > middle-box proliferation."
> >
> > My reply: "I agree that IPv4 dependency is hurting the Internet, but I
> also
> > view 464XLAT as a scheme to prolong the viability of IPv4-only software.
>
> One of more reliable ways to drive the IPv4-only software sunset would
> be to emit a compiler warning whenever the static analyzer discovers
> an AF_INET socket being made.
>
> This warning would come with a corresponding developer page explaining
> why AF_INET is the new strcpy(), and give the correct examples of how
> to implement the dualstack networking correctly.
>
> But even absent the compiler magic, I would like you to consider the
> following logic:
>
> 1) One can say "dualstack" access network promotes IPv4-only apps
> stronger than "IPv6+CLAT" access network.
>
> 2) Universal availability of CLAT would allow the percentage of
> "IPv6+CLAT" networks
> to increase, because now a network can just flip from IPv4-only to
> IPv6-only+CLAT at little or no cost.
>
> 3) This would increase the overall share of IPv6 while decreasing the
> share of IPv4 *at the same time*
>
> 4) This will increase the attractiveness of using AF_INET6.
>
> What do you think ?
>
> --a
>
>

That would be a nice step.

But that is improbable  and does not solve the non-zero number of websites
in the Alexa 100 that have IPv4 literals in html / xml / js.

It also does not solve the sip / xmpp issue of being completely littered
with IPv4 referrals.

See first post in this thread for the problem

CB


> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org <javascript:;>
> https://www.ietf.org/mailman/listinfo/v6ops
>

v2.23.0 | Report a Bug | By Email