[CDNi] RFC 9538 on Content Delivery Network Interconnection (CDNI) Delegation Using the Automated Certificate Management Environment
rfc-editor@rfc-editor.org Thu, 22 February 2024 20:53 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: cdni@ietfa.amsl.com
Delivered-To: cdni@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 925FEC14F704; Thu, 22 Feb 2024 12:53:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.658
X-Spam-Level:
X-Spam-Status: No, score=-6.658 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xn4roySqcBOi; Thu, 22 Feb 2024 12:53:12 -0800 (PST)
Received: from rfcpa.amsl.com (rfcpa.amsl.com [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DF3BBC14F71F; Thu, 22 Feb 2024 12:53:12 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 9DD69191A48B; Thu, 22 Feb 2024 12:53:12 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, cdni@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20240222205312.9DD69191A48B@rfcpa.amsl.com>
Date: Thu, 22 Feb 2024 12:53:12 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/cdni/fXRfqIN6sDwTjKYOF93tvWG5TQo>
Subject: [CDNi] RFC 9538 on Content Delivery Network Interconnection (CDNI) Delegation Using the Automated Certificate Management Environment
X-BeenThere: cdni@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "This list is to discuss issues associated with the Interconnection of Content Delivery Networks \(CDNs\)" <cdni.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cdni>, <mailto:cdni-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cdni/>
List-Post: <mailto:cdni@ietf.org>
List-Help: <mailto:cdni-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cdni>, <mailto:cdni-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Feb 2024 20:53:16 -0000
A new Request for Comments is now available in online RFC libraries. RFC 9538 Title: Content Delivery Network Interconnection (CDNI) Delegation Using the Automated Certificate Management Environment Author: F. Fieau, Ed., E. Stephan, S. Mishra Status: Standards Track Stream: IETF Date: February 2024 Mailbox: frederic.fieau@orange.com, emile.stephan@orange.com, sanjay.mishra@verizon.com Pages: 10 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-cdni-delegation-acme-04.txt URL: https://www.rfc-editor.org/info/rfc9538 DOI: 10.17487/RFC9538 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. This document is a product of the Content Delivery Networks Interconnection Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC