HTTP/2 200 date: Wed, 08 Oct 2025 00:04:29 GMT content-type: application/xml content-encoding: gzip cache-control: public, max-age=3600 cross-origin-opener-policy: same-origin expires: Wed, 08 Oct 2025 01:04:29 GMT referrer-policy: same-origin vary: Cookie, origin, Accept-Encoding x-content-type-options: nosniff x-frame-options: DENY x-resolution-methods: manual;auto;fallback x-resolution-outcomes: ;RfcAdapter: using docid IETF RFC 9115 -> using query @.type == "IETF" && @.primary == true && @.id == "RFC 9115" -> 1 found,; last-modified: Wed, 08 Oct 2025 00:04:29 GMT cf-cache-status: MISS set-cookie: __cf_bm=kT6p3l9NtNKJ_gcMmstgHopndzZcpBrfacCWB49xUGQ-1759881869-1.0.1.1-2Omn.7191YsHUnTIKP7iAFVRGRywWATZO.ttM1wYuf5j8BwD1MonOf7INhWcNDTuvuW3uJHWluQ1dgfs52kZvj97NubWY_wGxgJl0Ti5DjU; path=/; expires=Wed, 08-Oct-25 00:34:29 GMT; domain=.ietf.org; HttpOnly; Secure; SameSite=None server: cloudflare cf-ray: 98b161917e37ccbb-BLR alt-svc: h3=":443"; ma=86400 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.