Re: [Hls-interest] File extension and MIME-Type for an HLS encryption key

Roger Pantos <rpantos@apple.com> Thu, 01 July 2021 16:21 UTC

Return-Path: <rpantos@apple.com>
X-Original-To: hls-interest@ietfa.amsl.com
Delivered-To: hls-interest@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B2303A0909; Thu, 1 Jul 2021 09:21:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=apple.com
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 9ja_PsmOdijX; Thu, 1 Jul 2021 09:21:01 -0700 (PDT)
Received: from rn-mailsvcp-ppex-lapp35.apple.com (rn-mailsvcp-ppex-lapp35.rno.apple.com [17.179.253.44]) (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 2DF6A3A0913; Thu, 1 Jul 2021 09:21:00 -0700 (PDT)
Received: from pps.filterd (rn-mailsvcp-ppex-lapp35.rno.apple.com [127.0.0.1]) by rn-mailsvcp-ppex-lapp35.rno.apple.com (8.16.1.2/8.16.1.2) with SMTP id 161GDYBt024618; Thu, 1 Jul 2021 09:21:00 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=from : message-id : content-type : mime-version : subject : date : in-reply-to : cc : to : references; s=20180706; bh=Npsw98fgDfUIuUbTfPhbmJIClrxnIKyRw6GObpE5QuA=; b=otWzwbeWEGlocYYULO7BVXi7/6pXneXOPka5/w2HZJbWQqAq+FpWLHYdEKm4eVs1UOXn DVAM6c+vOHJBzhzCSmmYf1XmjA5d5RTCuJn8EZ8C6RPKGyc3+7J0Pbsf7QkMVZVjh14U xSyaWR0lwCRPmYXEy7PmVzJQECMhKQhjXdRcS6aSZYCZXDWSJBy+55wj/5RYDfmEQnNa m/ph4pU0iwRAvC4tx6g1E4Zm+tn7yz4DEooUviBYENS2VtWXCOWVx3ub4NEcR0nKffjI 9Kq2w46I/Cw7tlWp/IyUOaJslAHDMQQGJSNea3cyb8U/y7AgGcOYCtFvdzZa60ka6x/C 2A==
Received: from rn-mailsvcp-mta-lapp04.rno.apple.com (rn-mailsvcp-mta-lapp04.rno.apple.com [10.225.203.152]) by rn-mailsvcp-ppex-lapp35.rno.apple.com with ESMTP id 39dys7rcvh-11 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 01 Jul 2021 09:21:00 -0700
Received: from rn-mailsvcp-mmp-lapp04.rno.apple.com (rn-mailsvcp-mmp-lapp04.rno.apple.com [17.179.253.17]) by rn-mailsvcp-mta-lapp04.rno.apple.com (Oracle Communications Messaging Server 8.1.0.9.20210415 64bit (built Apr 15 2021)) with ESMTPS id <0QVK00BS9QQZXYJ0@rn-mailsvcp-mta-lapp04.rno.apple.com>; Thu, 01 Jul 2021 09:20:59 -0700 (PDT)
Received: from process_milters-daemon.rn-mailsvcp-mmp-lapp04.rno.apple.com by rn-mailsvcp-mmp-lapp04.rno.apple.com (Oracle Communications Messaging Server 8.1.0.9.20210415 64bit (built Apr 15 2021)) id <0QVK00800QOXRH00@rn-mailsvcp-mmp-lapp04.rno.apple.com>; Thu, 01 Jul 2021 09:20:59 -0700 (PDT)
X-Va-A:
X-Va-T-CD: 81ca60fce39c2560b6c4a7e5841f9b8f
X-Va-E-CD: 5d0816994e287319fd28096725e5ba7e
X-Va-R-CD: f4ab09f3ef2b9a7d2cb202312a980158
X-Va-CD: 0
X-Va-ID: 26c930d8-30db-42cb-b47c-445440de92f1
X-V-A:
X-V-T-CD: 81ca60fce39c2560b6c4a7e5841f9b8f
X-V-E-CD: 5d0816994e287319fd28096725e5ba7e
X-V-R-CD: f4ab09f3ef2b9a7d2cb202312a980158
X-V-CD: 0
X-V-ID: 16bc3b84-7482-481e-a968-4e36642ca021
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.391, 18.0.790 definitions=2021-07-01_09:2021-07-01, 2021-07-01 signatures=0
Received: from smtpclient.apple (unknown [17.11.41.152]) by rn-mailsvcp-mmp-lapp04.rno.apple.com (Oracle Communications Messaging Server 8.1.0.9.20210415 64bit (built Apr 15 2021)) with ESMTPSA id <0QVK00QHWQQZZH00@rn-mailsvcp-mmp-lapp04.rno.apple.com>; Thu, 01 Jul 2021 09:20:59 -0700 (PDT)
From: Roger Pantos <rpantos@apple.com>
Message-id: <870719E2-8E0B-4B76-AB24-B4BCED545250@apple.com>
Content-type: multipart/alternative; boundary="Apple-Mail=_90DECE12-CD64-4F9A-B728-D61DE2EC74DC"
MIME-version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
Date: Thu, 01 Jul 2021 09:20:58 -0700
In-reply-to: <5AA86F40-F359-4F0E-878E-E61AF916DF28@akamai.com>
Cc: "hls-interest@ietf.org" <hls-interest@ietf.org>
To: "Law, Will" <wilaw=40akamai.com@dmarc.ietf.org>
References: <5AA86F40-F359-4F0E-878E-E61AF916DF28@akamai.com>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.391, 18.0.790 definitions=2021-07-01_09:2021-07-01, 2021-07-01 signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/hls-interest/SgmdjFW37ldkeR035ifj4TLhNFg>
Subject: Re: [Hls-interest] File extension and MIME-Type for an HLS encryption key
X-BeenThere: hls-interest@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussions about HTTP Live Streaming \(HLS\)." <hls-interest.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hls-interest>, <mailto:hls-interest-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hls-interest/>
List-Post: <mailto:hls-interest@ietf.org>
List-Help: <mailto:hls-interest-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hls-interest>, <mailto:hls-interest-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Jul 2021 16:21:06 -0000


> On Jun 29, 2021, at 9:02 AM, Law, Will <wilaw=40akamai.com@dmarc.ietf.org> wrote:
> 
> Is there any consensus on what the file extension and MIME-Type should be for an encryption key delivered to a HLS  player? The spec defines no constraints on this question.
>  
> The DASH IF is standardizing an Ingest Specification which covers the ingest of CMAF-based content in both HLS and DASH formats. We’ll likely choose ‘.key’ as the file extension and are considering ‘application/octet-stream’ as the Mime-Type in the absence of objections. Asking here in case there is a de-facto industry standard already in use, or opinion on whether we should go to the length of registering a new ‘encryption key’ MIME-type with IANA.

For what it's worth, I haven't seen reports of the decryption key filename extension or MIME type causing interop issues, so I don't have a strong feeling about this one way or the other.

I'm not aware of a common industry practice in this area. As Valentijn noted, .key is used by Apple's Keynote app so that's a consideration. Maybe .lic for license?

I think that application/octet-stream is fine.


Roger.