Visual RFC.
ALL RFCs / RFC 7858
Read the RFC ↗
RFC 7858 / PROTOCOL MECHANISMS

Authenticate the intended resolver

02

An encrypted channel must be evaluated together with the chosen authentication profile.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

DIAGRAM§ 3.2 ↗
RFC 7858 · § 3.2EXAMPLE
3 / 3
Authenticate the intended resolverAn encrypted channel must be evaluated together with the chosen authentication profile.Configured resolver identityServer identity evidencecomparemismatchAuthenticated profile: stop on failureOpportunistic encryption alone cannot defeat an active impostor
03
An authentication mismatch stops an authenticated-profile connection.

An authentication mismatch stops an authenticated-profile connection.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
WHAT CHANGED
RFC 7858 profilesRFC 8310 § 1

RFC 8310 updates usage profiles and adds authentication-domain-name mechanisms; do not treat encryption alone as authenticated privacy.

Read the updated RFC section ↗
KEY POINT

Opportunistic privacy alone does not defeat an active impersonator.

  • Opportunistic privacy alone does not defeat an active impersonator.
  • Key-pinned or later authenticated profiles require the corresponding configured identity material.
DETAILS

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
All chapters in this RFC
  1. Open a dedicated TLS transport
  2. Authenticate the intended resolver
  3. Frame DNS messages inside the stream
  4. Reuse a connection for multiple queries
  5. Distinguish transport privacy from DNS data trust
RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗