Re: [dhcwg] Anyone interested in continuing draft-ietf-dhc-dhcpv6-prefix-pool-opt? Fri, 23 August 2013 12:18 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id C1D9711E82F5 for <>; Fri, 23 Aug 2013 05:18:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id dTsHMk0nF46a for <>; Fri, 23 Aug 2013 05:18:48 -0700 (PDT)
Received: from ( []) by (Postfix) with SMTP id 0167111E811D for <>; Fri, 23 Aug 2013 05:18:47 -0700 (PDT)
Received: (qmail 41396 invoked from network); 23 Aug 2013 12:18:44 -0000
Received: from (HELO localhost) ( by with SMTP; 23 Aug 2013 12:18:44 -0000
Date: Fri, 23 Aug 2013 14:18:44 +0200 (CEST)
Message-Id: <>
In-Reply-To: <>
References: <> <> <>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: [dhcwg] Anyone interested in continuing draft-ietf-dhc-dhcpv6-prefix-pool-opt?
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 23 Aug 2013 12:18:53 -0000

> BTW - I think I may have indicated this before, but does this really avoid the need for configuration on the router (relay)? How are items such as the link-address and next hop (dhcp server) addresses configured (rfc 3315 has a multicast default)? So there is still a bunch of "manual" configuration required? Admittedly you do say "more automation" but not really sure that has a lot of value - perhaps we need a Dynamic Router Configuration BOF?

As an operator I would prefer DHCPv6 to work similarly to DHCPv4 in a
typical scenario of:

- Large pools are explicitly configured on routers (relay agents).
- DHCP server is allowed to hand out addresses *within these pools*.
- Routers (relay agents) use information in the relayed DHCP packets
to build up some state (for instance making it possible to invalidate
the IP address when the lease expires).

Thus the DHCP server has a *limited* amount of freedom to hand out IP
within pools already known by the routers.

I would be very uncomfortable with, and probably would not want to
use, DHCP options which would let the DHCP server control address
allocation without any kind of preconfiguration on the router.

Steinar Haug, AS 2116