From nobody Tue Oct 16 08:07:05 2018 Return-Path: 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 56D5F12D4EE for ; Tue, 16 Oct 2018 08:07:04 -0700 (PDT) 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, RCVD_IN_DNSWL_NONE=-0.0001, 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 wZk9akRrwgxR for ; Tue, 16 Oct 2018 08:07:01 -0700 (PDT) Received: from 4.mo68.mail-out.ovh.net (4.mo68.mail-out.ovh.net [46.105.59.63]) (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 BFDD6130DC5 for ; Tue, 16 Oct 2018 08:07:00 -0700 (PDT) Received: from player694.ha.ovh.net (unknown [10.109.160.54]) by mo68.mail-out.ovh.net (Postfix) with ESMTP id 7244B100ABE for ; Tue, 16 Oct 2018 17:06:58 +0200 (CEST) Received: from [172.18.196.70] (unknown [46.183.103.8]) (Authenticated sender: paul@hoplahup.net) by player694.ha.ovh.net (Postfix) with ESMTPSA id 564E32C00D0; Tue, 16 Oct 2018 17:06:51 +0200 (CEST) From: "Paul Libbrecht" To: "Ned Freed" Cc: media-types@ietf.org, "Chris Lilley" Date: Tue, 16 Oct 2018 17:04:32 +0200 X-Mailer: MailMate (1.12r5523) Message-ID: In-Reply-To: <44F6AEF0-8A25-4981-8620-293FD5907483@hoplahup.net> References: <01Q88GLSKJC4011H9Q@mauve.mrochek.com> <44F6AEF0-8A25-4981-8620-293FD5907483@hoplahup.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Ovh-Tracer-Id: 18343724233889548513 X-VR-SPAMSTATE: OK X-VR-SPAMSCORE: -100 X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgedtkedrfedtgdekgecutefuodetggdotefrodftvfcurfhrohhfihhlvgemucfqggfjpdevjffgvefmvefgnecuuegrihhlohhuthemucehtddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd Archived-At: Subject: Re: [media-types] updates to RFC6838 in the horizon? 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Oct 2018 15:07:04 -0000 Dear all, this topic seems to have gone asleep since a while. Can anyone provide me information on the process of suggesting changes to the RFC 6838 (Media Type Specifications and Registration Procedures)? thanks in advance. Paul On 8 Dec 2016, at 23:17, Paul Libbrecht wrote: > This goes along the proposal I had to add UTI and Windows clipboard > flavour names within the template. I remember having been too late > "last time". > […] > Ned, how is the process to file such a change fo the template? > >>> 2) Is there value in adding the Apple UTI (which is at least >>> documented, and in current use) to the registration templates? >> >> Not that I'm aware of, but more information can't hurt. >>> My reason for asking is draft-ietf-justfont-toplevel >>> https://datatracker.ietf.org/doc/draft-ietf-justfont-toplevel/ >> >>> which will define a new top-level Media Type for fonts. I am very >>> tempted to just remove the "Macintosh file type code" from the >>> registration template, and could go either way on replacing it with >>> an "Apple Uniform Type Identifier" >>> field - opinions welcome. >> >> Either way works. From nobody Thu Oct 18 11:03:04 2018 Return-Path: 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 6734D130E04 for ; Thu, 18 Oct 2018 11:02:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.001 X-Spam-Level: X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isode.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 aQenIHSPd-_Q for ; Thu, 18 Oct 2018 11:02:52 -0700 (PDT) Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id 76787130DEB for ; Thu, 18 Oct 2018 11:02:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1539885771; d=isode.com; s=june2016; i=@isode.com; bh=4l9qaN2oCUBJtagp9NNH8XCj82o+bJFiEuzLZHyo20M=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=TxUGAsbdvl8LbWpbbr/6EDUPFf4dhk+Ec1j9rW5fBpukMo7sBvsUXN0xoJvcdzK4awflir Av14zdAPfCEJfi7uV1GVQhNlfHG+bK7wDBbN5RarRjpfOtg03Yxx4dZ4waY7Iu5Wb1BUK4 182WJN5bxy4z8MgyKbD8dkZ1mWFvZOw=; Received: from [192.168.0.7] (cpc121086-nmal24-2-0-cust54.19-2.cable.virginm.net [77.97.145.55]) by statler.isode.com (submission channel) via TCP with ESMTPSA id ; Thu, 18 Oct 2018 19:02:51 +0100 To: Paul Libbrecht Cc: Ned Freed , media-types@ietf.org, Chris Lilley References: <01Q88GLSKJC4011H9Q@mauve.mrochek.com> <44F6AEF0-8A25-4981-8620-293FD5907483@hoplahup.net> From: Alexey Melnikov Openpgp: preference=signencrypt Message-ID: Date: Thu, 18 Oct 2018 19:02:52 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-transfer-encoding: quoted-printable Archived-At: Subject: Re: [media-types] updates to RFC6838 in the horizon? 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Oct 2018 18:03:04 -0000 Hi Paul, On 16/10/2018 16:04, Paul Libbrecht wrote: > Dear all, >=20 > this topic seems to have gone asleep since a while. >=20 > Can anyone provide me information on the process of suggesting changes > to the RFC 6838 (Media Type Specifications and Registration Procedures)? Post a new draft with the new template(*)? I can't promise that there would be enough energy to get the update done, but seeing something concrete would certainly help. (*) - if you never done this, contact me off-list. Thank you, Alexey > thanks in advance. >=20 > Paul >=20 > On 8 Dec 2016, at 23:17, Paul Libbrecht wrote: >=20 >> This goes along the proposal I had to add UTI and Windows clipboard >> flavour names within the template. I remember having been too late >> "last time". >> [=E2=80=A6] >> Ned, how is the process to file such a change fo the template? >> >>>> 2) Is there value in adding the Apple UTI (which is at least >>>> documented, and in current use) to the registration templates? >>> >>> Not that I'm aware of, but more information can't hurt. >>>> My reason for asking is draft-ietf-justfont-toplevel >>>> https://datatracker.ietf.org/doc/draft-ietf-justfont-toplevel/ >>> >>>> which will define a new top-level Media Type for fonts. I am very >>>> tempted to just remove the "Macintosh file type code" from the >>>> registration template, and could go either way on replacing it with >>>> an "Apple Uniform Type Identifier" >>>> field - opinions welcome. >>> >>> Either way works. >=20 > _______________________________________________ > media-types mailing list > media-types@ietf.org > https://www.ietf.org/mailman/listinfo/media-types From nobody Thu Oct 18 15:46:37 2018 Return-Path: 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 13495130E00 for ; Thu, 18 Oct 2018 15:46:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.208 X-Spam-Level: X-Spam-Status: No, score=-1.208 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RDNS_NONE=0.793, SPF_PASS=-0.001] autolearn=no 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 QTZQk965YobL for ; Thu, 18 Oct 2018 15:46:34 -0700 (PDT) Received: from mauve.mrochek.com (unknown [66.159.242.17]) (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 684D6130DFF for ; Thu, 18 Oct 2018 15:46:34 -0700 (PDT) Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01QYLCDAFJ8000EOXZ@mauve.mrochek.com> for media-types@ietf.org; Thu, 18 Oct 2018 15:41:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=201712; t=1539902490; bh=Ud8Nz3RJpyn6xaClEjVc8r2t36sPv63CDgg85i0HK+k=; h=Cc:Date:From:Subject:In-reply-to:References:To:From; b=V0GV3pnYmnWHlBBfzInXRPgVWTQWSaA7o3foXuAZfCXcv9xtqh/pTUX14VG4DLBjN mtk+MO6M7KTOLKKIp/IrNJDcse894NXdhmWJAMCP5J6I2nRhlVkqjwFO8F/Omtwc4C 0+/nWUy2Hog0F9/0fWEY3TU+SqiNV0QTN10rwxNY= MIME-version: 1.0 Content-transfer-encoding: 8BIT Content-type: TEXT/PLAIN; charset=utf-8 Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01QYKRSFKKQO00BGSX@mauve.mrochek.com>; Thu, 18 Oct 2018 15:41:23 -0700 (PDT) Cc: Paul Libbrecht , Ned Freed , media-types@ietf.org, Chris Lilley Message-id: <01QYLCD6GWBE00BGSX@mauve.mrochek.com> Date: Thu, 18 Oct 2018 15:38:46 -0700 (PDT) From: Ned Freed In-reply-to: "Your message dated Thu, 18 Oct 2018 19:02:52 +0100" References: <01Q88GLSKJC4011H9Q@mauve.mrochek.com> <44F6AEF0-8A25-4981-8620-293FD5907483@hoplahup.net> To: Alexey Melnikov Archived-At: Subject: Re: [media-types] updates to RFC6838 in the horizon? 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Oct 2018 22:46:36 -0000 I don't see a problem with a draft updating the template. Pretty low cost thing to do. OTOH, nothing prevents a registration from including "additional" additional information, nor is a registration precluded from omitting any or all of the additional information fields. So the value of formally adding the fields would be if it gets people to list them when they wouldn't otherwise. Given past experience I'm skeptical this will happen. Ned > Hi Paul, > On 16/10/2018 16:04, Paul Libbrecht wrote: > > Dear all, > > > > this topic seems to have gone asleep since a while. > > > > Can anyone provide me information on the process of suggesting changes > > to the RFC 6838 (Media Type Specifications and Registration Procedures)? > Post a new draft with the new template(*)? I can't promise that there > would be enough energy to get the update done, but seeing something > concrete would certainly help. > (*) - if you never done this, contact me off-list. > Thank you, > Alexey > > thanks in advance. > > > > Paul > > > > On 8 Dec 2016, at 23:17, Paul Libbrecht wrote: > > > >> This goes along the proposal I had to add UTI and Windows clipboard > >> flavour names within the template. I remember having been too late > >> "last time". > >> […] > >> Ned, how is the process to file such a change fo the template? > >> > >>>> 2) Is there value in adding the Apple UTI (which is at least > >>>> documented, and in current use) to the registration templates? > >>> > >>> Not that I'm aware of, but more information can't hurt. > >>>> My reason for asking is draft-ietf-justfont-toplevel > >>>> https://datatracker.ietf.org/doc/draft-ietf-justfont-toplevel/ > >>> > >>>> which will define a new top-level Media Type for fonts. I am very > >>>> tempted to just remove the "Macintosh file type code" from the > >>>> registration template, and could go either way on replacing it with > >>>> an "Apple Uniform Type Identifier" > >>>> field - opinions welcome. > >>> > >>> Either way works. > > > > _______________________________________________ > > media-types mailing list > > media-types@ietf.org > > https://www.ietf.org/mailman/listinfo/media-types From nobody Thu Oct 18 23:18:04 2018 Return-Path: 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 CD1C0126CC7 for ; Thu, 18 Oct 2018 23:18:02 -0700 (PDT) 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, RCVD_IN_DNSWL_NONE=-0.0001, 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 aLQM2dI7aJby for ; Thu, 18 Oct 2018 23:18:00 -0700 (PDT) Received: from 3.mo177.mail-out.ovh.net (3.mo177.mail-out.ovh.net [46.105.36.172]) (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 DD872126BED for ; Thu, 18 Oct 2018 23:17:59 -0700 (PDT) Received: from player737.ha.ovh.net (unknown [10.109.159.132]) by mo177.mail-out.ovh.net (Postfix) with ESMTP id B511BCFA7F for ; Fri, 19 Oct 2018 08:17:56 +0200 (CEST) Received: from [192.168.170.33] (unknown [46.183.103.8]) (Authenticated sender: paul@hoplahup.net) by player737.ha.ovh.net (Postfix) with ESMTPSA id 963F2E00A7; Fri, 19 Oct 2018 08:17:45 +0200 (CEST) From: "Paul Libbrecht" To: "Ned Freed" Cc: "Alexey Melnikov" , media-types@ietf.org, "Chris Lilley" Date: Fri, 19 Oct 2018 08:17:33 +0200 X-Mailer: MailMate (1.12r5523) Message-ID: In-Reply-To: <01QYLCD6GWBE00BGSX@mauve.mrochek.com> References: <01Q88GLSKJC4011H9Q@mauve.mrochek.com> <44F6AEF0-8A25-4981-8620-293FD5907483@hoplahup.net> <01QYLCD6GWBE00BGSX@mauve.mrochek.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Ovh-Tracer-Id: 8580483193076648161 X-VR-SPAMSTATE: OK X-VR-SPAMSCORE: -100 X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgedtkedrfeehgddutdekucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuqfggjfdpvefjgfevmfevgfenuceurghilhhouhhtmecuhedttdenucesvcftvggtihhpihgvnhhtshculddquddttddm Archived-At: Subject: Re: [media-types] updates to RFC6838 in the horizon? 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Oct 2018 06:18:03 -0000 Thank you Ned, On 19 Oct 2018, at 0:38, Ned Freed wrote: > I don't see a problem with a draft updating the template. Pretty low > cost thing > to do. OTOH, nothing prevents a registration from including > "additional" > additional information, nor is a registration precluded from omitting > any or > all of the additional information fields. That’s pretty clear and it seems like, such an actualisation is probably useful to at least give a hint that clipboard types may be relevant. > So the value of formally adding the fields would be if it gets people > to > list them when they wouldn't otherwise. Given past experience I'm > skeptical > this will happen. Well, on this, I think it does depend a lot on the type. Sometimes it makes no sense (to all or to some) to make consider put this into a clipboard (e.g. because a selection does not make sense) and for these, the authors will simply ignore it. At least, it seems to me that clipboard type names make more sense than Macintosh 4-letter codes. thanks paul > >> Hi Paul, > >> On 16/10/2018 16:04, Paul Libbrecht wrote: >>> Dear all, >>> >>> this topic seems to have gone asleep since a while. >>> >>> Can anyone provide me information on the process of suggesting >>> changes >>> to the RFC 6838 (Media Type Specifications and Registration >>> Procedures)? > >> Post a new draft with the new template(*)? I can't promise that there >> would be enough energy to get the update done, but seeing something >> concrete would certainly help. > >> (*) - if you never done this, contact me off-list. > >> Thank you, >> Alexey > >>> thanks in advance. >>> >>> Paul >>> >>> On 8 Dec 2016, at 23:17, Paul Libbrecht wrote: >>> >>>> This goes along the proposal I had to add UTI and Windows clipboard >>>> flavour names within the template. I remember having been too late >>>> "last time". >>>> […] >>>> Ned, how is the process to file such a change fo the template? >>>> >>>>>> 2) Is there value in adding the Apple UTI (which is at least >>>>>> documented, and in current use) to the registration templates? >>>>> >>>>> Not that I'm aware of, but more information can't hurt. >>>>>> My reason for asking is draft-ietf-justfont-toplevel >>>>>> https://datatracker.ietf.org/doc/draft-ietf-justfont-toplevel/ >>>>> >>>>>> which will define a new top-level Media Type for fonts. I am very >>>>>> tempted to just remove the "Macintosh file type code" from the >>>>>> registration template, and could go either way on replacing it >>>>>> with >>>>>> an "Apple Uniform Type Identifier" >>>>>> field - opinions welcome. >>>>> >>>>> Either way works. >>> >>> _______________________________________________ >>> media-types mailing list >>> media-types@ietf.org >>> https://www.ietf.org/mailman/listinfo/media-types From nobody Sat Oct 20 07:50:08 2018 Return-Path: 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 BE20612D4F0 for ; Sat, 20 Oct 2018 07:50:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.208 X-Spam-Level: X-Spam-Status: No, score=-1.208 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RDNS_NONE=0.793, SPF_PASS=-0.001] autolearn=no 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 GYMtUptNbOsO for ; Sat, 20 Oct 2018 07:50:04 -0700 (PDT) Received: from mauve.mrochek.com (unknown [66.159.242.17]) (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 878A1127B92 for ; Sat, 20 Oct 2018 07:50:04 -0700 (PDT) Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01QYNOB7XALC00F1SO@mauve.mrochek.com> for media-types@ietf.org; Sat, 20 Oct 2018 07:45:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=201712; t=1540046699; bh=v2pUtaFa13gLWeRtBfZZ6Nx/7TxXl8JqeLmG4wuWdWo=; h=Cc:Date:From:Subject:In-reply-to:References:To:From; b=L/UytjLMQ1rPy3n7opRHFGxyPD+cTeoAQoLEnY7jKOePXCjcCeeJKo3L2tBIKJssU 7Wk+Cu7YMjzi9qkGFQyePrxpBGzKHaMydderYpS5gfo/12EQ8IOo26aU4qyfPDVNW9 I7x+sFOgarCGR4CncJedNFq9v9uaraRszvHY1ZGc= 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 <01QYM8BK7VLS00BGSX@mauve.mrochek.com>; Sat, 20 Oct 2018 07:44:56 -0700 (PDT) Cc: Ned Freed , Alexey Melnikov , media-types@ietf.org, Chris Lilley Message-id: <01QYNOB5YLQS00BGSX@mauve.mrochek.com> Date: Sat, 20 Oct 2018 07:41:33 -0700 (PDT) From: Ned Freed In-reply-to: "Your message dated Fri, 19 Oct 2018 08:17:33 +0200" References: <01Q88GLSKJC4011H9Q@mauve.mrochek.com> <44F6AEF0-8A25-4981-8620-293FD5907483@hoplahup.net> <01QYLCD6GWBE00BGSX@mauve.mrochek.com> To: Paul Libbrecht Archived-At: Subject: Re: [media-types] updates to RFC6838 in the horizon? 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Oct 2018 14:50:06 -0000 > Thank you Ned, > On 19 Oct 2018, at 0:38, Ned Freed wrote: > > I don't see a problem with a draft updating the template. Pretty low > > cost thing > > to do. OTOH, nothing prevents a registration from including > > "additional" > > additional information, nor is a registration precluded from omitting > > any or > > all of the additional information fields. > That’s pretty clear and it seems like, such an actualisation is > probably useful to at least give a hint that clipboard types may be > relevant. > > So the value of formally adding the fields would be if it gets people > > to > > list them when they wouldn't otherwise. Given past experience I'm > > skeptical > > this will happen. > Well, on this, I think it does depend a lot on the type. > Sometimes it makes no sense (to all or to some) to make consider put > this into a clipboard (e.g. because a selection does not make sense) and > for these, the authors will simply ignore it. At least, it seems to me > that clipboard type names make more sense than Macintosh 4-letter codes. It's not a question of what makes sense, it's a question of the information people have available and thus what they are able and willing to put in a registration. Past experience says people are unlikely to go the extra mile to think about any of this stuff even if we prompt them for it. Ned From nobody Sat Oct 20 21:43:31 2018 Return-Path: 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 487D7130E1E for ; Sat, 20 Oct 2018 21:43:30 -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 Mv-3s0V5W1GV for ; Sat, 20 Oct 2018 21:43:28 -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 00926130E06 for ; Sat, 20 Oct 2018 21:43:27 -0700 (PDT) Received: from [90.114.230.151] (helo=w3.org) by raoul.w3.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1gE5aA-000613-2Q; Sun, 21 Oct 2018 04:43:18 +0000 Date: Sun, 21 Oct 2018 00:43:16 -0400 From: Eric Prud'hommeaux To: Ned Freed Cc: Paul Libbrecht , media-types@ietf.org, Alexey Melnikov , Chris Lilley Message-ID: <20181021044314.GA15061@w3.org> References: <01Q88GLSKJC4011H9Q@mauve.mrochek.com> <44F6AEF0-8A25-4981-8620-293FD5907483@hoplahup.net> <01QYLCD6GWBE00BGSX@mauve.mrochek.com> <01QYNOB5YLQS00BGSX@mauve.mrochek.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <01QYNOB5YLQS00BGSX@mauve.mrochek.com> Organization: World Wide Web Consortium (W3C) - http://www.w3.org/ User-Agent: Mutt/1.9.4 (2018-02-28) Archived-At: Subject: Re: [media-types] updates to RFC6838 in the horizon? 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Oct 2018 04:43:30 -0000 * Ned Freed [2018-10-20 07:41-0700] > > Thank you Ned, > > > On 19 Oct 2018, at 0:38, Ned Freed wrote: > > > > I don't see a problem with a draft updating the template. Pretty low > > > cost thing > > > to do. OTOH, nothing prevents a registration from including > > > "additional" > > > additional information, nor is a registration precluded from omitting > > > any or > > > all of the additional information fields. > > > That’s pretty clear and it seems like, such an actualisation is > > probably useful to at least give a hint that clipboard types may be > > relevant. > > > > So the value of formally adding the fields would be if it gets people > > > to > > > list them when they wouldn't otherwise. Given past experience I'm > > > skeptical > > > this will happen. > > > Well, on this, I think it does depend a lot on the type. > > Sometimes it makes no sense (to all or to some) to make consider put > > this into a clipboard (e.g. because a selection does not make sense) and > > for these, the authors will simply ignore it. At least, it seems to me > > that clipboard type names make more sense than Macintosh 4-letter codes. > > It's not a question of what makes sense, it's a question of the information > people have available and thus what they are able and willing to put in a > registration. > > Past experience says people are unlikely to go the extra mile to think > about any of this stuff even if we prompt them for it. Speaking from experience, it occurs to almost no one to think about a clipboard type name and then wedge it into an unreceptive form. I believe that the folks who fill these out are pretty diligent. Clearly marking optional fields as such and providing links to understand, e.g. clipboard type names, allows said diligent netizens to leave less interop to chance, which is why they're filling out the form in the first place. > Ned > > > _______________________________________________ > media-types mailing list > media-types@ietf.org > https://www.ietf.org/mailman/listinfo/media-types -- -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. From nobody Sun Oct 21 07:57:18 2018 Return-Path: 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 18C801292AD for ; Sun, 21 Oct 2018 07:57:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.208 X-Spam-Level: X-Spam-Status: No, score=-1.208 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RDNS_NONE=0.793, SPF_PASS=-0.001] autolearn=no 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 ID6drBjCJv_6 for ; Sun, 21 Oct 2018 07:57:15 -0700 (PDT) Received: from mauve.mrochek.com (unknown [66.159.242.17]) (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 BEE02127333 for ; Sun, 21 Oct 2018 07:57:15 -0700 (PDT) Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01QYP2UH49TS00FI5W@mauve.mrochek.com> for media-types@ietf.org; Sun, 21 Oct 2018 07:52:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=201712; t=1540133531; bh=bonbwyIBvPnJEvvBHqW5m2/i+Q46FI8UoJXh8cS4GOQ=; h=Cc:Date:From:Subject:In-reply-to:References:To:From; b=Y9vgixCojM36NUkIa9C3OQCGN0b7rbWIYiNq/ZAe8gt/z4uLHJ0l0G3IWz0qc6qdI fmwhi8Hqk6biDgJR+zbR9ZbrW8fBmofnWgpgEYjz2peG+yW/9Qu1HpXdWtITMN8XCU JyXudjLN7OWG8q0wc8Hq6sn6+hgK2VXySRF8JEm8= 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 <01QYM8BK7VLS00BGSX@mauve.mrochek.com>; Sun, 21 Oct 2018 07:52:07 -0700 (PDT) Cc: Ned Freed , Paul Libbrecht , media-types@ietf.org, Alexey Melnikov , Chris Lilley Message-id: <01QYP2UEXT9E00BGSX@mauve.mrochek.com> Date: Sun, 21 Oct 2018 07:48:37 -0700 (PDT) From: Ned Freed In-reply-to: "Your message dated Sun, 21 Oct 2018 00:43:16 -0400" <20181021044314.GA15061@w3.org> References: <01Q88GLSKJC4011H9Q@mauve.mrochek.com> <44F6AEF0-8A25-4981-8620-293FD5907483@hoplahup.net> <01QYLCD6GWBE00BGSX@mauve.mrochek.com> <01QYNOB5YLQS00BGSX@mauve.mrochek.com> <20181021044314.GA15061@w3.org> To: Eric Prud'hommeaux Archived-At: Subject: Re: [media-types] updates to RFC6838 in the horizon? 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Oct 2018 14:57:17 -0000 > Speaking from experience, it occurs to almost no one to think about a > clipboard type name and then wedge it into an unreceptive form. I > believe that the folks who fill these out are pretty diligent. Some are. Many are not. Having seen every registration that has come in for the past 10+ year, I speak with some authority here. > Clearly > marking optional fields as such and providing links to understand, > e.g. clipboard type names, allows said diligent netizens to leave less > interop to chance, which is why they're filling out the form in the > first place. Again, I have no objection to adding such fields if people want to spend the time to do so. However, my skepticism as to their utility remains. Ned From nobody Tue Oct 30 22:23:12 2018 Return-Path: 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 09605124D68 for ; Tue, 30 Oct 2018 22:23:11 -0700 (PDT) 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, RCVD_IN_DNSWL_NONE=-0.0001] 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 9v8DGX9WDsYq for ; Tue, 30 Oct 2018 22:23:09 -0700 (PDT) Received: from bouvier.getmail.no (bouvier.getmail.no [84.210.184.8]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4D395120072 for ; Tue, 30 Oct 2018 22:23:08 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by bouvier.getmail.no (Postfix) with ESMTP id F27384002D; Wed, 31 Oct 2018 06:23:04 +0100 (CET) Received: from bouvier.getmail.no ([127.0.0.1]) by localhost (bouvier.get.c.bitbit.net [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id J0USmO6BJ-Iv; Wed, 31 Oct 2018 06:23:04 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by bouvier.getmail.no (Postfix) with ESMTP id 30C944002E; Wed, 31 Oct 2018 06:23:04 +0100 (CET) X-Virus-Scanned: amavisd-new at bouvier.get.c.bitbit.net Received: from bouvier.getmail.no ([127.0.0.1]) by localhost (bouvier.get.c.bitbit.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id mqlDlekMF-_k; Wed, 31 Oct 2018 06:23:04 +0100 (CET) Received: from hjemme.reinholdtsen.name (cm-84.212.222.24.getinternet.no [84.212.222.24]) by bouvier.getmail.no (Postfix) with SMTP id DFF454002D; Wed, 31 Oct 2018 06:23:03 +0100 (CET) Received: (nullmailer pid 2255 invoked by uid 10001); Wed, 31 Oct 2018 05:23:03 -0000 From: Petter Reinholdtsen To: media-types@ietf.org Date: Wed, 31 Oct 2018 06:23:03 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain Archived-At: Subject: [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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2018 05:23:11 -0000 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? -- Happy hacking Petter Reinholdtsen From nobody Wed Oct 31 03:27:05 2018 Return-Path: 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 ; 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 ; 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 ; 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 ) 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 To: Petter Reinholdtsen Cc: media-types@ietf.org Message-ID: <20181031102655.GI17721@w3.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: World Wide Web Consortium (W3C) - http://www.w3.org/ User-Agent: Mutt/1.9.4 (2018-02-28) Archived-At: 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2018 10:27:05 -0000 * Petter Reinholdtsen [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. From nobody Wed Oct 31 14:52:35 2018 Return-Path: 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 20894127333 for ; Wed, 31 Oct 2018 14:52:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.633 X-Spam-Level: X-Spam-Status: No, score=-3.633 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_SOFTFAIL=0.665] 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 dDb5bH2im4Y7 for ; Wed, 31 Oct 2018 14:52:32 -0700 (PDT) Received: from pechora1.lax.icann.org (pechora1.icann.org [IPv6:2620:0:2d0:201::1:71]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6384C129C6A for ; Wed, 31 Oct 2018 14:52:32 -0700 (PDT) Received: from mail-lj1-x22b.google.com (mail-lj1-x22b.google.com [IPv6:2a00:1450:4864:20::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pechora1.lax.icann.org (Postfix) with ESMTPS id DDAE31E01ED for ; Wed, 31 Oct 2018 21:52:31 +0000 (UTC) Received: by mail-lj1-x22b.google.com with SMTP id g8-v6so13382195ljk.1 for ; Wed, 31 Oct 2018 14:52:31 -0700 (PDT) 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=9QDoJe1lDVTwpWv4rsOB37SqIIXmy33BWaa8Bd7GmSQ=; b=pqXP3foPMKQRLLSSi6cy5RsUbHMbRL5JHAAtedV15cz2pv5HShN1TIt7NZ9iiPHh+y 1BupAD3tlKALZ3T361Qu99UGFWEc8H5gZzFLMwKcKVW7MY85Cr5JZHDuujw+pmY25xzw 1j3/hXWE+26rnHgsQqGJzMvx1OoDsNzotiptZIy5fljXDfUppeFUlfIKU29ihn/lRG90 7sz2pAy8fzstcxdxmHmbOeFnSPTeZSocseaAkjRVueJT/LWaXq/jYGxfFjY31kjZTiuk wnJhsKxdp7Ku8sLT3x6vRINoerWevISijDis+NDN+a2lIJQEs6pHhUi6yU7J5ja88cGP EEXw== 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=9QDoJe1lDVTwpWv4rsOB37SqIIXmy33BWaa8Bd7GmSQ=; b=f9pN/1kvpgqu9Dqh37h6x0bjjiFVkxJA2jfh6uOio48vSn84AqIlBDVLhiO2kyLbgX EXpZI7YRBE1AHPQiR0PmDDixeAEvDpG5/Ekz+OOKgv/a3gmrWfG+EvWT8rjyWHfinHQs jYnYqRFbzxn5TP15aQLEeFO6u+Bst6ampL7wkXi7OZXYp/i1KhXXCNvrhVpV11UIbWdQ pbrQgQk7LmKKSAZ11U7/cHEz97CtjwoyS1gEBBmtGpP1YYcZbTWlUppUdzPKGsqnYxBa It11C5/DcSXWVndeOcVsMxoA4bLad5LjENRUNbvLnl6HwVI6/dQkXeMi+2JjiSqCPhF0 32cA== X-Gm-Message-State: AGRZ1gLmOoPHdZ1C30Z62KPt+hCcCa2veisXo+58Z2MXzmCKaQ/xqVh5 jjOXHc7k1kb+XPlMsgFjxosAdWxmKIgnfuah+MMvt4ON X-Google-Smtp-Source: AJdET5fNhJfv1vlhf8O9ZZCJ5q3d5FzaKvYIn4i+zYkQAfRoH0Jl/Olzzo+avqpKqTdxVaxNKXwWn+9cax6mtpt4IaI= X-Received: by 2002:a2e:1603:: with SMTP id w3-v6mr3209778ljd.33.1541022749529; Wed, 31 Oct 2018 14:52:29 -0700 (PDT) MIME-Version: 1.0 From: "Murray S. Kucherawy" Date: Wed, 31 Oct 2018 14:52:17 -0700 Message-ID: To: media-types@iana.org Content-Type: multipart/alternative; boundary="000000000000939fa205798d517a" Archived-At: Subject: [media-types] Question about file extensions and Mac file type codes 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2018 21:52:35 -0000 --000000000000939fa205798d517a Content-Type: text/plain; charset="UTF-8" If an application includes extensions and/or Mac file type codes, is the set presented supposed to be exhaustive, or can it be a partial or open-ended list? I'm looking at: 3. File extension(s): various media file types, such as .mp4, .mov, .mkv, etc. ...and wondering if we're happy with that. -MSK --000000000000939fa205798d517a Content-Type: text/html; charset="UTF-8"
If an application includes extensions and/or Mac file type codes, is the set presented supposed to be exhaustive, or can it be a partial or open-ended list?

I'm looking at:

3. File extension(s): various media file types, such as .mp4, .mov, .mkv, etc.

...and wondering if we're happy with that.

-MSK
--000000000000939fa205798d517a-- From nobody Wed Oct 31 23:42:48 2018 Return-Path: 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 B0863130DE1 for ; Wed, 31 Oct 2018 23:42:47 -0700 (PDT) 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] 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 EdFVUKZ3yxq2 for ; Wed, 31 Oct 2018 23:42:44 -0700 (PDT) Received: from ryder.getmail.no (ryder.getmail.no [84.210.184.14]) by ietfa.amsl.com (Postfix) with ESMTP id 01BC0124C04 for ; Wed, 31 Oct 2018 23:42:43 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by ryder.getmail.no (Postfix) with ESMTP id BB2A862C83; Thu, 1 Nov 2018 07:42:37 +0100 (CET) Received: from ryder.getmail.no ([127.0.0.1]) by localhost (ryder.get.c.bitbit.net [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id ifpuIkM-UBqq; Thu, 1 Nov 2018 07:42:37 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by ryder.getmail.no (Postfix) with ESMTP id 2FED162C6C; Thu, 1 Nov 2018 07:42:37 +0100 (CET) X-Virus-Scanned: amavisd-new at ryder.getmail.no Received: from ryder.getmail.no ([127.0.0.1]) by localhost (ryder.get.c.bitbit.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id JHJnBEY0taI6; Thu, 1 Nov 2018 07:42:37 +0100 (CET) Received: from hjemme.reinholdtsen.name (cm-84.212.222.24.getinternet.no [84.212.222.24]) by ryder.getmail.no (Postfix) with SMTP id 0D1B062C83; Thu, 1 Nov 2018 07:42:37 +0100 (CET) Received: (nullmailer pid 9413 invoked by uid 10001); Thu, 01 Nov 2018 06:42:36 -0000 From: Petter Reinholdtsen To: media-types@ietf.org In-Reply-To: <20181031102655.GI17721@w3.org> References: <20181031102655.GI17721@w3.org> Date: Thu, 01 Nov 2018 07:42:36 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain Archived-At: 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2018 06:42:48 -0000 [Eric Prud'hommeaux] > 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 have no idea how to identify the tool maintainers which currently recognize text/x-{patch,diff}. Perhaps at least the maintainers of http://www.gnu.org/software/diffutils/ and http://savannah.gnu.org/projects/patch/ are relevant contributors to such discussion? They do not really use or recognice MIME types, being command line tools, but are responsible for the typical producer and consumer of these files. On Debian systems, text/x-patch and text/x-diff are set to be aliases for each other, with text/x-patch being the primary one, according to the /usr/share/mime/packages/freedesktop.org.xml file provided by the shared-mime-info package. I guess this provide one data point for preferring text/x-patch over text/x-diff as the official MIME type. Personally I would prefer to move to text/patch for the official MIME type as diff produces a patch in text format, which I believe text/patch expresses better than any of the alternatives. I notice you mention application/*. Is not text/* a better choice, given that for example patches in emails could be shown directly in the email and do not need a "viewer" to be readable to those of us receiving patches? -- Happy hacking Petter Reinholdtsen From nobody Wed Oct 31 23:58:40 2018 Return-Path: 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 2A166124408 for ; Wed, 31 Oct 2018 23:58:38 -0700 (PDT) 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] 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 PMmvQkWyhp5p for ; Wed, 31 Oct 2018 23:58:36 -0700 (PDT) Received: from ryder.getmail.no (ryder.getmail.no [84.210.184.14]) by ietfa.amsl.com (Postfix) with ESMTP id 4E15212008A for ; Wed, 31 Oct 2018 23:58:36 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by ryder.getmail.no (Postfix) with ESMTP id 799D062C6C; Thu, 1 Nov 2018 07:58:35 +0100 (CET) Received: from ryder.getmail.no ([127.0.0.1]) by localhost (ryder.get.c.bitbit.net [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id Ss6VbqpDn0NJ; Thu, 1 Nov 2018 07:58:35 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by ryder.getmail.no (Postfix) with ESMTP id 199BA62C83; Thu, 1 Nov 2018 07:58:35 +0100 (CET) X-Virus-Scanned: amavisd-new at ryder.getmail.no Received: from ryder.getmail.no ([127.0.0.1]) by localhost (ryder.get.c.bitbit.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id dTiEdkkIl_4U; Thu, 1 Nov 2018 07:58:35 +0100 (CET) Received: from hjemme.reinholdtsen.name (cm-84.212.222.24.getinternet.no [84.212.222.24]) by ryder.getmail.no (Postfix) with SMTP id E948A62C6C; Thu, 1 Nov 2018 07:58:34 +0100 (CET) Received: (nullmailer pid 9690 invoked by uid 10001); Thu, 01 Nov 2018 06:58:34 -0000 From: Petter Reinholdtsen To: media-types@ietf.org References: <5a5ba7c3-9992-b9e4-4aca-e2cc35e068c7@w3.org> In-reply-to: <5a5ba7c3-9992-b9e4-4aca-e2cc35e068c7@w3.org> Date: Thu, 01 Nov 2018 07:58:34 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain Archived-At: Subject: Re: [media-types] Add RFC reference to image/png mime type registration? X-BeenThere: media-types@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2018 06:58:38 -0000 [Chris Lilley] > No, I don't agree. The most recent reference is from 2003: OK. I just wanted to make sure everyone involved with IANA were aware that the registration text for image/png lacked updated references to the standards describing the format. I leave it completely up to the custodians of the IANA register if any update should happen. :) -- Happy hacking Petter Reinholdtsen