metasystema.org
CurrentPROPOSED STANDARDIETF stream

RFC 5934: Trust Anchor Management Protocol (TAMP)

In plain English — editorial summary, not part of the RFC

This document describes a transport independent protocol for the management of trust anchors (TAs) and community identifiers stored in a trust anchor store. The protocol makes use of the Cryptographic Message Syntax (CMS), and a digital signature is used to provide integrity protection and data origin authentication. The protocol can be used to manage trust anchor stores containing trust anchors represented as Certificate, TBSCertificate, or TrustAnchorInfo objects. [STANDARDS-TRACK]

Document record

Document ID
RFC5934
Published
August 2010
Authors
R. Housley; S. Ashmore; C. Wallace
Status
PROPOSED STANDARD
Stream
IETF
Area
sec
Pages
91
Also known as
—

Topics

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/5934-trust-anchor-management-protocol-tamp