[Uuidrev] [Errata Verified] RFC9562 (7958)

RFC Errata System <rfc-editor@rfc-editor.org> Wed, 29 May 2024 15:43 UTC

Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: uuidrev@ietf.org
Delivered-To: uuidrev@ietfa.amsl.com
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (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 602A2C14CE40; Wed, 29 May 2024 08:43:37 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id B0C6B7FA60; Wed, 29 May 2024 08:43:36 -0700 (PDT)
To: rdonchen@outlook.com, kydavis@cisco.com, brad@peabody.io, pjl7@uw.edu
From: RFC Errata System <rfc-editor@rfc-editor.org>
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20240529154336.B0C6B7FA60@rfcpa.rfc-editor.org>
Date: Wed, 29 May 2024 08:43:36 -0700
Message-ID-Hash: MOT5RG2ZFIKT27PORLTWECT4KKHIHYN3
X-Message-ID-Hash: MOT5RG2ZFIKT27PORLTWECT4KKHIHYN3
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: orie@transmute.industries, iesg@ietf.org, uuidrev@ietf.org, iana@iana.org, rfc-editor@rfc-editor.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Uuidrev] [Errata Verified] RFC9562 (7958)
List-Id: Revise Universally Unique Identifier Definitions <uuidrev.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/uuidrev/SlKTWWbPNiXpFWZQIWVFdCOf33k>
List-Archive: <https://mailarchive.ietf.org/arch/browse/uuidrev>
List-Help: <mailto:uuidrev-request@ietf.org?subject=help>
List-Owner: <mailto:uuidrev-owner@ietf.org>
List-Post: <mailto:uuidrev@ietf.org>
List-Subscribe: <mailto:uuidrev-join@ietf.org>
List-Unsubscribe: <mailto:uuidrev-leave@ietf.org>

The following errata report has been verified for RFC9562,
"Universally Unique IDentifiers (UUIDs)". 

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid7958

--------------------------------------
Status: Verified
Type: Technical

Reported by: Roman Donchenko <rdonchen@outlook.com>
Date Reported: 2024-05-25
Verified by: Orie Steele (IESG)

Section: 4.1

Original Text
-------------
     | 0    | x    | x    | x    | 1-7     | Reserved.  Network      |
     |      |      |      |      |         | Computing System (NCS)  |
     |      |      |      |      |         | backward compatibility, |
     |      |      |      |      |         | and includes Nil UUID   |
     |      |      |      |      |         | as per Section 5.9.     |


Corrected Text
--------------
     | 0    | x    | x    | x    | 0-7     | Reserved.  Network      |
     |      |      |      |      |         | Computing System (NCS)  |
     |      |      |      |      |         | backward compatibility, |
     |      |      |      |      |         | and includes Nil UUID   |
     |      |      |      |      |         | as per Section 5.9.     |


Notes
-----
This row matches the case where MSB0, MSB1, MSB2, MSB3 are all 0, which would make the variant number 0.

--------------------------------------
RFC9562 (draft-ietf-uuidrev-rfc4122bis-14)
--------------------------------------
Title               : Universally Unique IDentifiers (UUIDs)
Publication Date    : May 2024
Author(s)           : K. Davis, B. Peabody, P. Leach
Category            : PROPOSED STANDARD
Source              : Revise Universally Unique Identifier Definitions
Stream              : IETF
Verifying Party     : IESG