Re: [dane] Last Call: <draft-ietf-dane-protocol-19.txt> (The

Martin Rex <mrex@sap.com> Thu, 12 April 2012 21:35 UTC

Return-Path: <mrex@sap.com>
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 ABA1821F877B; Thu, 12 Apr 2012 14:35:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.078
X-Spam-Level:
X-Spam-Status: No, score=-10.078 tagged_above=-999 required=5 tests=[AWL=0.171, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2hEMghoxTk49; Thu, 12 Apr 2012 14:35:41 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id C058421F877A; Thu, 12 Apr 2012 14:35:40 -0700 (PDT)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id q3CLZdFC015720 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 12 Apr 2012 23:35:39 +0200 (MEST)
From: Martin Rex <mrex@sap.com>
Message-Id: <201204122135.q3CLZY5A015636@fs4113.wdf.sap.corp>
Subject: Re: [dane] Last Call: <draft-ietf-dane-protocol-19.txt> (The
To: sm@resistor.net
Date: Thu, 12 Apr 2012 23:35:34 +0200
In-Reply-To: <6.2.5.6.2.20120411202530.085195c0@resistor.net> from "SM" at Apr 12, 12 00:11:43 am
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-SAP: out
Cc: ietf@ietf.org, dane@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.com
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: Thu, 12 Apr 2012 21:35:41 -0000

SM wrote:
> 
> In Section 8.1:
> 
>    "If it is less likely that a user will hear about its trusted DNSSEC
>     validators being hacked that it is of a public CA being compromised"
> 
> I suggest using "compromised" instead of "hacked".

Similar to what John complains about, comparing trusted DNSSEC validators
to public CAs is comparing apples and oranges.

The equivalent of a trusted DNSSEC validator in the PKIX world would
be an SCVP server/service!

The compromise of the DNSSEC zone data for DANE is probably equivalent to
the compromise of an organizational CA signed by a public CA with
name constraints to that DNS zone.

The compromise of an unconstrained public CA in the PKIX world would
be equivalent to a compromise of the root DNSSEC zone data in the DANE world.


-Martin