Re: [mif] Comments on draft-mouton-mif-dhcpv6-drlo-00

<teemu.savolainen@nokia.com> Mon, 19 September 2011 08:31 UTC

Return-Path: <teemu.savolainen@nokia.com>
X-Original-To: mif@ietfa.amsl.com
Delivered-To: mif@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2120421F8B36 for <mif@ietfa.amsl.com>; Mon, 19 Sep 2011 01:31:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.161
X-Spam-Level:
X-Spam-Status: No, score=-3.161 tagged_above=-999 required=5 tests=[AWL=0.438, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 nbH5zI2w2XOd for <mif@ietfa.amsl.com>; Mon, 19 Sep 2011 01:31:04 -0700 (PDT)
Received: from mgw-da01.nokia.com (smtp.nokia.com [147.243.128.24]) by ietfa.amsl.com (Postfix) with ESMTP id 60C4421F8A71 for <mif@ietf.org>; Mon, 19 Sep 2011 01:31:04 -0700 (PDT)
Received: from vaebh105.NOE.Nokia.com (vaebh105.europe.nokia.com [10.160.244.31]) by mgw-da01.nokia.com (Switch-3.4.4/Switch-3.4.3) with ESMTP id p8J8X17w012815; Mon, 19 Sep 2011 11:33:24 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.6]) by vaebh105.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Mon, 19 Sep 2011 11:33:13 +0300
Received: from 008-AM1MMR1-002.mgdnok.nokia.com (65.54.30.57) by NOK-am1MHUB-02.mgdnok.nokia.com (65.54.30.6) with Microsoft SMTP Server (TLS) id 8.2.255.0; Mon, 19 Sep 2011 10:33:13 +0200
Received: from 008-AM1MPN1-037.mgdnok.nokia.com ([169.254.7.199]) by 008-AM1MMR1-002.mgdnok.nokia.com ([65.54.30.57]) with mapi id 14.01.0339.002; Mon, 19 Sep 2011 10:33:12 +0200
From: <teemu.savolainen@nokia.com>
To: <alexandru.petrescu@gmail.com>
Thread-Topic: [mif] Comments on draft-mouton-mif-dhcpv6-drlo-00
Thread-Index: AQHMclXvmeatSbe770ilB6P1NUlbCpVL1DV4///urQCAAJ4CcIAAFp+AgAAwtvCABON7gIAC19rw
Date: Mon, 19 Sep 2011 08:33:12 +0000
Message-ID: <916CE6CF87173740BC8A2CE44309696202F2B407@008-AM1MPN1-037.mgdnok.nokia.com>
References: <3CF88B99A9ED504197498BC6F6F04B81040FBDA9@XMB-BGL-41E.cisco.com> <4E6E7A72.9030208@gmail.com> <4E6EAFC2.5060906@gmail.com> <4E6EDEA8.3080108@gmail.com> <CFDF82EE-052B-4A61-AE1B-152337822B6E@nominum.com> <4E6F825C.3080303@gmail.com> <3D0B3661-8A8F-4BB2-A8EF-25007BEAF66C@nominum.com> <4E6F923F.7090304@gmail.com> <7061CEB8-8084-41D5-B31E-9F8E3B6C7091@nominum.com> <4E6F9B91.7010503@gmail.com> <B987CA14-569C-428C-8D8A-C97A0E42EF48@nominum.com> <4E6FA64E.7020801@gmail.com> <82337D11-0A39-4A10-AA0E-1E81B09DBA4F@nominum.com> <4E6FACF6.5000007@viagenie.ca>, <4E6FC0AE.5000108@gmail.com> <916CE6CF87173740BC8A2CE4430969620257327E@008-AM1MPN1-032.mgdnok.nokia.com> <4E6FD930.7040401@gmail.com> <916CE6CF87173740BC8A2CE443096962025734A7@008-AM1MPN1-032.mgdnok.nokia.com> <4E7070B5.6080900@gmail.com> <916CE6CF87173740BC8A2CE44309696202573B89@008-AM1MPN1-032.mgdnok.nokia.com> <4E74B363.7000402@gmail.com>
In-Reply-To: <4E74B363.7000402@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-tituslabs-classifications-30: TLPropertyRoot=Nokia; Confidentiality=Company Confidential; Project=None;
x-titus-version: 3.3.8.1
x-headerinfofordlp: None
x-tituslabs-classificationhash-30: VgNFIFU9Hx+/nZJb9Kg7IuZuBXX/gTPnV8RRCmXgbNBLv+s+z8dze93E2y5N3eQswSwwwxgghs89TU1NiT1JcwoYrWJF1mZc/NrOJDhIyVOXH9EPAg712fNqHrpoDEsvuRlOS1hSiwqJBl/y+vrUMbNcSOiAMcMwyx351Sa6Z/IFSlHIhsBMoR40FyewYK3KCsi7Yxw68v+kP9DvNAmUZxPlsGYqXedFJIa5k15Bm0XdsxKvBnVcmuxqzTj4b4GDU4EfHLLHaH9VmYnqNFtQ0A==
x-originating-ip: [10.162.60.55]
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=SHA1; boundary="----=_NextPart_000_0023_01CC76BF.E9913320"
MIME-Version: 1.0
X-OriginalArrivalTime: 19 Sep 2011 08:33:13.0869 (UTC) FILETIME=[C59903D0:01CC76A6]
X-Nokia-AV: Clean
Cc: mif@ietf.org
Subject: Re: [mif] Comments on draft-mouton-mif-dhcpv6-drlo-00
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mif>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Sep 2011 08:31:05 -0000

> > Additionally, in rel-10, also UE connected to PDN GW can use DHCPv6
> > Prefix Delegation to get prefixes for advertisement on local area
> > networks (such as "MiFi hotspot").
> 
> Hmmm... but I don't understand how a UE can be a Requesting Router at the
> same time as the PDN-GW being a RR.

PDG-GW can use DHCPv6 PD to ask for a pool of addresses it uses for UEs (or
it may have a locally provisioned pool), and from where it can further
delegate prefixes downstream (in DR role) to those UEs that implement RR
function.

> If the MiFi hotspot router requests a /64 prefix from a PDN-GW which has
> only /64 prefixes then the number of routing entries in the PDN-GW may
> double.

Yes! That is one big reason for existence of draft-ietf-dhc-pd-exclude-03
that optimizes routing entries in these kinds of scenarios on 3GPP accesses,
but also elsewhere - there was interest from fixed side for this as well.
The exclude option optimizes routing entries on gateway but with a
deployment-scenario/network setup dependent possible tradeoff of increased
address space usage.

> Second, if the MiFi hotspot router is a RR then I suppose the PDN-GW must
> be a delegating router for it (DR); the spec doesn't say, it says just
it's a RR. (if
> I read correctly).

Did you look at the 23.401 V10.4.0 (the latest version) section 5.3.1.2.6
that says it clearly: "The PDN GW acts as the DHCP server and fulfils the
role of a "Delegating Router" according to RFC 3633".

Best regards,

	Teemu