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

John C Klensin <john-ietf@jck.com> Thu, 27 January 2011 18:21 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: apps-review@core3.amsl.com
Delivered-To: apps-review@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 74D2B28C151 for <apps-review@core3.amsl.com>; Thu, 27 Jan 2011 10:21:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.988
X-Spam-Level:
X-Spam-Status: No, score=-102.988 tagged_above=-999 required=5 tests=[AWL=-0.389, 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 OshYInj+Etr0 for <apps-review@core3.amsl.com>; Thu, 27 Jan 2011 10:21:39 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 4A4F83A69C4 for <apps-review@ietf.org>; Thu, 27 Jan 2011 10:21:39 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PiWWM-0006eX-UX; Thu, 27 Jan 2011 13:24:39 -0500
Date: Thu, 27 Jan 2011 13:24:38 -0500
From: John C Klensin <john-ietf@jck.com>
To: SM <sm+ietf@elandsys.com>
Message-ID: <3E41020AED91D0D06F9F8851@PST.JCK.COM>
In-Reply-To: <6.2.5.6.2.20110127010602.0b515078@elandnews.com>
References: <AANLkTikaHw7GKiAn1B4Uu5sytyzmi97ExejzfDT82UzO@mail.gmail.com> <6.2.5.6.2.20110126212046.0c26cae8@resistor.net> <5869A181BE49612A2C0C7836@PST.JCK.COM> <6.2.5.6.2.20110127010602.0b515078@elandnews.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Mailman-Approved-At: Fri, 28 Jan 2011 08:09:28 -0800
Cc: apps-review@ietf.org
Subject: Re: [apps-review] Feeling kind of confused about draft-merrick-jms-uri-12
X-BeenThere: apps-review@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Apps Area Review List <apps-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-review>, <mailto:apps-review-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-review>
List-Post: <mailto:apps-review@ietf.org>
List-Help: <mailto:apps-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-review>, <mailto:apps-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jan 2011 18:21:40 -0000

--On Thursday, January 27, 2011 09:44 -0800 SM
<sm+ietf@elandsys.com> wrote:

> Hi John,
> 
> [following up on apps-review]
> 
> At 23:20 26-01-11, John C Klensin wrote:
>> Remember too that, as Mark has already pointed out in a
>> different way, the main point of a provisional registration is
>> to lower the odds that the same protocol identifier string
>> will be used to designate two different protocols.
> 
> Mark and you have commented on this case.  There was a comment
> from Larry (
> http://www.ietf.org/mail-archive/web/apps-discuss/current/msg0
> 2096.html ).
> 
>> I am not advising this in any way and I personally don't think
>> it would be worth the effort, but, in the interest of
>> procedural knowledge and consistency, RFC 2026 does give
>> anyone who feels strongly about this decision the right to
>> appeal it.
> 
> I suggest talking to the Apps Area Directors before taking
> that path.

Talking with the Apps Area Directors is the first (and normally
last) step on that path.  The difference is only the level of
formality.  Remember that the purpose of the IETF Appeals model
is to get a careful second look at areas of disagreement and to
attempt to see if agreement can be reached, not to initiate or
proceed with a judicial function of any sort.

> When a request for review come from the Apps Area Directors, I
> pick a reviewer for the assignment.  There was a case where
> the document was over 300 pages and there was a short
>...
> It has been difficult to get all the reviews done.  I value
> the contributions made by Tim and all members of the team.  I
> may voice my discontent to the Apps Area ADs if a reviewer
> mentions that his/her work is not given any consideration.

I don't believe that anything improper has occurred in the
review process or even in the IESG decision.   I appreciate your
review of the history.

I do believe that, if people feel strongly that accepting the
document and registration was a seriously bad idea, even after
they are sure they understand the nature of a provisional
registration, then they should try to understand the IESG's
reasoning from the Apps ADs and/or ask that the decision be
reviewed.

It would also be quite reasonable for people who find themselves
in that position to request additional text -- in a revised
announcement statement, in the registry, or in the document as
it will be published -- to suggest that.  Whether that could be
negotiated with the Apps ADs or required a formal appeal would
be up to the ADs and the IESG.

I am not personally convinced that either trying to get a
different decision or trying to get more clear disclaimers or
warnings into the text would be worthwhile.  But the IETF is
periodically accused of having procedures that work only for
those who know how to use them and I periodically feel an
obligation to explain possibly-useful procedures to those whose
only other recourse would be whining and/or ranting.

    john