Re: Last Call: <draft-farrresnickel-harassment-08.txt> (IETF Anti-Harassment Procedures) to Best Current Practice

Dave Crocker <dhc@dcrocker.net> Wed, 23 September 2015 15:06 UTC

Return-Path: <dhc@dcrocker.net>
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 3FB941A6FA3 for <ietf@ietfa.amsl.com>; Wed, 23 Sep 2015 08:06:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 kkh1EiXcv-2m for <ietf@ietfa.amsl.com>; Wed, 23 Sep 2015 08:06:02 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 033081A6FA0 for <ietf@ietf.org>; Wed, 23 Sep 2015 08:06:02 -0700 (PDT)
Received: from [192.168.1.87] (76-218-10-206.lightspeed.sntcca.sbcglobal.net [76.218.10.206]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id t8NF5wcY013976 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Wed, 23 Sep 2015 08:06:01 -0700
Subject: Re: Last Call: <draft-farrresnickel-harassment-08.txt> (IETF Anti-Harassment Procedures) to Best Current Practice
To: John C Klensin <john-ietf@jck.com>, ietf@ietf.org
References: <20150831144507.2223.61158.idtracker@ietfa.amsl.com> <B28CD323-73C7-4D5F-8A07-8C3E72028BD8@mnot.net> <00d001d0e618$57047d60$050d7820$@olddog.co.uk> <AF3F601F5AEDB4520F27DA46@JcK-HP8200.jck.com>
From: Dave Crocker <dhc@dcrocker.net>
X-Enigmail-Draft-Status: N1110
Organization: Brandenburg InternetWorking
Message-ID: <5602BFD1.9040805@dcrocker.net>
Date: Wed, 23 Sep 2015 08:05:53 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <AF3F601F5AEDB4520F27DA46@JcK-HP8200.jck.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Wed, 23 Sep 2015 08:06:01 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/xdEt2z_IbRkA1JS5NeiTCjnF_XI>
Cc: Nevil Brownlee <rfc-ise@rfc-editor.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 23 Sep 2015 15:06:04 -0000

On 9/22/2015 12:07 PM, John C Klensin wrote:
> https://datatracker.ietf.org/doc/conflict-review-crocker-diversity-conduct/),
...
>  I believe
> that, if both documents are to be published, the community would
> be better served by having these documents published together
> and having at least one reference and explanation of the
> different perspectives in one (or both) of them.


There is much that I agree with in John's posting, but this isn't one of
them.

This independent document is independent.  It is a discussion piece by a
couple of IETF participants.

The other document is a product of the IETF and it is intended to become
part of the formal IETF administrative structure.

If it takes work to understand the very considerable importance this
difference means, in terms of role and handling of an independent
document, then please do that work.

One of the less-pleasant bits of education I received throughout the
/seven months/ it has taken to get through the 'Independent' stream
process is that it is far from independent.  There seems to be a common
view that documents on that stream must be meaningfully subservient to
the IETF, rather than actually providing independent input to it.

I won't distract this thread further with details about the multiple
conceptual problems that afflicted the handling of this document, other
than to ask that no one try to impose further restrictions on a document
that really is intended to be /independent/.


d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net