Trust Anchor Management Requirements
RFC 6024, “Trust Anchor Management Requirements”, is an Informational document published in October 2010 by R. Reddy, C. Wallace. The canonical text is published by the RFC Editor.
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. This document is not an Internet Standards Track specification; it is published for informational purposes.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 6024 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 6023 A Childless Initiation of the Internet Key Exchange Version 2 Security Association
- RFC 6025 ASN.1 Translation
- RFC 6022 YANG Module for NETCONF Monitoring
- RFC 6026 Correct Transaction Handling for 2xx Responses to Session Initiation Protocol INVITE Requests
- RFC 6021 Common YANG Data Types
- RFC 6027 IPsec Cluster Problem Statement
- RFC 6020 YANG - A Data Modeling Language for the Network Configuration Protocol
- RFC 6028 Host Identity Protocol Multi-Hop Routing Extension