Re: [apps-discuss] New appsawg documents
Barry Leiba <barryleiba@computer.org> Wed, 31 August 2011 17:25 UTC
Return-Path: <barryleiba@gmail.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 403A721F8DD2 for <apps-discuss@ietfa.amsl.com>; Wed, 31 Aug 2011 10:25:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.026
X-Spam-Level:
X-Spam-Status: No, score=-103.026 tagged_above=-999 required=5 tests=[AWL=-0.049, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id InKvqC2im8wx for <apps-discuss@ietfa.amsl.com>; Wed, 31 Aug 2011 10:25:49 -0700 (PDT)
Received: from mail-yi0-f44.google.com (mail-yi0-f44.google.com [209.85.218.44]) by ietfa.amsl.com (Postfix) with ESMTP id 9961221F8DCD for <apps-discuss@ietf.org>; Wed, 31 Aug 2011 10:25:49 -0700 (PDT)
Received: by yie12 with SMTP id 12so947026yie.31 for <apps-discuss@ietf.org>; Wed, 31 Aug 2011 10:27:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=Ufcjv+CbGAC76aIBeBb48Kr7VOH9wrOmTnwbDl1Bevs=; b=s1M/FH9vnn4a4dUkMnlfnkH5aM1G2uvPk78Nfj2AnlYDjO+LBOZm+bCY4volRi04Qo cnkpkL4czsl9H3vslC/po9ch1Pg0l21tEIvqrydqq45EWdvmgvPcOsdD3KA02QJ11u5M WXFytDSQBbv8aSeb/X39AvbEk9qPnN2oab4AI=
MIME-Version: 1.0
Received: by 10.236.72.233 with SMTP id t69mr3672517yhd.55.1314811639374; Wed, 31 Aug 2011 10:27:19 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.236.208.35 with HTTP; Wed, 31 Aug 2011 10:27:19 -0700 (PDT)
In-Reply-To: <008301cc67f8$43bb4b00$4001a8c0@gateway.2wire.net>
References: <CALaySJKw3zwR-Joxm8oBi8Y6b4E0zq5r5HbNGykDaotVTdGeXQ@mail.gmail.com> <004001cc6736$d4baab40$4001a8c0@gateway.2wire.net> <CALaySJKkFht1k8Bux+d3jULBrzhwgx2uUu1fGX4TYVPewFKM5g@mail.gmail.com> <CALaySJ+1NhpqEAMOkRpKT5OOsL4-Z+CG9VHYdOrLdVJkNbcR=A@mail.gmail.com> <008301cc67f8$43bb4b00$4001a8c0@gateway.2wire.net>
Date: Wed, 31 Aug 2011 13:27:19 -0400
X-Google-Sender-Auth: btXBvlNW17dZ5hQYsM5hPpj034A
Message-ID: <CALaySJLSWaBRFSJW85vDFq=5woTwURcwX3T7X1iNHPQRReCv-Q@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: "t.petch" <ietfc@btconnect.com>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: Apps Discuss <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] New appsawg documents
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, 31 Aug 2011 17:25:50 -0000
> I want the process of producing an RFC to be challenging, to demonstrate > that there is support for this as an RFC and that there has been adequate > review. Asking for approval for seven I-Ds in three days does limit the > likely review, and indeed, I see that one I-D has already progressed > before even those three days are up, but I am not suggesting you extend it. Maybe you misunderstand the note that started this. No one has asked for approval for *any* documents. We've asked to hear objections to having the working group *process* the documents. They still all have to get review and go through the same process they would have gone through as individual submissions -- but with *more* oversight and attention. How do you think that will cheapen the process? We're also not handling seven at the same time. My note said that we'd focus on three first, and each of those will progress at its own pace. And be assured that any documents that have insufficient review and support will not make it to the ADs. That some have already "progressed" just means that we've given them working-group names. If the working group decides not to handle any document, either by explicit decision or by neglect and lack of support, that document can still fail. Further, most of these documents have already had significant review, comment, and discussion, some on this list and some elsewhere. I'd really prefer to see effort put into discussion of the documents, rather than into meta-discussion of the working group. If, in the end, someone thinks that a document either got a "free pass" by being handled by the working group, or got mired in process that it would have avoided as an individual submission, we'd all like to hear about it then. If it turns out that this working group isn't helping to do things right, we can and will shut it down. Barry
- [apps-discuss] New appsawg documents Barry Leiba
- Re: [apps-discuss] New appsawg documents Mykyta Yevstifeyev
- Re: [apps-discuss] New appsawg documents Barry Leiba
- Re: [apps-discuss] New appsawg documents t.petch
- Re: [apps-discuss] New appsawg documents Murray S. Kucherawy
- Re: [apps-discuss] New appsawg documents Barry Leiba
- Re: [apps-discuss] New appsawg documents Peter Saint-Andre
- Re: [apps-discuss] New appsawg documents Barry Leiba
- Re: [apps-discuss] New appsawg documents t.petch
- Re: [apps-discuss] New appsawg documents Alexey Melnikov
- Re: [apps-discuss] New appsawg documents Barry Leiba
- Re: [apps-discuss] New appsawg documents t.petch
- Re: [apps-discuss] New appsawg documents Jiankang Yao