Re: [media-types] updates to RFC6838 in the horizon?
Alexey Melnikov <alexey.melnikov@isode.com> Thu, 18 October 2018 18:02 UTC
Return-Path: <alexey.melnikov@isode.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 6734D130E04 for <media-types@ietfa.amsl.com>; 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 <media-types@ietfa.amsl.com>; 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 <media-types@ietf.org>; 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 <W8jKygAG7YEt@statler.isode.com>; Thu, 18 Oct 2018 19:02:51 +0100
To: Paul Libbrecht <paul@hoplahup.net>
Cc: Ned Freed <ned.freed@mrochek.com>, media-types@ietf.org, Chris Lilley <chris@w3.org>
References: <e25a4143-7999-4ed0-9947-776033636f15@getmailbird.com> <01Q88GLSKJC4011H9Q@mauve.mrochek.com> <44F6AEF0-8A25-4981-8620-293FD5907483@hoplahup.net> <D01957F2-D4C6-4899-8417-C90B7546CD54@hoplahup.net>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Openpgp: preference=signencrypt
Message-ID: <f63aa5c6-5c45-8c91-3285-3421621e2621@isode.com>
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: <D01957F2-D4C6-4899-8417-C90B7546CD54@hoplahup.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/qSyB94aG3OuFnkDlTBE1jSMBC2I>
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: Thu, 18 Oct 2018 18:03:04 -0000
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
- [media-types] Macintosh file type code Chris Lilley
- Re: [media-types] Macintosh file type code Ned Freed
- Re: [media-types] Macintosh file type code Paul Libbrecht
- Re: [media-types] Macintosh file type code Martin J. Dürst
- Re: [media-types] Macintosh file type code Chris Lilley
- Re: [media-types] updates to RFC6838 in the horiz… Paul Libbrecht
- Re: [media-types] updates to RFC6838 in the horiz… Alexey Melnikov
- Re: [media-types] updates to RFC6838 in the horiz… Ned Freed
- Re: [media-types] updates to RFC6838 in the horiz… Paul Libbrecht
- Re: [media-types] updates to RFC6838 in the horiz… Ned Freed
- Re: [media-types] updates to RFC6838 in the horiz… Eric Prud'hommeaux
- Re: [media-types] updates to RFC6838 in the horiz… Ned Freed