Re: Lisa's Apps Area Activity for August 2007

Dave Crocker <dhc@dcrocker.net> Tue, 04 September 2007 21:47 UTC

Return-path: <discuss-bounces@apps.ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1ISgEw-0004Im-Uz; Tue, 04 Sep 2007 17:47:18 -0400
Received: from discuss by megatron.ietf.org with local (Exim 4.43) id 1ISgEv-0004Ic-Kd for discuss-confirm+ok@megatron.ietf.org; Tue, 04 Sep 2007 17:47:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1ISgEv-0004IU-BA for discuss@apps.ietf.org; Tue, 04 Sep 2007 17:47:17 -0400
Received: from mail.songbird.com ([208.184.79.10]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ISgEt-0006CD-T2 for discuss@apps.ietf.org; Tue, 04 Sep 2007 17:47:17 -0400
Received: from [192.168.0.6] (adsl-67-124-150-100.dsl.pltn13.pacbell.net [67.124.150.100]) (authenticated bits=0) by mail.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id l84Lkv67018411 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 4 Sep 2007 14:46:58 -0700
Message-ID: <46DDD1E0.6040304@dcrocker.net>
Date: Tue, 04 Sep 2007 14:45:04 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Lisa Dusseault <lisa@osafoundation.org>
Subject: Re: Lisa's Apps Area Activity for August 2007
X-Priority: 2 (High)
References: <58F2EB70-4A11-4C0B-B517-A782520A6EDB@osafoundation.org>
In-Reply-To: <58F2EB70-4A11-4C0B-B517-A782520A6EDB@osafoundation.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Cc: Apps Discuss <discuss@apps.ietf.org>, Lisa Dusseault's Chairs <lisa-dusseault-chairs@tools.ietf.org>, iesg <iesg@ietf.org>
X-BeenThere: discuss@apps.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: general discussion of application-layer protocols <discuss.apps.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=unsubscribe>
List-Post: <mailto:discuss@apps.ietf.org>
List-Help: <mailto:discuss-request@apps.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=subscribe>
Errors-To: discuss-bounces@apps.ietf.org


Lisa Dusseault wrote:
>  - draft-crocker-rfc4234bis: Finished IESG Evaluation, waiting for 
> author to resolve LWSP issue raised in IETF Last Call and IESG 
> Evaluation (Dave or Paul)


The document authors have a number of problems with this Discuss from Lisa and 
efforts to clarify things privately have not been productive.

Since this is being distributed publicly, I am obligated to comment on it:

Simply put, there is not "LWSP issue".  The ABNF document has been in use a 
very long time and is formally accurate in in specification.  Over its 10+ 
year history, there have been a few examples of misreading the ABNF 
specification.  If that qualifies as a basis for mandating change, then we 
need to review quite a few other specifications.

In any event, there is a Discuss from Lisa that has stalled progress of the 
ABNF document, but the Discuss causes its own problems:

One is that we do not perceive any community consensus that any change -- 
nevermind no normative change -- is required for the document. At most, there 
might be some community interest in having commentary added, but that leads to 
the next problem.

We do not have any idea what will resolve Lisa's Discuss.  Lisa has provided 
no criteria for its closure, other than suggesting that we talk with one 
individual.  We are not aware the mere act of being vocal about an issue 
empowers a single community member to control resolution of a Discuss.  In 
effect, that would seem to be a delegation of the Discuss. Is that allowed?

If Lisa has requirements on this topic, she needs to state what they are in 
terms of her own understandings and requirements, not in terms of the 
unspecified needs of another.  We should remember that this is an extremely 
well-vetted document, both in long history and recent review.

Since the document's authors do not believe that the current process issues 
will alter the use of ABNF, we do not have much incentive to spend energy on 
the issue.  (A sour grapes muttering in response might claim that my writing 
this note -- and it is perhaps the third of its type I've send on the topic -- 
is more work than resolving the topic, but I'll note that that cannot be 
known, since there is now way of knowing what will resolve it.)

Lisa has stated that her Discuss really is on behalf of an IESG consensus that 
some text needs to be added.  Perhaps I missed the IESG minutes about this 
consensus?  It would be useful to get a citation to it.

In any event, if the IESG has consensus about the need to added commentary to 
an RFC before it is published, then this is an IESG requirement, not an IESG 
assessment of a community consensus.  Further there is a well-established and 
frequently-used mechanism for it.  IESG Notes are not exactly... noteworthy.

And for reference, the document authors have repeatedly stated their friendly 
willingness to add such text.  Or text that is produced by a community 
consensus process.  But since we do not, ourselves, understand what will 
satisfy Lisa in this matter, we do not feel qualified to lead the effort to 
resolve it.

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net