-
### Specification
ID generation is used in many places in PK. But the IDs must have different properties depending on the usecase.
The properties we care about are:
* Decentralised vs Central…
-
# Change Proposal Template
#### Source (Select one.)
- [x] IETF Published Draft
- [ ] Work in Progress Draft
#### Change Reason (Select all that apply.)
- [x] Typos and grammatical issues
…
-
It seems in April 2021 the draft was updated extensively.
Was wondering if the new proposed changes have any affect on your implementation of UUIDv6? Especially because the new draft proposes rest…
-
```
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9
┌─────────┬─────────┬─────────┬─────────┬─────────…
-
# Change Proposal Template
#### Source (Select one.)
- [ ] IETF Published Draft
- [x] Work in Progress Draft
#### Change Reason (Select all that apply.)
- [ ] Typos and grammatical issues
…
-
Some of the UUIDv7 implementations I've seen on GitHub have not implemented fractional seconds correctly. For instance, putting the number of milliseconds directly into the 12 bit field `subsec_a`, th…
-
Hello,
I was on the fence as to whether I should include this in #24, or file it as its own issue. If that other issue is better, let me know and I'll add a comment there instead.
I am working …
-
https://datatracker.ietf.org/doc/html/draft-peabody-dispatch-new-uuid-format-02#section-4.4.3
> The UUIDv7 Node MAY
> contain any set of data an implementation desires however the node
> …
-
One of the benefits of the sub-second fraction representation is that we no longer need to stick to decimal clock resolutions like msec, usec, and nsec. We can employ some exotic precision resolutions…
LiosK updated
2 years ago
-
The source code for UUIDv7 places the ms value (0-999) in the lower 12 bits (0-4095) of bytes 5 and 6:
```csharp
private void SetTimestampMs(Span bytes, TimeSpan unixTimeStamp)
{
…