Generation and privacy limits
05Uniqueness, ordering, privacy, and unguessability are separate properties.
Related RFCs and changes
“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.
DIAGRAM§ 6.7 ↗
RFC 9562 · § 6.7EXAMPLE
3 / 3
03
Authorize separately
Knowing an identifier must not automatically authorize access.
Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
Read the updated RFC section ↗
Use appropriate generator state and collision resistance for the use case.
- Use appropriate generator state and collision resistance for the use case.
- Time-based values can reveal timing, and older layouts can reveal host-related data.
- UUIDs are identifiers, not bearer capabilities unless a separate secure design establishes that role.
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