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

Extensions constrain authority

03

Extensions limit how a certificate or subordinate CA can be used.

Related RFCs and changes

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

DIAGRAM§ 4.2 ↗
RFC 5280 · § 4.2EXAMPLE
3 / 3
Extensions constrain authorityExtensions limit how a certificate or subordinate CA can be used. Current state: Critical unknown.Extensions constrain authorityExtensionsCA: TRUEpathLen: 0keyUsage: keyCertSignintended operationunknown critical extensioncritical?A critical extension cannot be silently ignored.
03
Critical unknown

A critical extension the processor cannot handle stops validation.

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

An unrecognized critical extension requires rejection.

  • An unrecognized critical extension requires rejection.
  • basicConstraints identifies CA certificates and can bound path length.
  • keyUsage and extendedKeyUsage constrain permitted uses when present.
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. A certificate binds a public key
  2. A chain ends at configured trust
  3. Extensions constrain authority
  4. Validity is a bounded interval
  5. Revocation is separate evidence
RFC 9700 / CHAPTERS

Chapters

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

RFC status and corrections ↗