You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
RFC 4122 UUIDv6 Example: 1EC9414C-232A-6B00-B3C8-9E6BDECED846
But in this library NewV6 generates ID like: 01eee693-1887-6e10-a722-9e6bdeced846 has a prefix 0
Many UUID libraries in other languages (for example python uuid6) follow the instructions of the RFC.
For UUIDv6, RFC also mentioned
The 48 bit node SHOULD be set to a pseudo-random value however implementations MAY choose to retain the old MAC address behavior from [RFC4122], Section 4.1.6 and [RFC4122], Section 4.5. For more information on MAC address usage within UUIDs see the Section 8
The last 48bit node can set to a pseudo-random value, it maybe more useful.
The text was updated successfully, but these errors were encountered:
I will check the first problem you report and fix it as soon as possible.
Regarding the second question , it is optional to use pseudo-randomness for the lower 48 bits of UUID1, 6. In addition, RFC recommends that you use uuidV7
RFC 4122 UUIDv6 Example: 1EC9414C-232A-6B00-B3C8-9E6BDECED846
But in this library NewV6 generates ID like: 01eee693-1887-6e10-a722-9e6bdeced846 has a prefix 0
Many UUID libraries in other languages (for example python uuid6) follow the instructions of the RFC.
For UUIDv6, RFC also mentioned
The last 48bit node can set to a pseudo-random value, it maybe more useful.
The text was updated successfully, but these errors were encountered: