[dhcwg] [Technical Errata Reported] RFC2131 (7776)
RFC Errata System <rfc-editor@rfc-editor.org> Tue, 23 January 2024 16:25 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
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 099C0C14F5E0 for <dhcwg@ietfa.amsl.com>; Tue, 23 Jan 2024 08:25:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.659
X-Spam-Level:
X-Spam-Status: No, score=-6.659 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5Jr8kycyVF-w for <dhcwg@ietfa.amsl.com>; Tue, 23 Jan 2024 08:25:44 -0800 (PST)
Received: from rfcpa.amsl.com (rfcpa.amsl.com [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 13C8BC14F5F5 for <dhcwg@ietf.org>; Tue, 23 Jan 2024 08:25:44 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id C48F61A3A46B; Tue, 23 Jan 2024 08:25:43 -0800 (PST)
To: droms@bucknell.edu, ek.ietf@gmail.com, evyncke@cisco.com, tim@qacafe.com, bevolz@gmail.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: sahsah.imrane@gmail.com, dhcwg@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20240123162543.C48F61A3A46B@rfcpa.amsl.com>
Date: Tue, 23 Jan 2024 08:25:43 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/F6Ga9DVSeIyJjH2OOJt1CS6sr3k>
Subject: [dhcwg] [Technical Errata Reported] RFC2131 (7776)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Dynamic Host Configuration <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, 23 Jan 2024 16:25:48 -0000
The following errata report has been submitted for RFC2131, "Dynamic Host Configuration Protocol". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid7776 -------------------------------------- Type: Technical Reported by: Imrane <sahsah.imrane@gmail.com> Section: 4.3.1 Original Text ------------- In the page 29 (if you were reading on a PDF), section "4.3.1 DHCPDISCOVER message" "table 3: Fields and options used by DHCP server", on the "options" list, the "Client identifier" option, it says "MUST NOT" for both DHCPOFFER and DHCPACK, however on DHCPNAK it says "MAY". Corrected Text -------------- "Client Identifier" should be a "MUST NOT" for the DHCPNAK as well. Notes ----- It seems that the field should only be used by a client and never by a server, and if that's true for the OFFER and ACK, then it should be even more correct for the NAK. "Vendor class identifier" has a MAY for all three messages, so maybe it was a typo in the previous option because of the repetitive input in the next one. Instructions: ------------- This erratum is currently posted as "Reported". (If it is spam, it will be removed shortly by the RFC Production Center.) Please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party will log in to change the status and edit the report, if necessary. -------------------------------------- RFC2131 (no draft string recorded) -------------------------------------- Title : Dynamic Host Configuration Protocol Publication Date : March 1997 Author(s) : R. Droms Category : DRAFT STANDARD Source : Dynamic Host Configuration Area : Internet Stream : IETF Verifying Party : IESG
- [dhcwg] [Technical Errata Reported] RFC2131 (7776) RFC Errata System
- Re: [dhcwg] [Technical Errata Reported] RFC2131 (… Rebecca VanRheenen
- Re: [dhcwg] [Technical Errata Reported] RFC2131 (… Bernie Volz
- Re: [dhcwg] [Technical Errata Reported] RFC2131 (… Eric Vyncke (evyncke)