Re: [dhcwg] [Technical Errata Reported] RFC8415 (6183)

[Erik Kline <[e-mail]>]

Thanks. Marked as Verified.

On Tue, May 19, 2020 at 2:19 PM Bernie Volz (volz) <[e-mail]> wrote:
>
> Hi:
>
> Yes, this is a good catch. It is a valid errata.
>
> - Bernie
>
> -----Original Message-----
> From: RFC Errata System <[e-mail]>
> Sent: Tuesday, May 19, 2020 3:18 PM
> To: [e-mail]; [e-mail]; Bernie Volz (volz) <[e-mail]>; Andrew Yourtchenko (ayourtch) <[e-mail]>; [e-mail]; [e-mail]; [e-mail]; [e-mail]; [e-mail]; Eric Vyncke (evyncke) <[e-mail]>; Bernie Volz (volz) <[e-mail]>; [e-mail]
> Cc: [e-mail]; [e-mail]; [e-mail]
> Subject: [Technical Errata Reported] RFC8415 (6183)
>
> The following errata report has been submitted for RFC8415, "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)".
>
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid6183
>
> --------------------------------------
> Type: Technical
> Reported by: Fernando Gont <[e-mail]>
>
> Section: 18.3.8
>
> Original Text
> -------------
>    After all the addresses have been processed, the server generates a
>    Reply message by setting the "msg-type" field to REPLY and copying
>    the transaction ID from the Decline message into the "transaction-id"
>    field.  The client includes a Status Code option (see Section 21.13)
>    with the value Success, a Server Identifier option (see Section 21.3)
>    with the server's DUID, and a Client Identifier option (see
>    Section 21.2) with the client's DUID
>
> Corrected Text
> --------------
>    After all the addresses have been processed, the server generates a
>    Reply message by setting the "msg-type" field to REPLY and copying
>    the transaction ID from the Decline message into the "transaction-id"
>    field.  The server includes a Status Code option (see Section 21.13)
>    with the value Success, a Server Identifier option (see Section 21.3)
>    with the server's DUID, and a Client Identifier option (see
>    Section 21.2) with the client's DUID
>
> Notes
> -----
> The corrected text replaces "client" with "server".
>
> I would like to thank Timothy Winters <[e-mail]> for confirming that this is a bug in the specification.
>
> Instructions:
> -------------
> This erratum is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party can log in to change the status and edit the report, if necessary.
>
> --------------------------------------
> RFC8415 (draft-ietf-dhc-rfc3315bis-13)
> --------------------------------------
> Title               : Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
> Publication Date    : November 2018
> Author(s)           : T. Mrugalski, M. Siodelski, B. Volz, A. Yourtchenko, M. Richardson, S. Jiang, T. Lemon, T. Winters
> Category            : PROPOSED STANDARD
> Source              : Dynamic Host Configuration
> Area                : Internet
> Stream              : IETF
> Verifying Party     : IESG