[dhcwg] Re: draft-ietf-dhc-rfc8415bis-07.txt published

"Eric Vyncke \(evyncke\)" <[email protected]> Thu, 12 Dec 2024 13:31:03 +0000
Newsgroups gmane.ietf.dhc
Message-ID <PH0PR11MB4966CFD7A3A69B40FC95AFC2A93F2@PH0PR11MB4966.namprd11.prod.outlook.com>
Hello Tomek and authors,

Thanks for the revised I-D, I will shortly request the IETF last call.

No worries for the SVG, we can either work on it (I expect a revised I-D after the last call/IESG evaluation) or simply leave it with ascii art.

The nits for Jan is perfectly fine (written by Éric, which also triggers the same warning 😊 ).

Regards

-éric

From: Tomek Mrugalski <[email protected]>
Date: Thursday, 12 December 2024 at 14:26
To: [email protected] <[email protected]>
Cc: Eric Vyncke (evyncke) <[email protected]>, Bernie Volz <[email protected]>, Timothy Winters <[email protected]>, Suresh Krishnan <[email protected]>, Michael Richardson <[email protected]>, Sheng JIANG <[email protected]>
Subject: draft-ietf-dhc-rfc8415bis-07.txt published
Hi,

The -07 version was published. It addressed:

- hopefully all AD's (Eric) comments, except the SVG suggestion.

- added explanation what happens if implementations choose to ignore
  SHOULD NOT related to deprecated options.

- sub-options => suboptions (as suggested by idnits)

- couple typos

There's one idnit being reported about using non-ascii chars, but that's
intentional (Jan's last name is really Žorž).

Regarding SVG, I managed to convert the diagrams to SVG, but couldn't
make it work in all txt, html and PDF. Perhaps it would work better for
I-D written in kramdown, but the xml didn't. Or at least I didn't figure
it out. Either the image was missing in one of the formats or was
duplicated in some. We had a brief discussion among authors and we felt
it's not worth to do it. This is the third iteration of this RFC and
nobody complained about the ascii art being hard to understand. So
decided to stick with ascii.

If we didn't miss anything, we feel it's now ready to go.

Thanks a lot to everyone who participated.

Cheers,
Tomek


On 12.12.2024 13:48, [email protected] wrote:
> Internet-Draft draft-ietf-dhc-rfc8415bis-07.txt is now available. It is a work
> item of the Dynamic Host Configuration (DHC) WG of the IETF.
>
>    Title:   Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
>    Authors: Tomek Mrugalski
>             Bernie Volz
>             Michael C. Richardson
>             Sheng Jiang
>             Timothy Winters
>    Name:    draft-ietf-dhc-rfc8415bis-07.txt
>    Pages:   142
>    Dates:   2024-12-12
>
> 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 obsoletes RFC8415 to incorporate reported errata and to
>    obsolete the assignment of temporary addresses (the IA_TA option) and
>    the server unicast capability (the Server Unicast option and
>    UseMulticast status code).
>
> The IETF datatracker status page for this Internet-Draft is:
> https://datatracker.ietf.org/doc/draft-ietf-dhc-rfc8415bis/
>
> There is also an HTML version available at:
> https://www.ietf.org/archive/id/draft-ietf-dhc-rfc8415bis-07.html
>
> A diff from the previous version is available at:
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-dhc-rfc8415bis-07
>
> Internet-Drafts are also available by rsync at:
> rsync.ietf.org::internet-drafts
>
>
> _______________________________________________
> dhcwg mailing list -- [email protected]
> To unsubscribe send an email to [email protected]

_______________________________________________
dhcwg mailing list -- [email protected]
To unsubscribe send an email to [email protected]