Re: ietf.org unaccessible for Tor users

Stephen Farrell <stephen.farrell@cs.tcd.ie> Tue, 15 March 2016 14:25 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
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 1DF4F12DA73 for <ietf@ietfa.amsl.com>; Tue, 15 Mar 2016 07:25:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.302
X-Spam-Level:
X-Spam-Status: No, score=-4.302 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_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 uhMSNWeZu3MA for <ietf@ietfa.amsl.com>; Tue, 15 Mar 2016 07:25:19 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 033A512D8AD for <ietf@ietf.org>; Tue, 15 Mar 2016 07:25:19 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id CB6D8BE33; Tue, 15 Mar 2016 14:25:17 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OQHdL84ilNQE; Tue, 15 Mar 2016 14:25:16 +0000 (GMT)
Received: from [10.87.49.100] (unknown [86.46.23.221]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id D3348BE32; Tue, 15 Mar 2016 14:25:15 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1458051916; bh=C+MbAXBMPWxCm4EGp/czBEbBaCNmEuKbUB06W6fdzC4=; h=Subject:To:References:From:Date:In-Reply-To:From; b=3rwPHLVH52f6oYrO1MoP+sebjK86RtLCinrHS1m+bvK4MiW3dhAfyzJ/LUcM19HMu dHKDYJOMS/qzCvvU+vYhmwH1WHNHAKwu5YFDnqdsju7ukBl54QLiDK0vjTX7SRlEk2 pEbPHRVaCJEBi8f5CTiQTiTevX15ewYClDsvDDLg=
Subject: Re: ietf.org unaccessible for Tor users
To: Eliot Lear <lear@cisco.com>, Michael Richardson <mcr+ietf@sandelman.ca>, IETF Disgust List <ietf@ietf.org>
References: <20160313143521.GC26841@Hirasawa> <m2a8m0y72q.wl%randy@psg.com> <F04B3B85-6B14-43BA-9A21-FC0A31E79065@piuha.net> <56E7E09D.7040100@cisco.com> <4349AFDD-350C-4217-9BEE-3DBD2F608F95@nohats.ca> <27177.1458050662@obiwan.sandelman.ca> <56E81891.50008@cisco.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <56E81B4B.30304@cs.tcd.ie>
Date: Tue, 15 Mar 2016 14:25:15 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <56E81891.50008@cisco.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="tr1RBQrdR1T4Ht3u8Q6N8VAvD2opRsRun"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/78ZPs6fBwruNI6qb8tBhPgvNOSs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
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: <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: Tue, 15 Mar 2016 14:25:26 -0000


On 15/03/16 14:13, Eliot Lear wrote:
> By providing the chaff 

We are not doing that. We are providing our usual web site is
all. That we need to turn off an additional control added by
CF is not the same as actively providing cover traffic.

> we are making a moral decision to
> help those who use Tor.  Have we done so consciously and is it the right
> one? 

I don't think we (the IETF) need to decide that. We need to
decide to re-level the field for exit nodes so that people
who access the IETF site via those hosts aren't discommoded.

Speaking personally, I'd answer your question with a yes, but
not on moral grounds, rather because Tor is one of the most
widely used privacy enhancing technologies; the IETF should
encourage use of such so that we learn how to make privacy
better on the Internet, so therefore we should, I think, be
actively encouraging its use so we learn more about it. I
don't think the IETF has established that as a consensus
position, but nor should we have to. It's fairly obvious I
reckon.

I'd also say yes on moral grounds as it happens, but one yes
should be enough for everyone except Molly Bloom:-)

Cheers,
S.