Trust Anchor Management Protocol (TAMP)
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 91
- Abstract
- 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]
- Publication Date
- 2010-08-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC5934- Link
- https://doi.org/10.17487/RFC5934
- Author(s)
- Russ HousleySam AshmoreCarl Wallace
- Keyword(s)
- Trust Anchors, TA
Latest version of IETF RFC 5934
Document Versions — IETF RFC 5934
-
▶ IETF RFC 5934 (2010-08-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 2119 [Active*]
- IETF RFC 2616 [Superseded*]
- IETF RFC 3986 [Active, Amended*]
- IETF RFC 5280 [Active, Amended*]
- IETF RFC 5652 [Active*]
- IETF RFC 5912 [Active*]
- IETF RFC 5914 [Active*]
- T-REC-X.680.1997 — ITU-T Recommendation X.680 (1997): "Information technology-Abstract Syntax Notation One (ASN.1): Specification of basic notation". EXTERNAL
- T-REC-X.690.1997 — - ITU-T Recommendation X.690 (1997), Information Technology - ASN.1 Encoding Rules: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER). EXTERNAL
Bibliographic Reference(s)
- NIST.FIPS.186 — DSS EXTERNAL
- Reddy, R. and C. Wallace, "Trust Anchor Management Requirements", Work in Progress, March 2010. EXTERNAL
- IETF RFC 3279 [Active*]
- IETF RFC 3370 [Active*]
- RFC4049 — RFC4049 EXTERNAL
- RFC4108 — RFC4108 EXTERNAL
- RFC5753 — RFC5753 EXTERNAL
- RFC5754 — CMS-SHA2 EXTERNAL
- RFC5755 — ATTRCERT EXTERNAL
- RSA.PKCS6.v1.5.1993 — PKCS6 EXTERNAL
- T-REC-X.208.1988 — CCITT/ISO88d EXTERNAL
- T-REC-X.509.2000 — X.509-2000 EXTERNAL
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC5934.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 5934, Trust Anchor Management Protocol (TAMP). Available at https://doi.org/10.17487/RFC5934
Snippet:
IETF RFC 5934, Trust Anchor Management Protocol (TAMP). Available at https://doi.org/10.17487/RFC5934
HTML (ISO 690 compliant)
Preview:
IETF RFC 5934, Trust Anchor Management Protocol (TAMP). Available at https://doi.org/10.17487/RFC5934
Snippet:
<span class="citation"><cite>IETF RFC 5934</cite>, Trust Anchor Management Protocol (TAMP). Available at <a href="https://doi.org/10.17487/RFC5934" target="_blank" rel="noopener">https://doi.org/10.17487/RFC5934</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 5934, Trust Anchor Management Protocol (TAMP)
doi: 10.17487/RFC5934
url: https://doi.org/10.17487/RFC5934
doi: 10.17487/RFC5934
url: https://doi.org/10.17487/RFC5934
Snippet:
<li> <cite id="bib-rfc5934">IETF RFC 5934</cite>, Trust Anchor Management Protocol (TAMP) <span class="doi">10.17487/RFC5934</span> </li>
Referenced By
- IETF RFC 5937 [Active*]
- IETF RFC 6024 [Active*]
- IETF RFC 7925 [Active*]