A Universally Unique IDentifier (UUID) URN Namespace
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 32
- Abstract
- 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]
- Publication Date
- 2005-07-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC4122- Link
- https://doi.org/10.17487/RFC4122
- Author(s)
- Paul J. LeachMichael H. MeallingRich Salz
- Keyword(s)
- URN, UUID
Latest version of IETF RFC 4122
Document Versions — IETF RFC 4122
-
▶ IETF RFC 4122 (2005-07-01)THIS DOC [SUPERSEDED] [LATEST VERSION]
Normative Reference(s)
- ISBN.0136116744 — 1 EXTERNAL
- ISBN.1859120415 — 2 EXTERNAL
- NIST FIPS 180-1 [Withdrawn]
- IETF RFC 1321 [Active*]
- IETF RFC 1750 [Superseded*]
- IETF RFC 2141 [Superseded*]
- IETF RFC 2234 [Superseded*]
- IETF RFC 4086 [Active*]
- T-REC-X.667 — ITU-T Recommendation X.667 (10/2012), “Generation and registration of Universally Unique Identifiers (UUIDs) and their use as ASN.1 Object Identifier components,” International Telecommunication Union, Oct. 2012. [Online]. Available at: https://www.itu.int/rec/T-REC-X.667 EXTERNAL
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC4122.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 4122, A Universally Unique IDentifier (UUID) URN Namespace. Available at https://doi.org/10.17487/RFC4122
Snippet:
IETF RFC 4122, A Universally Unique IDentifier (UUID) URN Namespace. Available at https://doi.org/10.17487/RFC4122
HTML (ISO 690 compliant)
Preview:
IETF RFC 4122, A Universally Unique IDentifier (UUID) URN Namespace. Available at https://doi.org/10.17487/RFC4122
Snippet:
<span class="citation"><cite>IETF RFC 4122</cite>, A Universally Unique IDentifier (UUID) URN Namespace. Available at <a href="https://doi.org/10.17487/RFC4122" target="_blank" rel="noopener">https://doi.org/10.17487/RFC4122</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 4122, A Universally Unique IDentifier (UUID) URN Namespace
doi: 10.17487/RFC4122
url: https://doi.org/10.17487/RFC4122
doi: 10.17487/RFC4122
url: https://doi.org/10.17487/RFC4122
Snippet:
<li> <cite id="bib-rfc4122">IETF RFC 4122</cite>, A Universally Unique IDentifier (UUID) URN Namespace <span class="doi">10.17487/RFC4122</span> </li>
Referenced By
- IMF End-to-End Workflows in Media Asset Management Systems [Active]
- IMF End-to-End Workflows in Media Asset Management Systems [Active]
- DCI DCSS v1.4.2 [Superseded*]
- DCI DCSS v1.4.5 [Active*]
- IETF draft-bhutton-json-schema-validation-00 [Active*]
- IETF draft-bhutton-json-schema-validation-01 [Active*]
- ISO 26429-10:2009 [Active]
- ISO 26429-7:2008 [Active, Reaffirmed]
- ISO 26429-8:2009 [Active, Reaffirmed]
- ISO 26429-9:2009 [Active]
- ISO 26430-1:2008 [Active, Reaffirmed]
- ISO 26430-3:2008 [Active, Reaffirmed]
- ISO 26430-9:2009 [Active, Reaffirmed]
- ISO 26433:2009 [Active, Reaffirmed]
- IETF RFC 4479 [Active*]
- IETF RFC 4918 [Active*]
- IETF RFC 5049 [Active*]
- IETF RFC 6120 [Active*]
- IETF RFC 6350 [Active*]
- IETF RFC 6455 [Active*]
- IETF RFC 6648 [Active*]
- IETF RFC 6933 [Active*]
- IETF RFC 6991 [Superseded*]
- IETF RFC 7217 [Active*]
- IETF RFC 7254 [Active*]
- IETF RFC 7515 [Active*]
- IETF RFC 7519 [Active*]
- SMPTE RDD 18:2010 [Superseded]
- SMPTE RDD 18:2012 [Superseded]
- SMPTE RDD 52:2020 [Active]
- SMPTE RP 2021-9:2009 [Superseded]
- SMPTE RP 2021-9:2012 [Superseded]
- SMPTE RP 2021-9:2015 [Superseded]
- SMPTE RP 2021-9:2017 [Active]
- SMPTE ST 2001-1:2013 [Superseded]
- SMPTE ST 2001-1:2015 [Active]
- SMPTE ST 2021-1:2015 [Superseded]
- SMPTE ST 2021:2008 [Active]
- SMPTE ST 2029:2022 [Active]
- SMPTE ST 2029:2023 [Active]
- SMPTE ST 2034-1:2014 [Superseded]
- SMPTE ST 2034-1:2017 [Active]
- SMPTE ST 2045:2010 [Withdrawn]
- SMPTE ST 2065-4:2013 [Superseded]
- SMPTE ST 2067-2:2013 [Superseded]
- SMPTE ST 2067-2:2016 [Superseded]
- SMPTE ST 2067-2:2020 [Active]
- SMPTE ST 2067-50:2018 [Active]
- SMPTE ST 2071-2:2013 [Superseded]
- SMPTE ST 2071-2:2014 [Superseded]
- SMPTE ST 2071-2:2016 [Active, Stabilized]
- SMPTE ST 2131:2026-05 [Active]
- SMPTE ST 330:2004 [Superseded]
- SMPTE ST 330:2011 [Superseded]
- SMPTE ST 330:2022 [Active]
- SMPTE ST 377-1:2011 [Superseded]
- SMPTE ST 428-7:2010 [Superseded]
- SMPTE ST 428-7:2014 [Active, Reaffirmed]
- SMPTE ST 429-10:2008 [Superseded]
- SMPTE ST 429-2:2009 [Superseded]
- SMPTE ST 429-2:2011 [Superseded]
- SMPTE ST 429-2:2013 [Superseded]
- SMPTE ST 429-2:2013 Am1:2018 [Superseded]
- SMPTE ST 429-2:2019 [Superseded]
- SMPTE ST 429-2:2019 Am 1:2020 [Superseded*]
- SMPTE ST 429-2:2020 [Superseded]
- SMPTE ST 429-2:2023-09 [Active]
- SMPTE ST 429-5:2009 [Superseded]
- SMPTE ST 429-5:2017 [Superseded]
- SMPTE ST 429-5:2023-09 [Active]
- SMPTE ST 429-7:2006 [Active, Reaffirmed]
- SMPTE ST 429-8:2007 [Active]
- SMPTE ST 429-9:2007 [Superseded]
- SMPTE ST 429-9:2014 [Active]
- SMPTE ST 430-1:2017 [Superseded]
- SMPTE ST 430-1:2017 Am1:2019 [Superseded]
- SMPTE ST 430-1:2023-09 [Active]
- SMPTE ST 430-11:2010 [Active]
- SMPTE ST 430-14:2015 [Superseded]
- SMPTE ST 430-14:2021 [Active]
- SMPTE ST 430-3:2012 [Active]
- SMPTE ST 430-9:2008 [Active, Amended]
- SMPTE ST 430-9:2008 Am1:2011 [Active]
- SMPTE ST 433:2008 [Active, Amended, Reaffirmed]
- SMPTE ST 433:2008 Am1:2011 [Active, Reaffirmed]