IETF Logo Mail Archive

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

James Woodyatt <jhw@nestlabs.com> Thu, 26 March 2015 16:29 UTC

Return-Path: <jhw@nestlabs.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 BD3421A7D80 for <v6ops@ietfa.amsl.com>; Thu, 26 Mar 2015 09:29:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level:
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, 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 N8nIS5h9VyZl for <v6ops@ietfa.amsl.com>; Thu, 26 Mar 2015 09:29:10 -0700 (PDT)
Received: from mail-oi0-x235.google.com (mail-oi0-x235.google.com [IPv6:2607:f8b0:4003:c06::235]) (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 AAAC31A1B62 for <v6ops@ietf.org>; Thu, 26 Mar 2015 09:29:10 -0700 (PDT)
Received: by oifl3 with SMTP id l3so53853189oif.0 for <v6ops@ietf.org>; Thu, 26 Mar 2015 09:29:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nestlabs.com; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=+oWAF9Hff2dKCr2xxgZp7njtIaWxTf/2Gy7LWCWdPeE=; b=fo8iT98Dv8iVkqdlBqx6QFYSNcGDjjk0E1N2j4l3itGqiaiDVoraplFbGfoC24HCM0 UY91jUfeRHmJBHSvnRkIkN1y20/+QrAIounZ9dInOGLduuPVWkFPMDniC1RBPqiTZSIl HC3lrWEdNEY4qm2+q1yaxWx1eZpssjJ9uRES8=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=+oWAF9Hff2dKCr2xxgZp7njtIaWxTf/2Gy7LWCWdPeE=; b=WKpvVxvfv0dYLxMTCcwLbjJKJr2mdwnNjS+udBUa9zOHRByxmjXWmRbC5uE8/B5Tvl 8qdJUlqDdEZXR0FyvDRmbVpt8ghbOVjCyE7GYJbbvczrXba8R8ceJ4oncNyHsU3ekQac cE1L50FtTv7FsKtiii3wfCvv8OCpP0L44hvEdp3daSMtUZqNbfbyxB3t430PYUIOtAp9 f15EgaWP383PcQXKidmtBX/aAzUJq8J3glYQLu7l1SzcqXpCtXZ59DOxgYf7k6Jwq8cF nvLQN1fIitjCorc2lFgyFzO/c9DfwerHBCVNZTXEkin1fhIp4guXOiGeQA6kyK2o8EQf WZ1w==
X-Gm-Message-State: ALoCoQmGPKvWIAUz22miMZnUMJSu+1nXXOaGFcWC1jUKDi+AL8AHXZYH4p1ZVWcP2XDqyOAvWCk1
MIME-Version: 1.0
X-Received: by 10.202.231.85 with SMTP id e82mr12070428oih.104.1427387350211; Thu, 26 Mar 2015 09:29:10 -0700 (PDT)
Received: by 10.76.150.2 with HTTP; Thu, 26 Mar 2015 09:29:10 -0700 (PDT)
In-Reply-To: <CAD6AjGTjXAeMF6pw5MO2Jrf9B8LJ48D3m1YTVkdBe=_OHjtroQ@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> <CAD6AjGTjXAeMF6pw5MO2Jrf9B8LJ48D3m1YTVkdBe=_OHjtroQ@mail.gmail.com>
Date: Thu, 26 Mar 2015 11:29:10 -0500
Message-ID: <CADhXe51TCqU2eMP4LS3DooZxQDAPD95OVJDXbiU7qvuvKCMq+w@mail.gmail.com>
From: James Woodyatt <jhw@nestlabs.com>
To: Ca By <cb.list6@gmail.com>
Content-Type: multipart/alternative; boundary="001a11417b20f7788b0512338391"
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/5bYswt5Ld18mhwrKq9gOcVVamZ0>
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 16:29:11 -0000

On Wed, Mar 25, 2015 at 8:21 PM, Ca By <cb.list6@gmail.com> wrote:
>
>
> [...] 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. [...]
>

Neither does IPv6+CLAT, which simply admits defeat. The IPv4 literals will
never die, and IPv4 as a service will never be sunset. Yes, I recognize
that entirely shifting the burden of supporting IPv4 onto the operating
system developers, into the unforeseeable future, while the network
operators get a clean transition to IPv6-only, can seem like a "solution"
from certain bell-shaped perspectives, but there is still a world outside
that perspective where some of us are trying to make a living.


-- 
james woodyatt <jhw@nestlabs.com>
Nest Labs, Communications Engineering

v2.23.0 | Report a Bug | By Email