Re: [apps-discuss] Objection to processing draft-ietf-appsawg-text-markdown-* documents as WG drafts (was: Re: Benoit Claise's Discuss on draft-ietf-appsawg-text-markdown-use-cases-02: (with DISCUSS and COMMENT))

Dave Crocker <dhc@dcrocker.net> Mon, 13 July 2015 04:43 UTC

Return-Path: <dhc@dcrocker.net>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 375C01A90C8; Sun, 12 Jul 2015 21:43:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ribBt8TxrmNd; Sun, 12 Jul 2015 21:43:45 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 29A2E1A903E; Sun, 12 Jul 2015 21:43:45 -0700 (PDT)
Received: from [192.168.1.87] (76-218-10-206.lightspeed.sntcca.sbcglobal.net [76.218.10.206]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id t6D4hUmj031862 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sun, 12 Jul 2015 21:43:35 -0700
Message-ID: <55A341EE.8000904@dcrocker.net>
Date: Sun, 12 Jul 2015 21:43:26 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>, The IESG <iesg@ietf.org>
References: <BC704810D276B2B3DD5EFBAE@JcK-HP8200.jck.com>
In-Reply-To: <BC704810D276B2B3DD5EFBAE@JcK-HP8200.jck.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Sun, 12 Jul 2015 21:43:44 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/apps-discuss/y6NGhpeF2QB5v8PxgGjAjmtLgw0>
Cc: appsawg-chairs@ietf.org, apps-discuss@ietf.org
Subject: Re: [apps-discuss] Objection to processing draft-ietf-appsawg-text-markdown-* documents as WG drafts (was: Re: Benoit Claise's Discuss on draft-ietf-appsawg-text-markdown-use-cases-02: (with DISCUSS and COMMENT))
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
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: <https://mailarchive.ietf.org/arch/browse/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: Mon, 13 Jul 2015 04:43:46 -0000

On 7/12/2015 4:20 PM, John C Klensin wrote:
> The kinds of problematic text (and a few actual
> errors) that are being found during and subsequent to IETF Last
> Call suggests strongly that the WG process failed to do an
> adequate review from several perspectives. 


John,

I'm confused.  You appear to be saying that it is exceptional for a
working group process to turn out documents for IESG processing that are
seriously flawed.  In contrast I believe it is a periodic occurrence
across all areas and all working groups, and arguably always has been.

While crappy drafts really are problematic, I do not understand what was
supposedly exceptional in the AppsArea wg process that distinguishes it
from various other working groups around the IETF over the years,
including these days.

In any event, absent very specific citations from you, that point to
actions that need to have been done differently, there is no way to know
what problems to correct, or requirements to impose, for this wg or any
other.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net