Also Mention UUID version 8
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 76/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Quiet
- Domain
- documentation
Research direction
Start with section 9.2, “testId,” and compare the current wording with the proposed sentence. Check RFC 9562 section 5.5 for the UUIDv8 rationale. Done means the specification mentions UUID version 8 alongside UUID version 5 and hash without changing the surrounding guidance.
Written by the indexing model from the issue text.
Description
Current
Under section "9.2. testId" the spec says:
A producer MAY use a canonical string directly, or MAY encode that canonical string as a deterministic identifier such as a UUID version 5 or hash.
Proposed Change
A producer MAY use a canonical string directly, or MAY encode that canonical string as a deterministic identifier such as a UUID version 5, UUID version 8 or hash."
Rationale
According to RFC 9562 UUIDv5 must be built from SHA-1. When basing the UUID on e.g. SHA-256, RFC 9562 explains, that UUIDv8 MUST be used.
RFC 9562, Section "5.5. UUID Version 5" says:
There may be scenarios, usually depending on organizational security policies, where SHA-1 libraries may not be available or may be deemed unsafe for use. As such, it may be desirable to generate name-based UUIDs derived from SHA-256 or newer SHA methods. These name-based UUIDs MUST NOT utilize UUIDv5 and MUST be within the UUIDv8 space defined by Section 5.8.
- Dominant language
- No language data
- Stars
- 93
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ctrf-io/ctrf
-
Difficulty 5/5 Over a week Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Clarify spec intent: common xtra field names, labels vs xtra.traits, stdout/stderr line-splitting Open
Difficulty 5/5 Over a week Newbie friendliness 35/100
Similar issues
-
user-reported
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kong/developer.konghq.com#7316 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Ecosystem: ClawMetry — the Qwen Code reader is now free and open source (follow-up to #9294 / #9338) Opencategory/integration priority/P3 scope/documentation status/ready-for-human type/feature-request
Difficulty 1/5 Under an hour Newbie friendliness 84/100