Re: ietf.org unaccessible for Tor users

Tim Chown <tjc@ecs.soton.ac.uk> Tue, 15 March 2016 14:33 UTC

Return-Path: <tjc@ecs.soton.ac.uk>
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 AFF0112DA4A for <ietf@ietfa.amsl.com>; Tue, 15 Mar 2016 07:33:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.222
X-Spam-Level:
X-Spam-Status: No, score=-1.222 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, SPF_NEUTRAL=0.779] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ecs.soton.ac.uk
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 CpQZ4Fl_WahB for <ietf@ietfa.amsl.com>; Tue, 15 Mar 2016 07:33:41 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 36BCF12D61B for <ietf@ietf.org>; Tue, 15 Mar 2016 07:33:41 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id u2FEXbNh017226 for <ietf@ietf.org>; Tue, 15 Mar 2016 14:33:37 GMT
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk u2FEXbNh017226
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1458052417; bh=55Q+s/5OGXTd81JCNzIreVlOLnI=; h=Mime-Version:Subject:From:In-Reply-To:Date:References:To; b=2b4wTGZX2RA5EWkPWHp44HUqFvejisD25MmzSuzB4TxOwoEwv/JIhm3Q5gIxMsWK9 KfTptQ7/AczdfL/pbPC63zSRNkVzLRJxPJwPSUmivyBQFRMey/mQLZTKsV/LNE+ncf SUwLAl04hr0TPu7ghzeyXJjvETrYjRljKeDms4Ds=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id s2EEXb0475708978fW ret-id none; Tue, 15 Mar 2016 14:33:37 +0000
Received: from 20010a88d51011.ipv6.customer.clara.net (20010a88d51011.ipv6.customer.clara.net [IPv6:2001:a88:d510:1101:1a7:42d1:795a:e97c] (may be forged)) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id u2FEXTn1020281 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Tue, 15 Mar 2016 14:33:30 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
Subject: Re: ietf.org unaccessible for Tor users
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <m2shzrrfag.wl%randy@psg.com>
Date: Tue, 15 Mar 2016 14:33:29 +0000
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|0019ef8b8baf46deeccac60a47ad4029s2EEXb03tjc|ecs.soton.ac.uk|A766E020-111C-4386-B0E9-FCFBA4B94DB5@ecs.soton.ac.uk>
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> <56E7EAA0.1050907@cs.tcd.ie> <56E7EE10.9000802@cisco.com> <56E7F4C7.6080808@mnt.se> <56E8070A.7070901@cisco.com> <C09D111E-188D-48EB-BD5E-B4CAF1B287BA@fb.com> <m2shzrrfag.wl%randy@psg.com> <A766E020-111C-4386-B0E9-FCFBA4B94DB5@ecs.soton.ac.uk>
To: IETF Disgust List <ietf@ietf.org>
X-Mailer: Apple Mail (2.3112)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=s2EEXb047570897800; tid=s2EEXb0475708978fW; client=relay,ipv6; mail=; rcpt=; nrcpt=1:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: u2FEXbNh017226
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/y89lZUqvsgitiMtAwqF_MRbFh8c>
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:33:42 -0000

> On 15 Mar 2016, at 14:23, Randy Bush <randy@psg.com> wrote:
> 
>   in these more privacy conscious days, we should be setting an example
>   of how our own technology (and those of our friends in other sdos)
>   can be used to maximize privacy and integrity.  client blocking,
>   discrimination, and breaking e2e encryption are not what i consider
>   nice examples.

This.

> On 15 Mar 2016, at 14:25, Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote:
> 
> 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.

And this.

Otherwise, it seems we have short memories.

Tim