Separate registration from security
05The URI registry records what a scheme name means. Its registration status is separate from the RFC publication category, and neither makes a token secure.
The RFC is Informational. A scheme registration and a document category do not encrypt a credential, approve access or prove adoption.
Source for this drawing: RFC 8959 · Read RFC section 3 ↗
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.
URI registration and RFC publication categories are separate facts.
- Section3 registers secret-token as a provisional URI scheme, identifying a token intended to be secret. This describes the RFC registration, not a live registry lookup.
- The change controller is the IESG. Section3 records no using applications yet at publication time; that historical entry is not a present-day adoption measurement.
- RFC8959 is Informational, not an Internet Standards Track specification. A registered marker grants no access, encryption, entropy or automatic secret-scanning deployment.
RFC8959 §§3 and Status of This Memo. No current adoption count or registry-status polling claim.
Read the RFC section ↗