Re: [apps-discuss] Feeling kind of confused about draft-merrick-jms-uri-12

Alexey Melnikov <alexey.melnikov@isode.com> Sun, 30 January 2011 14:12 UTC

Return-Path: <alexey.melnikov@isode.com>
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 37E613A67F9 for <apps-discuss@core3.amsl.com>; Sun, 30 Jan 2011 06:12:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.515
X-Spam-Level:
X-Spam-Status: No, score=-102.515 tagged_above=-999 required=5 tests=[AWL=0.084, BAYES_00=-2.599, 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 pNhVWVbROlZI for <apps-discuss@core3.amsl.com>; Sun, 30 Jan 2011 06:12:00 -0800 (PST)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id C24393A67B7 for <apps-discuss@ietf.org>; Sun, 30 Jan 2011 06:11:59 -0800 (PST)
Received: from [192.168.0.102] ((unknown) [109.73.6.25]) by rufus.isode.com (submission channel) via TCP with ESMTPA id <TUVybQADL550@rufus.isode.com>; Sun, 30 Jan 2011 14:15:10 +0000
X-SMTP-Protocol-Errors: NORDNS
Message-ID: <4D457248.2080700@isode.com>
Date: Sun, 30 Jan 2011 17:14:32 +0300
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Tim Bray <tbray@textuality.com>
References: <AANLkTikaHw7GKiAn1B4Uu5sytyzmi97ExejzfDT82UzO@mail.gmail.com>
In-Reply-To: <AANLkTikaHw7GKiAn1B4Uu5sytyzmi97ExejzfDT82UzO@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: apps-discuss@ietf.org
Subject: Re: [apps-discuss] Feeling kind of confused about draft-merrick-jms-uri-12
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: Sun, 30 Jan 2011 14:12:01 -0000

Tim Bray wrote:

>I was asked to review it.  My review was quite negative, challenging
>the notion that a URI was even appropriate for this space, and
>pointing out some fairly serious problems with the text.
>
Ok, I think there were some process failures on my side. I was keen to 
get this document finished before my AD term ends at the beginning of 
April, version -11 of the document was posted close to the IESG telechat 
date and I didn't follow up on your detailed comments. I did read your 
comments and from a quick look it seemed that most of your minor issues 
were addressed, while I didn't think your major issue were blocking 
publication. So my apologies for not communicating anything back to you.

I have replied to your original review and I hope you find my answers 
satisfactory.

Now, commenting on some specific issues:

>I'd have expected at least another draft.
>
I believe -11 was posted to address some of your concerns. My reading of 
changes in draft-merrick-jms-uri-11.txt is that editors addressed pretty 
much all your minor issues and nits. I apologize again for not replying 
to your major issues and not insisting that editors do, but I hope my 
replies in additional message explain why I thought that these issues 
are not worth blocking the document for.

Having said that, if you think some specific editorial changes can 
improve the document, I would be very interested to hear and apply them 
in AUTH48. If the changes are sufficiently major, I will ask IESG and 
the community to verify that they are acceptable.

>Today, the IESG announces that that
>draft, with one small change, is being published as an Informational
>RFC.
>
>So, what is the purpose of doing apps-area reviews, given that this
>one produced no observable effects?
>
There was lack of acknowledgment of your review from my side, but in 
general I don't think I agree with your statement.

My understanding of how Apps Review Team should work is that it provides 
additional reviews and information to Applications AD (and the rest of 
IESG) about suitability of publications and quality of documents. This 
is similar to SecDir (Security Area reviews) and Gen-Art (General Area 
reviews). None of them are supposed to be treated more than general IETF 
LC comments, although in practice ADs of relevant areas are actually 
paying much more attention to them.

So, your review was treated as one input regarding the document. This 
document was also reviewed by the Designated Expert for URI 
registrations (Graham Klyne) and Mark Nottingham (another Apps Review 
Team review). While they clearly indicated that the document is not 
ready for PS, I got impression that they thought that the publication as 
Informational with Provisional URI registration is quite acceptable.

Best Regards,
Alexey

-- 
IETF Application Area Director, <http://www.ietf.org/iesg/members.html>
Internet Messaging Team Lead, <http://www.isode.com>
JID: same as my email address