Read a human-speakable name
06The nih scheme uses lowercase hexadecimal digest text, optional hyphen groups and an optional checkdigit to help people copy or speak a name.
Separate copied value 5326-9056 with the old checkdigit b does not pass the check. Stop this teaching comparison; do not turn a passing checkdigit into identity proof.
Source for this drawing: RFC 6920 · Read RFC section 7 ↗
New to this? Start hereA quick picture + helpful background
A message needs an address.
Think of a packet as a small addressed envelope. Devices pass it onward; transport protocols decide what delivery promises an application gets.
Helpful first, if these ideas are unfamiliar
These pictures are analogies to help you learn. The linked RFC explains the actual rules.
Terms in this drawing
Related RFCs and changes
“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.
The digest is lowercase ASCII hex. Hyphens MAY be inserted for readability; authority and query are not included. There are no relative nih URIs.
- The digest is lowercase ASCII hex. Hyphens MAY be inserted for readability; authority and query are not included. There are no relative nih URIs.
- The optional checkdigit MUST use Luhn mod16 over only the hex digest with hyphens removed. Algorithm names and separators do not enter that calculation.
- For supported suites with assigned IDs, implementations MUST match the decimal ID form even without binary-format support. A checkdigit catches some transcription errors; it does not authenticate a person or key.
Also RFC6920 §§8.2–8.3,9.4,10. This illustrates the optional checkdigit when present; it is not a mandatory field. Worked values are public RFC examples or fictional teaching data. Naming, locating, and checking integrity are distinct operations.
Read the RFC section ↗