On Thu, 5 Jan 2023 at 12:35, Marvin W <[email protected]> wrote: > Which brings me to the conclusion: If we want to gauarantee a certain > amount of randomness in any id field, we should just state exactly > that, e.g. "the id SHOULD include at least 120 bits of randomness, for > example by using an UUIDv4" (and then we might see people in the wild > just encode 15 random bytes using base64, saving 16 bytes on the wire > with every id).
For the "SHOULD" case, yes. For the MUST case, if we're basically encoding a 128-bit number with a well-known syntax supported by external tooling like databases, then UUIDv4 is pretty much perfect. (I'd phrase the "SHOULD" case as "This identifier MUST be globally unique, and therefore it is RECOMMENDED to use UUIDv4", rather than specifying bits of randomness - the RECOMMENDED here is in the sense of "If you don't do this you'd better know what you're doing").
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
