Delegated Credentials for TLS
This is an older version of an Internet-Draft that was ultimately published as RFC 9345.
Expired & archived
|Authors||Richard Barnes , Subodh Iyengar , Nick Sullivan , Eric Rescorla|
|Last updated||2018-05-03 (Latest revision 2017-10-30)|
|RFC stream||Internet Engineering Task Force (IETF)|
GENART Last Call review (of -12) by Elwyn Davies Ready w/nits
ARTART Last Call review (of -12) by Christian Amsüss Ready w/nits
OPSDIR Last Call Review due 2022-04-08 Incomplete
|Additional resources||Mailing list discussion|
|Stream||WG state||WG Document|
|Associated WG milestone||
|Send notices to||(None)|
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
The organizational separation between the operator of a TLS server and the certificate authority that provides it credentials can cause problems, for example when it comes to reducing the lifetime of certificates or supporting new cryptographic algorithms. This document describes a mechanism to allow TLS server operators to create their own credential delegations without breaking compatibility with clients that do not support this specification.
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)