Trust Anchor Management Protocol (TAMP)
draft-housley-tamp-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Russ Housley , Raksha Reddy , Carl Wallace | ||
| Last updated | 2007-10-04 | ||
| Replaced by | RFC 5934 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-pkix-tamp | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document describes a transport independent, request-response protocol for the management of trust anchors and community identifiers stored in a device. The protocol makes use of the Cryptographic Message Syntax (CMS), and a digital signature is used to provide integrity protection and data origin authentication. Each trust anchor is associated with a list of functions within devices that make use of digital signature mechanisms. Digital signatures can be validated directly with the public key associated with the trust anchor, or they can be validated with a certified public key whose X.509 certification path terminates with the trust anchor public key.
Authors
Russ Housley
Raksha Reddy
Carl Wallace
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)