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

Alexandru Petrescu <alexandru.petrescu@gmail.com> Mon, 23 March 2015 17:55 UTC

Return-Path: <alexandru.petrescu@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 61AEA1AD063 for <v6ops@ietfa.amsl.com>; Mon, 23 Mar 2015 10:55:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level:
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham
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 XrMtSoFS95DY for <v6ops@ietfa.amsl.com>; Mon, 23 Mar 2015 10:55:09 -0700 (PDT)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C2C6F1AD05F for <v6ops@ietf.org>; Mon, 23 Mar 2015 10:55:07 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t2NHt5SX021275 for <v6ops@ietf.org>; Mon, 23 Mar 2015 18:55:05 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 21BC9202CFC for <v6ops@ietf.org>; Mon, 23 Mar 2015 18:55:46 +0100 (CET)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 1946D202C86 for <v6ops@ietf.org>; Mon, 23 Mar 2015 18:55:46 +0100 (CET)
Received: from [127.0.0.1] ([132.166.84.81]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t2NHt3dK027800 for <v6ops@ietf.org>; Mon, 23 Mar 2015 18:55:04 +0100
Message-ID: <55105376.7090307@gmail.com>
Date: Mon, 23 Mar 2015 18:55:02 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: v6ops@ietf.org
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>
In-Reply-To: <CAD6AjGSxk-Hrf_NBOjpV-jvraG+xSA4p1j-AO+FQFcVGzuf1Lg@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/H04Z9rkTLfRgR-QEd5PmwyYFe3I>
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 17:55:11 -0000

Le 23/03/2015 17:12, Ca By a écrit :
[...]
> Perhaps the IETF should give guidance via BCP that an IPv6-only
> solution that supports IPv4 sockets be supported on hosts

Updating RFC3542 "Advanced Socket API for IPv6"?

Alex

>
> CB
>
>> -----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>  <mailto: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 list
>> v6ops@ietf.org  <mailto:v6ops@ietf.org>
>> https://www.ietf.org/mailman/listinfo/v6ops
>>
>>
>>
>
>
> _______________________________________________ v6ops mailing list
> v6ops@ietf.org <mailto:v6ops@ietf.org>
> https://www.ietf.org/mailman/listinfo/v6ops
>
>
>
>
> _______________________________________________ v6ops mailing list
> v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops
>