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

Ca By <cb.list6@gmail.com> Mon, 23 March 2015 16: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 0B9831A911E for <v6ops@ietfa.amsl.com>; Mon, 23 Mar 2015 09:12:29 -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 v0CAgcFLX5yf for <v6ops@ietfa.amsl.com>; Mon, 23 Mar 2015 09:12:27 -0700 (PDT)
Received: from mail-we0-x232.google.com (mail-we0-x232.google.com [IPv6:2a00:1450:400c:c03::232]) (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 D73EB1A8A03 for <v6ops@ietf.org>; Mon, 23 Mar 2015 09:12:26 -0700 (PDT)
Received: by wegp1 with SMTP id p1so141859680weg.1 for <v6ops@ietf.org>; Mon, 23 Mar 2015 09:12:25 -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=NutygfsoBxja9qPgnpZKymdSpCS7N+dMAR4/Lh6ZyVI=; b=eVckGcakD8d+SCcmR7n2YvtVE3ljSbXlqQM6cRqHM6TAShK5JvK/9rXv0wAMGbl47f eXUMihNMS+x/VuUF7xSSmammk1KYb6kSFk0KSUhkH7JNk7mnjzl9tvMtT7JoELQYY8s6 hamBVp9Voc4lqNQC89dRK4QyykfF0FwpvqkcyuUK+FkKn6eJN5nW8K4IsM6PRJM00Ej9 b7pCpbXaJXepeAJlP08ADeUYpJqHuhNc4DQY4tGxP4D/2kzryk0HkWYi8hAT4QTndoUZ cfNDNuAcckopehXmL7g+4LTZdROrhKxCVXtMa7KZhxtMy3o2XT/3YBPtyf2QMH0TpsrB KYfg==
MIME-Version: 1.0
X-Received: by 10.180.82.169 with SMTP id j9mr10573419wiy.40.1427127145618; Mon, 23 Mar 2015 09:12:25 -0700 (PDT)
Received: by 10.194.93.164 with HTTP; Mon, 23 Mar 2015 09:12:25 -0700 (PDT)
In-Reply-To: <550F1F1F.3060703@cernet.edu.cn>
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>
Date: Mon, 23 Mar 2015 09:12:25 -0700
Message-ID: <CAD6AjGSxk-Hrf_NBOjpV-jvraG+xSA4p1j-AO+FQFcVGzuf1Lg@mail.gmail.com>
From: Ca By <cb.list6@gmail.com>
To: Xing Li <xing@cernet.edu.cn>
Content-Type: multipart/alternative; boundary="f46d0443041e90632b0511f6ee4b"
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/A-dn67Z8z2Iv1mFgE44T_GTe6UA>
Cc: IPv6 Ops WG <v6ops@ietf.org>, Tore Anderson <tore@fud.no>, Kossut Tomasz - Hurt <Tomasz.Kossut@orange.com>
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: Mon, 23 Mar 2015 16:12:29 -0000

On Sun, Mar 22, 2015 at 12:59 PM, Xing Li <xing@cernet.edu.cn> wrote:

>  Kossut Tomasz - Hurt 写道:
>
> CLAT is already in Windowsphone 8.1 - Pere & All thank you very much :)
>
> Idea of fancy "IPv6 bulding, house, cavern " is interesting but... I would suggest to enable IPv6 on key Microsoft content ie. Bing.com, live.com etc.
> "Internet is content"
> Cheers,
> tk
>
>
>  It will be great, if the new versions of all the operating systems can
> support both the CPE function of MAP-T (stateless NAT64 in the core) and
> CLAT for 464XLAT (stateful NAT64 in the core).
>
> Regards,
>
> xing
>
>

Xing,

I agree.  In mobile, Windows Phone and Android both support CLAT.

But there is one major mobile OS missing this feature.

Perhaps the IETF should give guidance via BCP that an IPv6-only solution
that supports IPv4 sockets be supported on hosts

CB

>  -----Original Message-----
> From: Tore Anderson [mailto:tore@fud.no <tore@fud.no>]
> Sent: Friday, March 20, 2015 1:42 PM
> To: Mikael Abrahamsson
> Cc: IPv6 Ops WG
> Subject: Re: [v6ops] The need for local-ipv4 socket transition solutions -- NAT64/DNS64 remains insufficient
>
> * Mikael Abrahamsson <swmike@swm.pp.se> <swmike@swm.pp.se>
>
>    Until then, the operating system will have to implement functions like
> 464XLAT to work around this situation. It's not good, but I'd say this
> is pretty typical transition problem.
>
>
>  Yep.
>
> Justine Vick from Microsoft held a very interesting presentation at the
> V6 World Congress on Wednesday about their plans to make one of their buildings IPv6-only. One of the things she had identified a need for was to have a CLAT in the desktop version of Windows. She had already established contact with the relevant teams to try to make that happen (I asked her to add the Windows Server folks to her CC list). Fingers crossed!
>
> Once we can translate IPv4 on our network borders/edges and keep the network itself IPv6-only we have way to proceed with the transition.
> Hopefully it will eventually dawn on the apps and web sites that use of literals or depending on AF_INET sockets isn't particularly smart if they want the optimal performance and functionality. (But if they don't it's no big deal either, they can get the best-effort service level.)
>
> Tore
>
>
> _______________________________________________
> v6ops mailing listv6ops@ietf.orghttps://www.ietf.org/mailman/listinfo/v6ops
>
>
>
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>
>