Re: ietf.org unaccessible for Tor users

Randy Bush <randy@psg.com> Mon, 14 March 2016 23:26 UTC

Return-Path: <randy@psg.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 05CB012D809 for <ietf@ietfa.amsl.com>; Mon, 14 Mar 2016 16:26:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.002
X-Spam-Level:
X-Spam-Status: No, score=-5.002 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] 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 n9dLUpMlJhpd for <ietf@ietfa.amsl.com>; Mon, 14 Mar 2016 16:26:43 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8665412D805 for <ietf@ietf.org>; Mon, 14 Mar 2016 16:26:41 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.82) (envelope-from <randy@psg.com>) id 1afbsk-0001b9-Rm; Mon, 14 Mar 2016 23:26:39 +0000
Date: Tue, 15 Mar 2016 08:26:37 +0900
Message-ID: <m2a8m0y72q.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Yui Hirasawa <yui@cock.li>
Subject: Re: ietf.org unaccessible for Tor users
In-Reply-To: <20160313143521.GC26841@Hirasawa>
References: <20160313143521.GC26841@Hirasawa>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/yX9f_SNZOZF53XaqtrmHW-9wBk4>
Cc: IETF Disgust List <ietf@ietf.org>
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: Mon, 14 Mar 2016 23:26:45 -0000

> By using CloudFlare IETF is actively blocking Tor connections to IETF
> page.

i agree this is a problem.  but i am not sure about the solution space.
are we trading one form of security for another?

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?

how much load-spreading and resilience do ietf web/wiki/archives
actually need?  if they need a cdn, and i am not so sure they do, can we
have a cdn which supports tls without being a monkey in the middle?  do
we pay to deploy a half dozen anycasted instances of our own and
maintain them [0]?

some of this we have discussed before, maybe not as insightfully as we
might have.

randy

0 - sysadmin is similar to doing the dishes; you go to sleep with a
    clean kitchen, but there will be more dishes tomorrow.