Re: [v6ops] Need ref to 3GPP spec for the use of DHCPv6 Prefix Delegation, e.g. for smartphone tethering
Gert Doering <gert@space.net> Mon, 07 October 2013 19:17 UTC
Return-Path: <gert@space.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 79BC711E8123 for <v6ops@ietfa.amsl.com>; Mon, 7 Oct 2013 12:17:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4TFuwYNjj3yc for <v6ops@ietfa.amsl.com>; Mon, 7 Oct 2013 12:17:47 -0700 (PDT)
Received: from mobil.space.net (mobil.space.net [IPv6:2001:608:2:81::67]) by ietfa.amsl.com (Postfix) with ESMTP id 34D5E11E8118 for <v6ops@ietf.org>; Mon, 7 Oct 2013 12:17:45 -0700 (PDT)
Received: from mobil.space.net (localhost [127.0.0.1]) by mobil.space.net (Postfix) with ESMTP id 3B2D060A1A for <v6ops@ietf.org>; Mon, 7 Oct 2013 21:17:43 +0200 (CEST)
X-SpaceNet-Relay: true
Received: from moebius3.space.net (moebius3.Space.Net [IPv6:2001:608:2:2::250]) by mobil.space.net (Postfix) with ESMTPS id 22B6460835 for <v6ops@ietf.org>; Mon, 7 Oct 2013 21:17:43 +0200 (CEST)
Received: (qmail 24863 invoked by uid 1007); 7 Oct 2013 21:17:43 +0200
Date: Mon, 07 Oct 2013 21:17:43 +0200
From: Gert Doering <gert@space.net>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Message-ID: <20131007191743.GY65295@Space.Net>
References: <B14A62A57AB87D45BB6DD7D9D2B78F0B2AB673CE@xmb-rcd-x06.cisco.com> <5252C5C2.5080706@gmail.com> <1808340F7EC362469DDFFB112B37E2FCD87724529F@SRVHKE02.rdm.cz> <5252DCEF.6030705@gmail.com> <1808340F7EC362469DDFFB112B37E2FCD87724530A@SRVHKE02.rdm.cz> <5252E66D.3080005@gmail.com> <20131007170914.GU65295@Space.Net> <5252EFE9.2090008@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="nXr/ldaYcWq08yut"
Content-Disposition: inline
In-Reply-To: <5252EFE9.2090008@gmail.com>
X-NCC-RegID: de.space
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
Subject: Re: [v6ops] Need ref to 3GPP spec for the use of DHCPv6 Prefix Delegation, e.g. for smartphone tethering
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
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: Mon, 07 Oct 2013 19:17:48 -0000
Hi, On Mon, Oct 07, 2013 at 07:31:21PM +0200, Alexandru Petrescu wrote: > Indeed it is implementation detail the vendor in question needs to solve. > > Just that solving it for DHCPv6 Prefix Delegation is going to be more > complex than just solving it for DHCPv6 for addresses, as the bbf > document presents it. Well, DHCPv6-for-addresses is about as complex if you do it via a relay, and the addresses do not come from a locally assigned pool. DHCPv6-for-addresses is much easier indeed if you only assign for a directly connected multiaccess network (cable, for example...) and do not have to deal with "ok, assignment has been done, now what addresses need to be stuffed into routing?" But still, I'm not sure what the context is to make a big deal out of it now? Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279
- [v6ops] Need ref to 3GPP spec for the use of DHCP… Alexandru Petrescu
- Re: [v6ops] Need ref to 3GPP spec for the use of … Mikael Abrahamsson
- Re: [v6ops] Need ref to 3GPP spec for the use of … Alexandru Petrescu
- Re: [v6ops] Need ref to 3GPP spec for the use of … Vízdal Aleš
- Re: [v6ops] Need ref to 3GPP spec for the use of … Alexandru Petrescu
- Re: [v6ops] Need ref to 3GPP spec for the use of … Rajiv Asati (rajiva)
- Re: [v6ops] Need ref to 3GPP spec for the use of … Alexandru Petrescu
- Re: [v6ops] Need ref to 3GPP spec for the use of … Vízdal Aleš
- Re: [v6ops] Need ref to 3GPP spec for the use of … Alexandru Petrescu
- Re: [v6ops] Need ref to 3GPP spec for the use of … Vízdal Aleš
- Re: [v6ops] Need ref to 3GPP spec for the use of … Alexandru Petrescu
- Re: [v6ops] Need ref to 3GPP spec for the use of … Gert Doering
- Re: [v6ops] Need ref to 3GPP spec for the use of … Alexandru Petrescu
- Re: [v6ops] Need ref to 3GPP spec for the use of … Gert Doering
- Re: [v6ops] Need ref to 3GPP spec for the use of … Vízdal Aleš
- Re: [v6ops] Need ref to 3GPP spec for the use of … Alexandru Petrescu
- Re: [v6ops] Need ref to 3GPP spec for the use of … Alexandru Petrescu
- Re: [v6ops] Need ref to 3GPP spec for the use of … Vízdal Aleš
- Re: [v6ops] Need ref to 3GPP spec for the use of … Alexandru Petrescu
- Re: [v6ops] Need ref to 3GPP spec for the use of … Vízdal Aleš
- [v6ops] Announcing draft-petrescu-relay-route-pd-… Alexandru Petrescu
- Re: [v6ops] Announcing draft-petrescu-relay-route… Ole Troan
- Re: [v6ops] Announcing draft-petrescu-relay-route… Leaf Yeh