Re: [media-types] Request feedback for proposed media-type registration

Mark Callow <khronos@callow.im> Tue, 31 March 2020 22:54 UTC

Return-Path: <khronos@callow.im>
X-Original-To: media-types@ietfa.amsl.com
Delivered-To: media-types@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BF4F3A0C4A for <media-types@ietfa.amsl.com>; Tue, 31 Mar 2020 15:54:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.774
X-Spam-Level:
X-Spam-Status: No, score=0.774 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_SOFTFAIL=0.972, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=callow.im
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 QWjYYglmrvbv for <media-types@ietfa.amsl.com>; Tue, 31 Mar 2020 15:54:28 -0700 (PDT)
Received: from pechora1.lax.icann.org (pechora1.icann.org [IPv6:2620:0:2d0:201::1:71]) (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 584EF3A0C4D for <media-types@ietf.org>; Tue, 31 Mar 2020 15:54:27 -0700 (PDT)
Received: from ssd1.hungerhost.com (ssd1.hungerhost.com [107.161.31.220]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pechora1.lax.icann.org (Postfix) with ESMTPS id 684771E0483 for <media-types@iana.org>; Tue, 31 Mar 2020 22:54:27 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=callow.im; s=default; h=Message-Id:In-Reply-To:To:References:Date:Subject:Mime-Version: Content-Type:From:Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=WZ1B0zwABiBSAm6doEWPiLQTraiGI+V5q4g+xd/00gQ=; b=GYFxECMjJLI/L+2ZvlPulZ8SpX wKKd1J/vhX3Fo/WEXwzDnejXbNgbxN5dmg5mm5z9uOsxGWscuSabZOCczr2SzF/N28R3drx2zSPpX LA70KiJZdZl6ohdmyYyJX8tyJV47WQQnsNDr3mxkYSz46MDIdNRQJfz1JWZG1Ein/hvE=;
Received: from [73.71.117.63] (port=54544 helo=[192.168.8.6]) by ssd1.hungerhost.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93) (envelope-from <khronos@callow.im>) id 1jJPlm-0006tL-3G for media-types@iana.org; Tue, 31 Mar 2020 18:54:06 -0400
From: Mark Callow <khronos@callow.im>
Content-Type: multipart/signed; boundary="Apple-Mail=_BEDC476E-D585-4C41-BCDA-A5A8BC75A350"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.14\))
Date: Tue, 31 Mar 2020 15:54:04 -0700
References: <35D0A921-87E6-43D3-A0D8-E7578C0FFE15@callow.im>
To: media-types@iana.org
In-Reply-To: <35D0A921-87E6-43D3-A0D8-E7578C0FFE15@callow.im>
Message-Id: <2171643F-B01A-4B92-966E-BD888B537EF5@callow.im>
X-Mailer: Apple Mail (2.3445.104.14)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - ssd1.hungerhost.com
X-AntiAbuse: Original Domain - iana.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - callow.im
X-Get-Message-Sender-Via: ssd1.hungerhost.com: authenticated_id: khronos@callow.im
X-Authenticated-Sender: ssd1.hungerhost.com: khronos@callow.im
X-Source:
X-Source-Args:
X-Source-Dir:
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/ePHqHKmtPopFYJVbAi0_FIAdVZ4>
Subject: Re: [media-types] Request feedback for proposed media-type registration
X-BeenThere: media-types@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." <media-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/media-types>, <mailto:media-types-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/media-types/>
List-Post: <mailto:media-types@ietf.org>
List-Help: <mailto:media-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/media-types>, <mailto:media-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Mar 2020 22:54:31 -0000

As requested, please advise on the following. Sending again in case it was not forwarded to the list.

Regards

    -Mark

> On Mar 23, 2020, at 16:56, Mark Callow <khronos@callow.im> wrote:
> 
> Greetings Media-Type Experts
> 
> I write to you as the point of contact for an existing media type in the standards tree, image/ktx which is promulgated by the Khronos Group.
> 
> Khronos has almost completed a new version of the specification known formally as The KTX File Format Version 2 <http://github.khronos.org/KTX-Specification/> and wishes to ensure this can be used within the Media-Type framework. Version 2 is significantly different from the existing version to the point where software that knows only about Version 1 will not be able to do anything useful with a Version 2 file. The purpose of both formats is the same, to be a container for texture data for 3D APIs. We expect Version 2 to have significant uptake due to its powerful features, including jpeg-levels of compression for transmitting texture data with transcoding to GPU block-compressed formats for use after receipt. It is likely to supplant version 1.
> 
> I should point out that both versions differs from a traditional image file in that the payload can consist of multiple possibly disparate images for cases such as mipmaps, array textures, cube maps or 3d textures.
> 
> The most likely course seems to be to register a new Media-Type image/ktx2. A putative registration application is attached. However I want to consult the experts here as to whether there are any alternative approaches that would be better such as using the tree or facets. For example creating a new tree image/texture/{ktx1,ktx2} or, using facets instead, image/texture.{ktx1,ktx2} or something else entirely. Maybe even just adding a new magic number to the existing registration.
> 
> Please advise. If a new Media-Type is the right way to go, then please review the attached draft registration.
> 
> Regards
> 
>     -Mark
> 
> <ktx-media-registration.txt>
> 
>