Re: [media-types] updates to RFC6838 in the horizon?

"Paul Libbrecht" <paul@hoplahup.net> Tue, 16 October 2018 15:07 UTC

Return-Path: <paul@hoplahup.net>
X-Original-To: media-types@ietfa.amsl.com
Delivered-To: media-types@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56D5F12D4EE for <media-types@ietfa.amsl.com>; 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 <media-types@ietfa.amsl.com>; 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 <media-types@ietf.org>; 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 <media-types@ietf.org>; 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 <paul@hoplahup.net>
To: Ned Freed <ned.freed@mrochek.com>
Cc: media-types@ietf.org, Chris Lilley <chris@w3.org>
Date: Tue, 16 Oct 2018 17:04:32 +0200
X-Mailer: MailMate (1.12r5523)
Message-ID: <D01957F2-D4C6-4899-8417-C90B7546CD54@hoplahup.net>
In-Reply-To: <44F6AEF0-8A25-4981-8620-293FD5907483@hoplahup.net>
References: <e25a4143-7999-4ed0-9947-776033636f15@getmailbird.com> <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: <https://mailarchive.ietf.org/arch/msg/media-types/SVJB5cfNMeGIZqIB8h320AZqqNU>
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." <media-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/media-types>, <mailto:media-types-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/media-types/>
List-Post: <mailto:media-types@ietf.org>
List-Help: <mailto:media-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/media-types>, <mailto:media-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 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.