Separate configuration from trust and privacy
05Configuration can influence routing-adjacent behavior and server choices; messages and identifiers create security and privacy concerns.
Related RFCs and changes
“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.
DIAGRAM§ 22 ↗
RFC 9915 · § 22EXAMPLE
3 / 3
03
Apply trust controls and privacy measures without treating an identifier as authentication.
Apply trust controls and privacy measures without treating an identifier as authentication.
Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
Read the updated RFC section ↗
A DUID is an identifier, not proof of a trusted device.
- A DUID is an identifier, not proof of a trusted device.
- Protect relay-server exchange and Reconfigure handling using their applicable mechanisms; do not assume universal base-message authentication.
The drawing is a simplified worked example. Follow the linked RFC and its updates for implementation requirements.
Read the RFC section ↗Diagrams simplify the RFC. Read the linked sections for complete requirements.
Privacy