Re: [dhcwg] Adoption Call for draft-dhcwg-dhc-rfc8415bis-00- Respond by Nov 18, 2022

[Robert Nagy <[e-mail]>]

I should have some time to review it over the weekend. Will submit comments by EOD Monday. 

Rob

Robert Nagy

CEO/ Senior Dive Master

DeepDive Networking, Inc

C: 408.480.5133

www.deepdivenetworking.com

Sent from my iPhone

On Dec 2, 2022, at 1:27 PM, Timothy Winters <[e-mail]> wrote:



Hi Bernie,

I was thinking about this today as well, all the support for adoption came from the authors of the document.  Let's extend the adoption call until 12/14. 

 In the meeting room at IETF 114 there seemed to be general interest in this work, but we need confirmation on the list. 

Can others from the working group chime on the mailing list if they support this for an adoption call?

~Tim

On Fri, Dec 2, 2022 at 4:13 PM Bernie Volz <[e-mail]> wrote:

What’s the status of this adoption call?

My guess is that it kind of failed as we had noone except myself comment to the list? But perhaps I missed some?

I do think we may need to consider adding an “Implementation Status” section as recommended by https://authors.ietf.org/recommended-content" target="_blank" rel="nofollow">https://authors.ietf.org/recommended-content (this would not end up in RFC).

- Bernie Volz

On Nov 2, 2022, at 4:28 PM, Bernie Volz <[e-mail]> wrote:

Hi:

Not sure how much it counts as I did many of the edits from RFC8415 for this bis draft, but I strongly support adoption by the WG of this document.

It would be great to get input from others on the changes as well as the few areas I had pointed out when announcing publication if the draft to the WG:

A few areas to consider during your review:
- Should we reduce some of the background material, such as sections 1.1 and 1.2 and/or 3.
- Should we remove all text related to even checking for unicast transmissions and even deprecate the UseMulticast status code. I think the only case that can end up with unicast at a 8415bis server would be if the server had been sending Server-Unicast option and is then upgraded as existing (pre8415bis clients) may then unicast … but likely if the upgraded server just accepted the message, there would not really be any harm. A 8415bis client that always multicasts should never run into problems (and thus get the UseMulticast status). The 8415bis server would never need to check if unicast.
- The Acknowledgements section has XXX, as (your) names will be inserted here as work on the document continues.

- Bernie Volz

On Oct 20, 2022, at 4:50 AM, Timothy Winters <[e-mail]> wrote:



Hello:

We would like initiating a WG call for adoption on https://datatracker.ietf.org/doc/html/draft-dhcwg-dhc-rfc8415bis" target="_blank" rel="nofollow">draft-dhcwg-dhc-rfc8415bis-00.  This document is an updated version of the DHCPv6 base specification with the intention of advancing to Internet standard.

This starts the call for adoption of this document. Please respond by November 18, 2022.

Thanks in advance for your consideration of whether the WG should or should not adopt this document as a work item.

Thanks,

Tim and Bernie

_______________________________________________
dhcwg mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/dhcwg" target="_blank" rel="nofollow">https://www.ietf.org/mailman/listinfo/dhcwg

_______________________________________________
dhcwg mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/dhcwg