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

"Eric Vyncke (evyncke)" <evyncke@cisco.com> Fri, 05 February 2021 12:16 UTC

IronPort-PHdr: 9a23:nEP71xa+rMj1mkJ4rbiZ6qD/LSx94ef9IxIV55w7irlHbqWk+dH4MVfC4el21QWTD4DW9+hDgOPNr+bmVHBTqZqCsXVXdptKWldFjMgNhAUvDYaDDlGzN//laSE2XaEgHF9o9n22Kw5ZTcD5YVCBp3Cu9zkZEw7jcwx4Ore9Fovblc/i0ee09tXaaBlJgzzoZ7R0IV22oAzdu9NQj5FlL/M6ywDCpT1DfOEFyA==
From: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
To: Bernie Volz <volz@metrocast.net>, RFC Errata System <rfc-editor@rfc-editor.org>
CC: "nmalykh@gmail.com" <nmalykh@gmail.com>, "Ted.Lemon@nominum.com" <Ted.Lemon@nominum.com>, "charles.perkins@nokia.com" <charles.perkins@nokia.com>, "michael.carney@sun.com" <michael.carney@sun.com>, "iesg@ietf.org" <iesg@ietf.org>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: [Errata Held for Document Update] RFC3315 (5450)
Thread-Index: AQHW+7fQ9cAlLvSCSUa3rJAsfvvqsqpJir6A
Date: Fri, 05 Feb 2021 12:16:20 +0000
Message-ID: <4F135347-B1E9-4FD2-A68C-D52BD64D8581@cisco.com>
References: <20210205095012.533E3F40738@rfc-editor.org> <9ADF3EB9-F4D7-47B3-B989-46E5015A9B2F@metrocast.net>
In-Reply-To: <9ADF3EB9-F4D7-47B3-B989-46E5015A9B2F@metrocast.net>
Accept-Language: fr-BE, en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/16.45.21011103
Content-Type: text/plain; charset="utf-8"
Content-ID: <28E661B9AE5D384F8989C7E2AE4072CA@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 4fcfa60b-3e77-49ad-2103-08d8c9cfd8ce
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Feb 2021 12:16:20.4531 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: xS6uY1Uj9taXP8FnS7JyI82WFikAXcT2JY+RgnQBhegAOgvYP0Kh5olkB7rOmfUVj3uAd8ZRHmueb0LuRZZpXw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: PH0PR11MB5062
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.15, xch-rcd-005.cisco.com
X-Outbound-Node: alln-core-9.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/TQ2woTbgeb3OmXwq23JcG9DR5ds>
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:16:26 -0000

Agreed Bernie, but, the process (reading the IESG statement on errata https://www.ietf.org/about/groups/iesg/statements/processing-rfc-errata/ ) is to process obsolete document as non-obsolete.

And, for sure, RFC 8415 did not make the same typo ;-) so, thank, you for your confirmation.

-éric


-----Original Message-----
From: Bernie Volz <volz@metrocast.net>
Date: Friday, 5 February 2021 at 13:09
To: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: "nmalykh@gmail.com" <nmalykh@gmail.com>, "Ted.Lemon@nominum.com" <Ted.Lemon@nominum.com>, "charles.perkins@nokia.com" <charles.perkins@nokia.com>, "michael.carney@sun.com" <michael.carney@sun.com>, Eric Vyncke <evyncke@cisco.com>, "iesg@ietf.org" <iesg@ietf.org>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [Errata Held for Document Update] RFC3315 (5450)

    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

[dhcwg] [Errata Held for Document Update] RFC3315… RFC Errata System
Re: [dhcwg] [Errata Held for Document Update] RFC… Bernie Volz
Re: [dhcwg] [Errata Held for Document Update] RFC… Eric Vyncke (evyncke)