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

Separate EDNS version and response codes

03

OPT reuses its TTL-shaped field for extended response code, EDNS version, and flags.

Related RFCs and changes

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

RFC 6891 · § 6.1.3EXAMPLE
3 / 3
Separate EDNS version and response codesOPT reuses its TTL-shaped field for extended response code, EDNS version, and flags.OPT TTL-SHAPED FIELD · NOT A CACHE TTLextended RCODEVERSIONflagsunsupported versionBADVERS + supported versionVersion negotiation is not a record lifetime
03
Return BADVERS rather than interpreting the data as a normal TTL.

Return BADVERS rather than interpreting the data as a normal TTL.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
KEY POINT

These bits do not mean an ordinary record-cache TTL.

  • These bits do not mean an ordinary record-cache TTL.
  • Unsupported EDNS versions use BADVERS with the responder’s supported version.
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. Attach message metadata using OPT
  2. Advertise a UDP receive limit
  3. Separate EDNS version and response codes
  4. Parse extensible option tuples
  5. Keep OPT out of the record cache

Drawing view

Scroll the drawing to see every part. Playback controls stay above it.

RFC 9700 / CHAPTERS

Chapters

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

RFC status and corrections ↗