Re: [dane] Encoding local parts in better ways

Sean Leonard <dev+ietf@seantek.com> Tue, 06 October 2015 18:57 UTC

Return-Path: <dev+ietf@seantek.com>
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 38B101B29F5 for <dane@ietfa.amsl.com>; Tue, 6 Oct 2015 11:57:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.301
X-Spam-Level:
X-Spam-Status: No, score=-0.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MANGLED_TEXT=2.3, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001] 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 D-sdJWqUNnQG for <dane@ietfa.amsl.com>; Tue, 6 Oct 2015 11:57:28 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DAB4D1B29F3 for <dane@ietf.org>; Tue, 6 Oct 2015 11:57:27 -0700 (PDT)
Received: from [192.168.123.7] (unknown [75.83.2.34]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 1D735509C7; Tue, 6 Oct 2015 14:57:25 -0400 (EDT)
To: dane@ietf.org, John Levine <johnl@taugh.com>
References: <20150921035448.5523.qmail@ary.lan>
From: Sean Leonard <dev+ietf@seantek.com>
Message-ID: <56141976.5010704@seantek.com>
Date: Tue, 06 Oct 2015 11:56:54 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <20150921035448.5523.qmail@ary.lan>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="------------ms040804070108020108050701"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dane/Rg3l3rIWK_8Bwl071M3A94nnnkc>
Subject: Re: [dane] Encoding local parts in better ways
X-BeenThere: dane@ietf.org
X-Mailman-Version: 2.1.15
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: <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: Tue, 06 Oct 2015 18:57:29 -0000

I read draft-levine-dns-mailbox-01 with interest and have the following 
editorial comments (and one technical comment):

Section 1:
Many systems allow "extensions" such as john-ext or mary+ext

The term used in the vernacular is "sub-addressing" (in everything that 
I have seen), and the term in [RFC5233] is "subaddressing" (no hyphen) 
or "detailed addressing" (with space). "Plus addressing" (occasionally 
"plus-addressing") and "minus addressing" or "'minus' addressing" has 
also been seen in the wild. I would change that sentence to say that:

Many systems allow for subaddressing, such as "john-ext" or "mary+ext", 
where "john" or "mary" is treated as the effective local-part, and "ext" 
is passed as detail information to the recipient for further handling. 
See [RFC5233].


Section 4.1:
and synthesizes an key record,

change to:
and synthesizes a key record,


Technical:
Abstract
"and the DNS design that only does exact matching."

I thought that DNS uses ASCII labels, which are matched 
case-insensitively, and that there are no other modern options. 
[RFC4343] [RFC6891] False? See also Sections 3 and 4 in the I-D.

Sean

On 9/20/2015 8:54 PM, John Levine wrote:
> I've sent in a new version of draft-levine-dns-mailbox-01 that
> describes a bunch of ways to encode mail address local parts in ways
> that don't need canonicalization or address guessing.
>
> Take a particular look at section 5, which publishes regular
> expressions to match a domain's mail addresses.
>
> * Can represent any plausible local part syntax including case
> folding, noise characters, multiple ways to write Unicode characters,
> suffixes where some are ignored and some aren't, BATV, and VERP.
>
> * Reasonably fast lookup (max of one query per localpart character)
>
> * Works fine with static zones served by ordinary name servers .
>
> * Doesn't make bulk addresss harvesting easy.
>
> If you really want to do experiments in publishing mail info in the
> DNS, I think this would be a rather interesting one.
>
> R's,
> John