RFC 5934: Trust Anchor Management Protocol (TAMP)

This document describes a transport independent protocol for the management of trust anchors (TAs) and community identifiers stored in a trust anchor store.…

Read RFC 5934 on the RFC Editor

Outgoing relationships (9 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 3986: Uniform Resource Identifier (URI): Generic Syntax
Informative reference — RFC 3279: Algorithms and Identifiers for the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile
Informative reference — RFC 3370: Cryptographic Message Syntax (CMS) Algorithms
Informative reference — RFC 5753: Use of Elliptic Curve Cryptography (ECC) Algorithms in Cryptographic Message Syntax (CMS)
Informative reference — RFC 5754: Using SHA2 Algorithms with Cryptographic Message Syntax
Informative reference — RFC 4108: Using Cryptographic Message Syntax (CMS) to Protect Firmware Packages
Informative reference — RFC 5755: An Internet Attribute Certificate Profile for Authorization
Informative reference — RFC 4049: BinaryTime: An Alternate Format for Representing Date and Time in ASN.1

Incoming relationships (6 related RFCs)

Normatively referenced by — RFC 7193: The application/cms Media Type
Informatively referenced by — RFC 6010: Cryptographic Message Syntax (CMS) Content Constraints Extension
Informatively referenced by — RFC 7299: Object Identifier Registry for the PKIX Working Group
Informatively referenced by — RFC 6024: Trust Anchor Management Requirements
Informatively referenced by — RFC 5937: Using Trust Anchor Constraints during Certification Path Processing
Informatively referenced by — RFC 7191: Cryptographic Message Syntax (CMS) Key Package Receipt and Error Content Types