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

Ned Freed <ned.freed@mrochek.com> Tue, 15 November 2011 04:38 UTC

Return-Path: <ned.freed@mrochek.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 D1E591F0DA9 for <apps-discuss@ietfa.amsl.com>; Mon, 14 Nov 2011 20:38:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.429
X-Spam-Level:
X-Spam-Status: No, score=-2.429 tagged_above=-999 required=5 tests=[AWL=-0.130, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 bNGkYSkmQH+e for <apps-discuss@ietfa.amsl.com>; Mon, 14 Nov 2011 20:38:38 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 085501F0DB0 for <apps-discuss@ietf.org>; Mon, 14 Nov 2011 20:38:38 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01O8F9FSZFV4016US7@mauve.mrochek.com> for apps-discuss@ietf.org; Mon, 14 Nov 2011 20:38:32 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01O8DV7Q11A800RCTX@mauve.mrochek.com>; Mon, 14 Nov 2011 20:38:27 -0800 (PST)
Message-id: <01O8F9FQDXQ400RCTX@mauve.mrochek.com>
Date: Mon, 14 Nov 2011 20:35:48 -0800
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Tue, 15 Nov 2011 10:43:51 +0900" <4EC1C3D7.7070402@it.aoyama.ac.jp>
MIME-version: 1.0
Content-type: TEXT/PLAIN; format="flowed"
References: <C68CB012D9182D408CED7B884F441D4D0611DABF22@nambxv01a.corp.adobe.com> <4EC0BE9E.8020702@it.aoyama.ac.jp> <01O8ETBP3QY400RCTX@mauve.mrochek.com> <4EC1C3D7.7070402@it.aoyama.ac.jp>
To: "\"Martin J. Dürst\"" <duerst@it.aoyama.ac.jp>
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 (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 04:38:38 -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.

Seems like a good idea to me. I'll see what I can come up with. Unfortunately
we're in draft-blackout so I can't post a revision.

> 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.

OK.

> 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.

That's nominally how it works, but I'm not strongly wedded to it as an
approach.

> 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.

OK.

> 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)

Realistically, that's the place where it is likely to do the most good.

				Ned