Re: [v6ops] Apple and IPv6, a few clarifications - ND proxy for bridging hotspots

Mikael Abrahamsson <swmike@swm.pp.se> Thu, 25 June 2015 09:29 UTC

Return-Path: <swmike@swm.pp.se>
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 4D9901B33E0 for <v6ops@ietfa.amsl.com>; Thu, 25 Jun 2015 02:29:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.661
X-Spam-Level:
X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_SE=0.35, 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 qvPTJ_ovFWnJ for <v6ops@ietfa.amsl.com>; Thu, 25 Jun 2015 02:29:01 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 343791B340F for <v6ops@ietf.org>; Thu, 25 Jun 2015 02:28:51 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id D16BAA1; Thu, 25 Jun 2015 11:28:48 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1435224528; bh=TvME6BLuiwGorfvj5AO5aHaha3anw3c0OuRuq6ztFak=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=nT+BTa0PHEJBaeM6/6L9CiN46rs8HEV5yjh9kw5NqPStZ3hTuFwWvcUdQQX+hJ/Qw Yv7sD9Rmac7auIISZZpCRxJnpmYFHTlg04/P+Dichzw4YZe3lG0j5yFIUwZN8AqVTo MpsGAZybGqJkVbUlbW75gjpYk/V6jesJBlunGXM8=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id CC3BD9F; Thu, 25 Jun 2015 11:28:48 +0200 (CEST)
Date: Thu, 25 Jun 2015 11:28:48 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
In-Reply-To: <558BC2FB.3020801@gmail.com>
Message-ID: <alpine.DEB.2.02.1506251121170.9487@uplift.swm.pp.se>
References: <E1C235B5-1421-4DAF-A2F3-F963982233DF@apple.com> <1599CF94-9B35-4858-AD52-6FADC8F25671@apple.com> <558ABAC3.4010802@gmail.com> <20150624151015.GN67883@Space.Net> <558ACC2F.7060509@gmail.com> <20150624161858.GP67883@Space.Net> <20150624234129.47252313E1E5@rock.dv.isc.org> <20150625071335.GQ67883@Space.Net> <558BC2FB.3020801@gmail.com>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/WtQksdU-fzTvhsis6Q9xEkIFYbw>
Cc: v6ops@ietf.org
Subject: Re: [v6ops] Apple and IPv6, a few clarifications - ND proxy for bridging hotspots
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: Thu, 25 Jun 2015 09:29:03 -0000

On Thu, 25 Jun 2015, Alexandru Petrescu wrote:

> After reading Mikael's email pointing to a 3gpp spec of late 2014
> mandating DHCPv6-PD to both UE and core network - I must say I am
> optimistic about the arrival of DHCPv6-PD to cellular network operators.
>
> Currently, some cellular networks already offer DHCPv6 together with
> SLAAC.  Technically that DHCPv6 is extremely simple to upgrade to DHCPv6-PD.
>
> My question is when?
>
> I can speculate it will be in late 2016.  Because 4G was in specs 2
> years before trial deployments.

To repeat myself:

DHCPv6-PD requirement didn't appear in 2014.

http://www.etsi.org/deliver/etsi_ts/123400_123499/123401/10.03.00_60/ts_123401v100300p.pdf 
from 2011-MARCH contains prefix delegation, and since it's not available 
in release 9, it seems this is indeed a LTE release 10 feature that is 
more than 4 years old, and still there isn't widespread implementation of 
it that I am aware of.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se