Visual RFC.
ALL RFCs / RFC 9562
Read the RFC ↗
RFC 9562 / MECHANISM GUIDE

UUID fields and text

01

A UUID is 128 bits, commonly written in five hexadecimal groups.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

DIAGRAM§ 4 ↗
RFC 9562 · § 4EXAMPLE
3 / 3
UUID fields and textA UUID is 128 bits, commonly written in five hexadecimal groups.UUID fields and textxxxxxxxx-xxxx-4xxx-8xxx-xxxxxxxxxxxx8 4 4 4 12versionvariant32 hexadecimal digits = 128 bits
03
Interpret 128 bits

Hyphens are presentation separators, not extra identifier bits.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
WHAT CHANGED
RFC 4122 versions 1–5RFC 9562 §§5.6–5.8

This revision defines time-ordered versions 6 and 7 and custom version 8, alongside revised generation guidance.

Read the updated RFC section ↗
KEY POINT

The standard text form has groups of 8-4-4-4-12 hexadecimal digits.

  • The standard text form has groups of 8-4-4-4-12 hexadecimal digits.
  • Version and variant bits identify the applicable layout.
  • A syntactically valid identifier does not authenticate its creator.
DETAILS

Examples are illustrative. Consult the linked RFC and its errata for implementation details.

Read the RFC section ↗

Diagrams simplify the RFC. Read the linked sections for complete requirements.

Privacy
All chapters in this RFC
  1. UUID fields and text
  2. Random UUID version 4
  3. Time-ordered UUID version 7
  4. Name-based and custom layouts
  5. Generation and privacy limits
RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗