Re: [dhcwg] [Errata Held for Document Update] RFC3315 (5450)

Bernie Volz <volz@metrocast.net> Fri, 05 February 2021 12:09 UTC

Return-Path: <volz@metrocast.net>
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 3CA7D3A0D24; Fri, 5 Feb 2021 04:09:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, 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 YTXSry3XSyVq; Fri, 5 Feb 2021 04:09:44 -0800 (PST)
Received: from proofpoint-cluster.metrocast.net (proofpoint-cluster.metrocast.net [65.175.128.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7D8DE3A0D25; Fri, 5 Feb 2021 04:09:44 -0800 (PST)
Received: from [192.168.1.120] (d-24-233-121-124.nh.cpe.atlanticbb.net [24.233.121.124]) (authenticated bits=0) by huckleberry.metrocast.net (8.14.7/8.14.4) with ESMTP id 115C9dPE015459 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NO); Fri, 5 Feb 2021 12:09:40 GMT
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Bernie Volz <volz@metrocast.net>
Mime-Version: 1.0 (1.0)
Date: Fri, 05 Feb 2021 07:09:38 -0500
Message-Id: <9ADF3EB9-F4D7-47B3-B989-46E5015A9B2F@metrocast.net>
References: <20210205095012.533E3F40738@rfc-editor.org>
Cc: nmalykh@gmail.com, Ted.Lemon@nominum.com, charles.perkins@nokia.com, michael.carney@sun.com, evyncke@cisco.com, iesg@ietf.org, dhcwg@ietf.org
In-Reply-To: <20210205095012.533E3F40738@rfc-editor.org>
To: RFC Errata System <rfc-editor@rfc-editor.org>
X-Mailer: iPad Mail (18D52)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:6.0.138, 18.0.572, 0.0.0000 definitions=2020-02-29_01:2020-02-28,2020-02-29,1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1810110000 definitions=main-2002290046
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/rylYdij6Wv4aw9DSLTUGVUboVB4>
Subject: Re: [dhcwg] [Errata Held for Document Update] RFC3315 (5450)
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: Fri, 05 Feb 2021 12:09:46 -0000

While this is an error, RFC8415 has replaced RFC3315 and that issue does not exit in RFC8415.

- Bernie

> On Feb 5, 2021, at 4:50 AM, RFC Errata System <rfc-editor@rfc-editor.org> wrote:
> 
> The following errata report has been held for document update 
> for RFC3315, "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)". 
> 
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid5450
> 
> --------------------------------------
> Status: Held for Document Update
> Type: Editorial
> 
> Reported by: Nikolai Malykh <nmalykh@gmail.com>
> Date Reported: 2018-08-03
> Held by: Éric Vyncke (IESG)
> 
> Section: 18.2.5
> 
> Original Text
> -------------
>   The server MUST include a Server Identifier option containing the
>   server's DUID in the Reply message.  If the client included a Client
>   Identification option in the Information-request message, the server
>   copies that option to the Reply message.
> 
> 
> 
> Corrected Text
> --------------
>   The server MUST include a Server Identifier option containing the
>   server's DUID in the Reply message.  If the client included a Client
>   Identifier option in the Information-request message, the server
>   copies that option to the Reply message.
> 
> 
> 
> Notes
> -----
> Incorrect option name
> 
> -- Verifier note --
> Indeed, minor typo in "Client Identification" rather than "Client Identifier".
> 
> --------------------------------------
> RFC3315 (draft-ietf-dhc-dhcpv6-28)
> --------------------------------------
> Title               : Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
> Publication Date    : July 2003
> Author(s)           : R. Droms, Ed., J. Bound, B. Volz, T. Lemon, C. Perkins, M. Carney
> Category            : PROPOSED STANDARD
> Source              : Dynamic Host Configuration
> Area                : Internet
> Stream              : IETF
> Verifying Party     : IESG