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

Parse extensible option tuples

04

Variable OPT data consists of option-code, option-length, and option-data tuples.

Related RFCs and changes

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

RFC 6891 · § 6.1.2EXAMPLE
3 / 3
Parse extensible option tuplesVariable OPT data consists of option-code, option-length, and option-data tuples.code Alength 3abcconsume exactly 3unknown codelengthSkip bounded data → next optionOption tuples have explicit data lengths
03
Skip an unknown option and continue at the next tuple.

Skip an unknown option and continue at the next tuple.

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

Option length bounds each option’s data.

  • Option length bounds each option’s data.
  • An endpoint ignores options it does not understand as specified; it cannot reinterpret their bytes as a following field.
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 ↗