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

A chain ends at configured trust

02

Path validation starts with a trusted anchor and processes certificates toward the target.

Related RFCs and changes

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

DIAGRAM§ 6.1 ↗
RFC 5280 · § 6.1EXAMPLE
3 / 3
A chain ends at configured trustPath validation starts with a trusted anchor and processes certificates toward the target. Current state: Target certificate.A chain ends at configured trustTrust anchorconfigured trustsignsIntermediatecertificatesignsTargetcertificateconstraints carried toward the target
03
Target certificate

Accept the path only if all required processing succeeds.

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

The trust anchor is an input, not a self-signature that creates trust.

  • The trust anchor is an input, not a self-signature that creates trust.
  • Verify signatures and certificate validity along the path.
  • Application identity matching is an additional concern outside basic path processing.
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

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 ↗