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

Stephen Farrell <stephen.farrell@cs.tcd.ie> Wed, 03 June 2015 20:18 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
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 03C931A8794 for <ietf@ietfa.amsl.com>; Wed, 3 Jun 2015 13:18:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 nbHomZCEzg1I for <ietf@ietfa.amsl.com>; Wed, 3 Jun 2015 13:18:14 -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 6BFF81AD05C for <ietf@ietf.org>; Wed, 3 Jun 2015 13:18:14 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 20B06BF13; Wed, 3 Jun 2015 21:18:13 +0100 (IST)
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 YCi6FP_fm5Jg; Wed, 3 Jun 2015 21:18:11 +0100 (IST)
Received: from [10.87.48.73] (unknown [86.46.31.250]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 9F80BBF11; Wed, 3 Jun 2015 21:18:11 +0100 (IST)
Message-ID: <556F6103.2090608@cs.tcd.ie>
Date: Wed, 03 Jun 2015 21:18:11 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Proposed Statement on "HTTPS everywhere for the IETF"
References: <20150601164359.29999.35343.idtracker@ietfa.amsl.com> <543B4D57-C84C-49B7-B108-827333434F72@cisco.com>
In-Reply-To: <543B4D57-C84C-49B7-B108-827333434F72@cisco.com>
OpenPGP: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/Be2rHBnIr9-3JmpvU8LVs_WvAOk>
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: Wed, 03 Jun 2015 20:18:16 -0000

Hiya,

On 03/06/15 19:31, Cullen Jennings (fluffy) wrote:
> 
> This is too little too late.
> 
> This wishy washy "we believe in security but don't like to actually
> use it ourselves" is not the leadership IETF should be providing to
> the internet. The internet has already been harmed by too many years
> of security that is not turned on.
> 
> Take a hum at next plenary and find out if people want the IETF to
> actually use security or not.

Or we can put this in place and then measure who continues to access
in clear and see what that tells us.

Maybe a hum at a plenary is a bit too large a hammer to bring out for
this fairly modest nail.

S.


> 
> 
> 
>> On Jun 1, 2015, at 10:43 AM, The IESG <iesg@ietf.org> wrote:
>> 
>> Hi All,
>> 
>> The IESG are planning to agree an IESG statement on "HTTPS
>> Everywhere for the IETF," please see [1] for the current text.
>> 
>> We are seeking community feedback on this and welcome assistance 
>> from the community in identifying any cases where a change or 
>> additional guidance is needed to put this into effect.
>> 
>> The IESG plans to finalise this statement just after IETF-93 in
>> Prague.
>> 
>> * Please send general feedback intended for discussion to
>> ietf@ietf.org
>> 
>> * Comments about specific issues arising can be sent to
>> iesg@ietf.org or tools-discuss@ietf.org as appropriate (use
>> iesg@ietf.org if not sure)
>> 
>> Regards, Terry & Stephen (for the IESG)
>> 
>> [1]
>> https://trac.tools.ietf.org/group/iesg/trac/wiki/HttpsEverywhere
>> 
> 
>