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

Phillip Hallam-Baker <phill@hallambaker.com> Mon, 01 June 2015 20:58 UTC

Return-Path: <hallam@gmail.com>
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 CE9F41A8A72 for <ietf@ietfa.amsl.com>; Mon, 1 Jun 2015 13:58:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level:
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 iOQCMr6PVTUu for <ietf@ietfa.amsl.com>; Mon, 1 Jun 2015 13:58:09 -0700 (PDT)
Received: from mail-lb0-x232.google.com (mail-lb0-x232.google.com [IPv6:2a00:1450:4010:c04::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D9111B2BD6 for <ietf@ietf.org>; Mon, 1 Jun 2015 13:58:09 -0700 (PDT)
Received: by lbcue7 with SMTP id ue7so92258461lbc.0 for <ietf@ietf.org>; Mon, 01 Jun 2015 13:58:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=eLSMbKwiANyFUIeAwPuYYeGS2yIFRREz/faDL0ogkCE=; b=Lc7OL1fGUzFxwTrkYXvNpB9Q3f6XRMoPbvCTEomKVQPcVVdUUcmUIEba2LLt2W5/yy Mm8v1T7C+WDz6jXZP5IUG7hxiulJCeTUjVdp2nuNP8vrcByyMG9UTXQ6/ta6tfcybj2F C5j0OOzekpbnf3oCDFMM21YtTQQ+DUGV0m967Ky9tBfG4Hpp+fFdOBObcDQssHpP1H5O pj482d4jroLRQSKkEE4Ch/SoeocJquBk9RWTZuDiawpvrtNAAmUGYRi5knLL+CnlhssU AtLxhvi/sU1prstp8tHIxfWQqsi1LwtMP1IHKXR/M8WBHouHgr32y2M4ajokq/6nCcgR VqQA==
MIME-Version: 1.0
X-Received: by 10.152.43.168 with SMTP id x8mr23037905lal.79.1433192287916; Mon, 01 Jun 2015 13:58:07 -0700 (PDT)
Sender: hallam@gmail.com
Received: by 10.112.203.163 with HTTP; Mon, 1 Jun 2015 13:58:07 -0700 (PDT)
In-Reply-To: <556CBD4A.9030708@gmail.com>
References: <20150601164359.29999.35343.idtracker@ietfa.amsl.com> <556CBD4A.9030708@gmail.com>
Date: Mon, 1 Jun 2015 16:58:07 -0400
X-Google-Sender-Auth: _PjiIOtFgjes4Mctlw_dSN3p77I
Message-ID: <CAMm+LwguFiH1Nz-DZznck--_OWbt49uFES+recJViYrC8X2W+w@mail.gmail.com>
Subject: Re: Proposed Statement on "HTTPS everywhere for the IETF"
From: Phillip Hallam-Baker <phill@hallambaker.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c22a5e375bcf05177b15a5
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/Ol9XapO4aYMETswDbaONAcbPMV0>
Cc: IETF Discussion Mailing List <ietf@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: Mon, 01 Jun 2015 20:58:11 -0000

On Mon, Jun 1, 2015 at 4:15 PM, Brian E Carpenter <
brian.e.carpenter@gmail.com> 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).
>

Agreed.

But I would add a note to say that blocking traffic analysis is something
that requires link layer encryption. I don't think we can do much to
prevent that type of attack in IETF but we could stir IEEE to do something
useful.