Visual RFC.
ALL RFCs / RFC 9457
Read the RFC ↗
RFC 9457 / MECHANISM GUIDE

Extension members

04

Problem types can define structured members beyond the standard fields.

Related RFCs and changes

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

DIAGRAM§ 3.2 ↗
RFC 9457 · § 3.2EXAMPLE
3 / 3
Extension membersProblem types can define structured members beyond the standard fields.Extension memberstype: https://api.example/creditbalance: 20Old client: ignore balanceNew client: balance = 20
03
New consumer reads it

A knowledgeable client can use the structured value.

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

Consumers must ignore extensions they do not recognize.

  • Consumers must ignore extensions they do not recognize.
  • Extension definitions belong to the problem type.
  • Avoid incompatible reuse of a member name.
DETAILS

Examples are illustrative. Consult the linked RFC and its errata for implementation details.

Read the RFC section ↗

Diagrams simplify the RFC. Read the linked sections for complete requirements.

Privacy
All chapters in this RFC
  1. A problem response
  2. Problem type identity
  3. Human-readable details
  4. Extension members
  5. Types and safe disclosure

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 ↗