Visual RFC.
ALL RFCs / RFC 6750
Read the RFC ↗
RFC 6750 / MECHANISMS

Limit the damage of disclosure

05

Audience and scope restriction reduce where and how a stolen token can be used.

Related RFCs and changes

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

DIAGRAM§ 5.2 ↗
RFC 6750 · § 5.2EXAMPLE
3 / 3
Limit the damage of disclosureAudience and scope restriction reduce where and how a stolen token can be used. Current state: Expiry.Limit the damage of disclosureaud: calendarscope: readexpires at TCalendar APIaud matchwrite requestread-onlyafter T → token rejected
03
Expiry

After expiration, a correctly validating server rejects the token.

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

The token must be protected in transit using TLS.

  • The token must be protected in transit using TLS.
  • Restrict tokens to intended recipients.
  • Short lifetimes reduce exposure but do not themselves stop all replay.
DETAILS

The illustration is schematic. Example values are illustrative; profiles and later security guidance can add requirements.

Read the RFC section ↗

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

Privacy
All chapters in this RFC
  1. Possession is the credential
  2. Put it in the request header
  3. URLs leave extra copies
  4. Errors describe different failures
  5. Limit the damage of disclosure
RFC 9700 / CHAPTERS

Chapters

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

RFC status and corrections ↗