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

Advertise a UDP receive limit

02

OPT’s CLASS field signals the maximum UDP payload the requester can reassemble and receive.

Related RFCs and changes

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

RFC 6891 · § 6.2.3EXAMPLE
3 / 3
Advertise a UDP receive limitOPT’s CLASS field signals the maximum UDP payload the requester can reassemble and receive.requesterresponderOPT: example UDP capacity 1232bounded response sizePath MTU can still be smaller1232 is an example capacity, not an EDNS protocol constant
03
A smaller path can still require size adjustment or TCP.

A smaller path can still require size adjustment or TCP.

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

Values below 512 are treated as 512.

  • Values below 512 are treated as 512.
  • Receive capacity does not prove that the network path can deliver that size without fragmentation.
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
RFC 9700 / CHAPTERS

Chapters

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

RFC status and corrections ↗