Re: Last Call: <draft-secretaries-good-practices-06.txt> (IETF Working Groups' Secretaries) to Best Current Practice

S Moonesamy <sm+ietf@elandsys.com> Thu, 12 June 2014 18:55 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE7AC1A023A for <ietf@ietfa.amsl.com>; Thu, 12 Jun 2014 11:55:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.651
X-Spam-Level:
X-Spam-Status: No, score=-2.651 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.651] 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 FORc29XgIs5K for <ietf@ietfa.amsl.com>; Thu, 12 Jun 2014 11:55:46 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 583061A0236 for <ietf@ietf.org>; Thu, 12 Jun 2014 11:55:46 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.150.25]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s5CItWEr019840 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 12 Jun 2014 11:55:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1402599344; x=1402685744; bh=pfmZYa+oyawQlaSDpfW8WX769LbpKGlEFwKkVxDVBdw=; h=Date:To:From:Subject:In-Reply-To:References; b=AXr8b0d5EBRscz1RxoPvGZKY7HD9HFseSI87MCy63M2DZyuUpq2fSXSZ/fJ8Du5Fz pnf1yzs/5qZPaSFRJ2REJZ9r00n2p9FcGqZLWmGdN7i40SM+plEuUq12ziHSeJgtHx EIwARLNKYhFKrDeXKU6Fd094Av2V0zfNYfkzhBrU=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1402599344; x=1402685744; i=@elandsys.com; bh=pfmZYa+oyawQlaSDpfW8WX769LbpKGlEFwKkVxDVBdw=; h=Date:To:From:Subject:In-Reply-To:References; b=Hdy1rZfJQzSkxgeUytu+XUuFz2Do3lUt3RbpY2Hm6WXiQn22C70ZdmfTCUmkyrJtQ 6Yc3dNl2Eju5jEqbtYiSjX3Mn0bFHF8YFnqtv/ga9CnIepuvFLQXL1HGUmx6qoCHQN yIoMQkZw9hiqI5qrMVTefpqAKr6Mo7LV+qxhu0ms=
Message-Id: <6.2.5.6.2.20140612102110.0e4fa980@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 12 Jun 2014 11:34:25 -0700
To: ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Last Call: <draft-secretaries-good-practices-06.txt> (IETF Working Groups' Secretaries) to Best Current Practice
In-Reply-To: <20140612132656.8100.57197.idtracker@ietfa.amsl.com>
References: <20140612132656.8100.57197.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Iyfs9Ejl9-bJRyOzJQA7rdQSiio
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jun 2014 18:55:48 -0000

At 06:26 12-06-2014, The IESG wrote:
>The IESG has received a request from an individual submitter to consider
>the following document:
>- 'IETF Working Groups' Secretaries'
>   <draft-secretaries-good-practices-06.txt> as Best Current Practice
>
>The IESG plans to make a decision in the next few weeks, and solicits
>final comments on this action. Please send substantive comments to the
>ietf@ietf.org mailing lists by 2014-07-10. Exceptionally, comments may be

I would give credit the anonymous reviewer who pointed this out.  A 
Working Group Chair has the responsibility to make decisions on 
behalf of the working group.  There are times where one or more 
participants disagree with a decision which was taken.  The question 
of who is responsible comes into play if the WG Secretary took the 
decision.  There is the word "responsibility" in the heading of 
Section 3 of the draft.  I suggest avoiding that word in the draft as 
I don't think it is okay to blame the WG Secretary for process 
issues.  Some people may consider that it is fair game to do that.  I 
suggest also reviewing the usage of the word "accountable".

In Section 3.1.1:

   "Note that WG Chairs may wish to set policies for accepting
    discussion's slot requests."

I suggest using the word "guidelines" instead of "policies".

Section 3.2 uses the term "WG document's adoption polls".  I suggest 
avoiding the word "polls" as it sounds like voting.

   "Decisions are sometimes taken by WG Chairs during WG sessions."

It has been said that decisions are taken on the mailing list.  The 
above can be a problem when BCP 25 is invoked.

I would like to thank the authors for putting the effort in doing this work.

Regards,
S. Moonesamy