Browse Prior Art Database

Trust Anchor Management Requirements (RFC6024)

IP.com Disclosure Number: IPCOM000200710D
Original Publication Date: 2010-Oct-01
Included in the Prior Art Database: 2010-Oct-27
Document File: 28 page(s) / 33K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

R. Reddy: AUTHOR [+2]

Abstract

Digital signatures are used in many applications. For digital signatures to provide integrity and authentication, the public key used to verify the digital signature must be "trusted", i.e., accepted by a relying party (RP) as appropriate for use in the given context. A public key used to verify a signature must be configured as a trust anchor (TA) or contained in a certificate that can be transitively verified by a certification path terminating at a trust anchor. A trust anchor is a public key and associated data used by a relying party to validate a signature on a signed object where the object is either:

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

Internet Engineering Task Force (IETF)                          R. Reddy Request for Comments: 6024                      National Security Agency Category: Informational                                       C. Wallace ISSN: 2070-1721                                       Cygnacom Solutions                                                             October 2010

                   Trust Anchor Management Requirements

Abstract

   A trust anchor represents an authoritative entity via a public key    and associated data.  The public key is used to verify digital    signatures, and the associated data is used to constrain the types of    information for which the trust anchor is authoritative.  A relying    party uses trust anchors to determine if a digitally signed object is    valid by verifying a digital signature using the trust anchor's    public key, and by enforcing the constraints expressed in the    associated data for the trust anchor.  This document describes some    of the problems associated with the lack of a standard trust anchor    management mechanism and defines requirements for data formats and    push-based protocols designed to address these problems.

Status of This Memo

   This document is not an Internet Standards Track specification; it is    published for informational purposes.

   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).  Not all documents    approved by the IESG are a candidate for any level of Internet    Standard; see 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/rfc6024.

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

Reddy & Wallace               Informational                     [Page 1]
 RFC 6024                 Trust Anchor Management            October 2010

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