From owner-ietf-ldapbis@OpenLDAP.org  Fri Aug  1 01:31:44 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA27093
	for <ldapbis-archive@lists.ietf.org>; Fri, 1 Aug 2003 01:31:43 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h715Pj31058941;
	Fri, 1 Aug 2003 05:29:29 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h715P5eq058925;
	Fri, 1 Aug 2003 05:25:05 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Fri, 1 Aug 2003 05:25:05 +0000
Received: from adacel.com (gunsmoke.adacel.com.au [210.11.130.7])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h715P32v058910
	for <ietf-ldapbis@OpenLDAP.org>; Fri, 1 Aug 2003 05:25:04 GMT
	(envelope-from steven.legg@adacel.com.au)
Received: from nexus.adacel.com (Not Verified[10.32.240.1]) by adacel.com with NetIQ MailMarshal (v5.5.3.16)
	id <B00011f3f9>; Fri, 01 Aug 2003 15:20:40 +1000
Received: (qmail 4637 invoked from network); 1 Aug 2003 05:20:09 -0000
Received: from unknown (HELO osmium) (10.32.24.165)
  by nexus.adacel.com with SMTP; 1 Aug 2003 05:20:09 -0000
Reply-To: <steven.legg@adacel.com.au>
From: "Steven Legg" <steven.legg@adacel.com.au>
To: "'Jim Sermersheim'" <jimse@novell.com>, <ietf-ldapbis@OpenLDAP.org>
Subject: RE: Attribute Name Length Bounds
Date: Fri, 1 Aug 2003 15:24:40 +1000
Message-ID: <002101c357ed$356d0a30$a518200a@osmium.mtwav.adacel.com.au>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2120.0
In-Reply-To: <sf16a7e1.057@prv-mail20.provo.novell.com>
Importance: Normal
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


Jim,

Jim Sermersheim wrote:
> I also see that we could just add "or exceed server limits" to the end of
the phrase "or the
> encoding structures or lengths of data fields are found to be incorrect"
in the first
> paragraph. But I'm not sure...
>
> This section talks about data that is either malformed or cannot be/is not
recognized, so it
> seems like a good fit. It splits the problems into two classes (those that
cause the
> connection to terminate, and those that simply return protocolError).
>
> Adding the change above causes a connection termination. The change Bob
suggests allows one
> to differentiate between something that looks like an attack (say some
size is 20gb), and
> something that simply exceeds a small limit, and act accordingly.
>
> Which seems more correct to others (and do both seem incorrect to anyone)?

Returning protocolError in response to a limitation in the server does not
seem appropriate to me. A protocolError suggests that the client has done
something wrong when in fact it is the server that has the problem. The
unwillingToPerform error is more appropriate in such circumstances.

Regards,
Steven




From owner-ietf-ldapbis@OpenLDAP.org  Fri Aug  1 19:38:07 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17351
	for <ldapbis-archive@lists.ietf.org>; Fri, 1 Aug 2003 19:38:06 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h71NVp31006633;
	Fri, 1 Aug 2003 23:36:15 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h71NU8cv006608;
	Fri, 1 Aug 2003 23:30:08 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Fri, 1 Aug 2003 23:30:08 +0000
Received: from rembrandt.esys.ca (rembrandt.esys.ca [198.161.92.131])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h71NU72v006598
	for <ietf-ldapbis@OpenLDAP.org>; Fri, 1 Aug 2003 23:30:07 GMT
	(envelope-from Alexey.Melnikov@isode.com)
Received: from isode.com (1Cust140.tnt109.lnd4.gbr.da.uu.net [62.188.172.140])
	(authenticated)
	by rembrandt.esys.ca (8.11.6/8.11.0.Beta0) with ESMTP id h71NXZV17910;
	Fri, 1 Aug 2003 17:33:36 -0600
Message-ID: <3F2AEBBA.608@isode.com>
Date: Fri, 01 Aug 2003 23:37:46 +0100
From: Alexey Melnikov <Alexey.Melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Roger Harrison <roger_harrison@novell.com>
CC: LDAPBis WG <ietf-ldapbis@OpenLDAP.org>
Subject: Comments about draft-ietf-ldapbis-authmeth-05.txt
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

I've promised during LDAPbis meeting to send some comments regarding 
draft-ietf-ldapbis-authmeth-XX. Here they are:

1).
 >5.2.2.3. Error Conditions
 >  
 >   For either form of assertion, the server MUST verify that the
 >   client's authentication identity as supplied in its TLS credentials
 >   is permitted to be mapped to the asserted authorization identity.

This makes sense for the explicit assertion case, but seems to be 
ambiguous for the implicit case.
IMHO, the mapping can be done as two steps:
a). deriving LDAP authentication identity from TLS credentials; If this 
steps fails, EXTERNAL mechanism returns failure.
b). verify that the authorization identity is allowed for the derived 
authentication identity. This is always "noop" for the implicit case.
I am not sure that the text is saying this.

2).
 > 8.2. Digest Authentication

I am not sure why this section is required in the document. DIGEST-MD5 
is defined in a separate document and there should be nothing magical 
about its usage in LDAP. If DIGEST-MD5 description creates confusion for 
LDAP implementors, let's fix the DIGEST-MD5 document!
Also, this section tries to redefine DIGEST-MD5 behavior, which is 
explicitly prohibited by the SASL specification.

...
 
 >   An LDAP client MAY determine whether the server supports this
 >   mechanism by performing a search request on the root DSE, requesting
 >   the supportedSASLMechanisms attribute, and checking whether the
 >   string "DIGEST-MD5" is present as a value of this attribute.

This just repeats something that is true for all SASL mechanisms.
   
 >   In the first stage of authentication, when the client is performing
 >   an "initial authentication" as defined in section 2.1 of [RFC2831],
 >   the client sends a bind request in which the version number is 3,
 >   the authentication choice is sasl, the sasl mechanism name is
 >   "DIGEST-MD5", and the credentials are absent. The client then waits
 >   for a response from the server to this request.
 >  
 >   The server will respond with a bind response in which the resultCode
 >   is saslBindInProgress, and the serverSaslCreds field is present. The
 >   contents of this field is a string defined by "digest-challenge" in
 >   section 2.1.1 of [RFC2831].

This just repeats what DIGEST-MD5 already says. If you really want this 
information, I suggest you replace the text with an example example of 
how to use DIGEST-MD5 in LDAP.

 > The server SHOULD include a realm
 >   indication and MUST indicate support for UTF-8.

LDAP doesn't define what is "realm", so the first statement is not very 
helpful.

UTF-8 support is a MUST in the DIGEST-MD5 document anyway.

 >   The client will send a bind request with a distinct message id, in
 >   which the version number is 3, the authentication choice is sasl,
 >   the sasl mechanism name is "DIGEST-MD5", and the credentials contain
 >   the string defined by "digest-response" in section 2.1.2 of
 >   [RFC2831]. The serv-type is "ldap".

You probably already know what I would like to say about this ;-).
   
 >   The server will respond with a bind response in which the resultCode
 >   is either success, or an error indication. If the authentication is
 >   successful and the server does not support subsequent
 >   authentication, then the credentials field is absent. If the
 >   authentication is successful and the server supports subsequent
 >   authentication, then the credentials field contains the string
 >   defined by "response-auth" in section 2.1.3 of [RFC2831]. Support
 >   for subsequent authentication is OPTIONAL in clients and servers.

Subsequent authentication is optional, but the "response-auth" is not. 
It is used for mutual authentication and an LDAP document can't change 
how DIGEST-MD5 mechanism operates.
If this is not clear from the DIGEST-MD5 document, I can clarify this.

3).

 >   [RFC2222] Myers, J., "Simple Authentication and Security Layer
 >       (SASL)", draft-myers-saslrev-xx.txt, a work in progress.

This should be draft-ietf-sasl-rfc2222bis-xx.txt

Alexey





From owner-ietf-ldapbis@OpenLDAP.org  Sun Aug  3 22:13:42 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA02687
	for <ldapbis-archive@lists.ietf.org>; Sun, 3 Aug 2003 22:13:39 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h7428831066045;
	Mon, 4 Aug 2003 02:12:20 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h7422Wta065842;
	Mon, 4 Aug 2003 02:02:32 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 4 Aug 2003 02:02:32 +0000
Received: from ausyms50.ca.com ([155.35.248.106])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h7422T2v065796
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 4 Aug 2003 02:02:30 GMT
	(envelope-from Ron.Ramsay@ca.com)
Received: from ausyms21.ca.com ([155.35.201.5]) by ausyms50.ca.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Mon, 4 Aug 2003 12:02:08 +1000
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: Comments about draft-ietf-ldapbis-authmeth-05.txt
Date: Mon, 4 Aug 2003 12:02:08 +1000
Message-ID: <1395B4B334FCC143B36AF788E68B63815E1BD0@ausyms21.ca.com>
Thread-Topic: Comments about draft-ietf-ldapbis-authmeth-05.txt
Thread-Index: AcNYhbxN/Q11nbMYTXWnlqpxOU23dABpbE4g
From: "Ramsay, Ron" <Ron.Ramsay@ca.com>
To: "Alexey Melnikov" <Alexey.Melnikov@isode.com>
Cc: "LDAPBis WG" <ietf-ldapbis@OpenLDAP.org>
X-OriginalArrivalTime: 04 Aug 2003 02:02:08.0306 (UTC) FILETIME=[68FE4120:01C35A2C]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by boole.openldap.org id h7422U2v065833
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 8bit

I've previously raised concerns about using Digets-MD5 in LDAP. The form of the challenge-response requires structures foreign to LDAP - you mention the realm. An authentication method required for LDAP can really only make use of information like the DN or attributes in an entry identified by the DN. Kurt has recommended that servers generate the information require by Digest-MD5 using local knowledge, but I cannot agree with a required authentication method not using native LDAP "concepts".

Ron

-----Original Message-----
From: Alexey Melnikov [mailto:Alexey.Melnikov@isode.com]
Sent: Saturday, 2 August 2003 08:38
To: Roger Harrison
Cc: LDAPBis WG
Subject: Comments about draft-ietf-ldapbis-authmeth-05.txt


I've promised during LDAPbis meeting to send some comments regarding 
draft-ietf-ldapbis-authmeth-XX. Here they are:

1).
 >5.2.2.3. Error Conditions
 >  
 >   For either form of assertion, the server MUST verify that the
 >   client's authentication identity as supplied in its TLS credentials
 >   is permitted to be mapped to the asserted authorization identity.

This makes sense for the explicit assertion case, but seems to be 
ambiguous for the implicit case.
IMHO, the mapping can be done as two steps:
a). deriving LDAP authentication identity from TLS credentials; If this 
steps fails, EXTERNAL mechanism returns failure.
b). verify that the authorization identity is allowed for the derived 
authentication identity. This is always "noop" for the implicit case.
I am not sure that the text is saying this.

2).
 > 8.2. Digest Authentication

I am not sure why this section is required in the document. DIGEST-MD5 
is defined in a separate document and there should be nothing magical 
about its usage in LDAP. If DIGEST-MD5 description creates confusion for 
LDAP implementors, let's fix the DIGEST-MD5 document!
Also, this section tries to redefine DIGEST-MD5 behavior, which is 
explicitly prohibited by the SASL specification.

...
 
 >   An LDAP client MAY determine whether the server supports this
 >   mechanism by performing a search request on the root DSE, requesting
 >   the supportedSASLMechanisms attribute, and checking whether the
 >   string "DIGEST-MD5" is present as a value of this attribute.

This just repeats something that is true for all SASL mechanisms.
   
 >   In the first stage of authentication, when the client is performing
 >   an "initial authentication" as defined in section 2.1 of [RFC2831],
 >   the client sends a bind request in which the version number is 3,
 >   the authentication choice is sasl, the sasl mechanism name is
 >   "DIGEST-MD5", and the credentials are absent. The client then waits
 >   for a response from the server to this request.
 >  
 >   The server will respond with a bind response in which the resultCode
 >   is saslBindInProgress, and the serverSaslCreds field is present. The
 >   contents of this field is a string defined by "digest-challenge" in
 >   section 2.1.1 of [RFC2831].

This just repeats what DIGEST-MD5 already says. If you really want this 
information, I suggest you replace the text with an example example of 
how to use DIGEST-MD5 in LDAP.

 > The server SHOULD include a realm
 >   indication and MUST indicate support for UTF-8.

LDAP doesn't define what is "realm", so the first statement is not very 
helpful.

UTF-8 support is a MUST in the DIGEST-MD5 document anyway.

 >   The client will send a bind request with a distinct message id, in
 >   which the version number is 3, the authentication choice is sasl,
 >   the sasl mechanism name is "DIGEST-MD5", and the credentials contain
 >   the string defined by "digest-response" in section 2.1.2 of
 >   [RFC2831]. The serv-type is "ldap".

You probably already know what I would like to say about this ;-).
   
 >   The server will respond with a bind response in which the resultCode
 >   is either success, or an error indication. If the authentication is
 >   successful and the server does not support subsequent
 >   authentication, then the credentials field is absent. If the
 >   authentication is successful and the server supports subsequent
 >   authentication, then the credentials field contains the string
 >   defined by "response-auth" in section 2.1.3 of [RFC2831]. Support
 >   for subsequent authentication is OPTIONAL in clients and servers.

Subsequent authentication is optional, but the "response-auth" is not. 
It is used for mutual authentication and an LDAP document can't change 
how DIGEST-MD5 mechanism operates.
If this is not clear from the DIGEST-MD5 document, I can clarify this.

3).

 >   [RFC2222] Myers, J., "Simple Authentication and Security Layer
 >       (SASL)", draft-myers-saslrev-xx.txt, a work in progress.

This should be draft-ietf-sasl-rfc2222bis-xx.txt

Alexey







From owner-ietf-ldapbis@OpenLDAP.org  Mon Aug  4 15:07:54 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA08762
	for <ldapbis-archive@lists.ietf.org>; Mon, 4 Aug 2003 15:07:53 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h74IoE3T006882;
	Mon, 4 Aug 2003 19:02:35 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h74IjroM006592;
	Mon, 4 Aug 2003 18:45:53 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 4 Aug 2003 18:45:53 +0000
Received: from rembrandt.esys.ca (rembrandt.esys.ca [198.161.92.131])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h74Ijn2v006562;
	Mon, 4 Aug 2003 18:45:49 GMT
	(envelope-from Alexey.Melnikov@isode.com)
Received: from isode.com (1Cust106.tnt28.lnd4.gbr.da.uu.net [62.188.156.106])
	(authenticated)
	by rembrandt.esys.ca (8.11.6/8.11.0.Beta0) with ESMTP id h74InPV18535;
	Mon, 4 Aug 2003 12:49:26 -0600
Message-ID: <3F2EA479.6090303@isode.com>
Date: Mon, 04 Aug 2003 19:22:49 +0100
From: Alexey Melnikov <Alexey.Melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
CC: Roger Harrison <RHARRISON@novell.com>, ietf-ldapbis@OpenLDAP.org
Subject: Re: [authmeth] effect of StartTLS on authentication state
References: <5.2.0.9.0.20030701171553.01da9e50@127.0.0.1>
In-Reply-To: <5.2.0.9.0.20030701171553.01da9e50@127.0.0.1>
Content-Type: text/plain; charset=koi8-r; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

"Kurt D. Zeilenga" wrote:

> The obvious security consideration is that a client which does:
>         StartTLS+simple
> and a client which does
>         simple+StartTLS
>
> would (assuming both provided the same credentials and the negotiated
> the same security layers, association state diagram were followed)
> achieve the same apparent authorization state and protection levels when,
> in fact, the latter approach is prone to a number of obvious attacks.
>
> For the life of me, I cannot imagine why a client would do
>     simple+StartTLS+modify
> or even
>     simple+StartTLS+search-for-user-application-objects
>
> If the exchanged information is sensitive enough to warrant starting TLS,
> then it follows that password which provides access to that 
> information is
> equally sensitive and should be protected by TLS.
>
> It's my opinion that the RFC 2830, section 5.1.1 absolute
> imperative is inappropriate and actually in conflict with section 3.1.
> Authorization state diagram aside (its not normative), if a client does
> simple+StartTLS+X, the server is free, per section 3.1, to return
> strongAuthRequired for X.  And if 3.1 isn't enough, please consider
> access and administrative control models behavior is a local matter and
> servers are free to return security codes as necessary to implement
> the model they support.  Also, nothing in the LDAP TS should be viewed
> as precluding from lowering the effective access rights or otherwise
> placing restrictions upon clients for this or any other reason.
>
> It is not only reasonable that servers treat StartTLS+simple differently
> than simple+StartTLS, it makes good sense from a security perspective.  I
> believe that the OpenLDAP behavior (which is policy driven) of forcing 
> the
> session to anonymous upon StartTLS has significantly improved the 
> security
> of the Internet.  There are a lot less clients doing simple+StartTLS now
> and that is, IMO, a good thing.
>
I agree with what Kurt is saying about simple+StartTLS.

However I would like to comment on the original message. IMHO, it would 
be wrong to require that StartTLS will cause the return to anonymous 
state with any SASL mechanism (with the exception of PLAIN). Imagine 
that GSSAPI is used to authenticate and then the client decided to start 
TLS. GSSAPI but itself will be able to protect credentials, and it might 
be more secure than certain TLS ciphers.

> Kurt
>
> At 04:18 PM 7/1/2003, Roger Harrison wrote:
> >A WG member has asked whether the server should drop all knowledge of 
> the connection, i.e. return to anonymous state, if it gets a StartTLS 
> request on a connection that has successfully bound using the simple 
> method. I believe that the intent of section 5 the authmeth draft is 
> clear on this point: if the association is in state S4 (authenticated 
> but no TLS) and the client performs action A3 (sends a Start TLS 
> request), then the next association state is S5 (authenticated with TLS).
> >
> >My understanding of existing implementations leads me to believe that 
> this is the generally accepted understanding of the way this should 
> work.  I can't see any serious security issues with maintaining this 
> behavior. Therefore, I propose that we do not change this 
> requirement.  I will consider adding wording to clarify this point if 
> WG members request it.
> >
> >Please respond with your opinions.
>
 
Alexey Melnikov
__________________________________________
Home Page: http://orthanc.ab.ca/mel
IETF standard
related pages: http://orthanc.ab.ca/mel/devel/Links.html
__________________________________________
 





From owner-ietf-ldapbis@OpenLDAP.org  Mon Aug  4 15:07:55 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA08763
	for <ldapbis-archive@lists.ietf.org>; Mon, 4 Aug 2003 15:07:53 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h74IoE3V006882;
	Mon, 4 Aug 2003 19:03:38 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h74IjLrK006524;
	Mon, 4 Aug 2003 18:45:21 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 4 Aug 2003 18:45:21 +0000
Received: from rembrandt.esys.ca (rembrandt.esys.ca [198.161.92.131])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h74IjJ2v006514
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 4 Aug 2003 18:45:19 GMT
	(envelope-from Alexey.Melnikov@isode.com)
Received: from isode.com (1Cust106.tnt28.lnd4.gbr.da.uu.net [62.188.156.106])
	(authenticated)
	by rembrandt.esys.ca (8.11.6/8.11.0.Beta0) with ESMTP id h74ImcV18509;
	Mon, 4 Aug 2003 12:48:39 -0600
Message-ID: <3F2E7793.1070900@isode.com>
Date: Mon, 04 Aug 2003 16:11:15 +0100
From: Alexey Melnikov <Alexey.Melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Ramsay, Ron" <Ron.Ramsay@ca.com>
CC: LDAPBis WG <ietf-ldapbis@OpenLDAP.org>
Subject: Re: Comments about draft-ietf-ldapbis-authmeth-05.txt
References: <1395B4B334FCC143B36AF788E68B63815E1BD0@ausyms21.ca.com>
In-Reply-To: <1395B4B334FCC143B36AF788E68B63815E1BD0@ausyms21.ca.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Ramsay, Ron wrote:

>I've previously raised concerns about using Digets-MD5 in LDAP. The form of the challenge-response requires structures foreign to LDAP - you mention the realm.
>
The concept of realm in DIGEST-MD5 came from HTTP. But this concept is 
not HTTP specific, e.g. Kerberos uses it as well.
But let's not debate on this mailing list whether this is was a good or 
bad idea.

> An authentication method required for LDAP can really only make use of information like the DN or attributes in an entry identified by the DN. Kurt has recommended that servers generate the information require by Digest-MD5 using local knowledge, but I cannot agree with a required authentication method not using native LDAP "concepts".
>
The problem I have with the document is that it references realm without 
explaining what it is (or at least some examples of valid values). For 
LDAP, some recommendations should be given. For example:
1). Use a hardcoded string as the realm (one of the implementations I 
worked on was doing that)
2). Use hostname (realm==host) or domain/cluster name (realm includes 
multiple hosts).
3). Use a node in DIT above user entry, for example for "cn=Barbara 
Jensen, ou=Accounting, o=Ace Industry, c=US"
 and "cn=John Doe, ou=Accounting, o=Ace Industry, c=US" realm can be 
"ou=Accounting, o=Ace Industry, c=US"
(or "o=Ace Industry, c=US"); for "cn=Gern Jensen, ou=Product Testing, 
o=Ace Industry, c=US" realm can be
"ou=Product Testing, o=Ace Industry, c=US".

Of course other choices are possible.

Alexey





From owner-ietf-ldapbis@OpenLDAP.org  Mon Aug  4 15:56:28 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA08781
	for <ldapbis-archive@lists.ietf.org>; Mon, 4 Aug 2003 15:07:55 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h74IoE3X006882;
	Mon, 4 Aug 2003 19:03:38 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h74IjHdf006507;
	Mon, 4 Aug 2003 18:45:17 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 4 Aug 2003 18:45:17 +0000
Received: from rembrandt.esys.ca (rembrandt.esys.ca [198.161.92.131])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h74IjF2v006497
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 4 Aug 2003 18:45:15 GMT
	(envelope-from Alexey.Melnikov@isode.com)
Received: from isode.com (1Cust106.tnt28.lnd4.gbr.da.uu.net [62.188.156.106])
	(authenticated)
	by rembrandt.esys.ca (8.11.6/8.11.0.Beta0) with ESMTP id h74ImqV18519;
	Mon, 4 Aug 2003 12:48:53 -0600
Message-ID: <3F2EA180.2090907@isode.com>
Date: Mon, 04 Aug 2003 19:10:08 +0100
From: Alexey Melnikov <Alexey.Melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Roger Harrison <roger_harrison@novell.com>
CC: LDAPBis WG <ietf-ldapbis@OpenLDAP.org>
Subject: Comments about draft-ietf-ldapbis-authmeth-06.txt
References: <1395B4B334FCC143B36AF788E68B63815E1BD0@ausyms21.ca.com>
In-Reply-To: <1395B4B334FCC143B36AF788E68B63815E1BD0@ausyms21.ca.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

More comments:

1). In 4.1.4

   If the client or server decides that the level of authentication or
   privacy is not high enough for it to continue, it SHOULD gracefully
   close the TLS connection immediately after the TLS negotiation has
   completed (see [Protocol] section 4.13.3.1 and section 4.2.3 below).
   If the client decides to continue, it MAY attempt to Start TLS
   again,

I though this is not allowed as it contradicts text in

 >5.1.1. Requesting to Start TLS on an LDAP Association
 >
 >   The client MAY send the Start TLS extended request at any time after
 >   establishing an LDAP association, except that in the following cases
 >   the client MUST NOT send a Start TLS extended request:
 >
 >        - if TLS is currently established on the connection, or
 >        - during a multi-stage SASL negotiation, or
 >        - if there are any LDAP operations outstanding on the
 >          connection.
 >

The text is ambiguous. either the client will have to perform graceful 
TLS closure and then restart TLS, or the client is allowed to restart 
TLS without TLS closure, even though TLS is already negotiated.

2).

 >4.2.3. TLS Connection Closure Effects
 >  
 >   Closure of the TLS session MUST cause the LDAP association to move
 >   to an anonymous authentication and authorization state regardless of
 >   the state established over TLS and regardless of the authentication
 >   and authorization state prior to TLS session establishment.

Ok, this was discussed before, so I might be missing some context.
But is there any good reason for this?

3).
 >7.3.1. "simple" Authentication Choice 
 > 
 >   DSAs that map the DN sent in the bind request to a directory entry
 >   with an associated set of one or more passwords will compare the
 >   presented password to the set of passwords associated with that
 >   entry. If there is a match, then the server will respond with
 >   resultCode success, otherwise the server will respond with
 >   resultCode invalidCredentials.

Does this allow for hashed passwords?

=========

Editorial:

1). In 4.1.:

   Note that the precise effects, on a client's authorization identity,
   of establishing TLS on an LDAP association are described in detail
   in section 4.5.

 No such section.

 There is a reference to 4.5.1.2 in some other place as well.

2).

 >G.32 Clarification on use of SASL mechanisms
 >  
 >   Section 3.3.1: BTW, what _are_ the "ANONYMOUS" and "PLAIN" SASL
 >   mechanisms?  They are not defined in RFC2222.  If you refer to other
 >   SASL mechanisms than those in rfc2222, Maybe you should only list
 >   which mechanisms _are_used, instead of which ones are _not. (Source:
 >   Hallvard Furuseth)

Changes to Normative References section should deal with this issue.

Add:

    [ANONYMOUS] Zeilenga, K.,"Anonymous SASL Mechanism",
    draft-zeilenga-sasl-anon-xx.txt, a work in progress.
(this will replace ANONYMOUS definition in RFC 2245)

    [PLAIN] Zeilenga, K.,"Plain SASL Mechanism",
    draft-zeilenga-sasl-plain-xx.txt, a work in progress.
(this will replace plain definition in RFC 2595)
 
Replace:
    [RFC2831] Leach, P. and C. Newman, "Using Digest Authentication as
      a SASL Mechanism", RFC 2831, May 2000. 
with
    [RFC2831] Leach, P., Newman, C., Melnikov, A., "Using Digest 
Authentication as
      a SASL Mechanism", draft-ietf-sasl-rfc2831bis-xx.txt, a work in 
progress.

Alexey





From owner-ietf-ldapbis@OpenLDAP.org  Tue Aug  5 00:22:48 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA19564
	for <ldapbis-archive@lists.ietf.org>; Tue, 5 Aug 2003 00:22:45 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h754EH31037766;
	Tue, 5 Aug 2003 04:16:07 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h754CFmq037735;
	Tue, 5 Aug 2003 04:12:15 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 5 Aug 2003 04:12:15 +0000
Received: from ausyms50.ca.com ([155.35.248.106])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h754CD2v037724
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 5 Aug 2003 04:12:14 GMT
	(envelope-from Ron.Ramsay@ca.com)
Received: from ausyms21.ca.com ([155.35.201.5]) by ausyms50.ca.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 5 Aug 2003 14:12:02 +1000
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: Comments about draft-ietf-ldapbis-authmeth-05.txt
Date: Tue, 5 Aug 2003 14:12:02 +1000
Message-ID: <1395B4B334FCC143B36AF788E68B638160BC40@ausyms21.ca.com>
Thread-Topic: Comments about draft-ietf-ldapbis-authmeth-05.txt
Thread-Index: AcNauJJ9mYZpKzQ0Sqm7BqJA9TEtbgATmtMQ
From: "Ramsay, Ron" <Ron.Ramsay@ca.com>
To: "Alexey Melnikov" <Alexey.Melnikov@isode.com>
Cc: "LDAPBis WG" <ietf-ldapbis@OpenLDAP.org>
X-OriginalArrivalTime: 05 Aug 2003 04:12:02.0743 (UTC) FILETIME=[B940B470:01C35B07]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by boole.openldap.org id h754CE2v037726
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 8bit

Good point. I note that RFC 2831 also allows the empty string for the realm.

But what about storing the password. The ideal would be to store the username/realm/password hash. But the username is a DN(?) and it doesn't have a canonical value. Yet the value used to precalculate the hash must agree with the value that the client is going to use when connecting. Do you have any suggestions about this?

Ron

-----Original Message-----
From: Alexey Melnikov [mailto:Alexey.Melnikov@isode.com]
Sent: Tuesday, 5 August 2003 01:11
To: Ramsay, Ron
Cc: LDAPBis WG
Subject: Re: Comments about draft-ietf-ldapbis-authmeth-05.txt


Ramsay, Ron wrote:

>I've previously raised concerns about using Digets-MD5 in LDAP. The form of the challenge-response requires structures foreign to LDAP - you mention the realm.
>
The concept of realm in DIGEST-MD5 came from HTTP. But this concept is 
not HTTP specific, e.g. Kerberos uses it as well.
But let's not debate on this mailing list whether this is was a good or 
bad idea.

> An authentication method required for LDAP can really only make use of information like the DN or attributes in an entry identified by the DN. Kurt has recommended that servers generate the information require by Digest-MD5 using local knowledge, but I cannot agree with a required authentication method not using native LDAP "concepts".
>
The problem I have with the document is that it references realm without 
explaining what it is (or at least some examples of valid values). For 
LDAP, some recommendations should be given. For example:
1). Use a hardcoded string as the realm (one of the implementations I 
worked on was doing that)
2). Use hostname (realm==host) or domain/cluster name (realm includes 
multiple hosts).
3). Use a node in DIT above user entry, for example for "cn=Barbara 
Jensen, ou=Accounting, o=Ace Industry, c=US"
 and "cn=John Doe, ou=Accounting, o=Ace Industry, c=US" realm can be 
"ou=Accounting, o=Ace Industry, c=US"
(or "o=Ace Industry, c=US"); for "cn=Gern Jensen, ou=Product Testing, 
o=Ace Industry, c=US" realm can be
"ou=Product Testing, o=Ace Industry, c=US".

Of course other choices are possible.

Alexey







From owner-ietf-ldapbis@OpenLDAP.org  Tue Aug  5 15:36:15 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25737
	for <ldapbis-archive@lists.ietf.org>; Tue, 5 Aug 2003 15:36:14 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h75JWn39004239;
	Tue, 5 Aug 2003 19:35:04 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h75JObKX003758;
	Tue, 5 Aug 2003 19:24:37 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 5 Aug 2003 19:24:37 +0000
Received: from nwkea-mail-1.sun.com (nwkea-mail-1.sun.com [192.18.42.13])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h75JOa2v003725
	for <ietf-ldapbis@openldap.org>; Tue, 5 Aug 2003 19:24:36 GMT
	(envelope-from steve.hanna@sun.com)
Received: from sydney.East.Sun.COM ([129.148.9.16])
	by nwkea-mail-1.sun.com (8.12.9/8.12.9) with ESMTP id h75JO5gn016466;
	Tue, 5 Aug 2003 12:24:05 -0700 (PDT)
Received: from sun.com (dhcp-ubur02-75-161 [129.148.75.161])
	by sydney.East.Sun.COM (8.11.7+Sun/8.11.7/ENSMAIL,v2.2) with ESMTP id h75JO4s09772;
	Tue, 5 Aug 2003 15:24:04 -0400 (EDT)
Message-ID: <3F300382.A68451FF@sun.com>
Date: Tue, 05 Aug 2003 15:20:34 -0400
From: Steve Hanna <steve.hanna@sun.com>
X-Mailer: Mozilla 4.79 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: PKIX List <ietf-pkix@imc.org>, ietf-ldapbis@OpenLDAP.org
Subject: PKIX LDAPv3 schema: component matching or separate entries
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------msA8B46CA38210A350F106092D"
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

This is a cryptographically signed message in MIME format.

--------------msA8B46CA38210A350F106092D
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

The draft minutes from the IETF 57 PKIX WG meeting say:

> LDAP Documents: - David Chadwick (Univ of Salford) & Peter Gietz
>                (DAASI)
> The WG has a suite of LDAP-PKIX drafts forming a comprehensive
> solution for LDAP based PKI information distribution.

I believe that the PK certificate schema is described in
draft-klasen-ldap-x509certificate-schema-03.txt.

That document (and the CRL and AC schemas) proposes a
change from storing certificates in the multi-valued
userCertificate and cACertificate attributes of an
entity's directory entry to storing certificates as
separate directory entries, subordinate to the entity's
directory entry. Values may then be extracted from
certificate fields and placed in attributes on the
certificate's directory entry so that it's easier to
search for certificates and retrieve only those you want.

At IETF 56, there was a discussion about whether to make
this change or stick with the current schema and use
component matching to solve the problem. As noted in the
meeting minutes, a straw poll favored component matching
but it was agreed to take this discussion to the mailing
list. I haven't seen any discussion on the mailing list,
but now it seems that the matter has been decided in favor
of the modified schema.

Did I miss something? Was this discussed and agreed to on
the mailing list? If not, it should be discussed here.

I would like to hear from customers who are using the old
schema as to whether they will be happy moving to the new
schema. I'm concerned that they may be reluctant to double
or triple the number of entries in their directory.

Thanks,

Steve Hanna
--------------msA8B46CA38210A350F106092D
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIIIEAYJKoZIhvcNAQcCoIIIATCCB/0CAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
BeMwggKjMIICDKADAgECAgMKVAgwDQYJKoZIhvcNAQEEBQAwgZIxCzAJBgNVBAYTAlpBMRUw
EwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEPMA0GA1UEChMGVGhh
d3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNlczEoMCYGA1UEAxMfUGVyc29uYWwg
RnJlZW1haWwgUlNBIDIwMDAuOC4zMDAeFw0wMzA3MTExMTAxNTFaFw0wNDA3MTAxMTAxNTFa
MGgxDjAMBgNVBAQTBUhhbm5hMRUwEwYDVQQqEwxTdGVwaGVuIFJvc3MxGzAZBgNVBAMTElN0
ZXBoZW4gUm9zcyBIYW5uYTEiMCAGCSqGSIb3DQEJARYTc3RldmUuaGFubmFAc3VuLmNvbTCB
nzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAoxRk/abMPe7Km2EqpD2FZXzjiBGUHhIdNlIO
9W6mdCQro1xMc+sv+93UuVnIzse+XA67Tqx4g5FdoQ+PI8TQYemYSkTD9GitgU563ypu03UV
86zTJA7u9zVkNv/qL2LRKZ9BXy2Smtet+PUh3nYjMh/ZY7LQxQzmdu1Zunue+yECAwEAAaMw
MC4wHgYDVR0RBBcwFYETc3RldmUuaGFubmFAc3VuLmNvbTAMBgNVHRMBAf8EAjAAMA0GCSqG
SIb3DQEBBAUAA4GBAHbpX0TKiOFu1vxKc3nAOcUHwoci5kinboYrnjWcl37mMXXbBFntaYRM
9LxpGtHdPm7F4pAviKp8bnFzTU46OyUw3kNUAVGDeWYVQC76f0dDZdA313Tn88UZYa+N6O8W
bO8wjKA2vg+yx79WXJCFDu+TpsG/28NKPdH42w8LEOVHMIIDODCCAqGgAwIBAgIQZkVyt8x0
9c9jdkWE0C6RATANBgkqhkiG9w0BAQQFADCB0TELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdl
c3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2FwZSBUb3duMRowGAYDVQQKExFUaGF3dGUgQ29uc3Vs
dGluZzEoMCYGA1UECxMfQ2VydGlmaWNhdGlvbiBTZXJ2aWNlcyBEaXZpc2lvbjEkMCIGA1UE
AxMbVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIENBMSswKQYJKoZIhvcNAQkBFhxwZXJzb25h
bC1mcmVlbWFpbEB0aGF3dGUuY29tMB4XDTAwMDgzMDAwMDAwMFoXDTA0MDgyNzIzNTk1OVow
gZIxCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUg
VG93bjEPMA0GA1UEChMGVGhhd3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNlczEo
MCYGA1UEAxMfUGVyc29uYWwgRnJlZW1haWwgUlNBIDIwMDAuOC4zMDCBnzANBgkqhkiG9w0B
AQEFAAOBjQAwgYkCgYEA3jMypmPHCSVFPtJueCdngcXaiBmClw7jRCmKYzUqbXA8+tyu9+50
bzC8M5B/+TRxoKNtmPHDT6Jl2w36S/HW3WGl+YXNVZo1Gp2Sdagnrthy+boC9tewkd4c6avg
GAOofENCUFGHgzzwObSbVIoTh/+zm51JZgAtCYnslGvpoWkCAwEAAaNOMEwwKQYDVR0RBCIw
IKQeMBwxGjAYBgNVBAMTEVByaXZhdGVMYWJlbDEtMjk3MBIGA1UdEwEB/wQIMAYBAf8CAQAw
CwYDVR0PBAQDAgEGMA0GCSqGSIb3DQEBBAUAA4GBADGxS0dd+QFx5fVTbF151j2YwCYTYoEi
pxL4IpXoG0m3J3sEObr85vIk65H6vewNKjj3UFWobPcNrUwbvAP0teuiR59sogxYjTFCCRFs
sBpp0SsSskBdavl50OouJd2K5PzbDR+dAvNa28o89kTqJmmHf0iezqWf54TYyWJirQXGMYIB
9TCCAfECAQEwgZowgZIxCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQ
BgNVBAcTCUNhcGUgVG93bjEPMA0GA1UEChMGVGhhd3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0
ZSBTZXJ2aWNlczEoMCYGA1UEAxMfUGVyc29uYWwgRnJlZW1haWwgUlNBIDIwMDAuOC4zMAID
ClQIMAkGBSsOAwIaBQCggbEwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0B
CQUxDxcNMDMwODA1MTkyMDM0WjAjBgkqhkiG9w0BCQQxFgQUrfqxe5CzYfX+T448xNeKpFPn
5oswUgYJKoZIhvcNAQkPMUUwQzAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwBwYFKw4D
AgcwDQYIKoZIhvcNAwICAUAwDQYIKoZIhvcNAwICASgwDQYJKoZIhvcNAQEBBQAEgYB7EzNB
XGagVQqHlXMmK2NbFRNvZrLpjj03Rqer9xbn3jkRy2pB7qbIeU7b9bN1Zv0P/TyACzlkhu+2
1hM2WRbuoD6VUaj+HnSokemv6YaZMk16HTdqkN5WBaWSIi7OvNAwwLLe1QYH5VSehUzR+9ZD
cym4+lBilD+YS+e9qgiTWA==
--------------msA8B46CA38210A350F106092D--



From owner-ietf-ldapbis@OpenLDAP.org  Wed Aug  6 15:36:12 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01848
	for <ldapbis-archive@lists.ietf.org>; Wed, 6 Aug 2003 15:36:08 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h76JQX37039465;
	Wed, 6 Aug 2003 19:31:13 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h76JKN1E038951;
	Wed, 6 Aug 2003 19:20:23 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 6 Aug 2003 19:20:23 +0000
Received: from tconl91223.tconl.com (tconl91223.tconl.com [204.26.91.223])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h76JKL2v038929
	for <ietf-ldapbis@openldap.org>; Wed, 6 Aug 2003 19:20:22 GMT
	(envelope-from jayhawk@tconl91223.tconl.com)
Received: (from jayhawk@localhost)
	by tconl91223.tconl.com (8.11.6/8.11.0) id h76JK1x03790
	for ietf-ldapbis@openldap.org; Wed, 6 Aug 2003 14:20:01 -0500
Date: Wed, 6 Aug 2003 14:20:00 -0500
From: Ryan Moats <rmoats@lemurnetworks.net>
To: ietf-ldapbis@OpenLDAP.org
Subject: LDAPBIS minutes?
Message-ID: <20030806142000.T2028@privateer.local.windrose.omaha.ne.us>
Reply-To: rmoats@lemurnetworks.net
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

I don't think I've seen minutes from Vienna posted to the list.  Is that
the case or did I just miss them?  I ask because I understand that
name limits were discussed in Vienna and then moved to the list, but I've
not seen anything about it since then.

Ryan


From owner-ietf-ldapbis@OpenLDAP.org  Wed Aug  6 16:02:05 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02607
	for <ldapbis-archive@lists.ietf.org>; Wed, 6 Aug 2003 16:02:05 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h76Jue31041273;
	Wed, 6 Aug 2003 19:57:01 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h76Jm2Vi040680;
	Wed, 6 Aug 2003 19:48:02 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 6 Aug 2003 19:48:02 +0000
Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h76Jm12v040643
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 6 Aug 2003 19:48:01 GMT
	(envelope-from rlmorgan@washington.edu)
Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139])
	by mxout3.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h76JlNgG028558;
	Wed, 6 Aug 2003 12:47:23 -0700
Received: from D-140-142-21-96.dhcp4.washington.edu (D-140-142-21-96.dhcp4.washington.edu [140.142.21.96])
	(authenticated bits=0)
	by smtp.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h76JlM4A006680
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT);
	Wed, 6 Aug 2003 12:47:22 -0700
Date: Wed, 6 Aug 2003 12:47:22 -0700 (PDT)
From: "RL 'Bob' Morgan" <rlmorgan@washington.edu>
X-X-Sender: rlmorgan@localhost.localdomain
To: Ryan Moats <rmoats@lemurnetworks.net>
cc: IETF ldapbis WG <ietf-ldapbis@OpenLDAP.org>
Subject: Re: LDAPBIS minutes?
In-Reply-To: <20030806142000.T2028@privateer.local.windrose.omaha.ne.us>
Message-ID: <Pine.LNX.4.44.0308061247001.4637-100000@localhost.localdomain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>


I'll be sending them out shortly, sorry for the delay.

 - RL "Bob"

On Wed, 6 Aug 2003, Ryan Moats wrote:

> I don't think I've seen minutes from Vienna posted to the list.  Is that
> the case or did I just miss them?  I ask because I understand that
> name limits were discussed in Vienna and then moved to the list, but I've
> not seen anything about it since then.
>
> Ryan



From owner-ietf-ldapbis@OpenLDAP.org  Thu Aug  7 09:52:35 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA12319
	for <ldapbis-archive@lists.ietf.org>; Thu, 7 Aug 2003 09:52:34 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h77Doa2x006601;
	Thu, 7 Aug 2003 13:50:53 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h77DhgFg005834;
	Thu, 7 Aug 2003 13:43:42 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 7 Aug 2003 13:43:42 +0000
Received: from sottmxssm.entrust.com (sottmxssm.entrust.com [216.191.252.10])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h77Dhe2v005723
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 7 Aug 2003 13:43:41 GMT
	(envelope-from sharon.boeyen@entrust.com)
Received: from sottguard01.entrust.com (sottguard01.entrust.com [10.4.61.249])
	by sottmxssm.entrust.com (Switch-2.2.6/Switch-2.2.4) with SMTP id V77D23SA28489
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 07 Aug 2003 09:39:29 -0400
Received: (qmail 22532 invoked by uid 64014); 7 Aug 2003 13:36:18 -0000
Received: from sharon.boeyen@entrust.com by sottguard01.entrust.com with AmikaGuardian-Server-1.1.2 (Processed in 0.117366 secs); 07 Aug 2003 13:36:18 -0000
Received: from unknown (HELO SOTTMXS01.entrust.com) (10.4.61.7)
  by sottguard01.entrust.com with SMTP; 7 Aug 2003 13:36:18 -0000
Received: by sottmxs01.entrust.com with Internet Mail Service (5.5.2656.59)
	id <QMF1YDDN>; Thu, 7 Aug 2003 09:43:12 -0400
Message-ID: <9A4F653B0A375841AC75A8D17712B9C9061AC43C@sottmxs04.entrust.com>
From: Sharon Boeyen <sharon.boeyen@entrust.com>
To: "'Steve Hanna'" <steve.hanna@sun.com>, PKIX List <ietf-pkix@imc.org>,
        ietf-ldapbis@OpenLDAP.org
Subject: RE: PKIX LDAPv3 schema: component matching or separate entries
Date: Thu, 7 Aug 2003 09:43:12 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: application/x-pkcs7-mime;
	name="smime.p7m"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename="smime.p7m"
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: base64

MIInNAYJKoZIhvcNAQcCoIInJTCCJyECAQExCzAJBgUrDgMCGgUAMIIZggYJKoZIhvcNAQcBoIIZ
cwSCGW9Db250ZW50LVR5cGU6IG11bHRpcGFydC9hbHRlcm5hdGl2ZTsNCglib3VuZGFyeT0iLS09
X05leHRQYXJ0X1NUSl84ODczOTk2OC4wOTQ1NDI3MTQiDQoNCg0KLS0tLT1fTmV4dFBhcnRfU1RK
Xzg4NzM5OTY4LjA5NDU0MjcxNA0KQ29udGVudC1UeXBlOiB0ZXh0L3BsYWluOw0KCWNoYXJzZXQ9
IlVTLUFTQ0lJIg0KQ29udGVudC1UcmFuc2Zlci1FbmNvZGluZzogcXVvdGVkLXByaW50YWJsZQ0K
DQpTdGV2ZSBJIGNlcnRhaW5seSBzaGFyZSB5b3VyIGNvbmNlcm5zLiBJIGRvbid0IGJlbGlldmUg
ZXhpc3Rpbmc9MjANCmRlcGxveWVkIHN5c3RlbXMgd2lsbCBtb2RpZnkgdGhlaXIgc2NoZW1hLiBU
aGV5IGFyZSB3b3JraW5nIGp1c3Q9MjANCmZpbmUgdGhlIHdheSB0aGV5IGFyZSBhbmQgaGF2ZSBu
byByZWFzb24gdG8gY2hhbmdlLiBBbHNvLCBmcm9tPTIwDQphbiBpbnRlcm9wZXJhYmlsaXR5IHN0
YW5kcG9pbnQgSSBleHBlY3QgZ3JlYXQgcmVsdWN0YW5jZSB0byBtb3ZlPTIwDQp0byB0aGUgc2No
ZW1hIGluIHJlYWwgd29ybGQgZGVwbG95bWVudHMgdGhhdCBuZWVkIHRvIGludGVyb3Agd2l0aD0y
MA0KZXhpc3Rpbmcgb25lcyB1c2luZyB0aGUgb2xkIHNjaGVtYS4NCg0KU2hhcm9uDQoNCi0tLS0t
T3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBTdGV2ZSBIYW5uYSA9NUJtYWlsdG86c3RldmUu
aGFubmE9NDBzdW4uY29tPTVEDQpTZW50OiBUdWVzZGF5LCBBdWd1c3QgMDUsIDIwMDMgMzoyMSBQ
TQ0KVG86IFBLSVggTGlzdDsgaWV0Zi1sZGFwYmlzPTQwT3BlbkxEQVAub3JnDQpTdWJqZWN0OiBQ
S0lYIExEQVB2MyBzY2hlbWE6IGNvbXBvbmVudCBtYXRjaGluZyBvciBzZXBhcmF0ZSBlbnRyaWVz
DQoNCg0KVGhlIGRyYWZ0IG1pbnV0ZXMgZnJvbSB0aGUgSUVURiA1NyBQS0lYIFdHIG1lZXRpbmcg
c2F5Og0KDQo+IExEQVAgRG9jdW1lbnRzOiAtIERhdmlkIENoYWR3aWNrIChVbml2IG9mIFNhbGZv
cmQpICYgUGV0ZXIgR2lldHoNCj4gICAgICAgICAgICAgICAgKERBQVNJKQ0KPiBUaGUgV0cgaGFz
IGEgc3VpdGUgb2YgTERBUC1QS0lYIGRyYWZ0cyBmb3JtaW5nIGEgY29tcHJlaGVuc2l2ZQ0KPiBz
b2x1dGlvbiBmb3IgTERBUCBiYXNlZCBQS0kgaW5mb3JtYXRpb24gZGlzdHJpYnV0aW9uLg0KDQpJ
IGJlbGlldmUgdGhhdCB0aGUgUEsgY2VydGlmaWNhdGUgc2NoZW1hIGlzIGRlc2NyaWJlZCBpbg0K
ZHJhZnQta2xhc2VuLWxkYXAteDUwOWNlcnRpZmljYXRlLXNjaGVtYS0wMy50eHQuDQoNClRoYXQg
ZG9jdW1lbnQgKGFuZCB0aGUgQ1JMIGFuZCBBQyBzY2hlbWFzKSBwcm9wb3NlcyBhDQpjaGFuZ2Ug
ZnJvbSBzdG9yaW5nIGNlcnRpZmljYXRlcyBpbiB0aGUgbXVsdGktdmFsdWVkDQp1c2VyQ2VydGlm
aWNhdGUgYW5kIGNBQ2VydGlmaWNhdGUgYXR0cmlidXRlcyBvZiBhbg0KZW50aXR5J3MgZGlyZWN0
b3J5IGVudHJ5IHRvIHN0b3JpbmcgY2VydGlmaWNhdGVzIGFzDQpzZXBhcmF0ZSBkaXJlY3Rvcnkg
ZW50cmllcywgc3Vib3JkaW5hdGUgdG8gdGhlIGVudGl0eSdzDQpkaXJlY3RvcnkgZW50cnkuIFZh
bHVlcyBtYXkgdGhlbiBiZSBleHRyYWN0ZWQgZnJvbQ0KY2VydGlmaWNhdGUgZmllbGRzIGFuZCBw
bGFjZWQgaW4gYXR0cmlidXRlcyBvbiB0aGUNCmNlcnRpZmljYXRlJ3MgZGlyZWN0b3J5IGVudHJ5
IHNvIHRoYXQgaXQncyBlYXNpZXIgdG8NCnNlYXJjaCBmb3IgY2VydGlmaWNhdGVzIGFuZCByZXRy
aWV2ZSBvbmx5IHRob3NlIHlvdSB3YW50Lg0KDQpBdCBJRVRGIDU2LCB0aGVyZSB3YXMgYSBkaXNj
dXNzaW9uIGFib3V0IHdoZXRoZXIgdG8gbWFrZQ0KdGhpcyBjaGFuZ2Ugb3Igc3RpY2sgd2l0aCB0
aGUgY3VycmVudCBzY2hlbWEgYW5kIHVzZQ0KY29tcG9uZW50IG1hdGNoaW5nIHRvIHNvbHZlIHRo
ZSBwcm9ibGVtLiBBcyBub3RlZCBpbiB0aGUNCm1lZXRpbmcgbWludXRlcywgYSBzdHJhdyBwb2xs
IGZhdm9yZWQgY29tcG9uZW50IG1hdGNoaW5nDQpidXQgaXQgd2FzIGFncmVlZCB0byB0YWtlIHRo
aXMgZGlzY3Vzc2lvbiB0byB0aGUgbWFpbGluZw0KbGlzdC4gSSBoYXZlbid0IHNlZW4gYW55IGRp
c2N1c3Npb24gb24gdGhlIG1haWxpbmcgbGlzdCwNCmJ1dCBub3cgaXQgc2VlbXMgdGhhdCB0aGUg
bWF0dGVyIGhhcyBiZWVuIGRlY2lkZWQgaW4gZmF2b3INCm9mIHRoZSBtb2RpZmllZCBzY2hlbWEu
DQoNCkRpZCBJIG1pc3Mgc29tZXRoaW5nPyBXYXMgdGhpcyBkaXNjdXNzZWQgYW5kIGFncmVlZCB0
byBvbg0KdGhlIG1haWxpbmcgbGlzdD8gSWYgbm90LCBpdCBzaG91bGQgYmUgZGlzY3Vzc2VkIGhl
cmUuDQoNCkkgd291bGQgbGlrZSB0byBoZWFyIGZyb20gY3VzdG9tZXJzIHdobyBhcmUgdXNpbmcg
dGhlIG9sZA0Kc2NoZW1hIGFzIHRvIHdoZXRoZXIgdGhleSB3aWxsIGJlIGhhcHB5IG1vdmluZyB0
byB0aGUgbmV3DQpzY2hlbWEuIEknbSBjb25jZXJuZWQgdGhhdCB0aGV5IG1heSBiZSByZWx1Y3Rh
bnQgdG8gZG91YmxlDQpvciB0cmlwbGUgdGhlIG51bWJlciBvZiBlbnRyaWVzIGluIHRoZWlyIGRp
cmVjdG9yeS4NCg0KVGhhbmtzLA0KDQpTdGV2ZSBIYW5uYQ0KDQotLS0tPV9OZXh0UGFydF9TVEpf
ODg3Mzk5NjguMDk0NTQyNzE0DQpDb250ZW50LVR5cGU6IGFwcGxpY2F0aW9uL3J0Zg0KQ29udGVu
dC1UcmFuc2Zlci1FbmNvZGluZzogYmFzZTY0DQoNCmUxeHlkR1l4WEdGdWMybGNZVzV6YVdOd1p6
RXlOVEpjWm5KdmJYUmxlSFFnWEdSbFptWXdlMXhtYjI1MGRHSnMNCkRRcDdYR1l3WEdaemQybHpj
eUJCY21saGJEdDlEUXA3WEdZeFhHWnRiMlJsY200Z1EyOTFjbWxsY2lCT1pYYzcNCmZRMEtlMXht
TWx4bWJtbHNYR1pqYUdGeWMyVjBNaUJUZVcxaWIydzdmUTBLZTF4bU0xeG1iVzlrWlhKdVhHWmoN
CmFHRnljMlYwTUNCRGIzVnlhV1Z5SUU1bGR6dDlmUTBLZTF4amIyeHZjblJpYkZ4eVpXUXdYR2R5
WldWdU1GeGkNCmJIVmxNRHRjY21Wa01GeG5jbVZsYmpCY1lteDFaVEkxTlR0OURRcGNkV014WEhC
aGNtUmNjR3hoYVc1Y1pHVm0NCmRHRmlNell3SUZ4bU1GeG1jekl3SUZOMFpYWmxJRWtnWTJWeWRH
RnBibXg1SUhOb1lYSmxJSGx2ZFhJZ1kyOXUNClkyVnlibk11SUVrZ1pHOXVKM1FnWW1Wc2FXVjJa
U0JsZUdsemRHbHVaeUJjY0dGeURRcGtaWEJzYjNsbFpDQnoNCmVYTjBaVzF6SUhkcGJHd2diVzlr
YVdaNUlIUm9aV2x5SUhOamFHVnRZUzRnVkdobGVTQmhjbVVnZDI5eWEybHUNClp5QnFkWE4wSUZ4
d1lYSU5DbVpwYm1VZ2RHaGxJSGRoZVNCMGFHVjVJR0Z5WlNCaGJtUWdhR0YyWlNCdWJ5QnkNClpX
RnpiMjRnZEc4Z1kyaGhibWRsTGlCQmJITnZMQ0JtY205dElGeHdZWElOQ21GdUlHbHVkR1Z5YjNC
bGNtRmkNCmFXeHBkSGtnYzNSaGJtUndiMmx1ZENCSklHVjRjR1ZqZENCbmNtVmhkQ0J5Wld4MVkz
UmhibU5sSUhSdklHMXYNCmRtVWdYSEJoY2cwS2RHOGdkR2hsSUhOamFHVnRZU0JwYmlCeVpXRnNJ
SGR2Y214a0lHUmxjR3h2ZVcxbGJuUnoNCklIUm9ZWFFnYm1WbFpDQjBieUJwYm5SbGNtOXdJSGRw
ZEdnZ1hIQmhjZzBLWlhocGMzUnBibWNnYjI1bGN5QjENCmMybHVaeUIwYUdVZ2IyeGtJSE5qYUdW
dFlTNWNjR0Z5RFFwY2NHRnlEUXBUYUdGeWIyNWNjR0Z5RFFwY2NHRnkNCkRRb3RMUzB0TFU5eWFX
ZHBibUZzSUUxbGMzTmhaMlV0TFMwdExWeHdZWElOQ2taeWIyMDZJRk4wWlhabElFaGgNCmJtNWhJ
RnR0WVdsc2RHODZjM1JsZG1VdWFHRnVibUZBYzNWdUxtTnZiVjFjY0dGeURRcFRaVzUwT2lCVWRX
VnoNClpHRjVMQ0JCZFdkMWMzUWdNRFVzSURJd01ETWdNem95TVNCUVRWeHdZWElOQ2xSdk9pQlFT
MGxZSUV4cGMzUTcNCklHbGxkR1l0YkdSaGNHSnBjMEJQY0dWdVRFUkJVQzV2Y21kY2NHRnlEUXBU
ZFdKcVpXTjBPaUJRUzBsWUlFeEUNClFWQjJNeUJ6WTJobGJXRTZJR052YlhCdmJtVnVkQ0J0WVhS
amFHbHVaeUJ2Y2lCelpYQmhjbUYwWlNCbGJuUnkNCmFXVnpYSEJoY2cwS1hIQmhjZzBLWEhCaGNn
MEtWR2hsSUdSeVlXWjBJRzFwYm5WMFpYTWdabkp2YlNCMGFHVWcNClNVVlVSaUExTnlCUVMwbFlJ
RmRISUcxbFpYUnBibWNnYzJGNU9seHdZWElOQ2x4d1lYSU5DajRnVEVSQlVDQkUNCmIyTjFiV1Z1
ZEhNNklDMGdSR0YyYVdRZ1EyaGhaSGRwWTJzZ0tGVnVhWFlnYjJZZ1UyRnNabTl5WkNrZ0ppQlEN
ClpYUmxjaUJIYVdWMGVseHdZWElOQ2o0Z0lDQWdJQ0FnSUNBZ0lDQWdJQ0FnS0VSQlFWTkpLVnh3
WVhJTkNqNGcNClZHaGxJRmRISUdoaGN5QmhJSE4xYVhSbElHOW1JRXhFUVZBdFVFdEpXQ0JrY21G
bWRITWdabTl5YldsdVp5QmgNCklHTnZiWEJ5WldobGJuTnBkbVZjY0dGeURRbytJSE52YkhWMGFX
OXVJR1p2Y2lCTVJFRlFJR0poYzJWa0lGQkwNClNTQnBibVp2Y20xaGRHbHZiaUJrYVhOMGNtbGlk
WFJwYjI0dVhIQmhjZzBLWEhCaGNnMEtTU0JpWld4cFpYWmwNCklIUm9ZWFFnZEdobElGQkxJR05s
Y25ScFptbGpZWFJsSUhOamFHVnRZU0JwY3lCa1pYTmpjbWxpWldRZ2FXNWMNCmNHRnlEUXBrY21G
bWRDMXJiR0Z6Wlc0dGJHUmhjQzE0TlRBNVkyVnlkR2xtYVdOaGRHVXRjMk5vWlcxaExUQXoNCkxu
UjRkQzVjY0dGeURRcGNjR0Z5RFFwVWFHRjBJR1J2WTNWdFpXNTBJQ2hoYm1RZ2RHaGxJRU5TVENC
aGJtUWcNClFVTWdjMk5vWlcxaGN5a2djSEp2Y0c5elpYTWdZVnh3WVhJTkNtTm9ZVzVuWlNCbWNt
OXRJSE4wYjNKcGJtY2cNClkyVnlkR2xtYVdOaGRHVnpJR2x1SUhSb1pTQnRkV3gwYVMxMllXeDFa
V1JjY0dGeURRcDFjMlZ5UTJWeWRHbG0NCmFXTmhkR1VnWVc1a0lHTkJRMlZ5ZEdsbWFXTmhkR1Vn
WVhSMGNtbGlkWFJsY3lCdlppQmhibHh3WVhJTkNtVnUNCmRHbDBlU2R6SUdScGNtVmpkRzl5ZVNC
bGJuUnllU0IwYnlCemRHOXlhVzVuSUdObGNuUnBabWxqWVhSbGN5QmgNCmMxeHdZWElOQ25ObGNH
RnlZWFJsSUdScGNtVmpkRzl5ZVNCbGJuUnlhV1Z6TENCemRXSnZjbVJwYm1GMFpTQjANCmJ5QjBh
R1VnWlc1MGFYUjVKM05jY0dGeURRcGthWEpsWTNSdmNua2daVzUwY25rdUlGWmhiSFZsY3lCdFlY
a2cNCmRHaGxiaUJpWlNCbGVIUnlZV04wWldRZ1puSnZiVnh3WVhJTkNtTmxjblJwWm1sallYUmxJ
R1pwWld4a2N5QmgNCmJtUWdjR3hoWTJWa0lHbHVJR0YwZEhKcFluVjBaWE1nYjI0Z2RHaGxYSEJo
Y2cwS1kyVnlkR2xtYVdOaGRHVW4NCmN5QmthWEpsWTNSdmNua2daVzUwY25rZ2MyOGdkR2hoZENC
cGRDZHpJR1ZoYzJsbGNpQjBiMXh3WVhJTkNuTmwNCllYSmphQ0JtYjNJZ1kyVnlkR2xtYVdOaGRH
VnpJR0Z1WkNCeVpYUnlhV1YyWlNCdmJteDVJSFJvYjNObElIbHYNCmRTQjNZVzUwTGx4d1lYSU5D
bHh3WVhJTkNrRjBJRWxGVkVZZ05UWXNJSFJvWlhKbElIZGhjeUJoSUdScGMyTjENCmMzTnBiMjRn
WVdKdmRYUWdkMmhsZEdobGNpQjBieUJ0WVd0bFhIQmhjZzBLZEdocGN5QmphR0Z1WjJVZ2IzSWcN
CmMzUnBZMnNnZDJsMGFDQjBhR1VnWTNWeWNtVnVkQ0J6WTJobGJXRWdZVzVrSUhWelpWeHdZWElO
Q21OdmJYQnYNCmJtVnVkQ0J0WVhSamFHbHVaeUIwYnlCemIyeDJaU0IwYUdVZ2NISnZZbXhsYlM0
Z1FYTWdibTkwWldRZ2FXNGcNCmRHaGxYSEJoY2cwS2JXVmxkR2x1WnlCdGFXNTFkR1Z6TENCaElI
TjBjbUYzSUhCdmJHd2dabUYyYjNKbFpDQmoNCmIyMXdiMjVsYm5RZ2JXRjBZMmhwYm1kY2NHRnlE
UXBpZFhRZ2FYUWdkMkZ6SUdGbmNtVmxaQ0IwYnlCMFlXdGwNCklIUm9hWE1nWkdselkzVnpjMmx2
YmlCMGJ5QjBhR1VnYldGcGJHbHVaMXh3WVhJTkNteHBjM1F1SUVrZ2FHRjINClpXNG5kQ0J6WldW
dUlHRnVlU0JrYVhOamRYTnphVzl1SUc5dUlIUm9aU0J0WVdsc2FXNW5JR3hwYzNRc1hIQmgNCmNn
MEtZblYwSUc1dmR5QnBkQ0J6WldWdGN5QjBhR0YwSUhSb1pTQnRZWFIwWlhJZ2FHRnpJR0psWlc0
Z1pHVmoNCmFXUmxaQ0JwYmlCbVlYWnZjbHh3WVhJTkNtOW1JSFJvWlNCdGIyUnBabWxsWkNCelky
aGxiV0V1WEhCaGNnMEsNClhIQmhjZzBLUkdsa0lFa2diV2x6Y3lCemIyMWxkR2hwYm1jL0lGZGhj
eUIwYUdseklHUnBjMk4xYzNObFpDQmgNCmJtUWdZV2R5WldWa0lIUnZJRzl1WEhCaGNnMEtkR2hs
SUcxaGFXeHBibWNnYkdsemREOGdTV1lnYm05MExDQnANCmRDQnphRzkxYkdRZ1ltVWdaR2x6WTNW
emMyVmtJR2hsY21VdVhIQmhjZzBLWEhCaGNnMEtTU0IzYjNWc1pDQnMNCmFXdGxJSFJ2SUdobFlY
SWdabkp2YlNCamRYTjBiMjFsY25NZ2QyaHZJR0Z5WlNCMWMybHVaeUIwYUdVZ2IyeGsNClhIQmhj
ZzBLYzJOb1pXMWhJR0Z6SUhSdklIZG9aWFJvWlhJZ2RHaGxlU0IzYVd4c0lHSmxJR2hoY0hCNUlH
MXYNCmRtbHVaeUIwYnlCMGFHVWdibVYzWEhCaGNnMEtjMk5vWlcxaExpQkpKMjBnWTI5dVkyVnli
bVZrSUhSb1lYUWcNCmRHaGxlU0J0WVhrZ1ltVWdjbVZzZFdOMFlXNTBJSFJ2SUdSdmRXSnNaVnh3
WVhJTkNtOXlJSFJ5YVhCc1pTQjANCmFHVWdiblZ0WW1WeUlHOW1JR1Z1ZEhKcFpYTWdhVzRnZEdo
bGFYSWdaR2x5WldOMGIzSjVMbHh3WVhJTkNseHcNCllYSU5DbFJvWVc1cmN5eGNjR0Z5RFFwY2NH
RnlEUXBUZEdWMlpTQklZVzV1WVZ4d1lYSU5DbjA9DQotLS0tPV9OZXh0UGFydF9TVEpfODg3Mzk5
NjguMDk0NTQyNzE0LS0NCg0KoIILHjCCA6YwggKOoAMCAQICBD38y5IwDQYJKoZIhvcNAQEFBQAw
MTELMAkGA1UEBhMCQ0ExEDAOBgNVBAoTB0VudHJ1c3QxEDAOBgNVBAsTB1IgYW5kIEQwHhcNMDMw
NzAyMTIxNzQ4WhcNMDQwMTAyMTI0NzQ4WjBZMQswCQYDVQQGEwJDQTEQMA4GA1UEChMHRW50cnVz
dDEQMA4GA1UECxMHUiBhbmQgRDEmMA4GA1UEBRMHMTYxNjY3MTAUBgNVBAMTDVNoYXJvbiBCb2V5
ZW4wgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAMQkJK7H7oW2RtKD+5d57k7BAXHy/aOs18nl
1jKPosZJQN9PhszRhnVCMZpyDkXq0PKG1v4tJbFrH5aCEFfROj3qMEwK+zxSVMLD4zpw5ciZNWwO
v65qxO9ifQUB8hV/LIBMCWPPvTPMGIRj3PkDrz8/EYy9BepH7unc3paVROFZAgMBAAGjggEgMIIB
HDALBgNVHQ8EBAMCB4AwKwYDVR0QBCQwIoAPMjAwMzA3MDIxMjE3NDhagQ8yMDAzMTEwODA3NDc0
OFowJAYDVR0RBB0wG4EZc2hhcm9uLmJvZXllbkBlbnRydXN0LmNvbTBUBgNVHR8ETTBLMEmgR6BF
pEMwQTELMAkGA1UEBhMCQ0ExEDAOBgNVBAoTB0VudHJ1c3QxEDAOBgNVBAsTB1IgYW5kIEQxDjAM
BgNVBAMTBUNSTDI1MB8GA1UdIwQYMBaAFPPwLCjmOac0GauakaimZkCSnOJxMB0GA1UdDgQWBBQ0
YnNZwTnlrV/mljLzDrF5k9BtcDAJBgNVHRMEAjAAMBkGCSqGSIb2fQdBAAQMMAobBFY3LjADAgSw
MA0GCSqGSIb3DQEBBQUAA4IBAQBCGAJqHsgrxDyh90ing3LNDc3DQmbXn1TtcwHrHZDAeRXl+J/w
yMwkLVNeHJfRawgOy59UpEcIfawhdoUFn10XDU/fXY+azaJvNuK6YE6EEk8eH0xbRYpPkBBzrw/g
r+wp0sGmJGPySjbuqX4dOqJ/fnKpdTe/ZgvguctukfsWBP+X2DREJ2uC2/fB6uQwq8/1sKX2BHsL
MEeq/epfdzGRli0nN4lpSUTDpnMUCWAnMEYvj08nmtsQNaIMS9v9d1ok9ShV2MM59my+jlIE/qEI
yaHF9wPSZfUc2bjEty2+Wvuy6ttXYVdFCjeUNNaMcgInd6Clh269YsC8ivNH6sMJMIIDdzCCAl+g
AwIBAgIEPfzFLzANBgkqhkiG9w0BAQUFADAxMQswCQYDVQQGEwJDQTEQMA4GA1UEChMHRW50cnVz
dDEQMA4GA1UECxMHUiBhbmQgRDAeFw0wMzA1MTIxMjA5MzBaFw0wMzExMTIxMjM5MzBaMFkxCzAJ
BgNVBAYTAkNBMRAwDgYDVQQKEwdFbnRydXN0MRAwDgYDVQQLEwdSIGFuZCBEMSYwDgYDVQQFEwcx
NjE2NjcxMBQGA1UEAxMNU2hhcm9uIEJvZXllbjCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEA
o6Fl6ltnYS/22/pvoIr8lO9eRkvdCinBx4tgVO+QRZF90u+QTtz4Brv9qf4I8FMTb8KSWQnjv4Dg
0gwjZnxZ+lxguVFFGrJrSDyOMCYPsKIGaz8JPrUvlQqfB/8Yu+1/4koVrHCxD4qI26vFF8D9mPGM
jQVQp1HoN/XEzDS+zGcCAwEAAaOB8jCB7zALBgNVHQ8EBAMCBSAwJAYDVR0RBB0wG4EZc2hhcm9u
LmJvZXllbkBlbnRydXN0LmNvbTBUBgNVHR8ETTBLMEmgR6BFpEMwQTELMAkGA1UEBhMCQ0ExEDAO
BgNVBAoTB0VudHJ1c3QxEDAOBgNVBAsTB1IgYW5kIEQxDjAMBgNVBAMTBUNSTDI1MB8GA1UdIwQY
MBaAFPPwLCjmOac0GauakaimZkCSnOJxMB0GA1UdDgQWBBTf/D6k/mHuAALWEVNvhucj5Cx0xDAJ
BgNVHRMEAjAAMBkGCSqGSIb2fQdBAAQMMAobBFY3LjADAgSwMA0GCSqGSIb3DQEBBQUAA4IBAQBX
XhNix13ybT60c+xhpIFCdTyqCqoa8IHzdtWdI6ltun2zxmEGYzMnfXM8cx9vr5dEmWehIIeUt12h
lLiOBfdVoakEBJ6LaoLOkveKyEVpPdR9aMvEIl5zdslQKnzCWlFNh4HII2EjGVnnG4PY72EJ++0z
wYu7PTMzTD4Hrta6wSnImddXdou6zjW1Rg/ipzzC7sZLNqVyhEkUdO6NY04oH3lAfvSazcFHCED1
DNEb5rXC8OT2i+KhSKxY04gFehD0d6gzoe40ZW5STfmnz3bvXk7ClE/TvmJMc6hkrQ9Az3snyeg0
Ybu+xiauNDtEqbngXdeYt+LJfxIBfMN4Ver6MIID9TCCAt2gAwIBAgIEMkiqIDANBgkqhkiG9w0B
AQUFADAxMQswCQYDVQQGEwJDQTEQMA4GA1UEChMHRW50cnVzdDEQMA4GA1UECxMHUiBhbmQgRDAe
Fw0wMjA0MTcwMjIwMjZaFw0yMjA0MTcwMjUwMjZaMDExCzAJBgNVBAYTAkNBMRAwDgYDVQQKEwdF
bnRydXN0MRAwDgYDVQQLEwdSIGFuZCBEMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA
vIeIjfoD5D86sD8CehB+kVhYJTL+VuaUZiVijGevUTlnUAwy1WpOYVpFCa8VK116TJ+o99axN1jM
bsVBYfRzFk9SWl4iAH+PyJ1S6D5Yl593KjHPhBCfdD0v9KoPqXhCwRlkvupreNlFx3FFk2Uf5jG/
i9SCP925OXbz3wod2mdIu8ueNWgTmA2XAOBdHZg6HYKo50BWUIgtRwFvzbh1J57+gNdHxMYLZmvj
5saS1mDTSibkPH/AY+D+xAozRmyOYa4SY2HVfZSM2SP7MkuVtKp17pzhwicoWAGKXrKeDRWDYeZB
TJjHoNP/SXKdpSzY7rV8GPrfWFoogc4350VbowIDAQABo4IBEzCCAQ8wEQYJYIZIAYb4QgEBBAQD
AgAHMFMGA1UdHwRMMEowSKBGoESkQjBAMQswCQYDVQQGEwJDQTEQMA4GA1UEChMHRW50cnVzdDEQ
MA4GA1UECxMHUiBhbmQgRDENMAsGA1UEAxMEQ1JMMTArBgNVHRAEJDAigA8yMDAyMDQxNzAyMjAy
NlqBDzIwMjIwNDE3MDI1MDI2WjALBgNVHQ8EBAMCAQYwHwYDVR0jBBgwFoAU8/AsKOY5pzQZq5qR
qKZmQJKc4nEwHQYDVR0OBBYEFPPwLCjmOac0GauakaimZkCSnOJxMAwGA1UdEwQFMAMBAf8wHQYJ
KoZIhvZ9B0EABBAwDhsIVjYuMDo0LjADAgSQMA0GCSqGSIb3DQEBBQUAA4IBAQCAPnm1Rpn5ya5k
BLFpckRtw+XuY/G5m6uQH9hVXgechp+i6/tXlYjQ8ccnJy1HcOmPS718LkG4drxBfrhjO9aTudv+
TNIMR9izay796hsBk7raBpYtxavOEjxb8jfp+EelztgcSZo737mYzcrr9pDjzJldsriCzPDU/N05
2R+RJ4Rs/0IiuWzIVH7y99S9O+rG14PjEKNQhA39gTwg9iMBtQoksDfKu09UCaFsE7aYUC8eE0wz
ki4G+Dl5RKE57MGaYAh+cccmyPR6Xw/gl8Yo3YGhOWz3qatAhbbplACm9LSmduMSLXQybke6cq5J
Ub8c9VMzi9cIiv6Hbf1/xObPMYICZTCCAmECAQEwOTAxMQswCQYDVQQGEwJDQTEQMA4GA1UEChMH
RW50cnVzdDEQMA4GA1UECxMHUiBhbmQgRAIEPfzLkjAJBgUrDgMCGgUAoIIBgjAYBgkqhkiG9w0B
CQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wMzA4MDcxMzQ1NDJaMCMGCSqGSIb3DQEJ
BDEWBBTkmTRdT/XLmnfLmRRnAupInArpQjCCASEGCSqGSIb3DQEJDzGCARIwggEOMAsGCWCGSAFl
AwQBKjALBglghkgBZQMEARYwCwYJYIZIAWUDBAECMA8GCSqGSIb2fQdCCgICAIAwDgYIKoZIhvcN
AwICAgCAMAoGCCqGSIb3DQMHMA0GCysGAQQBgTwHAQECMA4GCSqGSIb2fQdCCgIBKDANBggqhkiG
9w0DAgIBKDAHBgUrDgMCBzAHBgUrDgMCGjAKBggqhkiG9w0CBTALBgkqhkiG9w0BAQEwCwYJKoZI
hvcNAQEHMAkGByqGSM44BAEwCQYHKoZIzj0CATALBgkqhkiG9w0BAQUwCwYJKoZIhvcNAQEEMAkG
ByqGSM44BAMwCQYHKoZIzj0EATAMBgoqhkiG9w0BCQ8BMA0GCSqGSIb3DQEBAQUABIGAfsZUoHUN
prl8MaOdfJijqbYExi274VF+XUsgrkkd+lwGisYKzgl4U5PXM9JfOVqpKIBtV1rkqvDKL78esfUG
Uts1YlimCU2bzRtm8MeB2r2+sz0yoQW5/FbarUM0oFZJYWCbY1bq4uLirXbQyyROUvGkE2ECCJif
2BBCxzBFVjw=


From owner-ietf-ldapbis@OpenLDAP.org  Thu Aug  7 10:39:53 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17061
	for <ldapbis-archive@lists.ietf.org>; Thu, 7 Aug 2003 10:39:52 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h77Ecb31009631;
	Thu, 7 Aug 2003 14:38:53 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h77EXWoN009307;
	Thu, 7 Aug 2003 14:33:32 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 7 Aug 2003 14:33:32 +0000
Received: from sottmxssm.entrust.com (sottmxssm.entrust.com [216.191.252.10])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h77EXU2v009267
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 7 Aug 2003 14:33:31 GMT
	(envelope-from sharon.boeyen@entrust.com)
Received: from sottguard01.entrust.com (sottguard01.entrust.com [10.4.61.249])
	by sottmxssm.entrust.com (Switch-2.2.6/Switch-2.2.4) with SMTP id V77E0TPA03033
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 07 Aug 2003 10:29:25 -0400
Received: (qmail 32696 invoked by uid 64014); 7 Aug 2003 14:26:14 -0000
Received: from sharon.boeyen@entrust.com by sottguard01.entrust.com with AmikaGuardian-Server-1.1.2 (Processed in 0.871647 secs); 07 Aug 2003 14:26:14 -0000
Received: from unknown (HELO SOTTMXS01.entrust.com) (10.4.61.7)
  by 10.4.61.249 with SMTP; 7 Aug 2003 14:26:13 -0000
Received: by sottmxs01.entrust.com with Internet Mail Service (5.5.2656.59)
	id <QMF1Y1T7>; Thu, 7 Aug 2003 10:33:07 -0400
Message-ID: <9A4F653B0A375841AC75A8D17712B9C9061AC43F@sottmxs04.entrust.com>
From: Sharon Boeyen <sharon.boeyen@entrust.com>
To: "Steve Hanna (E-mail)" <steve.hanna@sun.com>,
        "pkix (E-mail)"
	 <ietf-pkix@imc.org>,
        "'ietf-ldapbis@OpenLDAP.org'"
	 <ietf-ldapbis@OpenLDAP.org>
Subject: FW:Resend  PKIX LDAPv3 schema: component matching or separate ent
	ries
Date: Thu, 7 Aug 2003 10:33:07 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>



Steve I certainly share your concerns. I don't believe existing 
deployed systems will modify their schema. They are working just 
fine the way they are and have no reason to change. Also, from 
an interoperability standpoint I expect great reluctance to move 
to the schema in real world deployments that need to interop with 
existing ones using the old schema.

Sharon

-----Original Message-----
From: Steve Hanna [mailto:steve.hanna@sun.com]
Sent: Tuesday, August 05, 2003 3:21 PM
To: PKIX List; ietf-ldapbis@OpenLDAP.org
Subject: PKIX LDAPv3 schema: component matching or separate entries


The draft minutes from the IETF 57 PKIX WG meeting say:

> LDAP Documents: - David Chadwick (Univ of Salford) & Peter Gietz
>                (DAASI)
> The WG has a suite of LDAP-PKIX drafts forming a comprehensive
> solution for LDAP based PKI information distribution.

I believe that the PK certificate schema is described in
draft-klasen-ldap-x509certificate-schema-03.txt.

That document (and the CRL and AC schemas) proposes a
change from storing certificates in the multi-valued
userCertificate and cACertificate attributes of an
entity's directory entry to storing certificates as
separate directory entries, subordinate to the entity's
directory entry. Values may then be extracted from
certificate fields and placed in attributes on the
certificate's directory entry so that it's easier to
search for certificates and retrieve only those you want.

At IETF 56, there was a discussion about whether to make
this change or stick with the current schema and use
component matching to solve the problem. As noted in the
meeting minutes, a straw poll favored component matching
but it was agreed to take this discussion to the mailing
list. I haven't seen any discussion on the mailing list,
but now it seems that the matter has been decided in favor
of the modified schema.

Did I miss something? Was this discussed and agreed to on
the mailing list? If not, it should be discussed here.

I would like to hear from customers who are using the old
schema as to whether they will be happy moving to the new
schema. I'm concerned that they may be reluctant to double
or triple the number of entries in their directory.

Thanks,

Steve Hanna


From owner-ietf-ldapbis@OpenLDAP.org  Mon Aug 11 04:59:37 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA10601
	for <ldapbis-archive@lists.ietf.org>; Mon, 11 Aug 2003 04:59:33 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h7B8uNNY083825;
	Mon, 11 Aug 2003 08:57:56 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h7B8sj23083812;
	Mon, 11 Aug 2003 08:54:45 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 11 Aug 2003 08:54:45 +0000
Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h7B8siNU083802
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 11 Aug 2003 08:54:44 GMT
	(envelope-from rlmorgan@washington.edu)
Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9])
	by mxout1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7B8sXoa016830
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 11 Aug 2003 01:54:34 -0700
Received: from [192.168.1.102] (12-231-112-60.client.attbi.com [12.231.112.60])
	(authenticated bits=0)
	by smtp.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7B8sWXa001649
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT)
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 11 Aug 2003 01:54:33 -0700
Date: Mon, 11 Aug 2003 01:54:34 -0700 (PDT)
From: "RL 'Bob' Morgan" <rlmorgan@washington.edu>
X-X-Sender: rlmorgan@localhost.localdomain
To: IETF ldapbis WG <ietf-ldapbis@OpenLDAP.org>
Subject: draft ldapbis meeting notes, IETF 57, Vienna
Message-ID: <Pine.LNX.4.44.0308110152490.8966-100000@localhost.localdomain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>


Draft notes below, please send me any corrections.

 - RL "Bob"

---


DRAFT ldapbis meeting notes
IETF 57, Vienna, Austria
2003-07-15
submitted by:  RL "Bob" Morgan

The co-chairs, Kurt Zeilenga and RL 'Bob' Morgan, called the meeting to
order at 14:15.

Kurt noted that the WG charter has been updated to reflect current plans,
which call for all remaining documents to go through WG Last Call in
July/August, and (assuming consensus) for revised documents to be
submitted to the IESG by September.  It is expected that the WG will not
need to meet at IETF in Minneapolis.

Jim Sermersheim spoke about the protocol document.  The "attribute
descriptor length" issue has received much discussion on the WG list, and
was discussed at length at this meeting.

Ted Hardie, the WG's Area Director, spoke for ("channeled") Chris Apple,
saying that the issue is that designers of LDAP-based applications and
schema need interoperable LDAP implementations to support them, and need
to know what limits they can design to.

Kurt responded that there are two separable issues.  One, the one that
started the email thread, is that an implementation was observed to
truncate short names; this is just a bad implementation, it may be useful
to clarify the doc to make it clear this isn't permitted.  The other is
that LDAP can be used in many contexts, so not all features are required
or appropriate for all contexts.  Applicability statements are the IETF
documents that say which features are required for particular
applications.

Rick Huber observed that the problem is a protocol interoperability
problem, hence should be addressed by the protocol spec.  John Strassner
observed that lots of schema designers are writing schema with long
attribute descriptors (names), and are depending on implementations
supporting this.  Kurt observed that other requirements like matching
rules will lead to a need for application-specific AS.

Ted said applicability statements would be fine, and suggested a "basic"
one on which variations can be based.

Leif Johansson asked if implementation-specific limits need to be
discoverable?  Ted said that would follow but isn't necessary.

Rick observed that requiring an application statement per app is a lot of
work for app developers.  Kurt said it might be feasible to define a
"general-purpose" LDAP AS, but might be hard to get consensus.

Ted said it seems byzantine to have protocol limits defined separately
from the protocol.  Kurt responded that it seems inappropriate to clutter
a general-purpose protocol spec with considerations of only one
application scenario.

It was observed that this discussion needs to move back to the mailing
list.

Jim requested that people look at the protocols and models documents
together for potential overlaps or gaps.  He also encouraged a review of
the use of MUST/SHOULD/MAY in the docs.

Kurt said that since it now appears that our documents will have to be
again at Proposed Standard level, interoperability reports can wait until
after this, when we prepare to go to Draft Standard.

Vithalprasad Gaitonde presented for Roger Harrison regarding the authmeth
document.  Draft -06 was produced.  It lists various fixes since the
previous version in its appendix.  Some issues were discussed.

Is password protection needed regardless of the use of authzid?

Is the SASL PLAIN method prohibited in LDAP?  No, just "not typically
used".

In the TLS server name check function, should the use of the CN RDN in the
Subject DN to hold the server DNS hostname be documented?  RL "Bob"
observed that other app-TLS specs have not done this, even though the
method is commonly used, because it is such a clumsy mechanism.

Must the SASL EXTERNAL operation immediately follow completion of
STARTTLS?  No, the first operation after STARTTLS should be another check
of server capabilities.  The TLS-complete-but-not-bound state may not be
in the authentication state diagram.

Use of derived DNS names OK in the TLS server name check function?  RL
"Bob" said that this would be a change from the current RFC, but is
consistent with the original intent.

It was observed that the description of DIGEST authentication in the
authmeth doc is too detailed, and may conflict with other specs, so it was
suggested to modify it to reduce this.

Kurt wrapped up the session by noting that once all documents have been
through Last Call, there will be a Last Call on the Roadmap document and
one more pass over the whole document set for consistency.

The session concluded at 15:15.





From owner-ietf-ldapbis@OpenLDAP.org  Tue Aug 12 09:50:56 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA13340
	for <ldapbis-archive@lists.ietf.org>; Tue, 12 Aug 2003 09:50:56 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h7CDiWNa070030;
	Tue, 12 Aug 2003 13:49:16 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h7CDh6et069952;
	Tue, 12 Aug 2003 13:43:06 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 12 Aug 2003 13:43:06 +0000
Received: from tconl91223.tconl.com (tconl91223.tconl.com [204.26.91.223])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h7CDh4NU069923
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 12 Aug 2003 13:43:05 GMT
	(envelope-from jayhawk@tconl91223.tconl.com)
Received: (from jayhawk@localhost)
	by tconl91223.tconl.com (8.11.6/8.11.0) id h7CDgUm02558;
	Tue, 12 Aug 2003 08:42:30 -0500
Date: Tue, 12 Aug 2003 08:42:30 -0500
From: Ryan Moats <rmoats@lemurnetworks.net>
To: "RL 'Bob' Morgan" <rlmorgan@washington.edu>
Cc: IETF ldapbis WG <ietf-ldapbis@OpenLDAP.org>
Subject: Re: draft ldapbis meeting notes, IETF 57, Vienna
Message-ID: <20030812084230.B1545@privateer.local.windrose.omaha.ne.us>
Reply-To: rmoats@lemurnetworks.net
References: <Pine.LNX.4.44.0308110152490.8966-100000@localhost.localdomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <Pine.LNX.4.44.0308110152490.8966-100000@localhost.localdomain>; from rlmorgan@washington.edu on Mon, Aug 11, 2003 at 01:54:34AM -0700
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

On Mon, Aug 11, 2003 at 01:54:34AM -0700, RL 'Bob' Morgan wrote:
| 
| Draft notes below, please send me any corrections.
| 
|  - RL "Bob"

This isn't a correction, its picking up the "descriptor length" thread.

First a point:  while the discussion has been about attribute descriptor
lengths, I feel that the same arguments apply to object class descriptors
as well.

| Jim Sermersheim spoke about the protocol document.  The "attribute
| descriptor length" issue has received much discussion on the WG list, and
| was discussed at length at this meeting.
| 
| Ted Hardie, the WG's Area Director, spoke for ("channeled") Chris Apple,
| saying that the issue is that designers of LDAP-based applications and
| schema need interoperable LDAP implementations to support them, and need
| to know what limits they can design to.
| 
| Kurt responded that there are two separable issues.  One, the one that
| started the email thread, is that an implementation was observed to
| truncate short names; this is just a bad implementation, it may be useful
| to clarify the doc to make it clear this isn't permitted.  The other is
| that LDAP can be used in many contexts, so not all features are required
| or appropriate for all contexts.  Applicability statements are the IETF
| documents that say which features are required for particular
| applications.

I believe that there was a suggestion made during the meeting that
"all label octets MUST be significant".  I can certainly live with that.

Ryan


From owner-ietf-ldapbis@OpenLDAP.org  Tue Aug 12 11:05:15 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18031
	for <ldapbis-archive@lists.ietf.org>; Tue, 12 Aug 2003 11:05:14 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h7CF2WNY073770;
	Tue, 12 Aug 2003 15:03:02 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h7CExqhS073654;
	Tue, 12 Aug 2003 14:59:52 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 12 Aug 2003 14:59:52 +0000
Received: from pat.uio.no (IDENT:7411@pat.uio.no [129.240.130.16])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h7CExoNU073643
	for <ietf-ldapbis@openldap.org>; Tue, 12 Aug 2003 14:59:51 GMT
	(envelope-from hbf@bombur.uio.no)
Received: from [129.240.10.29] (helo=mail-mx1.uio.no)
	by pat.uio.no with esmtp (Exim 4.20)
	id 19maci-0004CE-Hs; Tue, 12 Aug 2003 16:59:44 +0200
Received: from [129.240.186.42] (helo=bombur.uio.no)
	by mail-mx1.uio.no with esmtp (Exim 4.14)
	id 19macg-0006rJ-87; Tue, 12 Aug 2003 16:59:42 +0200
Received: from hbf by bombur.uio.no with local (Exim 2.12 #7)
	id 19macf-000684-00; Tue, 12 Aug 2003 16:59:41 +0200
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Message-Id: <HBF.20030812hoe7@bombur.uio.no>
To: rmoats@lemurnetworks.net
Cc: "RL 'Bob' Morgan" <rlmorgan@washington.edu>,
        IETF ldapbis WG <ietf-ldapbis@OpenLDAP.org>
Subject: Descriptor lengths (Was: draft ldapbis meeting notes, IETF 57, Vienna)
In-Reply-To: <20030812084230.B1545@privateer.local.windrose.omaha.ne.us>
References: <Pine.LNX.4.44.0308110152490.8966-100000@localhost.localdomain>
	<20030812084230.B1545@privateer.local.windrose.omaha.ne.us>
X-Mailer: VM 6.37 under Emacs 19.34.1
Date: Tue, 12 Aug 2003 16:59:41 +0200
X-MailScanner-Information: This message has been scanned for viruses/spam. Contact postmaster@uio.no if you have questions about this scanning.
X-UiO-MailScanner: No virus found
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

Ryan Moats writes:
> This isn't a correction, its picking up the "descriptor length" thread.
> 
> First a point:  while the discussion has been about attribute descriptor
> lengths, I feel that the same arguments apply to object class descriptors
> as well.

Also attribute options, and maybe the names of matching rules, matching
rule uses, DIT content rules, DIT structure rules, and name forms.

-- 
Hallvard


From owner-ietf-ldapbis@OpenLDAP.org  Tue Aug 12 12:05:26 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19937
	for <ldapbis-archive@lists.ietf.org>; Tue, 12 Aug 2003 12:05:24 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h7CG2XNY077884;
	Tue, 12 Aug 2003 16:02:47 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h7CFvOir077586;
	Tue, 12 Aug 2003 15:57:24 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 12 Aug 2003 15:57:24 +0000
Received: from pat.uio.no (IDENT:7411@pat.uio.no [129.240.130.16])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h7CFvLNU077552;
	Tue, 12 Aug 2003 15:57:21 GMT
	(envelope-from hbf@bombur.uio.no)
Received: from [129.240.10.44] (helo=mail-mx3.uio.no)
	by pat.uio.no with esmtp (Exim 4.20)
	id 19mbWP-0000mr-Le; Tue, 12 Aug 2003 17:57:17 +0200
Received: from [129.240.186.42] (helo=bombur.uio.no)
	by mail-mx3.uio.no with esmtp (Exim 4.14)
	id 19mbWL-0005nt-F8; Tue, 12 Aug 2003 17:57:13 +0200
Received: from hbf by bombur.uio.no with local (Exim 2.12 #7)
	id 19mbWK-0006Gv-00; Tue, 12 Aug 2003 17:57:12 +0200
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Message-Id: <HBF.20030812gprz@bombur.uio.no>
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Cc: Jim Sermersheim <jimse@novell.com>, ietf-ldapbis@OpenLDAP.org
Subject: Re: Fwd: Re: result code for a deleted identity on a connection
In-Reply-To: <5.2.0.9.0.20030729090709.01b8ef10@127.0.0.1>
References: <sf25b876.043@prv-mail20.provo.novell.com>
	<5.2.0.9.0.20030729090709.01b8ef10@127.0.0.1>
X-Mailer: VM 6.37 under Emacs 19.34.1
Date: Tue, 12 Aug 2003 17:57:12 +0200
X-MailScanner-Information: This message has been scanned for viruses/spam. Contact postmaster@uio.no if you have questions about this scanning.
X-UiO-MailScanner: No virus found
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

Kurt D. Zeilenga writes:
> My personal view on this thread is that issues of authentication
> and access control are a local matter and we should limit any
> additional text here to the Security Considerations section(s).

Well, Security Considerations could list some common scenarios where it
may be safest to return strongAuthRequired until the client rebinds.
At least the LDAP-specific ones (user entry deleted etc).

But there should also be a statement in [Protocol] that the server may
at any time return strongAuthRequired to the client if it decides that
the credentials from the previous bind have become invalid.  Then refer
to the above mentioned Security Considerations section for examples.

It's been mentioned before that returning that is supposed to be OK, but
I could not find any such statement in either [Protocol] or [Authmeth].

Also the same place might mention that if the creds for the TLS session
become invalid, the server or client it may gracefully close the TLS
association, and refer to 4.13.3.1.

-- 
Hallvard


From owner-ietf-ldapbis@OpenLDAP.org  Tue Aug 12 20:58:32 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05544
	for <ldapbis-archive@lists.ietf.org>; Tue, 12 Aug 2003 20:58:32 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h7D0uaNY003296;
	Wed, 13 Aug 2003 00:57:08 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h7D0rj3Z003214;
	Wed, 13 Aug 2003 00:53:45 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 13 Aug 2003 00:53:45 +0000
Received: from ausyms50.ca.com ([155.35.248.106])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h7D0rZNU003197
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 13 Aug 2003 00:53:39 GMT
	(envelope-from Ron.Ramsay@ca.com)
Received: from ausyms21.ca.com ([155.35.201.5]) by ausyms50.ca.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 13 Aug 2003 10:53:09 +1000
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: draft ldapbis meeting notes, IETF 57, Vienna
Date: Wed, 13 Aug 2003 10:53:09 +1000
Message-ID: <1395B4B334FCC143B36AF788E68B638167BE85@ausyms21.ca.com>
Thread-Topic: draft ldapbis meeting notes, IETF 57, Vienna
Thread-Index: AcNg2Iyl5qOyF6ELRgqhzYtuhDT1yAAXFLbQ
From: "Ramsay, Ron" <Ron.Ramsay@ca.com>
To: <rmoats@lemurnetworks.net>
Cc: "IETF ldapbis WG" <ietf-ldapbis@OpenLDAP.org>
X-OriginalArrivalTime: 13 Aug 2003 00:53:09.0308 (UTC) FILETIME=[43AD07C0:01C36135]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by boole.openldap.org id h7D0rdNU003203
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 8bit

Certainly, making all octets significant is a workable solution. If an implementation cannot handle the longer descriptors then an attempt to configure them should fail and then they would be unrecognised in the protocol. Everything is deterministic.

Ron

-----Original Message-----
From: Ryan Moats [mailto:rmoats@lemurnetworks.net]
Sent: Tuesday, 12 August 2003 23:43
To: RL 'Bob' Morgan
Cc: IETF ldapbis WG
Subject: Re: draft ldapbis meeting notes, IETF 57, Vienna


On Mon, Aug 11, 2003 at 01:54:34AM -0700, RL 'Bob' Morgan wrote:
| 
| Draft notes below, please send me any corrections.
| 
|  - RL "Bob"

This isn't a correction, its picking up the "descriptor length" thread.

First a point:  while the discussion has been about attribute descriptor
lengths, I feel that the same arguments apply to object class descriptors
as well.

| Jim Sermersheim spoke about the protocol document.  The "attribute
| descriptor length" issue has received much discussion on the WG list, and
| was discussed at length at this meeting.
| 
| Ted Hardie, the WG's Area Director, spoke for ("channeled") Chris Apple,
| saying that the issue is that designers of LDAP-based applications and
| schema need interoperable LDAP implementations to support them, and need
| to know what limits they can design to.
| 
| Kurt responded that there are two separable issues.  One, the one that
| started the email thread, is that an implementation was observed to
| truncate short names; this is just a bad implementation, it may be useful
| to clarify the doc to make it clear this isn't permitted.  The other is
| that LDAP can be used in many contexts, so not all features are required
| or appropriate for all contexts.  Applicability statements are the IETF
| documents that say which features are required for particular
| applications.

I believe that there was a suggestion made during the meeting that
"all label octets MUST be significant".  I can certainly live with that.

Ryan




From owner-ietf-ldapbis@OpenLDAP.org  Tue Aug 12 23:02:45 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA08119
	for <ldapbis-archive@lists.ietf.org>; Tue, 12 Aug 2003 23:02:44 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h7D31BNi008077;
	Wed, 13 Aug 2003 03:01:26 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h7D2q7Db006598;
	Wed, 13 Aug 2003 02:52:07 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 13 Aug 2003 02:52:07 +0000
Received: from adacel.com (gunsmoke.adacel.com.au [210.11.130.7])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h7D2q4NU006546
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 13 Aug 2003 02:52:05 GMT
	(envelope-from steven.legg@adacel.com.au)
Received: from nexus.adacel.com (Not Verified[10.32.240.1]) by adacel.com with NetIQ MailMarshal (v5.5.3.16)
	id <B00012d31c>; Wed, 13 Aug 2003 12:47:08 +1000
Received: (qmail 28520 invoked from network); 13 Aug 2003 02:45:46 -0000
Received: from unknown (HELO osmium) (10.32.24.165)
  by nexus.adacel.com with SMTP; 13 Aug 2003 02:45:46 -0000
Reply-To: <steven.legg@adacel.com.au>
From: "Steven Legg" <steven.legg@adacel.com.au>
To: <ldapext@ietf.org>
Cc: "'OSI Directory List'" <OSIdirectory@az05.bull.com>,
        <ietf-ldapbis@OpenLDAP.org>
Subject: The XML Enabled Directory - Mailing List
Date: Wed, 13 Aug 2003 12:51:34 +1000
Message-ID: <001e01c36145$cf53f710$a518200a@osmium.mtwav.adacel.com.au>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2120.0
Importance: Normal
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


Folks,

Some of you will have already noticed that I recently published
the first batch of a series of Internet drafts that describe
an XML rendition of LDAP and X.500 called the XML Enabled Directory (XED).

For those who are interested, the roadmap document is the best place
to start reading as it puts the other documents into context:

    http://www.ietf.org/internet-drafts/draft-legg-xed-roadmap-00.txt

Paraphrasing the roadmap's introduction:

   The XML Enabled Directory leverages existing LDAP and X.500
   directory technology to create a directory service that stores,
   manages and transmits XML format data, while maintaining
   interoperability with LDAP clients, X.500 DUAs and DSAs.

   The main features of XED are:

    - semantically equivalent XML renditions of existing directory
      protocols,

    - XML renditions of directory data,

    - the ability to accept at run time, user defined attribute syntaxes
      specified in a variety of XML schema languages,

    - the ability to perform filter matching on the parts of XML format
      attribute values,

    - the flexibility for implementors to develop XED clients using only
      their favoured XML schema language.

I have set up a mailing list, xeddev@adacel.com, to hold discussions
on the XED Internet drafts. Purely editorial comments can be sent
straight to me. To subscribe to the list send a message to
xeddev-request@adacel.com with the keyword subscribe in the body.
The list only accepts postings by subscribers.

Regards,
Steven



From owner-ietf-ldapbis@OpenLDAP.org  Wed Aug 13 09:52:52 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19210
	for <ldapbis-archive@lists.ietf.org>; Wed, 13 Aug 2003 09:52:51 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h7DDKeOK030117;
	Wed, 13 Aug 2003 13:51:35 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h7DDF99T029470;
	Wed, 13 Aug 2003 13:15:09 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 13 Aug 2003 13:15:09 +0000
Received: from rembrandt.esys.ca (rembrandt.esys.ca [198.161.92.131])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h7DDF8NU029460
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 13 Aug 2003 13:15:08 GMT
	(envelope-from Alexey.Melnikov@isode.com)
Received: from isode.com ([62.3.223.65])
	(authenticated)
	by rembrandt.esys.ca (8.11.6/8.11.0.Beta0) with ESMTP id h7DDIXV18021;
	Wed, 13 Aug 2003 07:18:34 -0600
Message-ID: <3F3A39C4.2050304@isode.com>
Date: Wed, 13 Aug 2003 14:14:44 +0100
From: Alexey Melnikov <Alexey.Melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Ramsay, Ron" <Ron.Ramsay@ca.com>
CC: LDAPBis WG <ietf-ldapbis@OpenLDAP.org>
Subject: Re: Comments about draft-ietf-ldapbis-authmeth-05.txt
References: <1395B4B334FCC143B36AF788E68B638160BC40@ausyms21.ca.com>
In-Reply-To: <1395B4B334FCC143B36AF788E68B638160BC40@ausyms21.ca.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Ramsay, Ron wrote:

>Good point. I note that RFC 2831 also allows the empty string for the realm.
>
>But what about storing the password. The ideal would be to store the username/realm/password hash. But the username is a DN(?) and it doesn't have a canonical value.
>
Yep, this is a problem.

> Yet the value used to precalculate the hash must agree with the value that the client is going to use when connecting. Do you have any suggestions about this?
>
All implementation that I've seen store password in the clear (which 
arguably defeat one of the purposes of DIGEST-MD5). But let's disregard 
them for a second.

After talking to my co-workers about the issue, here are some 
recommendations:
One way to solve this would be to require usage of some canonical form 
when passing this data to DIGEST-MD5.
Clients SHOULD send canonical forms of DNs that are used as usernames. 
Servers SHOULD send canonical forms of DNs when they are used as realms.
When adding/modifying a secret in the server's password database, 
canonical form of DNs SHOULD be used.

When DNs are constructed/canonicalized, the following steps should be 
done to insure interoperability:

1). For a known attribute the canonical attribute name must be used (e.g. "cn" ==> "CN", "CommonName" ==> "CN").
2). draft-ietf-ldapbis-strprep should be used for values of attributes (if they are recognized). In particular, for case insensitive values case folding will be performed.
3). Insignificant Spaces in DN production must be removed. E.g. "CN= John,  OU  = PSO" will be converted to "CN=John,OU=PSO".


I suggest that some text about the issue should be included in 
draft-ietf-ldapbis-authmeth.

Alexey




From owner-ietf-ldapbis@OpenLDAP.org  Wed Aug 13 10:44:29 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22294
	for <ldapbis-archive@lists.ietf.org>; Wed, 13 Aug 2003 10:44:26 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h7DEQCOH002855;
	Wed, 13 Aug 2003 14:42:24 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h7DEMexV002284;
	Wed, 13 Aug 2003 14:22:40 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 13 Aug 2003 14:22:40 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h7DEMdNf002272
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 13 Aug 2003 14:22:39 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from nomad.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.8/8.12.8) with ESMTP id h7DEMA5t098477;
	Wed, 13 Aug 2003 14:22:10 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030813071436.01c1ec78@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Wed, 13 Aug 2003 07:23:26 -0700
To: Alexey Melnikov <Alexey.Melnikov@isode.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: Comments about draft-ietf-ldapbis-authmeth-05.txt
Cc: "Ramsay, Ron" <Ron.Ramsay@ca.com>, LDAPBis WG <ietf-ldapbis@OpenLDAP.org>
In-Reply-To: <3F3A39C4.2050304@isode.com>
References: <1395B4B334FCC143B36AF788E68B638160BC40@ausyms21.ca.com>
 <1395B4B334FCC143B36AF788E68B638160BC40@ausyms21.ca.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

At 06:14 AM 8/13/2003, Alexey Melnikov wrote:
>I suggest that some text about the issue should be included in draft-ietf-ldapbis-authmeth.

If authmeth says anything about DNs and DIGEST-MD5, it should say
that the DIGEST-MD5 username and realm fields are, per the DIGEST-MD5
TS, syntactically and semantically not DNs.  They are syntactically
and semantically simple usernames and realms, respectively.

Kurt 



From owner-ietf-ldapbis@OpenLDAP.org  Wed Aug 13 11:22:20 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23061
	for <ldapbis-archive@lists.ietf.org>; Wed, 13 Aug 2003 11:22:15 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h7DFKBNl010859;
	Wed, 13 Aug 2003 15:20:16 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h7DFFjnZ010230;
	Wed, 13 Aug 2003 15:15:45 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 13 Aug 2003 15:15:44 +0000
Received: from rembrandt.esys.ca (rembrandt.esys.ca [198.161.92.131])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h7DFFgNf010195;
	Wed, 13 Aug 2003 15:15:42 GMT
	(envelope-from Alexey.Melnikov@isode.com)
Received: from isode.com ([62.3.223.65])
	(authenticated)
	by rembrandt.esys.ca (8.11.6/8.11.0.Beta0) with ESMTP id h7DFJRV19341;
	Wed, 13 Aug 2003 09:19:27 -0600
Message-ID: <3F3A5615.5010605@isode.com>
Date: Wed, 13 Aug 2003 16:15:33 +0100
From: Alexey Melnikov <Alexey.Melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
CC: "Ramsay, Ron" <Ron.Ramsay@ca.com>, LDAPBis WG <ietf-ldapbis@OpenLDAP.org>
Subject: Re: Comments about draft-ietf-ldapbis-authmeth-05.txt
References: <1395B4B334FCC143B36AF788E68B638160BC40@ausyms21.ca.com> <1395B4B334FCC143B36AF788E68B638160BC40@ausyms21.ca.com> <5.2.0.9.0.20030813071436.01c1ec78@127.0.0.1>
In-Reply-To: <5.2.0.9.0.20030813071436.01c1ec78@127.0.0.1>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Kurt D. Zeilenga wrote:

>At 06:14 AM 8/13/2003, Alexey Melnikov wrote:
>  
>
>>I suggest that some text about the issue should be included in draft-ietf-ldapbis-authmeth.
>>    
>>
>
>If authmeth says anything about DNs and DIGEST-MD5, it should say
>that the DIGEST-MD5 username and realm fields are, per the DIGEST-MD5
>TS,
>
Can you point me to the section where DIGEST-MD5 says that.

> syntactically and semantically not DNs.  They are syntactically
>and semantically simple usernames and realms, respectively.
>
I disagree. DIGEST-MD5 doesn't say anything about syntax of username or 
realm, so it definitely allows for DN syntax.
And because there is no common definition of "simple username" I would 
argue that a DN can be considered one for LDAP ;-).
(On a related note, I've seen IMAP servers that have used DNs as usernames).

Alexey




From owner-ietf-ldapbis@OpenLDAP.org  Wed Aug 13 14:22:41 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28763
	for <ldapbis-archive@lists.ietf.org>; Wed, 13 Aug 2003 14:22:41 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h7DI8CP1026109;
	Wed, 13 Aug 2003 18:21:21 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h7DI7Sei026100;
	Wed, 13 Aug 2003 18:07:28 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 13 Aug 2003 18:07:28 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h7DI7RNf026090
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 13 Aug 2003 18:07:27 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from nomad.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.8/8.12.8) with ESMTP id h7DI6w5t000823;
	Wed, 13 Aug 2003 18:06:59 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030813100023.01c258b0@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Wed, 13 Aug 2003 11:08:15 -0700
To: Alexey Melnikov <Alexey.Melnikov@isode.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: Comments about draft-ietf-ldapbis-authmeth-05.txt
Cc: "Ramsay, Ron" <Ron.Ramsay@ca.com>, LDAPBis WG <ietf-ldapbis@OpenLDAP.org>
In-Reply-To: <3F3A5615.5010605@isode.com>
References: <5.2.0.9.0.20030813071436.01c1ec78@127.0.0.1>
 <1395B4B334FCC143B36AF788E68B638160BC40@ausyms21.ca.com>
 <1395B4B334FCC143B36AF788E68B638160BC40@ausyms21.ca.com>
 <5.2.0.9.0.20030813071436.01c1ec78@127.0.0.1>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

At 08:15 AM 8/13/2003, Alexey Melnikov wrote:
>Kurt D. Zeilenga wrote:
>
>>At 06:14 AM 8/13/2003, Alexey Melnikov wrote:
>> 
>>
>>>I suggest that some text about the issue should be included in draft-ietf-ldapbis-authmeth.
>>>   
>>
>>If authmeth says anything about DNs and DIGEST-MD5, it should say
>>that the DIGEST-MD5 username and realm fields are, per the DIGEST-MD5
>>TS,
>Can you point me to the section where DIGEST-MD5 says that.

The DIGEST-MD5 TS [RFC2831] defines a username to be the user's
name (account) in a realm where the realm is a collection of names
(accounts), both have the form of a simple string and are to be
compared as simple strings.

>>syntactically and semantically not DNs.  They are syntactically
>>and semantically simple usernames and realms, respectively.
>I disagree. DIGEST-MD5 doesn't say anything about syntax of username or realm,

DIGEST-MD5 defines the syntax of the username and realm using ABNF.

>so it definitely allows for DN syntax.

It allows usernames that **look like** a string representation of a DN to
appear in the protocol, but they are not DNs to the protocol.  They
are usernames to the protocol.  One can have a realm that looks like
a domain name, but to the protocol its a realm.  The username is matched
per the username matching rules and not DN matching rules and the realm
is matched per realm matching rules and not domain matching rules.

>And because there is no common definition of "simple username" I would argue that a DN can be considered one for LDAP ;-).

There is a common definition, it's a "simple user name", e.g. an
account name.  A DN doesn't name a user, it names a entry.

>(On a related note, I've seen IMAP servers that have used DNs as usernames).

Did these IMAP servers allow all equivalent string representations
of the DN which referred to a user to be used as equivalent usernames in
DIGEST-MD5?  If no, then obviously the IMAP server didn't support
DNs as usernames.  It supported usernames which **looked like** DN
strings.

Kurt




From owner-ietf-ldapbis@OpenLDAP.org  Wed Aug 13 21:17:06 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA13653
	for <ldapbis-archive@lists.ietf.org>; Wed, 13 Aug 2003 21:17:06 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h7E1EENj061368;
	Thu, 14 Aug 2003 01:14:50 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h7E1AJpm061320;
	Thu, 14 Aug 2003 01:10:19 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 14 Aug 2003 01:10:19 +0000
Received: from ausyms50.ca.com ([155.35.248.106])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h7E1AGNf061286;
	Thu, 14 Aug 2003 01:10:17 GMT
	(envelope-from Ron.Ramsay@ca.com)
Received: from ausyms21.ca.com ([155.35.201.5]) by ausyms50.ca.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Thu, 14 Aug 2003 11:09:55 +1000
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: Comments about draft-ietf-ldapbis-authmeth-05.txt
Date: Thu, 14 Aug 2003 11:09:55 +1000
Message-ID: <1395B4B334FCC143B36AF788E68B638167C9FE@ausyms21.ca.com>
Thread-Topic: Comments about draft-ietf-ldapbis-authmeth-05.txt
Thread-Index: AcNhplnKjzTBKVQfQF+tgRfaE9mbRgAWiAOw
From: "Ramsay, Ron" <Ron.Ramsay@ca.com>
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>,
        "Alexey Melnikov" <Alexey.Melnikov@isode.com>
Cc: "LDAPBis WG" <ietf-ldapbis@OpenLDAP.org>
X-OriginalArrivalTime: 14 Aug 2003 01:09:55.0361 (UTC) FILETIME=[C5BE4910:01C36200]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by boole.openldap.org id h7E1AHNf061291
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 8bit

But, but, but ....

They are being used in an LDAP context!

If Digest-MD5 has to be 'localised' to LDAP, it should be done. If it can't be done, let's choose something like CRAM-MD5 for the mandatory-to-implement authentication method.

Ron

-----Original Message-----
From: Kurt D. Zeilenga [mailto:Kurt@OpenLDAP.org]
Sent: Thursday, 14 August 2003 00:23
To: Alexey Melnikov
Cc: Ramsay, Ron; LDAPBis WG
Subject: Re: Comments about draft-ietf-ldapbis-authmeth-05.txt


At 06:14 AM 8/13/2003, Alexey Melnikov wrote:
>I suggest that some text about the issue should be included in draft-ietf-ldapbis-authmeth.

If authmeth says anything about DNs and DIGEST-MD5, it should say
that the DIGEST-MD5 username and realm fields are, per the DIGEST-MD5
TS, syntactically and semantically not DNs.  They are syntactically
and semantically simple usernames and realms, respectively.

Kurt 





From owner-ietf-ldapbis@OpenLDAP.org  Sun Aug 17 09:41:23 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA13016
	for <ldapbis-archive@lists.ietf.org>; Sun, 17 Aug 2003 09:41:21 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h7HDchNn015711;
	Sun, 17 Aug 2003 13:40:09 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h7HDY7FP015650;
	Sun, 17 Aug 2003 13:34:07 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Sun, 17 Aug 2003 13:34:07 +0000
Received: from rembrandt.esys.ca (rembrandt.esys.ca [198.161.92.131])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h7HDY4Nf015620;
	Sun, 17 Aug 2003 13:34:04 GMT
	(envelope-from Alexey.Melnikov@isode.com)
Received: from isode.com ([62.3.217.250])
	(authenticated)
	by rembrandt.esys.ca (8.11.6/8.11.0.Beta0) with ESMTP id h7HDbTV02576;
	Sun, 17 Aug 2003 07:37:29 -0600
Message-ID: <3F3E47E4.8080307@isode.com>
Date: Sat, 16 Aug 2003 16:04:04 +0100
From: Alexey Melnikov <Alexey.Melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Ramsay, Ron" <Ron.Ramsay@ca.com>
CC: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>,
        LDAPBis WG <ietf-ldapbis@OpenLDAP.org>
Subject: Re: Comments about draft-ietf-ldapbis-authmeth-05.txt
References: <1395B4B334FCC143B36AF788E68B638167C9FE@ausyms21.ca.com>
In-Reply-To: <1395B4B334FCC143B36AF788E68B638167C9FE@ausyms21.ca.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Ramsay, Ron wrote:

>But, but, but ....
>
>They are being used in an LDAP context!
>
I agree.

>If Digest-MD5 has to be 'localised' to LDAP, it should be done. If it can't be done, let's choose something like CRAM-MD5 for the mandatory-to-implement authentication method.
>
CRAM-MD5 will not be better than DIGEST-MD5 in this respect, and 
considering lack of security of the former this is a non-starter.

I don't believe that DIGEST-MD5 says anything that would prevent using 
DNs with it.

>Ron
>
>-----Original Message-----
>From: Kurt D. Zeilenga [mailto:Kurt@OpenLDAP.org]
>Sent: Thursday, 14 August 2003 00:23
>To: Alexey Melnikov
>Cc: Ramsay, Ron; LDAPBis WG
>Subject: Re: Comments about draft-ietf-ldapbis-authmeth-05.txt
>
>
>At 06:14 AM 8/13/2003, Alexey Melnikov wrote:
>  
>
>>I suggest that some text about the issue should be included in draft-ietf-ldapbis-authmeth.
>>    
>>
>
>If authmeth says anything about DNs and DIGEST-MD5, it should say
>that the DIGEST-MD5 username and realm fields are, per the DIGEST-MD5
>TS, syntactically and semantically not DNs.  They are syntactically
>and semantically simple usernames and realms, respectively.
>
>  
>
Alexey
 





From owner-ietf-ldapbis@OpenLDAP.org  Sun Aug 17 09:41:31 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA13033
	for <ldapbis-archive@lists.ietf.org>; Sun, 17 Aug 2003 09:41:31 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h7HDchNp015711;
	Sun, 17 Aug 2003 13:40:09 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h7HDXoIR015609;
	Sun, 17 Aug 2003 13:33:50 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Sun, 17 Aug 2003 13:33:50 +0000
Received: from rembrandt.esys.ca (rembrandt.esys.ca [198.161.92.131])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h7HDXkNf015579;
	Sun, 17 Aug 2003 13:33:47 GMT
	(envelope-from Alexey.Melnikov@isode.com)
Received: from isode.com ([62.3.217.250])
	(authenticated)
	by rembrandt.esys.ca (8.11.6/8.11.0.Beta0) with ESMTP id h7HDbYV02580;
	Sun, 17 Aug 2003 07:37:34 -0600
Message-ID: <3F3E4C95.8080806@isode.com>
Date: Sat, 16 Aug 2003 16:24:05 +0100
From: Alexey Melnikov <Alexey.Melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
CC: "Ramsay, Ron" <Ron.Ramsay@ca.com>, LDAPBis WG <ietf-ldapbis@OpenLDAP.org>
Subject: Re: Comments about draft-ietf-ldapbis-authmeth-05.txt
References: <5.2.0.9.0.20030813071436.01c1ec78@127.0.0.1> <1395B4B334FCC143B36AF788E68B638160BC40@ausyms21.ca.com> <1395B4B334FCC143B36AF788E68B638160BC40@ausyms21.ca.com> <5.2.0.9.0.20030813071436.01c1ec78@127.0.0.1> <5.2.0.9.0.20030813100023.01c258b0@127.0.0.1>
In-Reply-To: <5.2.0.9.0.20030813100023.01c258b0@127.0.0.1>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Kurt D. Zeilenga wrote:

>At 08:15 AM 8/13/2003, Alexey Melnikov wrote:
>  
>
>>Kurt D. Zeilenga wrote:
>>    
>>
>>>At 06:14 AM 8/13/2003, Alexey Melnikov wrote:
>>>      
>>>
>>>>I suggest that some text about the issue should be included in draft-ietf-ldapbis-authmeth.
>>>>  
>>>>        
>>>>
>>>If authmeth says anything about DNs and DIGEST-MD5, it should say
>>>that the DIGEST-MD5 username and realm fields are, per the DIGEST-MD5
>>>TS,
>>>      
>>>
>>Can you point me to the section where DIGEST-MD5 says that.
>>    
>>
>
>The DIGEST-MD5 TS [RFC2831] defines a username to be the user's
>name (account) in a realm where the realm is a collection of names
>(accounts), both have the form of a simple string
>
Kurt, can you please point me to a formal definition of "simple username".

> and are to be compared as simple strings.
>
Fine, I don't disagree with that.

But DNs are used in simple bind. So it is quite logical to allow to use 
DNs in SASL as well.
(And for implementation of other protocols with a login command that I 
know this is true.)

So, if the server allows for DN form of usernames, the client should 
canonicalize a DN before passing it to the server to avoid 
interoperability problems. This is pretty much what my previous message 
suggested. I wasn't suggesting that the server should do that after 
receiving the username.

The same is true for a realm. If the server is using DNs as realms, it 
should canonicalize it before sending to the client. The client must not 
do any canonicalization.

[Minor comments below:]

>>>syntactically and semantically not DNs.  They are syntactically
>>>and semantically simple usernames and realms, respectively.
>>>      
>>>
>>I disagree. DIGEST-MD5 doesn't say anything about syntax of username or realm,
>>    
>>
>
>DIGEST-MD5 defines the syntax of the username and realm using ABNF.
>
Which is just a sequence of Unicode characters (no NUL allowed) 
represented in UTF8, nothing more.
Although the format of authentication ids (usernames) is SASL mechanism 
specific, DIGEST-MD5 doesn't have any restrictions other than the one 
mentioned above.

>>so it definitely allows for DN syntax.
>>    
>>
>
>It allows usernames that **look like** a string representation of a DN to
>appear in the protocol, but they are not DNs to the protocol.  They
>are usernames to the protocol.  One can have a realm that looks like
>a domain name, but to the protocol its a realm.  The username is matched
>per the username matching rules and not DN matching rules and the realm
>is matched per realm matching rules and not domain matching rules.
>  
>
>>And because there is no common definition of "simple username" I would argue that a DN can be considered one for LDAP ;-).
>>    
>>
>
>There is a common definition, it's a "simple user name", e.g. an
>account name.  A DN doesn't name a user, it names a entry.
>
Of course I wasn't talking about an *arbitrary* DN, but only that 
represents a user or a group of users.

>>(On a related note, I've seen IMAP servers that have used DNs as usernames).
>>    
>>
>
>Did these IMAP servers allow all equivalent string representations
>of the DN which referred to a user to be used as equivalent usernames in
>DIGEST-MD5?
>
Frankly I don't know, I don't remember if the server was supporting 
DIGEST-MD5.

>  If no, then obviously the IMAP server didn't support
>DNs as usernames.  It supported usernames which **looked like** DN
>strings.
>  
>
Alexey





From owner-ietf-ldapbis@OpenLDAP.org  Sun Aug 17 12:30:42 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA16020
	for <ldapbis-archive@lists.ietf.org>; Sun, 17 Aug 2003 12:30:42 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h7HGKiNr021484;
	Sun, 17 Aug 2003 16:28:13 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h7HGFxLi021212;
	Sun, 17 Aug 2003 16:15:59 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Sun, 17 Aug 2003 16:15:59 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h7HGFvNf021202
	for <ietf-ldapbis@OpenLDAP.org>; Sun, 17 Aug 2003 16:15:57 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from nomad.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.9/8.12.8) with ESMTP id h7HGFRiw020024;
	Sun, 17 Aug 2003 16:15:27 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030817080110.01c0d500@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Sun, 17 Aug 2003 09:16:42 -0700
To: Alexey Melnikov <Alexey.Melnikov@isode.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: Comments about draft-ietf-ldapbis-authmeth-05.txt
Cc: "Ramsay, Ron" <Ron.Ramsay@ca.com>, LDAPBis WG <ietf-ldapbis@OpenLDAP.org>
In-Reply-To: <3F3E4C95.8080806@isode.com>
References: <5.2.0.9.0.20030813100023.01c258b0@127.0.0.1>
 <5.2.0.9.0.20030813071436.01c1ec78@127.0.0.1>
 <1395B4B334FCC143B36AF788E68B638160BC40@ausyms21.ca.com>
 <1395B4B334FCC143B36AF788E68B638160BC40@ausyms21.ca.com>
 <5.2.0.9.0.20030813071436.01c1ec78@127.0.0.1>
 <5.2.0.9.0.20030813100023.01c258b0@127.0.0.1>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

Below are few additional technical comments...

Basically what you are asking is that we state additional requirements that
implementations canonicalize
        a) all usernames, or
        b) all usernames which look like string representations of DNs.

Both require the specification of an algorithm to produce a canonical string
representation of a DN.  The latter, (b), requires a specification of which input
strings are/are not to be canonicalized.

First, I note that it is not generally possible to produce a canonical string
representation of a DN solely based on input of a non-canonical string
representation. Minimally, applicable schema is needed.

Second, both a) and b) will introduce additional interoperability problems with
significant security implications.  In particular, if an existing system were
to have to different users "cn=foo" and "CN=FOO", one of these users
would no longer be able to long in as both a) and b) would cause these strings
to be treated as representing the same user where today they are clearly two
different users.

Hence, even if we had a canonicalization algorithm, it would be inappropriate
to specify it be used here.  We need to preserve current semantics.

Kurt



At 08:24 AM 8/16/2003, Alexey Melnikov wrote:
>Kurt D. Zeilenga wrote:
>
>>At 08:15 AM 8/13/2003, Alexey Melnikov wrote:
>> 
>>
>>>Kurt D. Zeilenga wrote:
>>>   
>>>
>>>>At 06:14 AM 8/13/2003, Alexey Melnikov wrote:
>>>>     
>>>>
>>>>>I suggest that some text about the issue should be included in draft-ietf-ldapbis-authmeth.
>>>>> 
>>>>>       
>>>>If authmeth says anything about DNs and DIGEST-MD5, it should say
>>>>that the DIGEST-MD5 username and realm fields are, per the DIGEST-MD5
>>>>TS,
>>>>     
>>>Can you point me to the section where DIGEST-MD5 says that.
>>>   
>>
>>The DIGEST-MD5 TS [RFC2831] defines a username to be the user's
>>name (account) in a realm where the realm is a collection of names
>>(accounts), both have the form of a simple string
>Kurt, can you please point me to a formal definition of "simple username".

RFC 2831 does not use the term "simple username".  It uses the term "username".
I believe RFC 2831 is reasonable clear that a username is a simple string used
as a user (account) name.  "simple" here meaning that the syntax and semantics
of the string are simple.


>>and are to be compared as simple strings.
>Fine, I don't disagree with that.

>But DNs are used in simple bind. So it is quite logical to allow to use DNs in SASL as well.
>(And for implementation of other protocols with a login command that I know this is true.)
>
>So, if the server allows for DN form of usernames, the client should canonicalize a DN before passing it to the server to avoid interoperability problems. This is pretty much what my previous message suggested. I wasn't suggesting that the server should do that after receiving the username.

How does the client determine whether the string entered by the user should or
shouldn't be canonized?  Is the client to canonicalize all strings which *look
like" DN string representations?  That obviously would break some usernames.

>The same is true for a realm. If the server is using DNs as realms, it should canonicalize it before sending to the client. The client must not do any canonicalization.

And that would break some realms.

Also, saying that the client should canonicalize DN strings would necessitate
defining a canonical string representation of a DN.  Note that it is not generally
possible to generate a canonical DN string based solely on the input of a DN string

>>DIGEST-MD5 defines the syntax of the username and realm using ABNF.
>Which is just a sequence of Unicode characters (no NUL allowed) represented in UTF8, nothing more.

RFC 2831 says a username is a sequence of UTF-8 encoded Unicode characters
which represent a user name.

RFC 2831 does not say a username is a sequence of UTF-8 encoded Unicode
characters which represent a DN.

>Although the format of authentication ids (usernames) is SASL mechanism specific, DIGEST-MD5 doesn't have any restrictions other than the one mentioned above.

It would be, in my opinion, inappropriate for LDAP to place additional syntax
and semantics upon the DIGEST-MD5 username and realm.

>>There is a common definition, it's a "simple user name", e.g. an
>>account name.  A DN doesn't name a user, it names a entry.
>Of course I wasn't talking about an *arbitrary* DN, but only that represents a user or a group of users.

My point is a "distinguished names" and a "user names" are different abstractions.
The username string represents a user name not a distinguished name.

>>>(On a related note, I've seen IMAP servers that have used DNs as usernames).
>>
>>Did these IMAP servers allow all equivalent string representations
>>of the DN which referred to a user to be used as equivalent usernames in
>>DIGEST-MD5?
>Frankly I don't know, I don't remember if the server was supporting DIGEST-MD5.

Even if was PLAIN or CRAM-MD5, I seriously doubt the IMAP server treated all
equivalent DN strings representations (stuffed in a username field) as being
equivalent.


>> If no, then obviously the IMAP server didn't support
>>DNs as usernames.  It supported usernames which **looked like** DN
>>strings.
>> 
>Alexey
>
>



From owner-ietf-ldapbis@OpenLDAP.org  Mon Aug 18 02:24:48 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA11695
	for <ldapbis-archive@lists.ietf.org>; Mon, 18 Aug 2003 02:24:46 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h7I6KnNj038134;
	Mon, 18 Aug 2003 06:21:53 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h7I6Ibpa038112;
	Mon, 18 Aug 2003 06:18:37 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 18 Aug 2003 06:18:37 +0000
Received: from ausyms50.ca.com ([155.35.248.106])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h7I6IWNf038077;
	Mon, 18 Aug 2003 06:18:33 GMT
	(envelope-from Ron.Ramsay@ca.com)
Received: from ausyms21.ca.com ([155.35.201.5]) by ausyms50.ca.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Mon, 18 Aug 2003 16:18:00 +1000
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: Comments about draft-ietf-ldapbis-authmeth-05.txt
Date: Mon, 18 Aug 2003 16:18:00 +1000
Message-ID: <1395B4B334FCC143B36AF788E68B63816B889A@ausyms21.ca.com>
Thread-Topic: Comments about draft-ietf-ldapbis-authmeth-05.txt
Thread-Index: AcNk2tfSszzTqfZEQtetUN5nXT0GzwAdHB9Q
From: "Ramsay, Ron" <Ron.Ramsay@ca.com>
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>,
        "Alexey Melnikov" <Alexey.Melnikov@isode.com>
Cc: "LDAPBis WG" <ietf-ldapbis@OpenLDAP.org>
X-OriginalArrivalTime: 18 Aug 2003 06:18:00.0886 (UTC) FILETIME=[79A08D60:01C36550]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by boole.openldap.org id h7I6IYNf038083
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 8bit

Hi Kurt,

I agree that we cannot canonicalise DNs (though I disagree that cn=foo and CN=FOO are different usernames). The canonicalisation was proposed to obviate the necessity of storing passwords in the clear.

I also think the authmeth has the power to profile Digest-MD5. If we simply state

1. The DN provided by the client in the bind is to be used (byte-for-byte) to calculate the required hashes, and
2. The realm provided by the server is to be used (byte-for-byte) to calculate hashes

then I think Digest-MD5 can be used in LDAP, but the passwords have to be stored in-the-clear. The realm suggestions of Alexey can also be added to the profile. (Is there any reason for requiring that the realm not be ""?)

Ron

-----Original Message-----
From: Kurt D. Zeilenga [mailto:Kurt@OpenLDAP.org]
Sent: Monday, 18 August 2003 02:17
To: Alexey Melnikov
Cc: Ramsay, Ron; LDAPBis WG
Subject: Re: Comments about draft-ietf-ldapbis-authmeth-05.txt


Below are few additional technical comments...

Basically what you are asking is that we state additional requirements that
implementations canonicalize
        a) all usernames, or
        b) all usernames which look like string representations of DNs.

Both require the specification of an algorithm to produce a canonical string
representation of a DN.  The latter, (b), requires a specification of which input
strings are/are not to be canonicalized.

First, I note that it is not generally possible to produce a canonical string
representation of a DN solely based on input of a non-canonical string
representation. Minimally, applicable schema is needed.

Second, both a) and b) will introduce additional interoperability problems with
significant security implications.  In particular, if an existing system were
to have to different users "cn=foo" and "CN=FOO", one of these users
would no longer be able to long in as both a) and b) would cause these strings
to be treated as representing the same user where today they are clearly two
different users.

Hence, even if we had a canonicalization algorithm, it would be inappropriate
to specify it be used here.  We need to preserve current semantics.

Kurt



At 08:24 AM 8/16/2003, Alexey Melnikov wrote:
>Kurt D. Zeilenga wrote:
>
>>At 08:15 AM 8/13/2003, Alexey Melnikov wrote:
>> 
>>
>>>Kurt D. Zeilenga wrote:
>>>   
>>>
>>>>At 06:14 AM 8/13/2003, Alexey Melnikov wrote:
>>>>     
>>>>
>>>>>I suggest that some text about the issue should be included in draft-ietf-ldapbis-authmeth.
>>>>> 
>>>>>       
>>>>If authmeth says anything about DNs and DIGEST-MD5, it should say
>>>>that the DIGEST-MD5 username and realm fields are, per the DIGEST-MD5
>>>>TS,
>>>>     
>>>Can you point me to the section where DIGEST-MD5 says that.
>>>   
>>
>>The DIGEST-MD5 TS [RFC2831] defines a username to be the user's
>>name (account) in a realm where the realm is a collection of names
>>(accounts), both have the form of a simple string
>Kurt, can you please point me to a formal definition of "simple username".

RFC 2831 does not use the term "simple username".  It uses the term "username".
I believe RFC 2831 is reasonable clear that a username is a simple string used
as a user (account) name.  "simple" here meaning that the syntax and semantics
of the string are simple.


>>and are to be compared as simple strings.
>Fine, I don't disagree with that.

>But DNs are used in simple bind. So it is quite logical to allow to use DNs in SASL as well.
>(And for implementation of other protocols with a login command that I know this is true.)
>
>So, if the server allows for DN form of usernames, the client should canonicalize a DN before passing it to the server to avoid interoperability problems. This is pretty much what my previous message suggested. I wasn't suggesting that the server should do that after receiving the username.

How does the client determine whether the string entered by the user should or
shouldn't be canonized?  Is the client to canonicalize all strings which *look
like" DN string representations?  That obviously would break some usernames.

>The same is true for a realm. If the server is using DNs as realms, it should canonicalize it before sending to the client. The client must not do any canonicalization.

And that would break some realms.

Also, saying that the client should canonicalize DN strings would necessitate
defining a canonical string representation of a DN.  Note that it is not generally
possible to generate a canonical DN string based solely on the input of a DN string

>>DIGEST-MD5 defines the syntax of the username and realm using ABNF.
>Which is just a sequence of Unicode characters (no NUL allowed) represented in UTF8, nothing more.

RFC 2831 says a username is a sequence of UTF-8 encoded Unicode characters
which represent a user name.

RFC 2831 does not say a username is a sequence of UTF-8 encoded Unicode
characters which represent a DN.

>Although the format of authentication ids (usernames) is SASL mechanism specific, DIGEST-MD5 doesn't have any restrictions other than the one mentioned above.

It would be, in my opinion, inappropriate for LDAP to place additional syntax
and semantics upon the DIGEST-MD5 username and realm.

>>There is a common definition, it's a "simple user name", e.g. an
>>account name.  A DN doesn't name a user, it names a entry.
>Of course I wasn't talking about an *arbitrary* DN, but only that represents a user or a group of users.

My point is a "distinguished names" and a "user names" are different abstractions.
The username string represents a user name not a distinguished name.

>>>(On a related note, I've seen IMAP servers that have used DNs as usernames).
>>
>>Did these IMAP servers allow all equivalent string representations
>>of the DN which referred to a user to be used as equivalent usernames in
>>DIGEST-MD5?
>Frankly I don't know, I don't remember if the server was supporting DIGEST-MD5.

Even if was PLAIN or CRAM-MD5, I seriously doubt the IMAP server treated all
equivalent DN strings representations (stuffed in a username field) as being
equivalent.


>> If no, then obviously the IMAP server didn't support
>>DNs as usernames.  It supported usernames which **looked like** DN
>>strings.
>> 
>Alexey
>
>





From owner-ietf-ldapbis@OpenLDAP.org  Mon Aug 18 12:45:50 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25776
	for <ldapbis-archive@lists.ietf.org>; Mon, 18 Aug 2003 12:45:49 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h7IGcrNj059706;
	Mon, 18 Aug 2003 16:43:59 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h7IGc9h5059674;
	Mon, 18 Aug 2003 16:38:09 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 18 Aug 2003 16:38:09 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h7IGc6Nf059664
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 18 Aug 2003 16:38:07 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from nomad.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.9/8.12.8) with ESMTP id h7IGbWsq021233;
	Mon, 18 Aug 2003 16:37:36 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030818082715.01bc6a28@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Mon, 18 Aug 2003 09:38:50 -0700
To: "Ramsay, Ron" <Ron.Ramsay@ca.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: RE: Comments about draft-ietf-ldapbis-authmeth-05.txt
Cc: "Alexey Melnikov" <Alexey.Melnikov@isode.com>,
        "LDAPBis WG" <ietf-ldapbis@OpenLDAP.org>
In-Reply-To: <1395B4B334FCC143B36AF788E68B63816B889A@ausyms21.ca.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

Ron,

It still sounds like you are trying to re-engineer LDAP and its
application of DIGEST-MD5.  DIGEST-MD5 is not designed to support
DN-based credentials.  As we have two mechanisms which are designed
to support such, it seems far more appropriate for those who want to
use DN-based credentials to simple use one of existing mechanism
than for us to try to hack the LDAP TS to support DN-based credentials
in DIGEST-MD5.

At 11:18 PM 8/17/2003, Ramsay, Ron wrote:
>I agree that we cannot canonicalise DNs (though I disagree that cn=foo and CN=FOO are different usernames). The canonicalisation was proposed to obviate the necessity of storing passwords in the clear.
>
>I also think the authmeth has the power to profile Digest-MD5.

There are many reasons why we cannot do such, most have been previously
discussed on the list.   However, I note that one of the reasons is that
it will likely interfer with proxying of DIGEST-MD5 authentication
requests to a "shared back-end authentication service" and/or
implementing an LDAP-accessible "shared back-end authentication
service".

>If we simply state

It's not so simple.  

>1. The DN provided by the client in the bind is to be used (byte-for-byte) to calculate the required hashes, and
>2. The realm provided by the server is to be used (byte-for-byte) to calculate hashes

First, I note, that servers are required to use all usernames and realms
byte-for-byte.  What's new to LDAP is that servers are to treat the
username/realm as DNs in interactions with the (possibly shared)
back-end authentication service.  Many of today's servers don't do that and
those that do don't do it any standard way (as there is no formal
specification of how to do that).  It is likely that any change in this
area would cause interoperability problems, some of which likely have
significant security considerations.

To standardize such interaction would require engineering work on how to
deal with the problem that dnMatch(dnString, SASLprep(dnString)) may be
FALSE for some representations of a DN.  This implies that one either
needs to restrict users to a subset of DN representations or apply a transform
such that dnMatch(dnString, SASLprep(transform(dnString))) is TRUE for all
possible dnStrings.  Both alternatives are problematic.

>then I think Digest-MD5 can be used in LDAP, but the passwords have to be stored in-the-clear.

I do not think it appropriate for authmeth to suggest DIGEST-MD5 passwords
are to be stored in-the-clear when DIGEST-MD5 was specifically designed
to avoid such.

>The realm suggestions of Alexey can also be added to the profile. (Is there any reason for requiring that the realm not be ""?)
>
>Ron
>
>-----Original Message-----
>From: Kurt D. Zeilenga [mailto:Kurt@OpenLDAP.org]
>Sent: Monday, 18 August 2003 02:17
>To: Alexey Melnikov
>Cc: Ramsay, Ron; LDAPBis WG
>Subject: Re: Comments about draft-ietf-ldapbis-authmeth-05.txt
>
>
>Below are few additional technical comments...
>
>Basically what you are asking is that we state additional requirements that
>implementations canonicalize
>        a) all usernames, or
>        b) all usernames which look like string representations of DNs.
>
>Both require the specification of an algorithm to produce a canonical string
>representation of a DN.  The latter, (b), requires a specification of which input
>strings are/are not to be canonicalized.
>
>First, I note that it is not generally possible to produce a canonical string
>representation of a DN solely based on input of a non-canonical string
>representation. Minimally, applicable schema is needed.
>
>Second, both a) and b) will introduce additional interoperability problems with
>significant security implications.  In particular, if an existing system were
>to have to different users "cn=foo" and "CN=FOO", one of these users
>would no longer be able to long in as both a) and b) would cause these strings
>to be treated as representing the same user where today they are clearly two
>different users.
>
>Hence, even if we had a canonicalization algorithm, it would be inappropriate
>to specify it be used here.  We need to preserve current semantics.
>
>Kurt
>
>
>
>At 08:24 AM 8/16/2003, Alexey Melnikov wrote:
>>Kurt D. Zeilenga wrote:
>>
>>>At 08:15 AM 8/13/2003, Alexey Melnikov wrote:
>>> 
>>>
>>>>Kurt D. Zeilenga wrote:
>>>>   
>>>>
>>>>>At 06:14 AM 8/13/2003, Alexey Melnikov wrote:
>>>>>     
>>>>>
>>>>>>I suggest that some text about the issue should be included in draft-ietf-ldapbis-authmeth.
>>>>>> 
>>>>>>       
>>>>>If authmeth says anything about DNs and DIGEST-MD5, it should say
>>>>>that the DIGEST-MD5 username and realm fields are, per the DIGEST-MD5
>>>>>TS,
>>>>>     
>>>>Can you point me to the section where DIGEST-MD5 says that.
>>>>   
>>>
>>>The DIGEST-MD5 TS [RFC2831] defines a username to be the user's
>>>name (account) in a realm where the realm is a collection of names
>>>(accounts), both have the form of a simple string
>>Kurt, can you please point me to a formal definition of "simple username".
>
>RFC 2831 does not use the term "simple username".  It uses the term "username".
>I believe RFC 2831 is reasonable clear that a username is a simple string used
>as a user (account) name.  "simple" here meaning that the syntax and semantics
>of the string are simple.
>
>
>>>and are to be compared as simple strings.
>>Fine, I don't disagree with that.
>
>>But DNs are used in simple bind. So it is quite logical to allow to use DNs in SASL as well.
>>(And for implementation of other protocols with a login command that I know this is true.)
>>
>>So, if the server allows for DN form of usernames, the client should canonicalize a DN before passing it to the server to avoid interoperability problems. This is pretty much what my previous message suggested. I wasn't suggesting that the server should do that after receiving the username.
>
>How does the client determine whether the string entered by the user should or
>shouldn't be canonized?  Is the client to canonicalize all strings which *look
>like" DN string representations?  That obviously would break some usernames.
>
>>The same is true for a realm. If the server is using DNs as realms, it should canonicalize it before sending to the client. The client must not do any canonicalization.
>
>And that would break some realms.
>
>Also, saying that the client should canonicalize DN strings would necessitate
>defining a canonical string representation of a DN.  Note that it is not generally
>possible to generate a canonical DN string based solely on the input of a DN string
>
>>>DIGEST-MD5 defines the syntax of the username and realm using ABNF.
>>Which is just a sequence of Unicode characters (no NUL allowed) represented in UTF8, nothing more.
>
>RFC 2831 says a username is a sequence of UTF-8 encoded Unicode characters
>which represent a user name.
>
>RFC 2831 does not say a username is a sequence of UTF-8 encoded Unicode
>characters which represent a DN.
>
>>Although the format of authentication ids (usernames) is SASL mechanism specific, DIGEST-MD5 doesn't have any restrictions other than the one mentioned above.
>
>It would be, in my opinion, inappropriate for LDAP to place additional syntax
>and semantics upon the DIGEST-MD5 username and realm.
>
>>>There is a common definition, it's a "simple user name", e.g. an
>>>account name.  A DN doesn't name a user, it names a entry.
>>Of course I wasn't talking about an *arbitrary* DN, but only that represents a user or a group of users.
>
>My point is a "distinguished names" and a "user names" are different abstractions.
>The username string represents a user name not a distinguished name.
>
>>>>(On a related note, I've seen IMAP servers that have used DNs as usernames).
>>>
>>>Did these IMAP servers allow all equivalent string representations
>>>of the DN which referred to a user to be used as equivalent usernames in
>>>DIGEST-MD5?
>>Frankly I don't know, I don't remember if the server was supporting DIGEST-MD5.
>
>Even if was PLAIN or CRAM-MD5, I seriously doubt the IMAP server treated all
>equivalent DN strings representations (stuffed in a username field) as being
>equivalent.
>
>
>>> If no, then obviously the IMAP server didn't support
>>>DNs as usernames.  It supported usernames which **looked like** DN
>>>strings.
>>> 
>>Alexey
>>
>>



From owner-ietf-ldapbis@OpenLDAP.org  Mon Aug 18 19:17:18 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09076
	for <ldapbis-archive@lists.ietf.org>; Mon, 18 Aug 2003 19:17:17 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h7IN8sNj070781;
	Mon, 18 Aug 2003 23:14:20 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h7IN5YT4070702;
	Mon, 18 Aug 2003 23:05:35 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 18 Aug 2003 23:05:34 +0000
Received: from adacel.com (gunsmoke.adacel.com.au [210.11.130.7])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h7IN5UNf070673
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 18 Aug 2003 23:05:31 GMT
	(envelope-from mark.ennis@adacel.com)
Received: from nexus.adacel.com (Not Verified[10.32.240.1]) by adacel.com with NetIQ MailMarshal (v5.5.3.16)
	id <B000133ff5>; Tue, 19 Aug 2003 09:00:59 +1000
Received: (qmail 8687 invoked from network); 18 Aug 2003 22:58:40 -0000
Received: from unknown (HELO adacel.com) (10.32.24.164)
  by nexus.adacel.com with SMTP; 18 Aug 2003 22:58:40 -0000
Message-ID: <3F415BA3.4040108@adacel.com>
Date: Tue, 19 Aug 2003 09:05:07 +1000
From: Mark Ennis <mark.ennis@adacel.com>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3.1) Gecko/20030425
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
CC: "Ramsay, Ron" <Ron.Ramsay@ca.com>,
        Alexey Melnikov <Alexey.Melnikov@isode.com>,
        LDAPBis WG <ietf-ldapbis@OpenLDAP.org>
Subject: Re: Comments about draft-ietf-ldapbis-authmeth-05.txt
References: <5.2.0.9.0.20030818082715.01bc6a28@127.0.0.1>
In-Reply-To: <5.2.0.9.0.20030818082715.01bc6a28@127.0.0.1>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Kurt,

It still seems to me as though you are the one re-engineering LDAP and 
its application of DIGEST-MD5. I have yet to come across anything in the 
LDAP or SASL specifications which preclude the use of distinguished name 
strings in the DIGEST-MD5 username value, except possibly the 
normalisation of the username field being proposed in the SASLprep work. 
After all, we should not forget that an LDAPDN *is* an UTF8 string in 
the protocol, and provided it is not mangled (normalised or SASLprep'd) 
prior to the server receiving it, it can then be interpreted (and 
matched) as a LDAPDN. Normalisation should occur prior to generating the 
digests at both server and client to produce consistent results and 
allow the possibility of storing the A1 hash rather than cleartext 
passwords.

I agree that the LDAP specifications do not preclude the use of 
non-LDAPDN strings in the username field, allowing interaction with 
(possibly shared) back-end authentication services. I see no particular 
problem with using the realm to distinguished how the username field 
should be interpreted.

- Mark.

Kurt D. Zeilenga wrote:
> Ron,
> 
> It still sounds like you are trying to re-engineer LDAP and its
> application of DIGEST-MD5.  DIGEST-MD5 is not designed to support
> DN-based credentials.  As we have two mechanisms which are designed
> to support such, it seems far more appropriate for those who want to
> use DN-based credentials to simple use one of existing mechanism
> than for us to try to hack the LDAP TS to support DN-based credentials
> in DIGEST-MD5.
> 
> At 11:18 PM 8/17/2003, Ramsay, Ron wrote:
> 
>>I agree that we cannot canonicalise DNs (though I disagree that cn=foo and CN=FOO are different usernames). The canonicalisation was proposed to obviate the necessity of storing passwords in the clear.
>>
>>I also think the authmeth has the power to profile Digest-MD5.
> 
> 
> There are many reasons why we cannot do such, most have been previously
> discussed on the list.   However, I note that one of the reasons is that
> it will likely interfer with proxying of DIGEST-MD5 authentication
> requests to a "shared back-end authentication service" and/or
> implementing an LDAP-accessible "shared back-end authentication
> service".
> 
> 
>>If we simply state
> 
> 
> It's not so simple.  
> 
> 
>>1. The DN provided by the client in the bind is to be used (byte-for-byte) to calculate the required hashes, and
>>2. The realm provided by the server is to be used (byte-for-byte) to calculate hashes
> 
> 
> First, I note, that servers are required to use all usernames and realms
> byte-for-byte.  What's new to LDAP is that servers are to treat the
> username/realm as DNs in interactions with the (possibly shared)
> back-end authentication service.  Many of today's servers don't do that and
> those that do don't do it any standard way (as there is no formal
> specification of how to do that).  It is likely that any change in this
> area would cause interoperability problems, some of which likely have
> significant security considerations.
> 
> To standardize such interaction would require engineering work on how to
> deal with the problem that dnMatch(dnString, SASLprep(dnString)) may be
> FALSE for some representations of a DN.  This implies that one either
> needs to restrict users to a subset of DN representations or apply a transform
> such that dnMatch(dnString, SASLprep(transform(dnString))) is TRUE for all
> possible dnStrings.  Both alternatives are problematic.
> 
> 
>>then I think Digest-MD5 can be used in LDAP, but the passwords have to be stored in-the-clear.
> 
> 
> I do not think it appropriate for authmeth to suggest DIGEST-MD5 passwords
> are to be stored in-the-clear when DIGEST-MD5 was specifically designed
> to avoid such.
> 
> 
>>The realm suggestions of Alexey can also be added to the profile. (Is there any reason for requiring that the realm not be ""?)
>>
>>Ron
>>
>>-----Original Message-----
>>From: Kurt D. Zeilenga [mailto:Kurt@OpenLDAP.org]
>>Sent: Monday, 18 August 2003 02:17
>>To: Alexey Melnikov
>>Cc: Ramsay, Ron; LDAPBis WG
>>Subject: Re: Comments about draft-ietf-ldapbis-authmeth-05.txt
>>
>>
>>Below are few additional technical comments...
>>
>>Basically what you are asking is that we state additional requirements that
>>implementations canonicalize
>>       a) all usernames, or
>>       b) all usernames which look like string representations of DNs.
>>
>>Both require the specification of an algorithm to produce a canonical string
>>representation of a DN.  The latter, (b), requires a specification of which input
>>strings are/are not to be canonicalized.
>>
>>First, I note that it is not generally possible to produce a canonical string
>>representation of a DN solely based on input of a non-canonical string
>>representation. Minimally, applicable schema is needed.
>>
>>Second, both a) and b) will introduce additional interoperability problems with
>>significant security implications.  In particular, if an existing system were
>>to have to different users "cn=foo" and "CN=FOO", one of these users
>>would no longer be able to long in as both a) and b) would cause these strings
>>to be treated as representing the same user where today they are clearly two
>>different users.
>>
>>Hence, even if we had a canonicalization algorithm, it would be inappropriate
>>to specify it be used here.  We need to preserve current semantics.
>>
>>Kurt
>>
>>
>>
>>At 08:24 AM 8/16/2003, Alexey Melnikov wrote:
>>
>>>Kurt D. Zeilenga wrote:
>>>
>>>
>>>>At 08:15 AM 8/13/2003, Alexey Melnikov wrote:
>>>>
>>>>
>>>>
>>>>>Kurt D. Zeilenga wrote:
>>>>>  
>>>>>
>>>>>
>>>>>>At 06:14 AM 8/13/2003, Alexey Melnikov wrote:
>>>>>>    
>>>>>>
>>>>>>
>>>>>>>I suggest that some text about the issue should be included in draft-ietf-ldapbis-authmeth.
>>>>>>>
>>>>>>>      
>>>>>>
>>>>>>If authmeth says anything about DNs and DIGEST-MD5, it should say
>>>>>>that the DIGEST-MD5 username and realm fields are, per the DIGEST-MD5
>>>>>>TS,
>>>>>>    
>>>>>
>>>>>Can you point me to the section where DIGEST-MD5 says that.
>>>>>  
>>>>
>>>>The DIGEST-MD5 TS [RFC2831] defines a username to be the user's
>>>>name (account) in a realm where the realm is a collection of names
>>>>(accounts), both have the form of a simple string
>>>
>>>Kurt, can you please point me to a formal definition of "simple username".
>>
>>RFC 2831 does not use the term "simple username".  It uses the term "username".
>>I believe RFC 2831 is reasonable clear that a username is a simple string used
>>as a user (account) name.  "simple" here meaning that the syntax and semantics
>>of the string are simple.
>>
>>
>>
>>>>and are to be compared as simple strings.
>>>
>>>Fine, I don't disagree with that.
>>
>>>But DNs are used in simple bind. So it is quite logical to allow to use DNs in SASL as well.
>>>(And for implementation of other protocols with a login command that I know this is true.)
>>>
>>>So, if the server allows for DN form of usernames, the client should canonicalize a DN before passing it to the server to avoid interoperability problems. This is pretty much what my previous message suggested. I wasn't suggesting that the server should do that after receiving the username.
>>
>>How does the client determine whether the string entered by the user should or
>>shouldn't be canonized?  Is the client to canonicalize all strings which *look
>>like" DN string representations?  That obviously would break some usernames.
>>
>>
>>>The same is true for a realm. If the server is using DNs as realms, it should canonicalize it before sending to the client. The client must not do any canonicalization.
>>
>>And that would break some realms.
>>
>>Also, saying that the client should canonicalize DN strings would necessitate
>>defining a canonical string representation of a DN.  Note that it is not generally
>>possible to generate a canonical DN string based solely on the input of a DN string
>>
>>
>>>>DIGEST-MD5 defines the syntax of the username and realm using ABNF.
>>>
>>>Which is just a sequence of Unicode characters (no NUL allowed) represented in UTF8, nothing more.
>>
>>RFC 2831 says a username is a sequence of UTF-8 encoded Unicode characters
>>which represent a user name.
>>
>>RFC 2831 does not say a username is a sequence of UTF-8 encoded Unicode
>>characters which represent a DN.
>>
>>
>>>Although the format of authentication ids (usernames) is SASL mechanism specific, DIGEST-MD5 doesn't have any restrictions other than the one mentioned above.
>>
>>It would be, in my opinion, inappropriate for LDAP to place additional syntax
>>and semantics upon the DIGEST-MD5 username and realm.
>>
>>
>>>>There is a common definition, it's a "simple user name", e.g. an
>>>>account name.  A DN doesn't name a user, it names a entry.
>>>
>>>Of course I wasn't talking about an *arbitrary* DN, but only that represents a user or a group of users.
>>
>>My point is a "distinguished names" and a "user names" are different abstractions.
>>The username string represents a user name not a distinguished name.
>>
>>
>>>>>(On a related note, I've seen IMAP servers that have used DNs as usernames).
>>>>
>>>>Did these IMAP servers allow all equivalent string representations
>>>>of the DN which referred to a user to be used as equivalent usernames in
>>>>DIGEST-MD5?
>>>
>>>Frankly I don't know, I don't remember if the server was supporting DIGEST-MD5.
>>
>>Even if was PLAIN or CRAM-MD5, I seriously doubt the IMAP server treated all
>>equivalent DN strings representations (stuffed in a username field) as being
>>equivalent.
>>
>>
>>
>>>>If no, then obviously the IMAP server didn't support
>>>>DNs as usernames.  It supported usernames which **looked like** DN
>>>>strings.
>>>>
>>>
>>>Alexey
>>>
>>>
> 
> 
> 
> 



From owner-ietf-ldapbis@OpenLDAP.org  Mon Aug 18 21:45:33 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11733
	for <ldapbis-archive@lists.ietf.org>; Mon, 18 Aug 2003 21:45:32 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h7J1ctNj073674;
	Tue, 19 Aug 2003 01:43:08 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h7J1Xdw4073621;
	Tue, 19 Aug 2003 01:33:39 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 19 Aug 2003 01:33:39 +0000
Received: from ausyms50.ca.com ([155.35.248.106])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h7J1XXNf073590;
	Tue, 19 Aug 2003 01:33:33 GMT
	(envelope-from Ron.Ramsay@ca.com)
Received: from ausyms21.ca.com ([155.35.201.5]) by ausyms50.ca.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 19 Aug 2003 11:33:12 +1000
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: Comments about draft-ietf-ldapbis-authmeth-05.txt
Date: Tue, 19 Aug 2003 11:33:11 +1000
Message-ID: <1395B4B334FCC143B36AF788E68B63816B8F5B@ausyms21.ca.com>
Thread-Topic: Comments about draft-ietf-ldapbis-authmeth-05.txt
Thread-Index: AcNl3T76K09mgfvhTpmnlllu6n9tzgAE8Jrg
From: "Ramsay, Ron" <Ron.Ramsay@ca.com>
To: "Mark Ennis" <mark.ennis@adacel.com>,
        "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Cc: "Alexey Melnikov" <Alexey.Melnikov@isode.com>,
        "LDAPBis WG" <ietf-ldapbis@OpenLDAP.org>
X-OriginalArrivalTime: 19 Aug 2003 01:33:12.0145 (UTC) FILETIME=[DA5B5C10:01C365F1]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by boole.openldap.org id h7J1XYNf073592
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 8bit

I agree that Kurt seems to be going too far in trying to exclude LDAP DNs.

I note that SASLprep is applied by the client, that LDAP DNs are UTF-8 encoded and that, therefore, there is no problem as long as the server does not attempt to change the DN (username).

I cannot see how the A1 hash can be stored unless the client is also required to somehow canonicalise the DN. SASLprep is not enough.

Using the realm to select a behaviour sounds interesting but may affect current implementations.

Ron

-----Original Message-----
From: Mark Ennis [mailto:mark.ennis@adacel.com]
Sent: Tuesday, 19 August 2003 09:05
To: Kurt D. Zeilenga
Cc: Ramsay, Ron; Alexey Melnikov; LDAPBis WG
Subject: Re: Comments about draft-ietf-ldapbis-authmeth-05.txt


Kurt,

It still seems to me as though you are the one re-engineering LDAP and 
its application of DIGEST-MD5. I have yet to come across anything in the 
LDAP or SASL specifications which preclude the use of distinguished name 
strings in the DIGEST-MD5 username value, except possibly the 
normalisation of the username field being proposed in the SASLprep work. 
After all, we should not forget that an LDAPDN *is* an UTF8 string in 
the protocol, and provided it is not mangled (normalised or SASLprep'd) 
prior to the server receiving it, it can then be interpreted (and 
matched) as a LDAPDN. Normalisation should occur prior to generating the 
digests at both server and client to produce consistent results and 
allow the possibility of storing the A1 hash rather than cleartext 
passwords.

I agree that the LDAP specifications do not preclude the use of 
non-LDAPDN strings in the username field, allowing interaction with 
(possibly shared) back-end authentication services. I see no particular 
problem with using the realm to distinguished how the username field 
should be interpreted.

- Mark.

Kurt D. Zeilenga wrote:
> Ron,
> 
> It still sounds like you are trying to re-engineer LDAP and its
> application of DIGEST-MD5.  DIGEST-MD5 is not designed to support
> DN-based credentials.  As we have two mechanisms which are designed
> to support such, it seems far more appropriate for those who want to
> use DN-based credentials to simple use one of existing mechanism
> than for us to try to hack the LDAP TS to support DN-based credentials
> in DIGEST-MD5.
> 
> At 11:18 PM 8/17/2003, Ramsay, Ron wrote:
> 
>>I agree that we cannot canonicalise DNs (though I disagree that cn=foo and CN=FOO are different usernames). The canonicalisation was proposed to obviate the necessity of storing passwords in the clear.
>>
>>I also think the authmeth has the power to profile Digest-MD5.
> 
> 
> There are many reasons why we cannot do such, most have been previously
> discussed on the list.   However, I note that one of the reasons is that
> it will likely interfer with proxying of DIGEST-MD5 authentication
> requests to a "shared back-end authentication service" and/or
> implementing an LDAP-accessible "shared back-end authentication
> service".
> 
> 
>>If we simply state
> 
> 
> It's not so simple.  
> 
> 
>>1. The DN provided by the client in the bind is to be used (byte-for-byte) to calculate the required hashes, and
>>2. The realm provided by the server is to be used (byte-for-byte) to calculate hashes
> 
> 
> First, I note, that servers are required to use all usernames and realms
> byte-for-byte.  What's new to LDAP is that servers are to treat the
> username/realm as DNs in interactions with the (possibly shared)
> back-end authentication service.  Many of today's servers don't do that and
> those that do don't do it any standard way (as there is no formal
> specification of how to do that).  It is likely that any change in this
> area would cause interoperability problems, some of which likely have
> significant security considerations.
> 
> To standardize such interaction would require engineering work on how to
> deal with the problem that dnMatch(dnString, SASLprep(dnString)) may be
> FALSE for some representations of a DN.  This implies that one either
> needs to restrict users to a subset of DN representations or apply a transform
> such that dnMatch(dnString, SASLprep(transform(dnString))) is TRUE for all
> possible dnStrings.  Both alternatives are problematic.
> 
> 
>>then I think Digest-MD5 can be used in LDAP, but the passwords have to be stored in-the-clear.
> 
> 
> I do not think it appropriate for authmeth to suggest DIGEST-MD5 passwords
> are to be stored in-the-clear when DIGEST-MD5 was specifically designed
> to avoid such.
> 
> 
>>The realm suggestions of Alexey can also be added to the profile. (Is there any reason for requiring that the realm not be ""?)
>>
>>Ron
>>
>>-----Original Message-----
>>From: Kurt D. Zeilenga [mailto:Kurt@OpenLDAP.org]
>>Sent: Monday, 18 August 2003 02:17
>>To: Alexey Melnikov
>>Cc: Ramsay, Ron; LDAPBis WG
>>Subject: Re: Comments about draft-ietf-ldapbis-authmeth-05.txt
>>
>>
>>Below are few additional technical comments...
>>
>>Basically what you are asking is that we state additional requirements that
>>implementations canonicalize
>>       a) all usernames, or
>>       b) all usernames which look like string representations of DNs.
>>
>>Both require the specification of an algorithm to produce a canonical string
>>representation of a DN.  The latter, (b), requires a specification of which input
>>strings are/are not to be canonicalized.
>>
>>First, I note that it is not generally possible to produce a canonical string
>>representation of a DN solely based on input of a non-canonical string
>>representation. Minimally, applicable schema is needed.
>>
>>Second, both a) and b) will introduce additional interoperability problems with
>>significant security implications.  In particular, if an existing system were
>>to have to different users "cn=foo" and "CN=FOO", one of these users
>>would no longer be able to long in as both a) and b) would cause these strings
>>to be treated as representing the same user where today they are clearly two
>>different users.
>>
>>Hence, even if we had a canonicalization algorithm, it would be inappropriate
>>to specify it be used here.  We need to preserve current semantics.
>>
>>Kurt
>>
>>
>>
>>At 08:24 AM 8/16/2003, Alexey Melnikov wrote:
>>
>>>Kurt D. Zeilenga wrote:
>>>
>>>
>>>>At 08:15 AM 8/13/2003, Alexey Melnikov wrote:
>>>>
>>>>
>>>>
>>>>>Kurt D. Zeilenga wrote:
>>>>>  
>>>>>
>>>>>
>>>>>>At 06:14 AM 8/13/2003, Alexey Melnikov wrote:
>>>>>>    
>>>>>>
>>>>>>
>>>>>>>I suggest that some text about the issue should be included in draft-ietf-ldapbis-authmeth.
>>>>>>>
>>>>>>>      
>>>>>>
>>>>>>If authmeth says anything about DNs and DIGEST-MD5, it should say
>>>>>>that the DIGEST-MD5 username and realm fields are, per the DIGEST-MD5
>>>>>>TS,
>>>>>>    
>>>>>
>>>>>Can you point me to the section where DIGEST-MD5 says that.
>>>>>  
>>>>
>>>>The DIGEST-MD5 TS [RFC2831] defines a username to be the user's
>>>>name (account) in a realm where the realm is a collection of names
>>>>(accounts), both have the form of a simple string
>>>
>>>Kurt, can you please point me to a formal definition of "simple username".
>>
>>RFC 2831 does not use the term "simple username".  It uses the term "username".
>>I believe RFC 2831 is reasonable clear that a username is a simple string used
>>as a user (account) name.  "simple" here meaning that the syntax and semantics
>>of the string are simple.
>>
>>
>>
>>>>and are to be compared as simple strings.
>>>
>>>Fine, I don't disagree with that.
>>
>>>But DNs are used in simple bind. So it is quite logical to allow to use DNs in SASL as well.
>>>(And for implementation of other protocols with a login command that I know this is true.)
>>>
>>>So, if the server allows for DN form of usernames, the client should canonicalize a DN before passing it to the server to avoid interoperability problems. This is pretty much what my previous message suggested. I wasn't suggesting that the server should do that after receiving the username.
>>
>>How does the client determine whether the string entered by the user should or
>>shouldn't be canonized?  Is the client to canonicalize all strings which *look
>>like" DN string representations?  That obviously would break some usernames.
>>
>>
>>>The same is true for a realm. If the server is using DNs as realms, it should canonicalize it before sending to the client. The client must not do any canonicalization.
>>
>>And that would break some realms.
>>
>>Also, saying that the client should canonicalize DN strings would necessitate
>>defining a canonical string representation of a DN.  Note that it is not generally
>>possible to generate a canonical DN string based solely on the input of a DN string
>>
>>
>>>>DIGEST-MD5 defines the syntax of the username and realm using ABNF.
>>>
>>>Which is just a sequence of Unicode characters (no NUL allowed) represented in UTF8, nothing more.
>>
>>RFC 2831 says a username is a sequence of UTF-8 encoded Unicode characters
>>which represent a user name.
>>
>>RFC 2831 does not say a username is a sequence of UTF-8 encoded Unicode
>>characters which represent a DN.
>>
>>
>>>Although the format of authentication ids (usernames) is SASL mechanism specific, DIGEST-MD5 doesn't have any restrictions other than the one mentioned above.
>>
>>It would be, in my opinion, inappropriate for LDAP to place additional syntax
>>and semantics upon the DIGEST-MD5 username and realm.
>>
>>
>>>>There is a common definition, it's a "simple user name", e.g. an
>>>>account name.  A DN doesn't name a user, it names a entry.
>>>
>>>Of course I wasn't talking about an *arbitrary* DN, but only that represents a user or a group of users.
>>
>>My point is a "distinguished names" and a "user names" are different abstractions.
>>The username string represents a user name not a distinguished name.
>>
>>
>>>>>(On a related note, I've seen IMAP servers that have used DNs as usernames).
>>>>
>>>>Did these IMAP servers allow all equivalent string representations
>>>>of the DN which referred to a user to be used as equivalent usernames in
>>>>DIGEST-MD5?
>>>
>>>Frankly I don't know, I don't remember if the server was supporting DIGEST-MD5.
>>
>>Even if was PLAIN or CRAM-MD5, I seriously doubt the IMAP server treated all
>>equivalent DN strings representations (stuffed in a username field) as being
>>equivalent.
>>
>>
>>
>>>>If no, then obviously the IMAP server didn't support
>>>>DNs as usernames.  It supported usernames which **looked like** DN
>>>>strings.
>>>>
>>>
>>>Alexey
>>>
>>>
> 
> 
> 
> 





From owner-ietf-ldapbis@OpenLDAP.org  Mon Aug 18 21:56:16 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11939
	for <ldapbis-archive@lists.ietf.org>; Mon, 18 Aug 2003 21:56:15 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h7J1otNj073892;
	Tue, 19 Aug 2003 01:54:44 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h7J1jg0P073790;
	Tue, 19 Aug 2003 01:45:42 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 19 Aug 2003 01:45:42 +0000
Received: from ausyms50.ca.com ([155.35.248.106])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h7J1jaNf073756;
	Tue, 19 Aug 2003 01:45:37 GMT
	(envelope-from Ron.Ramsay@ca.com)
Received: from ausyms21.ca.com ([155.35.201.5]) by ausyms50.ca.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 19 Aug 2003 11:45:16 +1000
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: Comments about draft-ietf-ldapbis-authmeth-05.txt
Date: Tue, 19 Aug 2003 11:45:15 +1000
Message-ID: <1395B4B334FCC143B36AF788E68B63816B8F87@ausyms21.ca.com>
Thread-Topic: Comments about draft-ietf-ldapbis-authmeth-05.txt
Thread-Index: AcNlpxn2RPs87W3cTqityYQyckoM7wASxCug
From: "Ramsay, Ron" <Ron.Ramsay@ca.com>
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Cc: "Alexey Melnikov" <Alexey.Melnikov@isode.com>,
        "LDAPBis WG" <ietf-ldapbis@OpenLDAP.org>
X-OriginalArrivalTime: 19 Aug 2003 01:45:16.0313 (UTC) FILETIME=[89FEA090:01C365F3]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by boole.openldap.org id h7J1jbNf073759
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 8bit

Kurt,

I don't see that backend authentication methods need to treat the username as a DN. An LDAP DN is a UTF-8 string, so surely it is a username?

As SASLprep(DN) is a DN, and as a client is expected to SASLprep its username, then DN = SASLprep(DN) and so they match.

What are the implementations that may be used in place of Digest-MD5? Are you being ingenuous?

If you are keen to support backend authentication methods, why don't you write down the requirements? Surely such a profile could also be added to authmeth.

Are these vendors of backend authentication methods able to speak for themselves?

Ron

-----Original Message-----
From: Kurt D. Zeilenga [mailto:Kurt@OpenLDAP.org]
Sent: Tuesday, 19 August 2003 02:39
To: Ramsay, Ron
Cc: Alexey Melnikov; LDAPBis WG
Subject: RE: Comments about draft-ietf-ldapbis-authmeth-05.txt


Ron,

It still sounds like you are trying to re-engineer LDAP and its
application of DIGEST-MD5.  DIGEST-MD5 is not designed to support
DN-based credentials.  As we have two mechanisms which are designed
to support such, it seems far more appropriate for those who want to
use DN-based credentials to simple use one of existing mechanism
than for us to try to hack the LDAP TS to support DN-based credentials
in DIGEST-MD5.

At 11:18 PM 8/17/2003, Ramsay, Ron wrote:
>I agree that we cannot canonicalise DNs (though I disagree that cn=foo and CN=FOO are different usernames). The canonicalisation was proposed to obviate the necessity of storing passwords in the clear.
>
>I also think the authmeth has the power to profile Digest-MD5.

There are many reasons why we cannot do such, most have been previously
discussed on the list.   However, I note that one of the reasons is that
it will likely interfer with proxying of DIGEST-MD5 authentication
requests to a "shared back-end authentication service" and/or
implementing an LDAP-accessible "shared back-end authentication
service".

>If we simply state

It's not so simple.  

>1. The DN provided by the client in the bind is to be used (byte-for-byte) to calculate the required hashes, and
>2. The realm provided by the server is to be used (byte-for-byte) to calculate hashes

First, I note, that servers are required to use all usernames and realms
byte-for-byte.  What's new to LDAP is that servers are to treat the
username/realm as DNs in interactions with the (possibly shared)
back-end authentication service.  Many of today's servers don't do that and
those that do don't do it any standard way (as there is no formal
specification of how to do that).  It is likely that any change in this
area would cause interoperability problems, some of which likely have
significant security considerations.

To standardize such interaction would require engineering work on how to
deal with the problem that dnMatch(dnString, SASLprep(dnString)) may be
FALSE for some representations of a DN.  This implies that one either
needs to restrict users to a subset of DN representations or apply a transform
such that dnMatch(dnString, SASLprep(transform(dnString))) is TRUE for all
possible dnStrings.  Both alternatives are problematic.

>then I think Digest-MD5 can be used in LDAP, but the passwords have to be stored in-the-clear.

I do not think it appropriate for authmeth to suggest DIGEST-MD5 passwords
are to be stored in-the-clear when DIGEST-MD5 was specifically designed
to avoid such.

>The realm suggestions of Alexey can also be added to the profile. (Is there any reason for requiring that the realm not be ""?)
>
>Ron
>
>-----Original Message-----
>From: Kurt D. Zeilenga [mailto:Kurt@OpenLDAP.org]
>Sent: Monday, 18 August 2003 02:17
>To: Alexey Melnikov
>Cc: Ramsay, Ron; LDAPBis WG
>Subject: Re: Comments about draft-ietf-ldapbis-authmeth-05.txt
>
>
>Below are few additional technical comments...
>
>Basically what you are asking is that we state additional requirements that
>implementations canonicalize
>        a) all usernames, or
>        b) all usernames which look like string representations of DNs.
>
>Both require the specification of an algorithm to produce a canonical string
>representation of a DN.  The latter, (b), requires a specification of which input
>strings are/are not to be canonicalized.
>
>First, I note that it is not generally possible to produce a canonical string
>representation of a DN solely based on input of a non-canonical string
>representation. Minimally, applicable schema is needed.
>
>Second, both a) and b) will introduce additional interoperability problems with
>significant security implications.  In particular, if an existing system were
>to have to different users "cn=foo" and "CN=FOO", one of these users
>would no longer be able to long in as both a) and b) would cause these strings
>to be treated as representing the same user where today they are clearly two
>different users.
>
>Hence, even if we had a canonicalization algorithm, it would be inappropriate
>to specify it be used here.  We need to preserve current semantics.
>
>Kurt
>
>
>
>At 08:24 AM 8/16/2003, Alexey Melnikov wrote:
>>Kurt D. Zeilenga wrote:
>>
>>>At 08:15 AM 8/13/2003, Alexey Melnikov wrote:
>>> 
>>>
>>>>Kurt D. Zeilenga wrote:
>>>>   
>>>>
>>>>>At 06:14 AM 8/13/2003, Alexey Melnikov wrote:
>>>>>     
>>>>>
>>>>>>I suggest that some text about the issue should be included in draft-ietf-ldapbis-authmeth.
>>>>>> 
>>>>>>       
>>>>>If authmeth says anything about DNs and DIGEST-MD5, it should say
>>>>>that the DIGEST-MD5 username and realm fields are, per the DIGEST-MD5
>>>>>TS,
>>>>>     
>>>>Can you point me to the section where DIGEST-MD5 says that.
>>>>   
>>>
>>>The DIGEST-MD5 TS [RFC2831] defines a username to be the user's
>>>name (account) in a realm where the realm is a collection of names
>>>(accounts), both have the form of a simple string
>>Kurt, can you please point me to a formal definition of "simple username".
>
>RFC 2831 does not use the term "simple username".  It uses the term "username".
>I believe RFC 2831 is reasonable clear that a username is a simple string used
>as a user (account) name.  "simple" here meaning that the syntax and semantics
>of the string are simple.
>
>
>>>and are to be compared as simple strings.
>>Fine, I don't disagree with that.
>
>>But DNs are used in simple bind. So it is quite logical to allow to use DNs in SASL as well.
>>(And for implementation of other protocols with a login command that I know this is true.)
>>
>>So, if the server allows for DN form of usernames, the client should canonicalize a DN before passing it to the server to avoid interoperability problems. This is pretty much what my previous message suggested. I wasn't suggesting that the server should do that after receiving the username.
>
>How does the client determine whether the string entered by the user should or
>shouldn't be canonized?  Is the client to canonicalize all strings which *look
>like" DN string representations?  That obviously would break some usernames.
>
>>The same is true for a realm. If the server is using DNs as realms, it should canonicalize it before sending to the client. The client must not do any canonicalization.
>
>And that would break some realms.
>
>Also, saying that the client should canonicalize DN strings would necessitate
>defining a canonical string representation of a DN.  Note that it is not generally
>possible to generate a canonical DN string based solely on the input of a DN string
>
>>>DIGEST-MD5 defines the syntax of the username and realm using ABNF.
>>Which is just a sequence of Unicode characters (no NUL allowed) represented in UTF8, nothing more.
>
>RFC 2831 says a username is a sequence of UTF-8 encoded Unicode characters
>which represent a user name.
>
>RFC 2831 does not say a username is a sequence of UTF-8 encoded Unicode
>characters which represent a DN.
>
>>Although the format of authentication ids (usernames) is SASL mechanism specific, DIGEST-MD5 doesn't have any restrictions other than the one mentioned above.
>
>It would be, in my opinion, inappropriate for LDAP to place additional syntax
>and semantics upon the DIGEST-MD5 username and realm.
>
>>>There is a common definition, it's a "simple user name", e.g. an
>>>account name.  A DN doesn't name a user, it names a entry.
>>Of course I wasn't talking about an *arbitrary* DN, but only that represents a user or a group of users.
>
>My point is a "distinguished names" and a "user names" are different abstractions.
>The username string represents a user name not a distinguished name.
>
>>>>(On a related note, I've seen IMAP servers that have used DNs as usernames).
>>>
>>>Did these IMAP servers allow all equivalent string representations
>>>of the DN which referred to a user to be used as equivalent usernames in
>>>DIGEST-MD5?
>>Frankly I don't know, I don't remember if the server was supporting DIGEST-MD5.
>
>Even if was PLAIN or CRAM-MD5, I seriously doubt the IMAP server treated all
>equivalent DN strings representations (stuffed in a username field) as being
>equivalent.
>
>
>>> If no, then obviously the IMAP server didn't support
>>>DNs as usernames.  It supported usernames which **looked like** DN
>>>strings.
>>> 
>>Alexey
>>
>>





From owner-ietf-ldapbis@OpenLDAP.org  Mon Aug 18 22:07:52 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA12233
	for <ldapbis-archive@lists.ietf.org>; Mon, 18 Aug 2003 22:07:51 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h7J22tNj074148;
	Tue, 19 Aug 2003 02:06:48 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h7J1xmAX074075;
	Tue, 19 Aug 2003 01:59:48 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 19 Aug 2003 01:59:48 +0000
Received: from adacel.com (gunsmoke.adacel.com.au [210.11.130.7])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h7J1xhNf074048
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 19 Aug 2003 01:59:43 GMT
	(envelope-from mark.ennis@adacel.com)
Received: from nexus.adacel.com (Not Verified[10.32.240.1]) by adacel.com with NetIQ MailMarshal (v5.5.3.16)
	id <B000134453>; Tue, 19 Aug 2003 11:55:11 +1000
Received: (qmail 30560 invoked from network); 19 Aug 2003 01:52:53 -0000
Received: from unknown (HELO adacel.com) (10.32.24.164)
  by nexus.adacel.com with SMTP; 19 Aug 2003 01:52:53 -0000
Message-ID: <3F418475.4020403@adacel.com>
Date: Tue, 19 Aug 2003 11:59:17 +1000
From: Mark Ennis <mark.ennis@adacel.com>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3.1) Gecko/20030425
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Ramsay, Ron" <Ron.Ramsay@ca.com>
CC: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>,
        Alexey Melnikov <Alexey.Melnikov@isode.com>,
        LDAPBis WG <ietf-ldapbis@OpenLDAP.org>
Subject: Re: Comments about draft-ietf-ldapbis-authmeth-05.txt
References: <1395B4B334FCC143B36AF788E68B63816B8F5B@ausyms21.ca.com>
In-Reply-To: <1395B4B334FCC143B36AF788E68B63816B8F5B@ausyms21.ca.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Ron,

You're right about storing the A1 hash being a problem without requiring 
some canonical form for the LDAPDN, which is a non-trivial issue.

My understanding of the realm is that it exists to identify different 
authentication services available to the server. The LDAP directory, 
using LDAPDN in the username, could be viewed as one of these 
authentication services. Where the realm is used for other purposes by a 
server, the use of it I proposed would potentially cause problems.

- Mark.

Ramsay, Ron wrote:
> I agree that Kurt seems to be going too far in trying to exclude LDAP DNs.
> 
> I note that SASLprep is applied by the client, that LDAP DNs are UTF-8 encoded and that, therefore, there is no problem as long as the server does not attempt to change the DN (username).
> 
> I cannot see how the A1 hash can be stored unless the client is also required to somehow canonicalise the DN. SASLprep is not enough.
> 
> Using the realm to select a behaviour sounds interesting but may affect current implementations.
> 
> Ron
> 
> -----Original Message-----
> From: Mark Ennis [mailto:mark.ennis@adacel.com]
> Sent: Tuesday, 19 August 2003 09:05
> To: Kurt D. Zeilenga
> Cc: Ramsay, Ron; Alexey Melnikov; LDAPBis WG
> Subject: Re: Comments about draft-ietf-ldapbis-authmeth-05.txt
> 
> 
> Kurt,
> 
> It still seems to me as though you are the one re-engineering LDAP and 
> its application of DIGEST-MD5. I have yet to come across anything in the 
> LDAP or SASL specifications which preclude the use of distinguished name 
> strings in the DIGEST-MD5 username value, except possibly the 
> normalisation of the username field being proposed in the SASLprep work. 
> After all, we should not forget that an LDAPDN *is* an UTF8 string in 
> the protocol, and provided it is not mangled (normalised or SASLprep'd) 
> prior to the server receiving it, it can then be interpreted (and 
> matched) as a LDAPDN. Normalisation should occur prior to generating the 
> digests at both server and client to produce consistent results and 
> allow the possibility of storing the A1 hash rather than cleartext 
> passwords.
> 
> I agree that the LDAP specifications do not preclude the use of 
> non-LDAPDN strings in the username field, allowing interaction with 
> (possibly shared) back-end authentication services. I see no particular 
> problem with using the realm to distinguished how the username field 
> should be interpreted.
> 
> - Mark.
> 
> Kurt D. Zeilenga wrote:
> 
>>Ron,
>>
>>It still sounds like you are trying to re-engineer LDAP and its
>>application of DIGEST-MD5.  DIGEST-MD5 is not designed to support
>>DN-based credentials.  As we have two mechanisms which are designed
>>to support such, it seems far more appropriate for those who want to
>>use DN-based credentials to simple use one of existing mechanism
>>than for us to try to hack the LDAP TS to support DN-based credentials
>>in DIGEST-MD5.
>>
>>At 11:18 PM 8/17/2003, Ramsay, Ron wrote:
>>
>>
>>>I agree that we cannot canonicalise DNs (though I disagree that cn=foo and CN=FOO are different usernames). The canonicalisation was proposed to obviate the necessity of storing passwords in the clear.
>>>
>>>I also think the authmeth has the power to profile Digest-MD5.
>>
>>
>>There are many reasons why we cannot do such, most have been previously
>>discussed on the list.   However, I note that one of the reasons is that
>>it will likely interfer with proxying of DIGEST-MD5 authentication
>>requests to a "shared back-end authentication service" and/or
>>implementing an LDAP-accessible "shared back-end authentication
>>service".
>>
>>
>>
>>>If we simply state
>>
>>
>>It's not so simple.  
>>
>>
>>
>>>1. The DN provided by the client in the bind is to be used (byte-for-byte) to calculate the required hashes, and
>>>2. The realm provided by the server is to be used (byte-for-byte) to calculate hashes
>>
>>
>>First, I note, that servers are required to use all usernames and realms
>>byte-for-byte.  What's new to LDAP is that servers are to treat the
>>username/realm as DNs in interactions with the (possibly shared)
>>back-end authentication service.  Many of today's servers don't do that and
>>those that do don't do it any standard way (as there is no formal
>>specification of how to do that).  It is likely that any change in this
>>area would cause interoperability problems, some of which likely have
>>significant security considerations.
>>
>>To standardize such interaction would require engineering work on how to
>>deal with the problem that dnMatch(dnString, SASLprep(dnString)) may be
>>FALSE for some representations of a DN.  This implies that one either
>>needs to restrict users to a subset of DN representations or apply a transform
>>such that dnMatch(dnString, SASLprep(transform(dnString))) is TRUE for all
>>possible dnStrings.  Both alternatives are problematic.
>>
>>
>>
>>>then I think Digest-MD5 can be used in LDAP, but the passwords have to be stored in-the-clear.
>>
>>
>>I do not think it appropriate for authmeth to suggest DIGEST-MD5 passwords
>>are to be stored in-the-clear when DIGEST-MD5 was specifically designed
>>to avoid such.
>>
>>
>>
>>>The realm suggestions of Alexey can also be added to the profile. (Is there any reason for requiring that the realm not be ""?)
>>>
>>>Ron
>>>
>>>-----Original Message-----
>>>From: Kurt D. Zeilenga [mailto:Kurt@OpenLDAP.org]
>>>Sent: Monday, 18 August 2003 02:17
>>>To: Alexey Melnikov
>>>Cc: Ramsay, Ron; LDAPBis WG
>>>Subject: Re: Comments about draft-ietf-ldapbis-authmeth-05.txt
>>>
>>>
>>>Below are few additional technical comments...
>>>
>>>Basically what you are asking is that we state additional requirements that
>>>implementations canonicalize
>>>      a) all usernames, or
>>>      b) all usernames which look like string representations of DNs.
>>>
>>>Both require the specification of an algorithm to produce a canonical string
>>>representation of a DN.  The latter, (b), requires a specification of which input
>>>strings are/are not to be canonicalized.
>>>
>>>First, I note that it is not generally possible to produce a canonical string
>>>representation of a DN solely based on input of a non-canonical string
>>>representation. Minimally, applicable schema is needed.
>>>
>>>Second, both a) and b) will introduce additional interoperability problems with
>>>significant security implications.  In particular, if an existing system were
>>>to have to different users "cn=foo" and "CN=FOO", one of these users
>>>would no longer be able to long in as both a) and b) would cause these strings
>>>to be treated as representing the same user where today they are clearly two
>>>different users.
>>>
>>>Hence, even if we had a canonicalization algorithm, it would be inappropriate
>>>to specify it be used here.  We need to preserve current semantics.
>>>
>>>Kurt
>>>
>>>
>>>
>>>At 08:24 AM 8/16/2003, Alexey Melnikov wrote:
>>>
>>>
>>>>Kurt D. Zeilenga wrote:
>>>>
>>>>
>>>>
>>>>>At 08:15 AM 8/13/2003, Alexey Melnikov wrote:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>Kurt D. Zeilenga wrote:
>>>>>> 
>>>>>>
>>>>>>
>>>>>>
>>>>>>>At 06:14 AM 8/13/2003, Alexey Melnikov wrote:
>>>>>>>   
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>I suggest that some text about the issue should be included in draft-ietf-ldapbis-authmeth.
>>>>>>>>
>>>>>>>>     
>>>>>>>
>>>>>>>If authmeth says anything about DNs and DIGEST-MD5, it should say
>>>>>>>that the DIGEST-MD5 username and realm fields are, per the DIGEST-MD5
>>>>>>>TS,
>>>>>>>   
>>>>>>
>>>>>>Can you point me to the section where DIGEST-MD5 says that.
>>>>>> 
>>>>>
>>>>>The DIGEST-MD5 TS [RFC2831] defines a username to be the user's
>>>>>name (account) in a realm where the realm is a collection of names
>>>>>(accounts), both have the form of a simple string
>>>>
>>>>Kurt, can you please point me to a formal definition of "simple username".
>>>
>>>RFC 2831 does not use the term "simple username".  It uses the term "username".
>>>I believe RFC 2831 is reasonable clear that a username is a simple string used
>>>as a user (account) name.  "simple" here meaning that the syntax and semantics
>>>of the string are simple.
>>>
>>>
>>>
>>>
>>>>>and are to be compared as simple strings.
>>>>
>>>>Fine, I don't disagree with that.
>>>
>>>>But DNs are used in simple bind. So it is quite logical to allow to use DNs in SASL as well.
>>>>(And for implementation of other protocols with a login command that I know this is true.)
>>>>
>>>>So, if the server allows for DN form of usernames, the client should canonicalize a DN before passing it to the server to avoid interoperability problems. This is pretty much what my previous message suggested. I wasn't suggesting that the server should do that after receiving the username.
>>>
>>>How does the client determine whether the string entered by the user should or
>>>shouldn't be canonized?  Is the client to canonicalize all strings which *look
>>>like" DN string representations?  That obviously would break some usernames.
>>>
>>>
>>>
>>>>The same is true for a realm. If the server is using DNs as realms, it should canonicalize it before sending to the client. The client must not do any canonicalization.
>>>
>>>And that would break some realms.
>>>
>>>Also, saying that the client should canonicalize DN strings would necessitate
>>>defining a canonical string representation of a DN.  Note that it is not generally
>>>possible to generate a canonical DN string based solely on the input of a DN string
>>>
>>>
>>>
>>>>>DIGEST-MD5 defines the syntax of the username and realm using ABNF.
>>>>
>>>>Which is just a sequence of Unicode characters (no NUL allowed) represented in UTF8, nothing more.
>>>
>>>RFC 2831 says a username is a sequence of UTF-8 encoded Unicode characters
>>>which represent a user name.
>>>
>>>RFC 2831 does not say a username is a sequence of UTF-8 encoded Unicode
>>>characters which represent a DN.
>>>
>>>
>>>
>>>>Although the format of authentication ids (usernames) is SASL mechanism specific, DIGEST-MD5 doesn't have any restrictions other than the one mentioned above.
>>>
>>>It would be, in my opinion, inappropriate for LDAP to place additional syntax
>>>and semantics upon the DIGEST-MD5 username and realm.
>>>
>>>
>>>
>>>>>There is a common definition, it's a "simple user name", e.g. an
>>>>>account name.  A DN doesn't name a user, it names a entry.
>>>>
>>>>Of course I wasn't talking about an *arbitrary* DN, but only that represents a user or a group of users.
>>>
>>>My point is a "distinguished names" and a "user names" are different abstractions.
>>>The username string represents a user name not a distinguished name.
>>>
>>>
>>>
>>>>>>(On a related note, I've seen IMAP servers that have used DNs as usernames).
>>>>>
>>>>>Did these IMAP servers allow all equivalent string representations
>>>>>of the DN which referred to a user to be used as equivalent usernames in
>>>>>DIGEST-MD5?
>>>>
>>>>Frankly I don't know, I don't remember if the server was supporting DIGEST-MD5.
>>>
>>>Even if was PLAIN or CRAM-MD5, I seriously doubt the IMAP server treated all
>>>equivalent DN strings representations (stuffed in a username field) as being
>>>equivalent.
>>>
>>>
>>>
>>>
>>>>>If no, then obviously the IMAP server didn't support
>>>>>DNs as usernames.  It supported usernames which **looked like** DN
>>>>>strings.
>>>>>
>>>>
>>>>Alexey
>>>>
>>>>
>>
>>
>>
>>
> 
> 
> 
> 



From owner-ietf-ldapbis@OpenLDAP.org  Mon Aug 18 22:31:25 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA12656
	for <ldapbis-archive@lists.ietf.org>; Mon, 18 Aug 2003 22:31:25 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h7J2KtNj074442;
	Tue, 19 Aug 2003 02:26:11 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h7J2ISJf074420;
	Tue, 19 Aug 2003 02:18:28 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 19 Aug 2003 02:18:28 +0000
Received: from ausyms50.ca.com ([155.35.248.106])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h7J2IMNf074379;
	Tue, 19 Aug 2003 02:18:22 GMT
	(envelope-from Ron.Ramsay@ca.com)
Received: from ausyms21.ca.com ([155.35.201.5]) by ausyms50.ca.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 19 Aug 2003 12:18:01 +1000
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: Comments about draft-ietf-ldapbis-authmeth-05.txt
Date: Tue, 19 Aug 2003 12:18:01 +1000
Message-ID: <1395B4B334FCC143B36AF788E68B63816B8FE8@ausyms21.ca.com>
Thread-Topic: Comments about draft-ietf-ldapbis-authmeth-05.txt
Thread-Index: AcNl9YuYtLiOCsgeR/K+rp85MJIU5QAARezg
From: "Ramsay, Ron" <Ron.Ramsay@ca.com>
To: "Mark Ennis" <mark.ennis@adacel.com>
Cc: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>,
        "Alexey Melnikov" <Alexey.Melnikov@isode.com>,
        "LDAPBis WG" <ietf-ldapbis@OpenLDAP.org>
X-OriginalArrivalTime: 19 Aug 2003 02:18:01.0894 (UTC) FILETIME=[1D927C60:01C365F8]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by boole.openldap.org id h7J2INNf074389
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 8bit

Let me propose a way forward.

The common namimg attributes used in DNs (c, l, o, ou, cn, dc) all have caseExactMatch as their matching rule. Therefore, DNs using these attributes can all be expressed in lowercase with extra spaces removed. So let's say that a realm of "canon@ldap" means that all DNs have been mapped to this form. For this realm, the A1 hash may be precomputed by the server. A client using this realm must use the mapped form of the DN to compute hashes.

If the realm is, say, "other@ldap", the A1 hash cannot be precomputed so the server must use the DN as presented by the client to form the hash. The hash cannot be precomputed.

For any other realm, the username may not be a DN or may not be restricted as above. How it is processed is a local matter.

Ron

-----Original Message-----
From: Mark Ennis [mailto:mark.ennis@adacel.com]
Sent: Tuesday, 19 August 2003 11:59
To: Ramsay, Ron
Cc: Kurt D. Zeilenga; Alexey Melnikov; LDAPBis WG
Subject: Re: Comments about draft-ietf-ldapbis-authmeth-05.txt


Ron,

You're right about storing the A1 hash being a problem without requiring 
some canonical form for the LDAPDN, which is a non-trivial issue.

My understanding of the realm is that it exists to identify different 
authentication services available to the server. The LDAP directory, 
using LDAPDN in the username, could be viewed as one of these 
authentication services. Where the realm is used for other purposes by a 
server, the use of it I proposed would potentially cause problems.

- Mark.

Ramsay, Ron wrote:
> I agree that Kurt seems to be going too far in trying to exclude LDAP DNs.
> 
> I note that SASLprep is applied by the client, that LDAP DNs are UTF-8 encoded and that, therefore, there is no problem as long as the server does not attempt to change the DN (username).
> 
> I cannot see how the A1 hash can be stored unless the client is also required to somehow canonicalise the DN. SASLprep is not enough.
> 
> Using the realm to select a behaviour sounds interesting but may affect current implementations.
> 
> Ron
> 
> -----Original Message-----
> From: Mark Ennis [mailto:mark.ennis@adacel.com]
> Sent: Tuesday, 19 August 2003 09:05
> To: Kurt D. Zeilenga
> Cc: Ramsay, Ron; Alexey Melnikov; LDAPBis WG
> Subject: Re: Comments about draft-ietf-ldapbis-authmeth-05.txt
> 
> 
> Kurt,
> 
> It still seems to me as though you are the one re-engineering LDAP and 
> its application of DIGEST-MD5. I have yet to come across anything in the 
> LDAP or SASL specifications which preclude the use of distinguished name 
> strings in the DIGEST-MD5 username value, except possibly the 
> normalisation of the username field being proposed in the SASLprep work. 
> After all, we should not forget that an LDAPDN *is* an UTF8 string in 
> the protocol, and provided it is not mangled (normalised or SASLprep'd) 
> prior to the server receiving it, it can then be interpreted (and 
> matched) as a LDAPDN. Normalisation should occur prior to generating the 
> digests at both server and client to produce consistent results and 
> allow the possibility of storing the A1 hash rather than cleartext 
> passwords.
> 
> I agree that the LDAP specifications do not preclude the use of 
> non-LDAPDN strings in the username field, allowing interaction with 
> (possibly shared) back-end authentication services. I see no particular 
> problem with using the realm to distinguished how the username field 
> should be interpreted.
> 
> - Mark.
> 
> Kurt D. Zeilenga wrote:
> 
>>Ron,
>>
>>It still sounds like you are trying to re-engineer LDAP and its
>>application of DIGEST-MD5.  DIGEST-MD5 is not designed to support
>>DN-based credentials.  As we have two mechanisms which are designed
>>to support such, it seems far more appropriate for those who want to
>>use DN-based credentials to simple use one of existing mechanism
>>than for us to try to hack the LDAP TS to support DN-based credentials
>>in DIGEST-MD5.
>>
>>At 11:18 PM 8/17/2003, Ramsay, Ron wrote:
>>
>>
>>>I agree that we cannot canonicalise DNs (though I disagree that cn=foo and CN=FOO are different usernames). The canonicalisation was proposed to obviate the necessity of storing passwords in the clear.
>>>
>>>I also think the authmeth has the power to profile Digest-MD5.
>>
>>
>>There are many reasons why we cannot do such, most have been previously
>>discussed on the list.   However, I note that one of the reasons is that
>>it will likely interfer with proxying of DIGEST-MD5 authentication
>>requests to a "shared back-end authentication service" and/or
>>implementing an LDAP-accessible "shared back-end authentication
>>service".
>>
>>
>>
>>>If we simply state
>>
>>
>>It's not so simple.  
>>
>>
>>
>>>1. The DN provided by the client in the bind is to be used (byte-for-byte) to calculate the required hashes, and
>>>2. The realm provided by the server is to be used (byte-for-byte) to calculate hashes
>>
>>
>>First, I note, that servers are required to use all usernames and realms
>>byte-for-byte.  What's new to LDAP is that servers are to treat the
>>username/realm as DNs in interactions with the (possibly shared)
>>back-end authentication service.  Many of today's servers don't do that and
>>those that do don't do it any standard way (as there is no formal
>>specification of how to do that).  It is likely that any change in this
>>area would cause interoperability problems, some of which likely have
>>significant security considerations.
>>
>>To standardize such interaction would require engineering work on how to
>>deal with the problem that dnMatch(dnString, SASLprep(dnString)) may be
>>FALSE for some representations of a DN.  This implies that one either
>>needs to restrict users to a subset of DN representations or apply a transform
>>such that dnMatch(dnString, SASLprep(transform(dnString))) is TRUE for all
>>possible dnStrings.  Both alternatives are problematic.
>>
>>
>>
>>>then I think Digest-MD5 can be used in LDAP, but the passwords have to be stored in-the-clear.
>>
>>
>>I do not think it appropriate for authmeth to suggest DIGEST-MD5 passwords
>>are to be stored in-the-clear when DIGEST-MD5 was specifically designed
>>to avoid such.
>>
>>
>>
>>>The realm suggestions of Alexey can also be added to the profile. (Is there any reason for requiring that the realm not be ""?)
>>>
>>>Ron
>>>
>>>-----Original Message-----
>>>From: Kurt D. Zeilenga [mailto:Kurt@OpenLDAP.org]
>>>Sent: Monday, 18 August 2003 02:17
>>>To: Alexey Melnikov
>>>Cc: Ramsay, Ron; LDAPBis WG
>>>Subject: Re: Comments about draft-ietf-ldapbis-authmeth-05.txt
>>>
>>>
>>>Below are few additional technical comments...
>>>
>>>Basically what you are asking is that we state additional requirements that
>>>implementations canonicalize
>>>      a) all usernames, or
>>>      b) all usernames which look like string representations of DNs.
>>>
>>>Both require the specification of an algorithm to produce a canonical string
>>>representation of a DN.  The latter, (b), requires a specification of which input
>>>strings are/are not to be canonicalized.
>>>
>>>First, I note that it is not generally possible to produce a canonical string
>>>representation of a DN solely based on input of a non-canonical string
>>>representation. Minimally, applicable schema is needed.
>>>
>>>Second, both a) and b) will introduce additional interoperability problems with
>>>significant security implications.  In particular, if an existing system were
>>>to have to different users "cn=foo" and "CN=FOO", one of these users
>>>would no longer be able to long in as both a) and b) would cause these strings
>>>to be treated as representing the same user where today they are clearly two
>>>different users.
>>>
>>>Hence, even if we had a canonicalization algorithm, it would be inappropriate
>>>to specify it be used here.  We need to preserve current semantics.
>>>
>>>Kurt
>>>
>>>
>>>
>>>At 08:24 AM 8/16/2003, Alexey Melnikov wrote:
>>>
>>>
>>>>Kurt D. Zeilenga wrote:
>>>>
>>>>
>>>>
>>>>>At 08:15 AM 8/13/2003, Alexey Melnikov wrote:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>Kurt D. Zeilenga wrote:
>>>>>> 
>>>>>>
>>>>>>
>>>>>>
>>>>>>>At 06:14 AM 8/13/2003, Alexey Melnikov wrote:
>>>>>>>   
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>I suggest that some text about the issue should be included in draft-ietf-ldapbis-authmeth.
>>>>>>>>
>>>>>>>>     
>>>>>>>
>>>>>>>If authmeth says anything about DNs and DIGEST-MD5, it should say
>>>>>>>that the DIGEST-MD5 username and realm fields are, per the DIGEST-MD5
>>>>>>>TS,
>>>>>>>   
>>>>>>
>>>>>>Can you point me to the section where DIGEST-MD5 says that.
>>>>>> 
>>>>>
>>>>>The DIGEST-MD5 TS [RFC2831] defines a username to be the user's
>>>>>name (account) in a realm where the realm is a collection of names
>>>>>(accounts), both have the form of a simple string
>>>>
>>>>Kurt, can you please point me to a formal definition of "simple username".
>>>
>>>RFC 2831 does not use the term "simple username".  It uses the term "username".
>>>I believe RFC 2831 is reasonable clear that a username is a simple string used
>>>as a user (account) name.  "simple" here meaning that the syntax and semantics
>>>of the string are simple.
>>>
>>>
>>>
>>>
>>>>>and are to be compared as simple strings.
>>>>
>>>>Fine, I don't disagree with that.
>>>
>>>>But DNs are used in simple bind. So it is quite logical to allow to use DNs in SASL as well.
>>>>(And for implementation of other protocols with a login command that I know this is true.)
>>>>
>>>>So, if the server allows for DN form of usernames, the client should canonicalize a DN before passing it to the server to avoid interoperability problems. This is pretty much what my previous message suggested. I wasn't suggesting that the server should do that after receiving the username.
>>>
>>>How does the client determine whether the string entered by the user should or
>>>shouldn't be canonized?  Is the client to canonicalize all strings which *look
>>>like" DN string representations?  That obviously would break some usernames.
>>>
>>>
>>>
>>>>The same is true for a realm. If the server is using DNs as realms, it should canonicalize it before sending to the client. The client must not do any canonicalization.
>>>
>>>And that would break some realms.
>>>
>>>Also, saying that the client should canonicalize DN strings would necessitate
>>>defining a canonical string representation of a DN.  Note that it is not generally
>>>possible to generate a canonical DN string based solely on the input of a DN string
>>>
>>>
>>>
>>>>>DIGEST-MD5 defines the syntax of the username and realm using ABNF.
>>>>
>>>>Which is just a sequence of Unicode characters (no NUL allowed) represented in UTF8, nothing more.
>>>
>>>RFC 2831 says a username is a sequence of UTF-8 encoded Unicode characters
>>>which represent a user name.
>>>
>>>RFC 2831 does not say a username is a sequence of UTF-8 encoded Unicode
>>>characters which represent a DN.
>>>
>>>
>>>
>>>>Although the format of authentication ids (usernames) is SASL mechanism specific, DIGEST-MD5 doesn't have any restrictions other than the one mentioned above.
>>>
>>>It would be, in my opinion, inappropriate for LDAP to place additional syntax
>>>and semantics upon the DIGEST-MD5 username and realm.
>>>
>>>
>>>
>>>>>There is a common definition, it's a "simple user name", e.g. an
>>>>>account name.  A DN doesn't name a user, it names a entry.
>>>>
>>>>Of course I wasn't talking about an *arbitrary* DN, but only that represents a user or a group of users.
>>>
>>>My point is a "distinguished names" and a "user names" are different abstractions.
>>>The username string represents a user name not a distinguished name.
>>>
>>>
>>>
>>>>>>(On a related note, I've seen IMAP servers that have used DNs as usernames).
>>>>>
>>>>>Did these IMAP servers allow all equivalent string representations
>>>>>of the DN which referred to a user to be used as equivalent usernames in
>>>>>DIGEST-MD5?
>>>>
>>>>Frankly I don't know, I don't remember if the server was supporting DIGEST-MD5.
>>>
>>>Even if was PLAIN or CRAM-MD5, I seriously doubt the IMAP server treated all
>>>equivalent DN strings representations (stuffed in a username field) as being
>>>equivalent.
>>>
>>>
>>>
>>>
>>>>>If no, then obviously the IMAP server didn't support
>>>>>DNs as usernames.  It supported usernames which **looked like** DN
>>>>>strings.
>>>>>
>>>>
>>>>Alexey
>>>>
>>>>
>>
>>
>>
>>
> 
> 
> 
> 





From owner-ietf-ldapbis@OpenLDAP.org  Mon Aug 18 23:38:03 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA13550
	for <ldapbis-archive@lists.ietf.org>; Mon, 18 Aug 2003 23:38:02 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h7J3X7Nf076554;
	Tue, 19 Aug 2003 03:33:07 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h7J3N9Vl076444;
	Tue, 19 Aug 2003 03:23:09 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 19 Aug 2003 03:23:09 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h7J3N5Nf076434
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 19 Aug 2003 03:23:05 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from nomad.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.9/8.12.8) with ESMTP id h7J3MVwE003142;
	Tue, 19 Aug 2003 03:22:31 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030818200914.01c3fb78@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Mon, 18 Aug 2003 20:23:48 -0700
To: "Ramsay, Ron" <Ron.Ramsay@ca.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: RE: Comments about draft-ietf-ldapbis-authmeth-05.txt
Cc: "Mark Ennis" <mark.ennis@adacel.com>,
        "Alexey Melnikov" <Alexey.Melnikov@isode.com>,
        "LDAPBis WG" <ietf-ldapbis@OpenLDAP.org>
In-Reply-To: <1395B4B334FCC143B36AF788E68B63816B8FE8@ausyms21.ca.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

At 07:18 PM 8/18/2003, Ramsay, Ron wrote:
>Let me propose a way forward.

I suggest you write an individual I-D detailing your
technical proposal.

Kurt,  LDAPBIS co-chair

>The common namimg attributes used in DNs (c, l, o, ou, cn, dc) all have caseExactMatch as their matching rule. Therefore, DNs using these attributes can all be expressed in lowercase with extra spaces removed. So let's say that a realm of "canon@ldap" means that all DNs have been mapped to this form. For this realm, the A1 hash may be precomputed by the server. A client using this realm must use the mapped form of the DN to compute hashes.
>
>If the realm is, say, "other@ldap", the A1 hash cannot be precomputed so the server must use the DN as presented by the client to form the hash. The hash cannot be precomputed.
>
>For any other realm, the username may not be a DN or may not be restricted as above. How it is processed is a local matter.
>
>Ron
>
>-----Original Message-----
>From: Mark Ennis [mailto:mark.ennis@adacel.com]
>Sent: Tuesday, 19 August 2003 11:59
>To: Ramsay, Ron
>Cc: Kurt D. Zeilenga; Alexey Melnikov; LDAPBis WG
>Subject: Re: Comments about draft-ietf-ldapbis-authmeth-05.txt
>
>
>Ron,
>
>You're right about storing the A1 hash being a problem without requiring 
>some canonical form for the LDAPDN, which is a non-trivial issue.
>
>My understanding of the realm is that it exists to identify different 
>authentication services available to the server. The LDAP directory, 
>using LDAPDN in the username, could be viewed as one of these 
>authentication services. Where the realm is used for other purposes by a 
>server, the use of it I proposed would potentially cause problems.
>
>- Mark.
>
>Ramsay, Ron wrote:
>> I agree that Kurt seems to be going too far in trying to exclude LDAP DNs.
>> 
>> I note that SASLprep is applied by the client, that LDAP DNs are UTF-8 encoded and that, therefore, there is no problem as long as the server does not attempt to change the DN (username).
>> 
>> I cannot see how the A1 hash can be stored unless the client is also required to somehow canonicalise the DN. SASLprep is not enough.
>> 
>> Using the realm to select a behaviour sounds interesting but may affect current implementations.
>> 
>> Ron
>> 
>> -----Original Message-----
>> From: Mark Ennis [mailto:mark.ennis@adacel.com]
>> Sent: Tuesday, 19 August 2003 09:05
>> To: Kurt D. Zeilenga
>> Cc: Ramsay, Ron; Alexey Melnikov; LDAPBis WG
>> Subject: Re: Comments about draft-ietf-ldapbis-authmeth-05.txt
>> 
>> 
>> Kurt,
>> 
>> It still seems to me as though you are the one re-engineering LDAP and 
>> its application of DIGEST-MD5. I have yet to come across anything in the 
>> LDAP or SASL specifications which preclude the use of distinguished name 
>> strings in the DIGEST-MD5 username value, except possibly the 
>> normalisation of the username field being proposed in the SASLprep work. 
>> After all, we should not forget that an LDAPDN *is* an UTF8 string in 
>> the protocol, and provided it is not mangled (normalised or SASLprep'd) 
>> prior to the server receiving it, it can then be interpreted (and 
>> matched) as a LDAPDN. Normalisation should occur prior to generating the 
>> digests at both server and client to produce consistent results and 
>> allow the possibility of storing the A1 hash rather than cleartext 
>> passwords.
>> 
>> I agree that the LDAP specifications do not preclude the use of 
>> non-LDAPDN strings in the username field, allowing interaction with 
>> (possibly shared) back-end authentication services. I see no particular 
>> problem with using the realm to distinguished how the username field 
>> should be interpreted.
>> 
>> - Mark.
>> 
>> Kurt D. Zeilenga wrote:
>> 
>>>Ron,
>>>
>>>It still sounds like you are trying to re-engineer LDAP and its
>>>application of DIGEST-MD5.  DIGEST-MD5 is not designed to support
>>>DN-based credentials.  As we have two mechanisms which are designed
>>>to support such, it seems far more appropriate for those who want to
>>>use DN-based credentials to simple use one of existing mechanism
>>>than for us to try to hack the LDAP TS to support DN-based credentials
>>>in DIGEST-MD5.
>>>
>>>At 11:18 PM 8/17/2003, Ramsay, Ron wrote:
>>>
>>>
>>>>I agree that we cannot canonicalise DNs (though I disagree that cn=foo and CN=FOO are different usernames). The canonicalisation was proposed to obviate the necessity of storing passwords in the clear.
>>>>
>>>>I also think the authmeth has the power to profile Digest-MD5.
>>>
>>>
>>>There are many reasons why we cannot do such, most have been previously
>>>discussed on the list.   However, I note that one of the reasons is that
>>>it will likely interfer with proxying of DIGEST-MD5 authentication
>>>requests to a "shared back-end authentication service" and/or
>>>implementing an LDAP-accessible "shared back-end authentication
>>>service".
>>>
>>>
>>>
>>>>If we simply state
>>>
>>>
>>>It's not so simple.  
>>>
>>>
>>>
>>>>1. The DN provided by the client in the bind is to be used (byte-for-byte) to calculate the required hashes, and
>>>>2. The realm provided by the server is to be used (byte-for-byte) to calculate hashes
>>>
>>>
>>>First, I note, that servers are required to use all usernames and realms
>>>byte-for-byte.  What's new to LDAP is that servers are to treat the
>>>username/realm as DNs in interactions with the (possibly shared)
>>>back-end authentication service.  Many of today's servers don't do that and
>>>those that do don't do it any standard way (as there is no formal
>>>specification of how to do that).  It is likely that any change in this
>>>area would cause interoperability problems, some of which likely have
>>>significant security considerations.
>>>
>>>To standardize such interaction would require engineering work on how to
>>>deal with the problem that dnMatch(dnString, SASLprep(dnString)) may be
>>>FALSE for some representations of a DN.  This implies that one either
>>>needs to restrict users to a subset of DN representations or apply a transform
>>>such that dnMatch(dnString, SASLprep(transform(dnString))) is TRUE for all
>>>possible dnStrings.  Both alternatives are problematic.
>>>
>>>
>>>
>>>>then I think Digest-MD5 can be used in LDAP, but the passwords have to be stored in-the-clear.
>>>
>>>
>>>I do not think it appropriate for authmeth to suggest DIGEST-MD5 passwords
>>>are to be stored in-the-clear when DIGEST-MD5 was specifically designed
>>>to avoid such.
>>>
>>>
>>>
>>>>The realm suggestions of Alexey can also be added to the profile. (Is there any reason for requiring that the realm not be ""?)
>>>>
>>>>Ron
>>>>
>>>>-----Original Message-----
>>>>From: Kurt D. Zeilenga [mailto:Kurt@OpenLDAP.org]
>>>>Sent: Monday, 18 August 2003 02:17
>>>>To: Alexey Melnikov
>>>>Cc: Ramsay, Ron; LDAPBis WG
>>>>Subject: Re: Comments about draft-ietf-ldapbis-authmeth-05.txt
>>>>
>>>>
>>>>Below are few additional technical comments...
>>>>
>>>>Basically what you are asking is that we state additional requirements that
>>>>implementations canonicalize
>>>>      a) all usernames, or
>>>>      b) all usernames which look like string representations of DNs.
>>>>
>>>>Both require the specification of an algorithm to produce a canonical string
>>>>representation of a DN.  The latter, (b), requires a specification of which input
>>>>strings are/are not to be canonicalized.
>>>>
>>>>First, I note that it is not generally possible to produce a canonical string
>>>>representation of a DN solely based on input of a non-canonical string
>>>>representation. Minimally, applicable schema is needed.
>>>>
>>>>Second, both a) and b) will introduce additional interoperability problems with
>>>>significant security implications.  In particular, if an existing system were
>>>>to have to different users "cn=foo" and "CN=FOO", one of these users
>>>>would no longer be able to long in as both a) and b) would cause these strings
>>>>to be treated as representing the same user where today they are clearly two
>>>>different users.
>>>>
>>>>Hence, even if we had a canonicalization algorithm, it would be inappropriate
>>>>to specify it be used here.  We need to preserve current semantics.
>>>>
>>>>Kurt
>>>>
>>>>
>>>>
>>>>At 08:24 AM 8/16/2003, Alexey Melnikov wrote:
>>>>
>>>>
>>>>>Kurt D. Zeilenga wrote:
>>>>>
>>>>>
>>>>>
>>>>>>At 08:15 AM 8/13/2003, Alexey Melnikov wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>Kurt D. Zeilenga wrote:
>>>>>>> 
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>At 06:14 AM 8/13/2003, Alexey Melnikov wrote:
>>>>>>>>   
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>I suggest that some text about the issue should be included in draft-ietf-ldapbis-authmeth.
>>>>>>>>>
>>>>>>>>>     
>>>>>>>>
>>>>>>>>If authmeth says anything about DNs and DIGEST-MD5, it should say
>>>>>>>>that the DIGEST-MD5 username and realm fields are, per the DIGEST-MD5
>>>>>>>>TS,
>>>>>>>>   
>>>>>>>
>>>>>>>Can you point me to the section where DIGEST-MD5 says that.
>>>>>>> 
>>>>>>
>>>>>>The DIGEST-MD5 TS [RFC2831] defines a username to be the user's
>>>>>>name (account) in a realm where the realm is a collection of names
>>>>>>(accounts), both have the form of a simple string
>>>>>
>>>>>Kurt, can you please point me to a formal definition of "simple username".
>>>>
>>>>RFC 2831 does not use the term "simple username".  It uses the term "username".
>>>>I believe RFC 2831 is reasonable clear that a username is a simple string used
>>>>as a user (account) name.  "simple" here meaning that the syntax and semantics
>>>>of the string are simple.
>>>>
>>>>
>>>>
>>>>
>>>>>>and are to be compared as simple strings.
>>>>>
>>>>>Fine, I don't disagree with that.
>>>>
>>>>>But DNs are used in simple bind. So it is quite logical to allow to use DNs in SASL as well.
>>>>>(And for implementation of other protocols with a login command that I know this is true.)
>>>>>
>>>>>So, if the server allows for DN form of usernames, the client should canonicalize a DN before passing it to the server to avoid interoperability problems. This is pretty much what my previous message suggested. I wasn't suggesting that the server should do that after receiving the username.
>>>>
>>>>How does the client determine whether the string entered by the user should or
>>>>shouldn't be canonized?  Is the client to canonicalize all strings which *look
>>>>like" DN string representations?  That obviously would break some usernames.
>>>>
>>>>
>>>>
>>>>>The same is true for a realm. If the server is using DNs as realms, it should canonicalize it before sending to the client. The client must not do any canonicalization.
>>>>
>>>>And that would break some realms.
>>>>
>>>>Also, saying that the client should canonicalize DN strings would necessitate
>>>>defining a canonical string representation of a DN.  Note that it is not generally
>>>>possible to generate a canonical DN string based solely on the input of a DN string
>>>>
>>>>
>>>>
>>>>>>DIGEST-MD5 defines the syntax of the username and realm using ABNF.
>>>>>
>>>>>Which is just a sequence of Unicode characters (no NUL allowed) represented in UTF8, nothing more.
>>>>
>>>>RFC 2831 says a username is a sequence of UTF-8 encoded Unicode characters
>>>>which represent a user name.
>>>>
>>>>RFC 2831 does not say a username is a sequence of UTF-8 encoded Unicode
>>>>characters which represent a DN.
>>>>
>>>>
>>>>
>>>>>Although the format of authentication ids (usernames) is SASL mechanism specific, DIGEST-MD5 doesn't have any restrictions other than the one mentioned above.
>>>>
>>>>It would be, in my opinion, inappropriate for LDAP to place additional syntax
>>>>and semantics upon the DIGEST-MD5 username and realm.
>>>>
>>>>
>>>>
>>>>>>There is a common definition, it's a "simple user name", e.g. an
>>>>>>account name.  A DN doesn't name a user, it names a entry.
>>>>>
>>>>>Of course I wasn't talking about an *arbitrary* DN, but only that represents a user or a group of users.
>>>>
>>>>My point is a "distinguished names" and a "user names" are different abstractions.
>>>>The username string represents a user name not a distinguished name.
>>>>
>>>>
>>>>
>>>>>>>(On a related note, I've seen IMAP servers that have used DNs as usernames).
>>>>>>
>>>>>>Did these IMAP servers allow all equivalent string representations
>>>>>>of the DN which referred to a user to be used as equivalent usernames in
>>>>>>DIGEST-MD5?
>>>>>
>>>>>Frankly I don't know, I don't remember if the server was supporting DIGEST-MD5.
>>>>
>>>>Even if was PLAIN or CRAM-MD5, I seriously doubt the IMAP server treated all
>>>>equivalent DN strings representations (stuffed in a username field) as being
>>>>equivalent.
>>>>
>>>>
>>>>
>>>>
>>>>>>If no, then obviously the IMAP server didn't support
>>>>>>DNs as usernames.  It supported usernames which **looked like** DN
>>>>>>strings.
>>>>>>
>>>>>
>>>>>Alexey
>>>>>
>>>>>
>>>
>>>
>>>
>>>
>> 
>> 
>> 
>> 



From owner-ietf-ldapbis@OpenLDAP.org  Tue Aug 19 05:45:33 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA03111
	for <ldapbis-archive@lists.ietf.org>; Tue, 19 Aug 2003 05:45:33 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h7J9cwNr090995;
	Tue, 19 Aug 2003 09:44:15 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h7J9YL36090703;
	Tue, 19 Aug 2003 09:34:21 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 19 Aug 2003 09:34:21 +0000
Received: from ausyms50.ca.com ([155.35.248.106])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h7J9YENf090656;
	Tue, 19 Aug 2003 09:34:15 GMT
	(envelope-from Ron.Ramsay@ca.com)
Received: from ausyms21.ca.com ([155.35.201.5]) by ausyms50.ca.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 19 Aug 2003 19:34:13 +1000
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: Comments about draft-ietf-ldapbis-authmeth-05.txt
Date: Tue, 19 Aug 2003 19:34:12 +1000
Message-ID: <1395B4B334FCC143B36AF788E68B63816D5330@ausyms21.ca.com>
Thread-Topic: Comments about draft-ietf-ldapbis-authmeth-05.txt
Thread-Index: AcNmATPTRpQKR+8lTfqtNtsCpA3tbwAM6Ohw
From: "Ramsay, Ron" <Ron.Ramsay@ca.com>
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Cc: "Mark Ennis" <mark.ennis@adacel.com>,
        "Alexey Melnikov" <Alexey.Melnikov@isode.com>,
        "LDAPBis WG" <ietf-ldapbis@OpenLDAP.org>
X-OriginalArrivalTime: 19 Aug 2003 09:34:13.0148 (UTC) FILETIME=[0CDAEDC0:01C36635]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by boole.openldap.org id h7J9YFNf090662
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 8bit

Well, OK, Kurt. But is there acceptance of this position on this list? Or, is there opposition to this position on this list?

?

-----Original Message-----
From: Kurt D. Zeilenga [mailto:Kurt@OpenLDAP.org]
Sent: Tuesday, 19 August 2003 13:24
To: Ramsay, Ron
Cc: Mark Ennis; Alexey Melnikov; LDAPBis WG
Subject: RE: Comments about draft-ietf-ldapbis-authmeth-05.txt


At 07:18 PM 8/18/2003, Ramsay, Ron wrote:
>Let me propose a way forward.

I suggest you write an individual I-D detailing your
technical proposal.

Kurt,  LDAPBIS co-chair

>The common namimg attributes used in DNs (c, l, o, ou, cn, dc) all have caseExactMatch as their matching rule. Therefore, DNs using these attributes can all be expressed in lowercase with extra spaces removed. So let's say that a realm of "canon@ldap" means that all DNs have been mapped to this form. For this realm, the A1 hash may be precomputed by the server. A client using this realm must use the mapped form of the DN to compute hashes.
>
>If the realm is, say, "other@ldap", the A1 hash cannot be precomputed so the server must use the DN as presented by the client to form the hash. The hash cannot be precomputed.
>
>For any other realm, the username may not be a DN or may not be restricted as above. How it is processed is a local matter.
>
>Ron
>
>-----Original Message-----
>From: Mark Ennis [mailto:mark.ennis@adacel.com]
>Sent: Tuesday, 19 August 2003 11:59
>To: Ramsay, Ron
>Cc: Kurt D. Zeilenga; Alexey Melnikov; LDAPBis WG
>Subject: Re: Comments about draft-ietf-ldapbis-authmeth-05.txt
>
>
>Ron,
>
>You're right about storing the A1 hash being a problem without requiring 
>some canonical form for the LDAPDN, which is a non-trivial issue.
>
>My understanding of the realm is that it exists to identify different 
>authentication services available to the server. The LDAP directory, 
>using LDAPDN in the username, could be viewed as one of these 
>authentication services. Where the realm is used for other purposes by a 
>server, the use of it I proposed would potentially cause problems.
>
>- Mark.
>
>Ramsay, Ron wrote:
>> I agree that Kurt seems to be going too far in trying to exclude LDAP DNs.
>> 
>> I note that SASLprep is applied by the client, that LDAP DNs are UTF-8 encoded and that, therefore, there is no problem as long as the server does not attempt to change the DN (username).
>> 
>> I cannot see how the A1 hash can be stored unless the client is also required to somehow canonicalise the DN. SASLprep is not enough.
>> 
>> Using the realm to select a behaviour sounds interesting but may affect current implementations.
>> 
>> Ron
>> 
>> -----Original Message-----
>> From: Mark Ennis [mailto:mark.ennis@adacel.com]
>> Sent: Tuesday, 19 August 2003 09:05
>> To: Kurt D. Zeilenga
>> Cc: Ramsay, Ron; Alexey Melnikov; LDAPBis WG
>> Subject: Re: Comments about draft-ietf-ldapbis-authmeth-05.txt
>> 
>> 
>> Kurt,
>> 
>> It still seems to me as though you are the one re-engineering LDAP and 
>> its application of DIGEST-MD5. I have yet to come across anything in the 
>> LDAP or SASL specifications which preclude the use of distinguished name 
>> strings in the DIGEST-MD5 username value, except possibly the 
>> normalisation of the username field being proposed in the SASLprep work. 
>> After all, we should not forget that an LDAPDN *is* an UTF8 string in 
>> the protocol, and provided it is not mangled (normalised or SASLprep'd) 
>> prior to the server receiving it, it can then be interpreted (and 
>> matched) as a LDAPDN. Normalisation should occur prior to generating the 
>> digests at both server and client to produce consistent results and 
>> allow the possibility of storing the A1 hash rather than cleartext 
>> passwords.
>> 
>> I agree that the LDAP specifications do not preclude the use of 
>> non-LDAPDN strings in the username field, allowing interaction with 
>> (possibly shared) back-end authentication services. I see no particular 
>> problem with using the realm to distinguished how the username field 
>> should be interpreted.
>> 
>> - Mark.
>> 
>> Kurt D. Zeilenga wrote:
>> 
>>>Ron,
>>>
>>>It still sounds like you are trying to re-engineer LDAP and its
>>>application of DIGEST-MD5.  DIGEST-MD5 is not designed to support
>>>DN-based credentials.  As we have two mechanisms which are designed
>>>to support such, it seems far more appropriate for those who want to
>>>use DN-based credentials to simple use one of existing mechanism
>>>than for us to try to hack the LDAP TS to support DN-based credentials
>>>in DIGEST-MD5.
>>>
>>>At 11:18 PM 8/17/2003, Ramsay, Ron wrote:
>>>
>>>
>>>>I agree that we cannot canonicalise DNs (though I disagree that cn=foo and CN=FOO are different usernames). The canonicalisation was proposed to obviate the necessity of storing passwords in the clear.
>>>>
>>>>I also think the authmeth has the power to profile Digest-MD5.
>>>
>>>
>>>There are many reasons why we cannot do such, most have been previously
>>>discussed on the list.   However, I note that one of the reasons is that
>>>it will likely interfer with proxying of DIGEST-MD5 authentication
>>>requests to a "shared back-end authentication service" and/or
>>>implementing an LDAP-accessible "shared back-end authentication
>>>service".
>>>
>>>
>>>
>>>>If we simply state
>>>
>>>
>>>It's not so simple.  
>>>
>>>
>>>
>>>>1. The DN provided by the client in the bind is to be used (byte-for-byte) to calculate the required hashes, and
>>>>2. The realm provided by the server is to be used (byte-for-byte) to calculate hashes
>>>
>>>
>>>First, I note, that servers are required to use all usernames and realms
>>>byte-for-byte.  What's new to LDAP is that servers are to treat the
>>>username/realm as DNs in interactions with the (possibly shared)
>>>back-end authentication service.  Many of today's servers don't do that and
>>>those that do don't do it any standard way (as there is no formal
>>>specification of how to do that).  It is likely that any change in this
>>>area would cause interoperability problems, some of which likely have
>>>significant security considerations.
>>>
>>>To standardize such interaction would require engineering work on how to
>>>deal with the problem that dnMatch(dnString, SASLprep(dnString)) may be
>>>FALSE for some representations of a DN.  This implies that one either
>>>needs to restrict users to a subset of DN representations or apply a transform
>>>such that dnMatch(dnString, SASLprep(transform(dnString))) is TRUE for all
>>>possible dnStrings.  Both alternatives are problematic.
>>>
>>>
>>>
>>>>then I think Digest-MD5 can be used in LDAP, but the passwords have to be stored in-the-clear.
>>>
>>>
>>>I do not think it appropriate for authmeth to suggest DIGEST-MD5 passwords
>>>are to be stored in-the-clear when DIGEST-MD5 was specifically designed
>>>to avoid such.
>>>
>>>
>>>
>>>>The realm suggestions of Alexey can also be added to the profile. (Is there any reason for requiring that the realm not be ""?)
>>>>
>>>>Ron
>>>>
>>>>-----Original Message-----
>>>>From: Kurt D. Zeilenga [mailto:Kurt@OpenLDAP.org]
>>>>Sent: Monday, 18 August 2003 02:17
>>>>To: Alexey Melnikov
>>>>Cc: Ramsay, Ron; LDAPBis WG
>>>>Subject: Re: Comments about draft-ietf-ldapbis-authmeth-05.txt
>>>>
>>>>
>>>>Below are few additional technical comments...
>>>>
>>>>Basically what you are asking is that we state additional requirements that
>>>>implementations canonicalize
>>>>      a) all usernames, or
>>>>      b) all usernames which look like string representations of DNs.
>>>>
>>>>Both require the specification of an algorithm to produce a canonical string
>>>>representation of a DN.  The latter, (b), requires a specification of which input
>>>>strings are/are not to be canonicalized.
>>>>
>>>>First, I note that it is not generally possible to produce a canonical string
>>>>representation of a DN solely based on input of a non-canonical string
>>>>representation. Minimally, applicable schema is needed.
>>>>
>>>>Second, both a) and b) will introduce additional interoperability problems with
>>>>significant security implications.  In particular, if an existing system were
>>>>to have to different users "cn=foo" and "CN=FOO", one of these users
>>>>would no longer be able to long in as both a) and b) would cause these strings
>>>>to be treated as representing the same user where today they are clearly two
>>>>different users.
>>>>
>>>>Hence, even if we had a canonicalization algorithm, it would be inappropriate
>>>>to specify it be used here.  We need to preserve current semantics.
>>>>
>>>>Kurt
>>>>
>>>>
>>>>
>>>>At 08:24 AM 8/16/2003, Alexey Melnikov wrote:
>>>>
>>>>
>>>>>Kurt D. Zeilenga wrote:
>>>>>
>>>>>
>>>>>
>>>>>>At 08:15 AM 8/13/2003, Alexey Melnikov wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>Kurt D. Zeilenga wrote:
>>>>>>> 
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>At 06:14 AM 8/13/2003, Alexey Melnikov wrote:
>>>>>>>>   
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>I suggest that some text about the issue should be included in draft-ietf-ldapbis-authmeth.
>>>>>>>>>
>>>>>>>>>     
>>>>>>>>
>>>>>>>>If authmeth says anything about DNs and DIGEST-MD5, it should say
>>>>>>>>that the DIGEST-MD5 username and realm fields are, per the DIGEST-MD5
>>>>>>>>TS,
>>>>>>>>   
>>>>>>>
>>>>>>>Can you point me to the section where DIGEST-MD5 says that.
>>>>>>> 
>>>>>>
>>>>>>The DIGEST-MD5 TS [RFC2831] defines a username to be the user's
>>>>>>name (account) in a realm where the realm is a collection of names
>>>>>>(accounts), both have the form of a simple string
>>>>>
>>>>>Kurt, can you please point me to a formal definition of "simple username".
>>>>
>>>>RFC 2831 does not use the term "simple username".  It uses the term "username".
>>>>I believe RFC 2831 is reasonable clear that a username is a simple string used
>>>>as a user (account) name.  "simple" here meaning that the syntax and semantics
>>>>of the string are simple.
>>>>
>>>>
>>>>
>>>>
>>>>>>and are to be compared as simple strings.
>>>>>
>>>>>Fine, I don't disagree with that.
>>>>
>>>>>But DNs are used in simple bind. So it is quite logical to allow to use DNs in SASL as well.
>>>>>(And for implementation of other protocols with a login command that I know this is true.)
>>>>>
>>>>>So, if the server allows for DN form of usernames, the client should canonicalize a DN before passing it to the server to avoid interoperability problems. This is pretty much what my previous message suggested. I wasn't suggesting that the server should do that after receiving the username.
>>>>
>>>>How does the client determine whether the string entered by the user should or
>>>>shouldn't be canonized?  Is the client to canonicalize all strings which *look
>>>>like" DN string representations?  That obviously would break some usernames.
>>>>
>>>>
>>>>
>>>>>The same is true for a realm. If the server is using DNs as realms, it should canonicalize it before sending to the client. The client must not do any canonicalization.
>>>>
>>>>And that would break some realms.
>>>>
>>>>Also, saying that the client should canonicalize DN strings would necessitate
>>>>defining a canonical string representation of a DN.  Note that it is not generally
>>>>possible to generate a canonical DN string based solely on the input of a DN string
>>>>
>>>>
>>>>
>>>>>>DIGEST-MD5 defines the syntax of the username and realm using ABNF.
>>>>>
>>>>>Which is just a sequence of Unicode characters (no NUL allowed) represented in UTF8, nothing more.
>>>>
>>>>RFC 2831 says a username is a sequence of UTF-8 encoded Unicode characters
>>>>which represent a user name.
>>>>
>>>>RFC 2831 does not say a username is a sequence of UTF-8 encoded Unicode
>>>>characters which represent a DN.
>>>>
>>>>
>>>>
>>>>>Although the format of authentication ids (usernames) is SASL mechanism specific, DIGEST-MD5 doesn't have any restrictions other than the one mentioned above.
>>>>
>>>>It would be, in my opinion, inappropriate for LDAP to place additional syntax
>>>>and semantics upon the DIGEST-MD5 username and realm.
>>>>
>>>>
>>>>
>>>>>>There is a common definition, it's a "simple user name", e.g. an
>>>>>>account name.  A DN doesn't name a user, it names a entry.
>>>>>
>>>>>Of course I wasn't talking about an *arbitrary* DN, but only that represents a user or a group of users.
>>>>
>>>>My point is a "distinguished names" and a "user names" are different abstractions.
>>>>The username string represents a user name not a distinguished name.
>>>>
>>>>
>>>>
>>>>>>>(On a related note, I've seen IMAP servers that have used DNs as usernames).
>>>>>>
>>>>>>Did these IMAP servers allow all equivalent string representations
>>>>>>of the DN which referred to a user to be used as equivalent usernames in
>>>>>>DIGEST-MD5?
>>>>>
>>>>>Frankly I don't know, I don't remember if the server was supporting DIGEST-MD5.
>>>>
>>>>Even if was PLAIN or CRAM-MD5, I seriously doubt the IMAP server treated all
>>>>equivalent DN strings representations (stuffed in a username field) as being
>>>>equivalent.
>>>>
>>>>
>>>>
>>>>
>>>>>>If no, then obviously the IMAP server didn't support
>>>>>>DNs as usernames.  It supported usernames which **looked like** DN
>>>>>>strings.
>>>>>>
>>>>>
>>>>>Alexey
>>>>>
>>>>>
>>>
>>>
>>>
>>>
>> 
>> 
>> 
>> 





From owner-ietf-ldapbis@OpenLDAP.org  Tue Aug 19 12:05:06 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20252
	for <ldapbis-archive@lists.ietf.org>; Tue, 19 Aug 2003 12:05:02 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h7JFv5Nj019662;
	Tue, 19 Aug 2003 16:02:00 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h7JFqYEU019346;
	Tue, 19 Aug 2003 15:52:34 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 19 Aug 2003 15:52:34 +0000
Received: from highlandsun.propagation.net (highlandsun.propagation.net [66.221.212.168])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h7JFqVNf019319;
	Tue, 19 Aug 2003 15:52:31 GMT
	(envelope-from hyc@highlandsun.com)
Received: from CELLO (localhost [127.0.0.1])
	by highlandsun.propagation.net (8.12.9/8.12.9) with SMTP id h7JFqRJ6006927;
	Tue, 19 Aug 2003 10:52:28 -0500
From: "Howard Chu" <hyc@highlandsun.com>
To: "'Mark Ennis'" <mark.ennis@adacel.com>,
        "'Kurt D. Zeilenga'" <Kurt@OpenLDAP.org>
Cc: "'Ramsay, Ron'" <Ron.Ramsay@ca.com>,
        "'Alexey Melnikov'" <Alexey.Melnikov@isode.com>,
        "'LDAPBis WG'" <ietf-ldapbis@OpenLDAP.org>
Subject: RE: Comments about draft-ietf-ldapbis-authmeth-05.txt
Date: Tue, 19 Aug 2003 00:43:17 -0700
Message-ID: <009e01c36669$cfd38150$0e01a8c0@CELLO>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
In-Reply-To: <3F415BA3.4040108@adacel.com>
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

> -----Original Message-----
> From: owner-ietf-ldapbis@OpenLDAP.org
> [mailto:owner-ietf-ldapbis@OpenLDAP.org]On Behalf Of Mark Ennis

> Kurt,

> It still seems to me as though you are the one re-engineering
> LDAP and
> its application of DIGEST-MD5. I have yet to come across
> anything in the
> LDAP or SASL specifications which preclude the use of
> distinguished name
> strings in the DIGEST-MD5 username value, except possibly the
> normalisation of the username field being proposed in the
> SASLprep work.

The fact that Distinguished Names are necessarily of unbounded length, while
the DIGEST-MD5 "digest-response" (which must contain the username) is
restricted by RFC2831 to 4096 bytes or less, implies that these two concepts
are inherently disjoint.

  -- Howard Chu
  Chief Architect, Symas Corp.       Director, Highland Sun
  http://www.symas.com               http://highlandsun.com/hyc
  Symas: Premier OpenSource Development and Support



From owner-ietf-ldapbis@OpenLDAP.org  Tue Aug 26 17:50:44 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13056
	for <ldapbis-archive@lists.ietf.org>; Tue, 26 Aug 2003 17:50:43 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h7QLlrNf094261;
	Tue, 26 Aug 2003 21:47:53 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h7QLcx2k092974;
	Tue, 26 Aug 2003 21:38:59 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 26 Aug 2003 21:38:59 +0000
Received: from prv-mail20.provo.novell.com (prv-mail20.provo.novell.com [137.65.81.122])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h7QLcwNf092908
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 26 Aug 2003 21:38:58 GMT
	(envelope-from jimse@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Tue, 26 Aug 2003 15:38:38 -0600
Message-Id: <sf4b7efe.076@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.1 
Date: Tue, 26 Aug 2003 15:35:45 -0600
From: "Jim Sermersheim" <jimse@novell.com>
To: <ietf-ldapbis@OpenLDAP.org>
Subject: referrals question
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

All,

Currently, [Protocol] (Section 4.1.10) says: "If an alias was
dereferenced, the <dn> part of the URL MUST be present, with the new
target object name". This assumes that there is a <dn> part in the
referral URL. [Protocol] says that other kinds of URLs can be returned.
There are no requirements that all types of URLs contain a place for a
DN. So, if an alias is dereferenced while resolving a name, and the
referral contains non-LDAP URLs, is the server expected to:

a) not return those non-LDAP referrals?
b) only return non-LDAP referrals where the server knows the format,
the URL format allows a DN, and the server fills in the DN part
c) return the non-LDAP referrals as they exist in the data store (if
they exist at all), even if no knowledge of DN placement is known.

I note that another case where the server should provide the dn part is
where a reference object has been placed and the referral attribute has
the dn part populated (and that dn is different from the dn of the
reference object). If the name being resolved is subordinate to that
reference object, the dn of the referral(s) should reflect the DN held
in the referral attribute plus the unresolved portion of the original dn
on the operation.


