Delegating TLS Certificates to a CDN
draft-sheffer-lurk-cert-delegation-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2016-11-14 (latest revision 2016-05-12) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
This Internet-Draft is no longer active. A copy of
the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-sheffer-lurk-cert-delegation-00.txt
https://www.ietf.org/archive/id/draft-sheffer-lurk-cert-delegation-00.txt
Abstract
An organization that owns web content often prefers to delegate hosting of this content to a Content Delivery Network (CDN). To serve HTTP content securely, it needs to be protected with TLS. This document proposes a way for the CDN to request constrained certificates so that it can serve web content on behalf of the content owner, without having the owner's long term certificate.
Authors
Yaron Sheffer (yaronf.ietf@gmail.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)