IETF Logo Mail Archive

Re: [dhcwg] [Technical Errata Reported] RFC2131 (7776)

Rebecca VanRheenen <rvanrheenen@amsl.com> Tue, 23 January 2024 17:33 UTC

Return-Path: <rvanrheenen@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 437BEC14F747 for <dhcwg@ietfa.amsl.com>; Tue, 23 Jan 2024 09:33:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.908
X-Spam-Level:
X-Spam-Status: No, score=-6.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 Uqlho5r-keSv for <dhcwg@ietfa.amsl.com>; Tue, 23 Jan 2024 09:33:52 -0800 (PST)
Received: from c8a.amsl.com (c8a.amsl.com [4.31.198.40]) (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 7F913C14F69B for <dhcwg@ietf.org>; Tue, 23 Jan 2024 09:33:52 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 5D1BF4250002; Tue, 23 Jan 2024 09:33:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5OU08BYHT6Ho; Tue, 23 Jan 2024 09:33:52 -0800 (PST)
Received: from [IPv6:2601:641:300:5fb0:f406:294c:d9d7:bf8f] (unknown [IPv6:2601:641:300:5fb0:f406:294c:d9d7:bf8f]) by c8a.amsl.com (Postfix) with ESMTPSA id 3897D424B427; Tue, 23 Jan 2024 09:33:52 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Rebecca VanRheenen <rvanrheenen@amsl.com>
In-Reply-To: <20240123162543.C48F61A3A46B@rfcpa.amsl.com>
Date: Tue, 23 Jan 2024 09:33:51 -0800
Cc: sahsah.imrane@gmail.com, dhcwg@ietf.org, RFC Editor <rfc-editor@rfc-editor.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <87953371-295C-40B2-9EEF-54F85238C531@amsl.com>
References: <20240123162543.C48F61A3A46B@rfcpa.amsl.com>
To: droms@bucknell.edu, Erik Kline <ek.ietf@gmail.com>, evyncke@cisco.com, tim@qacafe.com, Bernie Volz <bevolz@gmail.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/exWwHlwzf-Wb6hZBFQkJCAdhnqc>
Subject: Re: [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 17:33:56 -0000

Hi all,

Note that we have updated the Original/Corrected text in this errata report to conform to the expected style. See https://www.rfc-editor.org/errata/eid7776.

Thank you,
RFC Editor/rv


> On Jan 23, 2024, at 8:25 AM, RFC Errata System <rfc-editor@rfc-editor.org> wrote:
> 
> 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
>

v2.23.0 | Report a Bug | By Email