-
Currently our DocKeys are UUIDv5, which effectively takes some arbitrary input, and applies a SHA1 hash and inserting that into the UUID data field.
This was implemented originally because UUIDv5 w…
-
(Copied from my email to uuidrev@ietf.org to add a relevant but different topic)
I would propose to limit the size of Increased Clock Precision (6.2. Monotonicity and Counters: Method 4) to a certa…
-
- AD Review request from Murray on Section 6's SHOULDs.
- Addressing all as numbered by the section.subsection with author commentary.
- Feel free to discuss my suggestions.
Murray Feedback:
> …
-
As seen in #83, I made some remarks on draft 03. In this issue I will list things that are not fully handled by the current draft (04) and some additional things I have in mind:
1. As mentioned in …
-
As a result of the attempt to implement the standard, one unfortunate shortcoming was revealed. I propose to add the following text to the section "6.1. Timestamp Considerations" in the next version o…
-
| Q | A
| ------------ | ---
| Feature PR | symfony/symfony#47525
| PR author(s) | @nicolas-grekas
| Merged in | 6.2
-
I'm not sure if the spec mentions this, but I thought given that one of the inspirations was the usage of snowflake, I thought at the very least there's a way to provide the machine/node-id.
Unless…
-
Will it be possible to implement a machine ID as mentioned in the [proposal](https://www.ietf.org/archive/id/draft-peabody-dispatch-new-uuid-format-01.html#name-distributed-uuid-generation)?
-
RT
https://github.com/agnirudrasil/avault/blob/c6ca7037a5a99d97fcf43eb6b9ef935439171c02/backend/app/api/utils/snowflake.py
-
In 2013 I reported this errata to original UUID RFC (RFC 4122): https://www.rfc-editor.org/errata/eid3546 . In short, big endian / little endian are not used consistently in original RFC, so (in my op…