Re: [Atoca] ATOCA chairs - IETF process being violated?
"Thomson, Martin" <Martin.Thomson@andrew.com> Tue, 19 October 2010 02:30 UTC
Return-Path: <Martin.Thomson@andrew.com>
X-Original-To: earlywarning@core3.amsl.com
Delivered-To: earlywarning@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4B83C3A67FA for <earlywarning@core3.amsl.com>; Mon, 18 Oct 2010 19:30:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.893
X-Spam-Level:
X-Spam-Status: No, score=-2.893 tagged_above=-999 required=5 tests=[AWL=-0.294, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PfJ7-W4L0St2 for <earlywarning@core3.amsl.com>; Mon, 18 Oct 2010 19:30:48 -0700 (PDT)
Received: from csmailgw1.commscope.com (csmailgw1.commscope.com [198.135.207.244]) by core3.amsl.com (Postfix) with ESMTP id A417E3A6A98 for <earlywarning@ietf.org>; Mon, 18 Oct 2010 19:30:47 -0700 (PDT)
Received: from [10.86.20.103] ([10.86.20.103]:33917 "EHLO ACDCE7HC2.commscope.com") by csmailgw1.commscope.com with ESMTP id S35751282Ab0JSCcR (ORCPT <rfc822; earlywarning@ietf.org>); Mon, 18 Oct 2010 21:32:17 -0500
Received: from SISPE7HC1.commscope.com (10.97.4.12) by ACDCE7HC2.commscope.com (10.86.20.103) with Microsoft SMTP Server (TLS) id 8.1.436.0; Mon, 18 Oct 2010 21:32:16 -0500
Received: from SISPE7MB1.commscope.com ([fe80::9d82:a492:85e3:a293]) by SISPE7HC1.commscope.com ([fe80::8a9:4724:f6bb:3cdf%10]) with mapi; Tue, 19 Oct 2010 10:31:58 +0800
From: "Thomson, Martin" <Martin.Thomson@andrew.com>
To: "earlywarning@ietf.org" <earlywarning@ietf.org>, "Tschofenig, Hannes (NSN - FI/Espoo)" <hannes.tschofenig@nsn.com>
Date: Tue, 19 Oct 2010 10:31:56 +0800
Thread-Topic: [Atoca] ATOCA chairs - IETF process being violated?
Thread-Index: Actu6gZ3wRTQuVGqSj2TMTrnh0ZlmwASr4cw
Message-ID: <8B0A9FCBB9832F43971E38010638454F03F31EA7D0@SISPE7MB1.commscope.com>
References: <201010181728.o9IHS2tI002635@sj-core-5.cisco.com>
In-Reply-To: <201010181728.o9IHS2tI002635@sj-core-5.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-BCN: Meridius 1000 Version 3.4 on csmailgw1.commscope.com
X-BCN-Sender: Martin.Thomson@andrew.com
Subject: Re: [Atoca] ATOCA chairs - IETF process being violated?
X-BeenThere: earlywarning@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Discussion list for the IETF Authority-to-Citizen Alert \(atoca\) working group." <earlywarning.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/earlywarning>, <mailto:earlywarning-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/earlywarning>
List-Post: <mailto:earlywarning@ietf.org>
List-Help: <mailto:earlywarning-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/earlywarning>, <mailto:earlywarning-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Oct 2010 02:30:51 -0000
Approving these drafts was a little premature. While we have milestones for work items in our charter, we hadn't formally had the discussion about accepting these as working group items. For now, let us pretend that these -ietf- versions of the drafts don't exist. To help us, can we request that the authors of these drafts submit revisions of the individual drafts? We should have a discussion about the status of these items at our meeting. If it seems like we do want to adopt these drafts, we'll do a formal 2 week call on the list straight after the meeting. If not, we'll have to see what we can do to kill off the -ietf- drafts. Cheers, Martin (and Scott), ATOCA Chairs -----Original Message----- From: earlywarning-bounces@ietf.org [mailto:earlywarning-bounces@ietf.org] On Behalf Of James M. Polk Sent: Tuesday, 19 October 2010 4:28 AM To: earlywarning@ietf.org Subject: [Atoca] ATOCA chairs - IETF process being violated? ATOCA chairs I'm personally glad this WG formed. That said, one WG item was submitted today and I can't seem to find in the list archives any call for the WG to approve of any WG level documents. The WG was announced in this message (from Aug 17th) http://www.ietf.org/mail-archive/web/earlywarning/current/msg00358.html Martin, as one of two WG chairs, you welcomed all of us to the WG Sept 1st http://www.ietf.org/mail-archive/web/earlywarning/current/msg00359.html Martin, you're initial non-welcome message (Sept 14th) talked about Beijing meeting slots http://www.ietf.org/mail-archive/web/earlywarning/current/msg00360.html and said this: " We're expecting to spend some time on the following drafts: draft-rosen-atoca-cap draft-rosen-atoca-server-discovery draft-schulzrinne-atoca-requirements " that meeting agenda thread continued until the first WG item was submitted (Sept 24th) without the WG ever having a say in whether or not this ID was good or bad to adopt http://www.ietf.org/mail-archive/web/earlywarning/current/msg00377.html The very next message to this list (Oct 1st) had a rough agenda http://www.ietf.org/mail-archive/web/earlywarning/current/msg00378.html that didn't even mention draft-ietf-atoca-cap-00.txt Now on Oct 18th, draft-ietf-atoca-cap-00.txt is submitted - again without the proper (or even a mention of) list discussion about whether this ID is a good thing for the WG to adopt or not. Common guys - we can't start the WG by willfully violating IETF WG process like this! One of the two of you (chairs) is new, so this isn't really a surprise, but one of you authored one of the core IETF process documents (RFC 2418), so there's less tolerance here. This cannot be tolerated and each of these documents need to be rescinded (i.e., taken out of the ID repository) until the WG approves them. I mean, there hasn't even been a face-to-face meeting to have voices say yes or no (hums one way or the other or ever thumbs pointed up or down). There's been nothing within this WG to justify these two IDs being WG items yet. There's still time (6.5 hours) to have each resubmitted as individual IDs and us discuss them properly in Beijing, and maybe even indicate there that these should be put to the ATOCA list for WG consideration. Before this happens, these two IDs aren't properly WG items. James _______________________________________________ earlywarning mailing list earlywarning@ietf.org https://www.ietf.org/mailman/listinfo/earlywarning
- [Atoca] ATOCA chairs - IETF process being violate… James M. Polk
- Re: [Atoca] ATOCA chairs - IETF process being vio… DRAGE, Keith (Keith)
- Re: [Atoca] ATOCA chairs - IETF process being vio… Scott O. Bradner
- Re: [Atoca] ATOCA chairs - IETF process being vio… Thomson, Martin
- Re: [Atoca] ATOCA chairs - IETF process being vio… James M. Polk