Key Attestation Extension for Certificate Management Protocols
draft-wallace-lamps-key-attestation-ext-01
Document | Type |
Replaced Internet-Draft
(lamps WG)
Expired & archived
|
|
---|---|---|---|
Authors | Carl Wallace , Sean Turner | ||
Last updated | 2022-10-17 (Latest revision 2022-08-10) | ||
Replaced by | draft-ietf-lamps-key-attestation-ext | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | Adopted by a WG | |
Document shepherd | (None) | ||
IESG | IESG state | Replaced by draft-ietf-lamps-key-attestation-ext | |
Consensus boilerplate | Unknown | ||
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
Certification Authorities (CAs) issue certificates for public keys conveyed to the CA via a certificate management message or protocol. In some cases, a CA may wish to tailor certificate contents based on whether the corresponding private key is secured by hardware in non- exportable form. This document describes extensions that may be included in any of several widely used certificate management protocols to convey attestations about the private key to the CA to support this determination.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)