IETF Logo Mail Archive

Re: [dane] FYI: New Version Notification for draft-hoffman-dane-smime-04.txt

Jakob Schlyter <jakob@kirei.se> Tue, 11 September 2012 13:25 UTC

Return-Path: <jakob@kirei.se>
X-Original-To: dane@ietfa.amsl.com
Delivered-To: dane@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6DF1E21F87CC for <dane@ietfa.amsl.com>; Tue, 11 Sep 2012 06:25:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.698
X-Spam-Level:
X-Spam-Status: No, score=-0.698 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_EQ_SE=0.35, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uzdrISieVOlr for <dane@ietfa.amsl.com>; Tue, 11 Sep 2012 06:25:39 -0700 (PDT)
Received: from spg.kirei.se (spg.kirei.se [IPv6:2001:67c:394:15::9]) by ietfa.amsl.com (Postfix) with ESMTP id 29F4921F8620 for <dane@ietf.org>; Tue, 11 Sep 2012 06:25:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kirei.se; s=spg20100524; h=received:content-type:mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to:x-mailer; bh=S4ueXk87+WIEwLq3jVEVgoL/86ex5b4BfJ2wh12+16M=; b=p1lRUz647S9BVSo01Vw0oHlWHRW49jNR9KVEWTY5ADCIfypGcwR98IYqEh52kOmcZZj/UPP+xsa08 lm5nEzveSjoYFUfn6D7sUvcCujOVvVnaA+c944kCplvLjSvlWhO+2A2+ltIUuu5jt0wt4ibfkOJH5z VN4wmaF1Yk1MV6Hs=
Received: from mail.kirei.se (unknown [91.206.174.10]) by spg-relay.kirei.se (Halon Mail Gateway) with ESMTPS; Tue, 11 Sep 2012 15:25:36 +0200 (CEST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1486\))
From: Jakob Schlyter <jakob@kirei.se>
In-Reply-To: <046d01cd8fda$c5670d00$50352700$@augustcellars.com>
Date: Tue, 11 Sep 2012 15:25:34 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <7C162211-2928-46E5-83C3-CAEF246CD194@kirei.se>
References: <20120908161345.32470.87669.idtracker@ietfa.amsl.com> <577789DE-4A22-48D3-ACBE-8297B6C1DBCE@kirei.se> <046d01cd8fda$c5670d00$50352700$@augustcellars.com>
To: Jim Schaad <ietf@augustcellars.com>
X-Mailer: Apple Mail (2.1486)
Cc: 'IETF DANE WG list' <dane@ietf.org>
Subject: Re: [dane] FYI: New Version Notification for draft-hoffman-dane-smime-04.txt
X-BeenThere: dane@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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: <http://www.ietf.org/mail-archive/web/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: Tue, 11 Sep 2012 13:25:40 -0000

On 11 sep 2012, at 07:03, Jim Schaad <ietf@augustcellars.com> wrote:

> Problem #3 is almost impossible.  It would require that only end-entity
> certificate be listed, and this would mean that either it would be directly
> trusted or one would need to have both an EE certificate and a trust anchor
> listed in the DNS entry.  The capitalization issue would need to be
> addressed as in the previous paragraph, but is harder given that the sender
> may have never seen the mailbox name for the recipient and may be guessing
> at what the string should be if the DNS namespace is not over-populated.

I believe you somewhat exaggerating this problem. IMHO, the requirements you list are true but in no way a showstopper and I believe that publishing down-cased EE cert would be a very pragmatic and deployable way of doing this.

	jakob

v2.29.0 | Report a Bug | By Email | System Status