Re: [ldapext] Fwd: New Version Notification for draft-stroeder-mailboxrelatedobject-04.txt

Michael Ströder <michael@stroeder.com> Thu, 08 August 2013 18:39 UTC

Return-Path: <michael@stroeder.com>
X-Original-To: ldapext@ietfa.amsl.com
Delivered-To: ldapext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85ABE11E8163 for <ldapext@ietfa.amsl.com>; Thu, 8 Aug 2013 11:39:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.299
X-Spam-Level:
X-Spam-Status: No, score=-3.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
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 W6EmF41r5d31 for <ldapext@ietfa.amsl.com>; Thu, 8 Aug 2013 11:39:14 -0700 (PDT)
Received: from srv1.stroeder.com (srv1.stroeder.com [213.240.180.113]) by ietfa.amsl.com (Postfix) with ESMTP id 2C77211E80E2 for <ldapext@ietf.org>; Thu, 8 Aug 2013 11:39:13 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by srv1.stroeder.com (Postfix) with ESMTP id 941A460305; Thu, 8 Aug 2013 20:39:10 +0200 (CEST)
X-Virus-Scanned: amavisd-new at stroeder.com
Received: from srv1.stroeder.com ([127.0.0.1]) by localhost (srv1.stroeder.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NzFbb5kN1Cnm; Thu, 8 Aug 2013 20:39:06 +0200 (CEST)
Received: from nb2.stroeder.local (unknown [10.1.0.2]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by srv1.stroeder.com (Postfix) with ESMTPS id 93BD660207; Thu, 8 Aug 2013 18:39:05 +0000 (UTC)
Message-ID: <5203E5C9.3060704@stroeder.com>
Date: Thu, 08 Aug 2013 20:39:05 +0200
From: Michael Ströder <michael@stroeder.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:23.0) Gecko/20100101 Firefox/23.0 SeaMonkey/2.20
MIME-Version: 1.0
To: Alexey Melnikov <alexey.melnikov@isode.com>
References: <20130808072029.30689.91871.idtracker@ietfa.amsl.com> <520347AE.2080309@stroeder.com> <5203C9AA.20805@isode.com>
In-Reply-To: <5203C9AA.20805@isode.com>
X-Enigmail-Version: 1.5.2
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha1"; boundary="------------ms030003000702000000030904"
Cc: ldapext <ldapext@ietf.org>
Subject: Re: [ldapext] Fwd: New Version Notification for draft-stroeder-mailboxrelatedobject-04.txt
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ldapext>, <mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ldapext>, <mailto:ldapext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Aug 2013 18:39:29 -0000

Alexey,

Alexey Melnikov wrote:
> Some comments below:

Thanks for your time.

> 2.  Attribute Type Definition
> 
>    The attribute type 'intlMailAdr' is defined for storing SMTPUTF8
>    compliant addresses [RFC6530].
> 
>     ( 1.3.6.1.4.1.5427.1.389.4.18
>       NAME 'intlMailAdr'
>       DESC 'Internationalized Email Address'
>       EQUALITY caseIgnoreMatch
> 
> You describe problems with case-insensitive matching later in this section.
> Why not just use caseExactMatch? Strictly speaking left hand sides of email
> addresses are not ASCII case-insensitive.

1. The definition of 'mail' in RFC 4524 also defines case-insensitive matching
rules. Mainly the text pointing out the issue was taken from RFC 4524.

2. All applications are used to that. Note that the most important use-case is
searching for / completing an e-mail address. Case-insensitive matching by
default is more comfortable for that.

3. I'd rather expect only very few cases in which somebody want to add

intlMailAdr: joe@example.com
intlMailAdr: JOE@example.com

to a *single* entry meaning two *different* mailboxes. Do you know of any
deployment like this? What would be the semantics for that?
Note that 'intlMailAdr' is not meant as multi-valued attribute for mail group
entries for which such a case would be slightly more likely.
Also note that case-insensitive matching is a different thing to
case-preserving storage. I will add a note about the latter.

I'd appreciate if you propose text making this more clear if you feel it's needed.

> RFC 2821 --> RFC 5321.

Thanks. Updated all occurences in next version.

Ciao, Michael.