Re: [apps-discuss] On "supporting the publication of this document"

Alexey Melnikov <alexey.melnikov@isode.com> Wed, 11 May 2011 17:01 UTC

Return-Path: <alexey.melnikov@isode.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 D6C6FE0864 for <apps-discuss@ietfa.amsl.com>; Wed, 11 May 2011 10:01:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.166
X-Spam-Level:
X-Spam-Status: No, score=-102.166 tagged_above=-999 required=5 tests=[AWL=0.433, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D56Aok14DACC for <apps-discuss@ietfa.amsl.com>; Wed, 11 May 2011 10:01:10 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by ietfa.amsl.com (Postfix) with ESMTP id 2692CE0819 for <apps-discuss@ietf.org>; Wed, 11 May 2011 10:01:09 -0700 (PDT)
Received: from [192.168.1.124] ((unknown) [62.3.217.253]) by rufus.isode.com (submission channel) via TCP with ESMTPA id <TcrA0gBRc7SO@rufus.isode.com>; Wed, 11 May 2011 18:01:08 +0100
X-SMTP-Protocol-Errors: NORDNS
Message-ID: <4DCAC0AC.80001@isode.com>
Date: Wed, 11 May 2011 18:00:28 +0100
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: dcrocker@bbiw.net
References: <4DC88255.3070403@qualcomm.com> <4DC94F74.30905@dcrocker.net> <4DC9A9B9.3010702@stpeter.im> <4DCAAAB9.3080702@dcrocker.net>
In-Reply-To: <4DCAAAB9.3080702@dcrocker.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: Pete Resnick <presnick@qualcomm.com>, apps-discuss@ietf.org
Subject: Re: [apps-discuss] On "supporting the publication of this document"
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: Wed, 11 May 2011 17:01:10 -0000

Dave CROCKER wrote:

> On 5/10/2011 2:10 PM, Peter Saint-Andre wrote:
>
>> On 5/10/11 8:45 AM, Dave CROCKER wrote:
>>
>>> Your note suggests that, at the least, the text of a Last Call 
>>> should make
>>> much more clear what sorts of comments are being sought (and why and
>>> probably from whom.)  The community should not have to guess what 
>>> sorts of
>>> responses are useful for the IESG.
>>
>> FWIW, over in the XMPP Standards Foundation (xmpp.org) we ask the 
>> following
>> questions in each of our Last Call announcements:
>
> It has the considerable benefit of guiding the respondent to provide 
> pragmatic
> detail.
>
> The IETF would do well to include some form of similar guidance in its 
> Last Call
> announcement.

+1.

> On 5/10/2011 6:15 PM, Barry Leiba wrote:
>
>>>> #    Please consider the following questions during this Last Call 
>>>> and #
>>>> send your feedback to the standards@xmpp.org discussion list: # 
>>>> #    1.
>>>> Is this specification needed to fill gaps in the XMPP #       protocol
>>>> stack or to clarify an existing protocol? #    2. Does the 
>>>> specification
>>>> solve the problem stated in the #       introduction and 
>>>> requirements? #
>>>> 3. Do you plan to implement this specification in your code? 
>>>> #       If
>>>> not, why not? #    4. Do you have any security concerns related to 
>>>> this
>>>> specification? #    5. Is the specification accurate and clearly
>>>> written?
>>>>
>>>> Whether that's the right set of questions is another issue...
>>>
>>> This, and especially that last one, makes it sound like a PROTO 
>>> write-up.
>>> Are you sure you want that from a potentially huge list of people?
>>
>> Interesting: I think the last question is the *most* important, and 
>> the one
>> that *least* seems like it came out of a PROTO write-up.  Yes, that's 
>> the
>> question I *do* most want to see *all* reviews answer.
>
> Whereas I think each of these questions is quite important, with the 
> last one
> likely to get the most pro-forma responses, since it is the most 
> difficult to
> answer knowledgeably.

+1.