[CDNi] RFC 9246 on URI Signing for Content Delivery Network Interconnection (CDNI)

rfc-editor@rfc-editor.org Wed, 15 June 2022 01:46 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 A1134C15AAF7; Tue, 14 Jun 2022 18:46:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.657
X-Spam-Level:
X-Spam-Status: No, score=-1.657 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 rUUz4MvCiH9B; Tue, 14 Jun 2022 18:46:28 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [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 0B583C15AACF; Tue, 14 Jun 2022 18:46:28 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id E6D18CD7FF; Tue, 14 Jun 2022 18:46:27 -0700 (PDT)
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: <20220615014627.E6D18CD7FF@rfcpa.amsl.com>
Date: Tue, 14 Jun 2022 18:46:27 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/cdni/raqZZH2RZESmaHbH93rO8BoriEI>
Subject: [CDNi] RFC 9246 on URI Signing for Content Delivery Network Interconnection (CDNI)
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: Wed, 15 Jun 2022 01:46:31 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 9246

        Title:      URI Signing for Content Delivery 
                    Network Interconnection (CDNI) 
        Author:     R. van Brandenburg,
                    K. Leung,
                    P. Sorber
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2022
        Mailbox:    ray@tiledmedia.com,
                    mail4kentl@gmail.com,
                    sorber@apple.com
        Pages:      37
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-cdni-uri-signing-26.txt

        URL:        https://www.rfc-editor.org/info/rfc9246

        DOI:        10.17487/RFC9246

This document describes how the concept of URI Signing supports the
content access control requirements of Content Delivery Network
Interconnection (CDNI) and proposes a URI Signing method as a JSON
Web Token (JWT) profile.

The proposed URI Signing method specifies the information needed to
be included in the URI to transmit the signed JWT, as well as the
claims needed by the signed JWT to authorize a User Agent (UA). The
mechanism described can be used both in CDNI and single Content
Delivery Network (CDN) scenarios.

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