IETF Logo Mail Archive

Re: dane-openpgp 2nd LC resolution

Viktor Dukhovni <ietf-dane@dukhovni.org> Tue, 15 March 2016 02:01 UTC

Return-Path: <ietf-dane@dukhovni.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA1A612D86E for <ietf@ietfa.amsl.com>; Mon, 14 Mar 2016 19:01:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=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 0Ip9iUCc36Ni for <ietf@ietfa.amsl.com>; Mon, 14 Mar 2016 19:01:24 -0700 (PDT)
Received: from mournblade.imrryr.org (mournblade.imrryr.org [38.117.134.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7166912D867 for <ietf@ietf.org>; Mon, 14 Mar 2016 19:01:24 -0700 (PDT)
Received: from [172.31.24.203] (gzac12-mdf2-1.aoa.twosigma.com [208.77.215.155]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mournblade.imrryr.org (Postfix) with ESMTPSA id 7F022283031 for <ietf@ietf.org>; Tue, 15 Mar 2016 02:01:23 +0000 (UTC) (envelope-from ietf-dane@dukhovni.org)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
Subject: Re: dane-openpgp 2nd LC resolution
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
In-Reply-To: <56E768E6.5090905@dougbarton.us>
Date: Mon, 14 Mar 2016 22:01:22 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <C643AF75-9E42-4360-BA33-F44A9882B0DE@dukhovni.org>
References: <56DC484F.7010607@cs.tcd.ie> <56E636FD.9050902@dougbarton.us> <alpine.LFD.2.20.1603141916360.830@bofh.nohats.ca> <56E768E6.5090905@dougbarton.us>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.3112)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/rA6zr4WFDn9ADrNovyP1xCzjrFw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: ietf@ietf.org
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: <https://mailarchive.ietf.org/arch/browse/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, 15 Mar 2016 02:01:27 -0000

> On Mar 14, 2016, at 9:44 PM, Doug Barton <dougb@dougbarton.us> wrote:
> 
> Close behind that concern, the larger IETF community (or at least some very vocal segments of it) have serious concerns about this type of opportunistic encryption happening at all, or in my case, without user input. They (and to some extent I) remain unconvinced that your assertion that this type of opportunistic encryption is always better than the current state.

I would like to suggest that RFC7435 is a reasonable statement against the
all-or-nothing fallacy.

-- 
	Viktor.

v2.23.0 | Report a Bug | By Email