[apps-discuss] Encouraging third party registrations (was: Re: A modest proposal for MIME types (and URI schemes))

"Martin J. Dürst" <duerst@it.aoyama.ac.jp> Tue, 15 November 2011 01:43 UTC

Return-Path: <duerst@it.aoyama.ac.jp>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 5AE1A11E8099 for <apps-discuss@ietfa.amsl.com>; Mon, 14 Nov 2011 17:43:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.615
X-Spam-Status: No, score=-99.615 tagged_above=-999 required=5 tests=[AWL=0.175, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id lzr4oahzVqqq for <apps-discuss@ietfa.amsl.com>; Mon, 14 Nov 2011 17:43:55 -0800 (PST)
Received: from scintmta01.scbb.aoyama.ac.jp (scintmta01.scbb.aoyama.ac.jp []) by ietfa.amsl.com (Postfix) with ESMTP id 54C2D11E80CC for <apps-discuss@ietf.org>; Mon, 14 Nov 2011 17:43:55 -0800 (PST)
Received: from scmse01.scbb.aoyama.ac.jp ([]) by scintmta01.scbb.aoyama.ac.jp (secret/secret) with SMTP id pAF1hsUu028267 for <apps-discuss@ietf.org>; Tue, 15 Nov 2011 10:43:54 +0900
Received: from (unknown []) by scmse01.scbb.aoyama.ac.jp with smtp id 2c90_2d54_46ba6716_0f2b_11e1_bd48_001d096c566a; Tue, 15 Nov 2011 10:43:54 +0900
Received: from [IPv6:::1] ([]:47226) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S156D670> for <apps-discuss@ietf.org> from <duerst@it.aoyama.ac.jp>; Tue, 15 Nov 2011 10:43:57 +0900
Message-ID: <4EC1C3D7.7070402@it.aoyama.ac.jp>
Date: Tue, 15 Nov 2011 10:43:51 +0900
From: "\"Martin J. Dürst\"" <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv: Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: Ned Freed <ned.freed@mrochek.com>
References: <C68CB012D9182D408CED7B884F441D4D0611DABF22@nambxv01a.corp.adobe.com> <4EC0BE9E.8020702@it.aoyama.ac.jp> <01O8ETBP3QY400RCTX@mauve.mrochek.com>
In-Reply-To: <01O8ETBP3QY400RCTX@mauve.mrochek.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: Roy Fielding <fielding@adobe.com>, "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Subject: [apps-discuss] Encouraging third party registrations (was: Re: A modest proposal for MIME types (and URI schemes))
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Nov 2011 01:43:56 -0000

Hello Ned, others,

On 2011/11/15 4:33, Ned Freed wrote:

>> > ENCOURAGE the public to register any names that they have seen in
>> > deployed software. (same for URI schemes)
>> I think third-party registration is indeed something we should encourage
>> more.
> How do you propose we do that?

It seems that currently, people don't even know that it is possible. So 
the first step is to make this more known. On another list, you write: 
"We have always allowed registrations by any interested party." That's 
apparently true, but is it done because nowhere in RFC 4288 it says it's 
not possible? Then making it explicit in draft-freed-media-type-regs 
should help.

For example, you could put in a section 4.12, (Non-)Requirements for 
Contact Information, Author, and Change Controller, saying explicitly 
that third-party registrations are welcome.

This could also explain what in such a case contact information, author, 
and change controller should be. I'd assume that contact information 
goes to the submitter, but change controller stays with the company or 
individual that created the format, but you'll know better what's 
current practice. If I did a third-party registration, this would be the 
place where I'd really not know which way to go.

You can also add pointers to that new section, or just mention the fact, 
in other places where somebody might potentially look. As an example, in 
you could say that in addition to providing comments, new registrations 
and change requests by third parties are also possible.

The next step would then be to put text saying "Media Types may also be 
registered by third parties." or so on the relevant pages at IANA (e.g. 
http://www.iana.org/cgi-bin/mediatypes.pl and 

Regards,   Martin.