Re: [dhcwg] Call for Adoption: draft-yeh-dhc-dhcpv6-prefix-pool-opt-08

Ole Trøan <otroan@employees.org> Mon, 03 September 2012 08:03 UTC

Return-Path: <ichiroumakino@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 7102F21F84B6 for <dhcwg@ietfa.amsl.com>; Mon, 3 Sep 2012 01:03:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.105
X-Spam-Level:
X-Spam-Status: No, score=-3.105 tagged_above=-999 required=5 tests=[AWL=0.194, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1gdeycyPNRuj for <dhcwg@ietfa.amsl.com>; Mon, 3 Sep 2012 01:03:43 -0700 (PDT)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 83B2C21F84A6 for <dhcwg@ietf.org>; Mon, 3 Sep 2012 01:03:42 -0700 (PDT)
Received: by eekb45 with SMTP id b45so1844154eek.31 for <dhcwg@ietf.org>; Mon, 03 Sep 2012 01:03:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :message-id:references:to:x-mailer; bh=WDXRyYeZQbTSCaTsyiHGRYIXL5hzI9T3lo3udoPLcCg=; b=Z/N9N5qBEja3XiH38ioHZ+lZQ8w2fvU5mMViK5BMHzOt+hLwijzmB55fMXSmEkB3lA b+eA6SS9p5SaJha4uAdh/p3cKg55V2myMU46dGlHxFZYQYPKbBN/BIqSijmJMG2MiGWM JhUt1JzdnMc5Rhfhrg+FCOOFW2onH9wwQSkgYWhBGqpOe+ZeDF6zxHhZImayQjt/QOWS jMP06ClMg5E7Z1Ux6MM0GrvQgTFpZ4l0P3Zae7NZgOgzLUREShBxw/TmUjnBG7ujWOSn vRK68jek4ZHbCe7AQF5TO8fiL1NltF60XzWjCXzcaeKHpISA+BvKhpzJoc1wxOnkAK0z NSgw==
Received: by 10.14.211.3 with SMTP id v3mr20226737eeo.43.1346659421620; Mon, 03 Sep 2012 01:03:41 -0700 (PDT)
Received: from dhcp-lys01-vla250-10-147-112-75.cisco.com (64-103-25-233.cisco.com. [64.103.25.233]) by mx.google.com with ESMTPS id e7sm34202069eep.2.2012.09.03.01.03.39 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 03 Sep 2012 01:03:40 -0700 (PDT)
Sender: Ole Troan <ichiroumakino@gmail.com>
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: multipart/signed; boundary="Apple-Mail=_DCCF2F24-D223-413F-9F98-B1EFD6B43643"; protocol="application/pkcs7-signature"; micalg="sha1"
From: Ole Trøan <otroan@employees.org>
In-Reply-To: <91484F36-D059-4D90-8BFE-60434864A579@nominum.com>
Date: Mon, 03 Sep 2012 10:03:38 +0200
Message-Id: <6B6C7CCC-0971-4CD1-BC2F-849F6BDC1863@employees.org>
References: <91484F36-D059-4D90-8BFE-60434864A579@nominum.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.1278)
Cc: "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Call for Adoption: draft-yeh-dhc-dhcpv6-prefix-pool-opt-08
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: Mon, 03 Sep 2012 08:03:43 -0000

> The authors have proposed that the working group adopt the prefix pool option draft as a working group item.   We have engaged in some correspondence with participants in the Routing Area, and while some helpful advice was given, no objections were raised to going forward with the work, and it's a DHCP protocol extension, so it makes sense for it to happen in the DHC working group.
> 
> The document proposes an extension to the DHCP protocol that allows the DHCP server to communicate prefixes to the provider edge router when doing prefix delegation, such that this router can advertise a route to an aggregate prefix, rather than to many individual prefixes, and so that this router does not have to perform ad-hoc prefix aggregation, which may produce less optimal results.
> 
> If you think this work should be adopted by the working group, please reply to this message saying so.   If you think this work should not be adopted by the working group, please reply to this message saying so.   We will evaluate consensus on September 7.

I'm generally uncomfortable with piggybacking on the client initiated protocol, to manage a DHCPv6 relay sitting in the middle of the conversation.

I do not think it is a good idea to require DHCPv6 relays to rewrite DHCPv6 client messages. does this work with DHCPv6 authentication?

do we want to make DHCP a general management protocol of the DR/first-hop router?

I am against adopting this document as a working group document.

cheers,
Ole