Notary Protocols
draft-adams-notary-01
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Dr. Carlisle Adams , Robert Zuccherato | ||
| Last updated | 1998-02-27 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
https://www.ietf.org/archive/id/draft-adams-notary-01.txt
Abstract
This document describes a general notary service and the protocols to be used when communicating with it. The Notary Authority is a Trusted Third Party (TTP) that can be used as one component in building reliable non-repudiation services (see [ISONR]). Useful Notary Authority responsibilities in a PKI are to validate signatures and to provide up- to-date information regarding the status of certificates. We give examples of how to use the notary to extend the lifetime of a signature beyond key expiry or revocation and to query the notary regarding the status of a certificate.
Authors
Dr. Carlisle Adams
Robert Zuccherato
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)