RE: delegating (portions of) ietf list disciplinary process
"Thomas Gal" <tom@triagewireless.com> Thu, 29 September 2005 00:23 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EKmDO-0004hU-7L; Wed, 28 Sep 2005 20:23:58 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EKmDL-0004hP-V5 for ietf@megatron.ietf.org; Wed, 28 Sep 2005 20:23:56 -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 UAA23286 for <ietf@ietf.org>; Wed, 28 Sep 2005 20:23:54 -0400 (EDT)
Message-Id: <200509290023.UAA23286@ietf.org>
Received: from epsilon.postal.redwire.net ([64.186.240.40]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1EKmKu-0000Cc-47 for ietf@ietf.org; Wed, 28 Sep 2005 20:31:44 -0400
Received: (qmail 16120 invoked from network); 28 Sep 2005 17:23:45 -0700
Received: from c-064-186-224-138.sd2.redwire.net (HELO horatio) (tom.gal@64.186.224.138) by smtp.redwire.net with SMTP; 28 Sep 2005 17:23:45 -0700
From: Thomas Gal <tom@triagewireless.com>
To: nick.staff@comcast.net, 'Brian E Carpenter' <brc@zurich.ibm.com>, ietf@ietf.org
Date: Wed, 28 Sep 2005 17:23:51 -0700
Organization: Triage Wireless
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Thread-Index: AcXDdsbfTLrddlzERe21UVneBFBjMgAVnOTwAC8sIlA=
In-Reply-To: <200509280147.VAA06475@ietf.org>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3971661e40967acfc35f708dd5f33760
Cc:
Subject: RE: delegating (portions of) ietf list disciplinary process
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: tom@triagewireless.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1309382788=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
> > From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On > > > > I'm interested to know whether people would see arguments > for either > > or both of > > > > 1. An IETF Ombudsman (or Ombudscommittee), to act as a dispute > > mediator. > > > > 2. An IETF "netiquette" committee, to offload list banning > procedures > > from the IESG. > > > > Brian > Ahh, you beat me to the punch ;) > Both great ideas. I think this kind of issue is not predicated on deep technical knowledge, and really anyone who is familiar with the general IETF process would be quite capable to deal with such an issue. I'm firmly would put my faith in a comitee of say 5-10 over a smaller number any day however, with posting rights only revocable by unanimous consensus. > I'm a big fan of the netiquette committee. I'd like to > suggest that volunteers be allowed to "throw their names into > the hat" and that members be selected blindly from that pool. > This would of course avoid any stacking or favoritism, but > we would need a "qualifier" that prevented interlopers from > submitting their name. Though I hate to suggest it as it > would exclude me from selection, having attended an IETF > meeting in the last x years could possibly be a good filter. > Not sure about any good qualifiers, but I think it would be prudent to say force a member to recuse themselves if the issue concerns a WG in which they take an active roll. > I'm probably getting ahead of things but I was also thinking > some controls could be implemented to discourage frivolous > accusations. I realize that someone who repeatedly accuses > falsely won't be taken seriously, but sometimes the goal is > disruption and uncertainty which unfortunately these > accusations are almost guaranteed to provide. > First time you falsely accuse someone there should be a warning. It could also just be considered a learning opportunity. I don't think we should put up with more than a second time. > Anyway I think it's a great idea Brian. > Perhaps a good start would be to identify a few messages/threads which embody the type of posting we are trying to stop. Also I think a handy mechanism would be the notion of a "cooling off" period. While it may be futile to get someone to drop an issue completely, perhaps allowing WG Chairs for example to say "don't bring this up for a week or your posting rights will definitely be rescinded" is a simple way to force people to cool off, rethink their positions, and possibly come up with an amicable solution, possibly off the list even. We certanly don't wan't altercations taking place on the list. For example, I don't think that many issues start out too far outside what is acceptable, but as improprieties creep in it becomes difficult to blame one person without blaming another. I think this mechanism also provides a much more clear cut defenition of what is acceptable and what is not. -Tom
_______________________________________________ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
- RE: [dean@av8.com: Mismanagement of the DNSOP lis… Nick Staff
- RE: [dnsop] [dean@av8.com: Mismanagement of the D… Hallam-Baker, Phillip
- Re: delegating (portions of) ietf list disciplina… Marshall Eubanks
- Re: delegating (portions of) ietf list disciplina… Brian E Carpenter
- [dean@av8.com: Mismanagement of the DNSOP list] David Kessens
- RE: [dean@av8.com: Mismanagement of the DNSOP lis… Nicholas Staff
- Re: [dean@av8.com: Mismanagement of the DNSOP lis… Steven M. Bellovin
- RE: [dean@av8.com: Mismanagement of the DNSOP lis… Nicholas Staff
- Re: [dean@av8.com: Mismanagement of the DNSOP lis… Dean Anderson
- Re: [dnsop] [dean@av8.com: Mismanagement of the D… Dean Anderson
- RE: [dean@av8.com: Mismanagement of the DNSOP lis… bill
- RE: [dean@av8.com: Mismanagement of the DNSOP lis… Nick Staff
- Re: [dean@av8.com: Mismanagement of the DNSOP lis… David Kessens
- Re: [dean@av8.com: Mismanagement of the DNSOP lis… Brian E Carpenter
- Re: [dnsop] [dean@av8.com: Mismanagement of the D… Tim Bray
- RE: [dean@av8.com: Mismanagement of the DNSOP lis… Nick Staff
- Re: [dean@av8.com: Mismanagement of the DNSOP lis… Dave Crocker
- RE: [dnsop] [dean@av8.com: Mismanagement of the D… Hallam-Baker, Phillip
- Re: [dean@av8.com: Mismanagement of the DNSOP lis… Dean Anderson
- RE: [dean@av8.com: Mismanagement of the DNSOP lis… Dean Anderson
- Re: [dean@av8.com: Mismanagement of the DNSOP lis… Dean Anderson
- RE: [dnsop] [dean@av8.com: Mismanagement of the D… Dean Anderson
- Re: [dean@av8.com: Mismanagement of the DNSOP lis… Steven M. Bellovin
- RE: [dean@av8.com: Mismanagement of the DNSOP lis… Nick Staff
- RE: [dean@av8.com: Mismanagement of the DNSOP lis… Wijnen, Bert (Bert)
- RE: [dean@av8.com: Mismanagement of the DNSOP lis… Nick Staff
- Re: [dean@av8.com: Mismanagement of the DNSOP lis… John Leslie
- RE: [dean@av8.com: Mismanagement of the DNSOP lis… Nick Staff
- delegating (portions of) ietf list disciplinary p… Dave Crocker
- Procedures for the IETF list (RE: [dean@av8.com: … Harald Tveit Alvestrand
- RE: [dean@av8.com: Mismanagement of the DNSOP lis… C. M. Heard
- Re: [dean@av8.com: Mismanagement of the DNSOP lis… JFC (Jefsey) Morfin
- Re: [dnsop] [dean@av8.com: Mismanagement of the D… Robert Elz
- Re: [dean@av8.com: Mismanagement of the DNSOP lis… Steven M. Bellovin
- Re: [dnsop] [dean@av8.com: Mismanagement of the D… wayne
- Re: [dnsop] [dean@av8.com: Mismanagement of the D… Bill Sommerfeld
- Re: [dnsop] [dean@av8.com: Mismanagement of the D… Stephen Sprunk
- Re: [dnsop] [dean@av8.com: Mismanagement of the D… usphoenix
- RE: [dean@av8.com: Mismanagement of the DNSOP lis… Nick Staff
- RE: delegating (portions of) ietf list disciplina… Nick Staff
- Re: [dnsop] [dean@av8.com: Mismanagement of the D… Dean Anderson
- Re: delegating (portions of) ietf list disciplina… Theodore Ts'o
- Re: [dean@av8.com: Mismanagement of the DNSOP lis… Brian E Carpenter
- Re: [dnsop] [dean@av8.com: Mismanagement of the D… Dean Anderson
- Re: delegating (portions of) ietf list disciplina… Dean Anderson
- Re: [dnsop] [dean@av8.com: Mismanagement of the D… Kevin Loch
- Anycast DNS [some tech] was RE: [dnsop] [dean@av8… Dean Anderson
- Re: delegating (portions of) ietf list disciplina… Brian E Carpenter
- Re: delegating (portions of) ietf list disciplina… JFC (Jefsey) Morfin
- Re: [dean@av8.com: Mismanagement of the DNSOP lis… JFC (Jefsey) Morfin
- Re: delegating (portions of) ietf list disciplina… Michael Thomas
- Re: delegating (portions of) ietf list disciplina… Scott W Brim
- Re: [dnsop] [dean@av8.com: Mismanagement of the D… Dave Crocker
- Re: delegating (portions of) ietf list disciplina… Alexis Turner
- RE: [dnsop] [dean@av8.com: Mismanagement of the D… Thomas Gal
- RE: delegating (portions of) ietf list disciplina… Thomas Gal
- Re: [dnsop] [dean@av8.com: Mismanagement of the D… grenville armitage
- RE: [dnsop] [dean@av8.com: Mismanagement of the D… Thomas Gal
- Re: delegating (portions of) ietf list disciplina… Dave Crocker
- RE: delegating (portions of) ietf list disciplina… Nick Staff
- Minority opinions [Re: [dean@av8.com: Mismanageme… Brian E Carpenter
- Re: [dnsop] [dean@av8.com: Mismanagement of the D… Dean Anderson
- RE: delegating (portions of) ietf list disciplina… Dean Anderson
- Re: Minority opinions [Re: [dean@av8.com: Mismana… JFC (Jefsey) Morfin
- RE: Minority opinions [Re: [dean@av8.com: Mismana… Thomas Gal
- RE: delegating (portions of) ietf list disciplina… Nick Staff
- Re: delegating (portions of) ietf list disciplina… grenville armitage
- Re: delegating (portions of) ietf list disciplina… Theodore Ts'o
- RE: delegating (portions of) ietf list disciplina… Nick Staff