[dhcwg] [Technical Errata Reported] RFC8415 (6183)
RFC Errata System <rfc-editor@rfc-editor.org> Tue, 19 May 2020 19:17 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AECDA3A0D65 for <dhcwg@ietfa.amsl.com>; Tue, 19 May 2020 12:17:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VcXktJqurH-X for <dhcwg@ietfa.amsl.com>; Tue, 19 May 2020 12:17:50 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 285963A0D5E for <dhcwg@ietf.org>; Tue, 19 May 2020 12:17:50 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 1037AF406DB; Tue, 19 May 2020 12:17:46 -0700 (PDT)
To: tomasz.mrugalski@gmail.com, msiodelski@gmail.com, volz@cisco.com, ayourtch@cisco.com, mcr+ietf@sandelman.ca, jiangsheng@huawei.com, mellon@fugue.com, twinters@iol.unh.edu, ek.ietf@gmail.com, evyncke@cisco.com, volz@cisco.com, tomasz.mrugalski@gmail.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: fgont@si6networks.com, dhcwg@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20200519191746.1037AF406DB@rfc-editor.org>
Date: Tue, 19 May 2020 12:17:46 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/w7F43QEw0-hlljQp4Ihc8OZfmr0>
X-Mailman-Approved-At: Tue, 19 May 2020 14:18:47 -0700
Subject: [dhcwg] [Technical Errata Reported] RFC8415 (6183)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 May 2020 19:17:52 -0000
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 <fgont@si6networks.com> 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 <tim@qacafe.com> 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
- [dhcwg] [Technical Errata Reported] RFC8415 (6183) RFC Errata System
- Re: [dhcwg] [Technical Errata Reported] RFC8415 (… Bernie Volz (volz)
- Re: [dhcwg] [Technical Errata Reported] RFC8415 (… Erik Kline