[dhcwg] [Errata Held for Document Update] RFC4361 (5425)

RFC Errata System <rfc-editor@rfc-editor.org> Mon, 08 February 2021 08:22 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 183383A1495; Mon, 8 Feb 2021 00:22:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level:
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 ejWGVBH2TR2y; Mon, 8 Feb 2021 00:22:38 -0800 (PST)
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 B20E13A1493; Mon, 8 Feb 2021 00:22:38 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id AF5A1F40757; Mon, 8 Feb 2021 00:22:14 -0800 (PST)
To: nmalykh@gmail.com, mellon@nominum.com, sommerfeld@sun.com
X-PHP-Originating-Script: 1005:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: evyncke@cisco.com, iesg@ietf.org, dhcwg@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20210208082214.AF5A1F40757@rfc-editor.org>
Date: Mon, 08 Feb 2021 00:22:14 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/nhhMyEB7YSUcOyhdf6bHybeQVzI>
Subject: [dhcwg] [Errata Held for Document Update] RFC4361 (5425)
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: Mon, 08 Feb 2021 08:22:40 -0000

The following errata report has been held for document update 
for RFC4361, "Node-specific Client Identifiers for Dynamic Host Configuration Protocol Version Four (DHCPv4)". 

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid5425

--------------------------------------
Status: Held for Document Update
Type: Editorial

Reported by: Nikolai Malykh <nmalykh@gmail.com>
Date Reported: 2018-07-16
Held by: Eric Vyncke (IESG)

Section: 5

Original Text
-------------
   - DHCPv4 servers that do conform to this specification must
     interoperate correctly with DHCPv4 clients that do not conform to
     this specification, except that when configuring such clients,
     behaviors such as those described in section 2 may occur.


Corrected Text
--------------
   - DHCPv4 servers that do conform to this specification must
     interoperate correctly with DHCPv4 clients that do not conform to
     this specification, except that when configuring such clients,
     behaviors such as those described in section 4.2 may occur.


Notes
-----
Incorrect referenct to section 2.

-- Verifier note --
The original text should indeed refer to section 4.2 but it can be expected that the reader will auto-correct and as the error does not prevent interoperation, this errata is classified as "held for document update".

--------------------------------------
RFC4361 (draft-ietf-dhc-3315id-for-v4-05)
--------------------------------------
Title               : Node-specific Client Identifiers for Dynamic Host Configuration Protocol Version Four (DHCPv4)
Publication Date    : February 2006
Author(s)           : T. Lemon, B. Sommerfeld
Category            : PROPOSED STANDARD
Source              : Dynamic Host Configuration
Area                : Internet
Stream              : IETF
Verifying Party     : IESG