Re: What is a "management position? [Last Call: <draft-farrresnickel-harassment-05.txt> (IETF Anti-Harassment Procedures) to Best Current Practice]

Andrew Sullivan <ajs@anvilwalrusden.com> Mon, 16 March 2015 20:33 UTC

Return-Path: <ajs@anvilwalrusden.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 8406B1A9106; Mon, 16 Mar 2015 13:33:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.141
X-Spam-Level:
X-Spam-Status: No, score=-0.141 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311] autolearn=no
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 BtUqC3Uz_eh0; Mon, 16 Mar 2015 13:33:33 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D02A1A90D0; Mon, 16 Mar 2015 13:32:53 -0700 (PDT)
Received: from mx1.yitter.info (unknown [50.189.173.0]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id EA8F18A035; Mon, 16 Mar 2015 20:32:51 +0000 (UTC)
Date: Mon, 16 Mar 2015 16:32:50 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: dcrocker@bbiw.net
Subject: Re: What is a "management position? [Last Call: <draft-farrresnickel-harassment-05.txt> (IETF Anti-Harassment Procedures) to Best Current Practice]
Message-ID: <20150316203250.GJ2179@mx1.yitter.info>
References: <tslfv9a2t6p.fsf@mit.edu> <36671C44-DE53-4AC9-B8EA-465BF97B2FDB@piuha.net> <tsly4n0zo6g.fsf@mit.edu> <550350C4.9040201@qti.qualcomm.com> <5503914A.7060209@gmail.com> <5503BF22.5020902@gmail.com> <2AE2D092-C32A-46EB-88CA-71366965F4D7@cisco.com> <5505D873.1040203@gmail.com> <CAL0qLwbQf_2WUn8PrUXCMy_3w6tt+iJw0tyF=gUojA5fwRXJNg@mail.gmail.com> <550736E0.6080101@dcrocker.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <550736E0.6080101@dcrocker.net>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/cWya6n6PGePo8X0tLEZJshVJ03o>
Cc: IETF Discussion List <ietf@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
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: Mon, 16 Mar 2015 20:33:34 -0000

Hi,

(I've trimmed some cc:s)

On Mon, Mar 16, 2015 at 01:02:40PM -0700, Dave Crocker wrote:
> Formally, document writers (authors and editors) and note-takers
> (secretaries, scribes, etc.) have no authority.  Everything they do is
> at the will of chairs and the wg.  In practice, of course, they can be
> enormously influence, swaying the substance of content.
> 
> Calling such folk "management' is a bit awkward, however, since their
> roles are not usually described that way in the rest of the world.
> 
> Perhaps the language should, instead refer to anyone with an explicitly
> assigned role?

I really dislike this suggestion.  If someone who has no formal
authority and serves at the pleasure of the relevant WG chairs is
abusing their position of influence, the right thing to do is not to
expand the definition of Official Role-Holder.  The thing to do is to
complain to the people who _do_ have official authority and use the
processes we have.  

For the obvious problem with expanding the relevant class to
"influential persons" is that the very next thing we must do is
include anyone who happens to have influence by virtue of their long
service, authoritative viewpoints on a topic, past service in
"management", lengthy list of RFCs, or whatever.  Once we do that,
we're well into the developing multiple classes of participants as an
official part of our processes.  I think that would be a terrible
precedent to set.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com