[dhcwg] [Editorial Errata Reported] RFC6603 (4958)

RFC Errata System <rfc-editor@rfc-editor.org> Tue, 07 March 2017 08:13 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 9536D1293F0 for <dhcwg@ietfa.amsl.com>; Tue, 7 Mar 2017 00:13:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-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 IwRxoluNgRD0 for <dhcwg@ietfa.amsl.com>; Tue, 7 Mar 2017 00:13:04 -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 33DD7127A90 for <dhcwg@ietf.org>; Tue, 7 Mar 2017 00:13:04 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 3F9ABB82A93; Tue, 7 Mar 2017 00:13:03 -0800 (PST)
To: jouni.nospam@gmail.com, teemu.savolainen@nokia.com, suresh.krishnan@ericsson.com, ot@cisco.com, suresh.krishnan@ericsson.com, terry.manderson@icann.org, volz@cisco.com, tomasz.mrugalski@gmail.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20170307081303.3F9ABB82A93@rfc-editor.org>
Date: Tue, 7 Mar 2017 00:13:03 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/ECXPn4tz6mU4Ld9EVAqWYqGSE9s>
X-Mailman-Approved-At: Tue, 07 Mar 2017 03:53:47 -0800
Cc: dhcwg@ietf.org, text/plain@rfc-editor.org, rfc-editor@rfc-editor.orgContent-Type, sander@steffann.nl, charset=UTF-8@rfc-editor.org
Subject: [dhcwg] [Editorial Errata Reported] RFC6603 (4958)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.17
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: Tue, 07 Mar 2017 08:13:05 -0000

The following errata report has been submitted for RFC6603,
"Prefix Exclude Option for DHCPv6-based Prefix Delegation".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6603&eid=4958

--------------------------------------
Type: Editorial
Reported by: Sander Steffann <sander@steffann.nl>

Section: 6.1

Original Text
-------------
6.1.  Requesting Router

   The requesting router behavior regarding the use of the
   OPTION_PD_EXCLUDE option is mostly identical to the steps described
   in Section 5.1, with the difference being the use of a DHCPv6 Request
   instead of an Solicit message.  The requesting router SHOULD include
   the OPTION_PD_EXCLUDE option code in the OPTION_ORO option for DHCPv6
   messages as described in Section 22.7 of [RFC3315].  The requesting
   router SHOULD include the OPTION_PD_EXCLUDE option code in the
   OPTION_ORO option for DHCPv6 messages as described in Section 22.7 of
   [RFC3315].

Corrected Text
--------------
6.1.  Requesting Router

   The requesting router behavior regarding the use of the
   OPTION_PD_EXCLUDE option is mostly identical to the steps described
   in Section 5.1, with the difference being the use of a DHCPv6 Request
   instead of an Solicit message.  The requesting router SHOULD include
   the OPTION_PD_EXCLUDE option code in the OPTION_ORO option for DHCPv6
   messages as described in Section 22.7 of [RFC3315].


Notes
-----
Minor editorial bug: the last sentence of that paragraph was duplicated.

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. 

--------------------------------------
RFC6603 (draft-ietf-dhc-pd-exclude-04)
--------------------------------------
Title               : Prefix Exclude Option for DHCPv6-based Prefix Delegation
Publication Date    : May 2012
Author(s)           : J. Korhonen, Ed., T. Savolainen, S. Krishnan, O. Troan
Category            : PROPOSED STANDARD
Source              : Dynamic Host Configuration
Area                : Internet
Stream              : IETF
Verifying Party     : IESG