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

David Schinazi <dschinazi@apple.com> Fri, 26 June 2015 18:40 UTC

Return-Path: <dschinazi@apple.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 465031A92E0 for <v6ops@ietfa.amsl.com>; Fri, 26 Jun 2015 11:40:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level:
X-Spam-Status: No, score=-1.4 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, 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 Q2v8P8q8gP4X for <v6ops@ietfa.amsl.com>; Fri, 26 Jun 2015 11:40:36 -0700 (PDT)
Received: from mail-in4.apple.com (mail-out4.apple.com [17.151.62.26]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 66B761A90E2 for <v6ops@ietf.org>; Fri, 26 Jun 2015 11:40:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=apple.com; s=mailout2048s; c=relaxed/simple; q=dns/txt; i=@apple.com; t=1435344036; x=2299257636; h=From:Sender:Reply-To:Subject:Date:Message-id:To:Cc:MIME-version:Content-type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-reply-to:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=FXvqJhaT4sTZU86XRnzZb4IhWFYxW6brUY8gPnqdNww=; b=dKUBr41kuZCcZ556VRsvk5+d24f13kmqfc5hgG/QmqlcAx/uVIRJaoueSfw09MqW D0oOsdT/h0sGlfQAA3lqctMX+glr0i8r3px04iIDkI4okwz9Tt7iAsL8bLuo3D1n dDemqVZYZs3qh3LjsdXMVAZvPDbpXZume8+AbIf95gt+HG293PRK4kst8apd8r6+ 5A9J06JmsmgM4WWoogaxheXL6hF/Z+IYpXedYXMyX7ctdKXHk1cQ8GTGJeWW8hRb wAERCXKsuWngdU6fnkD/6lmpBClw+laN0u9fa+bAvmcfLVeNNLVob5FgFkmRvyEX 1WPLlvXiijgYx6DsTZ/7ig==;
Received: from relay3.apple.com (relay3.apple.com [17.128.113.83]) by mail-in4.apple.com (Apple Secure Mail Relay) with SMTP id 53.CB.18963.3AC9D855; Fri, 26 Jun 2015 11:40:35 -0700 (PDT)
X-AuditID: 11973e12-f79456d000004a13-6d-558d9ca35ae2
Received: from jimbu (jimbu.apple.com [17.151.62.37]) (using TLS with cipher DES-CBC3-SHA (168/168 bits)) (Client did not present a certificate) by relay3.apple.com (Apple SCV relay) with SMTP id 1D.E4.32123.3AC9D855; Fri, 26 Jun 2015 11:40:35 -0700 (PDT)
Received: from [17.153.52.250] by jimbu.apple.com (Oracle Communications Messaging Server 7.0.5.30.0 64bit (built Oct 22 2013)) with ESMTPSA id <0NQK00CRGEJN8050@jimbu.apple.com> for v6ops@ietf.org; Fri, 26 Jun 2015 11:40:35 -0700 (PDT)
Content-type: multipart/alternative; boundary="Apple-Mail=_3F1A2525-B61C-4A04-9F9A-DF2F92347372"
MIME-version: 1.0 (Mac OS X Mail 8.2 \(2102\))
From: David Schinazi <dschinazi@apple.com>
In-reply-to: <6536E263028723489CCD5B6821D4B21303ECB135@UK30S005EXS06.EEAD.EEINT.CO.UK>
Date: Fri, 26 Jun 2015 11:40:34 -0700
Message-id: <30B46C6D-5676-4E12-88FE-D6EBFA0D6793@apple.com>
References: <E1C235B5-1421-4DAF-A2F3-F963982233DF@apple.com> <1599CF94-9B35-4858-AD52-6FADC8F25671@apple.com> <6536E263028723489CCD5B6821D4B21303ECB135@UK30S005EXS06.EEAD.EEINT.CO.UK>
To: "Heatley, Nick" <nick.heatley@ee.co.uk>
X-Mailer: Apple Mail (2.2102)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrGLMWRmVeSWpSXmKPExsUi2FAYrLt4Tm+owa0vNhanj+1ldmD0WLLk J1MAYxSXTUpqTmZZapG+XQJXxrXzFQW/0iquzXzC3sDYEdnFyMkhIWAicW5zAzOELSZx4d56 ti5GLg4hgb2MEg+ajzHBFP1te8QKkWhlkrjy4DEbSEJI4BOjRP9SVxCbWSBJomvLUaAGDg5e AT2JR52yIGFhAUuJf2tOM4OE2QS0JA6sMQIJcwpESFzZ948VxGYRUJX4eWguO8QUE4ndnzrA pvMK2Eg8v/eTEWLtbkaJkzcngSVEBLQlmuf8YoS4TVZi65tWqDs72CS2nheZwCg0C8lFsxAu gghrSyxb+JoZwtaU2N+9nAVTXEOi89tE1gWMbKsYhXITM3N0M/NM9BILCnJS9ZLzczcxggJ+ up3QDsZTq6wOMQpwMCrx8Do094QKsSaWFVfmHmKU5mBREue9Vd8bKiSQnliSmp2aWpBaFF9U mpNafIiRiYNTqoGRaWt4wfdDqYXH4p/syY1Tm98fGW2ebLLJTWnVgWUlPyr444ye2PC9TNC6 3vqoY1q2R6TR/5QZ61z1lcL/u9m7bjl8JWm6KfelPZWP215N+1cgNtv7aVp4rr6klfDt5Yr/ Cpcvm7S0eMPCpuIKn8VR6WtLJvhcCX71LFS/VeFKT4PSnHvn985UYinOSDTUYi4qTgQAE584 bFkCAAA=
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrFLMWRmVeSWpSXmKPExsUiON1OVXfxnN5Qgx1nLC1OH9vL7MDosWTJ T6YAxigum5TUnMyy1CJ9uwSujGvnKwp+pVVcm/mEvYGxI7KLkZNDQsBE4m/bI1YIW0ziwr31 bF2MXBxCAq1MElcePGYDSQgJfGKU6F/qCmIzCyRJdG05ytTFyMHBK6An8ahTFiQsLGAp8W/N aWaQMJuAlsSBNUYgYU6BCIkr+/6BjWcRUJX4eWguO8QUE4ndnzrApvMK2Eg8v/eTEWLtbkaJ kzcngSVEBLQlmuf8YoS4TVZi65tWpgmM/LOQXDEL4QqIsLbEsoWvmSFsTYn93ctZMMU1JDq/ TWRdwMi2ilGgKDUnsdJYL7GgICdVLzk/dxMjKEQbCoN3MP5ZZnWIUYCDUYmHd0ZrT6gQa2JZ cWXuIUYJDmYlEV7Ort5QId6UxMqq1KL8+KLSnNTiQ4zSHCxK4rwLlreECgmkJ5akZqemFqQW wWSZODilGhi5+64wy91s++K5ZsWBr+xeUSXnI6ezb/p0UXVbm8/UkPCD+2YWpjEm21Rm1gpv kEvu2hfmzNpx+SlH5m2L7bODd7ZMsZAQvVS9Z2rZ6/OeXJc+7326KOHOpnTfhIQAxqWZce8l uQz/nWO9LM724PCfHg4pj8M1l2o1+e7sNov6YMhv+XP+cg4lluKMREMt5qLiRADnzdd2TQIA AA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/uNAqkkjD-F4yHZRX7jCr4jWzkOs>
Cc: Vividh Siddha <vividh@apple.com>, v6ops@ietf.org
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: <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: Fri, 26 Jun 2015 18:40:38 -0000

Nick,

Sorry about the confusion, "bringing up IPv4 specifically" was speculation on my end.
I did mean a separate APN that could be used for hotspots and/or systems that do not support IPv6.
To support an IPv4-only device on a personal hotspot from an IPv6-only iOS handset, we would need some
type of translation from v4 to v6 on the iOS device. We currently do not provide that.

Thanks,
David


> On Jun 24, 2015, at 00:58, Heatley, Nick <nick.heatley@ee.co.uk>; wrote:
> 
>  
>  
> From: v6ops [mailto:v6ops-bounces@ietf.org <mailto:v6ops-bounces@ietf.org>] On Behalf Of David Schinazi
> Sent: 24 June 2015 08:16
> To: v6ops@ietf.org <mailto:v6ops@ietf.org>
> Cc: Vividh Siddha
> Subject: Re: [v6ops] Apple and IPv6, a few clarifications
>  
> Hi again,
> 
> First off, thanks everyone for the feedback and advice!
> Here's an attempt at answering the questions that arose since my last post.
> 
> *) Personal hotspot on iOS
> Currently the hotspot shares whatever address families it gets from the cellular network.
> The current implementation broadcasts an IPv6-only network if the cellular network is of that type,
> but I could imagine carriers bringing up IPv4 specifically when using this feature. Our custom version
> of prefix sharing is described in more detail here:
> https://opensource.apple.com/source/xnu/xnu-2782.1.97/bsd/netinet6/nd6_prproxy.c <https://opensource.apple.com/source/xnu/xnu-2782.1.97/bsd/netinet6/nd6_prproxy.c>
> It supports creating multiple hotspots at the same time, such as Wi-FI and Bluetooth and bridges them.
> 
> [Heatley, Nick] Thanks for sharing the information, David.
> When you say you imagine carries bringing up IPv4 specifically for personal hotspot, not sure what you mean - do you mean a parallel, dedicated “hotspot APN”?
> Many carriers across the globe, for their own individual business reasons, have a common APN approach for the mass consumer market, but nevertheless desire this common APN to go IPv6-only.
>  
> So I am nervous about how to support *any* device on a personal hotspot from an IPv6-only iOS handset in this way, do you have any more details on your intentions here?
> Thanks for the discussion. Nick
>  
> 
> 
> 
> 
>  
> NOTICE AND DISCLAIMER
> This e-mail (including any attachments) is intended for the above-named person(s).  If you are not the intended recipient, notify the sender immediately, delete this email from your system and do not disclose or use for any purpose.  
>  
> We may monitor all incoming and outgoing emails in line with current legislation. We have taken steps to ensure that this email and attachments are free from any virus, but it remains your responsibility to ensure that viruses do not adversely affect you. 
> 
> EE Limited
> Registered in England and Wales
> Company Registered Number: 02382161
> Registered Office Address: Trident Place, Mosquito Way, Hatfield, Hertfordshire, AL10 9BW
> 
>