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

Owen DeLong <owen@delong.com> Mon, 22 June 2015 17:06 UTC

Return-Path: <owen@delong.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 032551B307D for <v6ops@ietfa.amsl.com>; Mon, 22 Jun 2015 10:06:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.589
X-Spam-Level: *
X-Spam-Status: No, score=1.589 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_ADSP_ALL=0.8, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 QzPJTuTHCtZc for <v6ops@ietfa.amsl.com>; Mon, 22 Jun 2015 10:06:33 -0700 (PDT)
Received: from owen.delong.com (owen.delong.com [IPv6:2620:0:930::200:2]) by ietfa.amsl.com (Postfix) with ESMTP id 2C2501A1C03 for <v6ops@ietf.org>; Mon, 22 Jun 2015 10:06:33 -0700 (PDT)
Received: from [IPv6:2620::930:0:ae87:a3ff:fe29:7192] ([IPv6:2620:0:930:0:ae87:a3ff:fe29:7192]) (authenticated bits=0) by owen.delong.com (8.14.4/8.14.2) with ESMTP id t5MH6N4P002092 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 22 Jun 2015 10:06:24 -0700
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
From: Owen DeLong <owen@delong.com>
In-Reply-To: <75B6FA9F576969419E42BECB86CB1B89168A9E9E@xmb-rcd-x06.cisco.com>
Date: Mon, 22 Jun 2015 10:06:23 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <18D137E7-FC14-4547-A944-34099BC3C4C8@delong.com>
References: <E1C235B5-1421-4DAF-A2F3-F963982233DF@apple.com> <5587EFDD.6030807@gmail.com> <alpine.DEB.2.02.1506221415100.9487@uplift.swm.pp.se> <AB88C7C2-A367-4233-9214-A210E47F1507@eircom.net> <75B6FA9F576969419E42BECB86CB1B89168A9E06@xmb-rcd-x06.cisco.com> <0E9A1FA2-6C5E-4526-8BDF-76AC5D9F3B3E@eircom.net> <75B6FA9F576969419E42BECB86CB1B89168A9E9E@xmb-rcd-x06.cisco.com>
To: "Hemant Singh (shemant)" <shemant@cisco.com>
X-Mailer: Apple Mail (2.2098)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.3 (owen.delong.com [IPv6:2620:0:930::200:2]); Mon, 22 Jun 2015 10:06:24 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/fbWsMN85ybZURIfvdnsBf6y5S1w>
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
Subject: Re: [v6ops] Apple and IPv6, a few clarifications - 64share
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: Mon, 22 Jun 2015 17:06:34 -0000

> On Jun 22, 2015, at 07:47 , Hemant Singh (shemant) <shemant@cisco.com> wrote:
> 
> -----Original Message-----
> From: Ross Chandler [mailto:ross@eircom.net] 
> Sent: Monday, June 22, 2015 10:28 AM
> To: Hemant Singh (shemant)
> Cc: Mikael Abrahamsson; v6ops@ietf.org
> Subject: Re: [v6ops] Apple and IPv6, a few clarifications - 64share
> 
>> Are you arguing for DHCPv6-PD prior to the stopgap of L2 bridging and 64share? I’ve seen this implemented in UEs.
> 
> It's up to the provider to deploy what they choose to deploy.   I am only discussing pitfalls with each tech being considered for deployment.  I do have a preference for DHCPv6 PD and routing.  The reason is DHCPv6 PD and IPv6 CE router can support all of wifi, Bluetooth, etc.  Additionally, devices such as Apple TV in the home can be assigned ULAs which the router on the phone will never forward to the WAN - thus no video from the home leaks to the cellular network.  I will never consider a technology that leaks a home's  TV video to the cellular network.  

Why not? I’m pretty annoyed that I have to use the HTTP interface and wifi hotspot on my phone rather than the iOS App to pull video off of my TiVO when I’m not home.

Mostly this is because TiVO has their head up their ass about thinking:

	1.	All homes have one and only one broadcast domain.
	2.	TiVO won’t use the cellular interface on an iOS device. (It will connect over wifi just fine).

Sometimes I use one iOS device in hotspot mode to watch video on another which thinks it’s on wifi but is actually using the cellular network from the first iOS device.

All of these limitations on how I use the cellular bandwidth I pay for are:
	1)	Silly
	2)	Annoying
	3)	Unnecessary

Owen