Re: [dane] Summary of IETF LC for draft-ietf-dane-openpgpkey

Viktor Dukhovni <ietf-dane@dukhovni.org> Fri, 18 September 2015 03:23 UTC

Return-Path: <ietf-dane@dukhovni.org>
X-Original-To: dane@ietfa.amsl.com
Delivered-To: dane@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A5011A1AA3; Thu, 17 Sep 2015 20:23:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.057
X-Spam-Level:
X-Spam-Status: No, score=-1.057 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_06_12=1.543, RCVD_IN_DNSWL_LOW=-0.7] 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 0F3Ng9crwC8A; Thu, 17 Sep 2015 20:23:21 -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 F3AA71A1A68; Thu, 17 Sep 2015 20:23:20 -0700 (PDT)
Received: from vpro.lan (cpe-74-71-8-253.nyc.res.rr.com [74.71.8.253]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mournblade.imrryr.org (Postfix) with ESMTPSA id E7C58282F4C; Fri, 18 Sep 2015 03:23:19 +0000 (UTC) (envelope-from ietf-dane@dukhovni.org)
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Content-Type: text/plain; charset="us-ascii"
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
In-Reply-To: <FF3E448B980D3B2ACE932A04@JcK-HP8200.jck.com>
Date: Thu, 17 Sep 2015 14:09:11 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <931830E6-6B8C-410E-9B57-F3E5CB5AE5B8@dukhovni.org>
References: <20150917055456.1162.qmail@ary.lan> <alpine.LFD.2.20.1509170214530.6901@bofh.nohats.ca> <FF3E448B980D3B2ACE932A04@JcK-HP8200.jck.com>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dane/szOe4kAbF1Vq6WTjWEcfYIiGOwI>
Cc: dane@ietf.org
Subject: Re: [dane] Summary of IETF LC for draft-ietf-dane-openpgpkey
X-BeenThere: dane@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org, dane@ietf.org
List-Id: DNS-based Authentication of Named Entities <dane.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dane>, <mailto:dane-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dane/>
List-Post: <mailto:dane@ietf.org>
List-Help: <mailto:dane-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dane>, <mailto:dane-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Sep 2015 03:23:22 -0000

> On Sep 17, 2015, at 5:26 AM, John C Klensin <john-ietf@jck.com> wrote:
> 
> The document seems to say that I should not trust a key found by
> this method just because of where I find it.  That is entirely
> consistent with other PGP documents and existing keyservers.  I
> should, instead, rely on web of trust relationships, e.g.,
> signatures on the particular key.

OPENPGP is a data format, WoT is one way to employ that format to
exchange messages.   It is not a *required* way to use OPENPGP.
In particular, if a user elects to configure an MUA to use DNSSEC
as a trusted introducer, so as to be able to increase privacy
of messaging beyond his immediate social circle, that's a fine
choice.  Think of it as "opportunistic PGP".  It's what you
do when you'd have otherwise sent the email in the clear anyway.

-- 
	Viktor.