Name bytes with a digest
01Named Information uses a hash function to turn defined input bytes into a digest, a fixed-size value that can be carried in a name.
ni:///sha-256; followed by that encoded digest names the example bytes without specifying a server.
Source for this drawing: RFC 6920 · Read RFC section 8.1 ↗
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.
SHA-256 is mandatory to implement: implementations MUST generate/send and accept/process names based on it (§2).
- SHA-256 is mandatory to implement: implementations MUST generate/send and accept/process names based on it (§2).
- The published Hello World! example is exactly 12 bytes with no quotes or trailing newline. The ni digest MUST use unpadded base64url (§3).
- Integrity checking is OPTIONAL in this specification (§3). A name is not proof that any application has checked received bytes.
Also RFC6920 §§1–3. Worked values are public RFC examples or fictional teaching data. Naming, locating, and checking integrity are distinct operations.
Read the RFC section ↗