RFC 9538: Content Delivery Network Interconnection (CDNI) Delegation Using the Automated Certificate Management Environment
In plain English — editorial summary, not part of the RFC
This document defines metadata to support delegating the delivery of HTTPS content between two or more interconnected Content Delivery Networks (CDNs). Specifically, this document defines a Content Delivery Network Interconnection (CDNI) Metadata interface object to enable delegation of X.509 certificates leveraging delegation schemes defined in RFC 9115. Per RFC 9115, delegating entities can remain in full control of the delegation and can revoke it at any time. This avoids the need to share private cryptographic key material between the involved entities.
Document record
- Document ID
- RFC9538
- Published
- February 2024
- Authors
- F. Fieau; E. Stephan; S. Mishra
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 10
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9447Automated Certificate Management Environment (ACME) Challenges Using an Authority TokenCurrent
September 2023
- RFC 9635Grant Negotiation and Authorization Protocol (GNAP)Current
October 2024
- RFC 9859Generalized DNS NotificationsCurrent
September 2025
- RFC 9891Automated Certificate Management Environment (ACME) Delay-Tolerant Networking (DTN) Node ID Validation ExtensionCurrent
November 2025
- RFC 8823Extensions to Automatic Certificate Management Environment for End-User S/MIME CertificatesCurrent
April 2021
- RFC 8737Automated Certificate Management Environment (ACME) TLS Application-Layer Protocol Negotiation (ALPN) Challenge ExtensionCurrent
February 2020
- RFC 8693OAuth 2.0 Token ExchangeCurrent
January 2020
- RFC 8555Automatic Certificate Management Environment (ACME)Current
March 2019
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?