Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Trust Anchor Management Protocol (TAMP) (RFC5934)

IP.com Disclosure Number: IPCOM000198988D
Original Publication Date: 2010-Aug-01
Included in the Prior Art Database: 2010-Aug-20

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

R. Housley: AUTHOR [+3]

Abstract

This document describes the Trust Anchor Management Protocol (TAMP). TAMP may be used to manage the trust anchors and community identifiers in any device that uses digital signatures; however, this specification was written with the requirements of cryptographic modules in mind. For example, TAMP can support signed firmware packages [RFC4108], where the trust anchor public key can be used to validate digital signatures on firmware packages or validate the X.509 certification path [RFC5280][X.509] of the firmware package signer.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 1% of the total text.

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 c...