Re: Last Call: <draft-moonesamy-ietf-conduct-3184bis-03.txt> (IETF Guidelines for Conduct) to Best Current Practice
S Moonesamy <sm+ietf@elandsys.com> Fri, 08 November 2013 02:30 UTC
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C7D121E8119 for <ietf@ietfa.amsl.com>; Thu, 7 Nov 2013 18:30:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.003
X-Spam-Level:
X-Spam-Status: No, score=-103.003 tagged_above=-999 required=5 tests=[AWL=-1.473, BAYES_00=-2.599, DATE_IN_PAST_06_12=1.069, 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 oU5xujh0Y4i2 for <ietf@ietfa.amsl.com>; Thu, 7 Nov 2013 18:30:03 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id DA2A121E817C for <ietf@ietf.org>; Thu, 7 Nov 2013 18:30:02 -0800 (PST)
Received: from SUBMAN.elandsys.com ([197.224.156.231]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id rA82TgG9018091 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 7 Nov 2013 18:29:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1383877795; bh=zZEmHxOmdSSX88QfS0OL5AyLEPno/4mRkk8PxDxx9Ws=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=X+ef94no3BtJbT9u3PnvbynDPvhEmruBKj7lQm/vnOU057jRrs1QtDbh0CHW+3Ybn AUKtbaP+RY9nYYTdNQqZOTT7IbyWmqwiyDHm+q62QZbKpO82+89hocl6bJPgIEytEE 14FuNzsNOTbQkOqNhZAfqFI7+GapHDflOTZyKj08=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1383877795; i=@elandsys.com; bh=zZEmHxOmdSSX88QfS0OL5AyLEPno/4mRkk8PxDxx9Ws=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=iaGFAdo3NT503Yhx/a7n1NrX3kC+5ht1lAhpZLJYpDwdQPjgwoRsgDUFvpOyk9y5E L+iwegzMEPDZl8G6fp6Uvg1weEiKZ993p7qODSa4FJ5+rbJetMM2PrKV2k6uavDGfd n5wkLeAC9NuZOT59jgi/lTxrm+uW0Bl+gFOezwYU=
Message-Id: <6.2.5.6.2.20131107102807.0e08a668@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 07 Nov 2013 11:43:23 -0800
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Last Call: <draft-moonesamy-ietf-conduct-3184bis-03.txt> (IETF Guidelines for Conduct) to Best Current Practice
In-Reply-To: <527BD63E.1050200@gmail.com>
References: <20131103150309.1554.26103.idtracker@ietfa.amsl.com> <527BD63E.1050200@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 08 Nov 2013 02:30:04 -0000
Hi Brian, At 10:04 07-11-2013, Brian E Carpenter wrote: >Some comments. > >1) I object to the change in the first sentence of the Introduction: > >"The work of the IETF relies on cooperation ..." has become >"The work of the IETF relies on collaboration...". > >I really think that "cooperation" is a significantly better word. >I want more than collaborators in the IETF (people who labor with >me). I want a spirit of cooperation. Also, "collaborate" has one very >negative meaning in English. > >(Please compare http://www.merriam-webster.com/dictionary/cooperate >and http://www.merriam-webster.com/dictionary/collaborate.) Thanks for pointing this out. I forgot about the case where "collaboration" has a negative connotation. I'll change the sentence to: The work of the IETF relies on cooperation among a diverse range of people, ideas, and communication styles. >2) In the item "4. Individuals are prepared to contribute to the ongoing >work of the group", I quite understand why some text was considered >objectionable and was deleted. But I think the the following text should >not have been deleted: > >"Working Group meetings run on a very limited time >schedule, and are not intended for the education of individuals. >The work of the group will continue on the mailing list, and many >questions would be better expressed on the list in the months that >follow." > >I would probably tune the last part so that it reads" > >"Working Group meetings run on a very limited time >schedule, and are not intended for the education of individuals. >The work of the group will continue on the mailing list, and >questions can be asked and answered on the list." I'll comment as an individual. This was a thread at http://www.ietf.org/mail-archive/web/diversity/current/msg00209.html The "not intended for the education of individuals" can be read in various ways. I understand that there is a time constraint. If there are five new persons, each taking one minute, at the microphone I see that as five new persons feeling comfortable to participate in the IETF. One of the points in the slide at http://www.ietf.org/proceedings/53/slides/plenary-3/sld016.htm is "grow other people". Is it worthwhile to spend the five minutes of a working group session on new participants? My answer is yes. At the end of the Technical Plenary there was a woman who came to the microphone to make a comment. I was interested in hearing her opinion. 11% of the attendees at this week's meeting are new. A quick look at the microphone line might show whether these attendees are causing problems. >3) The Security Considerations say: > >"Guidelines about IETF conduct do not affect the security of the >Internet in any way." > >I'm not so sure. Try this: > >"Guidelines about IETF conduct do not directly affect the security of the >Internet." Thanks, I'll go with the suggested text. >(I thought about drafting some text about how misconduct could damage >security, but I think that rat hole can be avoided in this particular >document.) Yes. :-) >4) Appendix A: Reporting transgressions of the guidelines > >Maybe just add a hint about the ombudsperson? > >"At the time of writing, the IETF is putting in place an >anti-harassment policy >and an ombudsperson to handle complaints." I'll leave this one open and wait for more feedback. Please note that I have read about the appeals. Regards, S. Moonesamy
- Re: Last Call: <draft-moonesamy-ietf-conduct-3184… S Moonesamy
- Re: Last Call: <draft-moonesamy-ietf-conduct-3184… Arturo Servin
- Re: Last Call: <draft-moonesamy-ietf-conduct-3184… S Moonesamy
- Re: Last Call: <draft-moonesamy-ietf-conduct-3184… Arturo Servin
- Re: Last Call: <draft-moonesamy-ietf-conduct-3184… S Moonesamy
- Re: Last Call: <draft-moonesamy-ietf-conduct-3184… Abdussalam Baryun
- Re: Last Call: <draft-moonesamy-ietf-conduct-3184… S Moonesamy
- Re: Last Call: <draft-moonesamy-ietf-conduct-3184… Brian E Carpenter
- Re: Last Call: <draft-moonesamy-ietf-conduct-3184… David Farmer
- Re: Last Call: <draft-moonesamy-ietf-conduct-3184… S Moonesamy
- Re: Last Call: <draft-moonesamy-ietf-conduct-3184… Abdussalam Baryun
- Re: Last Call: <draft-moonesamy-ietf-conduct-3184… S Moonesamy
- Re: Last Call: <draft-moonesamy-ietf-conduct-3184… Brian E Carpenter
- Re: Last Call: <draft-moonesamy-ietf-conduct-3184… Murray S. Kucherawy
- Re: Last Call: <draft-moonesamy-ietf-conduct-3184… S Moonesamy
- Re: Last Call: <draft-moonesamy-ietf-conduct-3184… S Moonesamy
- Re: Last Call: <draft-moonesamy-ietf-conduct-3184… Ines Robles
- Re: Last Call: <draft-moonesamy-ietf-conduct-3184… Dave Cridland
- Re: Last Call: <draft-moonesamy-ietf-conduct-3184… S Moonesamy
- Re: Last Call: <draft-moonesamy-ietf-conduct-3184… S Moonesamy
- Re: Last Call: <draft-moonesamy-ietf-conduct-3184… Abdussalam Baryun
- Re: Last Call: <draft-moonesamy-ietf-conduct-3184… Brian E Carpenter
- Re: Last Call: <draft-moonesamy-ietf-conduct-3184… Ines Robles
- Re: Last Call: <draft-moonesamy-ietf-conduct-3184… Ines Robles
- Re: Last Call: <draft-moonesamy-ietf-conduct-3184… Ines Robles
- Re: Last Call: <draft-moonesamy-ietf-conduct-3184… Stewart Bryant
- Re: Last Call: <draft-moonesamy-ietf-conduct-3184… S Moonesamy
- Re: Last Call: <draft-moonesamy-ietf-conduct-3184… Jari Arkko