RFC 6024: Trust Anchor Management Requirements

A trust anchor represents an authoritative entity via a public key and associated data. The public key is used to verify digital signatures, and the…

Read RFC 6024 on the RFC Editor

Outgoing relationships (10 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 5280: Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile
Normative reference — RFC 5055: Server-Based Certificate Validation Protocol (SCVP)
Informative reference — RFC 5652: Cryptographic Message Syntax (CMS)
Informative reference — RFC 2560: X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP
Informative reference — RFC 3161: Internet X.509 Public Key Infrastructure Time-Stamp Protocol (TSP)
Informative reference — RFC 4210: Internet X.509 Public Key Infrastructure Certificate Management Protocol (CMP)
Informative reference — RFC 4108: Using Cryptographic Message Syntax (CMS) to Protect Firmware Packages
Informative reference — RFC 5914: Trust Anchor Format
Informative reference — RFC 5934: Trust Anchor Management Protocol (TAMP)

Incoming relationships (4 related RFCs)

Normatively referenced by — RFC 8155: Traversal Using Relays around NAT (TURN) Server Auto Discovery
Informatively referenced by — RFC 9334: Remote ATtestation procedureS (RATS) Architecture
Informatively referenced by — RFC 9019: A Firmware Update Architecture for Internet of Things
Informatively referenced by — RFC 9397: Trusted Execution Environment Provisioning (TEEP) Architecture