Re: Redirections to `Content-Encoding: encrypted` payloads

"W. Felix Handte" <w@felixhandte.com> Thu, 01 October 2020 22:31 UTC

Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A2473A09BC for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 1 Oct 2020 15:31:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.862
X-Spam-Level:
X-Spam-Status: No, score=-2.862 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, MAILING_LIST_MULTI=-1, NICE_REPLY_A=-0.213, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hz8wP887zvt6 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 1 Oct 2020 15:31:27 -0700 (PDT)
Received: from lyra.w3.org (lyra.w3.org [128.30.52.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0C1AA3A09BA for <httpbisa-archive-bis2Juki@lists.ietf.org>; Thu, 1 Oct 2020 15:31:26 -0700 (PDT)
Received: from lists by lyra.w3.org with local (Exim 4.92) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1kO74J-0004Js-5u for ietf-http-wg-dist@listhub.w3.org; Thu, 01 Oct 2020 22:28:55 +0000
Resent-Date: Thu, 01 Oct 2020 22:28:55 +0000
Resent-Message-Id: <E1kO74J-0004Js-5u@lyra.w3.org>
Received: from mimas.w3.org ([128.30.52.79]) by lyra.w3.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <w@felixhandte.com>) id 1kO74G-0004J7-E9 for ietf-http-wg@listhub.w3.org; Thu, 01 Oct 2020 22:28:52 +0000
Received: from felixhandte.com ([54.172.180.13] helo=mail.felixhandte.com) by mimas.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <w@felixhandte.com>) id 1kO74F-0001iM-2k for ietf-http-wg@w3.org; Thu, 01 Oct 2020 22:28:52 +0000
Received: from [100.109.69.77] (unknown [163.114.130.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.felixhandte.com (Postfix) with ESMTPSA id C76B533776; Thu, 1 Oct 2020 22:28:39 +0000 (UTC)
To: ietf-http-wg@w3.org, alex@strugee.net
References: <622b20db1c96220b24718cfb80f4b5e8@strugee.net>
From: "W. Felix Handte" <w@felixhandte.com>
Message-ID: <b1f987e4-ca1c-2314-af01-5e6a813d21f4@felixhandte.com>
Date: Thu, 1 Oct 2020 18:28:38 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <622b20db1c96220b24718cfb80f4b5e8@strugee.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Received-SPF: pass client-ip=54.172.180.13; envelope-from=w@felixhandte.com; helo=mail.felixhandte.com
X-W3C-Hub-Spam-Status: No, score=-4.2
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, NICE_REPLY_A=-0.26, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_WL=-1
X-W3C-Scan-Sig: mimas.w3.org 1kO74F-0001iM-2k f6290bcbef839b3ca48fe83730b5d4a7
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Redirections to `Content-Encoding: encrypted` payloads
Archived-At: <https://www.w3.org/mid/b1f987e4-ca1c-2314-af01-5e6a813d21f4@felixhandte.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/38073
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <https://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

Hi Alex,

It's been a long time since I've played around with it, but it's worth 
pointing out that a solution already exists for (a narrow interpretation 
of) the use case you describe: HTTP Live Streaming lets you distribute 
encrypted video segments and pass the decryption key in the playlist 
metadata [0].

[0] https://tools.ietf.org/html/rfc8216#section-4.3.2.4

- Felix