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

"Mark Baugher (mbaugher)" <mbaugher@cisco.com> Mon, 01 June 2015 23:57 UTC

Return-Path: <mbaugher@cisco.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 2C12C1A1F04 for <ietf@ietfa.amsl.com>; Mon, 1 Jun 2015 16:57:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 80d9jGui3rbr for <ietf@ietfa.amsl.com>; Mon, 1 Jun 2015 16:57:06 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D1BE01A1EF9 for <ietf@ietf.org>; Mon, 1 Jun 2015 16:57:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1870; q=dns/txt; s=iport; t=1433203026; x=1434412626; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=Bn7WgdvTpWduTO23mj1LeSVrDZ14LBjcZb5bZB5rw+w=; b=XWIgiCSGKbRUzDTnkLy2rkD/XuALNs3TBOXCQ3fpJ4mg1euzhq5sMW64 +v2IpbX9RqYjlipLgrKMdenEWq9Prrs/e/DwNyJpnWX1Gsi3XcJsOHDhV ztiqzkxiwzqxCTNteNvClrwQ4e1sSf7z85lNrzruNQvydT6hhiyKW/Z8q o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ALBQAj8WxV/5tdJa1cgxBUXga+X4dRAoE5ORMBAQEBAQEBgQqEIgEBAQMBOj8QAgEIDgoeEDIlAgQOBRuICgjYdwEBAQEBAQEBAQEBAQEBAQEBAQEBAReLQ4RTMweDF4EWAQSGa4wlixaXOCNhgxdvgUaBAQEBAQ
X-IronPort-AV: E=Sophos;i="5.13,536,1427760000"; d="scan'208";a="155341473"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-2.cisco.com with ESMTP; 01 Jun 2015 23:57:00 +0000
Received: from xhc-rcd-x02.cisco.com (xhc-rcd-x02.cisco.com [173.37.183.76]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id t51Nv071005418 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 1 Jun 2015 23:57:00 GMT
Received: from xmb-aln-x10.cisco.com ([169.254.5.25]) by xhc-rcd-x02.cisco.com ([173.37.183.76]) with mapi id 14.03.0195.001; Mon, 1 Jun 2015 18:56:59 -0500
From: "Mark Baugher (mbaugher)" <mbaugher@cisco.com>
To: Roland Dobbins <rdobbins@arbor.net>
Subject: Re: Proposed Statement on "HTTPS everywhere for the IETF"
Thread-Topic: Proposed Statement on "HTTPS everywhere for the IETF"
Thread-Index: AQHQnI6zkRY/kXprrkiaQ7WqvLfAh52YU+OAgAAqY4CAABSTgIAAFSSA
Date: Mon, 01 Jun 2015 23:56:59 +0000
Message-ID: <A5367743-71D5-4201-BCD7-3A4F10911644@cisco.com>
References: <20150601164359.29999.35343.idtracker@ietfa.amsl.com> <CAL02cgRPFooA5fVFwvdprb3wPD+Y55pD+7RWjkACDv7T_TBW5Q@mail.gmail.com> <1472054.O9DP0qoCQf@gongo> <alpine.LFD.2.11.1506011720390.12155@bofh.nohats.ca> <FACB397F-15AA-4FE1-ABF2-1545ABBACF31@arbor.net>
In-Reply-To: <FACB397F-15AA-4FE1-ABF2-1545ABBACF31@arbor.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.24.78.67]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <8656C9864D8BCA4EB13B07021BF68A87@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/hImOz179WrDy3hhnbi4lWZZwbxU>
Cc: "ietf@ietf.org" <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 23:57:07 -0000

+1
On Jun 1, 2015, at 3:41 PM, Roland Dobbins <rdobbins@arbor.net> wrote:

> 
> On 2 Jun 2015, at 4:27, Paul Wouters wrote:
> 
>> We had to cater to governments banning encryption for its users, and we now see what that got them.
> 
> They just go around the encryption and compromise the endpoints.  They're *governments*, so they have the resources to do that (not debating whether or not they should, just stating observed fact).
> 
> Also, universal or near-universal encryption is a serious problem in terms of detection, classification, traceback, and mitigation of application-layer DDoS attacks.  It drastically limits the scaling capacity of defenders, and results in even more cost asymmetry between defenders and attackers (in favor of the attackers).
> 
> My guess is that those who make bold, sweeping statements about how everything ought to be encrypted all the time are rarely those who have to deal with the unintended consequences of overencryption.
> 
> In the final analysis, there are no technical solutions for social ills.  The entire issue of unwanted surveillance by government entities is a social and political problem; it seems pretty clear that since the social/political side of things aren't proving to be easily resolved, that some folks are advocating doing *something*, *anything*, irrespective of whether it will actually make a positive impact on the conditions to which they object and without regard to the non-trivial side-effects of what they're advocating.
> 
> The IESG and the IETF in general should concentrate on technical issues, and work on solving social and political problems should take place in other, more appropriate appropriate fora, IMHO.
> 
> -----------------------------------
> Roland Dobbins <rdobbins@arbor.net>
>