Trust Anchor Management Protocol (TAMP)
RFC 5934
Document | Type |
RFC - Proposed Standard
(August 2010; Errata)
Was draft-ietf-pkix-tamp (pkix WG)
|
|
---|---|---|---|
Authors | Carl Wallace , Sam Ashmore , Russ Housley | ||
Last updated | 2020-01-21 | ||
Replaces | draft-housley-tamp | ||
Stream | Internent Engineering Task Force (IETF) | ||
Formats | plain text html pdf htmlized (tools) htmlized with errata bibtex | ||
Reviews | |||
Stream | WG state | WG Document | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 5934 (Proposed Standard) | |
Action Holders |
(None)
|
||
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | Tim Polk | ||
Send notices to | (None) |
Internet Engineering Task Force (IETF) R. Housley Request for Comments: 5934 Vigil Security, LLC Category: Standards Track S. Ashmore ISSN: 2070-1721 National Security Agency C. Wallace Cygnacom Solutions August 2010 Trust Anchor Management Protocol (TAMP) 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. Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc5934. Housley, et al. Standards Track [Page 1] RFC 5934 TAMP August 2010 Copyright Notice Copyright (c) 2010 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English. Housley, et al. Standards Track [Page 2] RFC 5934 TAMP August 2010 Table of Contents 1. Introduction ....................................................4 1.1. Terminology ................................................5 1.2. Trust Anchors ..............................................5 1.2.1. Apex Trust Anchors ..................................6 1.2.2. Management Trust Anchors ............................7 1.2.3. Identity Trust Anchors ..............................7 1.3. Architectural Elements .....................................8 1.3.1. Cryptographic Module ................................8 1.3.2. Trust Anchor Store ..................................9 1.3.3. TAMP Processing Dependencies ........................9 1.3.4. Application-Specific Protocol Processing ...........10 1.4. ASN.1 Encoding ............................................11 2. Cryptographic Message Syntax Profile ...........................12 2.1. ContentInfo ...............................................13 2.2. SignedData Info ...........................................14 2.2.1. SignerInfo .........................................15 2.2.2. EncapsulatedContentInfo ............................16 2.2.3. Signed Attributes ..................................16 2.2.4. Unsigned Attributes ................................18 3. Trust Anchor Formats ...........................................18 4. Trust Anchor Management Protocol Messages ......................19 4.1. TAMP Status Query .........................................21Show full document text