RFC 4122: A Universally Unique IDentifier (UUID) URN Namespace
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 9562.
Current version: RFC 9562 — Universally Unique IDentifiers (UUIDs)
In plain English — editorial summary, not part of the RFC
This specification defines a Uniform Resource Name namespace for UUIDs (Universally Unique IDentifier), also known as GUIDs (Globally Unique IDentifier). A UUID is 128 bits long, and can guarantee uniqueness across space and time. UUIDs were originally used in the Apollo Network Computing System and later in the Open Software Foundation\'s (OSF) Distributed Computing Environment (DCE), and then in Microsoft Windows platforms. This specification is derived from the DCE specification with the kind permission of the OSF (now known as The Open Group). Information from earlier versions of the DCE specification have been incorporated into this document. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4122
- Published
- July 2005
- Authors
- P. Leach; M. Mealling; R. Salz
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 32
- Also known as
- —
- Obsoleted by:
- RFC 9562
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4854A Uniform Resource Name (URN) Namespace for Extensions to the Extensible Messaging and Presence Protocol (XMPP)Current
April 2007
- RFC 4926A URN Namespace for GEANTCurrent
July 2007
- RFC 5134A Uniform Resource Name Namespace for the EPCglobal Electronic Product Code (EPC) and Related StandardsCurrent
January 2008
- RFC 8141Uniform Resource Names (URNs)Current
April 2017
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?