IETF Logo Mail Archive

Re: Sam's text and way forward on the last call of draft-farrresnickel-harassment-05.txt

Stewart Bryant <stbryant@cisco.com> Thu, 19 March 2015 14:29 UTC

Return-Path: <stbryant@cisco.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 D4BAA1AC439 for <ietf@ietfa.amsl.com>; Thu, 19 Mar 2015 07:29:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 H48vvDpRfl0w for <ietf@ietfa.amsl.com>; Thu, 19 Mar 2015 07:29:46 -0700 (PDT)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 485551A0211 for <ietf@ietf.org>; Thu, 19 Mar 2015 07:29:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=373; q=dns/txt; s=iport; t=1426775386; x=1427984986; h=message-id:date:from:reply-to:mime-version:to:subject: references:in-reply-to:content-transfer-encoding; bh=uwBU/o+LOierTk2bcb1QmGtKSTE2d1ugiZIgYceIiMM=; b=aIE2+ZkcsEfhqBU/cp8G5Mb+gYPkRMHeP/NC6fkRSRxaG2tZjjQXCc34 uHChhFF4PLp/lpSBo4Si2ZzGiTj7tMaCMIwZjQcoYxUS2/qTw+SUN0uwN EPraW3rNo2mG6VzFlK+l9rTHW44Ql+Kqg9XAmL0vm8nAComAyLuIUXuht U=;
X-IronPort-AV: E=Sophos;i="5.11,430,1422921600"; d="scan'208";a="392419011"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP; 19 Mar 2015 14:29:44 +0000
Received: from [64.103.108.142] (dhcp-bdlk10-data-vlan301-64-103-108-142.cisco.com [64.103.108.142]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id t2JETiOk007297; Thu, 19 Mar 2015 14:29:44 GMT
Message-ID: <550ADD5A.6040805@cisco.com>
Date: Thu, 19 Mar 2015 14:29:46 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: adrian@olddog.co.uk, 'Jari Arkko' <jari.arkko@piuha.net>, 'IETF Discussion List' <ietf@ietf.org>
Subject: Re: Sam's text and way forward on the last call of draft-farrresnickel-harassment-05.txt
References: <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> <20150316203250.GJ2179@mx1.yitter.info> <55073F22.6000606@dcrocker.net> <20150316204616.GK2179@mx1.yitter.info> <55074AC1.9080500@dcrocker.net> <20150316214620.GO2179@mx1.yitter.info> <550751AC.7090108@dcrocker.net> <55075EBA.4000905@gmail.com> <5509BB58.4060307@qti.qualcomm.com> <B714CBFE-5D3D-4293-91C2-534A3437EB24@piuha.net> <014401d0624e$5220d940$f6628bc0$@olddog.co.uk>
In-Reply-To: <014401d0624e$5220d940$f6628bc0$@olddog.co.uk>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/pMqAdhqtbZR5tn-jZc-v5iaO_eI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: stbryant@cisco.com
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, 19 Mar 2015 14:29:48 -0000

Something nagging in the back of my mind is that in
the opacity of this process there is scope for abuse
by the Ombudsteam. This is particularly problematic
where the Ombudsteam can opaquely remove people
from IETF office. I suspect that it would probably be less of a
problem if the Ombudsteam were Nomcom appointees
rather than IETF chair appointees.

- Stewart

v2.23.0 | Report a Bug | By Email