Re: [apps-discuss] Encouraging third party registrations

"Martin J. Dürst" <duerst@it.aoyama.ac.jp> Tue, 15 November 2011 02:24 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 [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B0E911E8385 for <apps-discuss@ietfa.amsl.com>; Mon, 14 Nov 2011 18:24:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.618
X-Spam-Level:
X-Spam-Status: No, score=-99.618 tagged_above=-999 required=5 tests=[AWL=0.172, 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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9oNZcu1nFZsQ for <apps-discuss@ietfa.amsl.com>; Mon, 14 Nov 2011 18:24:52 -0800 (PST)
Received: from scintmta02.scbb.aoyama.ac.jp (scintmta02.scbb.aoyama.ac.jp [133.2.253.34]) by ietfa.amsl.com (Postfix) with ESMTP id ECC8D11E837E for <apps-discuss@ietf.org>; Mon, 14 Nov 2011 18:24:48 -0800 (PST)
Received: from scmse02.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta02.scbb.aoyama.ac.jp (secret/secret) with SMTP id pAF2OhWj004864 for <apps-discuss@ietf.org>; Tue, 15 Nov 2011 11:24:43 +0900
Received: from (unknown [133.2.206.133]) by scmse02.scbb.aoyama.ac.jp with smtp id 201e_0a49_fa650db6_0f30_11e1_a079_001d096c5782; Tue, 15 Nov 2011 11:24:43 +0900
Received: from [IPv6:::1] ([133.2.210.1]:55369) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S156D6B0> for <apps-discuss@ietf.org> from <duerst@it.aoyama.ac.jp>; Tue, 15 Nov 2011 11:24:46 +0900
Message-ID: <4EC1CD67.5030400@it.aoyama.ac.jp>
Date: Tue, 15 Nov 2011 11:24:39 +0900
From: =?UTF-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: Larry Masinter <masinter@adobe.com>
References: <C68CB012D9182D408CED7B884F441D4D0611DABF22@nambxv01a.corp.adobe.com> <4EC0BE9E.8020702@it.aoyama.ac.jp> <01O8ETBP3QY400RCTX@mauve.mrochek.com> <4EC1C3D7.7070402@it.aoyama.ac.jp> <4EC1CAC9.7000301@isode.com> <C68CB012D9182D408CED7B884F441D4D0611DAC11F@nambxv01a.corp.adobe.com>
In-Reply-To: <C68CB012D9182D408CED7B884F441D4D0611DAC11F@nambxv01a.corp.adobe.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
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:24:53 -0000

On 2011/11/15 11:15, Larry Masinter wrote:
> Who should a third-party registrar list as the "change controller" ?

Good question. I already proposed that it be answered in Ned's document. 
See below.

Regards,   Martin.

> -----Original Message-----
> From: apps-discuss-bounces@ietf.org [mailto:apps-discuss-bounces@ietf.org] On Behalf Of Alexey Melnikov
> Sent: Tuesday, November 15, 2011 10:13 AM
> To: "Martin J. Dürst"
> Cc: Roy Fielding; Ned Freed; apps-discuss@ietf.org
> Subject: Re: [apps-discuss] Encouraging third party registrations

> On 15/11/2011 01:43, "Martin J. Dürst" wrote:

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