From: "Gaurav Halwasia (ghalwasi)" <ghalwasi@cisco.com>
To: Ted Lemon <Ted.Lemon@nominum.com>, dhc WG <dhcwg@ietf.org>
Thread-Topic: Call for adoption: draft-lemon-dhc-pd-01
Thread-Index: AQHNlrARAq1IuhHT2UasbuE4rMIyj5ej0M6g
Date: Mon, 1 Oct 2012 02:48:51 +0000
Message-ID: <90903C21C73202418A48BFBE80AEE5EB1BD3A001@xmb-aln-x06.cisco.com>
References: <EBDD0AE4-93C6-44F1-9BE0-7B7BE5EC2173@nominum.com>
In-Reply-To: <EBDD0AE4-93C6-44F1-9BE0-7B7BE5EC2173@nominum.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [dhcwg] Call for adoption: draft-lemon-dhc-pd-01
Precedence: list

I read this I.D and I think it's a useful work to do. I am in favor of adop=
ting this document as WG document.

Thanks,
Gaurav=20

-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of T=
ed Lemon
Sent: Thursday, September 20, 2012 3:15 AM
To: dhc WG
Subject: [dhcwg] Call for adoption: draft-lemon-dhc-pd-01

I'd like the working group to work on this document.   The point of the doc=
ument is to provide a mechanism whereby DHCP requesting routers can indicat=
e their preference to the DHCP delegating router as to how the reverse zone=
 for a delegated prefix should be handled, and to provide a mechanism where=
by the delegating router can communicate back to the requesting router the =
mechanism that was chosen.

John will be evaluating consensus, since I'm the author of the draft.   He =
will evaluate consensus some time after October 2.   If you are in favor of=
 adopting this draft, please say so on the mailing list.   If you think it'=
s a bad idea, please say so on the list.

Thanks!

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www.ietf.org/mailman/listinfo/dhcwg