Clarification of RFC7030 CSR Attributes definition
draft-ietf-lamps-rfc7030-csrattrs-01
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
|---|---|---|---|
| Authors | Michael Richardson , Owen Friel , David von Oheimb , Dan Harkins | ||
| Last updated | 2023-04-03 (Latest revision 2022-09-30) | ||
| Replaces | draft-richardson-lamps-rfc7030-csrattrs | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Reviews |
GENART Early review
(of
-08)
by Lars Eggert
Ready w/nits
|
||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Yes | ||
| 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
The Enrollment over Secure Transport (EST, RFC7030) is ambiguous in its specification of the CSR Attributes Response. This has resulted in implementation challenges and implementor confusion. This document updates RFC7030 (EST) and clarifies how the CSR Attributes Response can be used by an EST server to specify both CSR attribute OIDs and also CSR attribute values, in particular X.509 extension values, that the server expects the client to include in subsequent CSR request.
Authors
Michael Richardson
Owen Friel
David von Oheimb
Dan Harkins
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)