IETF Logo Mail Archive

Re: [dhcwg] Anyone interested in continuing draft-ietf-dhc-dhcpv6-prefix-pool-opt?

"Leaf Yeh" <leaf.yeh.sdo@gmail.com> Fri, 23 August 2013 13:16 UTC

Return-Path: <leaf.yeh.sdo@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5042A11E81BE for <dhcwg@ietfa.amsl.com>; Fri, 23 Aug 2013 06:16:44 -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=[AWL=0.000, 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 9vIXUcjzh0CH for <dhcwg@ietfa.amsl.com>; Fri, 23 Aug 2013 06:16:43 -0700 (PDT)
Received: from mail-pb0-x22c.google.com (mail-pb0-x22c.google.com [IPv6:2607:f8b0:400e:c01::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 20AAE11E81B7 for <dhcwg@ietf.org>; Fri, 23 Aug 2013 06:16:43 -0700 (PDT)
Received: by mail-pb0-f44.google.com with SMTP id xa7so671953pbc.3 for <dhcwg@ietf.org>; Fri, 23 Aug 2013 06:16:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:thread-index :content-language; bh=gw9d67YG7I9USXqCFWJ+EUeT15y2XXcKK/f0AKgMNAU=; b=iMKIAtQA09SwkA1oqH0b1fq4i2VjUqy/4yGG/nrEN7gqJ5xUPZclJgsD24m9b3uwgW wSSoRj4BGQwr6OUVM8vUEW5Jhkuq67Gg6RNd+haEmylT+fuaTu+svybx1D/619GuV487 IW5XZ9i2PSIwpM2lrZO9n7ArEKZCwf0g5zhQ0jGVHPMLjC2dgKM5MMtNK359WmQFjUbi RRUrA68wSUVqX28V50YdpBgZXxJWHzUdZZbRWDY0MPIKxtPY7eEA37kfBqfB1XYhrcEb Z+HqCI09itCwxeYRZwPisOILS6pNzu0ptkvJwr+iyI1P12h1/ThRLLx6lGPFx/zmw5Em NHQg==
X-Received: by 10.66.228.38 with SMTP id sf6mr21067385pac.21.1377263802759; Fri, 23 Aug 2013 06:16:42 -0700 (PDT)
Received: from PC ([111.193.212.125]) by mx.google.com with ESMTPSA id oj6sm1059013pab.9.1969.12.31.16.00.00 (version=TLSv1 cipher=RC4-SHA bits=128/128); Fri, 23 Aug 2013 06:16:41 -0700 (PDT)
From: Leaf Yeh <leaf.yeh.sdo@gmail.com>
To: sthaug@nethelp.no, volz@cisco.com
References: <CAKOT5Kr_Ve+9taH_AmhUp1HwHY=ggytVjUuToMf2Wr4oKoozOQ@mail.gmail.com> <94C682931C08B048B7A8645303FDC9F36EEEE4E6DB@PUEXCB1B.nanterre.francetelecom.fr> <7B81A958-9434-46B6-973A-D4BD7F2C424F@cisco.com> <20130823.141844.74728418.sthaug@nethelp.no>
In-Reply-To: <20130823.141844.74728418.sthaug@nethelp.no>
Date: Fri, 23 Aug 2013 21:16:34 +0800
Message-ID: <521760b9.2683420a.5c2f.36fc@mx.google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac6f+vFXymVeN2eXTeaNivJYeYUd/QABqQOA
Content-Language: zh-cn
Cc: dhcwg@ietf.org, rdroms.ietf@gmail.com
Subject: Re: [dhcwg] Anyone interested in continuing draft-ietf-dhc-dhcpv6-prefix-pool-opt?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Aug 2013 13:16:44 -0000

Steinar - 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.

What kind of preconfiguration on the router you need ? Pls. read my reply to
Bernie's question.

OPTION_PREFIX_POOL defined in this draft just help your relay to know which
pool your customer's prefix are from, and this information could help your
router to do the dynamic route aggregation, which sounds your need on your
PE router.


Best Regards,
Leaf



-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of
sthaug@nethelp.no
Sent: Friday, August 23, 2013 8:19 PM
To: volz@cisco.com
Cc: dhcwg@ietf.org; rdroms.ietf@gmail.com
Subject: Re: [dhcwg] Anyone interested in continuing
draft-ietf-dhc-dhcpv6-prefix-pool-opt?

> 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
_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www.ietf.org/mailman/listinfo/dhcwg

v2.23.0 | Report a Bug | By Email