Re: [dhcwg] WG Adoption Call - draft-dhcwg-dhc-rfc3315bis-04

Hello,
	I’m also in favor of adopting this document as a working group document.  It has important changes to help improve interoperability.

~Tim

> On Mar 4, 2015, at 7:53 PM, STARK, BARBARA H <bs7652@att.com> wrote:
> 
> +1 for adoption
> This draft is wonderful and much needed. Thanks so much for doing it.
> As to the “additional question” -- as I parse through the ~100 emails that arrived in my inbox overnight, I’m not feeling a strong desire for notifications to go to dhc instead of or in addition to dhcpv6bis.
> Barbara
>  
> Please adopt this document as a wg item.
>  
> Thanks – Fred
> fred.l.templin@boeing.com <mailto:fred.l.templin@boeing.com>
>  
> From: dhcwg [mailto:dhcwg-bounces@ietf.org <mailto:dhcwg-bounces@ietf.org>] On Behalf Of Bernie Volz (volz)
> Sent: Wednesday, March 04, 2015 5:18 AM
> To: dhcwg@ietf.org <mailto:dhcwg@ietf.org>
> Subject: Re: [dhcwg] WG Adoption Call - draft-dhcwg-dhc-rfc3315bis-04 - Concludes March 9, 2015
> Importance: High
>  
> Reminder that this adoption call concludes March 9th.
>  
> I haven’t seen anyone comment on whether the DHC WG should adopt this document. We need SOME indication that people are in favor of having the WG adopt this document.
>  
> I am in favor of having the WG adopt this work – but as I am a co-author on the document, that is not a surprise.
>  
> -          Bernie
>  
> From: dhcwg [mailto:dhcwg-bounces@ietf.org <mailto:dhcwg-bounces@ietf.org>] On Behalf Of Bernie Volz (volz)
> Sent: Sunday, February 22, 2015 4:16 PM
> To: dhcwg@ietf.org <mailto:dhcwg@ietf.org>
> Subject: [dhcwg] WG Adoption Call - draft-dhcwg-dhc-rfc3315bis-04 - Concludes March 9, 2015
>  
> Hi:
>  
> As you all know, the work to update the DHCPv6 specs, mainly RFC3315 and RFC3633, has been going for some time. The design team involved in this work believes that it's a good time to ask for adoption of this work.
>  
> The document - draft-dhcwg-dhc-rfc3315bis-04 (https://tools.ietf.org/html/draft-dhcwg-dhc-rfc3315bis <https://tools.ietf.org/html/draft-dhcwg-dhc-rfc3315bis>) - started from a XMLized copy of RFC3315 (see the -00 draft). Most of the text from RFC3633 was merged (note: there are still missing pieces) there. A significant number of corrections, clarifications and smaller edits were made. The changes are documented in appendices A and B. They often mention ticket numbers. Those tickets can be reviewed and commented athttp://wiki.tools.ietf.org/group/dhcpv6bis/ <http://wiki.tools.ietf.org/group/dhcpv6bis/>.
>  
> As both DHC WG chairs, DHC secretary, and current AD are co-authors of this draft, we'll not be able to assess consensus on our own. We will consult with our AD to determine the best course of action. In any case, the adoption call consensus will be determined shortly after end of day March 9th. (Though if there are no objections, the consensus is clear.)
>  
> Keep in mind that this is a work well in progress with lots of outstanding things to do. The question here is whether this is the direction we, as a working group, want to take.
>  
> There's also an additional question if you support adoption. Every time a ticket is added, modified or commented in the issue tracker, there's a mail notification. Currently such notifications are sent to the dhcpv6bis mailing list. You can review those here:
> http://www.ietf.org/mail-archive/web/dhcpv6bis/current/maillist.html <http://www.ietf.org/mail-archive/web/dhcpv6bis/current/maillist.html>. If you want those notifications to be sent to the DHC rather than dhcpv6bis list, please say so.
>  
> -          Bernie & Tomek
>  
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg