Re: [media-types] Mime type for patch files?

Eric Prud'hommeaux <eric@w3.org> Wed, 31 October 2018 10:27 UTC

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 A2C6812D4E7 for <media-types@ietfa.amsl.com>; Wed, 31 Oct 2018 03:27:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 B-4yBT-Oegju for <media-types@ietfa.amsl.com>; Wed, 31 Oct 2018 03:27:02 -0700 (PDT)
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 CE888128A6E for <media-types@ietf.org>; Wed, 31 Oct 2018 03:27:01 -0700 (PDT)
Received: from amarseille-651-1-76-143.w109-208.abo.wanadoo.fr ([109.208.171.143] helo=w3.org) by raoul.w3.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from <eric@w3.org>) id 1gHniE-0003vS-EB; Wed, 31 Oct 2018 10:26:58 +0000
Date: Wed, 31 Oct 2018 06:26:56 -0400
From: Eric Prud'hommeaux <eric@w3.org>
To: Petter Reinholdtsen <pere@hungry.com>
Cc: media-types@ietf.org
Message-ID: <20181031102655.GI17721@w3.org>
References: <sa67ehyzo3s.fsf@meta.reinholdtsen.name>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <sa67ehyzo3s.fsf@meta.reinholdtsen.name>
Organization: World Wide Web Consortium (W3C) - http://www.w3.org/
User-Agent: Mutt/1.9.4 (2018-02-28)
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/CpujIkX2_vRY4ti154F0PJuVOLQ>
Subject: Re: [media-types] Mime type for patch files?
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, 31 Oct 2018 10:27:05 -0000

* Petter Reinholdtsen <pere@hungry.com> [2018-10-31 06:23+0100]
> 
> Hi,
> 
> I am new to this list, and hope I do not misunderstand its purpose.  I
> would like to suggest a "new" mime type, and hope for your input on the
> topic.
> 
> While testing a archive system on a subset of mails from the Debian
> archive, I noticed the following unregistered MIME types on the top ten
> list of MIME types used in the emails: text/x-patch and text/x-diff.
> 
> The fact that emailing patches as attachments is so popular make me
> suspect it is time to register a MIME type for it.  But what type should
> the suggested?  One of the above, or a new one without the x- prefix?

I think this negotiation must happen with the tool maintainers which
currently recognize text/x-{patch,diff}. Given that that's probably
impossible, the answer is almost certainly that you are stuck with
"x-". Thanks for picking this up.

I tried to answer your question but ended up puzzled by this text in
[RFC6838]:
[[
   Note that types with names beginning with "x-" are no longer
   considered to be members of this tree (see [RFC6648]).  Also note
   that if a generally useful and widely deployed type incorrectly ends
   up with an "x-" name prefix, it MAY be registered using its current
   name in an alternative tree by following the procedure defined in
   Appendix A.
]]

The only "x-" subtree in [IMT] is "x-www-form-urlencoded", and maybe
it's an exception. The tricky question is whether x-{diff,patch}
deserve the same exception. On one hand, we don't want a slippery
slope of exceptions, on the other hand, the tree's job is to document
current or achievable reality.


[RFC6838] https://tools.ietf.org/html/rfc6838#section-3.4
[IMT] https://www.iana.org/assignments/media-types/media-types.xhtml#application

-- 
-x-ericP

office: +1.617.599.3509
mobile: +33.6.80.80.35.59

(eric@w3.org)
Feel free to forward this message to any list for any purpose other than
email address distribution.

There are subtle nuances encoded in font variation and clever layout
which can only be seen by printing this message on high-clay paper.