[dhcwg] [Technical Errata Reported] RFC8415 (6269)

RFC Errata System <rfc-editor@rfc-editor.org> Sun, 30 August 2020 15:46 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 DF2C13A0B50 for <dhcwg@ietfa.amsl.com>; Sun, 30 Aug 2020 08:46:26 -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 9DjNHGs2gxCY for <dhcwg@ietfa.amsl.com>; Sun, 30 Aug 2020 08:46:25 -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 A25393A0B3C for <dhcwg@ietf.org>; Sun, 30 Aug 2020 08:46:25 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 6CECEF4076B; Sun, 30 Aug 2020 08:46:15 -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, tim@qacafe.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: fhamme@united-internet.de, dhcwg@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset=UTF-8
Message-Id: <20200830154615.6CECEF4076B@rfc-editor.org>
Date: Sun, 30 Aug 2020 08:46:15 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/oNqBzT7CSOtoV7kQNLkJfSY_73E>
X-Mailman-Approved-At: Sun, 30 Aug 2020 09:45:17 -0700
Subject: [dhcwg] [Technical Errata Reported] RFC8415 (6269)
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: Sun, 30 Aug 2020 15:46:27 -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/eid6269

--------------------------------------
Type: Technical
Reported by: Felix Hamme <fhamme@united-internet.de>

Section: GLOBAL

Original Text
-------------
section 16:
"A server MUST discard any Solicit, Confirm, Rebind, or Information-request messages it receives with a Layer 3 unicast destination address."

section 18.2:
"If the client has a source address of sufficient scope that can be used by the server as a return address and the client has received a Server Unicast option (see Section 21.12) from the server, the client SHOULD unicast any Request, Renew, Release, and Decline messages to the server."


Appendix B does not permit a Server Unicast option in a Reconfigure message.

Corrected Text
--------------
section 16:
"A server MUST discard any Solicit, Confirm, or Rebind messages it receives with a Layer 3 unicast destination address."

section 18.2:
"If the client has a source address of sufficient scope that can be used by the server as a return address and the client has received a Server Unicast option (see Section 21.12) from the server, the client SHOULD unicast any Request, Renew, Release, Decline, and Information-request messages to the server."

Appendix B permits a Server Unicast option in a Reconfigure message.

Notes
-----
Section 18.4 allows transmission of Information-request messages with a unicast destination address, if the client received a message with Server Unicast option. (See also https://mailarchive.ietf.org/arch/msg/dhcwg/x80cmfTN8fpRViiN_RHNXes-zVg/)

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