Re: [v6ops] Apple and IPv6, a few clarifications

Ross Chandler <ross@eircom.net> Sat, 20 June 2015 11:31 UTC

Return-Path: <ross@eircom.net>
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 D9C211A1B17 for <v6ops@ietfa.amsl.com>; Sat, 20 Jun 2015 04:31:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.009
X-Spam-Level:
X-Spam-Status: No, score=-0.009 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_RP_MATCHES_RCVD=-0.01] 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 qpIAFvZaFtnK for <v6ops@ietfa.amsl.com>; Sat, 20 Jun 2015 04:31:13 -0700 (PDT)
Received: from mail19.svc.cra.dublin.eircom.net (mail19.svc.cra.dublin.eircom.net [159.134.118.218]) by ietfa.amsl.com (Postfix) with SMTP id A84F61A1B16 for <v6ops@ietf.org>; Sat, 20 Jun 2015 04:31:12 -0700 (PDT)
Received: (qmail 18857 messnum 383533 invoked from network[213.94.190.11/avas00.vendorsvc.cra.dublin.eircom.net]); 20 Jun 2015 11:31:10 -0000
Received: from avas00.vendorsvc.cra.dublin.eircom.net (213.94.190.11) by mail19.svc.cra.dublin.eircom.net (qp 18857) with SMTP; 20 Jun 2015 11:31:10 -0000
Received: from [192.168.1.1] ([86.43.35.194]) by avas00.vendorsvc.cra.dublin.eircom.net with Cloudmark Gateway id ibX71q00B4BK5ly01bXA00; Sat, 20 Jun 2015 12:31:10 +0100
Content-Type: multipart/alternative; boundary="Apple-Mail=_9F1C769E-03EA-49BA-A765-84BFF8FFBDCF"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
From: Ross Chandler <ross@eircom.net>
In-Reply-To: <E1C235B5-1421-4DAF-A2F3-F963982233DF@apple.com>
Date: Sat, 20 Jun 2015 12:31:03 +0100
Message-Id: <DD560968-25B8-476F-8793-3FAB5AA0649F@eircom.net>
References: <E1C235B5-1421-4DAF-A2F3-F963982233DF@apple.com>
To: David Schinazi <dschinazi@apple.com>
X-Mailer: Apple Mail (2.2098)
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/wEGc5E9lOkhtBOszJpbPb5Jn5S4>
Cc: v6ops@ietf.org, Vividh Siddha <vsiddha@apple.com>
Subject: Re: [v6ops] Apple and IPv6, a few clarifications
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: Sat, 20 Jun 2015 11:31:16 -0000

Hi David,

Thanks for working towards supporting the IPv6-only carrier case!

Not all visited operators can yet be relied on to allow dual-stack or even IPv6-only bearers.
Does it support fallback to an IPv4-only bearer when data roaming?

Also could you clarify what the position will be with VPN support?

Ross



> On 19 Jun 2015, at 22:46, David Schinazi <dschinazi@apple.com>; wrote:
> 
> Hi everyone,
> 
> I'd like to clarify a few points about Apple's IPv6 announcements during WWDC 2015.
> The video (streaming with Safari or download with all browsers) and slides of that talk
> are available at: https://developer.apple.com/videos/wwdc/2015/?id=719 <https://developer.apple.com/videos/wwdc/2015/?id=719>
> 
> *) Personal hotspot on iOS
> If your iPhone has dual-stack connectivity on its cellular network, the hotspot it creates
> will be dual-stack as well. The phone will share its prefix with Wi-Fi clients.
> 
> *) Internet Sharing on the Mac
> Today, regular internet sharing (from your ethernet to Wi-Fi for example) does not
> support IPv6 because of the limited use cases, and the lack of demand for it.
> 
> *) Internet Sharing on the Mac - NAT64 testing mode
> The NAT64 test mode was designed to help developers ensure that their app can still
> function with IPv6-only NAT64+DNS64 connectivity and communicate with their IPv4
> server, even if the developer does not have access to the IPv6 internet. That NAT64
> network does not have IPv6 connectivity to the global IPv6 internet. As such, the current
> version advertises addresses from 2001::/64 instead of ULAs to simulate real IPv6
> connectivity, as all IPv6 packets are terminated at the NAT64 server on the Mac.
> This implementation detail could change in the future.
> 
> *) Making IPv4 literals work on NAT64 networks when using high-level APIs
> Starting with this year's versions, if you use NSURLSession to connect to an IPv4
> literal on an IPv6-only NAT64-DNS64 network, the API will bump in a IPv6 literal
> synthesized using RFC 7050. Note that this will not happen when using sockets
> directly. We do not support under-the-sockets bump-in-API (RFC 3338) and we
> do not support 464XLAT.
> 
> *) Happy Eyeballs
> We've heard feedback on our Happy Eyeballs implementation and are investigating
> this topic.
> 
> Note that this reflects how these technologies work in the current versions of the
> 2015 betas, many of these details could change in future betas. Please keep in mind
> that these betas are previews and we welcome feedback on improving them.
> 
> Feel free to contact me if you have any questions, I will also attend IETF93.
> 
> Thanks,
> David Schinazi
> Apple CoreOS Networking Engineer
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops