CARVIEW |
Select Language
HTTP/2 200
date: Tue, 07 Oct 2025 02:52:04 GMT
content-type: text/plain; charset=utf-8
content-encoding: gzip
content-security-policy: default-src 'self' 'unsafe-inline' data: https://datatracker.ietf.org/ https://www.ietf.org/ https://ietf.org/ https://analytics.ietf.org https://static.ietf.org; frame-ancestors 'self' ietf.org *.ietf.org meetecho.com *.meetecho.com
cross-origin-opener-policy: unsafe-none
etag: W/"c19a4c9687d002597736c13717b948e8"
referrer-policy: strict-origin-when-cross-origin
strict-transport-security: max-age=3600; includeSubDomains
vary: Cookie, Accept-Encoding
x-content-type-options: nosniff
x-frame-options: SAMEORIGIN
cf-cache-status: MISS
expires: Tue, 07 Oct 2025 06:52:04 GMT
cache-control: public, max-age=14400
set-cookie: __cf_bm=GBLQKAi4YrbBW6zuYwb2X2NFvkF54E9ZfgzjPG9ddFo-1759805524-1.0.1.1-q0dO.LRoeC8gGode0Omd.lD99TpNS_5eNqpZUDg7lV0pyw_JoXeo0zLkMAwZVbE2vCb72sLVH.ORCKh8HA2VhLTwNh3JBjBHelxiYzfeHtk; path=/; expires=Tue, 07-Oct-25 03:22:04 GMT; domain=.ietf.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98aa19a99d1fc46e-BLR
alt-svc: h3=":443"; ma=86400
@misc{rfc9115,
series = {Request for Comments},
number = 9115,
howpublished = {RFC 9115},
publisher = {RFC Editor},
doi = {10.17487/RFC9115},
url = {https://www.rfc-editor.org/info/rfc9115},
author = {Yaron Sheffer and Diego Lopez and Antonio Pastor and Thomas Fossati},
title = {{An Automatic Certificate Management Environment (ACME) Profile for Generating Delegated Certificates}},
pagetotal = 42,
year = 2021,
month = sep,
abstract = {This document defines a profile of the Automatic Certificate Management Environment (ACME) protocol by which the holder of an identifier (e.g., a domain name) can allow a third party to obtain an X.509 certificate such that the certificate subject is the delegated identifier while the certified public key corresponds to a private key controlled by the third party. A primary use case is that of a Content Delivery Network (CDN), the third party, terminating TLS sessions on behalf of a content provider (the holder of a domain name). The presented mechanism allows the holder of the identifier to retain control over the delegation and revoke it at any time. Importantly, this mechanism does not require any modification to the deployed TLS clients and servers.},
}