Trust Anchor Management Requirements
RFC 6024
|
| Document |
Type |
|
RFC - Informational
(October 2010; No errata)
|
|
Last updated |
|
2015-10-14
|
|
Stream |
|
IETF
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
WG state
|
|
WG Document
|
|
Document shepherd |
|
No shepherd assigned
|
| IESG |
IESG state |
|
RFC 6024 (Informational)
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
Tim Polk
|
|
Send notices to |
|
(None)
|
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 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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4
1.2. Requirements Notation . . . . . . . . . . . . . . . . . . 4
2. Problem Statement . . . . . . . . . . . . . . . . . . . . . . 5
3. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.1. Transport Independence . . . . . . . . . . . . . . . . . . 6
3.2. Basic Management Operations . . . . . . . . . . . . . . . 7
3.3. Management Targets . . . . . . . . . . . . . . . . . . . . 7
3.4. Delegation of TA Manager Authority . . . . . . . . . . . . 8
3.5. RFC 5280 Support . . . . . . . . . . . . . . . . . . . . . 9
3.6. Support Purposes other than Certification Path
Validation . . . . . . . . . . . . . . . . . . . . . . . . 9
3.7. Trust Anchor Format . . . . . . . . . . . . . . . . . . . 10
3.8. Source Authentication . . . . . . . . . . . . . . . . . . 10
3.9. Reduce Reliance on Out-of-Band Trust Mechanisms . . . . . 11
3.10. Replay Detection . . . . . . . . . . . . . . . . . . . . . 11
3.11. Compromise or Disaster Recovery . . . . . . . . . . . . . 12
4. Security Considerations . . . . . . . . . . . . . . . . . . . 12
5. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13
5.1. Normative References . . . . . . . . . . . . . . . . . . . 13
Show full document text