Re: [dane] Start of WGLC for draft-ietf-dane-openpgpkey - *please* review.

"Jim Schaad" <ietf@augustcellars.com> Mon, 23 February 2015 03:59 UTC

Return-Path: <ietf@augustcellars.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 A9B501A0163 for <dane@ietfa.amsl.com>; Sun, 22 Feb 2015 19:59:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
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 zRDSgWkljXwu for <dane@ietfa.amsl.com>; Sun, 22 Feb 2015 19:59:11 -0800 (PST)
Received: from smtp4.pacifier.net (smtp4.pacifier.net [64.255.237.176]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 571FC1A00F0 for <dane@ietf.org>; Sun, 22 Feb 2015 19:59:11 -0800 (PST)
Received: from Philemon (unknown [50.38.66.182]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp4.pacifier.net (Postfix) with ESMTPSA id C413A38EF2 for <dane@ietf.org>; Sun, 22 Feb 2015 19:59:10 -0800 (PST)
From: Jim Schaad <ietf@augustcellars.com>
To: dane@ietf.org
References: <CAHw9_iJPuG23Aok7V_wcAMirua_DPDLHy01tnd+DaUqEeK3NZA@mail.gmail.com> <001a01d04f19$b0292e90$107b8bb0$@augustcellars.com> <20150223035230.GD1260@mournblade.imrryr.org>
In-Reply-To: <20150223035230.GD1260@mournblade.imrryr.org>
Date: Sun, 22 Feb 2015 19:58:19 -0800
Message-ID: <001b01d04f1c$f626c940$e2745bc0$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGZrEAk8fO9l7kPFCFwPwE9DoqVVgHou59QAh//qxmdSpspIA==
Content-Language: en-us
Archived-At: <http://mailarchive.ietf.org/arch/msg/dane/TKkz1XKd--titbmBYK8A_qcEa-E>
Subject: Re: [dane] Start of WGLC for draft-ietf-dane-openpgpkey - *please* review.
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: <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, 23 Feb 2015 03:59:12 -0000


> -----Original Message-----
> From: dane [mailto:dane-bounces@ietf.org] On Behalf Of Viktor Dukhovni
> Sent: Sunday, February 22, 2015 7:53 PM
> To: dane@ietf.org
> Subject: Re: [dane] Start of WGLC for draft-ietf-dane-openpgpkey -
*please*
> review.
> 
> On Sun, Feb 22, 2015 at 07:34:53PM -0800, Jim Schaad wrote:
> 
> > 4.  In section 3, I strongly urge that the problem of case folding of
user
> > names be acknowledged.   I don't insist that the problem be solved.  (I
> > believe that it is not really solvable.)  However I strongly field
> > that the existence of the problem needs to be stated along with the fact
> that there
> > is no intention to solve it.   The problem statement can also easily
state
> > that this is a problem ONLY for US ASCII systems and not for UNICODE
> > systems as these are less likely to allow for case folding in the first
place.
> > (Does not need to be in section 3, but that seems to be the logical
> > place to put it.)
> 
> The problem *is* solvable.  Case-insensitive receiving domains, could
publish
> a case-folded version of the user name (hashed with a tag that prevents
> collisions in other domains, I proposed a concrete scheme some months
> back).  Senders could for the unmodified lookup key, and then for the
tagged
> case-folded key.

And what happens in the following case:

I am on a case sensitive receiving domain.
There are two recipients - JimSch and jimsch on the domain.
jimsch has a record but JimSch does not.
I now try and send mail to JimSch but get a key for jimsch.

Jim

> 
> The main question is whether we can reach consensus on wanting to solve it
> (for OPENPGPKEY and SMIMEA alike).  Solving is the easy part.
> 
> --
> 	Viktor.
> 
> _______________________________________________
> dane mailing list
> dane@ietf.org
> https://www.ietf.org/mailman/listinfo/dane