[dhcwg] New Version Notification for draft-dhcwg-dhc-rfc8415bis-00.txt

[Bernie Volz <[e-mail]>]

Hello:

The RFC8415bis team is pleased to present the first draft of the document.

Please review this document and provide feeback to the WG and team.

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.

Thanks much and we would appreciate your review of the document.

Also, we will likely want to start a WG adoption call shortly as this really is a WG document.

> A new version of I-D, draft-dhcwg-dhc-rfc8415bis-00.txt
> has been successfully submitted by Bernie Volz and posted to the
> IETF repository.
> 
> Name:        draft-dhcwg-dhc-rfc8415bis
> Revision:    00
> Title:        Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
> Document date:    2022-10-07
> Group:        Individual Submission
> Pages:        135
> URL:            https://www.ietf.org/archive/id/draft-dhcwg-dhc-rfc8415bis-00.txt
> Status:         https://datatracker.ietf.org/doc/draft-dhcwg-dhc-rfc8415bis/
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-dhcwg-dhc-rfc8415bis
> 
> 
> Abstract:
>   This document describes the Dynamic Host Configuration Protocol for
>   IPv6 (DHCPv6): an extensible mechanism for configuring nodes with
>   network configuration parameters, IP addresses, and prefixes.
>   Parameters can be provided statelessly, or in combination with
>   stateful assignment of one or more IPv6 addresses and/or IPv6
>   prefixes.  DHCPv6 can operate either in place of or in addition to
>   stateless address autoconfiguration (SLAAC).
> 
>   This document replaces RFC8415 to incorporate reported errata and to
>   deprecate assignment of temporary addresses (the IA_TA option) and
>   the server unicast capability (the Server Unicast option).
>