Re: [apps-discuss] Encouraging third party registrations

Alexey Melnikov <alexey.melnikov@isode.com> Tue, 15 November 2011 02:13 UTC

Return-Path: <alexey.melnikov@isode.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8232611E830B for <apps-discuss@ietfa.amsl.com>; Mon, 14 Nov 2011 18:13:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.449
X-Spam-Level:
X-Spam-Status: No, score=-102.449 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VO4X3T6ZsmiT for <apps-discuss@ietfa.amsl.com>; Mon, 14 Nov 2011 18:13:33 -0800 (PST)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by ietfa.amsl.com (Postfix) with ESMTP id 897F221F8D4C for <apps-discuss@ietf.org>; Mon, 14 Nov 2011 18:13:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1321323212; d=isode.com; s=selector; i=@isode.com; bh=qs5sCYsck7z00/K84xl8oq76NR9WyCFDMtVfkac6Cgs=; 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=A1Br/EKg7rJqgr5Nx77zsTX8muTd6QbStuTE2vsI9RQxaw20nfSrHsXcfM6b/od89pUPq2 5t9I58XatHSiHVLpBkhuBxza3RT20ZwLb3uJPI1/vjKPeQT0K+FX+W+5L/9Sqdf2xoOvEy awbYELnPysJQ1NUoQf/46uiS2o5rV6o=;
Received: from [192.168.174.158] (60-251-183-229.HINET-IP.hinet.net [60.251.183.229]) by rufus.isode.com (submission channel) via TCP with ESMTPSA id <TsHKyQAFEBiK@rufus.isode.com>; Tue, 15 Nov 2011 02:13:32 +0000
Message-ID: <4EC1CAC9.7000301@isode.com>
Date: Tue, 15 Nov 2011 02:13:29 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:8.0) Gecko/20111105 Thunderbird/8.0
To: =?ISO-8859-1?Q?=22Martin_J=2E_D=FCrst=22?= <duerst@it.aoyama.ac.jp>
References: <C68CB012D9182D408CED7B884F441D4D0611DABF22@nambxv01a.corp.adobe.com> <4EC0BE9E.8020702@it.aoyama.ac.jp> <01O8ETBP3QY400RCTX@mauve.mrochek.com> <4EC1C3D7.7070402@it.aoyama.ac.jp>
In-Reply-To: <4EC1C3D7.7070402@it.aoyama.ac.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: quoted-printable
Cc: Roy Fielding <fielding@adobe.com>, Ned Freed <ned.freed@mrochek.com>, "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] Encouraging third party registrations
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 02:13:34 -0000

Hi Martin,

On 15/11/2011 01:43, "Martin J. Dürst" wrote:
> 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.
+1. To be honest I didn't know that this procedure was to be expected. 
In all cases I was expecting that some representative of the 
company/organization that defined the media type should be involved in a 
registration, even if somebody else does the work to actually document it.
> 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.
Exactly.
> 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 
> http://tools.ietf.org/html/draft-freed-media-type-regs-01#section-5.5, 
> 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 
> http://www.iana.org/assignments/media-types/index.html).
>
>
> Regards,   Martin.
Best Regards,
Alexey