IETF Logo Mail Archive

Re: [v6ops] Apple and IPv6 - new NAT64 address synthesis API

Ross Chandler <ross@eircom.net> Tue, 31 May 2016 10:08 UTC

Return-Path: <ross@eircom.net>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B68FD12D6FB for <v6ops@ietfa.amsl.com>; Tue, 31 May 2016 03:08:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.678
X-Spam-Level:
X-Spam-Status: No, score=-2.678 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_BL_SPAMCOP_NET=1.347, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-1.426] autolearn=ham autolearn_force=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 b27ybwOBvCgh for <v6ops@ietfa.amsl.com>; Tue, 31 May 2016 03:08:54 -0700 (PDT)
Received: from mta00.svc.cra.dublin.eircom.net (mta00.svc.cra.dublin.eircom.net [159.134.118.55]) by ietfa.amsl.com (Postfix) with SMTP id B201C12D6E4 for <v6ops@ietf.org>; Tue, 31 May 2016 03:08:53 -0700 (PDT)
Received: (qmail 21700 messnum 5910944 invoked from network[213.94.190.11/avas00.vendorsvc.cra.dublin.eircom.net]); 31 May 2016 10:08:51 -0000
Received: from avas00.vendorsvc.cra.dublin.eircom.net (HELO avas00) (213.94.190.11) by mta00.svc.cra.dublin.eircom.net (qp 21700) with SMTP; 31 May 2016 10:08:51 -0000
Received: from [159.134.250.224] ([159.134.250.224]) by Cloudmark Gateway with SMTP id 7gbTbTXrZT74P7gbTbhpJW; Tue, 31 May 2016 11:08:51 +0100
X-CNFS-Analysis: v=2.1 cv=daMgpSje c=1 sm=1 tr=0 a=r1X+M5CiF9LD/oHFr0z0dw==:117 a=r1X+M5CiF9LD/oHFr0z0dw==:17 a=L9H7d07YOLsA:10 a=9cW_t1CCXrUA:10 a=s5jvgZ67dGcA:10 a=t-IPkPogAAAA:8 a=48vgC7mUAAAA:8 a=jqGG--jNLTTdw9G43W4A:9 a=QEXdDO2ut3YA:10 a=0gXKrx3AAncA:10 a=TlSEhoGMJ-46eavboIYA:9 a=MsuQN856Ask_DTIC:21 a=_W_S_7VecoQA:10 a=TwOW_m0CY6OjrxjWeTv9:22 a=w1C3t2QeGrPiZgrLijVG:22
Content-Type: multipart/alternative; boundary="Apple-Mail=_DCCC0BFE-959A-425C-B024-EB00227DCA44"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Ross Chandler <ross@eircom.net>
In-Reply-To: <ED8066C1-76D8-4BCD-BA8F-5D5F9F4FEA21@apple.com>
Date: Tue, 31 May 2016 11:07:09 +0100
Message-Id: <4C80D4B8-0230-4E1F-A577-93E63C9D053E@eircom.net>
References: <ED8066C1-76D8-4BCD-BA8F-5D5F9F4FEA21@apple.com>
To: David Schinazi <dschinazi@apple.com>
X-Mailer: Apple Mail (2.3124)
X-CMAE-Envelope: MS4wfBEw6JEkrPdBDWgf1G1RC/XN5ZgFWxxa7AcmOf/OyNjU0VW4kbg+y6P89TFGe7RrJKeqE6MOAkfb0+9Kllc7dObKUKHlpQSC2sFjgWmWvHD+9rAl/2ur EcmF03LVCNd54C3xoTImez//2fOpVUMrE1gpAbWaRwEdrnL5mEtvdoAqZmTXNW497pPeW79QasFtpf+jrJ6195A71cJcj/Vh6gY=
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/3BwrlS3O24Eve5TjbY7_Z6TdTRw>
Cc: v6ops@ietf.org
Subject: Re: [v6ops] Apple and IPv6 - new NAT64 address synthesis API
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 31 May 2016 10:08:57 -0000

Hi David,

Can I ask what Apple’s intentions are for supporting tethered devices? In particular in the case where the iOS device only has IPv6-only PDP/PDN connections or a shared handset & tethering IPv6-only APN?
If the tethering interface of the iOS device can only provide 64share (RFC 7278) without support for IPv4 (e.g. via an RFC 6877 clat) then tethered devices will be restricted to those supporting IPv6-only connectivity using DNS64/NAT64.  

Thanks
Ross



> On 30 Oct 2015, at 04:51, David Schinazi <dschinazi@apple.com> wrote:
> 
> Hi everyone,
> 
> This week Apple released the first betas of iOS 9.2 and OS X 10.11.2.
> With it, we’ve introduced a new API to allow developers to synthesize NAT64 IPv6 addresses from IPv4 literals.
> We’re hoping that this will help more applications support NAT64 networks correctly while they work on getting server support for IPv6.
> As usual, we’d love feedback from the IETF community.
> 
> The API is very simple: we ask developers to always ``resolve'’ their IPv4 literals using getaddrinfo() by treating their IPv4 literal as a hostname string (e.g. ``192.0.2.1''), and we will take care of returning an IPv4 sockaddr on IPv4 networks and an appropriately synthesized NAT64 IPv6 sockaddr when the network supports IPv6, NAT64 and DNS64 but not IPv4. This is accomplished using RFC 6052 and RFC 7050.
> 
> Our target audience is application developers that need to communicate to an IPv4-only host for which they do not have a hostname. An example is a P2P service transmitting IPv4 literals over the wire. We do agree that the correct long-term solution is IPv6 support for all hosts and protocols but this is an effort to ease the transition. We believe this will help fix any remaining apps that do not support IPv6 before we start rejecting them from the App Store in early 2016.
> 
> More details and a code sample can be found on the Apple documentation website:
> 
> https://developer.apple.com/library/prerelease/tvos/documentation/NetworkingInternetWeb/Conceptual/NetworkingOverview/UnderstandingandPreparingfortheIPv6Transition/UnderstandingandPreparingfortheIPv6Transition.html#//apple_ref/doc/uid/TP40010220-CH213-DontLinkElementID_4 <https://developer.apple.com/library/prerelease/tvos/documentation/NetworkingInternetWeb/Conceptual/NetworkingOverview/UnderstandingandPreparingfortheIPv6Transition/UnderstandingandPreparingfortheIPv6Transition.html#//apple_ref/doc/uid/TP40010220-CH213-DontLinkElementID_4>
> 
> Thanks,
> David Schinazi
> Apple CoreOS Networking Engineer
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

v2.23.0 | Report a Bug | By Email