Re: [openpgp] The DANE draft

Paul Wouters <paul@nohats.ca> Sun, 26 July 2015 18:51 UTC

Return-Path: <paul@nohats.ca>
X-Original-To: openpgp@ietfa.amsl.com
Delivered-To: openpgp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B35931ACD6D for <openpgp@ietfa.amsl.com>; Sun, 26 Jul 2015 11:51:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level:
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 K_ZLoo06m5oD for <openpgp@ietfa.amsl.com>; Sun, 26 Jul 2015 11:51:25 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 277161ACD69 for <openpgp@ietf.org>; Sun, 26 Jul 2015 11:51:25 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3mfYJV4n0yzD7t; Sun, 26 Jul 2015 20:51:22 +0200 (CEST)
Authentication-Results: mx.nohats.ca; dkim=pass (1024-bit key) header.d=nohats.ca header.i=@nohats.ca header.b=YftpJFsB
X-OPENPGPKEY: Message passed unmodified
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id Q3I8SO6N6aKL; Sun, 26 Jul 2015 20:51:21 +0200 (CEST)
Received: from bofh.nohats.ca (206-248-139-105.dsl.teksavvy.com [206.248.139.105]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Sun, 26 Jul 2015 20:51:21 +0200 (CEST)
Received: from [192.168.10.222] (unknown [62.209.224.147]) by bofh.nohats.ca (Postfix) with ESMTPSA id E797D80042; Sun, 26 Jul 2015 14:51:19 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1437936680; bh=Ddsf5V1HvALxxfWKeAp6siZwBLmSc5wSnVBk6+yvz74=; h=References:In-Reply-To:Cc:From:Subject:Date:To; b=YftpJFsBkbG/QTUyFjdR6qwhynOQ/5OHt81MZVWfp5h+6BK2VG4x3aKiLVspAuEkK gx91YYE7fMuhNXXvZxIaeOcOZgS/BkRg33m4L+C5Lqi7Qx4AO2TlBQe+rZmvacxqCQ J6q7taU6YKfrhXSrQBSIEgViustX7eXcfwg+oyto=
References: <CAMm+LwhYdBLXM8Td8q8SCnzgwywRgMx3wNKeS_Q0JSN4Lh7rZQ@mail.gmail.com> <87bnf1hair.fsf@alice.fifthhorseman.net> <CAMm+LwhGCtoNrLcDKA8PDDSM5DJN50G1Y+6V99v1hB9eyzjkgw@mail.gmail.com> <alpine.LFD.2.11.1507261124270.32550@bofh.nohats.ca> <CACsn0ckK+x46AvjoAhD_-6_Ak9y+TXtccYReCo9t6zbDr1=UHA@mail.gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <CACsn0ckK+x46AvjoAhD_-6_Ak9y+TXtccYReCo9t6zbDr1=UHA@mail.gmail.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-Id: <2AB3B153-D594-46B2-B1F8-1A6A49ABC51B@nohats.ca>
X-Mailer: iPhone Mail (13A4305g)
From: Paul Wouters <paul@nohats.ca>
Date: Sun, 26 Jul 2015 20:51:16 +0200
To: Watson Ladd <watsonbladd@gmail.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/openpgp/xj7LXfyPrbkcLQJAqZr2th087_g>
Cc: Phillip Hallam-Baker <phill@hallambaker.com>, Daniel Kahn Gillmor <dkg@fifthhorseman.net>, IETF OpenPGP <openpgp@ietf.org>
Subject: Re: [openpgp] The DANE draft
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Ongoing discussion of OpenPGP issues." <openpgp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/openpgp>, <mailto:openpgp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/openpgp/>
List-Post: <mailto:openpgp@ietf.org>
List-Help: <mailto:openpgp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/openpgp>, <mailto:openpgp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Jul 2015 18:51:26 -0000


Sent from my iPhone

> 
> Nationstates can also block DNSSEC resolution without breaking anything.

Then at least you have a confirmation you are under attack, unlike a non-responsive http(s) connection.

And economic pressure prevents nation states from fully blocking things like IPsec VPNs - I would hope DNSSEC would share that fate in the future.