Re: ietf.org unaccessible for Tor users

Andrew Sullivan <ajs@anvilwalrusden.com> Tue, 15 March 2016 01:55 UTC

Return-Path: <ajs@anvilwalrusden.com>
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 9BE4212D84D for <ietf@ietfa.amsl.com>; Mon, 14 Mar 2016 18:55:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=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 v9SQOaGM61hH for <ietf@ietfa.amsl.com>; Mon, 14 Mar 2016 18:55:58 -0700 (PDT)
Received: from mx2.yitter.info (mx2.yitter.info [50.116.54.116]) by ietfa.amsl.com (Postfix) with ESMTP id 1A91E12D5C0 for <ietf@ietf.org>; Mon, 14 Mar 2016 18:55:58 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx2.yitter.info (Postfix) with ESMTP id B35D810AA9 for <ietf@ietf.org>; Tue, 15 Mar 2016 01:55:57 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx2.yitter.info ([127.0.0.1]) by localhost (mx2.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6i-KXhAQz8lN for <ietf@ietf.org>; Tue, 15 Mar 2016 01:55:57 +0000 (UTC)
Received: from mx2.yitter.info (unknown [IPv6:2601:18d:8600:87d9:11d5:4941:1a0a:8d83]) by mx2.yitter.info (Postfix) with ESMTPSA id E691F106CE for <ietf@ietf.org>; Tue, 15 Mar 2016 01:55:56 +0000 (UTC)
Date: Mon, 14 Mar 2016 21:55:55 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: ietf.org unaccessible for Tor users
Message-ID: <20160315015555.GX84411@mx2.yitter.info>
References: <20160313143521.GC26841@Hirasawa> <m2a8m0y72q.wl%randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <m2a8m0y72q.wl%randy@psg.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/waTZfHfnlKMdC2lgpj4ZY1KFaXY>
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 01:55:59 -0000

Hi,

Speaking only as myself:

On Tue, Mar 15, 2016 at 08:26:37AM +0900, Randy Bush wrote:
> 
> what is the treat model which drives us to tls/https?  authenticity of
> the data?  privacy of what i access?  in the scheme of things, how
> important are our data anyway and what are we trading for perceived
> protection?

I think the question of what we want to accomplish is important and
the one I'd hope we'd focus on first when trying to answer these
questions.  It seems to me that people ought to be able to access IETF
stuff in as many ways as we can think of, and to do that without fear
of repercussions.  yet we need to do something about the attacks
against the IETF sites, which have been painful and which we need to
be prepared to handle.

No brilliant suggestions here, just questions.

A


-- 
Andrew Sullivan
ajs@anvilwalrusden.com