Surety is performing system maintenance this weekend. Electronic date stamps on new Prior Art Database disclosures may be delayed.
Browse Prior Art Database

Using Trust Anchor Constraints during Certification Path Processing (RFC5937)

IP.com Disclosure Number: IPCOM000198989D
Original Publication Date: 2010-Aug-01
Included in the Prior Art Database: 2010-Aug-20
Document File: 16 page(s) / 17K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

S. Ashmore: AUTHOR [+2]


Trust anchors are widely used to verify digital signatures and validate certification paths [RFC5280] [X.509]. They are required when validating certification paths. The Trust Anchor Format (TAF) specification [RFC5914] defines a means for limiting the scope in which a trust anchor may be used. [RFC5280] describes how to validate a certification path. The algorithm requires processing the name and key from a trust anchor. Usage of other information, including enforcement of constraints, is permitted but not required, and the processing rules are not specified (see Section 6.2 of RFC 5280).

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

Internet Engineering Task Force (IETF)                        S. Ashmore Request for Comments: 5937                      National Security Agency Category: Informational                                       C. Wallace ISSN: 2070-1721                                       Cygnacom Solutions                                                              August 2010

   Using Trust Anchor Constraints during Certification Path Processing


   This document describes how to use information associated with a    trust anchor public key when validating certification paths.  This    information can be used to constrain the usage of a trust anchor.    Typically, constraints are used to limit the certificate policies and    names that can appear in certification paths validated using a trust    anchor.

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/rfc5937.

 Ashmore & Wallace             Informational                     [Page 1]
 RFC 5937             Using Trust Anchor Constraints          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...