-
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 …
-
```
## Section 1
Two sentences appear to contradict each others:
- `A UUID is 128 bits long and requires no central registration process`
- `In addition, a global registration function is bein…
-
`Timestamp::from_rfc4122` method panics with `attempt to subtract with overflow` error when passing ticks value less than `UUID_TICKS_BETWEEN_EPOCHS`.
I'm not sure that the intentional use of a UUI…
-
(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…
-
The draft specification 'Compact UUIDs for Constrained Grammars' specifies 3 different textual encodings: uuid-ncname-32, uuid-ncname-58, uuid-ncname-64.
https://www.ietf.org/id/draft-taylor-uuid-ncn…
-
### Feature description
These versions of uuid, although I believe not officially ratified are better for database usage. could support be added please? there is a java library that supports them i…
-
# Context
Per [this discussion](https://news.ycombinator.com/item?id=32805325), this extension uses ` text` rather than ` uuid` for ulid and other identifiers with the same size of uuid. It a…
-
Section 5.6 says "the 48 bit node SHOULD be set to a pseudo-random value". Which does it mean:
1. the node SHOULD be reset to a pseudo-random number every time a new UUIDv6 is generated; or,
2. th…
-
- 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:
> …
-
(Continuation of a discussion in #144)
I want to propose that part of UUIDv8 gets split in a new format UUIDv9. I hope there is a slight chance that it is still possible at this stage.
Current s…