Re: [apps-discuss] On "supporting the publication of this document" (was: Re: We have no lambs (was: Applicability Statements))

SM <sm@resistor.net> Thu, 12 May 2011 17:38 UTC

Return-Path: <sm@resistor.net>
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 1EF35E0767 for <apps-discuss@ietfa.amsl.com>; Thu, 12 May 2011 10:38:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, 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 YPUa26F8pnqT for <apps-discuss@ietfa.amsl.com>; Thu, 12 May 2011 10:38:28 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 82F6BE0758 for <apps-discuss@ietf.org>; Thu, 12 May 2011 10:38:27 -0700 (PDT)
Received: from subman.resistor.net (IDENT:sm@localhost [127.0.0.1]) by mx.elandsys.com (8.14.4/8.14.5.Beta0) with ESMTP id p4CHcHNf011651; Thu, 12 May 2011 10:38:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1305221904; bh=zqBY0s01W51uVoIJfX7UIj4wGfb7uyP1cKqGn5mpWmk=; h=Message-Id:X-Mailer:Date:To:From:Subject:Cc:In-Reply-To: References:Mime-Version:Content-Type; b=QZXh2XZVV/VSBrBhLQklm3ri3YpQdyn8ufRlCLv5NzthMbI24LF8D/qsNEpL3fZok xaAQt9WpF/JV43rkPh45yiJq32XAz7XkMl/BuaVr1QUcIk5kpEeGqRNcPQv9bASb9S ZC0HeaRSMu3pynGY+Jz6+LJBi8y6PD7wgz6juZPg=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1305221904; bh=zqBY0s01W51uVoIJfX7UIj4wGfb7uyP1cKqGn5mpWmk=; h=Message-Id:X-Mailer:Date:To:From:Subject:Cc:In-Reply-To: References:Mime-Version:Content-Type; b=vjeJVrEfb6nGjMk7YrjlHuB15C4ttUEYm4fQcz4H7seaWjTY+5WEpZuxB8ftiqUl/ 7LXggjHSIDeISjoGkM24Am3JxxmKNLM5xzRHo9t5pG15JpgQaJtJECeXCvuE7dvn37 mN//ubYit7OMY7uIzKoWm1szYuch18UtlRZMRu7w=
Message-Id: <6.2.5.6.2.20110512084206.048c5280@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 12 May 2011 10:08:05 -0700
To: John C Klensin <john-ietf@jck.com>
From: SM <sm@resistor.net>
In-Reply-To: <35CAD4FD66C1EDA5E82D49F8@PST.JCK.COM>
References: <4DCAC1CB.3050905@qualcomm.com> <6.2.5.6.2.20110511115259.051cd3f8@resistor.net> <4DCAF61F.10000@qualcomm.com> <6.2.5.6.2.20110511141027.032dd408@resistor.net> <35CAD4FD66C1EDA5E82D49F8@PST.JCK.COM>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Cc: Apps Discuss <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] On "supporting the publication of this document" (was: Re: We have no lambs (was: Applicability Statements))
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: Thu, 12 May 2011 17:38:32 -0000

Hi John,
At 07:20 12-05-2011, John C Klensin wrote:
>I think you may have missed my point, although the style I adopt
>in the IETF rarely results in my being accused of saying things
>to be politically correct.  :-)

I was commenting on the two different angles.  I should not have used 
"politically correct" as it is an incorrect description.

>The determination the IESG needs to make is multidimensional.
>There is no agreed-upon statement of the dimensions, but I would
>try the following as components.  They should require different
>levels of certainty at different maturity levels, e.g., for
>Proposed Standard, "no known technical defects" is supposed to
>be adequate while, for higher levels, there should be some
>conviction that no such defects exist, not merely that no one
>has noticed.

Agreed.

[snip]

>(4) Do enough people in the community care about this spec that
>the IETF should put its stamp of approval on it?
>
>A "I think this is ok and should be published" statement may be
>very useful for (4), especially for non-WG documents.   One
>important characteristic of (4) is that the IESG actually does
>have to count, even if the counting process doesn't correspond
>to normal arithmetic.  For (1)-(3) high-information-content
>technical arguments are important, especially if they take a
>"don't publish" or "don't publish without..." position.  And, at
>least in theory, there is no counting at all -- it doesn't make
>any difference if a particular technical position is stated by
>one person or by five (whether explicitly or by "+1"
>endorsement): the issue should be the contents of that position.

I'll say yes to the above without going into the details.  As a 
comment on the "+1", I'll refer to Ted Hardie's comment about "context" [1].

[snip]

>I think the only thing that is unusual about Pete's approach is
>that he is trying to be explicit about the criteria he is going
>to use to evaluate and weight comments.  I think that is A Good
>Thing, but I don't think the criteria he suggests are in any way
>new or unusual.

My comment was not about the criteria; it was more about posting a 
message about the thinking.  It is not always an easy decision for 
the individual making the determination.  Should the person be open 
about how he or she will make the decision?  There are two choices:

  (i)  Stick to text from BCPs when making public statements and not voicing
       out any thoughts that might be misconstrued as bias.

  (ii) Be candid about likes and dislikes while being able to overcome the
       dislikes to avoid being biased.

The first option leaves people to second guess what the person might 
decide.  It is the favored option and it leaves less room for people 
to object to the decision.  The second option is interesting; people 
can come up and say "excuse me, you may have overlooked the '+1' 
posted by person X who is not a well-known suspect.  Person X is 
working on this specification".

If the community prefers to have ADs who have made it through Swiss 
finishing school, it won't see statements of support such as the 
"Walled Garden Standard" [2].

Regards,
-sm

1. http://www.ietf.org/mail-archive/web/apps-discuss/current/msg02580.html
2. http://www.ietf.org/mail-archive/web/ietf/current/msg50789.html