
From nobody Thu Mar  5 05:51:00 2020
Return-Path: <torsten@lodderstedt.net>
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 6B8283A1508 for <media-types@ietfa.amsl.com>; Thu,  5 Mar 2020 05:50:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, SPF_FAIL=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=lodderstedt.net
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 c2l9XXViLvz9 for <media-types@ietfa.amsl.com>; Thu,  5 Mar 2020 05:50:56 -0800 (PST)
Received: from pechora8.dc.icann.org (pechora8.icann.org [192.0.46.74]) (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 09BA03A1506 for <media-types@ietf.org>; Thu,  5 Mar 2020 05:50:55 -0800 (PST)
Received: from mail-wr1-x433.google.com (mail-wr1-x433.google.com [IPv6:2a00:1450:4864:20::433]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pechora8.dc.icann.org (Postfix) with ESMTPS id E2C90C08EE for <media-types@iana.org>; Thu,  5 Mar 2020 13:50:53 +0000 (UTC)
Received: by mail-wr1-x433.google.com with SMTP id v9so502169wrf.10 for <media-types@iana.org>; Thu, 05 Mar 2020 05:50:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lodderstedt.net; s=google; h=from:mime-version:subject:message-id:date:cc:to; bh=0T1W9QqsxsVrCX1R05/RP1P3oB7mP7cRRqquQwLNMKU=; b=MZIR/wzQk4CP0d1X/89zjgJEDywGG2zM3/sHLD/HSVkH5sslA/YgQ5CFsv0DN22kuG TOnJpiQb1c2gU/rHX7N+jXcS5j0xH6I/Ho8wpqE5WstHKR7aCoW+6cVljHRZ9KiTpm3h tgOlqXS40+lmJQJwRMhVb09f+kkx2JksIQjD7AA+w7F9IrnG1nB9gnoOtkOE4/uFzXcA G+pESa85HoBrCMnJlSOruXNnIGC1HOqR/zASVX+sP5g3Yo3rB7JG5/slQNZv+g9qQ47y t+O5PJwq7mSrV5ZfG+LghQOqhy9CyzwqjCPNick5IrtgBjA5mJFTOXiUZta6lE1mswvO +CFg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:message-id:date:cc:to; bh=0T1W9QqsxsVrCX1R05/RP1P3oB7mP7cRRqquQwLNMKU=; b=GCoC8zD4+u+YNFvE7s/zK592PBjLqpI4gDJnG72jw8DInh1BZLr6UCpOsd64F//pTT Z9p+CKi3iZKzn2lY9+fgNexQc0Y0n2dcZfRLBmc0nWLQgPCb9FZx00wNgHTmdNchkrZD Gs2yAT+KWQMvLm9AOTJKuE/dRo6NsYen2xPq9A8Q87D4abpsWQ/6t2xhlX7QkGt7ZVoU LZdvR1TkQQchRFOhY8ekHE+enl/awz+00mSIg/81hYteh594OwexaxUXBes7cSjQxASF Pu2PsEno26IABi0lYlrRriiUvoLsbkpZurN4YyQbx2aYUdBwVtJERShw/qf1pFHAzCwY 71oQ==
X-Gm-Message-State: ANhLgQ3NHpCTufjAaMhg4jVu0A49D7ddEqpXfuxKJBgPtDulfIPLXEVi vOcxlM1iMysGyFK0RQ1RyfSYaiLBooM=
X-Google-Smtp-Source: ADFU+vudakgzfD3vuEInLnI38PP2OjF99fQI6WnbsuiqIi4L79EYr/ur0aOnMoIC3M4mQQe34xmwGg==
X-Received: by 2002:adf:fc81:: with SMTP id g1mr10833140wrr.410.1583416232852;  Thu, 05 Mar 2020 05:50:32 -0800 (PST)
Received: from p200300eb8f11fdfef90b201319ec994d.dip0.t-ipconnect.de (p200300EB8F11FDFEF90B201319EC994D.dip0.t-ipconnect.de. [2003:eb:8f11:fdfe:f90b:2013:19ec:994d]) by smtp.gmail.com with ESMTPSA id c72sm3342362wme.35.2020.03.05.05.50.31 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 05 Mar 2020 05:50:32 -0800 (PST)
From: Torsten Lodderstedt <torsten@lodderstedt.net>
Content-Type: multipart/signed; boundary="Apple-Mail=_A1BEF8AF-341F-46EE-8CCF-9E75436D3991"; protocol="application/pkcs7-signature"; micalg=sha-256
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.60.0.2.5\))
Message-Id: <2917D6D2-827E-4D33-B91D-4B0923668C1F@lodderstedt.net>
Date: Thu, 5 Mar 2020 14:50:31 +0100
Cc: Vladimir Dzhuvinov <vladimir@connect2id.com>
To: media-types@iana.org
X-Mailer: Apple Mail (2.3608.60.0.2.5)
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/3w1pZsOk8fpPmeUmSLA12VyHteg>
Subject: [media-types] notice of a potential standards tree 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: Thu, 05 Mar 2020 13:50:57 -0000

--Apple-Mail=_A1BEF8AF-341F-46EE-8CCF-9E75436D3991
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi all,=20

I sending this message to to inform you that =
draft-ietf-oauth-jwt-introspection-response wants to register a new =
media type "application/token-introspection+jwt=E2=80=9D.

Please find the description of the new media type at =
https://tools.ietf.org/html/draft-ietf-oauth-jwt-introspection-response-08=
#section-11.3.1

best regards,
Torsten.=20



--Apple-Mail=_A1BEF8AF-341F-46EE-8CCF-9E75436D3991
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCCC38w
ggT0MIID3KADAgECAhBpfEIkHQiWmzF6zDsgdF+DMA0GCSqGSIb3DQEBCwUAMIGNMQswCQYDVQQG
EwJJVDEQMA4GA1UECAwHQmVyZ2FtbzEZMBcGA1UEBwwQUG9udGUgU2FuIFBpZXRybzEjMCEGA1UE
CgwaQWN0YWxpcyBTLnAuQS4vMDMzNTg1MjA5NjcxLDAqBgNVBAMMI0FjdGFsaXMgQ2xpZW50IEF1
dGhlbnRpY2F0aW9uIENBIEcyMB4XDTIwMDIyMzE3MjEzOVoXDTIxMDIyMzE3MjEzOVowIjEgMB4G
A1UEAwwXdG9yc3RlbkBsb2RkZXJzdGVkdC5uZXQwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEK
AoIBAQCrIaCISpAU98m6ZkDyUR3My5imAF4TKQk8eqo+oQ06PTWT/3yJXujVCjjOqOl8p11v/RoN
Gf8zqYbBsqGBuJx2NyxFmAnmCjcbnxihQdcmuxLm6izvxr2MawOovDheMXnfmGy/Ns5Fs6bd+M5F
jCNhP+Gljvgm/SFq1skvs7YUX2FxZmh+xPMm3FZ/a6Lyhkrd3JHzEqv8VWY69Aehezg39OuPJEpb
IdjK/eBcmaIG0qn5RQdXLByJYfXhepyVAZPJT5rAgaIQL/IjSIVInxf3FxOv+ELMAErclws6mKzy
zkY2JiItPEpKWzAWGCxCX2o0JjVj1f7xgaunLfJ+Ec0lAgMBAAGjggG4MIIBtDAMBgNVHRMBAf8E
AjAAMB8GA1UdIwQYMBaAFGvyjZ5owSUEH1E0V/YWXJTqTWkaMH4GCCsGAQUFBwEBBHIwcDA7Bggr
BgEFBQcwAoYvaHR0cDovL2NhY2VydC5hY3RhbGlzLml0L2NlcnRzL2FjdGFsaXMtYXV0Y2xpZzIw
MQYIKwYBBQUHMAGGJWh0dHA6Ly9vY3NwMDkuYWN0YWxpcy5pdC9WQS9BVVRIQ0wtRzIwIgYDVR0R
BBswGYEXdG9yc3RlbkBsb2RkZXJzdGVkdC5uZXQwRwYDVR0gBEAwPjA8BgYrgR8BGAEwMjAwBggr
BgEFBQcCARYkaHR0cHM6Ly93d3cuYWN0YWxpcy5pdC9hcmVhLWRvd25sb2FkMB0GA1UdJQQWMBQG
CCsGAQUFBwMCBggrBgEFBQcDBDBIBgNVHR8EQTA/MD2gO6A5hjdodHRwOi8vY3JsMDkuYWN0YWxp
cy5pdC9SZXBvc2l0b3J5L0FVVEhDTC1HMi9nZXRMYXN0Q1JMMB0GA1UdDgQWBBSuRfshihlGSEJ7
2UeyOZRJ1YYyMDAOBgNVHQ8BAf8EBAMCBaAwDQYJKoZIhvcNAQELBQADggEBAH/3ECMSOoOLiwCe
GsBj/WWnUhXvZyHmz3LW0DVdH3s30b2HWpomEVNDN3cWt4QSRhISqV0xyyChL6THhDY+Um2mo+z/
L5fxHd3MjhzvYKwUtLUJdWRgymlUBO9zNKi/IMVYv3O+mpOHuQrgtMaV9luDPRYPZrhF9y/InTZE
tb+FOrF9ykIRlYgMzqSKjuqFmmYO4d6GkbgfGKFZsAjkySjM9BUBLb70MdysOTxZ/HtZguIKfZ4q
CveZ9ZKe+LGsIpt5bFAs1LHIMBUlTCsuVIq2lD3TmScWbELn+Ace7WwKc+08GqOWZzUot5fkiIx3
/crnd7HTmUfqi0yCylHY62wwggaDMIIEa6ADAgECAhBP3hBL7ZVb3outZYfMQV7jMA0GCSqGSIb3
DQEBCwUAMGsxCzAJBgNVBAYTAklUMQ4wDAYDVQQHDAVNaWxhbjEjMCEGA1UECgwaQWN0YWxpcyBT
LnAuQS4vMDMzNTg1MjA5NjcxJzAlBgNVBAMMHkFjdGFsaXMgQXV0aGVudGljYXRpb24gUm9vdCBD
QTAeFw0xOTA5MjAwNzEyMDVaFw0zMDA5MjIxMTIyMDJaMIGNMQswCQYDVQQGEwJJVDEQMA4GA1UE
CAwHQmVyZ2FtbzEZMBcGA1UEBwwQUG9udGUgU2FuIFBpZXRybzEjMCEGA1UECgwaQWN0YWxpcyBT
LnAuQS4vMDMzNTg1MjA5NjcxLDAqBgNVBAMMI0FjdGFsaXMgQ2xpZW50IEF1dGhlbnRpY2F0aW9u
IENBIEcyMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAt2hzetk81C/73GfKPc6UfP+J
Gc7aGmPzGUeQJ1go3CdFpsBPonREDXUDdmRCIRkTDroH30RLsTO/0hEFiYjCyvvbSVSm05sXkvfJ
XOXefNqK21fBayr4JCgMRyLVwqRYXlKI7bb42nYSm7YcXGTDmdcydmJuuqcLqFQawWiBMNRRVEi4
uW5uXBZgWGmq8NoKH/+5xGBFbf6tNTWcGhPVceResuwK155+OiH6jTW01Na8aLj7c7IAGJ0Y9e6h
iHtRthfW7SwbU7ys73a3nNXv8Kv9XNr0RvJKHoOsKqxjffew3GKQrMXIHB5tm/je3XEnIxUT8JG3
sEsk7IfF3VirSwIDAQABo4IB/jCCAfowDwYDVR0TAQH/BAUwAwEB/zAfBgNVHSMEGDAWgBRS2Ig6
yJ94Zu2J83s4cJTJAgI20DBBBggrBgEFBQcBAQQ1MDMwMQYIKwYBBQUHMAGGJWh0dHA6Ly9vY3Nw
MDUuYWN0YWxpcy5pdC9WQS9BVVRILVJPT1QwRQYDVR0gBD4wPDA6BgRVHSAAMDIwMAYIKwYBBQUH
AgEWJGh0dHBzOi8vd3d3LmFjdGFsaXMuaXQvYXJlYS1kb3dubG9hZDAnBgNVHSUEIDAeBggrBgEF
BQcDAgYIKwYBBQUHAwQGCCsGAQUFBwMJMIHjBgNVHR8EgdswgdgwgZaggZOggZCGgY1sZGFwOi8v
bGRhcDA1LmFjdGFsaXMuaXQvY24lM2RBY3RhbGlzJTIwQXV0aGVudGljYXRpb24lMjBSb290JTIw
Q0EsbyUzZEFjdGFsaXMlMjBTLnAuQS4lMmYwMzM1ODUyMDk2NyxjJTNkSVQ/Y2VydGlmaWNhdGVS
ZXZvY2F0aW9uTGlzdDtiaW5hcnkwPaA7oDmGN2h0dHA6Ly9jcmwwNS5hY3RhbGlzLml0L1JlcG9z
aXRvcnkvQVVUSC1ST09UL2dldExhc3RDUkwwHQYDVR0OBBYEFGvyjZ5owSUEH1E0V/YWXJTqTWka
MA4GA1UdDwEB/wQEAwIBBjANBgkqhkiG9w0BAQsFAAOCAgEAYES6GaKrcvsOQZpEwboVOb2dri/f
Jrcpb7GSEW9JmA+Kep4GLmp9X50Iv8EK478kwf2aAjnPnsOdiItALcIgecS1qVxN+EY+V5GCNEy4
VAsB5gzlQBmKI9P4PxLt9pnQJneCVEvDnVBMZAllIL5s3uaCiIEb8eYZqG8taOWSM1nqjoCZULcc
hXWYajBqaJg0RUOZ6f5IB0lb26HA/7EUVmh1nSVglDoUeD7elINXHph0z3if1722UydcoH4Jj3Za
Y9dtQ4wJSNhSZOzES72UkS6we/556FOGs7oeJWuQe8Rq2EeeSGmGliZKUbYo4jB/C2omMn0L4QwI
5wMNrWd2FRNUUwxMBmbJYtEaDRTQ72HPA8DnbRkvRDSJkjsToqU6ZpBlBf4s5EwrhXqFVb2rM9mG
CPDZJi7Hw3y8BYD/d3iTL6PW5UjOTSpFcnSIP4HW5PI6MTHXl+ab6ajCnvJw6E1TGLh3zJypv5CQ
8Ftm0z7MKLt5Zr2E4jojZXeZn1sUpSqidZyp9mG/LYMRmHMkthDRnDnO2tHv5+YOO4cUEbTt5Bww
E5RPjqovsnedyd5SijIK+k1MCXFLMTfERz3qUN3i/fwueXcGy4jEf2n/FvYsEY3GBHXZCMVWPffB
fbl/ITjs9Q9NG37bAEm/mg2yNq02NLjDbQIKgt9W0aBU9SsxggOpMIIDpQIBATCBojCBjTELMAkG
A1UEBhMCSVQxEDAOBgNVBAgMB0JlcmdhbW8xGTAXBgNVBAcMEFBvbnRlIFNhbiBQaWV0cm8xIzAh
BgNVBAoMGkFjdGFsaXMgUy5wLkEuLzAzMzU4NTIwOTY3MSwwKgYDVQQDDCNBY3RhbGlzIENsaWVu
dCBBdXRoZW50aWNhdGlvbiBDQSBHMgIQaXxCJB0Ilpsxesw7IHRfgzANBglghkgBZQMEAgEFAKCC
AdcwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMjAwMzA1MTM1MDMx
WjAvBgkqhkiG9w0BCQQxIgQg2OUr7i+IPWqfyWtBi/MZAsNKiDMyRy2h49QIOcVFhygwgbMGCSsG
AQQBgjcQBDGBpTCBojCBjTELMAkGA1UEBhMCSVQxEDAOBgNVBAgMB0JlcmdhbW8xGTAXBgNVBAcM
EFBvbnRlIFNhbiBQaWV0cm8xIzAhBgNVBAoMGkFjdGFsaXMgUy5wLkEuLzAzMzU4NTIwOTY3MSww
KgYDVQQDDCNBY3RhbGlzIENsaWVudCBBdXRoZW50aWNhdGlvbiBDQSBHMgIQaXxCJB0Ilpsxesw7
IHRfgzCBtQYLKoZIhvcNAQkQAgsxgaWggaIwgY0xCzAJBgNVBAYTAklUMRAwDgYDVQQIDAdCZXJn
YW1vMRkwFwYDVQQHDBBQb250ZSBTYW4gUGlldHJvMSMwIQYDVQQKDBpBY3RhbGlzIFMucC5BLi8w
MzM1ODUyMDk2NzEsMCoGA1UEAwwjQWN0YWxpcyBDbGllbnQgQXV0aGVudGljYXRpb24gQ0EgRzIC
EGl8QiQdCJabMXrMOyB0X4MwDQYJKoZIhvcNAQEBBQAEggEAdk1JiVIbMEheCNkaBJsDVb7/Kdul
Le6Vew60ysY+1vxM3r61bWKPApFFiOhSlf4iIqTfsFSSNW9GFlY7dWoLoY22RiwSCj2uxJHo3fdu
pSZy77xiGaQYUXkBunm38Z9HnBcKgyN58W+9ilkSgOQqOZhmYYi6Z6+rHZLuN2wXEO1J5SOzlXDH
87BVk/pOKQs8B9FclKuj9p4p78+ocSH8Jyx4jOS5nbICZWiSJnCbGf4dMzDls25ClZbjtPLxsd8Q
vKPj/reEGXswyQ9qGVSmA0EdJH9LfQ3UaVNsguFRWlN4QzPLDJm8FvZ+UENXrO178hQjsF0rEroj
wQfrRqq2XAAAAAAAAA==
--Apple-Mail=_A1BEF8AF-341F-46EE-8CCF-9E75436D3991--


From nobody Sat Mar  7 18:02:01 2020
Return-Path: <neilj@fastmailteam.com>
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 85B4B3A1F40 for <media-types@ietfa.amsl.com>; Sat,  7 Mar 2020 18:01:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.319
X-Spam-Level: 
X-Spam-Status: No, score=-1.319 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, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmailteam.com header.b=jWJztedq; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=QG1rz9fJ
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 NxGaNQvRLI8X for <media-types@ietfa.amsl.com>; Sat,  7 Mar 2020 18:01:48 -0800 (PST)
Received: from pechora8.dc.icann.org (pechora8.icann.org [IPv6:2620:0:2830:201::1:74]) (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 CE3DB3A1F30 for <media-types@ietf.org>; Sat,  7 Mar 2020 18:01:48 -0800 (PST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pechora8.dc.icann.org (Postfix) with ESMTPS id D6A1CC018E for <media-types@iana.org>; Sun,  8 Mar 2020 02:01:45 +0000 (UTC)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id AFC7C21B2C for <media-types@iana.org>; Sat,  7 Mar 2020 21:01:24 -0500 (EST)
Received: from imap7 ([10.202.2.57]) by compute4.internal (MEProxy); Sat, 07 Mar 2020 21:01:24 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=mime-version:message-id:date:from:to:subject :content-type; s=fm2; bh=jPisJ6NHy+e3YmrMC8RdjhRtKqNGzqXF+J+1DQX oYxc=; b=jWJztedqiVJ+MsGKgriHWpypZt0DMFgtaYXfruBUEspL5ofmpQaz6iq KrDpSfKdPPRVprxXWgju+D4lXS2u/kt7arNVcktZyGIqGi+4CHehfGTZKr2DlGtm vg3udLWLsiJcNADwOgsNgjqoQDjZJJNlg/0LDRTgNEk7ElYqNG9DUQOZRPFak7bM siSkOI2JvHVXa1FhkEzXn20xP9I7bbNjMmJZq5Hz5D2X3uNHExgvgScUtRZiNIkr ajEteMxZUeedMRc9O/4dG0i/xLG2dBGKQO0BguxX45/91RWSqnDLXSs3tb+GNhwa 8I23067kP25nXWbuQxa/Vw4cUWi/W8w==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:message-id :mime-version:subject:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=jPisJ6NHy+e3YmrMC8RdjhRtKqNGz qXF+J+1DQXoYxc=; b=QG1rz9fJcy3l/3xp6/hFhC3kuR6tlXE4xai86sq3gLAxp xzmhQ1cdV7eMXFW3Y+daMZqAz8RgbYm1YUr0xs4xNw1s3tk8AvYGCiI9xYAtdQJi bn/jnyuMAuEd3MZ5LP2brav3gKSdIV4V+iZhFR9U9nN0zk3Letexsnk30idU9fbL VXiQiE/ewplGUhHlA+6ktZNcfQfs6jmQJXdUrzBsThtSU+ZCJcPCh+l4yoq7TnQH GI7QlTH6Oc6AoWUAJ+KyA6qDqd2zvdU7iV+mijiHnGLT9fJC30h5Le6uit3rLW7R oWWpKIQ6vyZ6tlmwZHjJ+gCfP8NH4y4BmAVV3BHVg==
X-ME-Sender: <xms:9FFkXpGfxbILdXpxsXJGpzjF0jcYovmBypjVmGp4D-NKWUe9YFUz5Q>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedrudduhedggeduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfffhffvufgtsegrtderre erredtnecuhfhrohhmpedfpfgvihhlucflvghnkhhinhhsfdcuoehnvghilhhjsehfrghs thhmrghilhhtvggrmhdrtghomheqnecuffhomhgrihhnpehivghtfhdrohhrghenucevlh hushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehnvghilhhjsehf rghsthhmrghilhhtvggrmhdrtghomh
X-ME-Proxy: <xmx:9FFkXpeZlwpToYcuqiSx14Hpg2CFIO2ji2_gLzyuhahotzJSudLBIg> <xmx:9FFkXqhTl5SUKqcp3-R6CRQTyASnZ-bA1sB26YhewG-9XhIt3vq0Fw> <xmx:9FFkXuV8Cf_Q3z2sERetukkvlP3o1fJ02oyWnE7e8hU-HxvqwMXgjA> <xmx:9FFkXkX1aECvPB2GKq6Qx3CdcKxKLS9BLe6J4jGoe-TaPpE_nV3VNw>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id E83B2180091; Sat,  7 Mar 2020 21:01:23 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.7-991-g5a577d3-fmstable-20200305v3
Mime-Version: 1.0
Message-Id: <83caa50c-082d-4689-9217-a076eead834b@beta.fastmail.com>
Date: Sun, 08 Mar 2020 13:00:39 +1100
From: "Neil Jenkins" <neilj@fastmailteam.com>
To: media-types@iana.org
Content-Type: multipart/alternative; boundary=c82a351b8e1340938f5595a6702982b7
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/R_DxJD5ro7JMbqzjUuAUz51vafY>
Subject: [media-types] Notice of intended registration of "jscalendar+json"
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: Sun, 08 Mar 2020 02:02:01 -0000

--c82a351b8e1340938f5595a6702982b7
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: quoted-printable

In accordance with Section 5.1 of of RFC6838 <https://tools.ietf.org/htm=
l/rfc6838#section-5.1>, I wish to notify the list of the intended regist=
ration of a new media type in the standards track document JSCalendar <h=
ttps://tools.ietf.org/html/draft-ietf-calext-jscalendar>. I welcome any =
comments or feedback. The intended registration is as follows:

   Type name:  application

   Subtype name:  jscalendar+json

   Required parameters:  type

      The "type" parameter conveys the type of the JSCalendar data in
      the body part, with the value being one of "jsevent", "jstask", or=

      "jsgroup".  The parameter MUST NOT occur more than once.  It MUST
      match the value of the "@type" property of the JSON-formatted
      JSCalendar object in the body.

   Optional parameters:  none

   Encoding considerations:  Same as encoding considerations of
      application/json as specified in RFC8529, Section=C2=A011 <https:/=
/tools.ietf.org/html/rfc8529#section-11> [RFC8259 <https://tools.ietf.or=
g/html/rfc8259>].

   Security considerations:  See Section 7 <https://tools.ietf.org/html/=
draft-ietf-calext-jscalendar-25#section-7> of this document.

   Interoperability considerations:  This media type provides an
      alternative to iCalendar, jCal and proprietary JSON-based
      calendaring data formats.

   Published specification:  This specification.

   Applications that use this media type:  Applications that currently
      make use of the text/calendar and application/calendar+json media
      types can use this as an alternative.  Similarly, applications
      that use the application/json media type to transfer calendaring
      data can use this to further specify the content.

   Fragment identifier considerations:  N/A

   Additional information:

      Magic number(s):  N/A

      File extensions(s):  N/A

      Macintosh file type code(s):  N/A

   Person & email address to contact for further information:
      calsify@ietf.org

   Intended usage:  COMMON

   Restrictions on usage:  N/A

   Author:  See the "Author's Address" section of this document.

   Change controller:  IETF

Cheers,
Neil.
--c82a351b8e1340938f5595a6702982b7
Content-Type: text/html

<!DOCTYPE html><html><head><title></title><style type="text/css">p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div>In accordance with <a href="https://tools.ietf.org/html/rfc6838#section-5.1">Section 5.1 of of RFC6838</a>, I wish to notify the list of the intended registration of a new media type in the standards track document <a href="https://tools.ietf.org/html/draft-ietf-calext-jscalendar">JSCalendar</a>. I welcome any comments or feedback. The intended registration is as follows:<br></div><div><br></div><pre>   Type name:  application

   Subtype name:  jscalendar+json

   Required parameters:  type

      The "type" parameter conveys the type of the JSCalendar data in
      the body part, with the value being one of "jsevent", "jstask", or
      "jsgroup".  The parameter MUST NOT occur more than once.  It MUST
      match the value of the "@type" property of the JSON-formatted
      JSCalendar object in the body.

   Optional parameters:  none

   Encoding considerations:  Same as encoding considerations of
      application/json as specified in <a href="https://tools.ietf.org/html/rfc8529#section-11">RFC8529, Section&nbsp;11</a> [<a href="https://tools.ietf.org/html/rfc8259" title="&quot;The JavaScript Object Notation (JSON) Data Interchange Format&quot;">RFC8259</a>].

   Security considerations:  See <a href="https://tools.ietf.org/html/draft-ietf-calext-jscalendar-25#section-7">Section 7</a> of this document.

   Interoperability considerations:  This media type provides an
      alternative to iCalendar, jCal and proprietary JSON-based
      calendaring data formats.

   Published specification:  This specification.

   Applications that use this media type:  Applications that currently
      make use of the text/calendar and application/calendar+json media
      types can use this as an alternative.  Similarly, applications
      that use the application/json media type to transfer calendaring
      data can use this to further specify the content.

   Fragment identifier considerations:  N/A

   Additional information:

      Magic number(s):  N/A

      File extensions(s):  N/A

      Macintosh file type code(s):  N/A

   Person &amp; email address to contact for further information:
      <a href="mailto:calsify@ietf.org">calsify@ietf.org</a>

   Intended usage:  COMMON

   Restrictions on usage:  N/A

   Author:  See the "Author's Address" section of this document.

   Change controller:  IETF<br></pre><div><br></div><div>Cheers,<br></div><div>Neil.</div></body></html>
--c82a351b8e1340938f5595a6702982b7--


From nobody Wed Mar 18 12:49:36 2020
Return-Path: <florent@sodria.com>
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 A681A3A1AF7 for <media-types@ietfa.amsl.com>; Wed, 18 Mar 2020 12:49:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.958
X-Spam-Level: 
X-Spam-Status: No, score=-0.958 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, KHOP_HELO_FCRDNS=0.274, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no 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 j3-p-9X49CLF for <media-types@ietfa.amsl.com>; Wed, 18 Mar 2020 12:49:32 -0700 (PDT)
Received: from mail.tcool.fr (ks3359019.kimsufi.com [37.187.96.26]) by ietfa.amsl.com (Postfix) with ESMTP id 097C93A1AF3 for <media-types@ietf.org>; Wed, 18 Mar 2020 12:49:31 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.tcool.fr (Postfix) with ESMTP id 87078C6008C for <media-types@ietf.org>; Wed, 18 Mar 2020 20:49:28 +0100 (CET)
Received: from mail.tcool.fr ([127.0.0.1]) by localhost (ks3359019.kimsufi.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DnNII7v2YqBU for <media-types@ietf.org>; Wed, 18 Mar 2020 20:49:28 +0100 (CET)
Received: from mail-ed1-f43.google.com (mail-ed1-f43.google.com [209.85.208.43]) by mail.tcool.fr (Postfix) with ESMTPSA id 2B05AC60074 for <media-types@ietf.org>; Wed, 18 Mar 2020 20:49:28 +0100 (CET)
Received: by mail-ed1-f43.google.com with SMTP id b21so22049271edy.9 for <media-types@ietf.org>; Wed, 18 Mar 2020 12:49:28 -0700 (PDT)
X-Gm-Message-State: ANhLgQ2C6pyQqaiGe9HgVa3FNnwVVsNTCUQeezSy7EcYhiogQT4F22i8 9HiBvyAViq2XEa7BENUn5xB4kzq/nOV8sGW4xZo=
X-Google-Smtp-Source: ADFU+vumc9ifkO2vXPK9qwZ/UXsN0Soa2lMYzxSquall5ZS0zcFIcDkOgFlzY5U69ygdV54cCSJYCWnyothvkrMlC0U=
X-Received: by 2002:a17:906:4001:: with SMTP id v1mr5577252ejj.36.1584560967726;  Wed, 18 Mar 2020 12:49:27 -0700 (PDT)
MIME-Version: 1.0
From: "Florent Viard (Sodria)" <florent@sodria.com>
Date: Wed, 18 Mar 2020 20:49:16 +0100
X-Gmail-Original-Message-ID: <CAMiUVfyD7x1E39CT_rbMGvRx=C9ko65MM=iEzOBLAoLR2zhNEA@mail.gmail.com>
Message-ID: <CAMiUVfyD7x1E39CT_rbMGvRx=C9ko65MM=iEzOBLAoLR2zhNEA@mail.gmail.com>
To: bjh21@cam.ac.uk, media-types@ietf.org, ingy@ingy.net, oren@ben-kiki.org,  cce@clarkevans.com
Cc: plessy@debian.org
Content-Type: multipart/alternative; boundary="0000000000009b3bc105a1265908"
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/IHzUA28glz35YfdiTWfLML3QCYM>
Subject: [media-types] Following: Re: Proposed media type registration for YAML
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: Wed, 18 Mar 2020 19:49:35 -0000

--0000000000009b3bc105a1265908
Content-Type: text/plain; charset="UTF-8"

This is a message following the thread:
"Re: [media-types] Proposed media type registration for YAML"
https://mailarchive.ietf.org/arch/msg/media-types/U6gTWZ55YG-lgwFLFA9hU9g4_qs/
(as i'm not able to reply to the original thread)

Hi Ben,

Around 5 years ago, you proposed to add a type for YAML on the media-types
list of the IETF.
Sadly, since then, nothing has changed.

What do you (or anyone else) think about going on with this and so finally
having an officially registered type?

I'm not affiliated, related or expert in YAML or anything IETF related, but
what you suggested as content for the registration form looks good to me.

If you ask me, I think that the type name should simply be
"application/yaml".
A standard type, and not a vendor type.
There are no RFC for YAML(?), but from what I can see, in the existing
registered type list, quite a few of them don't have an associated RFC.

One last bit of information, I noticed that YAML was already added a long
time ago in the "shared-mime-info" db as "application/x-yaml".

Thank you,

Florent

--0000000000009b3bc105a1265908
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>This is a message following the thread:<br></div><div=
>&quot;Re: [media-types] Proposed media type registration for YAML&quot;<br=
><div><a href=3D"https://mailarchive.ietf.org/arch/msg/media-types/U6gTWZ55=
YG-lgwFLFA9hU9g4_qs/">https://mailarchive.ietf.org/arch/msg/media-types/U6g=
TWZ55YG-lgwFLFA9hU9g4_qs/</a><span style=3D"color:rgb(128,128,128);font-fam=
ily:-apple-system,BlinkMacSystemFont,&quot;Segoe UI&quot;,Roboto,&quot;Helv=
etica Neue&quot;,Arial,&quot;Noto Sans&quot;,sans-serif,&quot;Apple Color E=
moji&quot;,&quot;Segoe UI Emoji&quot;,&quot;Segoe UI Symbol&quot;,&quot;Not=
o Color Emoji&quot;;font-size:14px"><br></span></div></div><div>(as i&#39;m=
 not able to reply to the original thread)</div><div><br></div><div>Hi Ben,=
<br></div><div><br></div><div>Around 5 years ago, you proposed to add a typ=
e for YAML on the media-types list of the IETF.</div><div>Sadly, since then=
, nothing has changed.</div><div><br></div><div>What do you (or anyone else=
) think about=C2=A0going on with this and so finally having an officially r=
egistered type?</div><div><br></div><div>I&#39;m not affiliated, related or=
 expert in YAML or anything IETF related, but what you suggested as content=
 for the registration form looks good to me.</div><div><br></div><div>If yo=
u ask me, I think that the type name should simply be &quot;application/yam=
l&quot;.</div><div>A standard type, and not a vendor type.</div><div>There =
are no RFC for YAML(?), but from what I can see, in the existing registered=
 type list, quite a few of them don&#39;t have an associated RFC.</div><div=
><br></div><div>One last bit of information, I noticed that YAML was alread=
y added a long time ago in the &quot;shared-mime-info&quot; db as &quot;app=
lication/x-yaml&quot;.</div><div><br></div><div>Thank you,</div><div><br></=
div><div>Florent</div></div>

--0000000000009b3bc105a1265908--


From nobody Wed Mar 18 14:36:11 2020
Return-Path: <paul@hoplahup.net>
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 B8BF63A1CB2 for <media-types@ietfa.amsl.com>; Wed, 18 Mar 2020 14:36:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.623
X-Spam-Level: 
X-Spam-Status: No, score=-1.623 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, KHOP_HELO_FCRDNS=0.274, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no 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 Iw1rXXudWEjQ for <media-types@ietfa.amsl.com>; Wed, 18 Mar 2020 14:36:04 -0700 (PDT)
Received: from pechora2.lax.icann.org (pechora2.icann.org [IPv6:2620:0:2d0:201::1:72]) (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 E19E13A1CA3 for <media-types@ietf.org>; Wed, 18 Mar 2020 14:36:03 -0700 (PDT)
Received: from 4.mo69.mail-out.ovh.net (4.mo69.mail-out.ovh.net [46.105.42.102]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pechora2.lax.icann.org (Postfix) with ESMTPS id 77F6E1E05C4 for <media-types@iana.org>; Wed, 18 Mar 2020 21:36:03 +0000 (UTC)
Received: from player773.ha.ovh.net (unknown [10.110.171.171]) by mo69.mail-out.ovh.net (Postfix) with ESMTP id E31D88886B for <media-types@iana.org>; Wed, 18 Mar 2020 22:35:40 +0100 (CET)
Received: from hoplahup.net (pD9526D41.dip0.t-ipconnect.de [217.82.109.65]) (Authenticated sender: paul@hoplahup.net) by player773.ha.ovh.net (Postfix) with ESMTPSA id 30BDD10A63AC7; Wed, 18 Mar 2020 21:35:39 +0000 (UTC)
From: "Paul Libbrecht" <paul@hoplahup.net>
To: "Neil Jenkins" <neilj@fastmailteam.com>
Cc: media-types@iana.org
Date: Wed, 18 Mar 2020 22:35:36 +0100
X-Mailer: MailMate Trial (1.13.1r5671)
Message-ID: <4E7712F0-BBDA-4ECA-A00C-4EF63B9669CC@hoplahup.net>
In-Reply-To: <83caa50c-082d-4689-9217-a076eead834b@beta.fastmail.com>
References: <83caa50c-082d-4689-9217-a076eead834b@beta.fastmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_2199EC94-21C8-4584-9010-F9D6905CCC28_="
Embedded-HTML: [{"HTML":[2385, 2444], "plain":[1447, 2226], "uuid":"85ACEA10-EB0A-4ECA-AE87-B439FFEDB037"}]
X-Ovh-Tracer-Id: 10676908818741070071
X-VR-SPAMSTATE: OK
X-VR-SPAMSCORE: -100
X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.2 (pechora2.lax.icann.org [192.0.33.72]); Wed, 18 Mar 2020 21:36:03 +0000 (UTC)
X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgedugedrudefjedgudegfecutefuodetggdotefrodftvfcurfhrohhfihhlvgemucfqggfjpdevjffgvefmvefgnecuuegrihhlohhuthemucehtddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpefhvffufffokfgjfhggtgesrgdtmherredtjeenucfhrhhomhepfdfrrghulhcunfhisggsrhgvtghhthdfuceophgruhhlsehhohhplhgrhhhuphdrnhgvtheqnecuffhomhgrihhnpegrphhplhgvrdgtohhmpdhorhgvihhllhihrdgtohhmpdhivghtfhdrohhrghenucfkpheptddrtddrtddrtddpvddujedrkedvrddutdelrdeiheenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhhouggvpehsmhhtphdqohhuthdphhgvlhhopehplhgrhigvrhejjeefrdhhrgdrohhvhhdrnhgvthdpihhnvghtpedtrddtrddtrddtpdhmrghilhhfrhhomhepphgruhhlsehhohhplhgrhhhuphdrnhgvthdprhgtphhtthhopehmvgguihgrqdhthihpvghssehirghnrgdrohhrgh
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/_4eCECOMHi-_UvqB8KA5fcu1ENo>
Subject: Re: [media-types] Notice of intended registration of "jscalendar+json"
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: Wed, 18 Mar 2020 21:36:10 -0000

--=_MailMate_2199EC94-21C8-4584-9010-F9D6905CCC28_=
Content-Type: text/plain; charset="UTF-8"; format=flowed
Content-Transfer-Encoding: quoted-printable

Hello Neil,

While this is not yet part of rfc6838, I would like to suggest to modify =

the _Additional information_ part to include clipboard-oriented =

designations, so that a copy-and-paste and drag-and-drop exchange is =

standardised too. This has been done on a few occasions (e.g. SVG) but =

should only be done if the media-type makes sense to be exchanged =

between apps or windows within a computer with copy-and-paste or =

drag-and-drop gestures.

I only looked on macOS but got no introspectable data from the calendar =

app that looks similar to the jscalendar intent so I cannot recommend a =

precise name. I could imagine something such as the following to be =

useful:

- macOS UTI (according to [Apple=E2=80=99s =

doc](https://developer.apple.com/library/archive/documentation/FileManage=
ment/Conceptual/understanding_utis/understand_utis_intro/understand_utis_=
intro.html): =

`public.jscalendar` conforms to `public.json` (which I see quoted e.g. =

in =

[this](https://www.oreilly.com/library/view/learning-swift-2nd/9781491967=
058/ch04.html) =

book).

- Windows: `jscalendar` (in Windows, there is media-type no =

inheritance).

Would it make sense to you to enrich it this way?

Off list, you seemed to answer that this is sensible but that it would =

be good to have the opinions of others. I would be interested to the =

same indeed.

What are the others=E2=80=99 opinion on the media-types=E2=80=99 list?

Thanks in advance.

Paul


On 8 Mar 2020, at 3:00, Neil Jenkins wrote:

> In accordance with Section 5.1 of of RFC6838 =

> <https://tools.ietf.org/html/rfc6838#section-5.1>, I wish to notify =

> the list of the intended registration of a new media type in the =

> standards track document JSCalendar =

> <https://tools.ietf.org/html/draft-ietf-calext-jscalendar>. I welcome =

> any comments or feedback. The intended registration is as follows:
>
>    Type name:  application
>
>    Subtype name:  jscalendar+json
>
>    Required parameters:  type
>
>       The "type" parameter conveys the type of the JSCalendar data in
>       the body part, with the value being one of "jsevent", "jstask", =

> or
>       "jsgroup".  The parameter MUST NOT occur more than once.  It =

> MUST
>       match the value of the "@type" property of the JSON-formatted
>       JSCalendar object in the body.
>
>    Optional parameters:  none
>
>    Encoding considerations:  Same as encoding considerations of
>       application/json as specified in RFC8529, Section=C2=A011 =

> <https://tools.ietf.org/html/rfc8529#section-11> [RFC8259 =

> <https://tools.ietf.org/html/rfc8259>].
>
>    Security considerations:  See Section 7 =

> <https://tools.ietf.org/html/draft-ietf-calext-jscalendar-25#section-7>=
 =

> of this document.
>
>    Interoperability considerations:  This media type provides an
>       alternative to iCalendar, jCal and proprietary JSON-based
>       calendaring data formats.
>
>    Published specification:  This specification.
>
>    Applications that use this media type:  Applications that currently
>       make use of the text/calendar and application/calendar+json =

> media
>       types can use this as an alternative.  Similarly, applications
>       that use the application/json media type to transfer calendaring
>       data can use this to further specify the content.
>
>    Fragment identifier considerations:  N/A
>
>    Additional information:
>
>       Magic number(s):  N/A
>
>       File extensions(s):  N/A
>
>       Macintosh file type code(s):  N/A
>
>    Person & email address to contact for further information:
>       calsify@ietf.org
>
>    Intended usage:  COMMON
>
>    Restrictions on usage:  N/A
>
>    Author:  See the "Author's Address" section of this document.
>
>    Change controller:  IETF
>
> Cheers,
> Neil.


> _______________________________________________
> media-types mailing list
> media-types@ietf.org
> https://www.ietf.org/mailman/listinfo/media-types

--=_MailMate_2199EC94-21C8-4584-9010-F9D6905CCC28_=
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html>
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/xhtml; charset=3Dutf-8"=
>
</head>
<body>
<div style=3D"font-family:sans-serif"><div style=3D"white-space:normal">
<p dir=3D"auto">Hello Neil,</p>

<p dir=3D"auto">While this is not yet part of rfc6838, I would like to su=
ggest to modify the <em>Additional information</em> part to include clipb=
oard-oriented designations, so that a copy-and-paste and drag-and-drop ex=
change is standardised too. This has been done on a few occasions (e.g. S=
VG) but should only be done if the media-type makes sense to be exchanged=
 between apps or windows within a computer with copy-and-paste or drag-an=
d-drop gestures.</p>

<p dir=3D"auto">I only looked on macOS but got no introspectable data fro=
m the calendar app that looks similar to the jscalendar intent so I canno=
t recommend a precise name. I could imagine something such as the followi=
ng to be useful:</p>

<ul>
<li><p dir=3D"auto">macOS UTI (according to <a href=3D"https://developer.=
apple.com/library/archive/documentation/FileManagement/Conceptual/underst=
anding_utis/understand_utis_intro/understand_utis_intro.html" style=3D"co=
lor:#3983C4">Apple=E2=80=99s doc</a>: <code style=3D"background-color:#F7=
F7F7; border-radius:3px; margin:0; padding:0 0.4em" bgcolor=3D"#F7F7F7">p=
ublic.jscalendar</code> conforms to <code style=3D"background-color:#F7F7=
F7; border-radius:3px; margin:0; padding:0 0.4em" bgcolor=3D"#F7F7F7">pub=
lic.json</code> (which I see quoted e.g. in <a href=3D"https://www.oreill=
y.com/library/view/learning-swift-2nd/9781491967058/ch04.html" style=3D"c=
olor:#3983C4">this</a> book).</p></li>
<li><p dir=3D"auto">Windows: <code style=3D"background-color:#F7F7F7; bor=
der-radius:3px; margin:0; padding:0 0.4em" bgcolor=3D"#F7F7F7">jscalendar=
</code> (in Windows, there is media-type no inheritance).</p></li>
</ul>

<p dir=3D"auto">Would it make sense to you to enrich it this way?</p>

<p dir=3D"auto">Off list, you seemed to answer that this is sensible but =
that it would be good to have the opinions of others. I would be interest=
ed to the same indeed.</p>

<p dir=3D"auto">What are the others=E2=80=99 opinion on the media-types=E2=
=80=99 list?</p>

<p dir=3D"auto">Thanks in advance.</p>

<p dir=3D"auto">Paul</p>

<p dir=3D"auto">On 8 Mar 2020, at 3:00, Neil Jenkins wrote:</p>

</div>
<div style=3D"white-space:normal"></div>
<blockquote style=3D"border-left:2px solid #777; color:#777; margin:0 0 5=
px; padding-left:5px"><div id=3D"85ACEA10-EB0A-4ECA-AE87-B439FFEDB037"><d=
iv>In accordance with <a href=3D"https://tools.ietf.org/html/rfc6838#sect=
ion-5.1">Section 5.1 of of RFC6838</a>, I wish to notify the list of the =
intended registration of a new media type in the standards track document=
 <a href=3D"https://tools.ietf.org/html/draft-ietf-calext-jscalendar">JSC=
alendar</a>. I welcome any comments or feedback. The intended registratio=
n is as follows:<br></div><div><br></div><pre>   Type name:  application

   Subtype name:  jscalendar+json

   Required parameters:  type

      The "type" parameter conveys the type of the JSCalendar data in
      the body part, with the value being one of "jsevent", "jstask", or
      "jsgroup".  The parameter MUST NOT occur more than once.  It MUST
      match the value of the "@type" property of the JSON-formatted
      JSCalendar object in the body.

   Optional parameters:  none

   Encoding considerations:  Same as encoding considerations of
      application/json as specified in <a href=3D"https://tools.ietf.org/=
html/rfc8529#section-11">RFC8529, Section=C2=A011</a> [<a href=3D"https:/=
/tools.ietf.org/html/rfc8259" title=3D'"The JavaScript Object Notation (J=
SON) Data Interchange Format"'>RFC8259</a>].

   Security considerations:  See <a href=3D"https://tools.ietf.org/html/d=
raft-ietf-calext-jscalendar-25#section-7">Section 7</a> of this document.=


   Interoperability considerations:  This media type provides an
      alternative to iCalendar, jCal and proprietary JSON-based
      calendaring data formats.

   Published specification:  This specification.

   Applications that use this media type:  Applications that currently
      make use of the text/calendar and application/calendar+json media
      types can use this as an alternative.  Similarly, applications
      that use the application/json media type to transfer calendaring
      data can use this to further specify the content.

   Fragment identifier considerations:  N/A

   Additional information:

      Magic number(s):  N/A

      File extensions(s):  N/A

      Macintosh file type code(s):  N/A

   Person &amp; email address to contact for further information:
      <a href=3D"mailto:calsify@ietf.org">calsify@ietf.org</a>

   Intended usage:  COMMON

   Restrictions on usage:  N/A

   Author:  See the "Author's Address" section of this document.

   Change controller:  IETF<br></pre><div><br></div><div>Cheers,<br></div=
><div>Neil.</div></div></blockquote>
<div style=3D"white-space:normal">
<blockquote style=3D"border-left:2px solid #777; color:#777; margin:0 0 5=
px; padding-left:5px">
</blockquote><blockquote style=3D"border-left:2px solid #777; color:#777;=
 margin:0 0 5px; padding-left:5px"><p dir=3D"auto">______________________=
_________________________<br>
media-types mailing list<br>
media-types@ietf.org<br>
<a href=3D"https://www.ietf.org/mailman/listinfo/media-types" style=3D"co=
lor:#777">https://www.ietf.org/mailman/listinfo/media-types</a></p>
</blockquote></div>
<div style=3D"white-space:normal">
</div>
</div>
</body>
</html>

--=_MailMate_2199EC94-21C8-4584-9010-F9D6905CCC28_=--


From nobody Thu Mar 19 03:26:30 2020
Return-Path: <bjh21@cam.ac.uk>
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 2F11C3A26A4 for <media-types@ietfa.amsl.com>; Thu, 19 Mar 2020 03:26:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cam.ac.uk
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 wi5OnTX7QXe9 for <media-types@ietfa.amsl.com>; Thu, 19 Mar 2020 03:26:25 -0700 (PDT)
Received: from ppsw-30.csi.cam.ac.uk (ppsw-30.csi.cam.ac.uk [131.111.8.130]) (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 BD8AD3A26A0 for <media-types@ietf.org>; Thu, 19 Mar 2020 03:26:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=cam.ac.uk;  s=20180806.ppsw; h=Sender:Content-Type:MIME-Version:References:Message-ID: In-Reply-To:Subject:cc:To:From:Date:Reply-To: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=JAtobZFT2tfaVhwccOOJwN7szHRuSgRUMJOsf/Hx8zg=; b=wvPz4JUY1+Lwkf1YDwnDWGR5AP GkGT0nc8dtMk1IeyHpk3qakJdawnUO2GECSZyeiXc6EnwwFp0v6xde+sJ48MdieB7q/CssEhvXuXf R/GjBpi9gmg0sazCf7wpEufdORmGu3bEqymWqSglVRiIDGuYnmOxYfTjTNGMAGvMMM4Q=;
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://help.uis.cam.ac.uk/email-scanner-virus
Received: from thunderbird-2.linux.ds.cam.ac.uk ([131.111.9.24]:40008) by ppsw-30.csi.cam.ac.uk (ppsw.cam.ac.uk [131.111.8.136]:25) with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) id 1jEsNZ-000TNN-eJ (Exim 4.92.3) (return-path <bjh21@cam.ac.uk>); Thu, 19 Mar 2020 10:26:21 +0000
Received: from bjh21 (helo=localhost) by thunderbird-2.linux.ds.cam.ac.uk with local-esmtp (Exim 4.90_1) (envelope-from <bjh21@cam.ac.uk>) id 1jEsNZ-000DwU-Bf; Thu, 19 Mar 2020 10:26:21 +0000
Date: Thu, 19 Mar 2020 10:26:20 +0000 (GMT)
From: Ben Harris <bjh21@cam.ac.uk>
To: "Florent Viard (Sodria)" <florent@sodria.com>
cc: media-types@ietf.org, ingy@ingy.net, oren@ben-kiki.org, cce@clarkevans.com, plessy@debian.org
In-Reply-To: <CAMiUVfyD7x1E39CT_rbMGvRx=C9ko65MM=iEzOBLAoLR2zhNEA@mail.gmail.com>
Message-ID: <alpine.DEB.2.21.2003191023000.52135@thunderbird-2.linux.ds.cam.ac.uk>
References: <CAMiUVfyD7x1E39CT_rbMGvRx=C9ko65MM=iEzOBLAoLR2zhNEA@mail.gmail.com>
User-Agent: Alpine 2.21 (DEB 202 2017-01-01)
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="1870862345-1061521696-1584613581=:52135"
Sender: "B.J. Harris" <bjh21@cam.ac.uk>
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/wR-RZv2QI6t1kNPLxO44Q9yak_k>
Subject: Re: [media-types] Following: Re: Proposed media type registration for YAML
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: Thu, 19 Mar 2020 10:26:28 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--1870862345-1061521696-1584613581=:52135
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8BIT

On Wed, 18 Mar 2020, Florent Viard (Sodria) wrote:

> Around 5 years ago, you proposed to add a type for YAML on the media-types
> list of the IETF.
> Sadly, since then, nothing has changed.
> 
> What do you (or anyone else) think about going on with this and so finally
> having an officially registered type?

The one use case I had for it vanished (replaced with JSON as I recall), 
so given the objections to my proposal I dropped it.

-- 
Ben Harris, University of Cambridge Information Services.  Tel: (01223) 748438
--1870862345-1061521696-1584613581=:52135--


From nobody Mon Mar 23 03:10:00 2020
Return-Path: <neilj@fastmailteam.com>
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 AF9D43A0484 for <media-types@ietfa.amsl.com>; Mon, 23 Mar 2020 03:09:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.319
X-Spam-Level: 
X-Spam-Status: No, score=-1.319 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, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmailteam.com header.b=vRM3LF3Q; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=0GVyordC
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 lUHGlU4Z-5uP for <media-types@ietfa.amsl.com>; Mon, 23 Mar 2020 03:09:53 -0700 (PDT)
Received: from pechora6.dc.icann.org (pechora6.icann.org [192.0.46.72]) (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 C38123A048D for <media-types@ietf.org>; Mon, 23 Mar 2020 03:09:52 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pechora6.dc.icann.org (Postfix) with ESMTPS id D82B11E01B4 for <media-types@iana.org>; Mon, 23 Mar 2020 10:09:51 +0000 (UTC)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 4902F5C0251; Mon, 23 Mar 2020 06:09:30 -0400 (EDT)
Received: from imap7 ([10.202.2.57]) by compute4.internal (MEProxy); Mon, 23 Mar 2020 06:09:30 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=mime-version:message-id:in-reply-to :references:date:from:to:cc:subject:content-type; s=fm2; bh=nmOE EwxjohIHFLbGeDIQcuESzq3J9z+Z8NOwMAJbQEw=; b=vRM3LF3Q827UXVc2xcbP Pr27qLnrY87IANYR4U2JJqFoCZRecObRndZURejb2dcHpDOv4QsH8IVx+gtfIbRG 4HhO+DsM/fU+UAtJJDjxish9J3ZGYM3n2MDGk4XvP8LfgSnMntQknFX5baAewLHb bGRRH5B70TayQdF3a+E0odF0wSAPsmh8zDsvvhuZVkXdsNPxfl6BTbAS1TlaAPTW 4mswPJaGH8fntWJNmWg1ZeaELSnDrr0hibgRX2iGE3BywNoh1ZStJ+/PIZ0HZyJw MI4Xyod1NDrxY/X5VzZNQVFU80bo6FIULk9mrSnx20rCVx6ynuc4oU1rpFuw2ya6 6w==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=nmOEEw xjohIHFLbGeDIQcuESzq3J9z+Z8NOwMAJbQEw=; b=0GVyordC8huHy1SwoKdACG 9yz/7QcMeCngVkiDhHAMgHCXX0b2/Vn8sXw+hY7L7+Fl9AXRqFMAXLSrK4oxlb7C j7BodmgGIFV5MLDFeMWFmAhYpV6LCznbVqsKY+xmllOB4VkeYuwkznatHCC81BBf J+OGJZpDZakb/w7HQrelU0d5mMAKmjwg97PVFKIvkVwgNdtLekLJQ1C9TacMa8A7 H+U1tjSUVVNd7HiCtaCWlNyslOYGLiDHYKZjW8Veg7S8eEtyk0q47KeWRY//vvME SF1Wqhid/2tVj9An8ikAETopa3h/1AKD0OUwyjnS4wKe8N9jJP+o5AmKVciVi2rA ==
X-ME-Sender: <xms:2Yp4Xld8XIXnyUHai0GqznCyWYBRPJ5cRxWek9DiB1w6MBE039UwOw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedrudegkedguddvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgesrgdtreerreerjeenucfhrhhomhepfdfpvghi lhculfgvnhhkihhnshdfuceonhgvihhljhesfhgrshhtmhgrihhlthgvrghmrdgtohhmqe enucevlhhushhtvghrufhiiigvpedunecurfgrrhgrmhepmhgrihhlfhhrohhmpehnvghi lhhjsehfrghsthhmrghilhhtvggrmhdrtghomh
X-ME-Proxy: <xmx:2Yp4XnyuxtSB9GtjmJWkxNjrS-bzAgxq6VviIj8EHPbz6zB5NAXZCw> <xmx:2Yp4XroyjLz1xB4nkG98anE8HdV2KEa-_V_5p_PccuoR2w77bE9UOg> <xmx:2Yp4XlxGeI9W60j-Dkv6RaiB4AQrAWv-k3pfb5N3F5k75G5MKgVYlQ> <xmx:2op4XjRHdiGfB55i4a_Zr4wNxh67YOlNNzOitE9-onfJpeHrltQeNw>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id CE846180090; Mon, 23 Mar 2020 06:09:29 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.7-1021-g152deaf-fmstable-20200319v1
Mime-Version: 1.0
Message-Id: <8ba2176a-624b-40ec-af70-b34e3ae9d7d3@beta.fastmail.com>
In-Reply-To: <4E7712F0-BBDA-4ECA-A00C-4EF63B9669CC@hoplahup.net>
References: <83caa50c-082d-4689-9217-a076eead834b@beta.fastmail.com> <4E7712F0-BBDA-4ECA-A00C-4EF63B9669CC@hoplahup.net>
Date: Mon, 23 Mar 2020 21:09:02 +1100
From: "Neil Jenkins" <neilj@fastmailteam.com>
To: media-types@iana.org
Cc: "Paul Libbrecht" <paul@hoplahup.net>
Content-Type: multipart/alternative; boundary=6850140604c841c9b1c7abc6a25e44a3
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/wK5iWBptKN29AwVvgp_RWiketmc>
Subject: Re: [media-types]  =?utf-8?q?Notice_of_intended_registration_of_=22js?= =?utf-8?q?calendar+json=22?=
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: Mon, 23 Mar 2020 10:09:58 -0000

--6850140604c841c9b1c7abc6a25e44a3
Content-Type: text/plain

On Thu, 19 Mar 2020, at 08:35, Paul Libbrecht wrote:
> I would like to suggest to modify the *Additional information* part to include clipboard-oriented designations, so that a copy-and-paste and drag-and-drop exchange is standardised too.

I think it make sense that such information might be copy-pasted on drag-dropped. To be honest I don't understand enough about how these designations work to say what we should do here, but if someone on the list with more expertise in this area has a suggestion I'm happy to update the registration text.

Cheers,
Neil.
--6850140604c841c9b1c7abc6a25e44a3
Content-Type: text/html

<!DOCTYPE html><html><head><title></title><style type="text/css">p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div>On Thu, 19 Mar 2020, at 08:35, Paul Libbrecht wrote:<br></div><blockquote type="cite"><div>I would like to suggest to modify the <i>Additional information</i> part to include clipboard-oriented designations, so that a copy-and-paste and drag-and-drop exchange is standardised too.<br></div></blockquote><div><br></div><div>I think it make sense that such information might be copy-pasted on drag-dropped. To be honest I don't understand enough about how these designations work to say what we should do here, but if someone on the list with more expertise in this area has a suggestion I'm happy to update the registration text.<br></div><div><br></div><div>Cheers,<br></div><div>Neil.<br></div></body></html>
--6850140604c841c9b1c7abc6a25e44a3--


From khronos@callow.im  Mon Mar 23 16:57:00 2020
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 18CEB3A0F3B for <media-types@ietfa.amsl.com>; Mon, 23 Mar 2020 16:57:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.433
X-Spam-Level: 
X-Spam-Status: No, score=-1.433 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, SPF_SOFTFAIL=0.665, 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 UpqxwMJ_MD_J for <media-types@ietfa.amsl.com>; Mon, 23 Mar 2020 16:56:58 -0700 (PDT)
Received: from pechora6.dc.icann.org (pechora6.icann.org [192.0.46.72]) (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 D91233A0F39 for <media-types@ietf.org>; Mon, 23 Mar 2020 16:56:57 -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 pechora6.dc.icann.org (Postfix) with ESMTPS id 4AE591E0454 for <media-types@iana.org>; Mon, 23 Mar 2020 23:56:55 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=callow.im;  s=default; h=To:Date:Message-Id: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: In-Reply-To:References:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=0tf/NOdCOnJfXAbUONusOAZ0SDnCbq6r3aipRqgzwvw=; b=TGVlglGdZ4nTE4ZzEoiD1upIPe 9zh1f/RUyWB4MG1aN2bq4M2M7BUQSEEFo4W0VXR9qsvsM12LmmTfbwIEGNmNQhfd+2i4KoEDxW4jE CMikKfXJTlYRpnCimczx4LjXAXRCTmyX9dj7QHQ0+fE6Y+Wg0ZBHib9c3pFGeORVZdAQ=;
Received: from [73.71.117.63] (port=65523 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 1jGWvr-0001o3-7W for media-types@iana.org; Mon, 23 Mar 2020 19:56:35 -0400
From: Mark Callow <khronos@callow.im>
Content-Type: multipart/signed; boundary="Apple-Mail=_B3041FBF-49A6-466D-A26A-7BA85A62C252"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Message-Id: <35D0A921-87E6-43D3-A0D8-E7578C0FFE15@callow.im>
Date: Mon, 23 Mar 2020 16:56:31 -0700
To: media-types@iana.org
X-Mailer: Apple Mail (2.3445.104.11)
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/94pZMVppcbYGAeaxSyop7WDxjWI>
X-Mailman-Approved-At: Mon, 23 Mar 2020 17:27:37 -0700
Subject: [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: Mon, 23 Mar 2020 23:57:53 -0000

--Apple-Mail=_B3041FBF-49A6-466D-A26A-7BA85A62C252
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_5637E18C-8E11-4089-963D-6648C5F77FCB"


--Apple-Mail=_5637E18C-8E11-4089-963D-6648C5F77FCB
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

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




--Apple-Mail=_5637E18C-8E11-4089-963D-6648C5F77FCB
Content-Type: multipart/mixed;
	boundary="Apple-Mail=_E78A98FB-1845-46B1-A9D5-AEF68BFD3C9F"


--Apple-Mail=_E78A98FB-1845-46B1-A9D5-AEF68BFD3C9F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D""><div =
class=3D"" style=3D"font-family: HelveticaNeue;">Greetings Media-Type =
Experts</div><div class=3D"" style=3D"font-family: HelveticaNeue;"><br =
class=3D""></div><div class=3D"" style=3D"font-family: HelveticaNeue;">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.</div><div class=3D"" style=3D"font-family: HelveticaNeue;"><br =
class=3D""></div><div class=3D"" style=3D"font-family: =
HelveticaNeue;">Khronos has almost completed a new version of the =
specification known formally as&nbsp;<a =
href=3D"http://github.khronos.org/KTX-Specification/" class=3D"">The KTX =
File Format Version 2</a>&nbsp;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.</div><div class=3D"" style=3D"font-family: HelveticaNeue;"><br =
class=3D""></div><div class=3D"" style=3D"font-family: =
HelveticaNeue;"><div class=3D"">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.</div></div><div class=3D"" =
style=3D"font-family: HelveticaNeue;"><br class=3D""></div><div class=3D""=
 style=3D"font-family: HelveticaNeue;">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.</div><div =
class=3D"" style=3D"font-family: HelveticaNeue;"><br class=3D""></div><div=
 class=3D"" style=3D"font-family: HelveticaNeue;">Please advise. If a =
new Media-Type is the right way to go, then please review the attached =
draft registration.</div><br class=3D"" style=3D"font-family: =
HelveticaNeue;"><div class=3D"" style=3D"font-family: =
HelveticaNeue;"><div class=3D"" style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;">Regards<br =
class=3D""><br class=3D"">&nbsp; &nbsp; -Mark</div></div><br class=3D"" =
style=3D"font-family: HelveticaNeue;"><div class=3D"" =
style=3D"font-family: HelveticaNeue;"></div></body></html>=

--Apple-Mail=_E78A98FB-1845-46B1-A9D5-AEF68BFD3C9F
Content-Disposition: attachment;
	filename=ktx-media-registration.txt
Content-Type: text/plain;
	x-unix-mode=0644;
	name="ktx-media-registration.txt"
Content-Transfer-Encoding: quoted-printable

Type name: Image

Subtype name: ktx2

Required parameters: none

Optional parameters: none

Encoding considerations: binary

Security considerations:

The ktx2 type is a binary data stream which contains no executable code =
that
could disrupt a client processor. There is no provision in the type
specification that would allow authors to insert executable code that =
would
present any security risk to a client machine. The only effect =
associated
with this data is to cause an image to be rendered on the recipient's =
display.

Because every item's length is available at its beginning, there is =
robust
defense against corrupted or fraudulent data that might overflow a =
decoder's
buffer. Also the signature bytes provide early detection of common file
transmission errors.

The image payload may be uncompressed or may be block-compressed.
Variable rate compression can be applied to supercompress the data.i

Block compression schemes are designed so small blocks blocks data
(typically 64 to 128 bits) can be decompressed in real time into a
small block of pixels (typically 4x4) during texel fetch. In such
schemes it is not possible for a small amount of data to expand
enormously because the level of compression is limited; the compressed
size is related directly to the number of pixels in the uncompressed
image and not to the content of the data.

When variable-rate compression is used, the format provides informatio
as to the expected size of the uncompressed data. However applications
must not rely on this and must guard against buffer overflow.

The ktx type does not provide encryption of the data payload. Users or
applications wishing or needing to keep their images confidential must
overlay their own encryption on the ktx data during transmission.

Interoperability considerations:

The data payload may be compressed using a vendor-specific scheme. In
this case, only devices or applications having a matching decompressor
will be able to display the data. The compression scheme is identified =
in
the ktx2 data so applications can quickly reject data using unsupported
schemes.

Published specification:

The KTX file format specification can be found at

    http://github.khronos.org/KTX-Specification/

Applications that use this media type :

Currently the tools in the KTX Software
(https://github.com/KhronosGroup/KTX-Software) - ktx2check, ktx2ktx2,
ktxinfo, ktxsc, toktx - and by gltfpack. Prototype loaders are
available in THREE.js and Babylon.js. It is anticipated it will
incorporated within the glTF standard and be widely used by by
applications using glTF content and by applications built on top
of the Vulkan and OpenGL families of standards as the means of
delivering texture data.

Additional information:

    Magic number(s): 12 octets
				 { =
0xAB,0x4B,0x54,0x58,0x20,0x32,0x30,0xBB,0x0D,0x0A,0x1A,0x0A }
    File extension(s): .ktx
    Macintosh file type code(s):

Person & email address to contact for further information:

    Mark Callow (khronos at callow.im)

Intended usage: COMMON

Restrictions on usage: none

Authors: Mark Callow, Alexey Knyazev

Change controller:

The Khronos Group (www.khronos.org), the industry consortium responsible =
for
standards such as OpenGL, OpenGL ES, WebGL and Vulkan.


--Apple-Mail=_E78A98FB-1845-46B1-A9D5-AEF68BFD3C9F
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""></div></div></body></html>
--Apple-Mail=_E78A98FB-1845-46B1-A9D5-AEF68BFD3C9F--

--Apple-Mail=_5637E18C-8E11-4089-963D-6648C5F77FCB--

--Apple-Mail=_B3041FBF-49A6-466D-A26A-7BA85A62C252
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQEzBAEBCgAdFiEE7YIgIVSPLJapfaYaETbJ7D8AEGMFAl55TK8ACgkQETbJ7D8A
EGMhrgf+KzvnRv7X1ogocLpP/vK2RpyapxuTYhCO8aZ9qP3E9UOQI9SmchfLJCFb
wAotljdSk9w40kf6D0mwPbAhngWFX93n4o3hPzw/XNIPABJ44532stZ5tId2iqZo
ZTTpRUMEIe0d8OLMmkYo4A4LxYenbe2Qx6kZivZzP3PHF8S7l/NAxjKT3FX4a891
9yZ1L/rc/qCo9/RSbRPgkUIRC1JA39L49j8lS+MCpOd6+TWCVoeUKoFtMssdZjuh
qn0XeLwkhW9PO7DEkJecXP7Me8qogjdKMUDsFrrs59ZrgqrMkmV32ccL5l5VFb8O
DY1YdDQBn409XJfpXzyuGuO/aR0o3A==
=JeTK
-----END PGP SIGNATURE-----

--Apple-Mail=_B3041FBF-49A6-466D-A26A-7BA85A62C252--


From nobody Tue Mar 31 15:54:32 2020
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

--Apple-Mail=_BEDC476E-D585-4C41-BCDA-A5A8BC75A350
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_273254A5-BBF7-4EAC-A8DA-105CEB8C3BCC"


--Apple-Mail=_273254A5-BBF7-4EAC-A8DA-105CEB8C3BCC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

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:
>=20
> Greetings Media-Type Experts
>=20
> 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.
>=20
> 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.
>=20
> 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.
>=20
> 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.
>=20
> Please advise. If a new Media-Type is the right way to go, then please =
review the attached draft registration.
>=20
> Regards
>=20
>     -Mark
>=20
> <ktx-media-registration.txt>
>=20
>=20




--Apple-Mail=_273254A5-BBF7-4EAC-A8DA-105CEB8C3BCC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">As =
requested, please advise on the following. Sending again in case it was =
not forwarded to the list.<div class=3D""><br class=3D""></div><div =
class=3D"">Regards<br class=3D""><br class=3D"">&nbsp; &nbsp; -Mark<br =
class=3D""><div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D"">On Mar 23, 2020, at 16:56, Mark Callow &lt;<a =
href=3D"mailto:khronos@callow.im" class=3D"">khronos@callow.im</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><meta =
http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii" =
class=3D""><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; line-break: after-white-space;" class=3D""><div class=3D"" =
style=3D"font-family: HelveticaNeue;">Greetings Media-Type =
Experts</div><div class=3D"" style=3D"font-family: HelveticaNeue;"><br =
class=3D""></div><div class=3D"" style=3D"font-family: HelveticaNeue;">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.</div><div class=3D"" style=3D"font-family: HelveticaNeue;"><br =
class=3D""></div><div class=3D"" style=3D"font-family: =
HelveticaNeue;">Khronos has almost completed a new version of the =
specification known formally as&nbsp;<a =
href=3D"http://github.khronos.org/KTX-Specification/" class=3D"">The KTX =
File Format Version 2</a>&nbsp;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.</div><div class=3D"" style=3D"font-family: HelveticaNeue;"><br =
class=3D""></div><div class=3D"" style=3D"font-family: =
HelveticaNeue;"><div class=3D"">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.</div></div><div class=3D"" =
style=3D"font-family: HelveticaNeue;"><br class=3D""></div><div class=3D""=
 style=3D"font-family: HelveticaNeue;">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.</div><div =
class=3D"" style=3D"font-family: HelveticaNeue;"><br class=3D""></div><div=
 class=3D"" style=3D"font-family: HelveticaNeue;">Please advise. If a =
new Media-Type is the right way to go, then please review the attached =
draft registration.</div><br class=3D"" style=3D"font-family: =
HelveticaNeue;"><div class=3D"" style=3D"font-family: =
HelveticaNeue;"><div class=3D"" style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;">Regards<br =
class=3D""><br class=3D"">&nbsp; &nbsp; -Mark</div></div><br class=3D"" =
style=3D"font-family: HelveticaNeue;"><div class=3D"" =
style=3D"font-family: HelveticaNeue;"></div></div><span =
id=3D"cid:B86A77C9-D166-4C30-A8EC-F3FCEB8B824F">&lt;ktx-media-registration=
.txt&gt;</span><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dus-ascii" class=3D""><div style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D""><br =
class=3D""><div class=3D"">
<div style=3D"letter-spacing: normal; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D""><br =
class=3D""></div></div></div></div></blockquote></div><br class=3D""><div =
class=3D"">
<div style=3D"color: rgb(0, 0, 0); letter-spacing: normal; orphans: =
auto; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><br class=3D""></div>

</div>
<br class=3D""></div></body></html>=

--Apple-Mail=_273254A5-BBF7-4EAC-A8DA-105CEB8C3BCC--

--Apple-Mail=_BEDC476E-D585-4C41-BCDA-A5A8BC75A350
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQEzBAEBCgAdFiEE7YIgIVSPLJapfaYaETbJ7D8AEGMFAl6DygwACgkQETbJ7D8A
EGMVZgf+MBVbGT1ObCR2kaiEvmIm0iMBAW0qypVxOXHr6E7Xb/70iUPwVyc3gybU
VHf5xi4oMNnTf1RXVJ2eMi1J6iuk8/ElfR5HheVe/jjKj56NyaFLjJdfZsRBcBID
OUB2lgUwksa9I0sFQM61dVSZwxfDXkjciPzq/74jztIUPESdlQyRX54RPJBAyPyI
kliraDptxyJhQWq14ulY6xfVIXJfH6b0Ir04xX0sh4aJUjzCshNscNAIiOvYhL9E
SqB7yqgZyatFt2/YqXY2MCejQJsPb374y9Oo9iO/RgqUpt5CzZa21TtFXJTWEXfu
Vmazmr3uw4xOKYgS6agYDBBNmiqadA==
=Cm+d
-----END PGP SIGNATURE-----

--Apple-Mail=_BEDC476E-D585-4C41-BCDA-A5A8BC75A350--

