Re: [dane] case sensitivity and draft-ietf-dane-smime / draft-wouters-dane-openpgp

Paul Wouters <paul@cypherpunks.ca> Mon, 09 September 2013 16:16 UTC

Return-Path: <paul@cypherpunks.ca>
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 BD4E021F9FAB for <dane@ietfa.amsl.com>; Mon, 9 Sep 2013 09:16:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.392
X-Spam-Level:
X-Spam-Status: No, score=-1.392 tagged_above=-999 required=5 tests=[AWL=1.207, BAYES_00=-2.599]
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 1kE5AB1Kh4Rv for <dane@ietfa.amsl.com>; Mon, 9 Sep 2013 09:16:35 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) by ietfa.amsl.com (Postfix) with ESMTP id CE96B21F999D for <dane@ietf.org>; Mon, 9 Sep 2013 08:50:01 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3cYYjM470Bz3nL for <dane@ietf.org>; Mon, 9 Sep 2013 11:49:59 -0400 (EDT)
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 64DG3eLc50wD for <dane@ietf.org>; Mon, 9 Sep 2013 11:49:58 -0400 (EDT)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) by mx.nohats.ca (Postfix) with ESMTP for <dane@ietf.org>; Mon, 9 Sep 2013 11:49:58 -0400 (EDT)
Received: by bofh.nohats.ca (Postfix, from userid 500) id B127E848E5; Mon, 9 Sep 2013 11:49:57 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id A57EC811F6 for <dane@ietf.org>; Mon, 9 Sep 2013 11:49:57 -0400 (EDT)
Date: Mon, 09 Sep 2013 11:49:57 -0400
From: Paul Wouters <paul@cypherpunks.ca>
X-X-Sender: paul@bofh.nohats.ca
To: dane WG list <dane@ietf.org>
In-Reply-To: <20130909151646.GM29796@mournblade.imrryr.org>
Message-ID: <alpine.LFD.2.10.1309091147050.14065@bofh.nohats.ca>
References: <alpine.LFD.2.10.1309091040120.14065@bofh.nohats.ca> <20130909151646.GM29796@mournblade.imrryr.org>
User-Agent: Alpine 2.10 (LFD 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format="flowed"; charset="US-ASCII"
Subject: Re: [dane] case sensitivity and draft-ietf-dane-smime / draft-wouters-dane-openpgp
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: Mon, 09 Sep 2013 16:16:40 -0000

On Mon, 9 Sep 2013, Viktor Dukhovni wrote:

> On Mon, Sep 09, 2013 at 10:52:26AM -0400, Paul Wouters wrote:
>
>> Mail servers and mail clients do not treat email addresses as
>> case-insensitive. When encoding an LHS with base32, the case matters.
>> Using the wrong case will cause you to not find the SMIMEA / OPENPGPKEY
>> record.
>
> This is not accurate.  While domain part of an email address is
> case-insensitive, the case-sensitivity of the local-part  is a
> local matter.  SMTP relays MUST NOT change the case of the local
> part of envelope addresses.  On arrival at the destination domain,
> that domain's mail system may choose to treat local-parts case
> insensitively, but remote systems must not rely on this.
>
> Therefore, <Paul@example.com> and <paul@example.com> are a-priori
> distinct addresses except perhaps in the hands of the MTAs that
> handle example.com mail.
>
> [ The fact that most systems are in practice case-insensitive is not
>  sufficient to invalidate the right of some to be case sensitive as
>  they see fit. ]

The _last_ thing I want to do is having an email client not encrypt a
message because someone mailed Paul@example.com instead of
paul@example.com.

So I think our choices are:

1) do a lookup for the case "as is" and a lookup for lowercased (serial
    or parallel)

2) lowercase and lookup once.

What I do _not_ think is a valid choice is "only do the as is case
lookup".

Paul