RFC 9562: Universally Unique IDentifiers (UUIDs)
In plain English — editorial summary, not part of the RFC
This specification defines UUIDs (Universally Unique IDentifiers) -- also known as GUIDs (Globally Unique IDentifiers) -- and a Uniform Resource Name namespace for UUIDs. A UUID is 128 bits long and is intended to guarantee uniqueness across space and time. UUIDs were originally used in the Apollo Network Computing System (NCS), later in the Open Software Foundation's (OSF's) Distributed Computing Environment (DCE), and then in Microsoft Windows platforms. This specification is derived from the OSF DCE specification with the kind permission of the OSF (now known as "The Open Group"). Information from earlier versions of the OSF DCE specification have been incorporated into this document. This document obsoletes RFC 4122.
Document record
- Document ID
- RFC9562
- Published
- May 2024
- Authors
- K. Davis; B. Peabody; P. Leach
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 46
- Also known as
- —
- Obsoletes:
- RFC 4122
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7989End-to-End Session Identification in IP-Based Multimedia Communication NetworksCurrent
October 2016
- RFC 9559Matroska Media Container Format SpecificationCurrent
October 2024
- RFC 9557Date and Time on the Internet: Timestamps with Additional InformationCurrent
April 2024
- RFC 9555JSContact: Converting from and to vCardUpdated
May 2024
- RFC 9554vCard Format Extensions for JSContactCurrent
May 2024
- RFC 9553JSContact: A JSON Representation of Contact DataCurrent
May 2024
- RFC 9581Concise Binary Object Representation (CBOR) Tags for Time, Duration, and PeriodCurrent
August 2024
- RFC 9585IMAP Response Code for Command Progress NotificationsCurrent
May 2024
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?