IETF Logo Mail Archive

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

Kossut Tomasz - Hurt <Tomasz.Kossut@orange.com> Fri, 20 March 2015 16:01 UTC

Return-Path: <Tomasz.Kossut@orange.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 CC76B1ACD5E for <v6ops@ietfa.amsl.com>; Fri, 20 Mar 2015 09:01:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.485
X-Spam-Level:
X-Spam-Status: No, score=0.485 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HELO_EQ_PL=1.135, HOST_EQ_PL=1.95, RCVD_IN_DNSWL_LOW=-0.7, 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 aWU0S-D2w5YA for <v6ops@ietfa.amsl.com>; Fri, 20 Mar 2015 09:01:20 -0700 (PDT)
Received: from mailin.tpsa.pl (mailout.tpsa.pl [212.160.172.10]) (using TLSv1 with cipher DES-CBC3-SHA (112/168 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 490E11ACD54 for <v6ops@ietf.org>; Fri, 20 Mar 2015 09:01:20 -0700 (PDT)
Received: from 10.236.62.155 (EHLO OPE10HT07.tp.gk.corp.tepenet) ([10.236.62.155]) by mailin.tpsa.pl (MOS 4.4.2a-FCS FastPath queued) with ESMTP id DSB84377; Fri, 20 Mar 2015 17:01:15 +0100 (CET)
From: Kossut Tomasz - Hurt <Tomasz.Kossut@orange.com>
To: Tore Anderson <tore@fud.no>, Mikael Abrahamsson <swmike@swm.pp.se>
Thread-Topic: [v6ops] The need for local-ipv4 socket transition solutions -- NAT64/DNS64 remains insufficient
Thread-Index: AQHQYw3SjkKiJBBaPk2i3LxXcr3q5Z0lanag
Date: Fri, 20 Mar 2015 16:01:08 +0000
Message-ID: <A0BB7AD89EA705449C486BDB5FDCBC7B28518DD8@OPE10MB06.tp.gk.corp.tepenet>
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>
In-Reply-To: <20150320134204.32af9c67@echo.ms.redpill-linpro.com>
Accept-Language: pl-PL, en-US
Content-Language: pl-PL
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [126.20.50.1]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Junkmail-Premium-Raw: score=8/50, refid=2.7.2:2015.3.20.145720:17:8.129, ip=, rules=__HAS_FROM, FROM_NAME_PHRASE, __TO_MALFORMED_2, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __IMS_MSGID, __HAS_MSGID, __SANE_MSGID, __REFERENCES, __IN_REP_TO, WEBMAIL_XOIP, __HAS_XOIP, __CT, __CT_TEXT_PLAIN, __CTE, __MIME_VERSION, WEBMAIL_X_IP_HDR, __ANY_URI, __URI_NO_WWW, __URI_NO_PATH, __INT_PROD_COMP, __SUBJ_ALPHA_NEGATE, SUPERLONG_LINE, __FORWARDED_MSG, BODYTEXTP_SIZE_3000_LESS, BODY_SIZE_1600_1699, __MIME_TEXT_ONLY, __URI_NS, HTML_00_01, HTML_00_10, BODY_SIZE_5000_LESS, WEBMAIL_SOURCE, BODY_SIZE_2000_LESS, BODY_SIZE_7000_LESS, REFERENCES
X-Junkmail-Status: score=10/50, host=mailin.tpsa.pl
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0C0202.550C444B.01A1, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2012-12-31 09:39:00, dmn=2013-03-21 17:37:32, mode=multiengine
X-Junkmail-IWF: false
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A0C0202.550C444B.01A1, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2012-12-31 09:39:00, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 2eca9daec65e3c3c3a1d95939e6b4202
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/oimDZGEGQAGAG6RtVAB2BMVeK04>
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: Fri, 20 Mar 2015 16:01:23 -0000

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 


-----Original Message-----
From: Tore Anderson [mailto: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>

> 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

v2.23.0 | Report a Bug | By Email