top | item 39260913 (no title) bebna | 2 years ago looks like v7 is basically v1 updated. v6 looks interesting with the db optimisation in mind.UUIDv7 spec: https://www.ietf.org/archive/id/draft-peabody-dispatch-new-u... discuss order hn newest yrro|2 years ago FYI that's a link to a now very old internet draft.The current draft can be found here: https://datatracker.ietf.org/doc/draft-ietf-uuidrev-rfc4122b... michaelmior|2 years ago > Systems that do not involve legacy UUIDv1 SHOULD consider using UUIDv7 instead.The optimization relevant to v6 also applies to v7. The difference is that v7 UUIDs are not directly compatible with v1 UUIDs.
yrro|2 years ago FYI that's a link to a now very old internet draft.The current draft can be found here: https://datatracker.ietf.org/doc/draft-ietf-uuidrev-rfc4122b...
michaelmior|2 years ago > Systems that do not involve legacy UUIDv1 SHOULD consider using UUIDv7 instead.The optimization relevant to v6 also applies to v7. The difference is that v7 UUIDs are not directly compatible with v1 UUIDs.
yrro|2 years ago
The current draft can be found here: https://datatracker.ietf.org/doc/draft-ietf-uuidrev-rfc4122b...
michaelmior|2 years ago
The optimization relevant to v6 also applies to v7. The difference is that v7 UUIDs are not directly compatible with v1 UUIDs.