Re: [dane] email canonicalization for SMIMEA owner names

Viktor Dukhovni <> Sat, 13 December 2014 04:59 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id B1CD31A88AE for <>; Fri, 12 Dec 2014 20:59:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id K5cgHelPN4IS for <>; Fri, 12 Dec 2014 20:59:10 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 510921A0385 for <>; Fri, 12 Dec 2014 20:59:10 -0800 (PST)
Received: by (Postfix, from userid 1034) id 3E4E9282F8B; Sat, 13 Dec 2014 04:59:09 +0000 (UTC)
Date: Sat, 13 Dec 2014 04:59:09 +0000
From: Viktor Dukhovni <>
Message-ID: <>
References: <> <20141213044737.14765.qmail@ary.lan>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20141213044737.14765.qmail@ary.lan>
User-Agent: Mutt/1.5.23 (2014-03-12)
Subject: Re: [dane] email canonicalization for SMIMEA owner names
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DNS-based Authentication of Named Entities <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 13 Dec 2014 04:59:12 -0000

On Sat, Dec 13, 2014 at 04:47:37AM -0000, John Levine wrote:

> >I was thinking of multiplexing by port, rather than URI.  So that
> >the service in question really could be a light-weight HTTPS server
> >add-on to an MTA, rather than an HTTP application in a general
> >purpose HTTPS server.
> Before we go too far down this road, we might check with some people
> who run large mail systems and ask how likely they are to spin up an
> all new address verification server.  It doesn't seem very likely to
> me.
> The DNS has its faults, but it has the great advantage of already existing.

And of course ask them also how likely they are to publish per-user
keys in DNS, other than perhaps a wildcard trust-anchor.

In other words, were they to provide access to a key lookup service,
what are the relevant design constraints.

Perhaps Ian Fette can comment from a Gmail perspective.

Also do they see key lookup for encryption on first contact as a
requirement?  Or is signature-only first contact with encryption
keys provided optionally on reply, their preferred  model for
encryption key distribution.