Re: [apps-discuss] Possible IESG statement on IESG processing of MIME type registrations from other SDOs
"Martin J. Dürst" <duerst@it.aoyama.ac.jp> Wed, 09 March 2011 07:43 UTC
Return-Path: <duerst@it.aoyama.ac.jp>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 15B433A6822 for <apps-discuss@core3.amsl.com>; Tue, 8 Mar 2011 23:43:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.84
X-Spam-Level:
X-Spam-Status: No, score=-99.84 tagged_above=-999 required=5 tests=[AWL=-0.050, 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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IM6a8nz+4dw5 for <apps-discuss@core3.amsl.com>; Tue, 8 Mar 2011 23:43:37 -0800 (PST)
Received: from scintmta02.scbb.aoyama.ac.jp (scintmta02.scbb.aoyama.ac.jp [133.2.253.34]) by core3.amsl.com (Postfix) with ESMTP id 33F2A3A685D for <apps-discuss@ietf.org>; Tue, 8 Mar 2011 23:43:36 -0800 (PST)
Received: from scmse02.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta02.scbb.aoyama.ac.jp (secret/secret) with SMTP id p297ikTW020245 for <apps-discuss@ietf.org>; Wed, 9 Mar 2011 16:44:46 +0900
Received: from (unknown [133.2.206.133]) by scmse02.scbb.aoyama.ac.jp with smtp id 7c1d_2f09_1ad304f2_4a21_11e0_a579_001d096c5782; Wed, 09 Mar 2011 16:44:46 +0900
Received: from [IPv6:::1] ([133.2.210.1]:59433) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S14E33B8> for <apps-discuss@ietf.org> from <duerst@it.aoyama.ac.jp>; Wed, 9 Mar 2011 16:44:47 +0900
Message-ID: <4D772FD6.4080305@it.aoyama.ac.jp>
Date: Wed, 09 Mar 2011 16:44:22 +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.0; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: Peter Saint-Andre <stpeter@stpeter.im>
References: <4D6FBE4D.10602@isode.com> <6.2.5.6.2.20110308164758.0be3c0a8@resistor.net> <AANLkTinKPGRPOCb_7wai6Rq0tKdop0yGb7UfHuzUkpXu@mail.gmail.com> <4D76FB18.1040304@stpeter.im>
In-Reply-To: <4D76FB18.1040304@stpeter.im>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Cc: apps-discuss@ietf.org
Subject: Re: [apps-discuss] Possible IESG statement on IESG processing of MIME type registrations from other SDOs
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 09 Mar 2011 07:43:39 -0000
Hello Peter, On 2011/03/09 12:59, Peter Saint-Andre wrote: > On 3/8/11 6:34 PM, Ted Hardie wrote: >> I'm not sure I agree that it turns into a formal standards process, >> but I definitely agree that it's going to be very hard for outsiders >> to find this statement and do the right thing, absent additional clue. > > Currently folks working within other SDOs ping one or both of the > Applications Area Directors, who usually say "we know it's not > mandatory, but it would be helpful if you could write a brief > Internet-Draft defining your registration request". So outsiders don't > need to find this statement and do the right thing from the start, and I > don't think the Apps ADs (or IESG in general) expect that they would. [Assuming the above also applies to W3C] I'm no longer working for W3C, but if I still did, and in particular if I still was in charge of coordinating these registration requests, I'd very clearly and explicitly not be happy with this. In my view, one of the main points of RFC 4288 was exactly to get away from the need to have things in two places, and to get away from the need for people who never before and never after wrote Internet Drafts to get familiar with all the details. If we think RFC 4288 has failed, we should fix it. (I for my part don't think it has failed, at least not in this respect.) Also, while the above solves the "find the Statement" problem, it won't avoid the problem that outsiders get told different things at different stages: First, they get told to follow RFC 4288 (or they might even find it themselves), then once they are through review on ietf-types, they get told something else. And the above "it would be helpful" still doesn't answer the question why. The assumption from non-IESG people including me is that the main or only reason is because the datatracker can only handle IDs. It would be helpful (sic) if you and Alex could be clear and frank about this. Regards, Martin. -- #-# Martin J. Dürst, Professor, Aoyama Gakuin University #-# http://www.sw.it.aoyama.ac.jp mailto:duerst@it.aoyama.ac.jp
- [apps-discuss] Possible IESG statement on IESG pr… Alexey Melnikov
- Re: [apps-discuss] Possible IESG statement on IES… Bjoern Hoehrmann
- Re: [apps-discuss] Possible IESG statement on IES… Martin J. Dürst
- Re: [apps-discuss] Possible IESG statement on IES… SM
- Re: [apps-discuss] Possible IESG statement on IES… Ted Hardie
- Re: [apps-discuss] Possible IESG statement on IES… Peter Saint-Andre
- Re: [apps-discuss] Possible IESG statement on IES… Martin J. Dürst
- Re: [apps-discuss] Possible IESG statement on IES… Alexey Melnikov
- Re: [apps-discuss] Possible IESG statement on IES… Bjoern Hoehrmann
- Re: [apps-discuss] Possible IESG statement on IES… Larry Masinter
- Re: [apps-discuss] Possible IESG statement on IES… Alexey Melnikov