Viewgraph · 5 frames
Registration and controlled issuance
Prefixes, delegated authority, the controlled issuance sequence, idempotent retries, and permanent non-reuse — the rules that make an RID trustworthy before anyone resolves it.
Viewgraph5 frames
Issuance
Only a registered, delegated issuer can issue
Syntax anyone can write. Issuance requires a registered prefix, proven authority, and an atomic registry write.
RSM ID Learning Center
rsmid.org
Prefix and authority
Authority flows from a registered prefix
A controller holds the prefix and delegates issuance; every delegation is auditable and revocable.
Rendering diagram…
Delegating issuance transfers no ownership of the resources named under it.
Reference algorithm
Authorize, generate, commit atomically
A candidate is not an identity until the registry transaction commits.
Authenticate the principal; check prefix, space, and kind.
80 random bits as 16 Crockford Base32 characters.
RID, first RRN, binding, event, and idempotency record together.
A duplicate RID means a new suffix — never a failed claim of authority.
Idempotency
A retried request returns the same RID
Keys are scoped to the issuer and a hash of the normalized request.
The originally committed RID comes back; no second RID is minted.
A conflict — never a silent overwrite.
Permanence
An issued RID belongs to its referent for good
Deletion, archival, transfer, or unavailability never free an RID for another resource.
Read as text
- IssuanceOnly a registered, delegated issuer can issueSyntax anyone can write. Issuance requires a registered prefix, proven authority, and an atomic registry write.Source: Document 08 v1.1 §5.4, §11.2
- Prefix and authorityAuthority flows from a registered prefixA controller holds the prefix and delegates issuance; every delegation is auditable and revocable.The Prefix Registry records prefix 451 and its controller. The controller delegates to an authorized issuer, recorded in the Authority Registry. The issuer issues an RID into the Resource Identity Registry.Source: Document 08 v1.1 §3.2, §5.4 — the 451 prefix is proposed, not registered
- Reference algorithmAuthorize, generate, commit atomicallyA candidate is not an identity until the registry transaction commits.1 · AuthorizeAuthenticate the principal; check prefix, space, and kind.2 · Generate a candidate80 random bits as 16 Crockford Base32 characters.3 · Commit atomicallyRID, first RRN, binding, event, and idempotency record together.4 · Retry on collisionA duplicate RID means a new suffix — never a failed claim of authority.Source: Document 09 v1.1 §6.1; Document 08 v1.1 §3.3, §3.4
- IdempotencyA retried request returns the same RIDKeys are scoped to the issuer and a hash of the normalized request.Same key, same requestThe originally committed RID comes back; no second RID is minted.Same key, different requestA conflict — never a silent overwrite.Source: Document 09 v1.1 §6.3
- PermanenceAn issued RID belongs to its referent for goodDeletion, archival, transfer, or unavailability never free an RID for another resource.RuleSource: Document 08 v1.1 §3.5; Document 09 v1.1 §6.4
Sources and provenance
Normative basis
- Document 08 v1.1 — Section 3.2Prefix allocation
- Document 08 v1.1 — Section 3.3Suffix generation
- Document 08 v1.1 — Section 3.4Concurrency and uniqueness
- Document 08 v1.1 — Section 3.5Immutability and non-reuse
- Document 08 v1.1 — Section 5.4Registry trust
- Document 08 v1.1 — Section 11.2Namespace authorization
- Document 09 v1.1 — Section 6.1Algorithm
- Document 09 v1.1 — Section 6.3Idempotency
- Document 09 v1.1 — Section 6.4Non-reuse
This viewgraph is an informative explanation. Where it and the specifications differ, Documents 08 and 09 v1.1 govern.
What it contains
- Document 08 v1.1 · normative
- Grounded directly in Document 08, the controlling standard. Cited by section.
- Document 09 v1.1 · reference implementation
- Guidance from Document 09, the proposed reference implementation. Subordinate to Document 08; its technology choices are not requirements.
- Interpretation
- Explanation or design rationale written for this Learning Center. It does not add requirements.
- Hypothetical example
- An illustrative scenario. Its identifiers are examples or fictional; none has been issued.
- Proposed, not operational
- Something the specifications propose — a host, a prefix, a federation, a service — that does not exist yet.
Related
Pathway: Naming and Authority · Technical · Revised 2026-10-09 · Content ID viewgraph.registration-and-issuance (a page identifier on this site, not an RID)