
From nobody Wed Dec 23 14:35:54 2020
Return-Path: <superuser@gmail.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 0A9683A0EED for <media-types@ietfa.amsl.com>; Wed, 23 Dec 2020 14:35:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.198
X-Spam-Level: 
X-Spam-Status: No, score=-0.198 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=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=gmail.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 NYyOK6WFrcnj for <media-types@ietfa.amsl.com>; Wed, 23 Dec 2020 14:35:52 -0800 (PST)
Received: from mail-vk1-xa29.google.com (mail-vk1-xa29.google.com [IPv6:2607:f8b0:4864:20::a29]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2405C3A0EEB for <media-types@ietf.org>; Wed, 23 Dec 2020 14:35:52 -0800 (PST)
Received: by mail-vk1-xa29.google.com with SMTP id q66so132498vke.0 for <media-types@ietf.org>; Wed, 23 Dec 2020 14:35:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=A87Paud4ZcuIFapoEw9X5HzXQ1BBzCxDiQbGd5J3IjA=; b=uiGXeMwXojIe25oGaddrNYUIaItZbZCkmt00qz3L/iVnjdcBUYNELF8/MsyGsnSnzc KkNBIFGM4sTQ93GqQ3GlOH9Wn3Ez6402XarxuENF0QFGyn02G7COU4mVfPaUT6JV+Ru8 mNaFxghHOIu9e0VE78OtE+kC5hJic1tDg3Shh1TzwGUB8ykWaZ5WONbJgkk0bcbyORYI P1I6HDXnqqyYvs+F4VIR4F9YNKsWefKFAHKQ9UKHm9c0HTebrfH1WtvjypY4UBvrxbWE a7CkqlwNDiiqxuZLiKxcDbX5Qj2UhZRJ0CwYwzTYtI8d6MlZA59yzoyTM7IsfbJhQ4S1 wavA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=A87Paud4ZcuIFapoEw9X5HzXQ1BBzCxDiQbGd5J3IjA=; b=QftI3FjkCokCvb27iBW5bWYmu9UarDYZ9I+R594zmUdP/RCAWvy+YRNBLFBy7ZmL0d /3/T5g5X2OY9+z8N/z8BusfSrn6VWU7duwi1rn1X7mFFQg4bpzN3PPLodYV16H5c3mLZ 4ocnkfJkYWgKpeK1Aa6YcYLlGU3EAyoJBas9+gb4a2Hktldl7+HoMod75qcnwVtEqx8t eZvvaDZerXOa8r07vMo7iNPZsJous/sq2XRPN1bqEpWfvZHPcSAJCzori5GzUr4wBpfv YGFjoRfOMGIFDmnDu47sJBMLNF4BG+VsuEZyWN/ppsCOrBKIL9hNDSPtEITPjktmkJvO nizA==
X-Gm-Message-State: AOAM532LQE6hDazQUOJ1qTou0QxEJ8Gzd7eFFPcTu1KxvCFuAfiYVJN6 WMkUNahE9JLxeXKAIAhKC1km5QKQF5Cies7+TqVudNhZ
X-Google-Smtp-Source: ABdhPJwJPqlb+v0Gsxs6vXABmRN53Gxx5e5R2QnpAg/vyL/7McodmERs+IS30x1G7z6vjvCb/YblPAZ0B0/4GGQFG9k=
X-Received: by 2002:ac5:cc75:: with SMTP id w21mr20694477vkm.14.1608762951040;  Wed, 23 Dec 2020 14:35:51 -0800 (PST)
MIME-Version: 1.0
References: <e2ee2ce0-641f-de3e-b1b6-d375b24328ad@rhiaro.co.uk> <029ad5c8-b441-3a1e-997d-af1187bc8149@rhiaro.co.uk>
In-Reply-To: <029ad5c8-b441-3a1e-997d-af1187bc8149@rhiaro.co.uk>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Wed, 23 Dec 2020 14:35:38 -0800
Message-ID: <CAL0qLwYAnCSi6XQ2u8d-Xpt0SezpAiVbhGyDorrDm3vN-Sk9FA@mail.gmail.com>
To: rhiaro <amy@rhiaro.co.uk>
Cc: media-types@ietf.org
Content-Type: multipart/alternative; boundary="00000000000039816505b729508f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/uQd0XdvdRjaB5THeXzPeP1K7Uv8>
Subject: Re: [media-types] Media subtypes containing "+"
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, 23 Dec 2020 22:35:54 -0000

--00000000000039816505b729508f
Content-Type: text/plain; charset="UTF-8"

Hi Amy, sorry for the delay.  Thanks for taking this on.

A question and a suggestion:

(1) In terms of handling, you might also propose this to art@ietf.org (the
general ART area mailing list) and to dispatch@ietf.org (the DISPATCH
working group); the latter would be the place to get a discussion going
about an appropriate venue for handling the document.

(2) I'm unclear on the nomenclature, in particular that the most specific
suffix is the first in the list of suffixes (when read left to right) and
the most generic is last.  My thought is that the list needs to be ordered,
and we just need to specify what that ordering is.  For instance, I'm
dreaming up a (possibly absurd) example of "foo+zip+gzip".  Would I un-gzip
it first, or unzip it first, with the goal of getting a "foo" out of it?
Why would I consider one of them more specific or generic than the other?

If (based on the end of Section 1.1) what you're suggesting is actually to
in effect consider "+zip+gzip" a single unified suffix of its own, then I
think what we're really saying here is that there's only ever one suffix,
but that suffix can contain a "+".  That is, when parsing the media
subtype, the suffix is everything at and after the first "+" irrespective
of how many "+" characters there are.  If that's the case, it might be
simpler to just say it that way so that the reader doesn't need to think
about a gradation of most-to-least specific.

-MSK

On Mon, Nov 30, 2020 at 6:49 AM rhiaro <amy@rhiaro.co.uk> wrote:

> Hi all,
>
> As requested, we have a draft which is an update to RFC 6838, so that we
> can discuss something concrete around multiple subtype suffixes:
>
>
> https://datatracker.ietf.org/doc/draft-w3cdidwg-media-types-with-multiple-suffixes/
>
> Does anybody have a few moments to review this, so we can work on moving
> this forward?
>
> Many thanks,
>
> Amy
>
> On 24.10.2020. 16:35, rhiaro wrote:
> > Hi all,
> >
> >> Is someone from the W3C willing to put such a draft together?
> > I'm a member of the W3C DID WG and have at long last drafted the update
> > to RFC6838 that has been discussed in this thread:
> >
> >
> https://datatracker.ietf.org/doc/draft-w3cdidwg-media-types-with-multiple-suffixes/
> >
> > I hope I have captured the intent of the comments so far in this thread
> > and used the correct language. Any and all feedback on refining this is
> > gratefully received.
> >
> > Amy
> >
> >
> > _______________________________________________
> > media-types mailing list
> > media-types@ietf.org
> > https://www.ietf.org/mailman/listinfo/media-types
> >
>
> _______________________________________________
> media-types mailing list
> media-types@ietf.org
> https://www.ietf.org/mailman/listinfo/media-types
>

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

<div dir=3D"ltr"><div><div>Hi Amy, sorry for the delay.=C2=A0 Thanks for ta=
king this on.<br><br></div>A question and a suggestion:<br><br></div><div>(=
1) In terms of handling, you might also propose this to <a href=3D"mailto:a=
rt@ietf.org">art@ietf.org</a> (the general ART area mailing list) and to <a=
 href=3D"mailto:dispatch@ietf.org">dispatch@ietf.org</a> (the DISPATCH work=
ing group); the latter would be the place to get a discussion going about a=
n appropriate venue for handling the document.</div><div><br></div><div>(2)=
 I&#39;m unclear on the nomenclature, in particular that the most specific =
suffix is the first in the list of suffixes (when read left to right) and t=
he most generic is last.=C2=A0 My thought is that the list needs to be orde=
red, and we just need to specify what that ordering is.=C2=A0 For instance,=
 I&#39;m dreaming up a (possibly absurd) example of &quot;foo+zip+gzip&quot=
;.=C2=A0 Would I un-gzip it first, or unzip it first, with the goal of gett=
ing a &quot;foo&quot; out of it?=C2=A0 Why would I consider one of them mor=
e specific or generic than the other?<br><br></div><div>If (based on the en=
d of Section 1.1) what you&#39;re suggesting is actually to in effect consi=
der &quot;+zip+gzip&quot; a single unified suffix of its own, then I think =
what we&#39;re really saying here is that there&#39;s only ever one suffix,=
 but that suffix can contain a &quot;+&quot;.=C2=A0 That is, when parsing t=
he media subtype, the suffix is everything at and after the first &quot;+&q=
uot; irrespective of how many &quot;+&quot; characters there are.=C2=A0 If =
that&#39;s the case, it might be simpler to just say it that way so that th=
e reader doesn&#39;t need to think about a gradation of most-to-least speci=
fic.<br></div><div><br></div><div>-MSK<br></div></div><br><div class=3D"gma=
il_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Nov 30, 2020 at 6:4=
9 AM rhiaro &lt;<a href=3D"mailto:amy@rhiaro.co.uk">amy@rhiaro.co.uk</a>&gt=
; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px=
 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi all,=
<br>
<br>
As requested, we have a draft which is an update to RFC 6838, so that we<br=
>
can discuss something concrete around multiple subtype suffixes:<br>
<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-w3cdidwg-media-types-with=
-multiple-suffixes/" rel=3D"noreferrer" target=3D"_blank">https://datatrack=
er.ietf.org/doc/draft-w3cdidwg-media-types-with-multiple-suffixes/</a><br>
<br>
Does anybody have a few moments to review this, so we can work on moving<br=
>
this forward?<br>
<br>
Many thanks,<br>
<br>
Amy<br>
<br>
On 24.10.2020. 16:35, rhiaro wrote:<br>
&gt; Hi all,<br>
&gt;<br>
&gt;&gt; Is someone from the W3C willing to put such a draft together?<br>
&gt; I&#39;m a member of the W3C DID WG and have at long last drafted the u=
pdate<br>
&gt; to RFC6838 that has been discussed in this thread:<br>
&gt;<br>
&gt; <a href=3D"https://datatracker.ietf.org/doc/draft-w3cdidwg-media-types=
-with-multiple-suffixes/" rel=3D"noreferrer" target=3D"_blank">https://data=
tracker.ietf.org/doc/draft-w3cdidwg-media-types-with-multiple-suffixes/</a>=
<br>
&gt;<br>
&gt; I hope I have captured the intent of the comments so far in this threa=
d<br>
&gt; and used the correct language. Any and all feedback on refining this i=
s<br>
&gt; gratefully received.<br>
&gt;<br>
&gt; Amy<br>
&gt;<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; media-types mailing list<br>
&gt; <a href=3D"mailto:media-types@ietf.org" target=3D"_blank">media-types@=
ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/media-types" rel=3D"n=
oreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/media-ty=
pes</a><br>
&gt;<br>
<br>
_______________________________________________<br>
media-types mailing list<br>
<a href=3D"mailto:media-types@ietf.org" target=3D"_blank">media-types@ietf.=
org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/media-types" rel=3D"norefe=
rrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/media-types</=
a><br>
</blockquote></div>

--00000000000039816505b729508f--


From nobody Wed Dec 23 14:38:10 2020
Return-Path: <superuser@gmail.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 CC5883A0EF4 for <media-types@ietfa.amsl.com>; Wed, 23 Dec 2020 14:38:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.602
X-Spam-Level: 
X-Spam-Status: No, score=0.602 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 hZN-UVoe-Bfo for <media-types@ietfa.amsl.com>; Wed, 23 Dec 2020 14:38:07 -0800 (PST)
Received: from mail-ua1-x935.google.com (mail-ua1-x935.google.com [IPv6:2607:f8b0:4864:20::935]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 99B9F3A0EF3 for <media-types@ietf.org>; Wed, 23 Dec 2020 14:38:07 -0800 (PST)
Received: by mail-ua1-x935.google.com with SMTP id w7so191333uap.13 for <media-types@ietf.org>; Wed, 23 Dec 2020 14:38:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=a/dR13gF4WA1TP760XGDLfjYGVeHE4UmFxVtcetuwXc=; b=tRNOH6tA5ec5zmNoA/Czl14j/EQa1WWEf4AACVvBf2woltzyatQ7XMJYPQf4t2lONn rrLZmlCxNEToRcUknxPtECLTk0Xch24aacCABVb4a+ChRJb6IQ5F4AcBMXj/NkLnHmAD SgGChaiDz2DCK7Hq5uWU6nGtcHCSKmfKzDSWo+dEMV5TaKLlTYqcgcFxkDF435HsfxPV f8QoQnuFyOY3qLmEv6OS0ujOV0z9IhWBLYgfkgrsTwVthD4IpNqmbhcpdbpxU+n7Rvu0 AumVvvGlog4cla13xVez0Py/0Nk4D83RKGaBX7jplWGFC8oYuIwHglWLNB15qBbPszFJ wd8g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=a/dR13gF4WA1TP760XGDLfjYGVeHE4UmFxVtcetuwXc=; b=VIj+OcaPULVjgKUhzVA91Tt8/3WYygLd9sAQOJ3zuJLCpq/fmvDNGHqEISWctpqJR+ lJL4W/68AdqRBcpL5+OxZkdSPDvnSDROG8lFbjRy4biarf7wBWVeHOkL8n9eraycDJ11 fzZrzEMTO+9sqLH1dGdSNVPEbP0S2YcQ7anmPtltJaa++OqXy/iwishq1VdylvmTDgzX T1vYOh25BWxSsf3MbhTDtRUyJuKpCIsYIs0MdkVyuCsw5+2u0zt/Gageh/MCt1CgGfUQ alCIpFfKyPfIZ6kFXBeoSeNRjyd2YFasNknWNqgVuP6cDZnKDACN04ZCpqo+7uoACSHS dubQ==
X-Gm-Message-State: AOAM532TX8vy7kbsL6jG1B9nMbrL1UIbPZGEKJ/pftj3ryTf9ikXdJPs b0N9vPqFzU9tWZd9mRoy/siDtoRTpHGNf1yTdCIk6EAQ
X-Google-Smtp-Source: ABdhPJxyuVgYSruKdtqIg7bivsRzT6G1Jf7QNs1LqfTgQLmCWjdTuERpdrh3iiLlO4bGQe8XcPlR7VkW8wHtPoa18sA=
X-Received: by 2002:a9f:2628:: with SMTP id 37mr17922741uag.87.1608763086375;  Wed, 23 Dec 2020 14:38:06 -0800 (PST)
MIME-Version: 1.0
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Wed, 23 Dec 2020 14:37:54 -0800
Message-ID: <CAL0qLwYbJXKzYEvYWH9ijXpH27eRqgZU78ThLd81cCecJ_E0Wg@mail.gmail.com>
To: media-types@ietf.org
Content-Type: multipart/alternative; boundary="0000000000004a917105b729586f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/icyp9B6hInfMMjEeFIlDhYhGb_8>
Subject: [media-types] Templates for basic MIME types
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, 23 Dec 2020 22:38:09 -0000

--0000000000004a917105b729586f
Content-Type: text/plain; charset="UTF-8"

There are a number of media types registered by RFCs 2045 and 2046
implicitly (e.g., image/jpeg, image/gif).  The media type registry has
entries for them pointing at those two documents, but the documents never
actually present registration templates for any of them.

Just to make the record complete, I plan to send the reviewers a set of
registration templates for them.  I'll post them here as well in case
anyone wants to comment.

I presume we're fine with that approach, rather than requiring an RFC?

-MSK, ART AD

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

<div dir=3D"ltr"><div>There are a number of media types registered by RFCs =
2045 and 2046 implicitly (e.g., image/jpeg, image/gif).=C2=A0 The media typ=
e registry has entries for them pointing at those two documents, but the do=
cuments never actually present registration templates for any of them.</div=
><div><br></div><div>Just to make the record complete, I plan to send the r=
eviewers a set of registration templates for them.=C2=A0 I&#39;ll post them=
 here as well in case anyone wants to comment.</div><div><br></div><div>I p=
resume we&#39;re fine with that approach, rather than requiring an RFC?</di=
v><div><br></div><div>-MSK, ART AD<br></div></div>

--0000000000004a917105b729586f--


From nobody Wed Dec 23 16:08:53 2020
Return-Path: <duerst@it.aoyama.ac.jp>
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 F23BF3A0489 for <media-types@ietfa.amsl.com>; Wed, 23 Dec 2020 16:08:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, MSGID_FROM_MTA_HEADER=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H2=-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=itaoyama.onmicrosoft.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 0ofXaBVbHygJ for <media-types@ietfa.amsl.com>; Wed, 23 Dec 2020 16:08:50 -0800 (PST)
Received: from JPN01-TY1-obe.outbound.protection.outlook.com (mail-eopbgr1400121.outbound.protection.outlook.com [40.107.140.121]) (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 CC10F3A0475 for <media-types@ietf.org>; Wed, 23 Dec 2020 16:08:49 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=J+HA74zVGa4+9GHkEsJLrp43819bIQdbxPexmU7jISgwTSST5ZRcqRNWCVmNchb+vsl9uA5MD33eh2JfFLIk+y1yqRNpsnHJ97r3MDbc2JJYSxAs76QNjAC+vdR7gLhCUXl1EjBwDU8cn+x/T6rNw4Wu0g9bxzg+A1086lGQBpLtXVgZ0ELdDdaRq8oXhYY29u3TjHFuCeborFUr2LOm8cmWnyuv/7rvwL2ULXmUS9FS0uITqN1pwkm4lTtz8KNb3jecmmtlLQOeyTBIup9nfOD1dMzcywz1Zuu6UrpwsZfWN6wiRvNrI8LiG6TxfoOV8ueHusZRyqr+2P5LKH1jig==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=iN712yKY6c1atDh+xMN155/LVY94bOZPOvtftUi9ZiI=; b=NiXsYRHtK9LvF5eqZRAog+3Z08LTs6QXg1sK8MjcZ+oX0Pxz2AiSRQyuW2MNT7zYi1Eca1SGG8oX82d6Z9vbEpg0homgQu0rp+2sJ1AkYlE6hJrmh0DPyqn7zVpgDfCChLVJsFZVemL4F+M3Xbl8mN2NG9xFw8uDWi8IYDDRtA7t2H1UXUZ0Td5voXkKpCeTTGAPgEWa+YCSPljqp1vL60Uqiq+ulkEQJXGgj5sJWP3h9pHxuOlex/H2R4/B4adchmTGIzN/72w3VOyw8sdolRyj7cX4M1UogKeoGYmh6hPTMg7YktMMPqL/xNNF63otGeQ67ge2s0MO1nfYWS+9fA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=it.aoyama.ac.jp; dmarc=pass action=none header.from=it.aoyama.ac.jp; dkim=pass header.d=it.aoyama.ac.jp; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=itaoyama.onmicrosoft.com; s=selector2-itaoyama-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=iN712yKY6c1atDh+xMN155/LVY94bOZPOvtftUi9ZiI=; b=VA/yWXOlK9euUx3Vic/BEFZtM7Yh/3i8cJFAIY7STiYqaRk6hto4lnUSmMw0DFToG0UnYvJ0UfInl8Geq+vKm1sJOccoDxHOe8BgZpixjsMN/cPYM9wbXicDSf6aTOFPRc4Z7dkOi8zSa34GCKLoFzquZrkmugU75vvYtE7J5Tk=
Authentication-Results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=it.aoyama.ac.jp;
Received: from OSBPR01MB2566.jpnprd01.prod.outlook.com (2603:1096:604:1c::13) by OSAPR01MB3089.jpnprd01.prod.outlook.com (2603:1096:604::22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3676.29; Thu, 24 Dec 2020 00:08:47 +0000
Received: from OSBPR01MB2566.jpnprd01.prod.outlook.com ([fe80::cd30:9f1d:e76d:e8a8]) by OSBPR01MB2566.jpnprd01.prod.outlook.com ([fe80::cd30:9f1d:e76d:e8a8%6]) with mapi id 15.20.3676.034; Thu, 24 Dec 2020 00:08:47 +0000
To: media-types@ietf.org
References: <CAL0qLwYbJXKzYEvYWH9ijXpH27eRqgZU78ThLd81cCecJ_E0Wg@mail.gmail.com>
From: =?UTF-8?Q?Martin_J=2e_D=c3=bcrst?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
Message-ID: <7bfe6d8d-18e3-3960-4be9-0815c8082ecf@it.aoyama.ac.jp>
Date: Thu, 24 Dec 2020 09:08:45 +0900
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
In-Reply-To: <CAL0qLwYbJXKzYEvYWH9ijXpH27eRqgZU78ThLd81cCecJ_E0Wg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Originating-IP: [121.118.76.82]
X-ClientProxiedBy: TY2PR04CA0015.apcprd04.prod.outlook.com (2603:1096:404:f6::27) To OSBPR01MB2566.jpnprd01.prod.outlook.com (2603:1096:604:1c::13)
MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
Received: from [192.168.1.6] (121.118.76.82) by TY2PR04CA0015.apcprd04.prod.outlook.com (2603:1096:404:f6::27) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3700.27 via Frontend Transport; Thu, 24 Dec 2020 00:08:47 +0000
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 0756c8f7-ff46-42f8-f8ae-08d8a7a015b0
X-MS-TrafficTypeDiagnostic: OSAPR01MB3089:
X-Microsoft-Antispam-PRVS: <OSAPR01MB30894F2AA441A3DEA9AC3676CADD0@OSAPR01MB3089.jpnprd01.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:8882;
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: GgD4Nnfgu+iWC5LD7bCtL6CNPPcHoBbsNq5oVwWuKhINtAZgJDXiPclNfTG8ClfYoLHWyAOmyVZ5PqUOOuBK39EXLY3+h3rqTeA3KVejo6hlF7UnGQDhz+BIBGXIHew0rfPEQ7GV0VIXq+IJMdXCO9JIjIgf9QYupfQR4gxS23EdHrG1+b/J+ymEZXhdr3YKYF36lGEOeGuEheks9+l1KpXz1Sg+icB+X77AdwfS5YPNxjHRtqGlQ0e5lo/OhtnslZF9svJ63bq8czNXtqWJHwk+rnWj0tw510thKZzk2zErrPidvZRRhPI+qlOdzGvBANJcpaE4uzjYTbekQBmp4c7KpyNa2MXTIFA0KlqMUfTk0fyXNbyBdaRsdzARTt9lyFM4n1D6s5lQ1CX7QiDa1e+ActlMSvggOVYiYHY+VVNLLbhON8pyYWLzvJCm0cX3y44hyc5yDcUb9AoTB6pEmxBIUkginif0Nw+Kw1SOCRMP2yL/cg+eLh7yOsKR1UBW7lXx0BIsIJcMwNPGHwRpdg0aay2R/ze6GL+BY0TrkzwDBoGgSdp7JM7HBq+l+qXp
X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:OSBPR01MB2566.jpnprd01.prod.outlook.com; PTR:; CAT:NONE;  SFS:(366004)(396003)(39840400004)(376002)(346002)(136003)(16526019)(8936002)(66946007)(53546011)(66476007)(186003)(31686004)(956004)(2616005)(66556008)(8676002)(4744005)(6486002)(26005)(2906002)(966005)(86362001)(52116002)(36916002)(478600001)(16576012)(316002)(786003)(5660300002)(6916009)(31696002)(43740500002)(45980500001); DIR:OUT; SFP:1102; 
X-MS-Exchange-AntiSpam-MessageData: =?utf-8?B?UG5qL2s3T1VmUzFQVC9pdkNBOGNHRVJZbzFpbnRHeVowUVcvOXBBSmpudTVs?= =?utf-8?B?RmN4VFBTUGwzemhzekhBRkVZb0N0YU1lZlhQSyt4UXdhYnZkT1BFbmVDVGRj?= =?utf-8?B?a2R0Tk1IR3A1RE44R2FhVUJLREVNMm83Tk9pRSt1K3JTY3VFYlZabG04djhk?= =?utf-8?B?Nm9qdlJITERUYW1hQmRCeDZTakxqR1ExbUhEWW5ZVk94SDhSaTlEdXg5amZ5?= =?utf-8?B?Q1QrVm85cUJFWFRJZHlucm9hY29kYUk3QVBSUnZLY2ErK1pKSi9kOFU4UFBj?= =?utf-8?B?N1phWTllKzZrZHliZDg1VHlkYjlTdEdFZkdoellPbm1SbHBrQm13RzFwbHRW?= =?utf-8?B?ZU5FUUtFNkdwbzFOd3RpRm9QNGJwN0VaZm5XUWN3dW5hMjIydDMyS1RDVFRj?= =?utf-8?B?ZHNLNTRSNExuWWdXZWRxQStvVmhNb09GemJyUWd5TStvamZlSzRRS05TQmM3?= =?utf-8?B?enRYMWVqc2g0ak5lUGErY3VIcWxUV3JrcjZIZi9QSCtLb2JWenNVMExHNStI?= =?utf-8?B?eFN2dVI1M2VqdHAyaWYxVnphYjhpMU9OeC9PV2oyMlNuVWJ0c3UzQm51eDYz?= =?utf-8?B?RWFkN0psOFZqK01ieFN3RmZDTW9uSkRFeFJPWjlKdUJhYkUxVUlFUWd2SVdV?= =?utf-8?B?TXNyTnovczFBV2tUZDMxdUt0QklCbFVPZ3ZXN0l2U1pKUVNTQmQyNHRGMURh?= =?utf-8?B?U3N0enVZUFdWOVUrU1JYY2pVNEMreGR0Y25GSEc2dXJQK3RlV0xkRmpwNE93?= =?utf-8?B?S3FpdFA5bDFHRlJ0Tll3VDlIZkRxYnZQQXF4QTl2blBFUXB4MG9FQThWZzMv?= =?utf-8?B?REZmMDZqb0h0ajBOdHhiL0hzcUtzNGZWUHcvMzh0dXRla01mbWM2aFIrZU9E?= =?utf-8?B?bEs3aEVCU0lmNFFaekc4Z25PRytLUHlvdVo2M09EelR5Zk9hQmdha1RmeWJC?= =?utf-8?B?Q1BlSkVmSWdadWFvc1lZcWRBYmhuN1cyMDQxcnBhK1J1QUFCYmp2cEVibkh1?= =?utf-8?B?WCtnMmJob2gyUTR4UGdsaXNDeFdkM1JNK3NnT1huWUwxYVBuZmJtRmkwd2hS?= =?utf-8?B?Wjc5andyZGhPeitRNFpRdlc1dVVlc2p6T3p1YkpFekU5b1RLLzhoYjZhV2pF?= =?utf-8?B?bkJhSUJ6Z2JGb3pRRzRZL1lqL0o2Vk9ON2FhMzZ3dXBRdlQ2dFh3MlU1ZFdm?= =?utf-8?B?b1N4MVUvbWZadUl5dWVFVU1nME5tek1OeTNkeStBaTA0TCs3eU5VeGI5NDBu?= =?utf-8?B?RUZpV0YyZVlYdkZDZC9XNmpVNkxSa2h3WXZBYnBjOXFwU3FXMmpUdnJWRmta?= =?utf-8?Q?ILNIfSotjvZMPyrCxTD2oVP6LN/QA5/bkN?=
X-OriginatorOrg: it.aoyama.ac.jp
X-MS-Exchange-CrossTenant-AuthSource: OSBPR01MB2566.jpnprd01.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 24 Dec 2020 00:08:47.2821 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: e02030e7-4d45-463e-a968-0290e738c18e
X-MS-Exchange-CrossTenant-Network-Message-Id: 0756c8f7-ff46-42f8-f8ae-08d8a7a015b0
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: 7JiMz9kx9MC10vDyL+09V05ie4w/9W3SbY86yz/42ZxciaFQxqU058kX+Fslh9clR+f6078wPttoe/iaYSBdAw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: OSAPR01MB3089
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/eQ6PRmwqHIUvEeXRRzh95WN58d0>
Subject: Re: [media-types] Templates for basic MIME types
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, 24 Dec 2020 00:08:52 -0000

On 24/12/2020 07:37, Murray S. Kucherawy wrote:
> There are a number of media types registered by RFCs 2045 and 2046
> implicitly (e.g., image/jpeg, image/gif).  The media type registry has
> entries for them pointing at those two documents, but the documents never
> actually present registration templates for any of them.
> 
> Just to make the record complete, I plan to send the reviewers a set of
> registration templates for them.  I'll post them here as well in case
> anyone wants to comment.
> 
> I presume we're fine with that approach, rather than requiring an RFC?

Very fine indeed, given that for 24 years, we were able to do even 
without the templates.

Regards,   Martin.

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


From nobody Wed Dec 23 16:48:19 2020
Return-Path: <chris@w3.org>
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 F30743A0972 for <media-types@ietfa.amsl.com>; Wed, 23 Dec 2020 16:48:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bkArW4nGtPrH for <media-types@ietfa.amsl.com>; Wed, 23 Dec 2020 16:48:15 -0800 (PST)
Received: from raoul.w3.org (raoul.w3.org [128.30.52.128]) (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 B65F83A0962 for <media-types@ietf.org>; Wed, 23 Dec 2020 16:48:15 -0800 (PST)
Received: from [62.74.91.105] (helo=[192.168.2.105]) by raoul.w3.org with esmtpsa (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from <chris@w3.org>) id 1ksEnc-0008Rm-JW for media-types@ietf.org; Thu, 24 Dec 2020 00:48:12 +0000
Content-Type: multipart/alternative; boundary="------------hcgh/PT4bt-DUtsO4WhbtbOy"
Message-ID: <544915d5-37a9-cc73-065c-bd1e694dfee2@w3.org>
Date: Thu, 24 Dec 2020 02:48:09 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:85.0) Gecko/20100101 Thunderbird/85.0
Content-Language: en-US
To: media-types@ietf.org
References: <CAL0qLwYbJXKzYEvYWH9ijXpH27eRqgZU78ThLd81cCecJ_E0Wg@mail.gmail.com>
From: Chris Lilley <chris@w3.org>
In-Reply-To: <CAL0qLwYbJXKzYEvYWH9ijXpH27eRqgZU78ThLd81cCecJ_E0Wg@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/MOAGuzcK7pdkvMp5CfdMBAeQBoU>
Subject: Re: [media-types] Templates for basic MIME types
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, 24 Dec 2020 00:48:18 -0000

This is a multi-part message in MIME format.
--------------hcgh/PT4bt-DUtsO4WhbtbOy
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

I'm happy to review any of the image media types.

On 2020-12-24 00:37, Murray S. Kucherawy wrote:
> There are a number of media types registered by RFCs 2045 and 2046 
> implicitly (e.g., image/jpeg, image/gif).Â  The media type registry 
> has entries for them pointing at those two documents, but the 
> documents never actually present registration templates for any of them.
>
> Just to make the record complete, I plan to send the reviewers a set 
> of registration templates for them.Â  I'll post them here as well in 
> case anyone wants to comment.
>
> I presume we're fine with that approach, rather than requiring an RFC?
>
> -MSK, ART AD
>
> _______________________________________________
> media-types mailing list
> media-types@ietf.org
> https://www.ietf.org/mailman/listinfo/media-types

-- 
Chris Lilley
@svgeesus
Technical Director @ W3C
W3C Strategy Team, Core Web Design
W3C Architecture & Technology Team, Core Web & Media

--------------hcgh/PT4bt-DUtsO4WhbtbOy
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>I'm happy to review any of the image media types.<br>
    </p>
    <div class="moz-cite-prefix">On 2020-12-24 00:37, Murray S.
      Kucherawy wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAL0qLwYbJXKzYEvYWH9ijXpH27eRqgZU78ThLd81cCecJ_E0Wg@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">
        <div>There are a number of media types registered by RFCs 2045
          and 2046 implicitly (e.g., image/jpeg, image/gif).Â  The media
          type registry has entries for them pointing at those two
          documents, but the documents never actually present
          registration templates for any of them.</div>
        <div><br>
        </div>
        <div>Just to make the record complete, I plan to send the
          reviewers a set of registration templates for them.Â  I'll post
          them here as well in case anyone wants to comment.</div>
        <div><br>
        </div>
        <div>I presume we're fine with that approach, rather than
          requiring an RFC?</div>
        <div><br>
        </div>
        <div>-MSK, ART AD<br>
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <pre class="moz-quote-pre" wrap="">_______________________________________________
media-types mailing list
<a class="moz-txt-link-abbreviated" href="mailto:media-types@ietf.org">media-types@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/media-types">https://www.ietf.org/mailman/listinfo/media-types</a>
</pre>
    </blockquote>
    <pre class="moz-signature" cols="72">-- 
Chris Lilley
@svgeesus
Technical Director @ W3C
W3C Strategy Team, Core Web Design
W3C Architecture &amp; Technology Team, Core Web &amp; Media</pre>
  </body>
</html>
--------------hcgh/PT4bt-DUtsO4WhbtbOy--


From nobody Thu Dec 24 00:26:44 2020
Return-Path: <duerst@it.aoyama.ac.jp>
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 83FE93A10E2 for <media-types@ietfa.amsl.com>; Thu, 24 Dec 2020 00:26:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, MSGID_FROM_MTA_HEADER=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H2=-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=itaoyama.onmicrosoft.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 XSPBzU7i0_n4 for <media-types@ietfa.amsl.com>; Thu, 24 Dec 2020 00:26:40 -0800 (PST)
Received: from JPN01-OS2-obe.outbound.protection.outlook.com (mail-eopbgr1410094.outbound.protection.outlook.com [40.107.141.94]) (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 5A8933A10E0 for <media-types@ietf.org>; Thu, 24 Dec 2020 00:26:39 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=kwIDTfDNOp1QpYpUtv6XShVYQkfQgCpNIO28ECPCKLNrEhzr2n5JPk0KXBjV2MCZ5nMvqKjcDIJo1/xamKwygN9q340Hd3Jy2qaopJanUfB+OqVFLG9RAMN7ceMfWV46UhoHbbiUufJSeZnXVL3MvnC9LDOWb4rRE1OS2eosuD34Z117pwwsRM2Cu28KU3rSyBT6va+BBBJZiHDcf13kAIENlbqRUaoYO662MrMoQsxyIWglWrnYiLHn4geXHGV28Yk5x/vixWSd8cjJAoZtZJJAQR4+jpHeSXeD70ATpSthIlu0fdTwEOCMDsRLt5xac9oYJAmX3tWPzXU1BR7ewA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=NavnaAmDbhqMYlR68p25VBJWvqyVTiywGWn+ho+FZaU=; b=IDrhPbTvqRAdooXVLGC9g6HOQtZz0lsuU35GRK60lUr7TpVY50aLqT/7ZPk0VziWOh7TrfGo9xhkxCA03Btt4zKC2oz6tAFfiVQE9Vlaw2rb/i4V4P5czz5a1MH8BeU+aulNFgsqWdC10bzzSNK9o2Y8xUhgzJHFsQfNSjsIHx1qp6mkEjyz4+lx41Vgd1mmWiNzlgqZExiGo28MlG2+yASvdjT5tkt7H+HUXDkpRKhaTHiZPel9ZwkRKxF32KXB8jSENVB9gTZeLTu895rRw4zajbKy3LOm9ZpU4BkFkbSYVMy40I8JX6TBvroKLBoMhDxU8XoizNJD+t6R7eHRpQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=it.aoyama.ac.jp; dmarc=pass action=none header.from=it.aoyama.ac.jp; dkim=pass header.d=it.aoyama.ac.jp; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=itaoyama.onmicrosoft.com; s=selector2-itaoyama-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=NavnaAmDbhqMYlR68p25VBJWvqyVTiywGWn+ho+FZaU=; b=SrYtplSQ9wEBEbW2jiklHaszf31lEykxJKW4Hf5+3ZX2n4hT4s7d8pEccKuXCuE5wDLD1OVC5R1VRHc0t6xnYNjhg4YpcXq6DM58fSy0gcbx9y2pKlVzSYgXFTt6dv6F2bpDhNl5jwOA2OXesgSdd3H1S+34O0KdKkf2I6Z17PM=
Authentication-Results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=it.aoyama.ac.jp;
Received: from OSBPR01MB2566.jpnprd01.prod.outlook.com (2603:1096:604:1c::13) by OSBPR01MB1733.jpnprd01.prod.outlook.com (2603:1096:603:6::22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3676.33; Thu, 24 Dec 2020 08:26:33 +0000
Received: from OSBPR01MB2566.jpnprd01.prod.outlook.com ([fe80::cd30:9f1d:e76d:e8a8]) by OSBPR01MB2566.jpnprd01.prod.outlook.com ([fe80::cd30:9f1d:e76d:e8a8%6]) with mapi id 15.20.3676.034; Thu, 24 Dec 2020 08:26:33 +0000
To: "Murray S. Kucherawy" <superuser@gmail.com>, rhiaro <amy@rhiaro.co.uk>
Cc: media-types@ietf.org
References: <e2ee2ce0-641f-de3e-b1b6-d375b24328ad@rhiaro.co.uk> <029ad5c8-b441-3a1e-997d-af1187bc8149@rhiaro.co.uk> <CAL0qLwYAnCSi6XQ2u8d-Xpt0SezpAiVbhGyDorrDm3vN-Sk9FA@mail.gmail.com>
From: =?UTF-8?Q?Martin_J=2e_D=c3=bcrst?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
Message-ID: <44a5b068-6843-b176-66ff-7926d598bb36@it.aoyama.ac.jp>
Date: Thu, 24 Dec 2020 17:26:31 +0900
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
In-Reply-To: <CAL0qLwYAnCSi6XQ2u8d-Xpt0SezpAiVbhGyDorrDm3vN-Sk9FA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Originating-IP: [121.118.76.82]
X-ClientProxiedBy: TY1PR01CA0167.jpnprd01.prod.outlook.com (2603:1096:402::19) To OSBPR01MB2566.jpnprd01.prod.outlook.com (2603:1096:604:1c::13)
MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
Received: from [192.168.1.6] (121.118.76.82) by TY1PR01CA0167.jpnprd01.prod.outlook.com (2603:1096:402::19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3700.27 via Frontend Transport; Thu, 24 Dec 2020 08:26:31 +0000
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 3f8d1203-b394-49bb-1fc7-08d8a7e59f05
X-MS-TrafficTypeDiagnostic: OSBPR01MB1733:
X-Microsoft-Antispam-PRVS: <OSBPR01MB17331AC735D4E31C9DD5CB3ACADD0@OSBPR01MB1733.jpnprd01.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:8882;
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: fn6Bxw59UEJaubftwyGDvXxyaoQsTJxbW1t2iQuKmIDnIp82gftNNSOYj4N1sF7wrKAYPPzhUD8sM7Rm6rqqTu9QaQkBdfwimwyI5euzOOfVWGcykBmmYvuZ4YRE00U5sgvADOOy+CD5bgyDkIYDxSgoDfPUBRfr4FQYxyKmHobfaqcizXy9SgEkXECpElXAF3iis9ZpFNsycQXcTzJptanTshZo71EhVSG/KvPgWirrBxViyF0fW/iYbCPn5sDiBS9CdcYVT5Lu+kt5RE2p7ErqhDOifbUKFuN2OzF+Y6CXRJme5LToE54dboHFP1Qwwvd2hM5QhlfcRI38QOvPMAWHTqsz4KHgf2bjO9ZMulvciCDbEblTN9yERxLl1qFm2eK7yV82sEMhx0Nm63Skjdky1giAuRmOzfaCX2Fi8qIy/Lqx4R2DVD1KT6gzbKfLzvDSzpH4t9lm05zmVSWYg/P+JLh8UlPkIsKZmC540Y1Pj/brohg4urxWw5Gt5ncamEYNFoatF9KQLH9j8mJnf/GqLsdZhfkvQuaIShMB5EW9XCfl3aDCNYPfS/EfuwP9
X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:OSBPR01MB2566.jpnprd01.prod.outlook.com; PTR:; CAT:NONE;  SFS:(39850400004)(136003)(396003)(376002)(346002)(366004)(786003)(5660300002)(53546011)(316002)(52116002)(86362001)(8676002)(16576012)(110136005)(31686004)(956004)(66476007)(4326008)(2906002)(2616005)(66946007)(36916002)(66556008)(83380400001)(186003)(478600001)(26005)(6486002)(16526019)(966005)(8936002)(31696002)(43740500002)(45980500001); DIR:OUT; SFP:1102; 
X-MS-Exchange-AntiSpam-MessageData: =?utf-8?B?NkttWmdjaGtHTktCUUMvcTJzdWJnUm1wQUlsZ2tDNDBHTW9nQWNadDJNNEU1?= =?utf-8?B?MjNpTC9QNkNTRFdCVXdyWllVSjc0OS9DcUh5MWVDQzNpSUN2a0lweU1zWXM3?= =?utf-8?B?OS9PU1AwaHFZM3RrYXV0eHFrRWswcWszcE5xYm9jQ29mYkIrSUZqZlR1U0Qv?= =?utf-8?B?UHZ2RllURU9PemZadGZrOUtpZzd4Q1FiRE9aZ0tzV1NUbk12TVpRRnRNTm1L?= =?utf-8?B?TXdWM1Q2VUNrd2VxOFJtQmlRQ29iK0dqZTdFZkFkVllIYVdxdjBMS0tQVmdR?= =?utf-8?B?eGtDNkpNOFk2ZkdiL1JQMHVILzI5MnlZdWJtOGxQSXNwWkwrQlNBbXdmQktM?= =?utf-8?B?czJsRWdtQ3V2NlpmMXNjRE81VjR4MlhWdityc040TWQzaGFMUis1Y3F6MVgr?= =?utf-8?B?cFRCL0lNdmV1N3ZNZGdSQmZPZHpGN1MzOG9UaTRpS3RJQ0lDZ2dwTE9tdEU4?= =?utf-8?B?Y2I2NXdJUjhHOFZLNk5ZZ0FUcFk1Y2NlempabWVQM1JvZ3hkT3J3clNZODFv?= =?utf-8?B?WXNXN2cvTWJEK3FUa0dDWkU1ZStOcGFmcVhpb0FDenRYd3JBdkg4S0lIV25T?= =?utf-8?B?VktidFgxYlAvOVIwNWpMaUM1UmRsVEN4ZnF4L3R5bitjdDZVUFFsWWhWQk5M?= =?utf-8?B?b0NiNkRDNVM4cjZKRHhiYlVyd2Njd2YrNDdKc3g1KzB6Y0FsUTF4eDdnSU0z?= =?utf-8?B?eDc4UlNrQm13UDRTTVRDekhHQlY0YlZNK2lrcGtxQjZVaVVYVG1ub0JmdlhM?= =?utf-8?B?ODZpVnlBK3lBLzZiL2NVZlVseVA0SVFnTUY2bW5qMlZ2eFJPVFFqV2ZXeFJN?= =?utf-8?B?a1hMb1A0WVhWZnc3SkEycFYwL0oxcVFGbURENVZTeElOOFl0amhGaU5MckZT?= =?utf-8?B?ZGtXTG5pbU9CMnBLc28xS3NXSlhZUGtPVlB3RzhHMGhiSnZVdmV6d1hXTkYw?= =?utf-8?B?QzV5akJOei9pTkduSDVFWFJPU0g1MnZnVXVVOXpab2lHV0xpTjBwdVRxVWk1?= =?utf-8?B?U2ZmM3U2dkVWbTlvSDlVdloxY3M2Ri90L3NhRXc3K0ViQUtlNEE2d1p4UkU2?= =?utf-8?B?SmZoU0J1Ym1kd0hxbWw2NFBlejBENkxTV0hVWnRRbUw2N0pPZDZSZkZQdGlP?= =?utf-8?B?b05ZZWdZUlk1NHU3eU5UWHZ2aDBiU2JwRnYyWHJNZjViR0ovWWVKTk8wZDdT?= =?utf-8?B?eHE1T09Xdjg2djJ2RU1DenR6ZUxZRjEycS82cktIQkdsSllUbVdUVzB5NTdn?= =?utf-8?B?SUE2UE02V09BZk9zSFU4NHpOMG8vSXFtZGN6YVFFTXIvVm5obXVvN1pUV3Vi?= =?utf-8?Q?S9C0U5P1DoqKYHzeLJHGQ7CIU4VqiYnMV8?=
X-OriginatorOrg: it.aoyama.ac.jp
X-MS-Exchange-CrossTenant-AuthSource: OSBPR01MB2566.jpnprd01.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 24 Dec 2020 08:26:32.9717 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: e02030e7-4d45-463e-a968-0290e738c18e
X-MS-Exchange-CrossTenant-Network-Message-Id: 3f8d1203-b394-49bb-1fc7-08d8a7e59f05
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: mTzBo2kFMlaTO28Vhslpbw4no+jOl6NdLJsO+VcDiPD8rwcCm6GLqD0csToBXHn/nuSacUG3eJNNQWShy8U6PQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: OSBPR01MB1733
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/drz2ENdsXUgIfj-G_LfxailQBDE>
Subject: Re: [media-types] Media subtypes containing "+"
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, 24 Dec 2020 08:26:43 -0000

On 24/12/2020 07:35, Murray S. Kucherawy wrote:
> Hi Amy, sorry for the delay.  Thanks for taking this on.
> 
> A question and a suggestion:
> 
> (1) In terms of handling, you might also propose this to art@ietf.org (the
> general ART area mailing list) and to dispatch@ietf.org (the DISPATCH
> working group); the latter would be the place to get a discussion going
> about an appropriate venue for handling the document.
> 
> (2) I'm unclear on the nomenclature, in particular that the most specific
> suffix is the first in the list of suffixes (when read left to right) and
> the most generic is last.  My thought is that the list needs to be ordered,
> and we just need to specify what that ordering is.  For instance, I'm
> dreaming up a (possibly absurd) example of "foo+zip+gzip".  Would I un-gzip
> it first, or unzip it first, with the goal of getting a "foo" out of it?
> Why would I consider one of them more specific or generic than the other?

If I understand correctly, you would un-gzip it first, and only then 
unzip it. In a slightly more realistic example, let's use svg+xml+gzip. 
Gzip is more generic (because it can be applied to any kind of data) 
than xml, and you definitely first have to un-gzip before feeding the 
document into an XML parser.

But you may be right that there are cases where the terminology 
'generic'/'specific' may not be adequate. foo+gzip+zip (foo gzipped and 
then zipped) may make as much (or as little!) sense as foo+zip+gzip,


> If (based on the end of Section 1.1) what you're suggesting is actually to
> in effect consider "+zip+gzip" a single unified suffix of its own, then I
> think what we're really saying here is that there's only ever one suffix,
> but that suffix can contain a "+".  That is, when parsing the media
> subtype, the suffix is everything at and after the first "+" irrespective
> of how many "+" characters there are.  If that's the case, it might be
> simpler to just say it that way so that the reader doesn't need to think
> about a gradation of most-to-least specific.

The problem with this approach may be that currently existing 
implementations, as well as some future implementations, may just look 
at the rightmost + and the following alphabetic characters. Therefore, 
you need to make sure that people constructing/proposing suffix 
combinations will choose the right order, and that means that you have 
to have some language about suffix ordering anyway.

Regards,   Martin.


> -MSK
> 
> On Mon, Nov 30, 2020 at 6:49 AM rhiaro <amy@rhiaro.co.uk> wrote:
> 
>> Hi all,
>>
>> As requested, we have a draft which is an update to RFC 6838, so that we
>> can discuss something concrete around multiple subtype suffixes:
>>
>>
>> https://datatracker.ietf.org/doc/draft-w3cdidwg-media-types-with-multiple-suffixes/
>>
>> Does anybody have a few moments to review this, so we can work on moving
>> this forward?
>>
>> Many thanks,
>>
>> Amy


From Graham.Klyne@oerc.ox.ac.uk  Thu Dec 24 05:41:15 2020
Return-Path: <Graham.Klyne@oerc.ox.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 2C6633A1251 for <media-types@ietfa.amsl.com>; Thu, 24 Dec 2020 05:41:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vYsg_eUt_lpR for <media-types@ietfa.amsl.com>; Thu, 24 Dec 2020 05:41:13 -0800 (PST)
Received: from relay17.mail.ox.ac.uk (relay17.mail.ox.ac.uk [129.67.1.165]) (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 569683A1250 for <media-types@ietf.org>; Thu, 24 Dec 2020 05:41:13 -0800 (PST)
Received: from smtp8.mail.ox.ac.uk ([163.1.2.204]) by relay17.mail.ox.ac.uk with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <Graham.Klyne@oerc.ox.ac.uk>) id 1ksQrf-0009ex-5U; Thu, 24 Dec 2020 13:41:11 +0000
Received: from gklyne38.plus.com ([81.174.129.24]:51455 helo=spare-94.atuin.ninebynine.org) by smtp8.mail.ox.ac.uk with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94) (envelope-from <Graham.Klyne@oerc.ox.ac.uk>) id 1ksQrf-0003WA-Qa; Thu, 24 Dec 2020 13:41:11 +0000
From: Graham Klyne <Graham.Klyne@oerc.ox.ac.uk>
To: rhiaro <amy@rhiaro.co.uk>, media-types@ietf.org
References: <e2ee2ce0-641f-de3e-b1b6-d375b24328ad@rhiaro.co.uk> <029ad5c8-b441-3a1e-997d-af1187bc8149@rhiaro.co.uk>
Organization: OeRC, Oxford University
Message-ID: <2271d528-9ec5-5173-cad7-ced15d44dd51@oerc.ox.ac.uk>
Date: Thu, 24 Dec 2020 13:41:08 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.5.1
MIME-Version: 1.0
In-Reply-To: <029ad5c8-b441-3a1e-997d-af1187bc8149@rhiaro.co.uk>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-GB
Content-Transfer-Encoding: 7bit
X-Oxford-Username: zool0635
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/oDnZ5Zu0QvqxQ3vvY2ZovDPu4L8>
Subject: Re: [media-types] Media subtypes containing "+"
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, 24 Dec 2020 14:42:44 -0000

[Re-sending:  I originally sent this response some time ago, but I'm not seeing 
it on the mailing list - I did respond to the prompt to confirm submission from 
a non-subscribed email address.]



Hi!

I think this is a useful contribution, thanks!

I have three comments:


1. In the discussion of suffix registrations, the draft says "each subset of 
suffixes, starting from the right-most suffix, MUST be individually registered 
as a subtype in its own right" - I think this is incorrect use of the term 
"subtype" as used by the MIME specification.  RFC6838 uses the phrase "media 
type name suffix" and/or "Structured Syntax Suffix Registration Template".

   https://www.rfc-editor.org/rfc/rfc6838.html#section-6

It's not clear to me what the best term would be, but I'd probably aim for 
something like "media type name suffix" or "subtype suffix" if that's clear from 
context.


2. I think an example would help to show what is being proposed (I think the 
description is clear enough, but it's always good to have something concrete to 
cross-check against).  In particular with reference to registration of multiple 
subtype suffixes used together.

E.g. in the case of refinements of application/ld+json (per 
https://w3c.github.io/json-ld-syntax/#iana-considerations), one could imagine 
more specific types defined; e.g.

     application/invoice+ld+json

Per the description, I think this would require the following suffixes have been 
registered:

     +json
     +ld+json

But not:

     +ld

And if this data may be offered with alternative RDF syntaxes, such as, e.g.:

     application/invoice+ld+rdf+xml

then:

     +xml
     +rdf+xml
     +ld+rdf+xml


3. A nit:  the draft makes reference to and uses RFC2119 language.  It is usual 
in RFC documents I've seen to explicitly call this out in the document.  E.g.

   https://www.rfc-editor.org/rfc/rfc6838.html#section-1.2


#g


On 30/11/2020 14:49, rhiaro wrote:
> Hi all,
> 
> As requested, we have a draft which is an update to RFC 6838, so that we
> can discuss something concrete around multiple subtype suffixes:
> 
> https://datatracker.ietf.org/doc/draft-w3cdidwg-media-types-with-multiple-suffixes/
> 
> Does anybody have a few moments to review this, so we can work on moving
> this forward?
> 
> Many thanks,
> 
> Amy
> 
> On 24.10.2020. 16:35, rhiaro wrote:
>> Hi all,
>>
>>> Is someone from the W3C willing to put such a draft together?
>> I'm a member of the W3C DID WG and have at long last drafted the update
>> to RFC6838 that has been discussed in this thread:
>>
>> https://datatracker.ietf.org/doc/draft-w3cdidwg-media-types-with-multiple-suffixes/
>>
>> I hope I have captured the intent of the comments so far in this thread
>> and used the correct language. Any and all feedback on refining this is
>> gratefully received.
>>
>> Amy
>>
>>
>> _______________________________________________
>> media-types mailing list
>> media-types@ietf.org
>> https://www.ietf.org/mailman/listinfo/media-types
>>
> 
> _______________________________________________
> media-types mailing list
> media-types@ietf.org
> https://www.ietf.org/mailman/listinfo/media-types
> 

-- 
Graham Klyne
mailto:graham.klyne@oerc.ox.ac.uk
Skype/Twitter: @gklyne


From nobody Fri Dec 25 08:17:12 2020
Return-Path: <eric@w3.org>
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 6EDBD3A13CF for <media-types@ietfa.amsl.com>; Fri, 25 Dec 2020 08:17:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r64LwRe6fbip for <media-types@ietfa.amsl.com>; Fri, 25 Dec 2020 08:17:09 -0800 (PST)
Received: from raoul.w3.org (raoul.w3.org [128.30.52.128]) (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 133EC3A13CE for <media-types@ietf.org>; Fri, 25 Dec 2020 08:17:08 -0800 (PST)
Received: from lfbn-cle-1-809-242.w92-171.abo.wanadoo.fr ([92.171.25.242] helo=w3.org) by raoul.w3.org with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <eric@w3.org>) id 1kspm6-0003TH-Uf; Fri, 25 Dec 2020 16:17:07 +0000
Date: Fri, 25 Dec 2020 17:17:03 +0100
From: Eric Prud'hommeaux <eric@w3.org>
To: Chris Lilley <chris@w3.org>
Cc: media-types@ietf.org
Message-ID: <20201225161703.GB34854@w3.org>
References: <CAL0qLwYbJXKzYEvYWH9ijXpH27eRqgZU78ThLd81cCecJ_E0Wg@mail.gmail.com> <544915d5-37a9-cc73-065c-bd1e694dfee2@w3.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <544915d5-37a9-cc73-065c-bd1e694dfee2@w3.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/_fAdLWswtsq7938IQqw5oMv4Yck>
Subject: Re: [media-types] Templates for basic MIME types
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: Fri, 25 Dec 2020 16:17:11 -0000

And I'll ask for sweeping changes that invalidate the billions of existing deployments...

Happy holidays, all!


On Thu, Dec 24, 2020 at 02:48:09AM +0200, Chris Lilley wrote:
> I'm happy to review any of the image media types.
> 
> On 2020-12-24 00:37, Murray S. Kucherawy wrote:
> > There are a number of media types registered by RFCs 2045 and 2046
> > implicitly (e.g., image/jpeg, image/gif).  The media type registry has
> > entries for them pointing at those two documents, but the documents
> > never actually present registration templates for any of them.
> > 
> > Just to make the record complete, I plan to send the reviewers a set of
> > registration templates for them.  I'll post them here as well in case
> > anyone wants to comment.
> > 
> > I presume we're fine with that approach, rather than requiring an RFC?
> > 
> > -MSK, ART AD
> > 
> > _______________________________________________
> > media-types mailing list
> > media-types@ietf.org
> > https://www.ietf.org/mailman/listinfo/media-types
> 
> -- 
> Chris Lilley
> @svgeesus
> Technical Director @ W3C
> W3C Strategy Team, Core Web Design
> W3C Architecture & Technology Team, Core Web & Media

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


From nobody Fri Dec 25 19:03:10 2020
Return-Path: <mnot@mnot.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 224083A05AA for <media-types@ietfa.amsl.com>; Fri, 25 Dec 2020 19:03:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level: 
X-Spam-Status: No, score=-2.101 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, RCVD_IN_MSPIKE_H2=-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=mnot.net header.b=IRtr8a0d; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=BmKdfNmg
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 NNFrQcbiCT76 for <media-types@ietfa.amsl.com>; Fri, 25 Dec 2020 19:03:07 -0800 (PST)
Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 584463A0544 for <media-types@ietf.org>; Fri, 25 Dec 2020 19:03:07 -0800 (PST)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.west.internal (Postfix) with ESMTP id 93C22641; Fri, 25 Dec 2020 22:03:04 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Fri, 25 Dec 2020 22:03:04 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm1; bh=G wrO0tv4VKCyQG8T3Oq3YIO+BnC6+QdpT1sppOF2hWQ=; b=IRtr8a0dawK9s/C5T KtxxOtMZdZMleDFpPP/k4A6l3MMi73aU/w+rMvj+qdnEHv3eBoHSW7bafuZBn+bH ms7c0BoFrvKxl3hPPT/xkOLk208OG4DA2KnGTU1rlc4otCTsVK5K0JGYeijzRwo3 9eN1mcoE/hc+IIIjNFUcmfMFJ0JGQf1B1+zV9wtm1UNnVCsh3Rq6qFsOoGOTszAN cPebimcqXHUMWa2ofhSkFbrOM0Cjo1xAzhryeNro9vzszfiWyPKN7Md3cODtBVZV Wk3v/J7Fte3pDT1/QXDlfnHN7tD/tVm61hpNe0gvKJo66WvyK2UsF3BIVR3YMOQX TyLHA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding: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=fm1; bh=GwrO0tv4VKCyQG8T3Oq3YIO+BnC6+QdpT1sppOF2h WQ=; b=BmKdfNmgBvCDCOAKjKkyvOw7p6mgNOcK22Rc0CKhrO3QxyT6kp0fqM6CA UMeK4wEL2/WUT721ecbFYzGhCpQhH9snPGOVeEpC67wlpN3WLC2tG4DlwPQj9Uz1 gKi+h9gBHBCPsuiDaPf6xE6XEdS+YOrhlyQWlSndjGvVCu657i7saBlLhi3gHtun Ap1QkWnbD6dI521IhIHDn5dJMk0GNPdCd+KDn1OrI5MiU3CLAa+QISzvEe9Ld8kZ uO07OqA3gW+yYqK9LcsUTUmi2E0kI+hN+gSSefTpodTbWuOxXitmSjGnuE0c7DZg y+qt1hycjat714OpwA13lvC3kKp5g==
X-ME-Sender: <xms:56fmX0WWURZcPFkqsrp-5AvODIU1I0_9661cJun7XyOyBalhq-E9kQ> <xme:56fmX4kVUXMpy96ZTPTjcCkenWumF10me0QJ-QdNVeSZYpRIgkjE2MAKRMiaWofbF _TYlZxNCklotcgm2g>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrvdduvddgheduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurheptggguffhjgffgffkfhfvofesthhqmhdthhdtvdenucfhrhhomhepofgrrhhk ucfpohhtthhinhhghhgrmhcuoehmnhhothesmhhnohhtrdhnvghtqeenucggtffrrghtth gvrhhnpeekuddvleejgeethfevkefhtdevkeelveekfeegleduiefhudegvdeiuefftddt hfenucffohhmrghinhepihgvthhfrdhorhhgpdhmnhhothdrnhgvthenucfkphepuddule drudejrdduheekrddvhedunecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehm rghilhhfrhhomhepmhhnohhtsehmnhhothdrnhgvth
X-ME-Proxy: <xmx:56fmX4aZi5LGoKhuQQtn7j2u0-ZVx0-3f8vNXmnxhowRUd43RsabpA> <xmx:56fmXzUuytGyGomMhB5lx72SoNowZV_iHL29GU8dgoVSQs-2dx6_vg> <xmx:56fmX-kOucOl_AK2uY31X-v-6gT94HA5TEIg_p-d7CzYj4-q31qw_g> <xmx:6KfmXwj7YJghi8sAvvA1T7BGYrT82dU8WF6Pw5tArJ0mFbRF8AdimQ>
Received: from [192.168.7.30] (119-17-158-251.77119e.mel.static.aussiebb.net [119.17.158.251]) by mail.messagingengine.com (Postfix) with ESMTPA id EC5C024005B; Fri, 25 Dec 2020 22:03:01 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.20.0.2.21\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <20201225161703.GB34854@w3.org>
Date: Sat, 26 Dec 2020 14:02:58 +1100
Cc: Chris Lilley <chris@w3.org>, media-types@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <E4131F62-74B2-4368-B41D-840C3CA5D77D@mnot.net>
References: <CAL0qLwYbJXKzYEvYWH9ijXpH27eRqgZU78ThLd81cCecJ_E0Wg@mail.gmail.com> <544915d5-37a9-cc73-065c-bd1e694dfee2@w3.org> <20201225161703.GB34854@w3.org>
To: Eric Prud'hommeaux <eric@w3.org>
X-Mailer: Apple Mail (2.3654.20.0.2.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/Jwt7bReHHPEHK3rCtI6oCXzcegY>
Subject: Re: [media-types] Templates for basic MIME types
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: Sat, 26 Dec 2020 03:03:09 -0000

My understanding has always been that the registration template is a =
transient artefact, and is not required to be published. Why is there a =
need for this?


> On 26 Dec 2020, at 3:17 am, Eric Prud'hommeaux <eric@w3.org> wrote:
>=20
> And I'll ask for sweeping changes that invalidate the billions of =
existing deployments...
>=20
> Happy holidays, all!
>=20
>=20
> On Thu, Dec 24, 2020 at 02:48:09AM +0200, Chris Lilley wrote:
>> I'm happy to review any of the image media types.
>>=20
>> On 2020-12-24 00:37, Murray S. Kucherawy wrote:
>>> There are a number of media types registered by RFCs 2045 and 2046
>>> implicitly (e.g., image/jpeg, image/gif).  The media type registry =
has
>>> entries for them pointing at those two documents, but the documents
>>> never actually present registration templates for any of them.
>>>=20
>>> Just to make the record complete, I plan to send the reviewers a set =
of
>>> registration templates for them.  I'll post them here as well in =
case
>>> anyone wants to comment.
>>>=20
>>> I presume we're fine with that approach, rather than requiring an =
RFC?
>>>=20
>>> -MSK, ART AD
>>>=20
>>> _______________________________________________
>>> media-types mailing list
>>> media-types@ietf.org
>>> https://www.ietf.org/mailman/listinfo/media-types
>>=20
>> --=20
>> Chris Lilley
>> @svgeesus
>> Technical Director @ W3C
>> W3C Strategy Team, Core Web Design
>> W3C Architecture & Technology Team, Core Web & Media
>=20
>> _______________________________________________
>> media-types mailing list
>> media-types@ietf.org
>> https://www.ietf.org/mailman/listinfo/media-types
>=20
> _______________________________________________
> media-types mailing list
> media-types@ietf.org
> https://www.ietf.org/mailman/listinfo/media-types

--
Mark Nottingham   https://www.mnot.net/


From nobody Sat Dec 26 00:00:17 2020
Return-Path: <ned.freed@mrochek.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 3CC173A0E92 for <media-types@ietfa.amsl.com>; Sat, 26 Dec 2020 00:00:15 -0800 (PST)
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, 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 (1024-bit key) header.d=mrochek.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 2JEGLfxXgdWL for <media-types@ietfa.amsl.com>; Sat, 26 Dec 2020 00:00:13 -0800 (PST)
Received: from plum.mrochek.com (plum.mrochek.com [172.95.64.195]) (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 BB22A3A0E93 for <media-types@ietf.org>; Sat, 26 Dec 2020 00:00:13 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01RTM0GBTAI800DC21@mauve.mrochek.com> for media-types@ietf.org; Fri, 25 Dec 2020 23:55:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mrochek.com; s=201712;  t=1608969309; bh=yuHOszVVxk77nYioNEwn7YzoDF0FCJPCXU/ulbPgukY=;  h=Cc:Date:From:Subject:In-reply-to:References:To:From; b=YDqrcwh78YFrr4T5xBtMF7uzo4nZTbzb624FMKgd7cNs7mMZ8N/8Wa5590+V6HwHv qV36a4SznFiBWrGj1YocRbBOm6t3c6ofS9fmLiqtHtDsMbOLPL6IOaEVA/vC0cKCtY FmE5k2/Vv3EhepDuuS02y4p+1oDkIXhgUls/4+pw=
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: TEXT/PLAIN; CHARSET=us-ascii
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01RTJOWYX49S004QVR@mauve.mrochek.com>; Fri, 25 Dec 2020 23:55:07 -0800 (PST)
Cc: Eric Prud'hommeaux <eric@w3.org>, media-types@ietf.org, Chris Lilley <chris@w3.org>
Message-id: <01RTM0GA5YFI004QVR@mauve.mrochek.com>
Date: Fri, 25 Dec 2020 23:24:13 -0800 (PST)
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Sat, 26 Dec 2020 14:02:58 +1100" <E4131F62-74B2-4368-B41D-840C3CA5D77D@mnot.net>
References: <CAL0qLwYbJXKzYEvYWH9ijXpH27eRqgZU78ThLd81cCecJ_E0Wg@mail.gmail.com> <544915d5-37a9-cc73-065c-bd1e694dfee2@w3.org> <20201225161703.GB34854@w3.org> <E4131F62-74B2-4368-B41D-840C3CA5D77D@mnot.net>
To: Mark Nottingham <mnot@mnot.net>
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/k2TgGiEkBqAggmyZvSN28j3CaLk>
Subject: Re: [media-types] Templates for basic MIME types
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: Sat, 26 Dec 2020 08:00:15 -0000

> My understanding has always been that the registration template is a
> transient artefact, and is not required to be published. Why is there a need
> for this?

Quite right - there is no need for this activity.

Registration templates are a handy tool for collecting and submtting the 
information necessary for a registration, nothing more.

The actual publication requirements for media types are laid out in section
4.10 of RFC 6848. Templates aren't mentioned in that section.

Sometimes templates end up getting published - the IETF does it routinely. Some
other standards bodies do so as well, others do not.

It's also the case that more information required to register now than
in the past. But increased information requirements do not apply retroactively
to previously registered media types. (It should be obvious why this is the
case.)

Of course nothing precludes engaging in this activity. But like Mark, I don't
see any actual need. And if you really want to spend time on media types, there
are plenty of entirely missing types that would benefit from being registered.

				Ned

> > On 26 Dec 2020, at 3:17 am, Eric Prud'hommeaux <eric@w3.org> wrote:
> >
> > And I'll ask for sweeping changes that invalidate the billions of existing deployments...
> >
> > Happy holidays, all!
> >
> >
> > On Thu, Dec 24, 2020 at 02:48:09AM +0200, Chris Lilley wrote:
> >> I'm happy to review any of the image media types.
> >>
> >> On 2020-12-24 00:37, Murray S. Kucherawy wrote:
> >>> There are a number of media types registered by RFCs 2045 and 2046
> >>> implicitly (e.g., image/jpeg, image/gif).  The media type registry has
> >>> entries for them pointing at those two documents, but the documents
> >>> never actually present registration templates for any of them.
> >>>
> >>> Just to make the record complete, I plan to send the reviewers a set of
> >>> registration templates for them.  I'll post them here as well in case
> >>> anyone wants to comment.
> >>>
> >>> I presume we're fine with that approach, rather than requiring an RFC?
> >>>
> >>> -MSK, ART AD
> >>>
> >>> _______________________________________________
> >>> media-types mailing list
> >>> media-types@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/media-types
> >>
> >> --
> >> Chris Lilley
> >> @svgeesus
> >> Technical Director @ W3C
> >> W3C Strategy Team, Core Web Design
> >> W3C Architecture & Technology Team, Core Web & Media
> >
> >> _______________________________________________
> >> media-types mailing list
> >> media-types@ietf.org
> >> https://www.ietf.org/mailman/listinfo/media-types
> >
> > _______________________________________________
> > media-types mailing list
> > media-types@ietf.org
> > https://www.ietf.org/mailman/listinfo/media-types

> --
> Mark Nottingham   https://www.mnot.net/

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


From nobody Sun Dec 27 08:36:44 2020
Return-Path: <msporny@digitalbazaar.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 4E14D3A0C26 for <media-types@ietfa.amsl.com>; Sun, 27 Dec 2020 08:36:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G3_YFtvMzYfG for <media-types@ietfa.amsl.com>; Sun, 27 Dec 2020 08:36:41 -0800 (PST)
Received: from mail.digitalbazaar.com (mail.digitalbazaar.com [96.89.14.193]) (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 4A4673A0657 for <media-types@ietf.org>; Sun, 27 Dec 2020 08:36:41 -0800 (PST)
Received: from [73.152.135.186] (helo=[10.4.10.95]) by mail.digitalbazaar.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.89) (envelope-from <msporny@digitalbazaar.com>) id 1ktZ4s-0001ry-Kd for media-types@ietf.org; Sun, 27 Dec 2020 11:39:33 -0500
To: media-types@ietf.org
References: <e2ee2ce0-641f-de3e-b1b6-d375b24328ad@rhiaro.co.uk> <029ad5c8-b441-3a1e-997d-af1187bc8149@rhiaro.co.uk> <CAL0qLwYAnCSi6XQ2u8d-Xpt0SezpAiVbhGyDorrDm3vN-Sk9FA@mail.gmail.com>
From: Manu Sporny <msporny@digitalbazaar.com>
Message-ID: <1091500a-3b2a-3ff7-587e-4a55990cef5e@digitalbazaar.com>
Date: Sun, 27 Dec 2020 11:36:36 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <CAL0qLwYAnCSi6XQ2u8d-Xpt0SezpAiVbhGyDorrDm3vN-Sk9FA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-GB
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 73.152.135.186
X-SA-Exim-Mail-From: msporny@digitalbazaar.com
X-SA-Exim-Version: 4.2.1 (built Tue, 02 Aug 2016 21:08:31 +0000)
X-SA-Exim-Scanned: Yes (on mail.digitalbazaar.com)
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/CdoZdUVL_RMTYICkiJ7dcis2D8k>
Subject: Re: [media-types] Media subtypes containing "+"
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, 27 Dec 2020 16:36:43 -0000

Hi Murray, Graham, and Martin,

I'm the lead editor of the Decentralized Identifier Core specification
in the W3C DID WG and have been working with Amy on the
media-types-with-multiple-suffixes document. The W3C DID WG specifically
needs it to be "done enough" for the JSON-LD serialization of DID
Documents. We plan to enter the Candidate Recommendation phase toward
the end of January and getting this document sorted is becoming a
priority. So any thoughts on whether we should stick with the direction
we're going in or have some sort of "backup plan" would be welcome.
Responses to statements below...

On 12/23/20 5:35 PM, Murray S. Kucherawy wrote:
> (1) In terms of handling, you might also propose this to art@ietf.org
> <mailto:art@ietf.org> (the general ART area mailing list) and to
> dispatch@ietf.org <mailto:dispatch@ietf.org> (the DISPATCH working
> group); the latter would be the place to get a discussion going about
> an appropriate venue for handling the document.

Hmm, by "handling" do you mean "further discussion"? We were under the
impression that the media-types group was the right forum for the
discussion. We're a bit lost as to how we'd publish this -- is that what
you're getting at?

> (2) I'm unclear on the nomenclature, in particular that the most 
> specific suffix is the first in the list of suffixes (when read left 
> to right) and the most generic is last.  My thought is that the list 
> needs to be ordered, and we just need to specify what that ordering 
> is.  For instance, I'm dreaming up a (possibly absurd) example of 
> "foo+zip+gzip".  Would I un-gzip it first, or unzip it first, with 
> the goal of getting a "foo" out of it?  Why would I consider one of 
> them more specific or generic than the other?

Our understanding was that the media-type string could contain multiple
subtypes and that there may be generic processing applications that
could determine if they could perform processing based on each generic
subtype.

For example, let's take the media type we're most concerned about right now:

application/did+ld+json

There are classes of processors that would be interested in each
subtype, for example:

json -- JSON linting software, JSON storage software that could store
        the document directly in an unstructured database, etc.

ld+json -- JSON-LD linting software, JSON-LD document processing
           software (expansion/compaction), JSON-LD to other RDF syntax
           processing software, etc.

did+ld+json -- Decentralized Identifier Document serialized as JSON-LD
               processing software such as DID resolution software,
               DID dereferencing software, Linked Data Signature
               processing software, etc.

So, the subtype(s) you're interested in depends on where you're
operating in the stack... there is definitely an answer to the "more
specific" / "more generic" question and the spec extension attempts to
point that out. I'm guessing that what you're saying is that "it needs
to do a better job at making that distinction"?

> If (based on the end of Section 1.1) what you're suggesting is 
> actually to in effect consider "+zip+gzip" a single unified suffix
> of its own, then I think what we're really saying here is that
> there's only ever one suffix, but that suffix can contain a "+".
> That is, when parsing the media subtype, the suffix is everything at
> and after the first "+" irrespective of how many "+" characters there
> are.  If that's the case, it might be simpler to just say it that way
> so that the reader doesn't need to think about a gradation of
> most-to-least specific.

Hmm, I don't think that's what we're trying to say. I think what we're
trying to say is the above, or to put it another way:

When there are multiple plus signs, there are multiple subtypes.
Subtypes that are registered have clear processing rules by pointing to
the specification that defines those processing rules.  So,
"application/did+ld+json" may be processed as "application/json",
"application/ld+json", and "application/did+ld+json"... and it's up to
the application to decide which subtype it would like to apply (all of
them are valid).

Does that make sense? Does anyone know of any media types where that
rationale breaks down? Or is that a nonsensical way to think about the
problem?

-- manu

-- 
Manu Sporny - https://www.linkedin.com/in/manusporny/
Founder/CEO - Digital Bazaar, Inc.
blog: Veres One Decentralized Identifier Blockchain Launches
https://tinyurl.com/veres-one-launches


From nobody Sun Dec 27 08:45:42 2020
Return-Path: <msporny@digitalbazaar.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 C70B53A0C2E for <media-types@ietfa.amsl.com>; Sun, 27 Dec 2020 08:45:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MOl6dViVSHXd for <media-types@ietfa.amsl.com>; Sun, 27 Dec 2020 08:45:39 -0800 (PST)
Received: from mail.digitalbazaar.com (mail.digitalbazaar.com [96.89.14.193]) (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 3BEF13A0C2A for <media-types@ietf.org>; Sun, 27 Dec 2020 08:45:38 -0800 (PST)
Received: from [73.152.135.186] (helo=[10.4.10.95]) by mail.digitalbazaar.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.89) (envelope-from <msporny@digitalbazaar.com>) id 1ktZDY-00024G-LV; Sun, 27 Dec 2020 11:48:30 -0500
To: =?UTF-8?Q?Martin_J=2e_D=c3=bcrst?= <duerst@it.aoyama.ac.jp>, "Murray S. Kucherawy" <superuser@gmail.com>, rhiaro <amy@rhiaro.co.uk>
Cc: media-types@ietf.org
References: <e2ee2ce0-641f-de3e-b1b6-d375b24328ad@rhiaro.co.uk> <029ad5c8-b441-3a1e-997d-af1187bc8149@rhiaro.co.uk> <CAL0qLwYAnCSi6XQ2u8d-Xpt0SezpAiVbhGyDorrDm3vN-Sk9FA@mail.gmail.com> <44a5b068-6843-b176-66ff-7926d598bb36@it.aoyama.ac.jp>
From: Manu Sporny <msporny@digitalbazaar.com>
Message-ID: <988ced9f-bfa1-5e66-2c81-07edcba541b4@digitalbazaar.com>
Date: Sun, 27 Dec 2020 11:45:33 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <44a5b068-6843-b176-66ff-7926d598bb36@it.aoyama.ac.jp>
Content-Type: text/plain; charset=utf-8
Content-Language: en-GB
Content-Transfer-Encoding: 8bit
X-SA-Exim-Connect-IP: 73.152.135.186
X-SA-Exim-Mail-From: msporny@digitalbazaar.com
X-SA-Exim-Version: 4.2.1 (built Tue, 02 Aug 2016 21:08:31 +0000)
X-SA-Exim-Scanned: Yes (on mail.digitalbazaar.com)
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/W3T6OlQzMrjTUr1Q_qLrSN0iUjc>
Subject: Re: [media-types] Media subtypes containing "+"
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, 27 Dec 2020 16:45:41 -0000

On 12/24/20 3:26 AM, Martin J. DÃ¼rst wrote:
> If I understand correctly, you would un-gzip it first, and only then 
> unzip it.

Yes... but remember you could have an application that's only really
interested in un-gzip'ing and stopping there. That's a perfectly
reasonable thing to do based on what ONE of the media subtypes is
telling you. If all you can do as an application is ungzip... well,
that's all you can do and the subtype makes that clear.

> In a slightly more realistic example, let's use svg+xml+gzip. Gzip is
> more generic (because it can be applied to any kind of data) than
> xml, and you definitely first have to un-gzip before feeding the 
> document into an XML parser.
> 
> But you may be right that there are cases where the terminology 
> 'generic'/'specific' may not be adequate. foo+gzip+zip (foo gzipped
> and then zipped) may make as much (or as little!) sense as
> foo+zip+gzip,

Yes, agreed that "specific" is not adequate, because there are multiple
"specific" identifiers that are valid, especially for the following use
case:

application/did+ld+json

These are all valid subtypes: "json", "ld+json", "did+ld+json" resulting
in these valid media type interpretations:

application/json
application/ld+json
application/did+ld+json

That's what we're trying to say... does that hold together?

> The problem with this approach may be that currently existing 
> implementations, as well as some future implementations, may just
> look at the rightmost + and the following alphabetic characters.
> Therefore, you need to make sure that people constructing/proposing
> suffix combinations will choose the right order, and that means that
> you have to have some language about suffix ordering anyway.

Ok, got it. Would adding language that explains the above (and the
previous response to Murray) make sense?

We expect that many applications don't do this sort of thing today,
rather either matching on the complete mime-type and doing processing,
or not. We are just trying to be complete about the mental model of
media subtypes and thought we were documenting something that was
already more or less there... but perhaps not? In any case, does adding
language about suffix ordering and how to interpret it address your
concern, Martin?

-- manu

-- 
Manu Sporny - https://www.linkedin.com/in/manusporny/
Founder/CEO - Digital Bazaar, Inc.
blog: Veres One Decentralized Identifier Blockchain Launches
https://tinyurl.com/veres-one-launches


From nobody Sun Dec 27 08:51:48 2020
Return-Path: <msporny@digitalbazaar.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 8B6493A0C57 for <media-types@ietfa.amsl.com>; Sun, 27 Dec 2020 08:51:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uw3J1HPgua0l for <media-types@ietfa.amsl.com>; Sun, 27 Dec 2020 08:51:45 -0800 (PST)
Received: from mail.digitalbazaar.com (mail.digitalbazaar.com [96.89.14.193]) (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 C6A8D3A0C40 for <media-types@ietf.org>; Sun, 27 Dec 2020 08:51:45 -0800 (PST)
Received: from [73.152.135.186] (helo=[10.4.10.95]) by mail.digitalbazaar.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.89) (envelope-from <msporny@digitalbazaar.com>) id 1ktZJT-0002At-Bq; Sun, 27 Dec 2020 11:54:38 -0500
To: Graham Klyne <Graham.Klyne@oerc.ox.ac.uk>, rhiaro <amy@rhiaro.co.uk>, media-types@ietf.org
References: <e2ee2ce0-641f-de3e-b1b6-d375b24328ad@rhiaro.co.uk> <029ad5c8-b441-3a1e-997d-af1187bc8149@rhiaro.co.uk> <2271d528-9ec5-5173-cad7-ced15d44dd51@oerc.ox.ac.uk>
From: Manu Sporny <msporny@digitalbazaar.com>
Message-ID: <6162e57e-184d-6715-b005-ee75122e8b94@digitalbazaar.com>
Date: Sun, 27 Dec 2020 11:51:40 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <2271d528-9ec5-5173-cad7-ced15d44dd51@oerc.ox.ac.uk>
Content-Type: text/plain; charset=utf-8
Content-Language: en-GB
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 73.152.135.186
X-SA-Exim-Mail-From: msporny@digitalbazaar.com
X-SA-Exim-Version: 4.2.1 (built Tue, 02 Aug 2016 21:08:31 +0000)
X-SA-Exim-Scanned: Yes (on mail.digitalbazaar.com)
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/Twhf5ni_UQdyol1FdUxVpst6Hsk>
Subject: Re: [media-types] Media subtypes containing "+"
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, 27 Dec 2020 16:51:48 -0000

On 12/24/20 8:41 AM, Graham Klyne wrote:
> 1. In the discussion of suffix registrations, the draft says "each 
> subset of suffixes, starting from the right-most suffix, MUST be 
> individually registered as a subtype in its own right" - I think this
> is incorrect use of the term "subtype" as used by the MIME
> specification. RFC6838 uses the phrase "media type name suffix"
> and/or "Structured Syntax Suffix Registration Template".
> 
> https://www.rfc-editor.org/rfc/rfc6838.html#section-6
> 
> It's not clear to me what the best term would be, but I'd probably
> aim for something like "media type name suffix" or "subtype suffix"
> if that's clear from context.

Ok, can do... we'll probably go with the more precise "media type name
suffix".

> 2. I think an example would help to show what is being proposed (I
> think the description is clear enough, but it's always good to have
> something concrete to cross-check against).

Yes, agreed, we'll add an example and use a real one as an example --
application/did+ld+json

> In particular with reference to registration of multiple subtype
> suffixes used together.
> 
> E.g. in the case of refinements of application/ld+json (per 
> https://w3c.github.io/json-ld-syntax/#iana-considerations), one
> could imagine more specific types defined; e.g.
> 
> application/invoice+ld+json
> 
> Per the description, I think this would require the following
> suffixes have been registered:
> 
> +json +ld+json
> 
> But not:
> 
> +ld

Yes, that is correct. We may want to put additional language in there
that states that you can only build valid media type names from a
structured suffix from right to left (not left to right).

> And if this data may be offered with alternative RDF syntaxes, such
> as, e.g.:
> 
> application/invoice+ld+rdf+xml
> 
> then:
> 
> +xml +rdf+xml +ld+rdf+xml

Yes, agreed.

> 3. A nit:  the draft makes reference to and uses RFC2119 language.
> It is usual in RFC documents I've seen to explicitly call this out in
> the document.  E.g.
> 
> https://www.rfc-editor.org/rfc/rfc6838.html#section-1.2

Ok, will do, thanks Graham!

-- manu

-- 
Manu Sporny - https://www.linkedin.com/in/manusporny/
Founder/CEO - Digital Bazaar, Inc.
blog: Veres One Decentralized Identifier Blockchain Launches
https://tinyurl.com/veres-one-launches


From nobody Mon Dec 28 03:25:29 2020
Return-Path: <eric@w3.org>
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 BA16D3A08A5 for <media-types@ietfa.amsl.com>; Mon, 28 Dec 2020 03:25:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TtT3gLs3Bc4P for <media-types@ietfa.amsl.com>; Mon, 28 Dec 2020 03:25:25 -0800 (PST)
Received: from raoul.w3.org (raoul.w3.org [128.30.52.128]) (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 65F8C3A0880 for <media-types@ietf.org>; Mon, 28 Dec 2020 03:25:24 -0800 (PST)
Received: from lfbn-cle-1-809-242.w92-171.abo.wanadoo.fr ([92.171.25.242] helo=w3.org) by raoul.w3.org with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <eric@w3.org>) id 1ktqeN-0002DB-CP; Mon, 28 Dec 2020 11:25:19 +0000
Date: Mon, 28 Dec 2020 12:25:15 +0100
From: Eric Prud'hommeaux <eric@w3.org>
To: Ned Freed <ned.freed@mrochek.com>
Cc: Mark Nottingham <mnot@mnot.net>, media-types@ietf.org, Chris Lilley <chris@w3.org>
Message-ID: <20201228112515.GD34854@w3.org>
References: <CAL0qLwYbJXKzYEvYWH9ijXpH27eRqgZU78ThLd81cCecJ_E0Wg@mail.gmail.com> <544915d5-37a9-cc73-065c-bd1e694dfee2@w3.org> <20201225161703.GB34854@w3.org> <E4131F62-74B2-4368-B41D-840C3CA5D77D@mnot.net> <01RTM0GA5YFI004QVR@mauve.mrochek.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <01RTM0GA5YFI004QVR@mauve.mrochek.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/FWaVoqeHnJ0Wspe9LEJWCsVaE0E>
Subject: Re: [media-types] Templates for basic MIME types
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, 28 Dec 2020 11:25:28 -0000

On Fri, Dec 25, 2020 at 11:24:13PM -0800, Ned Freed wrote:
> > My understanding has always been that the registration template is a
> > transient artefact, and is not required to be published. Why is there a need
> > for this?
> 
> Quite right - there is no need for this activity.
> 
> Registration templates are a handy tool for collecting and submtting the 
> information necessary for a registration, nothing more.

AFAICT, de facto media types include only the tree and the subtype
name, and references to specs ¹. Some of these specs may define some
parameters but the information isn't organized in a familiar way,
which means you have to dig way harder to find established consensus.

For instance, the two example media types, image/{jpeg,gif} are sort
of registered in RFC2046 but you can't look there to see if e.g.
image/jpeg can take an encoding parameter to switch between JFIF and
EXIF (after some annoying heuristics, it appears that it can't so
folks write EXIF + JFIF into JPEGs).

I read the proposal as offering to clarify that and all of the other
marvelous metadata (security, encoding, interop consideration and
fragment IDs) that has accumulated in the registration template over
the years ².

¹ https://www.iana.org/assignments/media-types/media-types.xhtml#image 
² https://www.iana.org/form/media-types


> The actual publication requirements for media types are laid out in section
> 4.10 of RFC 6848. Templates aren't mentioned in that section.
> 
> Sometimes templates end up getting published - the IETF does it routinely. Some
> other standards bodies do so as well, others do not.
> 
> It's also the case that more information required to register now than
> in the past. But increased information requirements do not apply retroactively
> to previously registered media types. (It should be obvious why this is the
> case.)

True, we can't change the deployment, but it still may be worth
documenting it.


> Of course nothing precludes engaging in this activity. But like Mark, I don't
> see any actual need. And if you really want to spend time on media types, there
> are plenty of entirely missing types that would benefit from being registered.

I can imagine you are speaking either of

1 formats for which there is a specification (e.g. W3C XML Schema) and
  no corresponding media type (i.e. I have to inspect an
  application/xml document to know if it's XML Schema)

2 commonly-used media types that don't show up in the registry (no
  examples come to mind)


> 				Ned
> 
> > > On 26 Dec 2020, at 3:17 am, Eric Prud'hommeaux <eric@w3.org> wrote:
> > >
> > > And I'll ask for sweeping changes that invalidate the billions of existing deployments...
> > >
> > > Happy holidays, all!
> > >
> > >
> > > On Thu, Dec 24, 2020 at 02:48:09AM +0200, Chris Lilley wrote:
> > >> I'm happy to review any of the image media types.
> > >>
> > >> On 2020-12-24 00:37, Murray S. Kucherawy wrote:
> > >>> There are a number of media types registered by RFCs 2045 and 2046
> > >>> implicitly (e.g., image/jpeg, image/gif).  The media type registry has
> > >>> entries for them pointing at those two documents, but the documents
> > >>> never actually present registration templates for any of them.
> > >>>
> > >>> Just to make the record complete, I plan to send the reviewers a set of
> > >>> registration templates for them.  I'll post them here as well in case
> > >>> anyone wants to comment.
> > >>>
> > >>> I presume we're fine with that approach, rather than requiring an RFC?
> > >>>
> > >>> -MSK, ART AD
> > >>>
> > >>> _______________________________________________
> > >>> media-types mailing list
> > >>> media-types@ietf.org
> > >>> https://www.ietf.org/mailman/listinfo/media-types
> > >>
> > >> --
> > >> Chris Lilley
> > >> @svgeesus
> > >> Technical Director @ W3C
> > >> W3C Strategy Team, Core Web Design
> > >> W3C Architecture & Technology Team, Core Web & Media
> > >
> > >> _______________________________________________
> > >> media-types mailing list
> > >> media-types@ietf.org
> > >> https://www.ietf.org/mailman/listinfo/media-types
> > >
> > > _______________________________________________
> > > media-types mailing list
> > > media-types@ietf.org
> > > https://www.ietf.org/mailman/listinfo/media-types
> 
> > --
> > Mark Nottingham   https://www.mnot.net/
> 
> > _______________________________________________
> > media-types mailing list
> > media-types@ietf.org
> > https://www.ietf.org/mailman/listinfo/media-types


From nobody Mon Dec 28 04:19:16 2020
Return-Path: <chris@w3.org>
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 F09723A0940 for <media-types@ietfa.amsl.com>; Mon, 28 Dec 2020 04:19:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BJPnzMZI4etX for <media-types@ietfa.amsl.com>; Mon, 28 Dec 2020 04:19:12 -0800 (PST)
Received: from raoul.w3.org (raoul.w3.org [128.30.52.128]) (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 663BD3A08BB for <media-types@ietf.org>; Mon, 28 Dec 2020 04:19:12 -0800 (PST)
Received: from 178-239-186.dynamic.cyta.gr ([178.59.239.186] helo=[192.168.2.105]) by raoul.w3.org with esmtpsa (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from <chris@w3.org>) id 1ktrUU-0003LG-Sd for media-types@ietf.org; Mon, 28 Dec 2020 12:19:11 +0000
Message-ID: <b333f3ba-dd77-2116-4435-5e66fe47dc8c@w3.org>
Date: Mon, 28 Dec 2020 14:19:08 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:85.0) Gecko/20100101 Thunderbird/85.0
Content-Language: en-US
References: <CAL0qLwYbJXKzYEvYWH9ijXpH27eRqgZU78ThLd81cCecJ_E0Wg@mail.gmail.com> <544915d5-37a9-cc73-065c-bd1e694dfee2@w3.org> <20201225161703.GB34854@w3.org> <E4131F62-74B2-4368-B41D-840C3CA5D77D@mnot.net> <01RTM0GA5YFI004QVR@mauve.mrochek.com> <20201228112515.GD34854@w3.org>
To: "media-types@ietf.org" <media-types@ietf.org>
From: Chris Lilley <chris@w3.org>
In-Reply-To: <20201228112515.GD34854@w3.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/5FhgH1wxqIEmyWsKwyu7vZI511A>
Subject: Re: [media-types] Templates for basic MIME types
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, 28 Dec 2020 12:19:15 -0000

Yes, that was my understanding too.

By modern standards, these original grandfathered types are way 
under-specified.

On 2020-12-28 13:25, Eric Prud'hommeaux wrote:
> I read the proposal as offering to clarify that and all of the other
> marvelous metadata (security, encoding, interop consideration and
> fragment IDs) that has accumulated in the registration template over
> the years Â².

-- 
Chris Lilley
@svgeesus
Technical Director @ W3C
W3C Strategy Team, Core Web Design
W3C Architecture & Technology Team, Core Web & Media


From nobody Mon Dec 28 06:00:35 2020
Return-Path: <ned.freed@mrochek.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 BE6EF3A0B38 for <media-types@ietfa.amsl.com>; Mon, 28 Dec 2020 06:00:34 -0800 (PST)
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, RCVD_IN_DNSWL_BLOCKED=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=mrochek.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 EDGbI9xh8wFn for <media-types@ietfa.amsl.com>; Mon, 28 Dec 2020 06:00:33 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [98.153.82.211]) (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 8E1AB3A0B2D for <media-types@ietf.org>; Mon, 28 Dec 2020 06:00:33 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01RTP5LPITXC007OWH@mauve.mrochek.com> for media-types@ietf.org; Mon, 28 Dec 2020 05:55:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mrochek.com; s=201712;  t=1609163726; bh=hWQlgdabHGyVJzdxIrJwQ6BVVYBfjfvshfkT16iSO5Q=;  h=Cc:Date:From:Subject:In-reply-to:References:To:From; b=RHIXY173Q9AoxtGPG6PHbtOU5Z8tnnUA+JqjhBnkApDDEHA1QiUjp0rSQe1EUNJ02 YVCPK1DvLwsBmi0/Tv74urBgQaubvEvfR+apa44/Zw5pCoSCpilMlV2T8PQyJD0UCw YOJMbADQ7W0T+Z8hd3ReEaMyTGPAJ3WYYxNyX4BU=
MIME-version: 1.0
Content-transfer-encoding: 8BIT
Content-type: TEXT/PLAIN; charset=utf-8; Format=flowed
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01RTJOWYX49S004QVR@mauve.mrochek.com>; Mon, 28 Dec 2020 05:55:21 -0800 (PST)
Cc: "media-types@ietf.org" <media-types@ietf.org>
Message-id: <01RTP5LMAMA0004QVR@mauve.mrochek.com>
Date: Mon, 28 Dec 2020 05:53:29 -0800 (PST)
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Mon, 28 Dec 2020 14:19:08 +0200" <b333f3ba-dd77-2116-4435-5e66fe47dc8c@w3.org>
References: <CAL0qLwYbJXKzYEvYWH9ijXpH27eRqgZU78ThLd81cCecJ_E0Wg@mail.gmail.com> <544915d5-37a9-cc73-065c-bd1e694dfee2@w3.org> <20201225161703.GB34854@w3.org> <E4131F62-74B2-4368-B41D-840C3CA5D77D@mnot.net> <01RTM0GA5YFI004QVR@mauve.mrochek.com> <20201228112515.GD34854@w3.org> <b333f3ba-dd77-2116-4435-5e66fe47dc8c@w3.org>
To: Chris Lilley <chris@w3.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/gFmPPw2x9BK82ByqeO4Rs3Pv1AM>
Subject: Re: [media-types] Templates for basic MIME types
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, 28 Dec 2020 14:00:35 -0000

> Yes, that was my understanding too.

> By modern standards, these original grandfathered types are way
> under-specified.

Is this causing an actual problem somewhere? Because if not, I would
think the time to update these registrations is when the MIME specifications
themselves are updated - something that's supposed to happen after work on the
core email specifications are complete.

This work is currently undderway in the emailcore WG. You're welcome to
join and participate.

				Ned

> On 2020-12-28 13:25, Eric Prud'hommeaux wrote:
> > I read the proposal as offering to clarify that and all of the other
> > marvelous metadata (security, encoding, interop consideration and
> > fragment IDs) that has accumulated in the registration template over
> > the years Â².

> --
> Chris Lilley
> @svgeesus
> Technical Director @ W3C
> W3C Strategy Team, Core Web Design
> W3C Architecture & Technology Team, Core Web & Media

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


From nobody Mon Dec 28 06:15:09 2020
Return-Path: <pere@hungry.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 E46C23A0B8F for <media-types@ietfa.amsl.com>; Mon, 28 Dec 2020 06:15:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vShmEE-tZVC4 for <media-types@ietfa.amsl.com>; Mon, 28 Dec 2020 06:15:06 -0800 (PST)
Received: from vuizook.err.no (vuizook.err.no [IPv6:2a02:20c8:2640::2]) (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 BAE1A3A0B89 for <media-types@ietf.org>; Mon, 28 Dec 2020 06:15:05 -0800 (PST)
Received: from cm-84.212.193.114.getinternet.no ([84.212.193.114] helo=hjemme.reinholdtsen.name) by vuizook.err.no with smtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <pere@hungry.com>) id 1kttIa-00052z-IR; Mon, 28 Dec 2020 14:15:02 +0000
Received: (nullmailer pid 6200 invoked by uid 10001); Mon, 28 Dec 2020 14:14:53 -0000
From: Petter Reinholdtsen <pere@hungry.com>
To: media-types@ietf.org
In-Reply-To: <20201228112515.GD34854@w3.org>
References: <CAL0qLwYbJXKzYEvYWH9ijXpH27eRqgZU78ThLd81cCecJ_E0Wg@mail.gmail.com> <544915d5-37a9-cc73-065c-bd1e694dfee2@w3.org> <20201225161703.GB34854@w3.org> <E4131F62-74B2-4368-B41D-840C3CA5D77D@mnot.net> <01RTM0GA5YFI004QVR@mauve.mrochek.com> <20201228112515.GD34854@w3.org>
Date: Mon, 28 Dec 2020 15:14:53 +0100
Message-ID: <sa6eejaow4i.fsf@hjemme.reinholdtsen.name>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/wD75mNJ_nk0Wg3uNpr5qXyA3XwY>
Subject: Re: [media-types] Templates for basic MIME types
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, 28 Dec 2020 14:15:09 -0000

[Eric Prud'hommeaux]
> I can imagine you are speaking either of
>
> 1 formats for which there is a specification (e.g. W3C XML Schema) and
>   no corresponding media type (i.e. I have to inspect an
>   application/xml document to know if it's XML Schema)
>
> 2 commonly-used media types that don't show up in the registry (no
>   examples come to mind)

One example of the latter is patch types, which I tried to get
registered, but gave up based on the lack of feedback here. :)

There are also heaps of unregistered multimedia related MIME types, as
can be seen from
<URL: https://wiki.debian.org/DebianMultimedia/PlayerSupport >.

-- 
Happy hacking
Petter Reinholdtsen


From nobody Mon Dec 28 07:54:03 2020
Return-Path: <amy@rhiaro.co.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 236083A0C43 for <media-types@ietfa.amsl.com>; Mon, 28 Dec 2020 07:54:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level: 
X-Spam-Status: No, score=-2.101 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, NICE_REPLY_A=-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 (1024-bit key) header.d=rhiaro.co.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 os5bOLxYttVX for <media-types@ietfa.amsl.com>; Mon, 28 Dec 2020 07:53:59 -0800 (PST)
Received: from dragonfly.birch.relay.mailchannels.net (dragonfly.birch.relay.mailchannels.net [23.83.209.51]) (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 B44453A0C29 for <media-types@ietf.org>; Mon, 28 Dec 2020 07:53:58 -0800 (PST)
X-Sender-Id: dreamhost|x-authsender|amy@rhiaro.co.uk
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 3C6BF401C65 for <media-types@ietf.org>; Mon, 28 Dec 2020 15:53:56 +0000 (UTC)
Received: from pdx1-sub0-mail-a64.g.dreamhost.com (100-96-5-83.trex.outbound.svc.cluster.local [100.96.5.83]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id 4EAF9401DA6 for <media-types@ietf.org>; Mon, 28 Dec 2020 15:53:54 +0000 (UTC)
X-Sender-Id: dreamhost|x-authsender|amy@rhiaro.co.uk
Received: from pdx1-sub0-mail-a64.g.dreamhost.com (pop.dreamhost.com [64.90.62.162]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.18.11); Mon, 28 Dec 2020 15:53:56 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: dreamhost|x-authsender|amy@rhiaro.co.uk
X-MailChannels-Auth-Id: dreamhost
X-Inform-Eight: 25247e8205e81877_1609170835443_339739719
X-MC-Loop-Signature: 1609170835443:3144970854
X-MC-Ingress-Time: 1609170835443
Received: from pdx1-sub0-mail-a64.g.dreamhost.com (localhost [127.0.0.1]) by pdx1-sub0-mail-a64.g.dreamhost.com (Postfix) with ESMTP id 044A686267 for <media-types@ietf.org>; Mon, 28 Dec 2020 07:53:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=rhiaro.co.uk; h=subject:to :references:from:message-id:date:mime-version:in-reply-to :content-type:content-transfer-encoding; s=rhiaro.co.uk; bh=Pbu+ i/jB7aM/uJgnGthvg4r6iVE=; b=i51naMWoDabC5nqYhyAG6Rf1AWUf50THdCDd 92BLI08Wzix5ptI1fYJWs6e5S6sE/Q+Pnq2am7mKm6jnsQHV0yP299S7uLHnm3lL NKEgf1kjciGaBBFivCspze84IkW50vgyXETrcxHoQu+e3bQ4mFuZRpICsmrLVZHt MEez8tY=
Received: from [192.168.8.100] (94.196.84.231.threembb.co.uk [94.196.84.231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: amy@rhiaro.co.uk) by pdx1-sub0-mail-a64.g.dreamhost.com (Postfix) with ESMTPSA id 4F58B8039F for <media-types@ietf.org>; Mon, 28 Dec 2020 07:53:52 -0800 (PST)
To: media-types@ietf.org
References: <e2ee2ce0-641f-de3e-b1b6-d375b24328ad@rhiaro.co.uk> <029ad5c8-b441-3a1e-997d-af1187bc8149@rhiaro.co.uk> <2271d528-9ec5-5173-cad7-ced15d44dd51@oerc.ox.ac.uk> <6162e57e-184d-6715-b005-ee75122e8b94@digitalbazaar.com>
X-DH-BACKEND: pdx1-sub0-mail-a64
From: rhiaro <amy@rhiaro.co.uk>
Autocrypt: addr=amy@rhiaro.co.uk; prefer-encrypt=mutual; keydata= xsFNBFk/2SQBEADQQ2a5b0PuZGALNdVKKKsZckwDq+4nRLrh8RLCWnI4+ffwzCOvKGMmbXpK ynNFDlnYmUI1be323wcTRv87ygaziuZ6Lh3KuiAazxR0pmnTi8F5IIJBKb35InvJV+zP6Mvg BXi/kI30eBssrBjX+tGR3cOE8i0b9i0asZ/1NdFjVqGEiL23qRZ6fsMm1epClVDaUh7oJmGK GqLgUEUe3HQ6/Y7FzXI9kxM0zX4xgdu3cV0Nu7kT3jNpCQ+gXIz5nfVo26oLwhjiWeDYpfSv L4EjGF7Q4ozjWIWJKmiBj89xCZECwjEWUCrfGUvS6l1TuBeyVMfiTHPwgk5yN+SxcZe0HKpR O/fzZvDNTlD0pQBHSWY1HZh2BeZIdg7/eCZrrQvALI2G/up0mN2o0i0DmK2Mly9mKd5SCSSP 8yCq8o5Ls8bKIN93B0bIK4wZaNhRucrtBuVfvJjUMCOoLKyfJWOeym31ORHZPPm+u1+7gs43 BB7Bil9jf4mED8ZcR4KDLyZZUzI+VwB4szeDq+XSVRu55w37i3ecd9Bt81MfDuV7AzOeG6fh 0UbULhUb1Wfwx4Hnhfhr/pxoXXMfAYFPxCag/TMBg062NDoWoYgrOWOOMuPZdX7rMJlF/y3V oMibwikWpmr76ekLXb3MnAx2PPIothZ4f1EFGkCFnswgAOAOjQARAQABzRlyaGlhcm8gPGFt eUByaGlhcm8uY28udWs+wsF9BBMBCAAnBQJZP9kkAhsjBQkJZgGABQsJCAcCBhUICQoLAgQW AgMBAh4BAheAAAoJEMU2cbsmXJvI2lUQAK+Q8j5BbpAJ+wATJpWqOfEHILz59jmgg374Ghnb bsznOaVh9a2xSleEdbJOPfH4Ig2mYGpbfRXGqYNCAVyEeFRGt1X+EtCGkdZVEsJbfzYv+YvO 62yh3XIEyL1nJ3hlsrX05jEu6H8poujxixwgnqLh+ixwdOKlj9JVRGgNrwEVhePH8t0qdBeS 5K8pV1upLTcbWd2ORTJgagLtce+XiKzMbJBq48inKVsSuCwj1QZIZuoDc4JYObkTGSOr/Naw Di3V3cZQP0wAQ45vydDLX1v7xb7C+J+86J5KADu5uSKMiz7nQ5HGDsPy4KUiXkJwKHoMWJqX 8kW+wTYqnevMyNc2VuZWtJl22RalwgZGNt0OlbXyXRTFVTrLl1dz9zbWR7dc6woNdAm4ItKy 9XbAsqR5zvexoryQMpdJjLaDJOh57mkZPAcgp22X1K0q4HDA61xdoQ66SUhwNCQ7YdefMyIc XbZQuUdYfRGYA2AgX6aaikhPHWScgAhOsrxl1F/EuT88tcoZJhWi/tE2WIeuA8MuEr2pfr7b d/1bfA2NJKCHu0PbaCG6MXUw//GX+DeJ1Lf1DPVEL0Vm+gAnJvA4tTvXFM7B0AYYbHiPMgWM EsUEg9ctyPqE9v6IwHRwCJ4pTohEF5DVSoF/SHQ/mRRYadsXHRREtwQvd+8ceLfZaPWRzsFN BFk/2SQBEACtFbXD85Yp8KC1hwR9p11HOa1w3ne5MkZhput5vZFexs9zaPqSExJli2ZD56eT EqV8oG/gX3yEE8uwBge7z/dZfnIMh+xV9RBQahSo1HIfWCuh+D1aseceDZhDVwEX1/9tVA3M RW29nN73HdOrT3Q6/dQMJpHDSEkA9fla3S6O51rPH8uXZ0bsvCZGvKFoDb24Bd/TeGoLmz7t KM+xrev6mIZeuvtkQe4Glsnnymm/FJjrCUvBeGcCWGUWDZs+y7DFL6/vR0LY8xVwi8wviHio wPm48QieY5D6WEG+Xh0xFV/2cwxiz15KTEkzP88QDY86q9R5b78wPYOByyo76aiCfzk+yEle pw5TxEHwyw0KPl5S/2niXaQycv672l0aeyMtpmOuF2uHWz6gIwvLPH90gxQ9nS0R0TIpI/14 ldnOahObTcteBYwKaomKkxFahmUxxR7BZp59y7YwT29VJxpp/XqzxhUS2CjwEXln8ZNiZ1/5 dCl26DxuTr8vTIJlAt1/FyuO3ofCdn5x3c2pf6b+0Z+QrK/adZoIRVAI2koeq0fz/w8XV+5b TbzAYGYB0gNgmqYJ+C7vJSnDSqoZuTFfuvQbs6SlByqekFKQtBuu0r5h0j8xbEkBIbdgIl7i RxVk/91huTGspCgONhw9TxQd0rVdnvvHJcIHATLMiQEllQARAQABwsFlBBgBCAAPBQJZP9kk AhsMBQkJZgGAAAoJEMU2cbsmXJvI8M4P/jy3ixkWklWij8L7NPjpdM12qm0eHPcf0+a5yKXv 6sXUbOK/fiAUK4jrSOGclKVuGjd8XTbBTLGHp01rD4M26gJd2aqAmQtZ+OLST8lYdSU3Zgev nzt1G4hIRFlCXRXXdgGNW9Ls84nQOJgAYfwjZ4aS4WQDfbsl8DOm1MgjWxZXi3cBX6sRHmhE lcyQ4Dz7irEPBik3kIZDJIden/ags31ljM4vlM9+1sQoUJVmhg9dNnITE1yMOIOcrBflsGoa Or/8cgXsVhncLNDvlDBhkHp4LlnK6s1erVVBbs5GMQ6udly81Ov2UjIwLPewhk6MUDYfg9T9 QIIzbPBq8zr/8WC/z49p5SZkMlFFXMXi7mNhIzznlIHclQ2/TvxHeLRGbDlemWau6yhoViMb 2s1ucpEoNwhG/wylsS+g8wMGi1Zg7jKfYX0qqnF0qQqql6b60SLV83rITJfQmIMVX5rqjj5S bq4sLherSivVZA85gLPWeWOfBZuqNuOWr2ExyJ4tHvXCrfFa3m8kj2MVnkIMZ2/Cf58gnesc af+jkG0pZSZ1nDWoJjPUUWH1cXb3xdbo/ELCQDFwrRV2blUYY295vUd1iDKXC53mTiHBMeIz XyBwjSKRdLI9GhU7RrULQgrovwY1pXHk8Qm3cF4nWZtpgmkoAceK/fp9IahbMlRGRywQ
Message-ID: <edf7baaf-b25b-7804-02e3-aaaadaea3f08@rhiaro.co.uk>
Date: Mon, 28 Dec 2020 15:53:49 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <6162e57e-184d-6715-b005-ee75122e8b94@digitalbazaar.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/IUf0FSDcc2Ud162g0wzNTYep6C4>
Subject: Re: [media-types] Media subtypes containing "+"
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, 28 Dec 2020 15:54:02 -0000

Hi all,

Thank you all for the feedback so far. I've made some edits based on the
suggestions to try to clarify things.

Still waiting for the upload confirmation email from the ietf tracker
for the new version, but meanwhile the draft is at:
https://rhiaro.github.io/draft-w3cdidwg-media-types-with-multiple-suffixe=
s/

Amy

On 27.12.2020. 16:51, Manu Sporny wrote:
> On 12/24/20 8:41 AM, Graham Klyne wrote:
>> 1. In the discussion of suffix registrations, the draft says "each=20
>> subset of suffixes, starting from the right-most suffix, MUST be=20
>> individually registered as a subtype in its own right" - I think this
>> is incorrect use of the term "subtype" as used by the MIME
>> specification. RFC6838 uses the phrase "media type name suffix"
>> and/or "Structured Syntax Suffix Registration Template".
>>
>> https://www.rfc-editor.org/rfc/rfc6838.html#section-6
>>
>> It's not clear to me what the best term would be, but I'd probably
>> aim for something like "media type name suffix" or "subtype suffix"
>> if that's clear from context.
> Ok, can do... we'll probably go with the more precise "media type name
> suffix".
>
>> 2. I think an example would help to show what is being proposed (I
>> think the description is clear enough, but it's always good to have
>> something concrete to cross-check against).
> Yes, agreed, we'll add an example and use a real one as an example --
> application/did+ld+json
>
>> In particular with reference to registration of multiple subtype
>> suffixes used together.
>>
>> E.g. in the case of refinements of application/ld+json (per=20
>> https://w3c.github.io/json-ld-syntax/#iana-considerations), one
>> could imagine more specific types defined; e.g.
>>
>> application/invoice+ld+json
>>
>> Per the description, I think this would require the following
>> suffixes have been registered:
>>
>> +json +ld+json
>>
>> But not:
>>
>> +ld
> Yes, that is correct. We may want to put additional language in there
> that states that you can only build valid media type names from a
> structured suffix from right to left (not left to right).
>
>> And if this data may be offered with alternative RDF syntaxes, such
>> as, e.g.:
>>
>> application/invoice+ld+rdf+xml
>>
>> then:
>>
>> +xml +rdf+xml +ld+rdf+xml
> Yes, agreed.
>
>> 3. A nit:  the draft makes reference to and uses RFC2119 language.
>> It is usual in RFC documents I've seen to explicitly call this out in
>> the document.  E.g.
>>
>> https://www.rfc-editor.org/rfc/rfc6838.html#section-1.2
> Ok, will do, thanks Graham!
>
> -- manu
>

