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

Stephen Farrell <stephen.farrell@cs.tcd.ie> Mon, 01 June 2015 20:35 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 BA1AD1B33D1 for <ietf@ietfa.amsl.com>; Mon, 1 Jun 2015 13:35:03 -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 uKbOrpog9fX5 for <ietf@ietfa.amsl.com>; Mon, 1 Jun 2015 13:35:02 -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 2486F1B33CD for <ietf@ietf.org>; Mon, 1 Jun 2015 13:35:02 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 88BC4BED1; Mon, 1 Jun 2015 21:35:00 +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 hOwx8-HWu4ul; Mon, 1 Jun 2015 21:34:58 +0100 (IST)
Received: from [10.87.48.73] (unknown [86.46.31.250]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 50B94BED2; Mon, 1 Jun 2015 21:34:58 +0100 (IST)
Message-ID: <556CC1F1.7060302@cs.tcd.ie>
Date: Mon, 01 Jun 2015 21:34:57 +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: Brian E Carpenter <brian.e.carpenter@gmail.com>, ietf@ietf.org
Subject: Re: Proposed Statement on "HTTPS everywhere for the IETF"
References: <20150601164359.29999.35343.idtracker@ietfa.amsl.com> <556CBD4A.9030708@gmail.com>
In-Reply-To: <556CBD4A.9030708@gmail.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/W21xKsELHPsY243IQwxlFbLzJqE>
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: Mon, 01 Jun 2015 20:35:03 -0000

Hiya,

On 01/06/15 21:15, Brian E Carpenter wrote:
> Hi,
> 
> I think this is reasonable. However, it seems necessary to qualify it
> by pointing out that users of HTTPS remain exposed to traffic analysis
> (e.g. see https://arxiv.org/pdf/1403.0297).

Good point. We can add something to that effect I think.

Cheers,
S.

> 
>     Brian
> 
> On 02/06/2015 04:43, The IESG 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
>>
>> .
>>
> 
> 
>