Return-Path: Received: from murder ([unix socket]) by eikenes.alvestrand.no (Cyrus v2.2.8-Mandrake-RPM-2.2.8-4.2.101mdk) with LMTPA; Sat, 20 Aug 2005 10:19:40 +0200 X-Sieve: CMU Sieve 2.2 Received: from localhost (eikenes.alvestrand.no [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 9AF9C320084 for ; Sat, 20 Aug 2005 10:19:40 +0200 (CEST) Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 28523-07 for ; Sat, 20 Aug 2005 10:19:35 +0200 (CEST) X-Greylist: domain auto-whitelisted by SQLgrey-1.4.8 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by eikenes.alvestrand.no (Postfix) with ESMTP id 3B17832007B for ; Sat, 20 Aug 2005 10:19:31 +0200 (CEST) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E6ORL-0007S1-Ib; Sat, 20 Aug 2005 04:10:55 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E6ORG-0007Rk-15 for ietf@megatron.ietf.org; Sat, 20 Aug 2005 04:10:52 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA10669 for ; Sat, 20 Aug 2005 04:10:48 -0400 (EDT) Received: from montage.altserver.com ([63.247.74.122]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E6P1N-0006Zk-Eq for ietf@ietf.org; Sat, 20 Aug 2005 04:48:09 -0400 Received: from ver78-2-82-241-91-24.fbx.proxad.net ([82.241.91.24] helo=jfc.afrac.org) by montage.altserver.com with esmtpa (Exim 4.44) id 1E6OR1-0002ya-1t; Sat, 20 Aug 2005 01:10:35 -0700 Message-Id: <6.2.3.4.2.20050820100847.03cccc80@mail.jefsey.com> X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.4 Date: Sat, 20 Aug 2005 10:10:28 +0200 To: Brian E Carpenter From: "JFC (Jefsey) Morfin" In-Reply-To: <4305E914.1020300@zurich.ibm.com> References: <6.2.1.2.2.20050818101910.0373feb0@mail.jefsey.com> <4305E914.1020300@zurich.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - montage.altserver.com X-AntiAbuse: Original Domain - ietf.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - jefsey.com X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135 Cc: dmm@1-4-5.net, ietf@ietf.org, henrik@levkowetz.com Subject: Re: is the WG-Charter concept changed? X-BeenThere: ietf@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF-Discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: ietf-bounces@ietf.org Errors-To: ietf-bounces@ietf.org X-Virus-Scanned: by amavisd-new at alvestrand.no At 16:13 19/08/2005, Brian E Carpenter wrote: >JFC (Jefsey) Morfin wrote: >>http://www.ietf.org/internet-drafts/draft-ietf-proto-wgchair-doc-shepherding-05.txt >> >>The Draft above seems already to be used in some areas to rule a >>procedure to decrease the AD's working load and to speed up the >>reviewing process. It gives more importance to the WG Chair's personal opinion, > >No, it does not do that - it moves some procedural responsibility to >the PROTO shepherd, but it doesn't change either the WG Chair's duty >to judge WG consensus or the AD's responsibility to review the draft >for the IESG. Sorry, Brian - you comment but you do not respond. 1. comment: yes it gives more importance to the WG Chair's personal opinion (but this is not a problem if this is consistently organised): (1) due to the load on ADs, this may lead to more delegation of the AD to the Shepherding Chair, however the Chair has more time: this is no problem if the WG knows the report (AD delegates to Chair who writes and can less review, Chair is to delegate part of the reviewing to WG). (2) the opinion of the Chair becomes the reference in the questionnaire, no more the Charter the Draft overlooks. 2. question: is the Charter still the reference when reporting to the IESG? If no this is a big change in the IETF. If yes, then this must translate into the reporting questionnaire. At least in asking the way the Charter has been respected in all technical inclusiveness. You cannot say something is the reference to follow, and not even allude to it in the execution reporting questionnaire. jfc > Brian > > what may have cons and pros. I thought the WG Chair decides of >>rough consensus and if the WG deliverables are ready in reference >>to the Charter, the "contract" between the IETF/IESG/IAB community >>and the WG. Am I wrong or is this changed ? >>The word "Charter" is not even used in this Draft. The decisions >>and comments sent to the IESG are therefore subject to the WG >>Chair's position and not to the IESG requirements. I suggested the >>authors the following two additions (tentative text provided). I >>have not received a response yet while I face a case where this >>point is important and urgent. >>1. The first addition is that the proposed write-ups are presented >>for quick comments to the WG. >>2. two questions more are added, one on the way the Charter has >>been respected, one on the care given not to favor one technical >>vision over others (one might refer to RFC 3869). I suppose >>competition in a WG is not between propositions but for the best >>user needs support? >>jfc >> >>_______________________________________________ >>Ietf mailing list >>Ietf@ietf.org >>https://www1.ietf.org/mailman/listinfo/ietf > > >_______________________________________________ >Ietf mailing list >Ietf@ietf.org >https://www1.ietf.org/mailman/listinfo/ietf > _______________________________________________ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf