IETF Logo Mail Archive

Re: Proposed Statement on "HTTPS everywhere for the IETF"

Joe Touch <touch@isi.edu> Tue, 02 June 2015 18:59 UTC

Return-Path: <touch@isi.edu>
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 37F341ACE64; Tue, 2 Jun 2015 11:59:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] 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 cS1BmG-yCdJc; Tue, 2 Jun 2015 11:59:35 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F0D7F1ACE62; Tue, 2 Jun 2015 11:59:34 -0700 (PDT)
Received: from [128.9.160.252] (pen.isi.edu [128.9.160.252]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id t52Ix4mX012758 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 2 Jun 2015 11:59:04 -0700 (PDT)
Message-ID: <556DFCF7.3020607@isi.edu>
Date: Tue, 02 Jun 2015 11:59:03 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Richard Barnes <rlb@ipv.sx>
Subject: Re: Proposed Statement on "HTTPS everywhere for the IETF"
References: <20150601164359.29999.35343.idtracker@ietfa.amsl.com> <CAL02cgRPFooA5fVFwvdprb3wPD+Y55pD+7RWjkACDv7T_TBW5Q@mail.gmail.com> <556DE0EF.2040809@isi.edu> <CAL02cgSdSFOaDqz9+jAZ7KsoMXOa5u=ff_i=c3EQ-SG0-ZPG7A@mail.gmail.com>
In-Reply-To: <CAL02cgSdSFOaDqz9+jAZ7KsoMXOa5u=ff_i=c3EQ-SG0-ZPG7A@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/fd3YYIZIG5ylmX_7F2OUorjrd-k>
Cc: "ietf@ietf.org" <ietf@ietf.org>, IETF Announcement List <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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: <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: Tue, 02 Jun 2015 18:59:36 -0000


On 6/2/2015 11:51 AM, Richard Barnes wrote:
> 
> 
> On Tue, Jun 2, 2015 at 12:59 PM, Joe Touch <touch@isi.edu
> <mailto:touch@isi.edu>> wrote:
> 
>     On 6/1/2015 10:16 AM, Richard Barnes wrote:
>     > Do it.  Do it boldly and fearlessly.  Make the statement and implement it.
>     >
>     ...
>     > Don't be tied to legacy.  Anything that doesn't support HTTPS at this
>     > point needs to upgrade and deserves to be broken.
> 
>     Leaving out the have-nots - or those whose access is blocked by others
>     when content cannot be scanned - isn't moving forward.
> 
> 
> [citation-required]
> 
> Where is this place where the entire HTTPS web is not accessible? 

http://en.wikipedia.org/wiki/Censorship_of_Wikipedia

Search for HTTPS.

> How do they do their banking, or buy things?

Often through state-run companies (i.e., whose HTTPS content they can
screen).

Joe

v2.23.0 | Report a Bug | By Email