IETF Logo Mail Archive

Re: [homenet] DHCP PD

Ole Troan <otroan@employees.org> Wed, 05 February 2014 08:04 UTC

Return-Path: <otroan@employees.org>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60CE71A00A7 for <homenet@ietfa.amsl.com>; Wed, 5 Feb 2014 00:04:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level:
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_SOFTFAIL=0.665] 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 THj-t3KpEn99 for <homenet@ietfa.amsl.com>; Wed, 5 Feb 2014 00:04:54 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) by ietfa.amsl.com (Postfix) with ESMTP id B304C1A0063 for <homenet@ietf.org>; Wed, 5 Feb 2014 00:04:53 -0800 (PST)
X-Files: signature.asc : 496
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgkFAAjw8VKQ/khM/2dsb2JhbABZgww4vySBCBZ0giUBAQQBeRALDjhXBi6HYggNzj0XjnUHgySBFASQP4kekG+DLjs
X-IronPort-AV: E=Sophos; i="4.95,785,1384300800"; d="asc'?scan'208"; a="4677789"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by aer-iport-1.cisco.com with ESMTP; 05 Feb 2014 08:04:52 +0000
Received: from dhcp-10-61-101-122.cisco.com (dhcp-10-61-101-122.cisco.com [10.61.101.122]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s1584oae029155 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 5 Feb 2014 08:04:51 GMT
Content-Type: multipart/signed; boundary="Apple-Mail=_5B9AA376-DBE6-4BAC-BBBB-AFA285468801"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Ole Troan <otroan@employees.org>
In-Reply-To: <E2FC2ECC-D5C7-448D-A2CA-7FB32A4818F6@fugue.com>
Date: Wed, 05 Feb 2014 09:04:50 +0100
Message-Id: <86B24348-21AE-43A8-BF16-555EB566BE72@employees.org>
References: <C0F2DB0D-176D-4FDD-BC6A-8249DFDDF6D7@employees.org> <52EA3032.3050703@gmail.com> <BA48563E-9E2E-4865-A85C-3AFA56DABF0C@employees.org> <52EA3361.1010501@gmail.com> <2EB6289E-C7FD-481F-99F9-E35730245943@employees.org> <52EA442D.3020707@gmail.com> <DB3D5008-D2DB-4CEC-9C80-DD00429F58FC@employees.org> <52EA47AA.90302@gmail.com> <1FE00515-A7AD-4C48-A7F2-63BA8696D818@darou.fr> <52EA4BB1.9010607@gmail.com> <2922CC94-540D-4215-899B-4722BD1C5EBC@employees.org> <52EF90BD.4070701@gmail.com> <18C8BE29C547CC4DBBCF3C4F0B8EC1780608ED@wds-exc1.okna.nominet.org.uk> <8B52F0C3-EB5A-48D1-9596-52302F6A4A3C@darou.fr> <8FA52BBD-9A61-4795-9BA3-AB8B0A63EB98@fugue.com> <CAKD1Yr0-kFJjRL-FhMJsnqa+ikpbGBcvFTGoN44pnJbpE=udCA@mail.gmail.com> <29DCB6B2-B428-4B45-8796-ACB09E40376A@fugue.com> <E67F19D0-96A2-4D18-B153-7B2F10117039@iki.fi> <F1877423-844E-4096-8DF4-319893BA7410@fugue.com> <8FB38433-5358-4172-968C-76564A875520@employees.org> <E2FC2ECC-D5C7-448D-A2CA-7FB32A4818F6@fugue.com>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.1827)
Cc: Alexandru Petrescu <alexandru.petrescu@gmail.com>, Markus Stenberg <markus.stenberg@iki.fi>, Ray Bellis <Ray.Bellis@nominet.org.uk>, Pierre Pfister <pierre.pfister@darou.fr>, "homenet@ietf.org Group" <homenet@ietf.org>, Lorenzo Colitti <lorenzo@google.com>
Subject: Re: [homenet] DHCP PD
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Feb 2014 08:04:55 -0000

Ted,

>> actually, we're talking about prefix assignment. which may be splitting hairs, but isn't quite the same as prefix delegation.
> 
> Splain?   You mean we're talking about the general problem, rather than the DHCP-PD solution?   If so, that's fine, but the specific comment that Markus made was about DHCP PD, and that's what I was responding to.   I am not specifically advocating the use of DHCP PD to solve this problem, but I do want to see it evaluated realistically, and not on the basis of a misunderstanding of what it does and how it's used.

as one of the authors of RFC3633, DHCP PD was not designed to do assignment of prefixes inside a network.
DHCP PD was designed to be a "fax replacement".

there has been a number of proposals for how DHCP PD could be adapted for this purpose:

they generally fall into one of flat assignment with central DHCP server or hierarchical PD with a spanning tree of DHCP relays.

http://tools.ietf.org/html/draft-baker-homenet-prefix-assignment-01
http://tools.ietf.org/html/draft-chakrabarti-homenet-prefix-alloc-01
http://tools.ietf.org/html/draft-gmann-homenet-relay-autoconf-01
http://tools.ietf.org/html/draft-grundemann-hipnet-00

please take a look at those drafts, and let us know what we've missed in the DHCP PD "solution space".

cheers,
Ole

v2.23.0 | Report a Bug | By Email