From owner-ietf-ldapbis@OpenLDAP.org  Thu May  1 16:03: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 QAA06163
	for <ldapbis-archive@lists.ietf.org>; Thu, 1 May 2003 16:03:30 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h41JUqEl030673;
	Thu, 1 May 2003 19:31:42 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 h41JSO12030577;
	Thu, 1 May 2003 19:28:24 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 1 May 2003 19:28:24 +0000
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h41JS6Eh030566
	for <ietf-ldapbis@openldap.org>; Thu, 1 May 2003 19:28:06 GMT
	(envelope-from nsyracus@cnri.reston.va.us)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02591;
	Thu, 1 May 2003 15:25:11 -0400 (EDT)
Message-Id: <200305011925.PAA02591@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: ietf-ldapbis@OpenLDAP.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-ldapbis-user-schema-05.txt
Date: Thu, 01 May 2003 15:25:10 -0400
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>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the LDAP (v3) Revision Working Group of the IETF.

	Title		: LDAP:  User Schema
	Author(s)	: K. Dally
	Filename	: draft-ietf-ldapbis-user-schema-05.txt
	Pages		: 25
	Date		: 2003-5-1
	
This document is a integral part of the LDAP technical specification 
[ROADMAP].  It provides an overview of attribute types and object 
classes intended for use by LDAP directory clients for many 
directory services, such as, White Pages.  Originally specified the 
ISO/IEC 9594 and X.500 documents, these objects are widely used as a 
basis for the schema in many LDAP directories.  This document does 
not cover attributes used for the administration of directory 
servers, nor does it include directory objects defined for specific 
uses in other documents.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ldapbis-user-schema-05.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-ldapbis-user-schema-05.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-ldapbis-user-schema-05.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2003-5-1153607.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ldapbis-user-schema-05.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-ldapbis-user-schema-05.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-5-1153607.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-ietf-ldapbis@OpenLDAP.org  Fri May  2 16:37: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 QAA01684
	for <ldapbis-archive@lists.ietf.org>; Fri, 2 May 2003 16:36: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 h42Kb0El096626;
	Fri, 2 May 2003 20:38: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 h42KYt95096534;
	Fri, 2 May 2003 20:34:55 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Fri, 2 May 2003 20:34:55 +0000
Received: from pat.uio.no (pat.uio.no [129.240.130.16])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h42KYrEh096521
	for <ietf-ldapbis@openldap.org>; Fri, 2 May 2003 20:34:54 GMT
	(envelope-from hbf@bombur.uio.no)
Received: from goggins.uio.no ([129.240.201.2])
	by pat.uio.no with esmtp (Exim 2.12 #7)
	id 19BhF6-0001ig-00
	for ietf-ldapbis@openldap.org; Fri, 2 May 2003 22:34:52 +0200
Received: from bombur.uio.no ([129.240.186.42])
	by goggins.uio.no with esmtp (Exim 2.12 #7)
	id 19BhF5-00054p-00
	for ietf-ldapbis@openldap.org; Fri, 2 May 2003 22:34:51 +0200
Received: from hbf by bombur.uio.no with local (Exim 2.12 #7)
	id 19BhF5-0001Ex-00
	for ietf-ldapbis@OpenLDAP.org; Fri, 2 May 2003 22:34:51 +0200
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Message-Id: <HBF.20030502kpe7@bombur.uio.no>
To: ietf-ldapbis@OpenLDAP.org
Subject: Schema draft: Syntaxes postalAddress...preferredDeliveryMethod
Date: Fri, 2 May 2003 22:34:51 +0200
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>

In the Schema-05 draft, why have postalAddress, postalCode,
postOfficeBox and preferredDeliveryMethod changed syntax from 1.3.* to
1.5.*?  It doesn't match the Syntaxes-05 draft, and it's not mentioned
in the appendix with changes.

-- 
Hallvard



From owner-ietf-ldapbis@OpenLDAP.org  Fri May  2 16:42:40 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 QAA01847
	for <ldapbis-archive@lists.ietf.org>; Fri, 2 May 2003 16:42: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 h42Kh0El097062;
	Fri, 2 May 2003 20:43: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 h42Kf1FN096894;
	Fri, 2 May 2003 20:41:01 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Fri, 2 May 2003 20:41:01 +0000
Received: from pat.uio.no (pat.uio.no [129.240.130.16])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h42KexEh096870
	for <ietf-ldapbis@openldap.org>; Fri, 2 May 2003 20:41:00 GMT
	(envelope-from hbf@bombur.uio.no)
Received: from mons.uio.no ([129.240.130.14])
	by pat.uio.no with esmtp (Exim 2.12 #7)
	id 19BhKy-00024V-00; Fri, 2 May 2003 22:40:56 +0200
Received: from bombur.uio.no ([129.240.186.42])
	by mons.uio.no with esmtp (Exim 2.12 #7)
	id 19BhKy-00005v-00; Fri, 2 May 2003 22:40:56 +0200
Received: from hbf by bombur.uio.no with local (Exim 2.12 #7)
	id 19BhKx-0001Fo-00; Fri, 2 May 2003 22:40:55 +0200
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Message-Id: <HBF.20030502klqq@bombur.uio.no>
To: Vijay KN <KNVIJAY@novell.com>
Cc: Vithalprasad Gaitonde <GVithalprasad@novell.com>,
        Savitha R <RSAVITHA@novell.com>, ietf-ldapbis@OpenLDAP.org
Subject: Re: result code for a deleted identity on a connection
In-Reply-To: <seaf6b3a.068@prv-mail20.provo.novell.com>
References: <seaf6b3a.068@prv-mail20.provo.novell.com>
X-Mailer: VM 6.37 under Emacs 19.34.1
Date: Fri, 2 May 2003 22:40:55 +0200
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>

Vijay KN writes:
> I am not very clear how a server can continue to serve requests on the
> connection. If new objects are created on the connection after the user
> object deletion, then what is the user-id assigned by the server as the
> creator/owner for such objects (since the user object has been deleted)
> ?

If the server did not detect the problem, it would just continue using
the user ID it did before.  It couldn't do that if it needed to look
up the ID object in the directory for each update, of course.  But if
the ID is just the bind DN, or if the info was cached, it would work.

> Audit logs would show that objects were created by the user, after
> the user object had been deleted. Isn't this a problem ?

Depends on what the logs are used for, or if they are used at all.

-- 
Hallvard


From owner-ietf-ldapbis@OpenLDAP.org  Fri May  2 16:53:11 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 QAA02277
	for <ldapbis-archive@lists.ietf.org>; Fri, 2 May 2003 16:53:10 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h42Kt0El097981;
	Fri, 2 May 2003 20:55:05 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 h42KrIaF097681;
	Fri, 2 May 2003 20:53:18 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Fri, 2 May 2003 20:53:18 +0000
Received: from pat.uio.no (pat.uio.no [129.240.130.16])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h42KrFEh097641
	for <ietf-ldapbis@openldap.org>; Fri, 2 May 2003 20:53:16 GMT
	(envelope-from hbf@bombur.uio.no)
Received: from mons.uio.no ([129.240.130.14])
	by pat.uio.no with esmtp (Exim 2.12 #7)
	id 19BhWq-00037L-00; Fri, 2 May 2003 22:53:12 +0200
Received: from bombur.uio.no ([129.240.186.42])
	by mons.uio.no with esmtp (Exim 2.12 #7)
	id 19BhWp-0001Bh-00; Fri, 2 May 2003 22:53:11 +0200
Received: from hbf by bombur.uio.no with local (Exim 2.12 #7)
	id 19BhWp-0001HZ-00; Fri, 2 May 2003 22:53:11 +0200
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Message-Id: <HBF.20030502kecx@bombur.uio.no>
To: Vithalprasad Gaitonde <gvithalprasad@novell.com>
Cc: Vijay KN <KNVIJAY@novell.com>, Savitha R <RSAVITHA@novell.com>,
        ietf-ldapbis@OpenLDAP.org
Subject: Re: result code for a deleted identity on a connection
In-Reply-To: <seaf6cb2.011@prv-mail20.provo.novell.com>
References: <seaf6cb2.011@prv-mail20.provo.novell.com>
X-Mailer: VM 6.37 under Emacs 19.34.1
Date: Fri, 2 May 2003 22:53:11 +0200
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>

Vithalprasad Gaitonde writes:
> "I suspect it might be a lot of work for servers to keep track of this.
> So I think the server should have that option, but it should also have
> the option not to notice this condition and keep serving requests as
> if nothing happened."
> 
> Well...wouldn't this be a security breach. The object may have been
> deleted by the administrator as he is an invalid user for the directory
> (e.g. left the Organization). In such a case, it would be inappropriate
> for the user to be allowed access.

He'd have to keep an authenticated LDAP connection from an off-site host
alive when he anticipated that he'd be fired, but if so it would be a
problem, yes.  If that's a scenario you worry about, you'll need a
server which handles it.  I just think that in most cases the situation
is unlikely enough that it can be made a QoI issue, but if server
implementors don't mind implementing it I'm not going to quarrel.

If we are going to worry about the bind credentials being invalidated,
I'd be more worried about users who bound with valid credentials but
then the attribute with the credentials (password or certificate) was
deleted or modified from the user's object.  That happens frequently
here, and regularly because the user has broken the rules and gets
temporarily closed out from the system.  If so, it should be allowed to
configure the server to only start returning failures e.g. 4 hours after
the object was changed, though, since there are also 'benign' situations
where the password changes.  We don't want users thrown out of the
system immediately in these cases.  I don't know if the same can apply
when the bind object gets deleted.

> invalidCredentials may be a misleading error code to return as the bind
> has already succeeded.

Well, the bind had succeeded, but now the bind credentials have become
invalid.  And the code can't be mistaken for anything else, since no
other operation than bind normally returns it.

-- 
Hallvard


From owner-ietf-ldapbis@OpenLDAP.org  Fri May  2 17:14: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 ESMTP id RAA03022
	for <ldapbis-archive@lists.ietf.org>; Fri, 2 May 2003 17:14:27 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h42L7DFB099024;
	Fri, 2 May 2003 21:16:30 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 h42KxQ2A098396;
	Fri, 2 May 2003 20:59:26 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Fri, 2 May 2003 20:59:26 +0000
Received: from pat.uio.no (pat.uio.no [129.240.130.16])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h42KxMEh098366;
	Fri, 2 May 2003 20:59:23 GMT
	(envelope-from hbf@bombur.uio.no)
Received: from mons.uio.no ([129.240.130.14])
	by pat.uio.no with esmtp (Exim 2.12 #7)
	id 19Bhcn-0003ew-00; Fri, 2 May 2003 22:59:21 +0200
Received: from bombur.uio.no ([129.240.186.42])
	by mons.uio.no with esmtp (Exim 2.12 #7)
	id 19Bhcn-0001dB-00; Fri, 2 May 2003 22:59:21 +0200
Received: from hbf by bombur.uio.no with local (Exim 2.12 #7)
	id 19Bhcn-0001IW-00; Fri, 2 May 2003 22:59:21 +0200
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Message-Id: <HBF.20030502kana@bombur.uio.no>
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Cc: Vithalprasad Gaitonde <gvithalprasad@novell.com>,
        ietf-ldapbis@OpenLDAP.org, Vijay KN <KNVIJAY@novell.com>,
        Savitha R <RSAVITHA@novell.com>
Subject: Re: result code for a deleted identity on a connection
In-Reply-To: <5.2.0.9.0.20030430070834.02a42210@127.0.0.1>
References: <seaf4fcf.044@prv-mail25.provo.novell.com>
	<5.2.0.9.0.20030430070834.02a42210@127.0.0.1>
X-Mailer: VM 6.37 under Emacs 19.34.1
Date: Fri, 2 May 2003 22:59:21 +0200
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:
>> We should probably have a result code like invalidIdentity which is
>> sent back with a notice of disconnection (section 4.4.1 protocol draft)
>> followed by a closing of the connection by the server.
> 
> RFC 2251, 4.4.1:
>>   - strongAuthRequired: The server has detected that an established
>>     underlying security association protecting communication between
>>     the client and server has unexpectedly failed or been compromised.
> 
> I think it would be reasonable to return this in this case as well.

Why ask for _strong_ auth, and not just auth?

-- 
Hallvard


From owner-ietf-ldapbis@OpenLDAP.org  Fri May  2 18:37: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 SAA05890
	for <ldapbis-archive@lists.ietf.org>; Fri, 2 May 2003 18:37:29 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h42MV0El002477;
	Fri, 2 May 2003 22:31: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 h42MTWg5002424;
	Fri, 2 May 2003 22:29:32 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Fri, 2 May 2003 22:29:32 +0000
Received: from smtpproxy2.mitre.org (smtpproxy2.mitre.org [192.80.55.70])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h42MTUEh002413
	for <ietf-ldapbis@openldap.org>; Fri, 2 May 2003 22:29:31 GMT
	(envelope-from kdally@mitre.org)
Received: from avsrv2.mitre.org (avsrv2.mitre.org [128.29.154.4])
	by smtpproxy2.mitre.org (8.12.9/8.12.8) with ESMTP id h42MTTNe008158;
	Fri, 2 May 2003 18:29:29 -0400 (EDT)
Received: from MAILHUB1 (mailhub1.mitre.org [129.83.20.31])
	by smtpsrv2.mitre.org (8.12.9/8.12.8) with ESMTP id h42MTPmp005889;
	Fri, 2 May 2003 18:29:25 -0400 (EDT)
Received: from mm109527-2k.mitre.org (128.29.3.75) by mailhub1.mitre.org with SMTP
        id 2258552; Fri, 02 May 2003 18:29:22 -0400
Message-ID: <3EB2F141.B4C49CBD@mitre.org>
Date: Fri, 02 May 2003 18:29:21 -0400
From: Kathy Dally <kdally@mitre.org>
Organization: The MITRE Corporation
X-Mailer: Mozilla 4.79 [en]C-20020130M  (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
CC: ietf-ldapbis@OpenLDAP.org
Subject: Re: Schema draft: Syntaxes postalAddress...preferredDeliveryMethod
References: <HBF.20030502kpe7@bombur.uio.no>
Content-Type: text/plain; charset=us-ascii
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

Hi Hallvard!

The change was not intentional.  Thanks for catching it.

Regards,
Kathy Dally

Hallvard B Furuseth wrote:
> 
> In the Schema-05 draft, why have postalAddress, postalCode,
> postOfficeBox and preferredDeliveryMethod changed syntax from 1.3.* to
> 1.5.*?  It doesn't match the Syntaxes-05 draft, and it's not mentioned
> in the appendix with changes.
> 
> --
> Hallvard



From owner-ietf-ldapbis@OpenLDAP.org  Fri May  2 18:41:59 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 SAA06024
	for <ldapbis-archive@lists.ietf.org>; Fri, 2 May 2003 18:41:58 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h42Mh0El002979;
	Fri, 2 May 2003 22:43: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 h42MeTKE002917;
	Fri, 2 May 2003 22:40:29 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Fri, 2 May 2003 22:40:29 +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 h42MeREh002907
	for <ietf-ldapbis@OpenLDAP.org>; Fri, 2 May 2003 22:40:28 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 h42MeR9a038180;
	Fri, 2 May 2003 22:40:27 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030502150950.027514b8@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Fri, 02 May 2003 15:38:01 -0700
To: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: result code for a deleted identity on a connection
Cc: ietf-ldapbis@OpenLDAP.org
In-Reply-To: <HBF.20030502kana@bombur.uio.no>
References: <5.2.0.9.0.20030430070834.02a42210@127.0.0.1>
 <seaf4fcf.044@prv-mail25.provo.novell.com>
 <5.2.0.9.0.20030430070834.02a42210@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 01:59 PM 5/2/2003, Hallvard B Furuseth wrote:
>Kurt D. Zeilenga writes:
>>> We should probably have a result code like invalidIdentity which is
>>> sent back with a notice of disconnection (section 4.4.1 protocol draft)
>>> followed by a closing of the connection by the server.
>> 
>> RFC 2251, 4.4.1:
>>>   - strongAuthRequired: The server has detected that an established
>>>     underlying security association protecting communication between
>>>     the client and server has unexpectedly failed or been compromised.
>> 
>> I think it would be reasonable to return this in this case as well.
>
>Why ask for _strong_ auth, and not just auth?

First, we've clarified the result code, in general, to mean:
>        strongAuthRequired (8)
>           Except when returned in a Notice of Disconnect (see section 
>           4.4.1), this indicates that the server requires the client to
>           authentication using a strong(er) mechanism.

But I'm thinking RFC 2251, 4.4.1 should be clarified as well:
        - strongAuthRequired: The server has detected that an establish
          security association between the client and server has
          unexpectedly failed or been compromised, or that the
          server now requires the client to authenticate using a
          strong(er) mechanism.

That is, generalized the result code here as well.  I also
think other codes should be allowed in the Notice.  I think
it reasonable for implementations to return a variety of
other codes including busy, other, adminLimitExceeded,
unwillingToPerform, and confidentialityRequired.

Kurt 



From owner-ietf-ldapbis@OpenLDAP.org  Sat May  3 00:01:19 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 AAA10877
	for <ldapbis-archive@lists.ietf.org>; Sat, 3 May 2003 00:01:04 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h43412El012412;
	Sat, 3 May 2003 04:01:46 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 h433uIIB012253;
	Sat, 3 May 2003 03:56:18 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Sat, 3 May 2003 03:56:18 +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 h433uGEh012236
	for <ietf-ldapbis@OpenLDAP.org>; Sat, 3 May 2003 03:56:16 GMT
	(envelope-from RHARRISON@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Fri, 02 May 2003 21:55:55 -0600
Message-Id: <seb2e96b.002@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.0 
Date: Fri, 02 May 2003 21:52:59 -0600
From: "Roger Harrison" <RHARRISON@novell.com>
To: <mark.ennis@adacel.com>, <ietf-ldapbis@OpenLDAP.org>
Subject: Re: Should response-auth be optional for digest authentication
	in authmeth?
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=_035C83DB.33521BC6"
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 MIME message. If you are reading this text, you may want to 
consider changing to a mail reader or gateway that understands how to 
properly handle MIME multipart messages.

--=_035C83DB.33521BC6
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

The text in draft-ietf-ldapbis-authmeth-05.txt Section 8.2 paragraph 6
is identical to RFC 2829 Section 6.1 paragraph 5, so this wording
predates the revision work being done in the ldapbis working group. 
 
That said, here is a summary of my review of the issue:
 
1. Based on the wording of RFC2831 section 2.1.3  it appears that the
intent was for the response-auth to always be sent.
 
2. It appears that one use of the response-auth is to provide a limited
form of mutual authentication of the server to the client (i.e. the
server can at least prove that it knows the client's password, thus it
can be trusted).
 
3. For purposes of mutual authentication, the value of the
response-auth is equally valuable regardless of whether the client and
server support subsequent authentication.
 
4. The response-auth value is required to perform subsequent
authentication.
 
5. The only reason I can see for making the response-auth optional WRT
LDAP is to signal to the client whether the server supports subsequent
authentication.
 
I believe we should modify the text of authmeth-05 section 8.2
paragraph 6 to always have the credentials field contain the value of
response-auth *if* this can be done without causing a problem for item 5
above (ability to signal server support for subsequent authenticaion)
AND also not cause interoperability problems for clients that may not be
expecting the value.
 
I'd would greatly appreciate guidance from other working group members
on the best course of action to take.
 
Thanks,
 
Roger
 
Roger G. Harrison
Manager, eDirectory Core and Utilities
Novell, Inc., the Leader Provider of Net Business Solutions
www.novell.com 

>>> Mark Ennis <mark.ennis@adacel.com> 4/14/2003 11:48:24 PM >>>
The current draft of authmeth (draft-ietf-ldapbis-authmeth-05.txt) 
indicates, in section 8.2 paragraph 6, that the response-auth SASL 
message is only included in the bind response for a successful bind
when 
the server supports subsequent authentication. This seems counter to
the 
intention of RFC2831 section 2.1.3 which indicates that the 
response-auth should always be returned.

The response-auth provides one of the security aspects documented in 
RFC2831, that of protection against "Spoofing by counterfeit servers" 
(section 3.8). RFC2617, upon which RFC2831 is based, describes this 
protection as "The optional response digest in the "response-auth" 
directive supports mutual authentication -- the server proves that it 
knows the user's secret, and with qop=auth-int also provides limited 
integrity protection of the response.". Note that response-auth is 
optional in RFC2617, but not (in my opinion) in RFC2831.

Was this diversion from the apparent intention of RFC2831 intentional 
and if so, what is the reasoning behind weakening the authentication 
procedure in this way?

Regards,
Mark Ennis




--=_035C83DB.33521BC6
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1169" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Tahoma">
<DIV>The text in draft-ietf-ldapbis-authmeth-05.txt Section 8.2 paragraph 6 is 
identical to RFC 2829 Section 6.1 paragraph 5, so this wording predates the 
revision work being done in the ldapbis working group. </DIV>
<DIV>&nbsp;</DIV>
<DIV>That said, here is a summary of my review of the issue:</DIV>
<DIV>&nbsp;</DIV>
<DIV>1. Based on the wording of RFC2831 section 2.1.3&nbsp;&nbsp;it appears that 
the intent was for the response-auth to always be sent.</DIV>
<DIV>&nbsp;</DIV>
<DIV>2. It appears that one use of the response-auth is to provide a limited 
form of mutual authentication of the server to the client (i.e. the server can 
at least prove that it knows the client's password, thus it can be 
trusted).</DIV>
<DIV>&nbsp;</DIV>
<DIV>3. For purposes of mutual authentication, the value of the response-auth is 
equally valuable regardless of whether the client and server support subsequent 
authentication.</DIV>
<DIV>&nbsp;</DIV>
<DIV>4. The response-auth value is required to perform subsequent 
authentication.</DIV>
<DIV>&nbsp;</DIV>
<DIV>5. The only reason I can see for making the response-auth optional WRT LDAP 
is to signal to the client whether the server supports subsequent 
authentication.</DIV>
<DIV>&nbsp;</DIV>
<DIV>I believe we should modify the text of authmeth-05 section 8.2 paragraph 6 
to always have the credentials field contain the value of response-auth *if* 
this can be done without causing a problem for item 5 above (ability to signal 
server support for subsequent authenticaion) AND also not cause interoperability 
problems for clients that may not be expecting the value.</DIV>
<DIV>&nbsp;</DIV>
<DIV>I'd would greatly appreciate guidance from other working group members on 
the best course of action to take.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Thanks,</DIV>
<DIV>&nbsp;</DIV>
<DIV>Roger</DIV>
<DIV>&nbsp;</DIV>
<DIV>Roger G. Harrison<BR>Manager, eDirectory Core and Utilities<BR>Novell, 
Inc., the Leader Provider of Net Business Solutions<BR><A 
href="http://www.novell.com">www.novell.com</A></DIV>
<DIV><BR>&gt;&gt;&gt; Mark Ennis &lt;mark.ennis@adacel.com&gt; 4/14/2003 
11:48:24 PM &gt;&gt;&gt;<BR>The current draft of authmeth 
(draft-ietf-ldapbis-authmeth-05.txt) <BR>indicates, in section 8.2 paragraph 6, 
that the response-auth SASL <BR>message is only included in the bind response 
for a successful bind when <BR>the server supports subsequent authentication. 
This seems counter to the <BR>intention of RFC2831 section 2.1.3 which indicates 
that the <BR>response-auth should always be returned.<BR><BR>The response-auth 
provides one of the security aspects documented in <BR>RFC2831, that of 
protection against "Spoofing by counterfeit servers" <BR>(section 3.8). RFC2617, 
upon which RFC2831 is based, describes this <BR>protection as "The optional 
response digest in the "response-auth" <BR>directive supports mutual 
authentication -- the server proves that it <BR>knows the user's secret, and 
with qop=auth-int also provides limited <BR>integrity protection of the 
response.". Note that response-auth is <BR>optional in RFC2617, but not (in my 
opinion) in RFC2831.<BR><BR>Was this diversion from the apparent intention of 
RFC2831 intentional <BR>and if so, what is the reasoning behind weakening the 
authentication <BR>procedure in this way?<BR><BR>Regards,<BR>Mark 
Ennis<BR><BR><BR></DIV></BODY></HTML>

--=_035C83DB.33521BC6--


From owner-ietf-ldapbis@OpenLDAP.org  Sun May  4 18:36: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 SAA08791
	for <ldapbis-archive@lists.ietf.org>; Sun, 4 May 2003 18:36:11 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h44MPGEl081831;
	Sun, 4 May 2003 22:26: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 h44MOlBJ081819;
	Sun, 4 May 2003 22:24:47 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Sun, 4 May 2003 22:24:47 +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 h44MOiEh081809
	for <ietf-ldapbis@openldap.org>; Sun, 4 May 2003 22:24:45 GMT
	(envelope-from mark.ennis@adacel.com)
Received: from nexus.adacel.com (Not Verified[10.32.240.1]) by adacel.com with MailMarshal (v5,0,3,91)
	id <B0000592c9>; Mon, 05 May 2003 08:22:08 +1000
Received: (qmail 4980 invoked from network); 4 May 2003 22:24:14 -0000
Received: from unknown (HELO adacel.com) (10.32.24.164)
  by nexus.adacel.com with SMTP; 4 May 2003 22:24:14 -0000
Message-ID: <3EB5930D.5000108@adacel.com>
Date: Mon, 05 May 2003 08:24:13 +1000
From: Mark Ennis <mark.ennis@adacel.com>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Roger Harrison <RHARRISON@novell.com>
CC: ietf-ldapbis@OpenLDAP.org
Subject: Re: Should response-auth be optional for digest authentication	in
 authmeth?
References: <seb2e96b.002@prv-mail20.provo.novell.com>
In-Reply-To: <seb2e96b.002@prv-mail20.provo.novell.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

My impression is that using the presences/absence of the rspauth field 
to indicate support for subsequent authentication is unnecessary as 
RFC2831 section 2.2.2 indicates an attempt to use subsequent 
authentication should be ignored by servers which do not permit it (it 
is treated as a request for authenticaion and the server response is a 
new digest-challenge).

- Mark.

Roger Harrison wrote:
> The text in draft-ietf-ldapbis-authmeth-05.txt Section 8.2 paragraph 6 
> is identical to RFC 2829 Section 6.1 paragraph 5, so this wording 
> predates the revision work being done in the ldapbis working group.
>  
> That said, here is a summary of my review of the issue:
>  
> 1. Based on the wording of RFC2831 section 2.1.3  it appears that the 
> intent was for the response-auth to always be sent.
>  
> 2. It appears that one use of the response-auth is to provide a limited 
> form of mutual authentication of the server to the client (i.e. the 
> server can at least prove that it knows the client's password, thus it 
> can be trusted).
>  
> 3. For purposes of mutual authentication, the value of the response-auth 
> is equally valuable regardless of whether the client and server support 
> subsequent authentication.
>  
> 4. The response-auth value is required to perform subsequent authentication.
>  
> 5. The only reason I can see for making the response-auth optional WRT 
> LDAP is to signal to the client whether the server supports subsequent 
> authentication.
>  
> I believe we should modify the text of authmeth-05 section 8.2 paragraph 
> 6 to always have the credentials field contain the value of 
> response-auth *if* this can be done without causing a problem for item 5 
> above (ability to signal server support for subsequent authenticaion) 
> AND also not cause interoperability problems for clients that may not be 
> expecting the value.
>  
> I'd would greatly appreciate guidance from other working group members 
> on the best course of action to take.
>  
> Thanks,
>  
> Roger
>  
> Roger G. Harrison
> Manager, eDirectory Core and Utilities
> Novell, Inc., the Leader Provider of Net Business Solutions
> www.novell.com <http://www.novell.com>
> 
>  >>> Mark Ennis <mark.ennis@adacel.com> 4/14/2003 11:48:24 PM >>>
> The current draft of authmeth (draft-ietf-ldapbis-authmeth-05.txt)
> indicates, in section 8.2 paragraph 6, that the response-auth SASL
> message is only included in the bind response for a successful bind when
> the server supports subsequent authentication. This seems counter to the
> intention of RFC2831 section 2.1.3 which indicates that the
> response-auth should always be returned.
> 
> The response-auth provides one of the security aspects documented in
> RFC2831, that of protection against "Spoofing by counterfeit servers"
> (section 3.8). RFC2617, upon which RFC2831 is based, describes this
> protection as "The optional response digest in the "response-auth"
> directive supports mutual authentication -- the server proves that it
> knows the user's secret, and with qop=auth-int also provides limited
> integrity protection of the response.". Note that response-auth is
> optional in RFC2617, but not (in my opinion) in RFC2831.
> 
> Was this diversion from the apparent intention of RFC2831 intentional
> and if so, what is the reasoning behind weakening the authentication
> procedure in this way?
> 
> Regards,
> Mark Ennis
> 
> 



From owner-ietf-ldapbis@OpenLDAP.org  Mon May  5 02:01: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 CAA14967
	for <ldapbis-archive@lists.ietf.org>; Mon, 5 May 2003 02:01:10 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4561JEl089162;
	Mon, 5 May 2003 06:02: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 h455tsRh089047;
	Mon, 5 May 2003 05:55:54 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 5 May 2003 05:55:54 +0000
Received: from prv-mail25.provo.novell.com (prv-mail25.provo.novell.com [137.65.81.121])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h455trEh089030
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 5 May 2003 05:55:53 GMT
	(envelope-from gvithalprasad@novell.com)
Received: from INET-PRV1-MTA by prv-mail25.provo.novell.com
	with Novell_GroupWise; Sun, 04 May 2003 23:55:32 -0600
Message-Id: <seb5a874.019@prv-mail25.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.0 
Date: Sun, 04 May 2003 23:55:22 -0600
From: "Vithalprasad Gaitonde" <gvithalprasad@novell.com>
To: <ietf-ldapbis@OpenLDAP.org>
Cc: "Vijay KN" <KNVIJAY@novell.com>, "Savitha R" <RSAVITHA@novell.com>
Subject: Re: result code for a deleted identity on a connection
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

"But I'm thinking RFC 2251, 4.4.1 should be clarified as well:
        - strongAuthRequired: The server has detected that an
establish
          security association between the client and server has
          unexpectedly failed or been compromised, or that the
          server now requires the client to authenticate using a
          strong(er) mechanism."
But what does strong(er) imply in the case which we are talking
about...does that mean the client has to go over TLS or use some SASL
bind and not use a clear text simple bind ?..at least that was the
conventional meaning of strongauthrequired.

Prasad


>>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 5/3/2003 4:08:01 AM >>>
At 01:59 PM 5/2/2003, Hallvard B Furuseth wrote:
>Kurt D. Zeilenga writes:
>>> We should probably have a result code like invalidIdentity which
is
>>> sent back with a notice of disconnection (section 4.4.1 protocol
draft)
>>> followed by a closing of the connection by the server.
>> 
>> RFC 2251, 4.4.1:
>>>   - strongAuthRequired: The server has detected that an
established
>>>     underlying security association protecting communication
between
>>>     the client and server has unexpectedly failed or been
compromised.
>> 
>> I think it would be reasonable to return this in this case as well.
>
>Why ask for _strong_ auth, and not just auth?

First, we've clarified the result code, in general, to mean:
>        strongAuthRequired (8)
>           Except when returned in a Notice of Disconnect (see section

>           4.4.1), this indicates that the server requires the client
to
>           authentication using a strong(er) mechanism.

But I'm thinking RFC 2251, 4.4.1 should be clarified as well:
        - strongAuthRequired: The server has detected that an
establish
          security association between the client and server has
          unexpectedly failed or been compromised, or that the
          server now requires the client to authenticate using a
          strong(er) mechanism.

That is, generalized the result code here as well.  I also
think other codes should be allowed in the Notice.  I think
it reasonable for implementations to return a variety of
other codes including busy, other, adminLimitExceeded,
unwillingToPerform, and confidentialityRequired.

Kurt 



From owner-ietf-ldapbis@OpenLDAP.org  Mon May  5 20:19: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 UAA22350
	for <ldapbis-archive@lists.ietf.org>; Mon, 5 May 2003 20:19: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 h460JPEl046272;
	Tue, 6 May 2003 00: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 h460F8DE046157;
	Tue, 6 May 2003 00:15:08 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 6 May 2003 00:15:08 +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 h460F6Eh046146
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 6 May 2003 00:15:07 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 h460F0c6002674
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 6 May 2003 00:15:02 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030505170904.02aa92c0@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Mon, 05 May 2003 17:12:25 -0700
To: ietf-ldapbis@OpenLDAP.org
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: IETF ldapbis WG Last Call:
  draft-ietf-ldapbis-user-schema-05.txt
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>

This message initiates a LDAPbis Working Group Last Call on the
document:

          LDAP: User Schema
          <draft-ietf-ldapbis-user-schema-05.txt>

The purpose of this WG Last Call it to ensure that the Working Group
has achieved consensus that the document is suitable for publication
as an IETF Draft Standard.

Please review the document for both technical and editorial problems.
Technical issues should be discussed on this list.  Editorial issues
may be sent to the document editor.

The Last Call period will end on Wednesday, May 21, 2003.

Upon completion of the last call, the WG chair(s) will take action
based upon the consensus of the WG.  Possible actions include:

  1) recommending to the IETF Application Area Directors that the
     document, after possible editorial or other minor changes, be
     considered by the IESG for publication as a Draft Standard
     (which generally involves an IETF-wide Last Call); or

  2) requiring that outstanding issues be adequately addressed prior
     to further action (including, possibly, another Last Call).

Remember that it is our responsibility as Working Group members to
ensure the quality of our documents and of the Internet Standards
process.  So, please read and comment!

 - Kurt Zeilenga
   LDAPbis co-chair 



From owner-ietf-ldapbis@OpenLDAP.org  Tue May  6 07:56: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 HAA15945
	for <ldapbis-archive@lists.ietf.org>; Tue, 6 May 2003 07:56:20 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h46BnSEr084117;
	Tue, 6 May 2003 11:54:42 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 h46BjqIT084005;
	Tue, 6 May 2003 11:45:52 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 6 May 2003 11:45:52 +0000
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h46BjnEh083975
	for <ietf-ldapbis@openldap.org>; Tue, 6 May 2003 11:45:49 GMT
	(envelope-from nsyracus@cnri.reston.va.us)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15186;
	Tue, 6 May 2003 07:41:11 -0400 (EDT)
Message-Id: <200305061141.HAA15186@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
CC: ietf-ldapbis@OpenLDAP.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-zeilenga-ldapbis-strprep-00.txt
Date: Tue, 06 May 2003 07:40:56 -0400
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>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: LDAP: Internationalized String Preparation
	Author(s)	: K. Zeilenga
	Filename	: draft-zeilenga-ldapbis-strprep-00.txt
	Pages		: 10
	Date		: 2003-5-5
	
The previous Lightweight Directory Access Protocol (LDAP) technical
specifications did not precisely define how string matching is to be
performed.  This lead to a number of usability and interoperability
problems.  This document defines string preparation algorithms for
matching rules defined for use in LDAP.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-zeilenga-ldapbis-strprep-00.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-zeilenga-ldapbis-strprep-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-zeilenga-ldapbis-strprep-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2003-5-5145755.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-zeilenga-ldapbis-strprep-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-zeilenga-ldapbis-strprep-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-5-5145755.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-ietf-ldapbis@OpenLDAP.org  Tue May  6 07:56:57 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 HAA15988
	for <ldapbis-archive@lists.ietf.org>; Tue, 6 May 2003 07:56:57 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h46BnSEp084117;
	Tue, 6 May 2003 11:54:41 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 h46BjpYw083996;
	Tue, 6 May 2003 11:45:51 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 6 May 2003 11:45:51 +0000
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h46BjnEh083976
	for <ietf-ldapbis@openldap.org>; Tue, 6 May 2003 11:45:49 GMT
	(envelope-from nsyracus@cnri.reston.va.us)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15257;
	Tue, 6 May 2003 07:41:30 -0400 (EDT)
Message-Id: <200305061141.HAA15257@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: ietf-ldapbis@OpenLDAP.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-ldapbis-dn-10.txt
Date: Tue, 06 May 2003 07:41:30 -0400
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>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the LDAP (v3) Revision Working Group of the IETF.

	Title		: LDAP:String Representation of Distinguished Names
	Author(s)	: K. Zeilenga
	Filename	: draft-ietf-ldapbis-dn-10.txt
	Pages		: 13
	Date		: 2003-5-5
	
The X.500 Directory uses distinguished names (DNs) as primary keys to
entries in the directory.  This document defines the string
representation used in the Lightweight Directory Access Protocol
(LDAP) to transfer distinguished names.  The string representation is
designed to give a clean representation of commonly used distinguished
names, while being able to represent any distinguished name.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ldapbis-dn-10.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-ldapbis-dn-10.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-ldapbis-dn-10.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2003-5-5151116.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ldapbis-dn-10.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-ldapbis-dn-10.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-5-5151116.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-ietf-ldapbis@OpenLDAP.org  Tue May  6 10:28: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 KAA24299
	for <ldapbis-archive@lists.ietf.org>; Tue, 6 May 2003 10:28: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 h46EPTEp093855;
	Tue, 6 May 2003 14:30: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 h46EPIIZ093842;
	Tue, 6 May 2003 14:25:18 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 6 May 2003 14:25:18 +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 h46EPGEh093832
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 6 May 2003 14:25:16 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 h46EPGc6009578
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 6 May 2003 14:25:16 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030506071933.02c6f6a0@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Tue, 06 May 2003 07:22:46 -0700
To: ietf-ldapbis@OpenLDAP.org
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: I-D ACTION:draft-ietf-ldapbis-dn-10.txt
In-Reply-To: <200305061141.HAA15257@ietf.org>
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>

This revision adopts the "registry approach" (from
draft-zeilenga-ldapbis-rfc2253-03) discussed previously.

Please review.

Thanks, Kurt
 
At 04:41 AM 5/6/2003, Internet-Drafts@ietf.org wrote:
>A New Internet-Draft is available from the on-line Internet-Drafts directories.
>This draft is a work item of the LDAP (v3) Revision Working Group of the IETF.
>
>        Title           : LDAP:String Representation of Distinguished Names
>        Author(s)       : K. Zeilenga
>        Filename        : draft-ietf-ldapbis-dn-10.txt
>        Pages           : 13
>        Date            : 2003-5-5
>        
>The X.500 Directory uses distinguished names (DNs) as primary keys to
>entries in the directory.  This document defines the string
>representation used in the Lightweight Directory Access Protocol
>(LDAP) to transfer distinguished names.  The string representation is
>designed to give a clean representation of commonly used distinguished
>names, while being able to represent any distinguished name.
>
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-ietf-ldapbis-dn-10.txt
>
>To remove yourself from the IETF Announcement list, send a message to 
>ietf-announce-request with the word unsubscribe in the body of the message.
>
>Internet-Drafts are also available by anonymous FTP. Login with the username
>"anonymous" and a password of your e-mail address. After logging in,
>type "cd internet-drafts" and then
>        "get draft-ietf-ldapbis-dn-10.txt".
>
>A list of Internet-Drafts directories can be found in
>http://www.ietf.org/shadow.html 
>or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>
>Internet-Drafts can also be obtained by e-mail.
>
>Send a message to:
>        mailserv@ietf.org.
>In the body type:
>        "FILE /internet-drafts/draft-ietf-ldapbis-dn-10.txt".
>        
>NOTE:   The mail server at ietf.org can return the document in
>        MIME-encoded form by using the "mpack" utility.  To use this
>        feature, insert the command "ENCODING mime" before the "FILE"
>        command.  To decode the response(s), you will need "munpack" or
>        a MIME-compliant mail reader.  Different MIME-compliant mail readers
>        exhibit different behavior, especially when dealing with
>        "multipart" MIME messages (i.e. documents which have been split
>        up into multiple messages), so check your local documentation on
>        how to manipulate these messages.
>                
>                
>Below is the data which will enable a MIME compliant mail reader
>implementation to automatically retrieve the ASCII version of the
>Internet-Draft.
>Content-Type: text/plain
>Content-ID:     <2003-5-5151116.I-D@ietf.org>
>
>ENCODING mime
>FILE /internet-drafts/draft-ietf-ldapbis-dn-10.txt
>
><ftp://ftp.ietf.org/internet-drafts/draft-ietf-ldapbis-dn-10.txt>



From owner-ietf-ldapbis@OpenLDAP.org  Tue May  6 10: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 KAA25092
	for <ldapbis-archive@lists.ietf.org>; Tue, 6 May 2003 10: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 h46EnTFP095297;
	Tue, 6 May 2003 14:58: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 h46Ebw3H094533;
	Tue, 6 May 2003 14:37:58 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 6 May 2003 14:37:58 +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 h46EbuEh094522
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 6 May 2003 14:37:56 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 h46Ebuc6009660
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 6 May 2003 14:37:56 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030506072259.02c780b8@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Tue, 06 May 2003 07:35:26 -0700
To: ietf-ldapbis@OpenLDAP.org
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: I-D ACTION:draft-zeilenga-ldapbis-strprep-00.txt
In-Reply-To: <200305061141.HAA15186@ietf.org>
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>

This I-D describes stringprep-based algorithms for
preparing strings for matching.   They are compatible
with algorithms suggested for use in X.500:  "Internationalized String Matching Rules for X.500"
  <draft-zeilenga-ldapbis-strmatch-02.txt>

I believe this I-D should become a WG I-D and become
an integral part of the LDAP Technical Specification
[Roadmap] and that the LDAP: Syntaxes and Matching
Rules [Syntaxes] I-D be updated to require textual
strings be prepared for matching according to it.

Hence, I ask for your comments on this proposal.
As I authored this I-D, I defer chair responsibilities
with regard to this proposal and this I-D to my
co-chair.

Kurt


At 04:40 AM 5/6/2003, Internet-Drafts@ietf.org wrote:
>A New Internet-Draft is available from the on-line Internet-Drafts directories.
>
>
>        Title           : LDAP: Internationalized String Preparation
>        Author(s)       : K. Zeilenga
>        Filename        : draft-zeilenga-ldapbis-strprep-00.txt
>        Pages           : 10
>        Date            : 2003-5-5
>        
>The previous Lightweight Directory Access Protocol (LDAP) technical
>specifications did not precisely define how string matching is to be
>performed.  This lead to a number of usability and interoperability
>problems.  This document defines string preparation algorithms for
>matching rules defined for use in LDAP.
>
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-zeilenga-ldapbis-strprep-00.txt
>
>To remove yourself from the IETF Announcement list, send a message to 
>ietf-announce-request with the word unsubscribe in the body of the message.
>
>Internet-Drafts are also available by anonymous FTP. Login with the username
>"anonymous" and a password of your e-mail address. After logging in,
>type "cd internet-drafts" and then
>        "get draft-zeilenga-ldapbis-strprep-00.txt".
>
>A list of Internet-Drafts directories can be found in
>http://www.ietf.org/shadow.html 
>or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>
>Internet-Drafts can also be obtained by e-mail.
>
>Send a message to:
>        mailserv@ietf.org.
>In the body type:
>        "FILE /internet-drafts/draft-zeilenga-ldapbis-strprep-00.txt".
>        
>NOTE:   The mail server at ietf.org can return the document in
>        MIME-encoded form by using the "mpack" utility.  To use this
>        feature, insert the command "ENCODING mime" before the "FILE"
>        command.  To decode the response(s), you will need "munpack" or
>        a MIME-compliant mail reader.  Different MIME-compliant mail readers
>        exhibit different behavior, especially when dealing with
>        "multipart" MIME messages (i.e. documents which have been split
>        up into multiple messages), so check your local documentation on
>        how to manipulate these messages.
>                
>                
>Below is the data which will enable a MIME compliant mail reader
>implementation to automatically retrieve the ASCII version of the
>Internet-Draft.
>Content-Type: text/plain
>Content-ID:     <2003-5-5145755.I-D@ietf.org>
>
>ENCODING mime
>FILE /internet-drafts/draft-zeilenga-ldapbis-strprep-00.txt
>
><ftp://ftp.ietf.org/internet-drafts/draft-zeilenga-ldapbis-strprep-00.txt>



From owner-ietf-ldapbis@OpenLDAP.org  Tue May  6 16:24:59 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 QAA07153
	for <ldapbis-archive@lists.ietf.org>; Tue, 6 May 2003 16:24:58 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h46KPVEn014327;
	Tue, 6 May 2003 20:26:22 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 h46KLPk8014153;
	Tue, 6 May 2003 20:21:25 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 6 May 2003 20:21:25 +0000
Received: from smtp.avinci.de (smtp.avinci.de [62.80.112.129])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h46KLNEh014118
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 6 May 2003 20:21:23 GMT
	(envelope-from norbert+lists.ietf-ldapbis@burgundy.dyndns.org)
Received: from burgundy.dyndns.org (pD9520157.dip.t-dialin.net [217.82.1.87])
	(authenticated bits=0)
	by smtp.avinci.de (8.12.7/8.12.7) with ESMTP id h46KL1DN003024
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 6 May 2003 22:21:02 +0200
Received: from localhost (localhost [127.0.0.1])
	by burgundy.dyndns.org (Postfix) with ESMTP id F0A2AC2C1
	for <ietf-ldapbis@OpenLDAP.org>; Tue,  6 May 2003 22:21:00 +0200 (CEST)
Received: from [10.10.9.3] (trex.local [10.10.9.3])
	by burgundy.dyndns.org (Postfix) with ESMTP id 8163BC25E
	for <ietf-ldapbis@OpenLDAP.org>; Tue,  6 May 2003 22:20:57 +0200 (CEST)
Date: Tue, 06 May 2003 22:21:00 +0200
From: Norbert Klasen <norbert+lists.ietf-ldapbis@burgundy.dyndns.org>
To: ietf-ldapbis@OpenLDAP.org
Subject: I-D ACTION:draft-klasen-ldap-facs-tel-number-matching-00.txt
Message-ID: <100842373.1052259660@[10.10.9.3]>
X-Mailer: Mulberry/3.0.3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by AMaViS 0.3.12pre8
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

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.


	Title	: LDAPv3: matching rules for facsimile Telephone numbers
	Author(s)	: N. Klasen
	Filename	: draft-klasen-ldap-facs-tel-number-matching-00.txt
	Pages		: 8
	Date		: 2003-5-5
	
This document defines an equality and substrings matching rule for
the Facsimile Telephone Number syntax and updates the
facsimileTelephoneNumber attribute type to use them.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-klasen-ldap-facs-tel-number-match
ing-00.txt

To remove yourself from the IETF Announcement list, send a message to
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-klasen-ldap-facs-tel-number-matching-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-klasen-ldap-facs-tel-number-matching-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

<ftp://ftp.ietf.org/internet-drafts/draft-klasen-ldap-facs-tel-number-match
ing-00.txt>


From owner-ietf-ldapbis@OpenLDAP.org  Wed May  7 00:09:40 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 AAA19850
	for <ldapbis-archive@lists.ietf.org>; Wed, 7 May 2003 00:09:40 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4747YEl033698;
	Wed, 7 May 2003 04:08:28 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 h47459NP033635;
	Wed, 7 May 2003 04:05:09 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 7 May 2003 04:05:09 +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 h47455Eh033615
	for <ietf-ldapbis@openldap.org>; Wed, 7 May 2003 04:05:07 GMT
	(envelope-from steven.legg@adacel.com.au)
Received: from nexus.adacel.com (Not Verified[10.32.240.1]) by adacel.com with MailMarshal (v5,0,3,91)
	id <B00005cd1c>; Wed, 07 May 2003 14:02:05 +1000
Received: (qmail 457 invoked from network); 7 May 2003 04:04:27 -0000
Received: from unknown (HELO osmium) (10.32.24.165)
  by nexus.adacel.com with SMTP; 7 May 2003 04:04:27 -0000
Reply-To: <steven.legg@adacel.com.au>
From: "Steven Legg" <steven.legg@adacel.com.au>
To: "'Norbert Klasen'" <norbert+lists.ietf-ldapbis@burgundy.dyndns.org>,
        <ietf-ldapbis@OpenLDAP.org>
Subject: RE: I-D ACTION:draft-klasen-ldap-facs-tel-number-matching-00.txt
Date: Wed, 7 May 2003 14:04:26 +1000
Message-ID: <004c01c3144d$c08c66d0$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
In-Reply-To: <100842373.1052259660@[10.10.9.3]>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2120.0
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



Norbert,

The matching rule definitions need correction.

The assertion syntax for facsimileNumberMatch is TelephoneNumber,
i.e. SYNTAX 1.3.6.1.4.1.1466.115.121.1.50 .
The assertion syntax for facsimileNumberSubstringsMatch is
SubstringAssertion,
i.e. SYNTAX 1.3.6.1.4.1.1466.115.121.1.58 .

Regards,
Steven

Norbert Klasen wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>
>
> 	Title	: LDAPv3: matching rules for facsimile Telephone numbers
> 	Author(s)	: N. Klasen
> 	Filename	:
> draft-klasen-ldap-facs-tel-number-matching-00.txt
> 	Pages		: 8
> 	Date		: 2003-5-5
>
> This document defines an equality and substrings matching rule for
> the Facsimile Telephone Number syntax and updates the
> facsimileTelephoneNumber attribute type to use them.



From owner-ietf-ldapbis@OpenLDAP.org  Wed May  7 01:33: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 BAA21195
	for <ldapbis-archive@lists.ietf.org>; Wed, 7 May 2003 01:33: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 h475VYEl035812;
	Wed, 7 May 2003 05:31:52 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 h475TGFF035744;
	Wed, 7 May 2003 05:29:16 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 7 May 2003 05:29:16 +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 h475TDEh035731
	for <ietf-ldapbis@openldap.org>; Wed, 7 May 2003 05:29:14 GMT
	(envelope-from mark.ennis@adacel.com)
Received: from nexus.adacel.com (Not Verified[10.32.240.1]) by adacel.com with MailMarshal (v5,0,3,91)
	id <B00005cf33>; Wed, 07 May 2003 15:26:29 +1000
Received: (qmail 13413 invoked from network); 7 May 2003 05:28:51 -0000
Received: from unknown (HELO adacel.com) (10.32.24.164)
  by nexus.adacel.com with SMTP; 7 May 2003 05:28:51 -0000
Message-ID: <3EB89991.2040202@adacel.com>
Date: Wed, 07 May 2003 15:28:49 +1000
From: Mark Ennis <mark.ennis@adacel.com>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf-ldapbis@OpenLDAP.org
Subject: Issues with current authmeth draft.
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

Following are some issues I encountered with the current authmeth draft 
(draft-ietf-ldapbis-authmeth-05.txt).

1) The phrase "inside an OCTET STRING wrapper" is ambiguous.

This phrase is from a sentence in the fourth paragraph of section 4.3:
"The credentials field contains the arbitrary data used for 
authentication, inside an OCTET STRING wrapper." It appears to be 
transcribed from RFC2251.

This phrase could arguably be interpreted to mean either:
i) The SASL credentials are arbitrary data stored in the 
SaslCrentials.credentials OCTET STRING field, or
ii) The SASL credentials are arbitrary data in a BER encoded OCTET 
STRING in the SaslCredentials.credentials OCTET STRING field, i.e. the 
SaslCredentials.credentials contains BER.

Although I interpret the intention to be i), I find the wording 
ambiguous and think it should be fixed, probably by simply removing this 
phrase from the sentence.

2) DIGEST-MD5 authentication identity

There does not appear to be a clear statement as to the form of the 
authentication identity (as opposed to authorization identity) to be 
provided in the username-value of the SASL credentials for DIGEST-MD5 
(or other mechanisms). I have seen examples of this value being an 
arbitrary identifier such as a Unix system might use, a LDAPDN and an 
*authzid*-style production.

3) Section 4.3.3 *Other SASL Mechanisms*

This section states "Other SASL mechanisms may be used with LDAP, but 
their usage is not considered in this document.", however, the 
DIGEST-MD5 mechanism has not been referenced in section 4.3 and yet, 
contrary to this statement, is considered later in the document.

- Mark Ennis.



From owner-ietf-ldapbis@OpenLDAP.org  Thu May  8 09:35: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 JAA22190
	for <ldapbis-archive@lists.ietf.org>; Thu, 8 May 2003 09:35:03 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h48DZsEn027803;
	Thu, 8 May 2003 13:36:27 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 h48DOOHS027281;
	Thu, 8 May 2003 13:24:24 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 8 May 2003 13:24:24 +0000
Received: from pat.uio.no (pat.uio.no [129.240.130.16])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h48DOLEh027266
	for <ietf-ldapbis@openldap.org>; Thu, 8 May 2003 13:24:22 GMT
	(envelope-from hbf@bombur.uio.no)
Received: from goggins.uio.no ([129.240.201.2])
	by pat.uio.no with esmtp (Exim 2.12 #7)
	id 19DlNc-00043j-00; Thu, 8 May 2003 15:24:12 +0200
Received: from bombur.uio.no ([129.240.186.42])
	by goggins.uio.no with esmtp (Exim 2.12 #7)
	id 19DlNM-0000ad-00; Thu, 8 May 2003 15:23:56 +0200
Received: from hbf by bombur.uio.no with local (Exim 2.12 #7)
	id 19DlNL-0005MT-00; Thu, 8 May 2003 15:23:55 +0200
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Message-Id: <HBF.20030508tjt0@bombur.uio.no>
To: <steven.legg@adacel.com.au>
Cc: "'Norbert Klasen'" <norbert+lists.ietf-ldapbis@burgundy.dyndns.org>,
        <ietf-ldapbis@OpenLDAP.org>
Subject: RE: I-D ACTION:draft-klasen-ldap-facs-tel-number-matching-00.txt
In-Reply-To: <004c01c3144d$c08c66d0$a518200a@osmium.mtwav.adacel.com.au>
References: <100842373.1052259660@[10.10.9.3]>
	<004c01c3144d$c08c66d0$a518200a@osmium.mtwav.adacel.com.au>
X-Mailer: VM 6.37 under Emacs 19.34.1
Date: Thu, 8 May 2003 15:23:55 +0200
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>

Steven Legg writes:
> 
> The assertion syntax for facsimileNumberMatch is TelephoneNumber,
> i.e. SYNTAX 1.3.6.1.4.1.1466.115.121.1.50 .
> The assertion syntax for facsimileNumberSubstringsMatch is
> SubstringAssertion,
> i.e. SYNTAX 1.3.6.1.4.1.1466.115.121.1.58 .

The '$' separators in fax-numbers are just treated as plain characters
when matching?

-- 
Hallvard


From owner-ietf-ldapbis@OpenLDAP.org  Thu May  8 12:32: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 MAA29110
	for <ldapbis-archive@lists.ietf.org>; Thu, 8 May 2003 12:32:12 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h48GPkFZ042041;
	Thu, 8 May 2003 16:34: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 h48G7NLA036267;
	Thu, 8 May 2003 16:07:23 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 8 May 2003 16:07:23 +0000
Received: from pat.uio.no (pat.uio.no [129.240.130.16])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h48G7FEh036237
	for <ietf-ldapbis@openldap.org>; Thu, 8 May 2003 16:07:15 GMT
	(envelope-from hbf@bombur.uio.no)
Received: from mons.uio.no ([129.240.130.14])
	by pat.uio.no with esmtp (Exim 2.12 #7)
	id 19DnvK-0005Op-00; Thu, 8 May 2003 18:07:10 +0200
Received: from bombur.uio.no ([129.240.186.42])
	by mons.uio.no with esmtp (Exim 2.12 #7)
	id 19DnvI-0005Nh-00; Thu, 8 May 2003 18:07:08 +0200
Received: from hbf by bombur.uio.no with local (Exim 2.12 #7)
	id 19DnvD-0005ki-00; Thu, 8 May 2003 18:07:03 +0200
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Message-Id: <HBF.20030508qtmo@bombur.uio.no>
To: steven.legg@adacel.com.au
Cc: Norbert Klasen <norbert+lists.ietf-ldapbis@burgundy.dyndns.org>,
        <ietf-ldapbis@OpenLDAP.org>
Subject: RE: I-D ACTION:draft-klasen-ldap-facs-tel-number-matching-00.txt
In-Reply-To: <HBF.20030508tjt0@bombur.uio.no>
References: <100842373.1052259660@[10.10.9.3]>
	<004c01c3144d$c08c66d0$a518200a@osmium.mtwav.adacel.com.au>
	<HBF.20030508tjt0@bombur.uio.no>
X-Mailer: VM 6.37 under Emacs 19.34.1
Date: Thu, 8 May 2003 18:07:03 +0200
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 wrote:
>Steven Legg writes:
>> 
>> The assertion syntax for facsimileNumberMatch is TelephoneNumber,
>> i.e. SYNTAX 1.3.6.1.4.1.1466.115.121.1.50 .
>> The assertion syntax for facsimileNumberSubstringsMatch is
>> SubstringAssertion,
>> i.e. SYNTAX 1.3.6.1.4.1.1466.115.121.1.58 .
> 
> The '$' separators in fax-numbers are just treated as plain characters
> when matching?

Hold on.  According to the Syntaxes draft, TelephoneNumber is a
PrintableString, and PrintableString doesn't allow '$'.  Me not
understand...

-- 
Hallvard


From owner-ietf-ldapbis@OpenLDAP.org  Thu May  8 15:19:22 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 PAA05504
	for <ldapbis-archive@lists.ietf.org>; Thu, 8 May 2003 15:19:22 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h48JJkEl057941;
	Thu, 8 May 2003 19:20:33 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 h48JJRQJ057901;
	Thu, 8 May 2003 19:19:27 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 8 May 2003 19:19:27 +0000
Received: from smtp.avinci.de (smtp.avinci.de [62.80.112.129])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h48JJLEh057871
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 8 May 2003 19:19:22 GMT
	(envelope-from norbert+lists.ietf-ldapbis@burgundy.dyndns.org)
Received: from burgundy.dyndns.org (pD9520A18.dip.t-dialin.net [217.82.10.24])
	(authenticated bits=0)
	by smtp.avinci.de (8.12.7/8.12.7) with ESMTP id h48JIhDN013443;
	Thu, 8 May 2003 21:18:48 +0200
Received: from localhost (localhost [127.0.0.1])
	by burgundy.dyndns.org (Postfix) with ESMTP
	id 83FD8C2C1; Thu,  8 May 2003 21:18:42 +0200 (CEST)
Received: from [10.10.9.3] (trex.local [10.10.9.3])
	by burgundy.dyndns.org (Postfix) with ESMTP
	id E74C3C188; Thu,  8 May 2003 21:18:38 +0200 (CEST)
Date: Thu, 08 May 2003 21:18:45 +0200
From: Norbert Klasen <norbert+lists.ietf-ldapbis@burgundy.dyndns.org>
To: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>, steven.legg@adacel.com.au
Cc: ietf-ldapbis@OpenLDAP.org
Subject: RE: I-D ACTION:draft-klasen-ldap-facs-tel-number-matching-00.txt
Message-ID: <99690917.1052428725@[10.10.9.3]>
In-Reply-To: <HBF.20030508qtmo@bombur.uio.no>
References: <100842373.1052259660@[10.10.9.3]>
 	<004c01c3144d$c08c66d0$a518200a@osmium.mtwav.adacel.com.au>
 	<HBF.20030508tjt0@bombur.uio.no> <HBF.20030508qtmo@bombur.uio.no>
X-Mailer: Mulberry/3.0.3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by AMaViS 0.3.12pre8
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

Hallavard,

--On Donnerstag, 8. Mai 2003 18:07 +0200 Hallvard B Furuseth 
<h.b.furuseth@usit.uio.no> wrote:

> I wrote:
>> Steven Legg writes:
>>>
>>> The assertion syntax for facsimileNumberMatch is TelephoneNumber,
>>> i.e. SYNTAX 1.3.6.1.4.1.1466.115.121.1.50 .
>>> The assertion syntax for facsimileNumberSubstringsMatch is
>>> SubstringAssertion,
>>> i.e. SYNTAX 1.3.6.1.4.1.1466.115.121.1.58 .
>>
>> The '$' separators in fax-numbers are just treated as plain characters
>> when matching?

The point is that these matching rules only act on the telephone number 
part of a Facsimile Telephone Number. So only characters before the first 
'$' are taken into account when matching. That is why the ASSERTION syntax 
is TelephoneNumber.

> Hold on.  According to the Syntaxes draft, TelephoneNumber is a
> PrintableString, and PrintableString doesn't allow '$'.  Me not
> understand...

Take as example the following entry:
dn: o=avinci
objectclass: organization
o: avinci
facsimileTelephoneNumber: +49 2102 124 555 $fineResolution$a3Width

Now, searching for "facsimileTelephoneNumber=+49-2102-124-555" would match 
this entry, as
- only the telephone-number part, ie. "+49 2102 124 555 " of the attribute 
value is taken into account
- and the assertion value "+49-2102-124-555" matches the attribute value
  "+49 2102 124 555 " by the telephone number matching rule, ie. ignoring
  the case of letters, and ignoring    space and `-' characters.

I think adding this example and a copy of the ABNF from the definition of 
the Facsimile Telephone Number syntax to the draft should make things a lot 
clearer.

Norbert


From owner-ietf-ldapbis@OpenLDAP.org  Fri May  9 20:17:00 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 UAA07957
	for <ldapbis-archive@lists.ietf.org>; Fri, 9 May 2003 20:16:59 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4A0DuEl051546;
	Sat, 10 May 2003 00:18:36 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 h4A0D1Q3051510;
	Sat, 10 May 2003 00:13:01 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Sat, 10 May 2003 00:13:01 +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 h4A0CxEh051496
	for <ietf-ldapbis@OpenLDAP.org>; Sat, 10 May 2003 00:12:59 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 h4A0C8c6046924;
	Sat, 10 May 2003 00:12:25 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030509170436.01a4ae38@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Fri, 09 May 2003 17:09:31 -0700
To: "Roger Harrison" <RHARRISON@novell.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: Should response-auth be optional for digest authentication
  in authmeth?
Cc: <mark.ennis@adacel.com>, <ietf-ldapbis@OpenLDAP.org>
In-Reply-To: <seb2e96b.002@prv-mail20.provo.novell.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 08:52 PM 5/2/2003, Roger Harrison wrote:
>I believe we should modify the text of authmeth-05 section 8.2 paragraph 6 to always have the credentials field contain the value of response-auth *if* this can be done without causing a problem for item 5 above (ability to signal server support for subsequent authenticaion) AND also not cause interoperability problems for clients that may not be expecting the value.

I believe this modification is quite appropriate.
RFC 2831 is correct here, we need to align to it
(actually to draft-ietf-sasl-rfc2831bis).

If anyone things RFC 2831 is incorrect here then they
should take the issue up with the SASL WG.

Kurt



From owner-ietf-ldapbis@OpenLDAP.org  Fri May  9 20:28: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 UAA08135
	for <ldapbis-archive@lists.ietf.org>; Fri, 9 May 2003 20:28:22 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4A0PuEp052042;
	Sat, 10 May 2003 00:30:06 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 h4A0LkO3051907;
	Sat, 10 May 2003 00:21:46 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Sat, 10 May 2003 00:21:46 +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 h4A0LhEh051897
	for <ietf-ldapbis@OpenLDAP.org>; Sat, 10 May 2003 00:21:45 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 h4A0Lec6046975;
	Sat, 10 May 2003 00:21:40 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030509170956.023c44d8@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Fri, 09 May 2003 17:19:07 -0700
To: Mark Ennis <mark.ennis@adacel.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: Issues with current authmeth draft.
Cc: ietf-ldapbis@OpenLDAP.org
In-Reply-To: <3EB89991.2040202@adacel.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 10:28 PM 5/6/2003, Mark Ennis wrote:
>Following are some issues I encountered with the current authmeth draft (draft-ietf-ldapbis-authmeth-05.txt).
>
>1) The phrase "inside an OCTET STRING wrapper" is ambiguous.
>
>This phrase is from a sentence in the fourth paragraph of section 4.3:
>"The credentials field contains the arbitrary data used for authentication, inside an OCTET STRING wrapper." It appears to be transcribed from RFC2251.

This should be:
        The credentials field, an OCTET STRING, contains the arbitrary
        data used for authentication.

>2) DIGEST-MD5 authentication identity
>
>There does not appear to be a clear statement as to the form of the authentication identity (as opposed to authorization identity) to be provided in the username-value of the SASL credentials for DIGEST-MD5 (or other mechanisms).

RFC 2831 says its a user name.  That is, it's not a LDAPDN, not
an authzid, not a domain name, not a ....

>3) Section 4.3.3 *Other SASL Mechanisms*
>
>This section states "Other SASL mechanisms may be used with LDAP, but their usage is not considered in this document.", however, the DIGEST-MD5 mechanism has not been referenced in section 4.3 and yet, contrary to this statement, is considered later in the document.

I note as well that the ANONYMOUS/PLAIN section (4.2) should
be deleted.  ANONYMOUS and PLAIN, like in other mechanism,
can be used in LDAP if a) supported and b) enabled.  I note
that they each offer capabilities not found in their simple
bind equivalents (and hence are used in some deployments).
For example, PLAIN (over TLS) is quite useful when interacting
with legacy authentication subsystems. 



From owner-ietf-ldapbis@OpenLDAP.org  Fri May  9 20:28:24 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 UAA08150
	for <ldapbis-archive@lists.ietf.org>; Fri, 9 May 2003 20:28:23 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4A0PuEr052042;
	Sat, 10 May 2003 00:30:06 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 h4A0OVp2051988;
	Sat, 10 May 2003 00:24:31 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Sat, 10 May 2003 00:24:31 +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 h4A0OUEh051978
	for <ietf-ldapbis@OpenLDAP.org>; Sat, 10 May 2003 00:24:30 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 h4A0ORc6046980;
	Sat, 10 May 2003 00:24:28 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030509171928.023ab700@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Fri, 09 May 2003 17:21:55 -0700
To: "Vithalprasad Gaitonde" <gvithalprasad@novell.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: result code for a deleted identity on a connection
Cc: <ietf-ldapbis@OpenLDAP.org>, "Vijay KN" <KNVIJAY@novell.com>,
        "Savitha R" <RSAVITHA@novell.com>
In-Reply-To: <seb5a874.019@prv-mail25.provo.novell.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 10:55 PM 5/4/2003, Vithalprasad Gaitonde wrote:
>"But I'm thinking RFC 2251, 4.4.1 should be clarified as well:
>        - strongAuthRequired: The server has detected that an
>establish
>          security association between the client and server has
>          unexpectedly failed or been compromised, or that the
>          server now requires the client to authenticate using a
>          strong(er) mechanism."
>But what does strong(er) imply in the case which we are talking
>about...

In this case, it's the former part of the description which applies.
That is, the code indicates that a security association has failed.

>does that mean the client has to go over TLS or use some SASL
>bind and not use a clear text simple bind ?

It means either a security association has failed or the
better mechanisms are needed.

>.at least that was the
>conventional meaning of strongauthrequired.
>
>Prasad
>
>
>>>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 5/3/2003 4:08:01 AM >>>
>At 01:59 PM 5/2/2003, Hallvard B Furuseth wrote:
>>Kurt D. Zeilenga writes:
>>>> We should probably have a result code like invalidIdentity which
>is
>>>> sent back with a notice of disconnection (section 4.4.1 protocol
>draft)
>>>> followed by a closing of the connection by the server.
>>> 
>>> RFC 2251, 4.4.1:
>>>>   - strongAuthRequired: The server has detected that an
>established
>>>>     underlying security association protecting communication
>between
>>>>     the client and server has unexpectedly failed or been
>compromised.
>>> 
>>> I think it would be reasonable to return this in this case as well.
>>
>>Why ask for _strong_ auth, and not just auth?
>
>First, we've clarified the result code, in general, to mean:
>>        strongAuthRequired (8)
>>           Except when returned in a Notice of Disconnect (see section
>
>>           4.4.1), this indicates that the server requires the client
>to
>>           authentication using a strong(er) mechanism.
>
>But I'm thinking RFC 2251, 4.4.1 should be clarified as well:
>        - strongAuthRequired: The server has detected that an
>establish
>          security association between the client and server has
>          unexpectedly failed or been compromised, or that the
>          server now requires the client to authenticate using a
>          strong(er) mechanism.
>
>That is, generalized the result code here as well.  I also
>think other codes should be allowed in the Notice.  I think
>it reasonable for implementations to return a variety of
>other codes including busy, other, adminLimitExceeded,
>unwillingToPerform, and confidentialityRequired.
>
>Kurt 



From owner-ietf-ldapbis@OpenLDAP.org  Sun May 11 11:07:38 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 LAA06037
	for <ldapbis-archive@lists.ietf.org>; Sun, 11 May 2003 11:07: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 h4BF89El024553;
	Sun, 11 May 2003 15:09: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 h4BF55vm024489;
	Sun, 11 May 2003 15:05:05 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Sun, 11 May 2003 15:05:05 +0000
Received: from boole.openldap.org (kurt@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4BF54Eh024478
	for <ietf-ldapbis@openldap.org>; Sun, 11 May 2003 15:05:04 GMT
	(envelope-from kurt@boole.openldap.org)
Received: (from kurt@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) id h4BF54Sf024477
	for ietf-ldapbis@openldap.org; Sun, 11 May 2003 15:05:04 GMT
	(envelope-from kurt)
Received: from mpls-qmqp-01.inet.qwest.net (mpls-qmqp-01.inet.qwest.net [63.231.195.112])
	by boole.openldap.org (8.12.9/8.12.9) with SMTP id h4B5L0Eh005464
	for <ietf-ldapbis@openldap.org>; Sun, 11 May 2003 05:21:00 GMT
	(envelope-from hoytkesterson@earthlink.net)
Received: (qmail 51511 invoked by uid 0); 11 May 2003 05:20:59 -0000
Received: from unknown (63.231.195.13)
  by mpls-qmqp-01.inet.qwest.net with QMQP; 11 May 2003 05:20:59 -0000
Received: from vdsl-130-13-127-251.phnx.uswest.net (HELO ?192.168.2.7?) (130.13.127.251)
  by mpls-pop-13.inet.qwest.net with SMTP; 11 May 2003 05:20:59 -0000
Date: Sat, 10 May 2003 22:20:48 -0700
Message-Id: <a0521060cbae38c677827@[192.168.2.7]>
From: "Hoyt L. Kesterson II" <hoytkesterson@earthlink.net>
To: "OSI Directory List" <OSIdirectory@az05.bull.com>,
        ietf-ldapbis@OpenLDAP.org
Mime-Version: 1.0
X-Sender: hoytkesterson@earthlink.net@mail.earthlink.net
Subject: PDAM on X.500 and LDAP alignment is on the server
Content-Type: text/html; 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>

<!doctype html public "-//W3C//DTD W3 HTML//EN">
ISO JTC1 SC6 has just initiated a ballot on the Proposed Draft Amendment (PDAM) on X.500 and LDAP alignment. The PDAM can be found in PDF and Word format at

   ftp://ftp.bull.com/pub/OSIdirectory/London2003Output/6N12465LDAPAlignmentPDAM.pdf

   ftp://ftp.bull.com/pub/OSIdirectory/London2003Output/6N12465LDAPAlignmentPDAM.doc

The ballot will close on 9 August 2003 but the secretariat has stated that she will accept comments until 20 August. Comments received on this document will be addressed at an editing meeting in Geneva 11 - 17 September 2001.

   hoyt


From owner-ietf-ldapbis@OpenLDAP.org  Sun May 11 18:55: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 SAA15126
	for <ldapbis-archive@lists.ietf.org>; Sun, 11 May 2003 18:55: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 h4BMuBEl031794;
	Sun, 11 May 2003 22:57: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 h4BMpYUl031709;
	Sun, 11 May 2003 22:51:34 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Sun, 11 May 2003 22:51: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 h4BMpVEh031682
	for <ietf-ldapbis@openldap.org>; Sun, 11 May 2003 22:51:32 GMT
	(envelope-from mark.ennis@adacel.com)
Received: from nexus.adacel.com (Not Verified[10.32.240.1]) by adacel.com with MailMarshal (v5,0,3,91)
	id <B000062970>; Mon, 12 May 2003 08:48:12 +1000
Received: (qmail 23152 invoked from network); 11 May 2003 22:51:09 -0000
Received: from unknown (HELO adacel.com) (10.32.24.164)
  by nexus.adacel.com with SMTP; 11 May 2003 22:51:09 -0000
Message-ID: <3EBED3DD.6070104@adacel.com>
Date: Mon, 12 May 2003 08:51:09 +1000
From: Mark Ennis <mark.ennis@adacel.com>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
CC: ietf-ldapbis@OpenLDAP.org
Subject: Re: Issues with current authmeth draft.
References: <5.2.0.9.0.20030509170956.023c44d8@127.0.0.1>
In-Reply-To: <5.2.0.9.0.20030509170956.023c44d8@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 10:28 PM 5/6/2003, Mark Ennis wrote:
> 
>>2) DIGEST-MD5 authentication identity
>>
>>There does not appear to be a clear statement as to the form of the authentication identity (as opposed to authorization identity) to be provided in the username-value of the SASL credentials for DIGEST-MD5 (or other mechanisms).
> 
> 
> RFC 2831 says its a user name.  That is, it's not a LDAPDN, not
> an authzid, not a domain name, not a ....
> 

On the other hand, RFC2831 does not specify the authzid field in the 
SASL parameters should use the authzid syntax defined in RFC2829 either. 
It does, however, define the username SASL parameter as
      "The user's name in the specified realm, encoded according to the
       value of the "charset" directive. This directive is required and
       MUST be present exactly once; otherwise, authentication fails."

I suggest this supports the potential to use LDAPDN which is the closest 
thing to a username within LDAP that is required by the LDAP 
specifications. After all, the "user's name" in LDAP is the LDAPDN of 
the user's entry.

Furthermore, [authmeth] has the statement:
   "Clients sending a bind request with the sasl choice selected SHOULD
    NOT send a value in the name field. Servers receiving a bind request
    with the sasl choice selected SHALL ignore any value in the name
    field. "
in *4.3 SASL Authentication* which appears to prohibits the use of the 
BindRequest name field to establish the authentication identity. Without 
this or the  SASL username providing a LDAPDN, how should the 
authentication credentials be determined?

- Mark.



From owner-ietf-ldapbis@OpenLDAP.org  Sun May 11 19:30: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 TAA15463
	for <ldapbis-archive@lists.ietf.org>; Sun, 11 May 2003 19:30:22 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4BNWBEl032320;
	Sun, 11 May 2003 23:32:22 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 h4BNRI5r032233;
	Sun, 11 May 2003 23:27:18 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Sun, 11 May 2003 23:27:18 +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 h4BNRGEh032222
	for <ietf-ldapbis@OpenLDAP.org>; Sun, 11 May 2003 23:27:16 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 h4BNRBc6063791;
	Sun, 11 May 2003 23:27:12 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030511160317.02c61500@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Sun, 11 May 2003 16:24:26 -0700
To: Mark Ennis <mark.ennis@adacel.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: Issues with current authmeth draft.
Cc: ietf-ldapbis@OpenLDAP.org
In-Reply-To: <3EBED3DD.6070104@adacel.com>
References: <5.2.0.9.0.20030509170956.023c44d8@127.0.0.1>
 <5.2.0.9.0.20030509170956.023c44d8@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 03:51 PM 5/11/2003, Mark Ennis wrote:
>Kurt D. Zeilenga wrote:
>>At 10:28 PM 5/6/2003, Mark Ennis wrote:
>>
>>>2) DIGEST-MD5 authentication identity
>>>
>>>There does not appear to be a clear statement as to the form of the authentication identity (as opposed to authorization identity) to be provided in the username-value of the SASL credentials for DIGEST-MD5 (or other mechanisms).
>>
>>RFC 2831 says its a user name.  That is, it's not a LDAPDN, not
>>an authzid, not a domain name, not a ....
>
>On the other hand, RFC2831 does not specify the authzid field in the SASL parameters should use the authzid syntax defined in RFC2829 either.

RFC 2222 says the form of the (proxy) authorization identity
is application protocol specific.

>It does, however, define the username SASL parameter as
>     "The user's name in the specified realm, encoded according to the
>      value of the "charset" directive. This directive is required and
>      MUST be present exactly once; otherwise, authentication fails."

I think this is an issue which already came up in the SASL WG.

>I suggest this supports the potential to use LDAPDN

I don't believe it supports any such thing.

>which is the closest thing to a username within LDAP that is required by the LDAP specifications.

I don't think the LDAP specifications require a DN for authentication
proposes.  If one considers EXTERNAL, the underlying authentication
identity can be anything.  Likewise, any SASL mechanism can be used.
Here the form of the authentication identity is mechanism specific.

Regardless of the mechanism, it is the server's responsibility to
derive an appropriate authorization identity from the authentication
identity associated with the credentials.  And if a (proxy) authorization
identity is asserted, make sure the identity associated with the
credentials is authorized to assume that asserted (proxy)
authorization identity and, as appropriate, derive an identity
representation suitable for application of access control and other
administrative policies.

>After all, the "user's name" in LDAP is the LDAPDN of the user's entry.

Not necessarily.  There may be no LDAPDN associated with the user
and, even if so, it may not refer to an entry.

>Furthermore, [authmeth] has the statement:
>  "Clients sending a bind request with the sasl choice selected SHOULD
>   NOT send a value in the name field. Servers receiving a bind request
>   with the sasl choice selected SHALL ignore any value in the name
>   field. "
>in *4.3 SASL Authentication* which appears to prohibits the use of the BindRequest name field to establish the authentication identity.
>Without this or the  SASL username providing a LDAPDN, how should the authentication credentials be determined?

A local matter.  That is, how identities of different forms (or
of the same form used in different contexts) relate to each other is
a local matter.  How and where credentials are stored is a local
matter.  Which identities may assume (proxy for) other identities is
also a local matter.  And the form of identity used in access control
systems is local matter.

It's certainly a matter which the client should not concern itself
with...

Kurt 



From owner-ietf-ldapbis@OpenLDAP.org  Mon May 12 01:13: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 BAA19808
	for <ldapbis-archive@lists.ietf.org>; Mon, 12 May 2003 01:13:11 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4C5EDEl039111;
	Mon, 12 May 2003 05:14: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 h4C59S4n038983;
	Mon, 12 May 2003 05:09:28 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 12 May 2003 05:09:28 +0000
Received: from ausyms50.ca.com ([155.35.248.106])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4C59NEh038944;
	Mon, 12 May 2003 05:09:24 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, 12 May 2003 15:09:01 +1000
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: Issues with current authmeth draft.
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
Date: Mon, 12 May 2003 15:09:02 +1000
Message-ID: <1395B4B334FCC143B36AF788E68B63810EC3C3@ausyms21.ca.com>
Thread-Topic: Issues with current authmeth draft.
Thread-Index: AcMYFZs4d2WCZBDtSTuNCv9av+CiugALlZ8Q
From: "Ramsay, Ron" <Ron.Ramsay@ca.com>
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>,
        "Mark Ennis" <mark.ennis@adacel.com>
Cc: <ietf-ldapbis@OpenLDAP.org>
X-OriginalArrivalTime: 12 May 2003 05:09:01.0913 (UTC) FILETIME=[9A1FE490:01C31844]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by boole.openldap.org id h4C59OEh038950
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 find this a bit hard to deal with. We are authenticating to a directory, aren't we? I remember quite an extensive discussion once about how the user name in the simple bind alternative related to a user entry. At that time it was pointed out the X.500 requires it to be the 'distinguished' name of an entry. This actually precludes there being no entry and also precludes the name being an alias.

Has LDAP jettisoned the X.500 model?

So, I'm finding it difficult, Kurt, following the non-directory approach you are following in directory authentication.

In short, I oppose it.

Ron.

-----Original Message-----
From: Kurt D. Zeilenga [mailto:Kurt@OpenLDAP.org]
Sent: Monday, 12 May 2003 09:24
To: Mark Ennis
Cc: ietf-ldapbis@OpenLDAP.org
Subject: Re: Issues with current authmeth draft.


At 03:51 PM 5/11/2003, Mark Ennis wrote:
>Kurt D. Zeilenga wrote:
>>At 10:28 PM 5/6/2003, Mark Ennis wrote:
>>
>>>2) DIGEST-MD5 authentication identity
>>>
>>>There does not appear to be a clear statement as to the form of the authentication identity (as opposed to authorization identity) to be provided in the username-value of the SASL credentials for DIGEST-MD5 (or other mechanisms).
>>
>>RFC 2831 says its a user name.  That is, it's not a LDAPDN, not
>>an authzid, not a domain name, not a ....
>
>On the other hand, RFC2831 does not specify the authzid field in the SASL parameters should use the authzid syntax defined in RFC2829 either.

RFC 2222 says the form of the (proxy) authorization identity
is application protocol specific.

>It does, however, define the username SASL parameter as
>     "The user's name in the specified realm, encoded according to the
>      value of the "charset" directive. This directive is required and
>      MUST be present exactly once; otherwise, authentication fails."

I think this is an issue which already came up in the SASL WG.

>I suggest this supports the potential to use LDAPDN

I don't believe it supports any such thing.

>which is the closest thing to a username within LDAP that is required by the LDAP specifications.

I don't think the LDAP specifications require a DN for authentication
proposes.  If one considers EXTERNAL, the underlying authentication
identity can be anything.  Likewise, any SASL mechanism can be used.
Here the form of the authentication identity is mechanism specific.

Regardless of the mechanism, it is the server's responsibility to
derive an appropriate authorization identity from the authentication
identity associated with the credentials.  And if a (proxy) authorization
identity is asserted, make sure the identity associated with the
credentials is authorized to assume that asserted (proxy)
authorization identity and, as appropriate, derive an identity
representation suitable for application of access control and other
administrative policies.

>After all, the "user's name" in LDAP is the LDAPDN of the user's entry.

Not necessarily.  There may be no LDAPDN associated with the user
and, even if so, it may not refer to an entry.

>Furthermore, [authmeth] has the statement:
>  "Clients sending a bind request with the sasl choice selected SHOULD
>   NOT send a value in the name field. Servers receiving a bind request
>   with the sasl choice selected SHALL ignore any value in the name
>   field. "
>in *4.3 SASL Authentication* which appears to prohibits the use of the BindRequest name field to establish the authentication identity.
>Without this or the  SASL username providing a LDAPDN, how should the authentication credentials be determined?

A local matter.  That is, how identities of different forms (or
of the same form used in different contexts) relate to each other is
a local matter.  How and where credentials are stored is a local
matter.  Which identities may assume (proxy for) other identities is
also a local matter.  And the form of identity used in access control
systems is local matter.

It's certainly a matter which the client should not concern itself
with...

Kurt 





From owner-ietf-ldapbis@OpenLDAP.org  Mon May 12 02:06: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 CAA27139
	for <ldapbis-archive@lists.ietf.org>; Mon, 12 May 2003 02:06:28 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4C68DEl040243;
	Mon, 12 May 2003 06:08: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 h4C66ZSb040227;
	Mon, 12 May 2003 06:06:35 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 12 May 2003 06:06:35 +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 h4C66XEh040217
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 12 May 2003 06:06:34 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 h4C66Rc6066730;
	Mon, 12 May 2003 06:06:27 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030511223216.028294a8@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Sun, 11 May 2003 23:03:52 -0700
To: "Ramsay, Ron" <Ron.Ramsay@ca.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: RE: Issues with current authmeth draft.
Cc: "Mark Ennis" <mark.ennis@adacel.com>, <ietf-ldapbis@OpenLDAP.org>
In-Reply-To: <1395B4B334FCC143B36AF788E68B63810EC3C3@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 10:09 PM 5/11/2003, Ramsay, Ron wrote:
>I find this a bit hard to deal with. We are authenticating to a directory, aren't we? I remember quite an extensive discussion once about how the user name in the simple bind alternative related to a user entry. At that time it was pointed out the X.500 requires it to be the 'distinguished' name of an entry. This actually precludes there being no entry and also precludes the name being an alias.

I note that your points are made with respect to simple method
while my points were made with respect to the SASL method.

>Has LDAP jettisoned the X.500 model?

I would say no.  LDAP supports, in addition to X.500-based
mechanisms, many mechanisms which are not specific to X.500
nor LDAP, such as DIGEST-MD5.

Kurt



From owner-ietf-ldapbis@OpenLDAP.org  Mon May 12 03:25: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 DAA04081
	for <ldapbis-archive@lists.ietf.org>; Mon, 12 May 2003 03:25:40 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4C7QEEl042295;
	Mon, 12 May 2003 07:26:33 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 h4C7PqO6042263;
	Mon, 12 May 2003 07:25:52 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 12 May 2003 07:25:52 +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 h4C7PnEh042237
	for <ietf-ldapbis@openldap.org>; Mon, 12 May 2003 07:25:50 GMT
	(envelope-from mark.ennis@adacel.com)
Received: from nexus.adacel.com (Not Verified[10.32.240.1]) by adacel.com with MailMarshal (v5,0,3,91)
	id <B00006379a>; Mon, 12 May 2003 17:22:28 +1000
Received: (qmail 4482 invoked from network); 12 May 2003 07:25:27 -0000
Received: from unknown (HELO adacel.com) (10.32.24.164)
  by nexus.adacel.com with SMTP; 12 May 2003 07:25:27 -0000
Message-ID: <3EBF4C65.7050900@adacel.com>
Date: Mon, 12 May 2003 17:25:25 +1000
From: Mark Ennis <mark.ennis@adacel.com>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
CC: ietf-ldapbis@OpenLDAP.org
Subject: Re: Issues with current authmeth draft.
References: <5.2.0.9.0.20030509170956.023c44d8@127.0.0.1> <5.2.0.9.0.20030509170956.023c44d8@127.0.0.1> <5.2.0.9.0.20030511160317.02c61500@127.0.0.1>
In-Reply-To: <5.2.0.9.0.20030511160317.02c61500@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 03:51 PM 5/11/2003, Mark Ennis wrote:
> 
>>Kurt D. Zeilenga wrote:
>>
>>>At 10:28 PM 5/6/2003, Mark Ennis wrote:
>>>
>>>
>>>>2) DIGEST-MD5 authentication identity
>>>>
>>>>There does not appear to be a clear statement as to the form of the authentication identity (as opposed to authorization identity) to be provided in the username-value of the SASL credentials for DIGEST-MD5 (or other mechanisms).
>>>
>>>RFC 2831 says its a user name.  That is, it's not a LDAPDN, not
>>>an authzid, not a domain name, not a ....
>>
>>On the other hand, RFC2831 does not specify the authzid field in the SASL parameters should use the authzid syntax defined in RFC2829 either.
> 
> 
> RFC 2222 says the form of the (proxy) authorization identity
> is application protocol specific.
> 
So? I am not questioning the appropriateness of [authmeth] defining the 
authzid syntax for the authorization identity defined in RFC2831. I was 
intending to point out that RFC2222 and RFC2831 are not LDAP 
specifications. Their use and the appropriate content of their fields 
with respect to LDAP are defined by an LDAP specification, i.e. 
[authmeth], which sees fit to define the content of the authzid field 
(and therefore the form the authorization identity will take), but not 
the username field (and therefore the form the authentication 
credentials will take). I question the value in defining the usage of 
one and not the other by the LDAP specification.

> 
>>It does, however, define the username SASL parameter as
>>    "The user's name in the specified realm, encoded according to the
>>     value of the "charset" directive. This directive is required and
>>     MUST be present exactly once; otherwise, authentication fails."
> 
> 
> I think this is an issue which already came up in the SASL WG.
> 
> 
>>I suggest this supports the potential to use LDAPDN
> 
> 
> I don't believe it supports any such thing.
> 

So, if I have an authentication engine which uses distinguished names as 
the unique identifier in the realm and passwords for the shared secret, 
I can't use this authentication engine with the SASL "DIGEST-MD5" 
mechanism because I can't use the LDAPDN in the username-value in this 
mechanism? I must introduce a new arbitrary identifier and a mapping of 
this identifier to a distinguished name in order to bind? This does not 
seem reasonable.

> 
>>which is the closest thing to a username within LDAP that is required by the LDAP specifications.
> 
> 
> I don't think the LDAP specifications require a DN for authentication
> proposes.  If one considers EXTERNAL, the underlying authentication
> identity can be anything.  Likewise, any SASL mechanism can be used.
> Here the form of the authentication identity is mechanism specific.
> 
> Regardless of the mechanism, it is the server's responsibility to
> derive an appropriate authorization identity from the authentication
> identity associated with the credentials.  And if a (proxy) authorization
> identity is asserted, make sure the identity associated with the
> credentials is authorized to assume that asserted (proxy)
> authorization identity and, as appropriate, derive an identity
> representation suitable for application of access control and other
> administrative policies.
> 
> 
>>After all, the "user's name" in LDAP is the LDAPDN of the user's entry.
> 
> 
> Not necessarily.  There may be no LDAPDN associated with the user
> and, even if so, it may not refer to an entry.
> 
I conceed I used a poor argument here. I agree that there is not a 
requirement for an entry identified by the LDAPDN used in authentication 
to exist. I also agree that SASL allows for authentication using 
credentials which do not include an LDAPDN, and that the server is 
responsible for defining a mapping if it requires it.

However, I do not accept that SASL prevents my use of an LDAPDN as an 
identifier in authentication credentials. One of the possible forms of 
an identifier in the authentication credentials for an "EXTERNAL" SASL 
authentication is the subject name of a certificate, i.e. a 
distinguished name. Where my authentication engine is an LDAP or X.500 
system, I do accept that I should need to introduce a new identifier, if 
the directory does contain entries associated with LDAPDNs where the 
entries hold user passwords (or their hashes), if I wish to use SASL 
"DIGEST-MD5" authentication. [This would seem to be the point Ron Ramsey 
was making.]

I feel that [authmeth] should make some statement as to the usage of the 
username field in the SASL "DIGEST-MD5" credentials when used for digest 
authentication in LDAP, even if this is to clarify that the content of 
the username-value is an arbitrary octet string assigned by the server. 
Clients which make assumptions about the content of this field based on 
prior experience may have problems interworking with other servers. As I 
mentioned previously, I have already encountered LDAP clients which 
appear to make assumptions about the content of this field.

> 
>>Furthermore, [authmeth] has the statement:
>> "Clients sending a bind request with the sasl choice selected SHOULD
>>  NOT send a value in the name field. Servers receiving a bind request
>>  with the sasl choice selected SHALL ignore any value in the name
>>  field. "
>>in *4.3 SASL Authentication* which appears to prohibits the use of the BindRequest name field to establish the authentication identity.
>>Without this or the  SASL username providing a LDAPDN, how should the authentication credentials be determined?
> 
> 
> A local matter.  That is, how identities of different forms (or
> of the same form used in different contexts) relate to each other is
> a local matter.  How and where credentials are stored is a local
> matter.  Which identities may assume (proxy for) other identities is
> also a local matter.  And the form of identity used in access control
> systems is local matter.

Accepted.

> 
> It's certainly a matter which the client should not concern itself
> with...
> 
> Kurt 
> 
> 
> 



From owner-ietf-ldapbis@OpenLDAP.org  Mon May 12 04:01:27 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 EAA04790
	for <ldapbis-archive@lists.ietf.org>; Mon, 12 May 2003 04:01:27 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4C82EEn043296;
	Mon, 12 May 2003 08:02:41 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 h4C7uEsU043114;
	Mon, 12 May 2003 07:56:14 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 12 May 2003 07:56:14 +0000
Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.185])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4C7uCEh043103
	for <ietf-ldapbis@openldap.org>; Mon, 12 May 2003 07:56:12 GMT
	(envelope-from mlists@keutel.de)
Received: from [212.227.126.206] (helo=mrelayng.kundenserver.de)
	by moutng.kundenserver.de with esmtp (Exim 3.35 #1)
	id 19F8AI-0001Cz-00; Mon, 12 May 2003 09:56:06 +0200
Received: from [217.231.201.120] (helo=KeutelArbeit1)
	by mrelayng.kundenserver.de with asmtp (Exim 3.35 #1)
	id 19F8AI-0000TP-00; Mon, 12 May 2003 09:56:06 +0200
From: "Jochen Keutel" <mlists@keutel.de>
To: "ldapext" <ldapext@ietf.org>, "ietf-ldapbis" <ietf-ldapbis@OpenLDAP.org>
Subject: name form for inetOrgPerson with uid as naming attribute?
Date: Mon, 12 May 2003 09:56:05 +0200
Message-ID: <JLEJICLPLLMHBCHHOKOECEOACOAA.mlists@keutel.de>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-15"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by boole.openldap.org id h4C7uDEh043104
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

Hello,
  it's common practice to store objects of object class
inetOrgPerson with uid as naming attribute in an LDAP directory.
But - AFAIK - there is no name form allowing that; so LDAP
servers which care about name forms (e.g. X.500 servers) reject this.

It's quite boring to define this name form in each new directory
project I have ... (and, additionally, it's always a new
object identifier of the OID branch of the customer ...).

Is it possible to define this name form in any of the LDAP
standard documents?

draft-zeilenga-ldap-user-schema-06.txt doesn't mention name forms.
Neither do draft-ietf-ldapbis-user-schema-05.txt or RFC2798.

Or is it outside the scope of LDAP to define name forms?

Regards,  Jochen Keutel.





From owner-ietf-ldapbis@OpenLDAP.org  Mon May 12 04:12:40 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 EAA04932
	for <ldapbis-archive@lists.ietf.org>; Mon, 12 May 2003 04:12:40 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4C8EEEt043732;
	Mon, 12 May 2003 08:14:19 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 h4C89b7G043554;
	Mon, 12 May 2003 08:09:37 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 12 May 2003 08:09:37 +0000
Received: from nb2.stroeder.com (krl9-d9bb4eb6.pool.mediaWays.net [217.187.78.182])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4C89PEh043543
	for <ietf-ldapbis@openldap.org>; Mon, 12 May 2003 08:09:25 GMT
	(envelope-from michael@stroeder.com)
Received: from localhost (localhost.stroeder.com [127.0.0.1])
	by nb2.stroeder.com (Postfix) with ESMTP
	id CB71910D6D; Mon, 12 May 2003 10:09:00 +0200 (CEST)
Received: from stroeder.com (localhost.stroeder.com [127.0.0.1])
	by nb2.stroeder.com (Postfix) with ESMTP
	id 09ABF10CF7; Mon, 12 May 2003 10:09:00 +0200 (CEST)
Message-ID: <3EBF569B.5020500@stroeder.com>
Date: Mon, 12 May 2003 10:08:59 +0200
From: =?ISO-8859-15?Q?Michael_Str=F6der?= <michael@stroeder.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3.1) Gecko/20030425
X-Accept-Language: de-de, de, en-us, en
MIME-Version: 1.0
To: Jochen Keutel <mlists@keutel.de>
Cc: ldapext <ldapext@ietf.org>, ietf-ldapbis <ietf-ldapbis@OpenLDAP.org>
Subject: Re: [ldapext] name form for inetOrgPerson with uid as naming attribute?
References: <JLEJICLPLLMHBCHHOKOECEOACOAA.mlists@keutel.de>
In-Reply-To: <JLEJICLPLLMHBCHHOKOECEOACOAA.mlists@keutel.de>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by AMaViS 0.3.12pre8
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

Jochen Keutel wrote:
>   it's common practice to store objects of object class
> inetOrgPerson with uid as naming attribute in an LDAP directory.
> But - AFAIK - there is no name form allowing that; so LDAP
> servers which care about name forms (e.g. X.500 servers) reject this.
> 
> It's quite boring to define this name form in each new directory
> project I have ... (and, additionally, it's always a new
> object identifier of the OID branch of the customer ...).
> 
> Is it possible to define this name form in any of the LDAP
> standard documents?

IMHO it would be most appropriate to define a name form applicable for a 
certain object class in the document defining this object class. How about 
starting a new revision of RFC 2798, e.g. draft-[something]-ldap-RFC2798bis?

BTW we could add other useful things needed by LDAP community...

Ciao, Michael.



From owner-ietf-ldapbis@OpenLDAP.org  Mon May 12 04:12: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 EAA04964
	for <ldapbis-archive@lists.ietf.org>; Mon, 12 May 2003 04:12: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 h4C8EEEr043732;
	Mon, 12 May 2003 08:14:18 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 h4C88v9d043534;
	Mon, 12 May 2003 08:08:57 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 12 May 2003 08:08:57 +0000
Received: from ausyms50.ca.com ([155.35.248.106])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4C88pEh043486;
	Mon, 12 May 2003 08:08:51 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, 12 May 2003 18:08:30 +1000
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: Issues with current authmeth draft.
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
Date: Mon, 12 May 2003 18:08:29 +1000
Message-ID: <1395B4B334FCC143B36AF788E68B63810EC6DA@ausyms21.ca.com>
Thread-Topic: Issues with current authmeth draft.
Thread-Index: AcMYV9npejIIaHtgSlSvgTxVojDWoQAAlyRw
From: "Ramsay, Ron" <Ron.Ramsay@ca.com>
To: "Mark Ennis" <mark.ennis@adacel.com>,
        "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Cc: <ietf-ldapbis@OpenLDAP.org>
X-OriginalArrivalTime: 12 May 2003 08:08:30.0173 (UTC) FILETIME=[AC81F8D0:01C3185D]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by boole.openldap.org id h4C88qEh043505
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

Two concepts discussed in this document are authentication identity and authorisation identity. I take it that access control decisions are made on the basis of the authorisation identity. Therefore, I believe this should be a DN. I think RFC 2829 requires that it is a DN if it is provided. Digest-MD5 seems, through the notion of realm, to assume that authentication will take place in another domain.

Of TLS, RFC 2829 requires that the certificate subject be taken as the identity of the user.

It is not clear to me whether the directory actually requires an authentication identity, but it probably requires an authorisation identity. Under this interpretation, SASL may provide an authentication identity and this may or may not be understood by the directory. In the case of simple bind, the directory must understand it as it is responsible for authentication. In the case of Digest-MD5 there would be no need to understand it as authentication is handled 'outside' the directory. In the case of EXTERNAL, no identity is provided.

For simple bind, the authorisation identity would be the same as the authentication identity. For EXTERNAL, the authorisation identity should be the certificate subject. It would seem, for Digest-MD5, that the authorisation identity, a DN, should be provided unless the server can derive it by some out-of-band method.

If you agree with this, then the logical course of action would be to require, for Digest-MD5, that the autorisation identity be a LDAP DN as per RFC 2253 and that it be provided unless the client has out-of-band knowledge that the server will derive it.

From the point of view of a server that performs Digest-MD5 authentication internally, it could use such an authorization identity to locate data necessary to perform the computation. But in this case, the authentication identity has no function!

So, how can an authentication identity be useful if it is not a DN? Unless it, to, is optional. What is our model?

Ron

-----Original Message-----
From: Mark Ennis [mailto:mark.ennis@adacel.com]
Sent: Monday, 12 May 2003 17:25
To: Kurt D. Zeilenga
Cc: ietf-ldapbis@OpenLDAP.org
Subject: Re: Issues with current authmeth draft.


Kurt D. Zeilenga wrote:
> At 03:51 PM 5/11/2003, Mark Ennis wrote:
> 
>>Kurt D. Zeilenga wrote:
>>
>>>At 10:28 PM 5/6/2003, Mark Ennis wrote:
>>>
>>>
>>>>2) DIGEST-MD5 authentication identity
>>>>
>>>>There does not appear to be a clear statement as to the form of the authentication identity (as opposed to authorization identity) to be provided in the username-value of the SASL credentials for DIGEST-MD5 (or other mechanisms).
>>>
>>>RFC 2831 says its a user name.  That is, it's not a LDAPDN, not
>>>an authzid, not a domain name, not a ....
>>
>>On the other hand, RFC2831 does not specify the authzid field in the SASL parameters should use the authzid syntax defined in RFC2829 either.
> 
> 
> RFC 2222 says the form of the (proxy) authorization identity
> is application protocol specific.
> 
So? I am not questioning the appropriateness of [authmeth] defining the 
authzid syntax for the authorization identity defined in RFC2831. I was 
intending to point out that RFC2222 and RFC2831 are not LDAP 
specifications. Their use and the appropriate content of their fields 
with respect to LDAP are defined by an LDAP specification, i.e. 
[authmeth], which sees fit to define the content of the authzid field 
(and therefore the form the authorization identity will take), but not 
the username field (and therefore the form the authentication 
credentials will take). I question the value in defining the usage of 
one and not the other by the LDAP specification.

> 
>>It does, however, define the username SASL parameter as
>>    "The user's name in the specified realm, encoded according to the
>>     value of the "charset" directive. This directive is required and
>>     MUST be present exactly once; otherwise, authentication fails."
> 
> 
> I think this is an issue which already came up in the SASL WG.
> 
> 
>>I suggest this supports the potential to use LDAPDN
> 
> 
> I don't believe it supports any such thing.
> 

So, if I have an authentication engine which uses distinguished names as 
the unique identifier in the realm and passwords for the shared secret, 
I can't use this authentication engine with the SASL "DIGEST-MD5" 
mechanism because I can't use the LDAPDN in the username-value in this 
mechanism? I must introduce a new arbitrary identifier and a mapping of 
this identifier to a distinguished name in order to bind? This does not 
seem reasonable.

> 
>>which is the closest thing to a username within LDAP that is required by the LDAP specifications.
> 
> 
> I don't think the LDAP specifications require a DN for authentication
> proposes.  If one considers EXTERNAL, the underlying authentication
> identity can be anything.  Likewise, any SASL mechanism can be used.
> Here the form of the authentication identity is mechanism specific.
> 
> Regardless of the mechanism, it is the server's responsibility to
> derive an appropriate authorization identity from the authentication
> identity associated with the credentials.  And if a (proxy) authorization
> identity is asserted, make sure the identity associated with the
> credentials is authorized to assume that asserted (proxy)
> authorization identity and, as appropriate, derive an identity
> representation suitable for application of access control and other
> administrative policies.
> 
> 
>>After all, the "user's name" in LDAP is the LDAPDN of the user's entry.
> 
> 
> Not necessarily.  There may be no LDAPDN associated with the user
> and, even if so, it may not refer to an entry.
> 
I conceed I used a poor argument here. I agree that there is not a 
requirement for an entry identified by the LDAPDN used in authentication 
to exist. I also agree that SASL allows for authentication using 
credentials which do not include an LDAPDN, and that the server is 
responsible for defining a mapping if it requires it.

However, I do not accept that SASL prevents my use of an LDAPDN as an 
identifier in authentication credentials. One of the possible forms of 
an identifier in the authentication credentials for an "EXTERNAL" SASL 
authentication is the subject name of a certificate, i.e. a 
distinguished name. Where my authentication engine is an LDAP or X.500 
system, I do accept that I should need to introduce a new identifier, if 
the directory does contain entries associated with LDAPDNs where the 
entries hold user passwords (or their hashes), if I wish to use SASL 
"DIGEST-MD5" authentication. [This would seem to be the point Ron Ramsey 
was making.]

I feel that [authmeth] should make some statement as to the usage of the 
username field in the SASL "DIGEST-MD5" credentials when used for digest 
authentication in LDAP, even if this is to clarify that the content of 
the username-value is an arbitrary octet string assigned by the server. 
Clients which make assumptions about the content of this field based on 
prior experience may have problems interworking with other servers. As I 
mentioned previously, I have already encountered LDAP clients which 
appear to make assumptions about the content of this field.

> 
>>Furthermore, [authmeth] has the statement:
>> "Clients sending a bind request with the sasl choice selected SHOULD
>>  NOT send a value in the name field. Servers receiving a bind request
>>  with the sasl choice selected SHALL ignore any value in the name
>>  field. "
>>in *4.3 SASL Authentication* which appears to prohibits the use of the BindRequest name field to establish the authentication identity.
>>Without this or the  SASL username providing a LDAPDN, how should the authentication credentials be determined?
> 
> 
> A local matter.  That is, how identities of different forms (or
> of the same form used in different contexts) relate to each other is
> a local matter.  How and where credentials are stored is a local
> matter.  Which identities may assume (proxy for) other identities is
> also a local matter.  And the form of identity used in access control
> systems is local matter.

Accepted.

> 
> It's certainly a matter which the client should not concern itself
> with...
> 
> Kurt 
> 
> 
> 





From owner-ietf-ldapbis@OpenLDAP.org  Mon May 12 09:19:14 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 JAA11201
	for <ldapbis-archive@lists.ietf.org>; Mon, 12 May 2003 09:19:13 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4CDKGEl060191;
	Mon, 12 May 2003 13:20: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 h4CDGv6L059984;
	Mon, 12 May 2003 13:16:57 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 12 May 2003 13:16:57 +0000
Received: from e1.ny.us.ibm.com (e1.ny.us.ibm.com [32.97.182.101])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4CDGpEh059894;
	Mon, 12 May 2003 13:16:51 GMT
	(envelope-from jmcmeek@us.ibm.com)
Received: from northrelay02.pok.ibm.com (northrelay02.pok.ibm.com [9.56.224.150])
	by e1.ny.us.ibm.com (8.12.9/8.12.2) with ESMTP id h4CDGPWn044108;
	Mon, 12 May 2003 09:16:25 -0400
Received: from d27ml001.rchland.ibm.com (d01av02.pok.ibm.com [9.56.224.216])
	by northrelay02.pok.ibm.com (8.12.9/NCO/VER6.5) with ESMTP id h4CDGNAj033382;
	Mon, 12 May 2003 09:16:23 -0400
Subject: RE: Issues with current authmeth draft.
To: "Ramsay, Ron" <Ron.Ramsay@ca.com>
Cc: ietf-ldapbis@OpenLDAP.org, "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>,
        "Mark Ennis" <mark.ennis@adacel.com>
X-Mailer: Lotus Notes Release 5.0.12   February 13, 2003
Message-ID: <OFEAE3F7AF.5E983947-ON86256D24.0043D737-86256D24.0048E93C@us.ibm.com>
From: John McMeeking <jmcmeek@us.ibm.com>
Date: Mon, 12 May 2003 08:16:22 -0500
X-MIMETrack: Serialize by Router on d27ml001/27/M/IBM(Release 6.0.1CF1|March 04, 2003
 =?GB2312?B?q6E/KSBhdCAwNS8xMi8yMDAzIDA4OjE2OjI0?=
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>





With respect to DIGEST-MD5:

1) If only the authentication mechanism is used (not data integrity or
confidentiality), it provides a bind mechanism that protects the password
without the need to establish a secure connection.  Also, LDAP DNs are a
natural choice for a user name when authenticating to a LDAP directory.
From that perspective, I would like DIGEST-MD5 to allow the user name to be
a bind DN.  One way to do that might be to define a standard realm name
that LDAP servers support, for example "RFC2253 LDAP DN".  This would
provide a standard way for clients to take advantage of DIGEST-MD5 for
password protection not offered by simple bind.  The mapping from
authentication id to authorization id is trivial.

2) In the general case of using password based authentication to LDAP, with
a "user registry" that may, or may not, be the directory, the user name can
be most anything and the authentication id can be thought of as "<username>
in <authentication realm>".  For servers that have an access control
mechanism, the server must have some means of mapping the authentication id
to an authorization id.  And that is left to the server.  I'm fine with
that.

If we look at authentication id with other mechanisms:

GSSAPI:  The authentication id is based on a Kerberos principal name
(jsmith@mycompany.com).  Using the general form I described above:
"<kerberos-principal> in <all Kerberos realms>".

EXTERNAL: Some folks tend to think of the authentication id as the
certificate subject DN, which is something LDAP folks are comfortable with.
But as I understand it, the subject DN really should be used in association
with the issuer DN.  So the authentication id is more properly something
like "<subject-dn> in <certificates issued by issuer-DN>", which isn't a DN
at all.

simple bind:  could be expressed as "<bind-dn> in <RFC2253 LDAP DN>"

Looked at this way, I'd say RFC2829 over-emphasizes authorization id, and
neglects the use that of LDAP DN as a natural choice for user names when
authenticating to a LDAP directory.  I suspect it would be rare for a
client to know what authorization id to specify, and it is likely that a
server would require the user name to be the same id the server would
generate internally.

To summarize:  I'd like authmeth to define a realm name for use with
Digest-MD5 that corresponds to LDAP DNs known to this server.  Authzid is
okay, but perhaps could be better put into context.


John  McMeeking



                                                                                                                                    
                      "Ramsay, Ron"                                                                                                 
                      <Ron.Ramsay@ca.com>         To:       "Mark Ennis" <mark.ennis@adacel.com>, "Kurt D. Zeilenga"                
                      Sent by:                     <Kurt@OpenLDAP.org>                                                              
                      owner-ietf-ldapbis@O        cc:       <ietf-ldapbis@OpenLDAP.org>                                             
                      penLDAP.org                 Subject:  RE: Issues with current authmeth draft.                                 
                                                                                                                                    
                                                                                                                                    
                      05/12/2003 03:08 AM                                                                                           
                                                                                                                                    
                                                                                                                                    




Two concepts discussed in this document are authentication identity and
authorisation identity. I take it that access control decisions are made on
the basis of the authorisation identity. Therefore, I believe this should
be a DN. I think RFC 2829 requires that it is a DN if it is provided.
Digest-MD5 seems, through the notion of realm, to assume that
authentication will take place in another domain.

Of TLS, RFC 2829 requires that the certificate subject be taken as the
identity of the user.

It is not clear to me whether the directory actually requires an
authentication identity, but it probably requires an authorisation
identity. Under this interpretation, SASL may provide an authentication
identity and this may or may not be understood by the directory. In the
case of simple bind, the directory must understand it as it is responsible
for authentication. In the case of Digest-MD5 there would be no need to
understand it as authentication is handled 'outside' the directory. In the
case of EXTERNAL, no identity is provided.

For simple bind, the authorisation identity would be the same as the
authentication identity. For EXTERNAL, the authorisation identity should be
the certificate subject. It would seem, for Digest-MD5, that the
authorisation identity, a DN, should be provided unless the server can
derive it by some out-of-band method.

If you agree with this, then the logical course of action would be to
require, for Digest-MD5, that the autorisation identity be a LDAP DN as per
RFC 2253 and that it be provided unless the client has out-of-band
knowledge that the server will derive it.

From the point of view of a server that performs Digest-MD5 authentication
internally, it could use such an authorization identity to locate data
necessary to perform the computation. But in this case, the authentication
identity has no function!

So, how can an authentication identity be useful if it is not a DN? Unless
it, to, is optional. What is our model?

Ron

-----Original Message-----
From: Mark Ennis [mailto:mark.ennis@adacel.com]
Sent: Monday, 12 May 2003 17:25
To: Kurt D. Zeilenga
Cc: ietf-ldapbis@OpenLDAP.org
Subject: Re: Issues with current authmeth draft.


Kurt D. Zeilenga wrote:
> At 03:51 PM 5/11/2003, Mark Ennis wrote:
>
>>Kurt D. Zeilenga wrote:
>>
>>>At 10:28 PM 5/6/2003, Mark Ennis wrote:
>>>
>>>
>>>>2) DIGEST-MD5 authentication identity
>>>>
>>>>There does not appear to be a clear statement as to the form of the
authentication identity (as opposed to authorization identity) to be
provided in the username-value of the SASL credentials for DIGEST-MD5 (or
other mechanisms).
>>>
>>>RFC 2831 says its a user name.  That is, it's not a LDAPDN, not
>>>an authzid, not a domain name, not a ....
>>
>>On the other hand, RFC2831 does not specify the authzid field in the SASL
parameters should use the authzid syntax defined in RFC2829 either.
>
>
> RFC 2222 says the form of the (proxy) authorization identity
> is application protocol specific.
>
So? I am not questioning the appropriateness of [authmeth] defining the
authzid syntax for the authorization identity defined in RFC2831. I was
intending to point out that RFC2222 and RFC2831 are not LDAP
specifications. Their use and the appropriate content of their fields
with respect to LDAP are defined by an LDAP specification, i.e.
[authmeth], which sees fit to define the content of the authzid field
(and therefore the form the authorization identity will take), but not
the username field (and therefore the form the authentication
credentials will take). I question the value in defining the usage of
one and not the other by the LDAP specification.

>
>>It does, however, define the username SASL parameter as
>>    "The user's name in the specified realm, encoded according to the
>>     value of the "charset" directive. This directive is required and
>>     MUST be present exactly once; otherwise, authentication fails."
>
>
> I think this is an issue which already came up in the SASL WG.
>
>
>>I suggest this supports the potential to use LDAPDN
>
>
> I don't believe it supports any such thing.
>

So, if I have an authentication engine which uses distinguished names as
the unique identifier in the realm and passwords for the shared secret,
I can't use this authentication engine with the SASL "DIGEST-MD5"
mechanism because I can't use the LDAPDN in the username-value in this
mechanism? I must introduce a new arbitrary identifier and a mapping of
this identifier to a distinguished name in order to bind? This does not
seem reasonable.

>
>>which is the closest thing to a username within LDAP that is required by
the LDAP specifications.
>
>
> I don't think the LDAP specifications require a DN for authentication
> proposes.  If one considers EXTERNAL, the underlying authentication
> identity can be anything.  Likewise, any SASL mechanism can be used.
> Here the form of the authentication identity is mechanism specific.
>
> Regardless of the mechanism, it is the server's responsibility to
> derive an appropriate authorization identity from the authentication
> identity associated with the credentials.  And if a (proxy) authorization
> identity is asserted, make sure the identity associated with the
> credentials is authorized to assume that asserted (proxy)
> authorization identity and, as appropriate, derive an identity
> representation suitable for application of access control and other
> administrative policies.
>
>
>>After all, the "user's name" in LDAP is the LDAPDN of the user's entry.
>
>
> Not necessarily.  There may be no LDAPDN associated with the user
> and, even if so, it may not refer to an entry.
>
I conceed I used a poor argument here. I agree that there is not a
requirement for an entry identified by the LDAPDN used in authentication
to exist. I also agree that SASL allows for authentication using
credentials which do not include an LDAPDN, and that the server is
responsible for defining a mapping if it requires it.

However, I do not accept that SASL prevents my use of an LDAPDN as an
identifier in authentication credentials. One of the possible forms of
an identifier in the authentication credentials for an "EXTERNAL" SASL
authentication is the subject name of a certificate, i.e. a
distinguished name. Where my authentication engine is an LDAP or X.500
system, I do accept that I should need to introduce a new identifier, if
the directory does contain entries associated with LDAPDNs where the
entries hold user passwords (or their hashes), if I wish to use SASL
"DIGEST-MD5" authentication. [This would seem to be the point Ron Ramsey
was making.]

I feel that [authmeth] should make some statement as to the usage of the
username field in the SASL "DIGEST-MD5" credentials when used for digest
authentication in LDAP, even if this is to clarify that the content of
the username-value is an arbitrary octet string assigned by the server.
Clients which make assumptions about the content of this field based on
prior experience may have problems interworking with other servers. As I
mentioned previously, I have already encountered LDAP clients which
appear to make assumptions about the content of this field.

>
>>Furthermore, [authmeth] has the statement:
>> "Clients sending a bind request with the sasl choice selected SHOULD
>>  NOT send a value in the name field. Servers receiving a bind request
>>  with the sasl choice selected SHALL ignore any value in the name
>>  field. "
>>in *4.3 SASL Authentication* which appears to prohibits the use of the
BindRequest name field to establish the authentication identity.
>>Without this or the  SASL username providing a LDAPDN, how should the
authentication credentials be determined?
>
>
> A local matter.  That is, how identities of different forms (or
> of the same form used in different contexts) relate to each other is
> a local matter.  How and where credentials are stored is a local
> matter.  Which identities may assume (proxy for) other identities is
> also a local matter.  And the form of identity used in access control
> systems is local matter.

Accepted.

>
> It's certainly a matter which the client should not concern itself
> with...
>
> Kurt
>
>
>








From owner-ietf-ldapbis@OpenLDAP.org  Mon May 12 10:05:38 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 KAA12919
	for <ldapbis-archive@lists.ietf.org>; Mon, 12 May 2003 10:05:37 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4CE2FFB062670;
	Mon, 12 May 2003 14:07:12 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 h4CDqtB7061813;
	Mon, 12 May 2003 13:52:55 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 12 May 2003 13:52:55 +0000
Received: from netscape.com (r2d2.aoltw.net [64.236.137.26])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4CDqsEh061793
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 12 May 2003 13:52:54 GMT
	(envelope-from mcs@netscape.com)
Received: from judge.mcom.com (judge.nscp.aoltw.net [10.169.8.47])
	by netscape.com (8.10.0/8.10.0) with ESMTP id h4CDqOE14750
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 12 May 2003 06:52:24 -0700 (PDT)
Received: from netscape.com ([10.169.192.48]) by judge.mcom.com
          (Netscape Messaging Server 4.15) with ESMTP id HES17F00.122;
          Mon, 12 May 2003 06:52:27 -0700 
Message-ID: <3EBFA715.8090601@netscape.com>
Date: Mon, 12 May 2003 09:52:21 -0400
From: mcs@netscape.com (Mark C Smith)
Organization: Netscape Communications Corp.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030428 Netscape/7.02+
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: =?ISO-8859-1?Q?Michael_Str=F6der?= <michael@stroeder.com>
CC: Jochen Keutel <mlists@keutel.de>, ldapext <ldapext@ietf.org>,
        ietf-ldapbis <ietf-ldapbis@OpenLDAP.org>
Subject: Re: [ldapext] name form for inetOrgPerson with uid as naming attribute?
References: <JLEJICLPLLMHBCHHOKOECEOACOAA.mlists@keutel.de> <3EBF569B.5020500@stroeder.com>
In-Reply-To: <3EBF569B.5020500@stroeder.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
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

Michael Ströder wrote:
>
> IMHO it would be most appropriate to define a name form applicable for a 
> certain object class in the document defining this object class. How 
> about starting a new revision of RFC 2798, e.g. 
> draft-[something]-ldap-RFC2798bis?
> 
> BTW we could add other useful things needed by LDAP community...

Years ago John Dale proposed two name forms for inclusion in the 
inetOrgPerson document but, at the time, it was too late to include them 
(debate had been going on long enough about the document and we were 
about to send it to the IESG).  But revising 2798 seems like a good idea 
if there is sufficient interest.  I'd be happy to take on the editing 
tasks again.

For the record, here are the nameforms John proposed (I translated them 
to RFC 2252 syntax, so any syntax errors are mine):

nameForms: ( 2.16.840.1.113678.640.7.8
   NAME 'inetOrgPersonNameForm'
   OC inetOrgPerson
   MUST cn
   MAY ou )

nameForms: ( 2.16.840.1.113678.640.7.9
   NAME 'inetOrgPersonNameForm'
   OC inetOrgPerson
   MUST uid
   MAY ( cn $ ou ) )

-Mark Smith
  Netscape



From owner-ietf-ldapbis@OpenLDAP.org  Mon May 12 10:54: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 KAA17514
	for <ldapbis-archive@lists.ietf.org>; Mon, 12 May 2003 10:54: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 h4CEuGEl066896;
	Mon, 12 May 2003 14:56:25 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 h4CEt2cj066786;
	Mon, 12 May 2003 14:55:02 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 12 May 2003 14:55:02 +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 h4CEswEh066773
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 12 May 2003 14:54:58 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 h4CEsnc6069245;
	Mon, 12 May 2003 14:54:49 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030512072647.029576c8@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Mon, 12 May 2003 07:52:13 -0700
To: John McMeeking <jmcmeek@us.ibm.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: RE: Issues with current authmeth draft.
Cc: "Ramsay, Ron" <Ron.Ramsay@ca.com>, ietf-ldapbis@OpenLDAP.org,
        "Mark Ennis" <mark.ennis@adacel.com>
In-Reply-To: <OFEAE3F7AF.5E983947-ON86256D24.0043D737-86256D24.0048E93C@
 us.ibm.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:16 AM 5/12/2003, John McMeeking wrote:
>With respect to DIGEST-MD5:
>
>1) If only the authentication mechanism is used (not data integrity or
>confidentiality), it provides a bind mechanism that protects the password
>without the need to establish a secure connection.  Also, LDAP DNs are a
>natural choice for a user name when authenticating to a LDAP directory.
>>From that perspective, I would like DIGEST-MD5 to allow the user name to be
>a bind DN.

There are few problems here.

First DIGEST-MD5 security considerations encourage server implementors
to store the A1 hash, not the clear text password.  For DIGEST-MD5 to
work as intended, the client MUST provide the authentication identity
is the form which the server used in generating the A1 hash.  There
is no canonical DN textual string representation.

Secondly, when DIGEST-MD5 is revised, the client and the server will
be required to "stringprep" the username according to an algorithm
specified in the DIGEST-MD5.  There will be some LDAPDNs which will
not pass this stringprep and others which would be mangled.  One would
have to define an algorithm for encoding LDAPDNs into DIGEST-MD5
usernames and then require servers decode these for subsequent
processing.

Third, this would make LDAP's use of DIGEST-MD5 inconsistent with
the general use of DIGEST-MD5, yielding it impossible for a
multi-protocol application to consistently use the mechanism.

>One way to do that might be to define a standard realm name
>that LDAP servers support, for example "RFC2253 LDAP DN".

This would defeat the purpose of realms in DIGEST-MD5.

>This would provide a standard way for clients to take advantage of DIGEST-MD5 for
>password protection not offered by simple bind.  The mapping from
>authentication id to authorization id is trivial.
>
>2) In the general case of using password based authentication to LDAP, with
>a "user registry" that may, or may not, be the directory, the user name can
>be most anything and the authentication id can be thought of as "<username>
>in <authentication realm>".  For servers that have an access control
>mechanism, the server must have some means of mapping the authentication id
>to an authorization id.  And that is left to the server.  I'm fine with
>that.
>
>If we look at authentication id with other mechanisms:
>
>GSSAPI:  The authentication id is based on a Kerberos principal name
>(jsmith@mycompany.com).  Using the general form I described above:
>"<kerberos-principal> in <all Kerberos realms>".
>
>EXTERNAL: Some folks tend to think of the authentication id as the
>certificate subject DN, which is something LDAP folks are comfortable with.
>But as I understand it, the subject DN really should be used in association
>with the issuer DN.  So the authentication id is more properly something
>like "<subject-dn> in <certificates issued by issuer-DN>", which isn't a DN
>at all.
>
>simple bind:  could be expressed as "<bind-dn> in <RFC2253 LDAP DN>"
>
>Looked at this way, I'd say RFC2829 over-emphasizes authorization id,

That I would agree with.  The purpose of SASL authorization identity
strings are to support identity assumption (proxy authorization).

>and
>neglects the use that of LDAP DN as a natural choice for user names when
>authenticating to a LDAP directory.  I suspect it would be rare for a
>client to know what authorization id to specify, and it is likely that a
>server would require the user name to be the same id the server would
>generate internally.

I think we put too much in "LDAP DNs are natural" line.  They aren't.
Users shouldn't have to know their DN.

Kurt



From owner-ietf-ldapbis@OpenLDAP.org  Mon May 12 11:58: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 LAA21931
	for <ldapbis-archive@lists.ietf.org>; Mon, 12 May 2003 11:58: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 h4CFcGFJ070242;
	Mon, 12 May 2003 15:57:32 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 h4CFWLAf069931;
	Mon, 12 May 2003 15:32:21 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 12 May 2003 15:32:21 +0000
Received: from e4.ny.us.ibm.com (e4.ny.us.ibm.com [32.97.182.104])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4CFWCEh069850;
	Mon, 12 May 2003 15:32:12 GMT
	(envelope-from jmcmeek@us.ibm.com)
Received: from northrelay04.pok.ibm.com (northrelay04.pok.ibm.com [9.56.224.206])
	by e4.ny.us.ibm.com (8.12.9/8.12.2) with ESMTP id h4CFVjsZ113044;
	Mon, 12 May 2003 11:31:45 -0400
Received: from d27ml001.rchland.ibm.com (d01av02.pok.ibm.com [9.56.224.216])
	by northrelay04.pok.ibm.com (8.12.9/NCO/VER6.5) with ESMTP id h4CFVh8J027506;
	Mon, 12 May 2003 11:31:43 -0400
Subject: RE: Issues with current authmeth draft.
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Cc: ietf-ldapbis@OpenLDAP.org, "Mark Ennis" <mark.ennis@adacel.com>,
        "Ramsay, Ron" <Ron.Ramsay@ca.com>
X-Mailer: Lotus Notes Release 5.0.12   February 13, 2003
Message-ID: <OFD0863EA3.23595ECB-ON86256D24.00526F0F-86256D24.00554A98@us.ibm.com>
From: John McMeeking <jmcmeek@us.ibm.com>
Date: Mon, 12 May 2003 10:31:35 -0500
X-MIMETrack: Serialize by Router on d27ml001/27/M/IBM(Release 6.0.1CF1|March 04, 2003
 =?GB2312?B?q6E/KSBhdCAwNS8xMi8yMDAzIDEwOjMxOjQ0?=
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>





First, I doubt that Digest-MD5 with a LDAP DN (either as a authentication
id or as an authorization id) would often be using a DN provided directly
by a user.  I would expect its use to be more likely in one of these
scenarios:

1) An application is configured with a bind DN to use.  For this purpose, I
think it would be reasonable if some standard or directory vendor supplied
tool generated the proper normalized DN required for Digest-MD5.  This
might be a wrapper around a Generate Digest-MD5 UserName extended request.

2) An application authenticates to LDAP by first doing a search for
(&(mail=xxxx)(objectclass=person)) and then issuing an LDAP bind request
with the returned DN and the user entered password.  For this purpose, a
standard algorithm, the above extended operation, or an operational
attribute, could be used.

See additional comments marked <JAM>.

I'll have to refresh my memory on the stringprep part.  If that turns out
to require defining a DN normalization algorithm, or defining supporting
extending operations, it might be more appropriate to address this type of
item in a separate RFC.


John  McMeeking


                                                                                                                                 
                      "Kurt D.                                                                                                   
                      Zeilenga"                To:       John McMeeking/Rochester/IBM@IBMUS                                      
                      <Kurt@OpenLDAP.or        cc:       "Ramsay, Ron" <Ron.Ramsay@ca.com>, ietf-ldapbis@OpenLDAP.org, "Mark     
                      g>                        Ennis" <mark.ennis@adacel.com>                                                   
                                               Subject:  RE: Issues with current authmeth draft.                                 
                      05/12/2003 09:52                                                                                           
                      AM                                                                                                         
                                                                                                                                 
                                                                                                                                 




At 09:52 AM 5/12/2003, Kurt D. Zeilenga wrote:
>With respect to DIGEST-MD5:
>
>1) If only the authentication mechanism is used (not data integrity or
>confidentiality), it provides a bind mechanism that protects the password
>without the need to establish a secure connection.  Also, LDAP DNs are a
>natural choice for a user name when authenticating to a LDAP directory.
>>From that perspective, I would like DIGEST-MD5 to allow the user name to
be
>a bind DN.

There are few problems here.

First DIGEST-MD5 security considerations encourage server implementors
to store the A1 hash, not the clear text password.  For DIGEST-MD5 to
work as intended, the client MUST provide the authentication identity
is the form which the server used in generating the A1 hash.  There
is no canonical DN textual string representation.

Secondly, when DIGEST-MD5 is revised, the client and the server will
be required to "stringprep" the username according to an algorithm
specified in the DIGEST-MD5.  There will be some LDAPDNs which will
not pass this stringprep and others which would be mangled.  One would
have to define an algorithm for encoding LDAPDNs into DIGEST-MD5
usernames and then require servers decode these for subsequent
processing.

Third, this would make LDAP's use of DIGEST-MD5 inconsistent with
the general use of DIGEST-MD5, yielding it impossible for a
multi-protocol application to consistently use the mechanism.

<JAM>
Technical problems aside (not to trivialize them), I don't see where a
predefined "LDAP DN" realm introduces any such problems.  This realm would
only be used by application that are designed to authenticate using a LDAP
DN, but want the additional password protection.  The multi-protocol
application can use the appropriate realms.
</JAM>

>One way to do that might be to define a standard realm name
>that LDAP servers support, for example "RFC2253 LDAP DN".

This would defeat the purpose of realms in DIGEST-MD5.

<JAM>
I see this exectly the opposite way.  The purpose realm is to allow the
application to chose which relam it uses and provide a hint to the user
what username would be appropriate.  I do not intend that an LDAP server
would support only this "LDAP DN" realm.
</JAM>

>This would provide a standard way for clients to take advantage of
DIGEST-MD5 for
>password protection not offered by simple bind.  The mapping from
>authentication id to authorization id is trivial.
>
>2) In the general case of using password based authentication to LDAP,
with
>a "user registry" that may, or may not, be the directory, the user name
can
>be most anything and the authentication id can be thought of as
"<username>
>in <authentication realm>".  For servers that have an access control
>mechanism, the server must have some means of mapping the authentication
id
>to an authorization id.  And that is left to the server.  I'm fine with
>that.
>
>If we look at authentication id with other mechanisms:
>
>GSSAPI:  The authentication id is based on a Kerberos principal name
>(jsmith@mycompany.com).  Using the general form I described above:
>"<kerberos-principal> in <all Kerberos realms>".
>
>EXTERNAL: Some folks tend to think of the authentication id as the
>certificate subject DN, which is something LDAP folks are comfortable
with.
>But as I understand it, the subject DN really should be used in
association
>with the issuer DN.  So the authentication id is more properly something
>like "<subject-dn> in <certificates issued by issuer-DN>", which isn't a
DN
>at all.
>
>simple bind:  could be expressed as "<bind-dn> in <RFC2253 LDAP DN>"
>
>Looked at this way, I'd say RFC2829 over-emphasizes authorization id,

That I would agree with.  The purpose of SASL authorization identity
strings are to support identity assumption (proxy authorization).

>and
>neglects the use that of LDAP DN as a natural choice for user names when
>authenticating to a LDAP directory.  I suspect it would be rare for a
>client to know what authorization id to specify, and it is likely that a
>server would require the user name to be the same id the server would
>generate internally.

I think we put too much in "LDAP DNs are natural" line.  They aren't.
Users shouldn't have to know their DN.

<JAM>
I agree that users shouldn't know what their DN is, and for the
applications I deal with that use simple binds, the user doesn't know their
DN.  However, it is natural for applications to use DNs.
</JAM>

Kurt






From owner-ietf-ldapbis@OpenLDAP.org  Mon May 12 12:24: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 MAA23120
	for <ldapbis-archive@lists.ietf.org>; Mon, 12 May 2003 12:24: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 h4CGQSEj073575;
	Mon, 12 May 2003 16:26: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 h4CG930w072431;
	Mon, 12 May 2003 16:09:03 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 12 May 2003 16:09:03 +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 h4CG91Eh072421
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 12 May 2003 16:09:01 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 h4CG8uc6069802;
	Mon, 12 May 2003 16:08:56 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030512081844.0291da50@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Mon, 12 May 2003 09:06:20 -0700
To: Mark Ennis <mark.ennis@adacel.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: Issues with current authmeth draft.
Cc: ietf-ldapbis@OpenLDAP.org
In-Reply-To: <3EBF4C65.7050900@adacel.com>
References: <5.2.0.9.0.20030511160317.02c61500@127.0.0.1>
 <5.2.0.9.0.20030509170956.023c44d8@127.0.0.1>
 <5.2.0.9.0.20030509170956.023c44d8@127.0.0.1>
 <5.2.0.9.0.20030511160317.02c61500@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 12:25 AM 5/12/2003, Mark Ennis wrote:
>Kurt D. Zeilenga wrote:
>>At 03:51 PM 5/11/2003, Mark Ennis wrote:
>>
>>>Kurt D. Zeilenga wrote:
>>>
>>>>At 10:28 PM 5/6/2003, Mark Ennis wrote:
>>>>
>>>>
>>>>>2) DIGEST-MD5 authentication identity
>>>>>
>>>>>There does not appear to be a clear statement as to the form of the authentication identity (as opposed to authorization identity) to be provided in the username-value of the SASL credentials for DIGEST-MD5 (or other mechanisms).
>>>>
>>>>RFC 2831 says its a user name.  That is, it's not a LDAPDN, not
>>>>an authzid, not a domain name, not a ....
>>>
>>>On the other hand, RFC2831 does not specify the authzid field in the SASL parameters should use the authzid syntax defined in RFC2829 either.
>>
>>RFC 2222 says the form of the (proxy) authorization identity
>>is application protocol specific.
>So?

Because RFC 2222 makes it fairly clear that the form of the
authentication identity is mechanism specific while the form
of the authorization identity is specific to the application-level
protocol profiling its use of SASL.

>I am not questioning the appropriateness of [authmeth] defining the authzid syntax for the authorization identity defined in RFC2831. I was intending to point out that RFC2222 and RFC2831 are not LDAP specifications.  Their use and the appropriate content of their fields with respect to LDAP are defined by an LDAP specification,

I think we need to be careful here.  The LDAP SASL profile defines
a few application protocol specific particulars, in accordance with
SASL profiling requirements.  Beyond this, it is generally inappropriate
for any other application protocol TS, to overload fields of specific
mechanisms.  That would defeats many of the values the SASL framework
brings to the Internet.

>i.e. [authmeth], which sees fit to define the content of the authzid field (and therefore the form the authorization identity will take), but not the username field (and therefore the form the authentication credentials will take).

RFC 2222 says the authorization identity form is application protocol
specific.  RFC 2222 implies the form of the authentication identity
is mechanism specific.

>I question the value in defining the usage of one and not the other by the LDAP specification.

Noted.


>>>It does, however, define the username SASL parameter as
>>>   "The user's name in the specified realm, encoded according to the
>>>    value of the "charset" directive. This directive is required and
>>>    MUST be present exactly once; otherwise, authentication fails."
>>
>>I think this is an issue which already came up in the SASL WG.
>>
>>>I suggest this supports the potential to use LDAPDN
>>
>>I don't believe it supports any such thing.
>
>So, if I have an authentication engine which uses distinguished names as the unique identifier in the realm and passwords for the shared secret, I can't use this authentication engine with the SASL "DIGEST-MD5" mechanism because I can't use the LDAPDN in the username-value in this mechanism?

A username value doesn't have LDAPDN syntax or semantics in the
protocol.

>I must introduce a new arbitrary identifier and a mapping of this identifier to a distinguished name in order to bind? This does not seem reasonable.

Or introduce identity mapping.
Or use a more appropriate mechanism.



>>>which is the closest thing to a username within LDAP that is required by the LDAP specifications.
>>
>>I don't think the LDAP specifications require a DN for authentication
>>proposes.  If one considers EXTERNAL, the underlying authentication
>>identity can be anything.  Likewise, any SASL mechanism can be used.
>>Here the form of the authentication identity is mechanism specific.
>>Regardless of the mechanism, it is the server's responsibility to
>>derive an appropriate authorization identity from the authentication
>>identity associated with the credentials.  And if a (proxy) authorization
>>identity is asserted, make sure the identity associated with the
>>credentials is authorized to assume that asserted (proxy)
>>authorization identity and, as appropriate, derive an identity
>>representation suitable for application of access control and other
>>administrative policies.
>>
>>>After all, the "user's name" in LDAP is the LDAPDN of the user's entry.
>>
>>Not necessarily.  There may be no LDAPDN associated with the user
>>and, even if so, it may not refer to an entry.
>I conceed I used a poor argument here. I agree that there is not a requirement for an entry identified by the LDAPDN used in authentication to exist. I also agree that SASL allows for authentication using credentials which do not include an LDAPDN, and that the server is responsible for defining a mapping if it requires it.

Okay, DIGEST-MD5 is clearly one of those mechanisms.

>However, I do not accept that SASL prevents my use of an LDAPDN as an identifier in authentication credentials.

Well, a username might look like an LDAPDN... but clearly the username
does not have LDAPDN semantics.

>One of the possible forms of an identifier in the authentication credentials for an "EXTERNAL" SASL authentication is the subject name of a certificate, i.e. a distinguished name. Where my authentication engine is an LDAP or X.500 system, I do accept that I should need to introduce a new identifier, if the directory does contain entries associated with LDAPDNs where the entries hold user passwords (or their hashes), if I wish to use SASL "DIGEST-MD5" authentication. [This would seem to be the point Ron Ramsey was making.]
>
>I feel that [authmeth] should make some statement as to the usage of the username field in the SASL "DIGEST-MD5" credentials when used for digest authentication in LDAP, even if this is to clarify that the content of the username-value is an arbitrary octet string assigned by the server.

I note that RFC 2222 and 2831 are being revised and they will include
some clarification in this area.  I would likely support (I'd have to
see the exact wording to be sure, please suggest something) an
[authmeth] clarification that reiterate these general statements
with a "for instance" for the DIGEST-MD5 username instance.

>Clients which make assumptions about the content of this field based on prior experience may have problems interworking with other servers. As I mentioned previously, I have already encountered LDAP clients which appear to make assumptions about the content of this field.
>
>>
>>>Furthermore, [authmeth] has the statement:
>>>"Clients sending a bind request with the sasl choice selected SHOULD
>>> NOT send a value in the name field. Servers receiving a bind request
>>> with the sasl choice selected SHALL ignore any value in the name
>>> field. "
>>>in *4.3 SASL Authentication* which appears to prohibits the use of the BindRequest name field to establish the authentication identity.
>>>Without this or the  SASL username providing a LDAPDN, how should the authentication credentials be determined?
>>
>>A local matter.  That is, how identities of different forms (or
>>of the same form used in different contexts) relate to each other is
>>a local matter.  How and where credentials are stored is a local
>>matter.  Which identities may assume (proxy for) other identities is
>>also a local matter.  And the form of identity used in access control
>>systems is local matter.
>
>Accepted.
>
>>It's certainly a matter which the client should not concern itself
>>with...
>>Kurt 



From owner-ietf-ldapbis@OpenLDAP.org  Mon May 12 12:25: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 MAA23152
	for <ldapbis-archive@lists.ietf.org>; Mon, 12 May 2003 12:25:11 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4CGQSEh073575;
	Mon, 12 May 2003 16:26:28 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 h4CGJrxB073122;
	Mon, 12 May 2003 16:19:53 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 12 May 2003 16:19:53 +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 h4CGJoEh073112
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 12 May 2003 16:19:50 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 h4CGJgc6069863;
	Mon, 12 May 2003 16:19:43 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030512090746.02965340@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Mon, 12 May 2003 09:17:07 -0700
To: John McMeeking <jmcmeek@us.ibm.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: RE: Issues with current authmeth draft.
Cc: ietf-ldapbis@OpenLDAP.org, "Mark Ennis" <mark.ennis@adacel.com>,
        "Ramsay, Ron" <Ron.Ramsay@ca.com>
In-Reply-To: <OFD0863EA3.23595ECB-ON86256D24.00526F0F-86256D24.00554A98@
 us.ibm.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 08:31 AM 5/12/2003, John McMeeking wrote:
>First, I doubt that Digest-MD5 with a LDAP DN (either as a authentication
>id or as an authorization id) would often be using a DN provided directly
>by a user.

YES!  DIGEST-MD5 is intended to be used where the user's credential
is a short user name and a password.

>I would expect its use to be more likely in one of these
>scenarios:
>
>1) An application is configured with a bind DN to use.  For this purpose, I
>think it would be reasonable if some standard or directory vendor supplied
>tool generated the proper normalized DN required for Digest-MD5.  This
>might be a wrapper around a Generate Digest-MD5 UserName extended request.

Then the application should use a mechanism intended for use
with DNs, like simple bind over TLS.

>2) An application authenticates to LDAP by first doing a search for
>(&(mail=xxxx)(objectclass=person)) and then issuing an LDAP bind request
>with the returned DN and the user entered password.  For this purpose, a
>standard algorithm, the above extended operation, or an operational
>attribute, could be used.

Requires the directory to be searchable and, to some degree, readable
by anonymous users.  Very bad.

>See additional comments marked <JAM>.
>
>I'll have to refresh my memory on the stringprep part.  If that turns out
>to require defining a DN normalization algorithm, or defining supporting
>extending operations, it might be more appropriate to address this type of
>item in a separate RFC.

Or just to say that simple bind with TLS, not DIGEST-MD5, is
applicable to applications attempting to authenticate with
credentials consisting of an LDAP DN and password.



>John  McMeeking
>
>
>                                                                                                                                 
>                      "Kurt D.                                                                                                   
>                      Zeilenga"                To:       John McMeeking/Rochester/IBM@IBMUS                                      
>                      <Kurt@OpenLDAP.or        cc:       "Ramsay, Ron" <Ron.Ramsay@ca.com>, ietf-ldapbis@OpenLDAP.org, "Mark     
>                      g>                        Ennis" <mark.ennis@adacel.com>                                                   
>                                               Subject:  RE: Issues with current authmeth draft.                                 
>                      05/12/2003 09:52                                                                                           
>                      AM                                                                                                         
>                                                                                                                                 
>                                                                                                                                 
>
>
>
>
>At 09:52 AM 5/12/2003, Kurt D. Zeilenga wrote:
>>With respect to DIGEST-MD5:
>>
>>1) If only the authentication mechanism is used (not data integrity or
>>confidentiality), it provides a bind mechanism that protects the password
>>without the need to establish a secure connection.  Also, LDAP DNs are a
>>natural choice for a user name when authenticating to a LDAP directory.
>>>From that perspective, I would like DIGEST-MD5 to allow the user name to
>be
>>a bind DN.
>
>There are few problems here.
>
>First DIGEST-MD5 security considerations encourage server implementors
>to store the A1 hash, not the clear text password.  For DIGEST-MD5 to
>work as intended, the client MUST provide the authentication identity
>is the form which the server used in generating the A1 hash.  There
>is no canonical DN textual string representation.
>
>Secondly, when DIGEST-MD5 is revised, the client and the server will
>be required to "stringprep" the username according to an algorithm
>specified in the DIGEST-MD5.  There will be some LDAPDNs which will
>not pass this stringprep and others which would be mangled.  One would
>have to define an algorithm for encoding LDAPDNs into DIGEST-MD5
>usernames and then require servers decode these for subsequent
>processing.
>
>Third, this would make LDAP's use of DIGEST-MD5 inconsistent with
>the general use of DIGEST-MD5, yielding it impossible for a
>multi-protocol application to consistently use the mechanism.
>
><JAM>
>Technical problems aside (not to trivialize them), I don't see where a
>predefined "LDAP DN" realm introduces any such problems.  This realm would
>only be used by application that are designed to authenticate using a LDAP
>DN, but want the additional password protection.  The multi-protocol
>application can use the appropriate realms.
></JAM>
>
>>One way to do that might be to define a standard realm name
>>that LDAP servers support, for example "RFC2253 LDAP DN".
>
>This would defeat the purpose of realms in DIGEST-MD5.
>
><JAM>
>I see this exectly the opposite way.  The purpose realm is to allow the
>application to chose which relam it uses and provide a hint to the user
>what username would be appropriate.  I do not intend that an LDAP server
>would support only this "LDAP DN" realm.
></JAM>
>
>>This would provide a standard way for clients to take advantage of
>DIGEST-MD5 for
>>password protection not offered by simple bind.  The mapping from
>>authentication id to authorization id is trivial.
>>
>>2) In the general case of using password based authentication to LDAP,
>with
>>a "user registry" that may, or may not, be the directory, the user name
>can
>>be most anything and the authentication id can be thought of as
>"<username>
>>in <authentication realm>".  For servers that have an access control
>>mechanism, the server must have some means of mapping the authentication
>id
>>to an authorization id.  And that is left to the server.  I'm fine with
>>that.
>>
>>If we look at authentication id with other mechanisms:
>>
>>GSSAPI:  The authentication id is based on a Kerberos principal name
>>(jsmith@mycompany.com).  Using the general form I described above:
>>"<kerberos-principal> in <all Kerberos realms>".
>>
>>EXTERNAL: Some folks tend to think of the authentication id as the
>>certificate subject DN, which is something LDAP folks are comfortable
>with.
>>But as I understand it, the subject DN really should be used in
>association
>>with the issuer DN.  So the authentication id is more properly something
>>like "<subject-dn> in <certificates issued by issuer-DN>", which isn't a
>DN
>>at all.
>>
>>simple bind:  could be expressed as "<bind-dn> in <RFC2253 LDAP DN>"
>>
>>Looked at this way, I'd say RFC2829 over-emphasizes authorization id,
>
>That I would agree with.  The purpose of SASL authorization identity
>strings are to support identity assumption (proxy authorization).
>
>>and
>>neglects the use that of LDAP DN as a natural choice for user names when
>>authenticating to a LDAP directory.  I suspect it would be rare for a
>>client to know what authorization id to specify, and it is likely that a
>>server would require the user name to be the same id the server would
>>generate internally.
>
>I think we put too much in "LDAP DNs are natural" line.  They aren't.
>Users shouldn't have to know their DN.
>
><JAM>
>I agree that users shouldn't know what their DN is, and for the
>applications I deal with that use simple binds, the user doesn't know their
>DN.  However, it is natural for applications to use DNs.
></JAM>
>
>Kurt



From owner-ietf-ldapbis@OpenLDAP.org  Mon May 12 19:25:01 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 TAA08503
	for <ldapbis-archive@lists.ietf.org>; Mon, 12 May 2003 19:25:00 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4CNQJEl091082;
	Mon, 12 May 2003 23:26: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 h4CNOsik091005;
	Mon, 12 May 2003 23:24:54 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 12 May 2003 23:24:54 +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 h4CNOpEh090968
	for <ietf-ldapbis@openldap.org>; Mon, 12 May 2003 23:24:52 GMT
	(envelope-from mark.ennis@adacel.com)
Received: from nexus.adacel.com (Not Verified[10.32.240.1]) by adacel.com with MailMarshal (v5,0,3,91)
	id <B000064696>; Tue, 13 May 2003 09:21:25 +1000
Received: (qmail 17998 invoked from network); 12 May 2003 23:24:30 -0000
Received: from unknown (HELO adacel.com) (10.32.24.164)
  by nexus.adacel.com with SMTP; 12 May 2003 23:24:29 -0000
Message-ID: <3EC02D2D.8030402@adacel.com>
Date: Tue, 13 May 2003 09:24:29 +1000
From: Mark Ennis <mark.ennis@adacel.com>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
CC: John McMeeking <jmcmeek@us.ibm.com>, ietf-ldapbis@OpenLDAP.org,
        "Ramsay, Ron" <Ron.Ramsay@ca.com>
Subject: Re: Issues with current authmeth draft.
References: <5.2.0.9.0.20030512090746.02965340@127.0.0.1>
In-Reply-To: <5.2.0.9.0.20030512090746.02965340@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,

All the introductory text in RFC2829 and [authmeth] indicate that the 
reason for introducing and, in [authmeth] case, requiring DIGEST-MD5 is 
for security considerations relating to protecting passwords from 
eavesdropping. The only mention of non-LDAPDN authentication identities 
in the early parts of these documents are in reference to using these 
non-LDAPDN identities as authorization identities for backward 
compatibility with non-LDAP authentication mechanisms. You are 
suggesting DIGEST-MD5 and other SASL mechanisms were introduced for 
other than reasons related to security considerations and yet all the 
text in the documents introducing these mechanisms into LDAP indicate 
the reasons are security related and for backwards-compatibility only.

- Mark.

Kurt D. Zeilenga wrote:
> At 08:31 AM 5/12/2003, John McMeeking wrote:
> 
>>First, I doubt that Digest-MD5 with a LDAP DN (either as a authentication
>>id or as an authorization id) would often be using a DN provided directly
>>by a user.
> 
> 
> YES!  DIGEST-MD5 is intended to be used where the user's credential
> is a short user name and a password.
> 
> 
>>I would expect its use to be more likely in one of these
>>scenarios:
>>
>>1) An application is configured with a bind DN to use.  For this purpose, I
>>think it would be reasonable if some standard or directory vendor supplied
>>tool generated the proper normalized DN required for Digest-MD5.  This
>>might be a wrapper around a Generate Digest-MD5 UserName extended request.
> 
> 
> Then the application should use a mechanism intended for use
> with DNs, like simple bind over TLS.
> 
> 
>>2) An application authenticates to LDAP by first doing a search for
>>(&(mail=xxxx)(objectclass=person)) and then issuing an LDAP bind request
>>with the returned DN and the user entered password.  For this purpose, a
>>standard algorithm, the above extended operation, or an operational
>>attribute, could be used.
> 
> 
> Requires the directory to be searchable and, to some degree, readable
> by anonymous users.  Very bad.
> 
> 
>>See additional comments marked <JAM>.
>>
>>I'll have to refresh my memory on the stringprep part.  If that turns out
>>to require defining a DN normalization algorithm, or defining supporting
>>extending operations, it might be more appropriate to address this type of
>>item in a separate RFC.
> 
> 
> Or just to say that simple bind with TLS, not DIGEST-MD5, is
> applicable to applications attempting to authenticate with
> credentials consisting of an LDAP DN and password.



From owner-ietf-ldapbis@OpenLDAP.org  Mon May 12 19:30: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 TAA08570
	for <ldapbis-archive@lists.ietf.org>; Mon, 12 May 2003 19:30: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 h4CNWJEl091328;
	Mon, 12 May 2003 23:32:22 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 h4CNSr5i091154;
	Mon, 12 May 2003 23:28:53 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 12 May 2003 23:28:53 +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 h4CNSpEh091143
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 12 May 2003 23:28:51 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 h4CNSlc6072536;
	Mon, 12 May 2003 23:28:47 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030512153318.02957500@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Mon, 12 May 2003 16:26:10 -0700
To: "Ramsay, Ron" <Ron.Ramsay@ca.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: RE: Issues with current authmeth draft.
Cc: <ietf-ldapbis@OpenLDAP.org>
In-Reply-To: <1395B4B334FCC143B36AF788E68B63810EC6DA@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 01:08 AM 5/12/2003, Ramsay, Ron wrote:
>Two concepts discussed in this document are authentication identity and authorisation identity.   I take it that access control decisions are made on the basis of the authorisation identity.

The form of the authorization identity used in access control
decisions may not be the same as the form asserted by the
client wishing to assume some identity.  Note that when a
client does asserts an authorization identity, is requesting
to assume an identity other than that associated with its
credentials.  When an client wishes to act under its own
identity is should not assert a proxy authorization identity.

>Therefore, I believe this should be a DN. I think RFC 2829 requires that it is a DN if it is provided.

Sorry, no.

>Digest-MD5 seems, through the notion of realm, to assume that authentication will take place in another domain.


>Of TLS, RFC 2829 requires that the certificate subject be taken as the identity of the user.

Sorry, no.  RFC 2829, 5.1.2.1:
   The server will derive the client's authorization identity from
   the authentication identity supplied in the client's TLS
   credentials (typically a public key certificate) according
   to local policy.   The underlying mechanics of  
   how this is accomplished are implementation specific.

>It is not clear to me whether the directory actually requires an authentication identity, but it probably requires an authorisation identity. 

Yes, one can take the view that SASL authentication results in the
establishment of an authorization identity suitable for use in
subsequent access control decisions.

>Under this interpretation, SASL may provide an authentication identity and this may or may not be understood by the directory.

If you have clear separation between SASL and directory processing,
authentication details can be hidden from the directory.  The SASL
subsystem can be produce an authorization identity which the access
control subsystem can (directly or indirectly) use.

>In the case of simple bind, the directory must understand it as it is responsible for authentication. 

Well, I think it can be argued that the bind name need not refer
to an entry normally visible as part of the directory.  For example,
a server is quite free to map the bind name to some identity in an
external and then ask that external system to verify the credentials.

>In the case of Digest-MD5 there would be no need to understand it as authentication is handled 'outside' the directory.

Well, then again, a server is free to map the username to a DN
and access information at that DN in order to complete authentication.

>In the case of EXTERNAL, no identity is provided.

>For simple bind, the authorisation identity would be the same as the authentication identity.

Yes, but the server is free to represent the authorization identity
in another form if so chooses.  Maybe it prefers authzids.  Maybe
it prefers short user names.

>For EXTERNAL, the authorisation identity should be the certificate subject.

Not necessarily.  The server could, for instance, use an alternative
subject name.  Or the certificate serial number.

> It would seem, for Digest-MD5, that the authorisation identity, a DN, should be provided unless the server can derive it by some out-of-band method.

Maybe the server uses usernames directly in its access control system.
No DN form needed.  But if the server needed a DN, it certainly can
map the username to a DN using whatever algorithm suits it.

>If you agree with this,

I think not.

>then the logical course of action would be to require, for Digest-MD5, that the autorisation identity be a LDAP DN as per RFC 2253

No.  The authzid is for proxy authorization, not for indicating which
identity should be derived from the authentication identity.

>and that it be provided unless the client has out-of-band knowledge that the server will derive it.

The client should assume the server is capable of deriving a
suitable authorization identity in the appropriate form from the
authentication identity associated with its credentials.  Requiring
the normal clients (those not doing proxy authorization) to know more
than its credentials is unnecessary and counter to intent of
username/password mechanisms.

If the client knows instead a DN and password, then it should a
mechanism intended for DN/password authentication (such as
Simple bind over TLS).

>From the point of view of a server that performs Digest-MD5 authentication internally, it could use such an authorization identity to locate data necessary to perform the computation. But in this case, the authentication identity has no function!

Sorry, but I think that has a significant impact upon the security
of the mechanism.

>So, how can an authentication identity be useful if it is not a DN?

There is actually no requirement to implement authentication
and authorization based upon DNs.  A server could just implement
the DIGEST-MD5, not support proxy authorization at all, and use
simple user names in making access control decisions.

Kurt 



From owner-ietf-ldapbis@OpenLDAP.org  Mon May 12 20:08:02 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 UAA09459
	for <ldapbis-archive@lists.ietf.org>; Mon, 12 May 2003 20:08:01 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4D08JEl092198;
	Tue, 13 May 2003 00:08:27 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 h4D03kuY091888;
	Tue, 13 May 2003 00:03:46 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 13 May 2003 00:03:46 +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 h4D03iEh091878
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 13 May 2003 00:03:44 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 h4D03ec6072785;
	Tue, 13 May 2003 00:03:40 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030512162909.029492b8@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Mon, 12 May 2003 17:00:52 -0700
To: Mark Ennis <mark.ennis@adacel.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: Issues with current authmeth draft.
Cc: ietf-ldapbis@OpenLDAP.org
In-Reply-To: <3EC02D2D.8030402@adacel.com>
References: <5.2.0.9.0.20030512090746.02965340@127.0.0.1>
 <5.2.0.9.0.20030512090746.02965340@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 04:24 PM 5/12/2003, Mark Ennis wrote:
>All the introductory text in RFC2829 and [authmeth] indicate that the reason for introducing and, in [authmeth] case, requiring DIGEST-MD5 is for security considerations relating to protecting passwords from eavesdropping. The only mention of non-LDAPDN authentication identities in the early parts of these documents are in reference to using these non-LDAPDN identities as authorization identities for backward compatibility with non-LDAP authentication mechanisms.

Since RFC 2829 is a largely a SASL profile, I wouldn't expect it
to discuss LDAPDNs except in contexts where SASL allows application
profiles to use application specific forms of identities.

However, RFC 2829 is fairly clear when it states (very early):
   An authentication identity is the name presented in a credential.

   There are many forms of authentication credentials -- the form used
   depends upon the particular authentication mechanism negotiated by
   the parties.  For example: X.509 certificates, Kerberos tickets,     
   simple identity and password pairs.  Note that an authentication     
   mechanism may constrain the form of authentication identities used   
   with it.

In DIGEST-MD5 clearly constrains the form of the authentication
identity to a simple identity string, a user name.

>You are suggesting DIGEST-MD5 and other SASL mechanisms were introduced for other than reasons related to security considerations and yet all the text in the documents introducing these mechanisms into LDAP indicate the reasons are security related and for backwards-compatibility only.

I am suggesting that RFC 2829 recommends implementation of
simple bind over TLS to support DN/password credentials.
But it requires implementation of DIGEST-MD5 to support
username/password credentials.

However, regardless of this, it should be clear that stuffing
LDAPDNs into usernames is not a path to interoperability nor
security.  Matching issues alone should be enough to kill that
idea.  We cannot morph DIGEST-MD5 into something its not, that
breaks mechanism commonality between application protocols.
We needed to use each mechanism in a manner consistent with
its specification.

Going forward, it would be much better to clarify that simple
+TLS is to be used for DN/password credentials and DIGEST-MD5
(or PLAIN+TLS) be used for username/password credentials.

I note that due to the specification and interoperability problems
with DIGEST-MD5 (not just with LDAP), I would not be opposed to
changing the mandatory-to-implement authentication mechanism
from DIGEST-MD5 to simple+TLS.

Kurt

PS: I was once suggested in an I-D how one could stuff DNs
into DIGEST-MD5 credentials, it got no where.  See LDAPEXT
archives.



From owner-ietf-ldapbis@OpenLDAP.org  Mon May 12 20:12: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 ESMTP id UAA09605
	for <ldapbis-archive@lists.ietf.org>; Mon, 12 May 2003 20:12:27 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4D0EJEl092448;
	Tue, 13 May 2003 00:14: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 h4D08n0d092233;
	Tue, 13 May 2003 00:08:49 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 13 May 2003 00:08:49 +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 h4D08kEh092206
	for <ietf-ldapbis@openldap.org>; Tue, 13 May 2003 00:08:47 GMT
	(envelope-from mark.ennis@adacel.com)
Received: from nexus.adacel.com (Not Verified[10.32.240.1]) by adacel.com with MailMarshal (v5,0,3,91)
	id <B0000647e0>; Tue, 13 May 2003 10:05:21 +1000
Received: (qmail 24576 invoked from network); 13 May 2003 00:08:26 -0000
Received: from unknown (HELO adacel.com) (10.32.24.164)
  by nexus.adacel.com with SMTP; 13 May 2003 00:08:26 -0000
Message-ID: <3EC03779.6020509@adacel.com>
Date: Tue, 13 May 2003 10:08:25 +1000
From: Mark Ennis <mark.ennis@adacel.com>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
CC: "Ramsay, Ron" <Ron.Ramsay@ca.com>, ietf-ldapbis@OpenLDAP.org
Subject: Re: Issues with current authmeth draft.
References: <5.2.0.9.0.20030512153318.02957500@127.0.0.1>
In-Reply-To: <5.2.0.9.0.20030512153318.02957500@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:
> 
> If the client knows instead a DN and password, then it should a
> mechanism intended for DN/password authentication (such as
> Simple bind over TLS).

 From an interoperability perspective this has problems as a server is 
only required to implement DIGEST-MD5 and simple authentication, not 
TLS. This theoretical client would then only be able to interwork with 
servers which implement TLS or would be forced to use a less secure 
authentication mechanism (simple bind without TLS). This seems counter 
to the reasons in RFC2829 and [authmeth] for introducing SASL 
mechanisms, in particular, SASL DIGEST-MD5.

- Mark.



From owner-ietf-ldapbis@OpenLDAP.org  Mon May 12 21:19:09 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 VAA10719
	for <ldapbis-archive@lists.ietf.org>; Mon, 12 May 2003 21:19: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 h4D1KKEl093888;
	Tue, 13 May 2003 01:20:41 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 h4D1HMdk093800;
	Tue, 13 May 2003 01:17:22 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 13 May 2003 01:17:22 +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 h4D1HKEh093773
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 13 May 2003 01:17:21 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 h4D1HFc6073253;
	Tue, 13 May 2003 01:17:15 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030512175849.029b1100@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Mon, 12 May 2003 18:14:39 -0700
To: Mark Ennis <mark.ennis@adacel.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: Issues with current authmeth draft.
Cc: "Ramsay, Ron" <Ron.Ramsay@ca.com>, ietf-ldapbis@OpenLDAP.org
In-Reply-To: <3EC03779.6020509@adacel.com>
References: <5.2.0.9.0.20030512153318.02957500@127.0.0.1>
 <5.2.0.9.0.20030512153318.02957500@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 05:08 PM 5/12/2003, Mark Ennis wrote:
>This seems counter to the reasons in RFC2829 and [authmeth] for introducing SASL mechanisms, in particular, SASL DIGEST-MD5. 

Well then we should clarify the rationale.

Kurt




From owner-ietf-ldapbis@OpenLDAP.org  Mon May 12 22:06: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 WAA11325
	for <ldapbis-archive@lists.ietf.org>; Mon, 12 May 2003 22:06:30 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4D28KEl095847;
	Tue, 13 May 2003 02:08:33 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 h4D26svO095833;
	Tue, 13 May 2003 02:06:54 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 13 May 2003 02:06:54 +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 h4D26pEh095793;
	Tue, 13 May 2003 02:06:51 GMT
	(envelope-from RHARRISON@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Mon, 12 May 2003 20:06:31 -0600
Message-Id: <sebffec7.054@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.0 
Date: Mon, 12 May 2003 20:06:03 -0600
From: "Roger Harrison" <RHARRISON@novell.com>
To: <mark.ennis@adacel.com>, <Kurt@OpenLDAP.org>
Cc: <Ron.Ramsay@ca.com>, <ietf-ldapbis@OpenLDAP.org>
Subject: Re: Issues with current authmeth draft.
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=_F2AD0137.66074031"
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 MIME message. If you are reading this text, you may want to 
consider changing to a mail reader or gateway that understands how to 
properly handle MIME multipart messages.

--=_F2AD0137.66074031
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Mark,
 
Would you please  provide a pointer to the text describing the
"reasons... for introducing SASL mechanisms..." that you are referring
to so that I can make appropriate changes.
 
Thanks,
 
Roger

>>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 5/12/2003 7:14:39 PM >>>
At 05:08 PM 5/12/2003, Mark Ennis wrote:
>This seems counter to the reasons in RFC2829 and [authmeth] for
introducing SASL mechanisms, in particular, SASL DIGEST-MD5. 

Well then we should clarify the rationale.

Kurt




--=_F2AD0137.66074031
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1169" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Tahoma">
<DIV>Mark,</DIV>
<DIV>&nbsp;</DIV>
<DIV>Would you please&nbsp; provide a pointer to the text describing the 
"reasons... for introducing SASL mechanisms..." that you are referring to so 
that I can make appropriate changes.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Thanks,</DIV>
<DIV>&nbsp;</DIV>
<DIV>Roger<BR><BR>&gt;&gt;&gt; "Kurt D. Zeilenga" &lt;Kurt@OpenLDAP.org&gt; 
5/12/2003 7:14:39 PM &gt;&gt;&gt;<BR>At 05:08 PM 5/12/2003, Mark Ennis 
wrote:<BR>&gt;This seems counter to the reasons in RFC2829 and [authmeth] for 
introducing SASL mechanisms, in particular, SASL DIGEST-MD5. <BR><BR>Well then 
we should clarify the rationale.<BR><BR>Kurt<BR><BR><BR></DIV></BODY></HTML>

--=_F2AD0137.66074031--


From owner-ietf-ldapbis@OpenLDAP.org  Mon May 12 22:12: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 WAA11512
	for <ldapbis-archive@lists.ietf.org>; Mon, 12 May 2003 22:12: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 h4D2EKEl096132;
	Tue, 13 May 2003 02:14:22 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 h4D2CuXb096034;
	Tue, 13 May 2003 02:12:56 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 13 May 2003 02:12:56 +0000
Received: from ausyms50.ca.com ([155.35.248.106])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4D2CpEh096003;
	Tue, 13 May 2003 02:12:51 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, 13 May 2003 12:12:27 +1000
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: Issues with current authmeth draft.
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
Date: Tue, 13 May 2003 12:12:27 +1000
Message-ID: <1395B4B334FCC143B36AF788E68B6381105F3A@ausyms21.ca.com>
Thread-Topic: Issues with current authmeth draft.
Thread-Index: AcMY3kHQoe6rOX14Q4epWFmP2b6SEwAFKLbQ
From: "Ramsay, Ron" <Ron.Ramsay@ca.com>
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Cc: <ietf-ldapbis@OpenLDAP.org>
X-OriginalArrivalTime: 13 May 2003 02:12:27.0975 (UTC) FILETIME=[1A0EFD70:01C318F5]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by boole.openldap.org id h4D2CqEh096005
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 don't see how you can say that these authentication methods are not expected to use DNs. RFC 2829 states:

"All servers which support the storage of authentication credentials, such as passwords or certificates, in the directory MUST support the dnAuthzId choice."

The word is MUST!

I don't know what you make of

"The user's certificate subject field SHOULD be the name of the user's directory entry...."

but it suggests to me that the subject DN is the authetication name.

But without dwelling on the technicalities I think we have a simple problem here. If Digest-MD5 is a non-directory authentication method it must be removed from authmeth (to its own RFC). Authmeth should only deal with LDAP-based authentication methods.

The problem with Digest-MD5 is that either the password or a hash of the password has to be stored somewhere. A "directory" implementation would store this in a "user" entry and use an authentication identity which is the name of this entry. I see that you propose that the auth ID shoudl be a simple string, and that the directory should resolve this to a DN, if it needs to, but this is using the directory as a directory application! and is clearly not appropriate for a mandatory-to-implement procedure as the actual mechanism is not specified.

Ron


-----Original Message-----
From: Kurt D. Zeilenga [mailto:Kurt@OpenLDAP.org]
Sent: Tuesday, 13 May 2003 09:26
To: Ramsay, Ron
Cc: ietf-ldapbis@OpenLDAP.org
Subject: RE: Issues with current authmeth draft.


At 01:08 AM 5/12/2003, Ramsay, Ron wrote:
>Two concepts discussed in this document are authentication identity and authorisation identity.   I take it that access control decisions are made on the basis of the authorisation identity.

The form of the authorization identity used in access control
decisions may not be the same as the form asserted by the
client wishing to assume some identity.  Note that when a
client does asserts an authorization identity, is requesting
to assume an identity other than that associated with its
credentials.  When an client wishes to act under its own
identity is should not assert a proxy authorization identity.

>Therefore, I believe this should be a DN. I think RFC 2829 requires that it is a DN if it is provided.

Sorry, no.

>Digest-MD5 seems, through the notion of realm, to assume that authentication will take place in another domain.


>Of TLS, RFC 2829 requires that the certificate subject be taken as the identity of the user.

Sorry, no.  RFC 2829, 5.1.2.1:
   The server will derive the client's authorization identity from
   the authentication identity supplied in the client's TLS
   credentials (typically a public key certificate) according
   to local policy.   The underlying mechanics of  
   how this is accomplished are implementation specific.

>It is not clear to me whether the directory actually requires an authentication identity, but it probably requires an authorisation identity. 

Yes, one can take the view that SASL authentication results in the
establishment of an authorization identity suitable for use in
subsequent access control decisions.

>Under this interpretation, SASL may provide an authentication identity and this may or may not be understood by the directory.

If you have clear separation between SASL and directory processing,
authentication details can be hidden from the directory.  The SASL
subsystem can be produce an authorization identity which the access
control subsystem can (directly or indirectly) use.

>In the case of simple bind, the directory must understand it as it is responsible for authentication. 

Well, I think it can be argued that the bind name need not refer
to an entry normally visible as part of the directory.  For example,
a server is quite free to map the bind name to some identity in an
external and then ask that external system to verify the credentials.

>In the case of Digest-MD5 there would be no need to understand it as authentication is handled 'outside' the directory.

Well, then again, a server is free to map the username to a DN
and access information at that DN in order to complete authentication.

>In the case of EXTERNAL, no identity is provided.

>For simple bind, the authorisation identity would be the same as the authentication identity.

Yes, but the server is free to represent the authorization identity
in another form if so chooses.  Maybe it prefers authzids.  Maybe
it prefers short user names.

>For EXTERNAL, the authorisation identity should be the certificate subject.

Not necessarily.  The server could, for instance, use an alternative
subject name.  Or the certificate serial number.

> It would seem, for Digest-MD5, that the authorisation identity, a DN, should be provided unless the server can derive it by some out-of-band method.

Maybe the server uses usernames directly in its access control system.
No DN form needed.  But if the server needed a DN, it certainly can
map the username to a DN using whatever algorithm suits it.

>If you agree with this,

I think not.

>then the logical course of action would be to require, for Digest-MD5, that the autorisation identity be a LDAP DN as per RFC 2253

No.  The authzid is for proxy authorization, not for indicating which
identity should be derived from the authentication identity.

>and that it be provided unless the client has out-of-band knowledge that the server will derive it.

The client should assume the server is capable of deriving a
suitable authorization identity in the appropriate form from the
authentication identity associated with its credentials.  Requiring
the normal clients (those not doing proxy authorization) to know more
than its credentials is unnecessary and counter to intent of
username/password mechanisms.

If the client knows instead a DN and password, then it should a
mechanism intended for DN/password authentication (such as
Simple bind over TLS).

>From the point of view of a server that performs Digest-MD5 authentication internally, it could use such an authorization identity to locate data necessary to perform the computation. But in this case, the authentication identity has no function!

Sorry, but I think that has a significant impact upon the security
of the mechanism.

>So, how can an authentication identity be useful if it is not a DN?

There is actually no requirement to implement authentication
and authorization based upon DNs.  A server could just implement
the DIGEST-MD5, not support proxy authorization at all, and use
simple user names in making access control decisions.

Kurt 





From owner-ietf-ldapbis@OpenLDAP.org  Mon May 12 22:24:47 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 WAA11680
	for <ldapbis-archive@lists.ietf.org>; Mon, 12 May 2003 22: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 h4D2QKEr096607;
	Tue, 13 May 2003 02:26:34 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 h4D2Kq2n096457;
	Tue, 13 May 2003 02:20:52 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 13 May 2003 02:20:51 +0000
Received: from ausyms50.ca.com ([155.35.248.106])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4D2KmEh096427;
	Tue, 13 May 2003 02:20:48 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, 13 May 2003 12:20:27 +1000
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: Issues with current authmeth draft.
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
Date: Tue, 13 May 2003 12:20:27 +1000
Message-ID: <1395B4B334FCC143B36AF788E68B6381105F59@ausyms21.ca.com>
Thread-Topic: Issues with current authmeth draft.
Thread-Index: AcMY48pPlR3o8g6lR9qQbrHGq9pmkwAEcS8A
From: "Ramsay, Ron" <Ron.Ramsay@ca.com>
To: "Mark Ennis" <mark.ennis@adacel.com>,
        "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Cc: <ietf-ldapbis@OpenLDAP.org>
X-OriginalArrivalTime: 13 May 2003 02:20:27.0581 (UTC) FILETIME=[37ED0ED0:01C318F6]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by boole.openldap.org id h4D2KnEh096428
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 don't like messages that say "hear, hear", but I fell compelled to say hear, hear! There is also no credence given to the greater effort required to run TLS operationally. Digest-MD5 was suggested as a replacement for CRAM-MD5 not, as I believe, because it had very little connection with directories, but because it was argued to be superior. The aim, though, was a password mechanism that did not present the password in the clear.

Ron

-----Original Message-----
From: Mark Ennis [mailto:mark.ennis@adacel.com]
Sent: Tuesday, 13 May 2003 10:08
To: Kurt D. Zeilenga
Cc: Ramsay, Ron; ietf-ldapbis@OpenLDAP.org
Subject: Re: Issues with current authmeth draft.


Kurt D. Zeilenga wrote:
> 
> If the client knows instead a DN and password, then it should a
> mechanism intended for DN/password authentication (such as
> Simple bind over TLS).

 From an interoperability perspective this has problems as a server is 
only required to implement DIGEST-MD5 and simple authentication, not 
TLS. This theoretical client would then only be able to interwork with 
servers which implement TLS or would be forced to use a less secure 
authentication mechanism (simple bind without TLS). This seems counter 
to the reasons in RFC2829 and [authmeth] for introducing SASL 
mechanisms, in particular, SASL DIGEST-MD5.

- Mark.





From owner-ietf-ldapbis@OpenLDAP.org  Mon May 12 22:24: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 WAA11677
	for <ldapbis-archive@lists.ietf.org>; Mon, 12 May 2003 22:24: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 h4D2QKEp096607;
	Tue, 13 May 2003 02:26:33 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 h4D2PwvY096596;
	Tue, 13 May 2003 02:25:58 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 13 May 2003 02:25:58 +0000
Received: from ausyms50.ca.com ([155.35.248.106])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4D2PsEh096562;
	Tue, 13 May 2003 02:25:55 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, 13 May 2003 12:25:34 +1000
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: Issues with current authmeth draft.
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
Date: Tue, 13 May 2003 12:25:33 +1000
Message-ID: <1395B4B334FCC143B36AF788E68B6381105F69@ausyms21.ca.com>
Thread-Topic: Issues with current authmeth draft.
Thread-Index: AcMY485o68K22F44TMmPPoxmVF+gwQAEq36w
From: "Ramsay, Ron" <Ron.Ramsay@ca.com>
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>,
        "Mark Ennis" <mark.ennis@adacel.com>
Cc: <ietf-ldapbis@OpenLDAP.org>
X-OriginalArrivalTime: 13 May 2003 02:25:34.0158 (UTC) FILETIME=[EEA8FEE0:01C318F6]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by boole.openldap.org id h4D2PtEh096567
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 don't believe you can mandate simple/TLS! At the time RFC 2829 was debated, a large number on the WG wanted this. They did not get their way because of the complexity of the solution. It was argued that a password-based method would be better. I think they believed it would still be DN/password, though. 

-----Original Message-----
From: Kurt D. Zeilenga [mailto:Kurt@OpenLDAP.org]
Sent: Tuesday, 13 May 2003 10:01
To: Mark Ennis
Cc: ietf-ldapbis@OpenLDAP.org
Subject: Re: Issues with current authmeth draft.


At 04:24 PM 5/12/2003, Mark Ennis wrote:
>All the introductory text in RFC2829 and [authmeth] indicate that the reason for introducing and, in [authmeth] case, requiring DIGEST-MD5 is for security considerations relating to protecting passwords from eavesdropping. The only mention of non-LDAPDN authentication identities in the early parts of these documents are in reference to using these non-LDAPDN identities as authorization identities for backward compatibility with non-LDAP authentication mechanisms.

Since RFC 2829 is a largely a SASL profile, I wouldn't expect it
to discuss LDAPDNs except in contexts where SASL allows application
profiles to use application specific forms of identities.

However, RFC 2829 is fairly clear when it states (very early):
   An authentication identity is the name presented in a credential.

   There are many forms of authentication credentials -- the form used
   depends upon the particular authentication mechanism negotiated by
   the parties.  For example: X.509 certificates, Kerberos tickets,     
   simple identity and password pairs.  Note that an authentication     
   mechanism may constrain the form of authentication identities used   
   with it.

In DIGEST-MD5 clearly constrains the form of the authentication
identity to a simple identity string, a user name.

>You are suggesting DIGEST-MD5 and other SASL mechanisms were introduced for other than reasons related to security considerations and yet all the text in the documents introducing these mechanisms into LDAP indicate the reasons are security related and for backwards-compatibility only.

I am suggesting that RFC 2829 recommends implementation of
simple bind over TLS to support DN/password credentials.
But it requires implementation of DIGEST-MD5 to support
username/password credentials.

However, regardless of this, it should be clear that stuffing
LDAPDNs into usernames is not a path to interoperability nor
security.  Matching issues alone should be enough to kill that
idea.  We cannot morph DIGEST-MD5 into something its not, that
breaks mechanism commonality between application protocols.
We needed to use each mechanism in a manner consistent with
its specification.

Going forward, it would be much better to clarify that simple
+TLS is to be used for DN/password credentials and DIGEST-MD5
(or PLAIN+TLS) be used for username/password credentials.

I note that due to the specification and interoperability problems
with DIGEST-MD5 (not just with LDAP), I would not be opposed to
changing the mandatory-to-implement authentication mechanism
from DIGEST-MD5 to simple+TLS.

Kurt

PS: I was once suggested in an I-D how one could stuff DNs
into DIGEST-MD5 credentials, it got no where.  See LDAPEXT
archives.





From owner-ietf-ldapbis@OpenLDAP.org  Mon May 12 23:39:22 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 XAA13258
	for <ldapbis-archive@lists.ietf.org>; Mon, 12 May 2003 23:39: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 h4D3QKF9001040;
	Tue, 13 May 2003 03:41:17 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 h4D3HSt4000151;
	Tue, 13 May 2003 03:17:28 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 13 May 2003 03:17: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 h4D3HQEh000138
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 13 May 2003 03:17: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 h4D3HPc6074542;
	Tue, 13 May 2003 03:17:25 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030512195717.02923988@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Mon, 12 May 2003 20:14:49 -0700
To: "Ramsay, Ron" <Ron.Ramsay@ca.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Simple+TLS as mandatory-to-implement (RE: Issues with current
  authmeth draft.)
Cc: <ietf-ldapbis@OpenLDAP.org>
In-Reply-To: <1395B4B334FCC143B36AF788E68B6381105F69@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:25 PM 5/12/2003, Ramsay, Ron wrote:
>I don't believe you can mandate simple/TLS!

I certainly cannot mandate it.  But the IETF certainly can. 

>At the time RFC 2829 was debated, a large number on the WG wanted this. They did not get their way because of the complexity of the solution. It was argued that a password-based method would be better. I think they believed it would still be DN/password, though. 

I think clear from this discussion that some folks didn't
get what they thought they were getting.

If one takes the view that RFC 2829 intended DNs in DIGEST-MD5
user names, than RFC 2829 is serious broken.  DNs in DIGEST-MD5
is not workable.  So, it would be quite reasonable to open a
discussion on choosing a different mandatory-to-implement strong
authentication mechanism.

If one takes the view that RFC 2829 intended user name in
DIGEST-MD5 user names, then RFC 2829 just needs some clarification.
However, since significant specification and interoperability issues
exist with DIGEST-MD5, it would be reasonable here to open a
discussion on choosing a different mandatory-to-implement strong
authentication method.

At this point, I (as co-chair), consider the issue open.

Kurt 



From owner-ietf-ldapbis@OpenLDAP.org  Mon May 12 23:40: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 XAA13297
	for <ldapbis-archive@lists.ietf.org>; Mon, 12 May 2003 23:40:40 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4D3cKEp002288;
	Tue, 13 May 2003 03:42:46 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 h4D3c4xk002223;
	Tue, 13 May 2003 03:38:04 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 13 May 2003 03:38:04 +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 h4D3c1Eh002107
	for <ietf-ldapbis@openldap.org>; Tue, 13 May 2003 03:38:02 GMT
	(envelope-from mark.ennis@adacel.com)
Received: from nexus.adacel.com (Not Verified[10.32.240.1]) by adacel.com with MailMarshal (v5,0,3,91)
	id <B000064dd6>; Tue, 13 May 2003 13:34:34 +1000
Received: (qmail 25227 invoked from network); 13 May 2003 03:37:39 -0000
Received: from unknown (HELO adacel.com) (10.32.24.164)
  by nexus.adacel.com with SMTP; 13 May 2003 03:37:39 -0000
Message-ID: <3EC06882.2070704@adacel.com>
Date: Tue, 13 May 2003 13:37:38 +1000
From: Mark Ennis <mark.ennis@adacel.com>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Roger Harrison <RHARRISON@novell.com>
CC: Kurt@OpenLDAP.org, Ron.Ramsay@ca.com, ietf-ldapbis@OpenLDAP.org
Subject: Re: Issues with current authmeth draft.
References: <sebffec6.051@prv-mail20.provo.novell.com>
In-Reply-To: <sebffec6.051@prv-mail20.provo.novell.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

Roger,

I am not convinced at this stage that the text under discussion needs to 
be revised. We also have the problem that "clarification" of this text 
could lead to backward compatibility problems with pre-LDAPbis systems 
as we are potentially changing assumption on which the remaining text 
has, in the past, been interpreted. Particularly given that the text 
from the [authmeth] introduction has re-iterated the same points made in 
RFC2829 *1. Introduction*.

However, that said, I was referencing the following:

The [authmeth] text in *2. Introduction* discusses the security 
considerations for LDAP, identifying a set of basic threats and then the 
security mechanisms proposed to minimise these risks, including use of 
SASL and TLS.

The [authmeth] text in *3. Rationale for LDAPv3 Security Mechanisms* 
discusses the desirability for identities to take the form of 
distinguished names and authentication data to be stored in the 
directory. It also suggests support for non-LDAPDN authorization 
identities should be supported for backward-compatibility with 
non-LDAP-based authentication services.

- Mark.

Roger Harrison wrote:
> Mark,
>  
> Would you please  provide a pointer to the text describing the 
> "reasons... for introducing SASL mechanisms..." that you are referring 
> to so that I can make appropriate changes.
>  
> Thanks,
>  
> Roger
> 
>  >>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 5/12/2003 7:14:39 PM >>>
> At 05:08 PM 5/12/2003, Mark Ennis wrote:
>  >This seems counter to the reasons in RFC2829 and [authmeth] for 
> introducing SASL mechanisms, in particular, SASL DIGEST-MD5.
> 
> Well then we should clarify the rationale.
> 
> Kurt
> 
> 



From owner-ietf-ldapbis@OpenLDAP.org  Tue May 13 01:00:36 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 BAA15067
	for <ldapbis-archive@lists.ietf.org>; Tue, 13 May 2003 01:00:35 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4D4iLEt009266;
	Tue, 13 May 2003 05:02:33 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 h4D4d1mG008710;
	Tue, 13 May 2003 04:39:01 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 13 May 2003 04:39:01 +0000
Received: from ausyms50.ca.com ([155.35.248.106])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4D4cvEh008628;
	Tue, 13 May 2003 04:38:57 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, 13 May 2003 14:38:34 +1000
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: Simple+TLS as mandatory-to-implement (RE: Issues with current  authmeth draft.)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
Date: Tue, 13 May 2003 14:38:33 +1000
Message-ID: <1395B4B334FCC143B36AF788E68B638110620E@ausyms21.ca.com>
Thread-Topic: Simple+TLS as mandatory-to-implement (RE: Issues with current  authmeth draft.)
Thread-Index: AcMY/i/2BXmojYuITZSegWGTOSJ+MgACshpQ
From: "Ramsay, Ron" <Ron.Ramsay@ca.com>
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Cc: <ietf-ldapbis@OpenLDAP.org>
X-OriginalArrivalTime: 13 May 2003 04:38:34.0122 (UTC) FILETIME=[8316DEA0:01C31909]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by boole.openldap.org id h4D4cwEh008675
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 guess te time for history is now passed, btu I would like to note that the date on the RFC is May 2000 and that SASL profiling is a very recent occurrence. It wpuld be interesting to hear from, say, Paul Leech, what he thought he was arguing for, or even from the authors of the RFC.

I note that LDAPbis cannot change the LDAP specification, but do you see it as possible to change the mandatory-to-implement authentication method? I note that RFC 2829 is on the Standards Track.

Ron

-----Original Message-----
From: Kurt D. Zeilenga [mailto:Kurt@OpenLDAP.org]
Sent: Tuesday, 13 May 2003 13:15
To: Ramsay, Ron
Cc: ietf-ldapbis@OpenLDAP.org
Subject: Simple+TLS as mandatory-to-implement (RE: Issues with current
authmeth draft.)


At 07:25 PM 5/12/2003, Ramsay, Ron wrote:
>I don't believe you can mandate simple/TLS!

I certainly cannot mandate it.  But the IETF certainly can. 

>At the time RFC 2829 was debated, a large number on the WG wanted this. They did not get their way because of the complexity of the solution. It was argued that a password-based method would be better. I think they believed it would still be DN/password, though. 

I think clear from this discussion that some folks didn't
get what they thought they were getting.

If one takes the view that RFC 2829 intended DNs in DIGEST-MD5
user names, than RFC 2829 is serious broken.  DNs in DIGEST-MD5
is not workable.  So, it would be quite reasonable to open a
discussion on choosing a different mandatory-to-implement strong
authentication mechanism.

If one takes the view that RFC 2829 intended user name in
DIGEST-MD5 user names, then RFC 2829 just needs some clarification.
However, since significant specification and interoperability issues
exist with DIGEST-MD5, it would be reasonable here to open a
discussion on choosing a different mandatory-to-implement strong
authentication method.

At this point, I (as co-chair), consider the issue open.

Kurt 





From owner-ietf-ldapbis@OpenLDAP.org  Tue May 13 01:48: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 ESMTP id BAA16097
	for <ldapbis-archive@lists.ietf.org>; Tue, 13 May 2003 01:48:54 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4D5oLEl016997;
	Tue, 13 May 2003 05:50:41 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 h4D5ia8R016283;
	Tue, 13 May 2003 05:44:36 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 13 May 2003 05:44:36 +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 h4D5iWEh016265
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 13 May 2003 05:44:32 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 h4D5iNc6075329;
	Tue, 13 May 2003 05:44:24 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030512222623.02a3d6f0@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Mon, 12 May 2003 22:41:47 -0700
To: "Ramsay, Ron" <Ron.Ramsay@ca.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: RE: Simple+TLS as mandatory-to-implement (RE: Issues with
  current  authmeth draft.)
Cc: <ietf-ldapbis@OpenLDAP.org>
In-Reply-To: <1395B4B334FCC143B36AF788E68B638110620E@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 09:38 PM 5/12/2003, Ramsay, Ron wrote:
>I note that LDAPbis cannot change the LDAP specification,

We certainly can change, within certain limits, the LDAP
technical specification.  See our charter.

>but do you see it as possible to change the mandatory-to-implement authentication method?

Yes.  Changing an elective feature to be mandatory-to-implement
is quite possible.  However, such changes should not be made lightly.

Kurt 



From owner-ietf-ldapbis@OpenLDAP.org  Tue May 13 02:47:40 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 CAA29121
	for <ldapbis-archive@lists.ietf.org>; Tue, 13 May 2003 02:47:40 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4D6cLF7022948;
	Tue, 13 May 2003 06:49:25 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 h4D6aHQF022656;
	Tue, 13 May 2003 06:36:17 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 13 May 2003 06:36:17 +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 h4D6aEEh022565
	for <ietf-ldapbis@openldap.org>; Tue, 13 May 2003 06:36:15 GMT
	(envelope-from mark.ennis@adacel.com)
Received: from nexus.adacel.com (Not Verified[10.32.240.1]) by adacel.com with MailMarshal (v5,0,3,91)
	id <B0000651f1>; Tue, 13 May 2003 16:32:46 +1000
Received: (qmail 18246 invoked from network); 13 May 2003 06:35:53 -0000
Received: from unknown (HELO adacel.com) (10.32.24.164)
  by nexus.adacel.com with SMTP; 13 May 2003 06:35:53 -0000
Message-ID: <3EC09245.6070408@adacel.com>
Date: Tue, 13 May 2003 16:35:49 +1000
From: Mark Ennis <mark.ennis@adacel.com>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
CC: "Ramsay, Ron" <Ron.Ramsay@ca.com>, ietf-ldapbis@OpenLDAP.org
Subject: Re: Simple+TLS as mandatory-to-implement (RE: Issues with current
  authmeth draft.)
References: <5.2.0.9.0.20030512195717.02923988@127.0.0.1>
In-Reply-To: <5.2.0.9.0.20030512195717.02923988@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,

Having reviewed RFC2222 and RFC2831, I do not accept your assertion that 
the username field in the SASL DIGEST-MD5 protocol messages is 
constrained to a simple representation as might be found in a Unix or MS 
Windows style username/password authentication mechanism and excludes 
the use of a LDAPDN.

RFC2222 only appears to directly address the identity in the 
authentication credentials in *3. Introduction and Overview*, paragraph 7:
    The transmitted authorization identity may be different than the
    identity in the client's authentication credentials.  This permits
    agents such as proxy servers to authenticate using their own
    credentials, yet request the access privileges of the identity for
    which they are proxying.  With any mechanism, transmitting an
    authorization identity of the empty string directs the server to
    derive an authorization identity from the client's authentication
    credentials.

The example regarding proxy servers actually *implies* that the 
difference permitted between authentication and authorization identity 
is a difference in identity asserted rather than a difference in form of 
the identity.

The only support for a difference in form of authentication and 
authorization identities is *implied* by the section on profiling 
requirements which requires a SASL profile to specify how the 
authorization identity should be interpreted. This section in no way 
prohibits a profile from also optionally providing a specification on 
how authentication credentials or authentication identity may be 
interpreted.

A review of draft-ietf-sasl-rfc2831bis-00.txt does indicate a problem 
which is the requirement to normalize the username-val content into 
Unicode Normalization Form KC 
[http://www.unicode.org/unicode/reports/tr15/]. Requiring the content of 
the username-val to be normalized in this way would certainly 
potentially change the semantics of a string which happened to be a 
LDAPDN. However, the purpose of this normalization is to provide 
consistent matching (in this case making sure that different 
implementations will generate the same digest). This could equally well 
be accomplished by moving the requirement to normalize the values to the 
point at which the values are used to generate the digest instead of 
requiring them to be normalized in the protocol message. Having not been 
a subscriber to the SASL mailing lists, I do not claim to know if this 
alternative approach has been considered and discarded for some reason, 
but I would certainly be interested in a reference to this discussion if 
it occurred.

I get the feeling that you view the SASL authentication as a way of 
having a single authentication server for a number of different 
applications of which LDAP is but one. I can see this view has benefits, 
however, I do not think RFC2222 in any way requires this model and I do 
not see that accepting the use of LDAPDN as a possible value to include 
in the username-val field in the SASL DIGEST-MD5 protocol necessarily 
breaks this model, provided the LDAP specification [authmeth] permits 
other forms of the username also.

Should the general opinion support the view that LDAPDN and DIGEST-MD5 
are absolutely incompatible, then I would propose defining a variation 
on DIGEST-MD5 for LDAP, possibly using an algorithm value other than 
"md5-sess", e.g. "md5-ldap", which uses the authzid syntax to encode the 
  username-val and introduces the Unicode Normalization Form KC at the 
point where the digests are being generated rather than where 
draft-ietf-sasl-rfc2831bis-00.txt is doing this.

- Mark.

Kurt D. Zeilenga wrote:
> At 07:25 PM 5/12/2003, Ramsay, Ron wrote:
> 
>>I don't believe you can mandate simple/TLS!
> 
> 
> I certainly cannot mandate it.  But the IETF certainly can. 
> 
> 
>>At the time RFC 2829 was debated, a large number on the WG wanted this. They did not get their way because of the complexity of the solution. It was argued that a password-based method would be better. I think they believed it would still be DN/password, though. 
> 
> 
> I think clear from this discussion that some folks didn't
> get what they thought they were getting.
> 
> If one takes the view that RFC 2829 intended DNs in DIGEST-MD5
> user names, than RFC 2829 is serious broken.  DNs in DIGEST-MD5
> is not workable.  So, it would be quite reasonable to open a
> discussion on choosing a different mandatory-to-implement strong
> authentication mechanism.
> 
> If one takes the view that RFC 2829 intended user name in
> DIGEST-MD5 user names, then RFC 2829 just needs some clarification.
> However, since significant specification and interoperability issues
> exist with DIGEST-MD5, it would be reasonable here to open a
> discussion on choosing a different mandatory-to-implement strong
> authentication method.
> 
> At this point, I (as co-chair), consider the issue open.
> 
> Kurt 
> 
> 
> 



From owner-ietf-ldapbis@OpenLDAP.org  Tue May 13 03:45: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 ESMTP id DAA29968
	for <ldapbis-archive@lists.ietf.org>; Tue, 13 May 2003 03:45:27 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4D7WMFV030388;
	Tue, 13 May 2003 07:47:06 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 h4D7Qh5c029372;
	Tue, 13 May 2003 07:26:43 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 13 May 2003 07:26:43 +0000
Received: from ausyms50.ca.com ([155.35.248.106])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4D7QcEh029296;
	Tue, 13 May 2003 07:26: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);
	 Tue, 13 May 2003 17:26:24 +1000
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: Simple+TLS as mandatory-to-implement (RE: Issues with current  authmeth draft.)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
Date: Tue, 13 May 2003 17:26:23 +1000
Message-ID: <1395B4B334FCC143B36AF788E68B6381106546@ausyms21.ca.com>
Thread-Topic: Simple+TLS as mandatory-to-implement (RE: Issues with current  authmeth draft.)
Thread-Index: AcMZGergVONsqLHRRHKR+o8TuYf2tAAAZx9A
From: "Ramsay, Ron" <Ron.Ramsay@ca.com>
To: "Mark Ennis" <mark.ennis@adacel.com>,
        "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Cc: <ietf-ldapbis@OpenLDAP.org>
X-OriginalArrivalTime: 13 May 2003 07:26:24.0245 (UTC) FILETIME=[F559B250:01C31920]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by boole.openldap.org id h4D7QdEh029335
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 Mark,

I thought Kurt made a specific objection to LDAP-DN, which is that it can have different values which match. I assume the protocol exchange is

C: (nothing)
S: challenge
C: hash(hash(username+realm+password)+challenge), username

If this is the case, the server will have to use the client-supplied DN to verify the response. One would not normally depend on the client normalising the DN (if this could be done unambiguously), so the server is prevented from storing the prehash, that is, passwords would have to be stored in the clear.

Ron

----Original Message-----
From: Mark Ennis [mailto:mark.ennis@adacel.com]
Sent: Tuesday, 13 May 2003 16:36
To: Kurt D. Zeilenga
Cc: Ramsay, Ron; ietf-ldapbis@OpenLDAP.org
Subject: Re: Simple+TLS as mandatory-to-implement (RE: Issues with
current authmeth draft.)


Kurt,

Having reviewed RFC2222 and RFC2831, I do not accept your assertion that 
the username field in the SASL DIGEST-MD5 protocol messages is 
constrained to a simple representation as might be found in a Unix or MS 
Windows style username/password authentication mechanism and excludes 
the use of a LDAPDN.

RFC2222 only appears to directly address the identity in the 
authentication credentials in *3. Introduction and Overview*, paragraph 7:
    The transmitted authorization identity may be different than the
    identity in the client's authentication credentials.  This permits
    agents such as proxy servers to authenticate using their own
    credentials, yet request the access privileges of the identity for
    which they are proxying.  With any mechanism, transmitting an
    authorization identity of the empty string directs the server to
    derive an authorization identity from the client's authentication
    credentials.

The example regarding proxy servers actually *implies* that the 
difference permitted between authentication and authorization identity 
is a difference in identity asserted rather than a difference in form of 
the identity.

The only support for a difference in form of authentication and 
authorization identities is *implied* by the section on profiling 
requirements which requires a SASL profile to specify how the 
authorization identity should be interpreted. This section in no way 
prohibits a profile from also optionally providing a specification on 
how authentication credentials or authentication identity may be 
interpreted.

A review of draft-ietf-sasl-rfc2831bis-00.txt does indicate a problem 
which is the requirement to normalize the username-val content into 
Unicode Normalization Form KC 
[http://www.unicode.org/unicode/reports/tr15/]. Requiring the content of 
the username-val to be normalized in this way would certainly 
potentially change the semantics of a string which happened to be a 
LDAPDN. However, the purpose of this normalization is to provide 
consistent matching (in this case making sure that different 
implementations will generate the same digest). This could equally well 
be accomplished by moving the requirement to normalize the values to the 
point at which the values are used to generate the digest instead of 
requiring them to be normalized in the protocol message. Having not been 
a subscriber to the SASL mailing lists, I do not claim to know if this 
alternative approach has been considered and discarded for some reason, 
but I would certainly be interested in a reference to this discussion if 
it occurred.

I get the feeling that you view the SASL authentication as a way of 
having a single authentication server for a number of different 
applications of which LDAP is but one. I can see this view has benefits, 
however, I do not think RFC2222 in any way requires this model and I do 
not see that accepting the use of LDAPDN as a possible value to include 
in the username-val field in the SASL DIGEST-MD5 protocol necessarily 
breaks this model, provided the LDAP specification [authmeth] permits 
other forms of the username also.

Should the general opinion support the view that LDAPDN and DIGEST-MD5 
are absolutely incompatible, then I would propose defining a variation 
on DIGEST-MD5 for LDAP, possibly using an algorithm value other than 
"md5-sess", e.g. "md5-ldap", which uses the authzid syntax to encode the 
  username-val and introduces the Unicode Normalization Form KC at the 
point where the digests are being generated rather than where 
draft-ietf-sasl-rfc2831bis-00.txt is doing this.

- Mark.

Kurt D. Zeilenga wrote:
> At 07:25 PM 5/12/2003, Ramsay, Ron wrote:
> 
>>I don't believe you can mandate simple/TLS!
> 
> 
> I certainly cannot mandate it.  But the IETF certainly can. 
> 
> 
>>At the time RFC 2829 was debated, a large number on the WG wanted this. They did not get their way because of the complexity of the solution. It was argued that a password-based method would be better. I think they believed it would still be DN/password, though. 
> 
> 
> I think clear from this discussion that some folks didn't
> get what they thought they were getting.
> 
> If one takes the view that RFC 2829 intended DNs in DIGEST-MD5
> user names, than RFC 2829 is serious broken.  DNs in DIGEST-MD5
> is not workable.  So, it would be quite reasonable to open a
> discussion on choosing a different mandatory-to-implement strong
> authentication mechanism.
> 
> If one takes the view that RFC 2829 intended user name in
> DIGEST-MD5 user names, then RFC 2829 just needs some clarification.
> However, since significant specification and interoperability issues
> exist with DIGEST-MD5, it would be reasonable here to open a
> discussion on choosing a different mandatory-to-implement strong
> authentication method.
> 
> At this point, I (as co-chair), consider the issue open.
> 
> Kurt 
> 
> 
> 





From owner-ietf-ldapbis@OpenLDAP.org  Tue May 13 12:02:00 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 MAA18158
	for <ldapbis-archive@lists.ietf.org>; Tue, 13 May 2003 12:01:59 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4DFcTFZ007116;
	Tue, 13 May 2003 16:02:52 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 h4DFYSEF005927;
	Tue, 13 May 2003 15:34:28 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 13 May 2003 15:34: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 h4DFYQEh005912
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 13 May 2003 15:34:26 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 h4DFYCc6079307;
	Tue, 13 May 2003 15:34:18 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030513074355.029edd18@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Tue, 13 May 2003 08:31:26 -0700
To: Mark Ennis <mark.ennis@adacel.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: Simple+TLS as mandatory-to-implement (RE: Issues with
  current authmeth draft.)
Cc: ietf-ldapbis@OpenLDAP.org
In-Reply-To: <3EC09245.6070408@adacel.com>
References: <5.2.0.9.0.20030512195717.02923988@127.0.0.1>
 <5.2.0.9.0.20030512195717.02923988@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 11:35 PM 5/12/2003, Mark Ennis wrote:
>Having reviewed RFC2222 and RFC2831, I do not accept your assertion that the username field in the SASL DIGEST-MD5 protocol messages is constrained to a simple representation as might be found in a Unix or MS Windows style username/password authentication mechanism and excludes the use of a LDAPDN.

Neither did they account for LDAPDNs being used.  I believe
subsequent revision of RFC 2831 will make it very clear that
the DIGEST-MD5 is a user name.  To get an idea of where they
are going, you might read draft-ietf-sasl-saslprep.

Anyways, the fact is that many LDAP implementations support
DIGEST-MD5 using simple user names and passwords consistently
with the current specifications and revisions being discussed
in the SASL WG.  So changing the specifications in ways that
would break these existing implementations can only be done
with very good reasons.

Now, you argue that you have existing implementations which
do it a different way and specifications should be changed
to accommodate you.  The reasons you have stated so far are,
simply, not good enough.

Applications which have DN/password credentials should just
use simple+TLS as discussed in RFC 2829.

Also, I note that if you have comment regarding the revision
of RFC 2222, RFC 2831, or any other SASL framework/mechanism
technical specification, I suggest you take them to the SASL
WG.  They own the SASL revision work.

Kurt 



From owner-ietf-ldapbis@OpenLDAP.org  Tue May 13 14:53:17 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 OAA24274
	for <ldapbis-archive@lists.ietf.org>; Tue, 13 May 2003 14:53:13 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4DIoPEp041661;
	Tue, 13 May 2003 18:53:55 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 h4DInGe3041450;
	Tue, 13 May 2003 18:49:16 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 13 May 2003 18:49:16 +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 h4DInFEh041437
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 13 May 2003 18:49:15 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 h4DInFc6081444
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 13 May 2003 18:49:15 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030513112751.02aa1e08@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Tue, 13 May 2003 11:38:27 -0700
To: ietf-ldapbis@OpenLDAP.org
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: T.61 -> Unicode mapping
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>

One of the holes which needs to filled in the proposal
for Internationalization of X.500/LDAP Matching Rules
is a specification of the algorithm for mapping T.61
characters to Unicode characters.

Does anyone have a reference to a suitable algorithm?
If not, anyone willing to detail a suitable algorithm?

Kurt



From owner-ietf-ldapbis@OpenLDAP.org  Tue May 13 15:47:27 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 PAA27344
	for <ldapbis-archive@lists.ietf.org>; Tue, 13 May 2003 15:47: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 h4DJcQFJ051518;
	Tue, 13 May 2003 19:49:32 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 h4DJZonq050989;
	Tue, 13 May 2003 19:35:50 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 13 May 2003 19:35:50 +0000
Received: from carnelian.propagation.net (carnelian.propagation.net [209.164.120.1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4DJZKEh050850;
	Tue, 13 May 2003 19:35:20 GMT
	(envelope-from hyc@highlandsun.com)
Received: from CELLO (c-24-126-120-178.we.client2.attbi.com [24.126.120.178])
	by carnelian.propagation.net (8.9.3p2/8.8.5) with SMTP id OAA01533;
	Tue, 13 May 2003 14:35:14 -0500
From: "Howard Chu" <hyc@highlandsun.com>
To: "'Kurt D. Zeilenga'" <Kurt@OpenLDAP.org>, <ietf-ldapbis@OpenLDAP.org>
Subject: RE: T.61 -> Unicode mapping
Date: Tue, 13 May 2003 12:35:01 -0700
Message-ID: <006201c31986$c63ca0c0$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.2600.0000
In-reply-To: <5.2.0.9.0.20030513112751.02aa1e08@127.0.0.1>
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

> -----Original Message-----
> From: owner-ietf-ldapbis@OpenLDAP.org
> [mailto:owner-ietf-ldapbis@OpenLDAP.org]On Behalf Of Kurt D. Zeilenga

> One of the holes which needs to filled in the proposal
> for Internationalization of X.500/LDAP Matching Rules
> is a specification of the algorithm for mapping T.61
> characters to Unicode characters.
>
> Does anyone have a reference to a suitable algorithm?
> If not, anyone willing to detail a suitable algorithm?

I wrote a pretty good mapping in OpenLDAP's libldap/t61.c.

Part of the problem is that older software used "T.61" as "arbitrary 8-bit
text" and so used character values that don't exist in the actual T.61
definition. Of course, the T.61 definition was lacking some pretty essential
character codes to begin with, so this distortion of the spec is somewhat
unavoidable.

  -- 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 May 13 18:55:13 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 SAA03146
	for <ldapbis-archive@lists.ietf.org>; Tue, 13 May 2003 18:55:13 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4DMuREl083625;
	Tue, 13 May 2003 22:56:52 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 h4DMrKiL083233;
	Tue, 13 May 2003 22:53:20 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 13 May 2003 22:53:20 +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 h4DMrGEh083170
	for <ietf-ldapbis@openldap.org>; Tue, 13 May 2003 22:53:17 GMT
	(envelope-from mark.ennis@adacel.com)
Received: from nexus.adacel.com (Not Verified[10.32.240.1]) by adacel.com with MailMarshal (v5,0,3,91)
	id <B000066255>; Wed, 14 May 2003 08:50:43 +1000
Received: (qmail 1321 invoked from network); 13 May 2003 22:52:54 -0000
Received: from unknown (HELO adacel.com) (10.32.24.164)
  by nexus.adacel.com with SMTP; 13 May 2003 22:52:54 -0000
Message-ID: <3EC17745.3030506@adacel.com>
Date: Wed, 14 May 2003 08:52:53 +1000
From: Mark Ennis <mark.ennis@adacel.com>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Ramsay, Ron" <Ron.Ramsay@ca.com>
CC: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>, ietf-ldapbis@OpenLDAP.org
Subject: Re: Simple+TLS as mandatory-to-implement (RE: Issues with current
  authmeth draft.)
References: <1395B4B334FCC143B36AF788E68B6381106546@ausyms21.ca.com>
In-Reply-To: <1395B4B334FCC143B36AF788E68B6381106546@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,

I agree that there is a problem for systems which wish to use the LDAPDN 
as the username-val and yet store the A1 hash. As you mention, it is 
necessary to use the client supplied DN when forming the digest to 
ensure the digests will match. There is also a problem for such systems 
if they attempt to rename or move the entry, thus changing the DN name 
of the entry and invalidating the stored A1 hash (and effectively 
discarding the stored knowledge on the shared secret).

- Mark.

Ramsay, Ron wrote:
> Hi Mark,
> 
> I thought Kurt made a specific objection to LDAP-DN, which is that it can have different values which match. I assume the protocol exchange is
> 
> C: (nothing)
> S: challenge
> C: hash(hash(username+realm+password)+challenge), username
> 
> If this is the case, the server will have to use the client-supplied DN to verify the response. One would not normally depend on the client normalising the DN (if this could be done unambiguously), so the server is prevented from storing the prehash, that is, passwords would have to be stored in the clear.
> 
> Ron
> 
> ----Original Message-----
> From: Mark Ennis [mailto:mark.ennis@adacel.com]
> Sent: Tuesday, 13 May 2003 16:36
> To: Kurt D. Zeilenga
> Cc: Ramsay, Ron; ietf-ldapbis@OpenLDAP.org
> Subject: Re: Simple+TLS as mandatory-to-implement (RE: Issues with
> current authmeth draft.)
> 
> 
> Kurt,
> 
> Having reviewed RFC2222 and RFC2831, I do not accept your assertion that 
> the username field in the SASL DIGEST-MD5 protocol messages is 
> constrained to a simple representation as might be found in a Unix or MS 
> Windows style username/password authentication mechanism and excludes 
> the use of a LDAPDN.
> 
> RFC2222 only appears to directly address the identity in the 
> authentication credentials in *3. Introduction and Overview*, paragraph 7:
>     The transmitted authorization identity may be different than the
>     identity in the client's authentication credentials.  This permits
>     agents such as proxy servers to authenticate using their own
>     credentials, yet request the access privileges of the identity for
>     which they are proxying.  With any mechanism, transmitting an
>     authorization identity of the empty string directs the server to
>     derive an authorization identity from the client's authentication
>     credentials.
> 
> The example regarding proxy servers actually *implies* that the 
> difference permitted between authentication and authorization identity 
> is a difference in identity asserted rather than a difference in form of 
> the identity.
> 
> The only support for a difference in form of authentication and 
> authorization identities is *implied* by the section on profiling 
> requirements which requires a SASL profile to specify how the 
> authorization identity should be interpreted. This section in no way 
> prohibits a profile from also optionally providing a specification on 
> how authentication credentials or authentication identity may be 
> interpreted.
> 
> A review of draft-ietf-sasl-rfc2831bis-00.txt does indicate a problem 
> which is the requirement to normalize the username-val content into 
> Unicode Normalization Form KC 
> [http://www.unicode.org/unicode/reports/tr15/]. Requiring the content of 
> the username-val to be normalized in this way would certainly 
> potentially change the semantics of a string which happened to be a 
> LDAPDN. However, the purpose of this normalization is to provide 
> consistent matching (in this case making sure that different 
> implementations will generate the same digest). This could equally well 
> be accomplished by moving the requirement to normalize the values to the 
> point at which the values are used to generate the digest instead of 
> requiring them to be normalized in the protocol message. Having not been 
> a subscriber to the SASL mailing lists, I do not claim to know if this 
> alternative approach has been considered and discarded for some reason, 
> but I would certainly be interested in a reference to this discussion if 
> it occurred.
> 
> I get the feeling that you view the SASL authentication as a way of 
> having a single authentication server for a number of different 
> applications of which LDAP is but one. I can see this view has benefits, 
> however, I do not think RFC2222 in any way requires this model and I do 
> not see that accepting the use of LDAPDN as a possible value to include 
> in the username-val field in the SASL DIGEST-MD5 protocol necessarily 
> breaks this model, provided the LDAP specification [authmeth] permits 
> other forms of the username also.
> 
> Should the general opinion support the view that LDAPDN and DIGEST-MD5 
> are absolutely incompatible, then I would propose defining a variation 
> on DIGEST-MD5 for LDAP, possibly using an algorithm value other than 
> "md5-sess", e.g. "md5-ldap", which uses the authzid syntax to encode the 
>   username-val and introduces the Unicode Normalization Form KC at the 
> point where the digests are being generated rather than where 
> draft-ietf-sasl-rfc2831bis-00.txt is doing this.
> 
> - Mark.
> 
> Kurt D. Zeilenga wrote:
> 
>>At 07:25 PM 5/12/2003, Ramsay, Ron wrote:
>>
>>
>>>I don't believe you can mandate simple/TLS!
>>
>>
>>I certainly cannot mandate it.  But the IETF certainly can. 
>>
>>
>>
>>>At the time RFC 2829 was debated, a large number on the WG wanted this. They did not get their way because of the complexity of the solution. It was argued that a password-based method would be better. I think they believed it would still be DN/password, though. 
>>
>>
>>I think clear from this discussion that some folks didn't
>>get what they thought they were getting.
>>
>>If one takes the view that RFC 2829 intended DNs in DIGEST-MD5
>>user names, than RFC 2829 is serious broken.  DNs in DIGEST-MD5
>>is not workable.  So, it would be quite reasonable to open a
>>discussion on choosing a different mandatory-to-implement strong
>>authentication mechanism.
>>
>>If one takes the view that RFC 2829 intended user name in
>>DIGEST-MD5 user names, then RFC 2829 just needs some clarification.
>>However, since significant specification and interoperability issues
>>exist with DIGEST-MD5, it would be reasonable here to open a
>>discussion on choosing a different mandatory-to-implement strong
>>authentication method.
>>
>>At this point, I (as co-chair), consider the issue open.
>>
>>Kurt 
>>
>>
>>
> 
> 
> 
> 
> 



From owner-ietf-ldapbis@OpenLDAP.org  Wed May 14 00:43:47 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 AAA09843
	for <ldapbis-archive@lists.ietf.org>; Wed, 14 May 2003 00:43: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 h4E4iTEl025649;
	Wed, 14 May 2003 04:45: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 h4E4iRCs025631;
	Wed, 14 May 2003 04:44:27 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 14 May 2003 04:44:27 +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 h4E4iNEh025582
	for <ietf-ldapbis@openldap.org>; Wed, 14 May 2003 04:44:25 GMT
	(envelope-from mark.ennis@adacel.com)
Received: from nexus.adacel.com (Not Verified[10.32.240.1]) by adacel.com with MailMarshal (v5,0,3,91)
	id <B000066c68>; Wed, 14 May 2003 14:41:50 +1000
Received: (qmail 26571 invoked from network); 14 May 2003 04:44:03 -0000
Received: from unknown (HELO adacel.com) (10.32.24.164)
  by nexus.adacel.com with SMTP; 14 May 2003 04:44:03 -0000
Message-ID: <3EC1C98F.1040806@adacel.com>
Date: Wed, 14 May 2003 14:43:59 +1000
From: Mark Ennis <mark.ennis@adacel.com>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
CC: ietf-ldapbis@OpenLDAP.org
Subject: Re: Simple+TLS as mandatory-to-implement (RE: Issues with  current
 authmeth draft.)
References: <5.2.0.9.0.20030512195717.02923988@127.0.0.1> <5.2.0.9.0.20030512195717.02923988@127.0.0.1> <5.2.0.9.0.20030513074355.029edd18@127.0.0.1>
In-Reply-To: <5.2.0.9.0.20030513074355.029edd18@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 is my opinion that RFC2829 intended to continue to use the LDAPDN as 
the primary authentication identity, including when using SASL 
DIGEST-MD5 mechanism. I believe I am not alone in this interpretation of 
RFC2829 and this view seems to be supported by text in the current 
[authmeth] draft.

It is clear that you disagree with my view and that current development 
of the SASL specifications will move the SASL specifications in a 
direction which would not support my interpretation of RFC2829.

Both sides of the argument have been expressed in detail and there is no 
point in continuing the discussion.

My original concern that the [authmeth] draft does not sufficiently 
address the issue of authentication identity seems to have been 
adequately demonstrated.

With regards to an alternative mandatory-to-implement authentication 
mechanism which is more secure than using cleartext passwords, I would 
like to see one which allows for distinguished names as one form of the 
authentication identity, but would be reluctant to support mandatory 
implementation of startTLS extended operation to achieve this if it can 
be avoided.

- Mark.

Kurt D. Zeilenga wrote:
> At 11:35 PM 5/12/2003, Mark Ennis wrote:
> 
>>Having reviewed RFC2222 and RFC2831, I do not accept your assertion that the username field in the SASL DIGEST-MD5 protocol messages is constrained to a simple representation as might be found in a Unix or MS Windows style username/password authentication mechanism and excludes the use of a LDAPDN.
> 
> 
> Neither did they account for LDAPDNs being used.  I believe
> subsequent revision of RFC 2831 will make it very clear that
> the DIGEST-MD5 is a user name.  To get an idea of where they
> are going, you might read draft-ietf-sasl-saslprep.
> 
> Anyways, the fact is that many LDAP implementations support
> DIGEST-MD5 using simple user names and passwords consistently
> with the current specifications and revisions being discussed
> in the SASL WG.  So changing the specifications in ways that
> would break these existing implementations can only be done
> with very good reasons.
> 
> Now, you argue that you have existing implementations which
> do it a different way and specifications should be changed
> to accommodate you.  The reasons you have stated so far are,
> simply, not good enough.
> 
> Applications which have DN/password credentials should just
> use simple+TLS as discussed in RFC 2829.
> 
> Also, I note that if you have comment regarding the revision
> of RFC 2222, RFC 2831, or any other SASL framework/mechanism
> technical specification, I suggest you take them to the SASL
> WG.  They own the SASL revision work.
> 
> Kurt 
> 
> 
> 



From owner-ietf-ldapbis@OpenLDAP.org  Wed May 14 00:49:09 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 AAA09921
	for <ldapbis-archive@lists.ietf.org>; Wed, 14 May 2003 00:49:09 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4E4oSEl026455;
	Wed, 14 May 2003 04:50:30 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 h4E4k8ve025936;
	Wed, 14 May 2003 04:46:08 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 14 May 2003 04:46:08 +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 h4E4k6Eh025851
	for <ietf-ldapbis@openldap.org>; Wed, 14 May 2003 04:46:07 GMT
	(envelope-from steven.legg@adacel.com.au)
Received: from nexus.adacel.com (Not Verified[10.32.240.1]) by adacel.com with MailMarshal (v5,0,3,91)
	id <B000066c70>; Wed, 14 May 2003 14:43:33 +1000
Received: (qmail 26784 invoked from network); 14 May 2003 04:45:46 -0000
Received: from unknown (HELO osmium) (10.32.24.165)
  by nexus.adacel.com with SMTP; 14 May 2003 04:45:46 -0000
Reply-To: <steven.legg@adacel.com.au>
From: "Steven Legg" <steven.legg@adacel.com.au>
To: <ietf-ldapbis@OpenLDAP.org>
Subject: New Version of ASN.1
Date: Wed, 14 May 2003 14:45:44 +1000
Message-ID: <004301c319d3$ae977060$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,

A new version of ASN.1 has just been released by the ITU and the previous
version withdrawn. The ASN.1 working group of the ITU would like us to
reference the latest version. The new version is fully backward compatible
and I don't see any reason why we shouldn't reference this new version.

The ASN.1 specifications are available on-line for free at:
http://www.itu.int/ITU-T/studygroups/com17/languages/index.html

Regards,
Steven


From owner-ietf-ldapbis@OpenLDAP.org  Wed May 14 10:11: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 KAA19144
	for <ldapbis-archive@lists.ietf.org>; Wed, 14 May 2003 10:11: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 h4EE33F1095617;
	Wed, 14 May 2003 14:10: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 h4EDuD7S095056;
	Wed, 14 May 2003 13:56:13 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 14 May 2003 13:56:13 +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 h4EDuBEh095046
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 14 May 2003 13:56:12 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 h4EDu7c6090625;
	Wed, 14 May 2003 13:56:08 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030514062827.02823dc8@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Wed, 14 May 2003 06:53:29 -0700
To: Mark Ennis <mark.ennis@adacel.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: Simple+TLS as mandatory-to-implement (RE: Issues with 
  current authmeth draft.)
Cc: ietf-ldapbis@OpenLDAP.org
In-Reply-To: <3EC1C98F.1040806@adacel.com>
References: <5.2.0.9.0.20030513074355.029edd18@127.0.0.1>
 <5.2.0.9.0.20030512195717.02923988@127.0.0.1>
 <5.2.0.9.0.20030512195717.02923988@127.0.0.1>
 <5.2.0.9.0.20030513074355.029edd18@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 09:43 PM 5/13/2003, Mark Ennis wrote:
>With regards to an alternative mandatory-to-implement authentication mechanism which is more secure than using cleartext passwords, I would like to see one which allows for distinguished names as one form of the authentication identity, but would be reluctant to support mandatory implementation of startTLS extended operation to achieve this if it can be avoided.

Does your desire to avoiding StartTLS outweigh your desire for
credentials with LDAPDNs?  Or does your desire for credentials
with LDAPDNs outweigh your desire to avoid StartTLS?

Kurt 



From owner-ietf-ldapbis@OpenLDAP.org  Wed May 14 19:08:39 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 TAA09729
	for <ldapbis-archive@lists.ietf.org>; Wed, 14 May 2003 19:08: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 h4EN2ZFJ038283;
	Wed, 14 May 2003 23:10:25 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 h4EMxaOp037812;
	Wed, 14 May 2003 22:59:36 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 14 May 2003 22:59:36 +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 h4EMxWEh037759
	for <ietf-ldapbis@openldap.org>; Wed, 14 May 2003 22:59:33 GMT
	(envelope-from mark.ennis@adacel.com)
Received: from nexus.adacel.com (Not Verified[10.32.240.1]) by adacel.com with MailMarshal (v5,0,3,91)
	id <B000067fc4>; Thu, 15 May 2003 08:56:49 +1000
Received: (qmail 28539 invoked from network); 14 May 2003 22:59:07 -0000
Received: from unknown (HELO adacel.com) (10.32.24.164)
  by nexus.adacel.com with SMTP; 14 May 2003 22:59:07 -0000
Message-ID: <3EC2CA3B.7040509@adacel.com>
Date: Thu, 15 May 2003 08:59:07 +1000
From: Mark Ennis <mark.ennis@adacel.com>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
CC: ietf-ldapbis@OpenLDAP.org
Subject: Re: Simple+TLS as mandatory-to-implement (RE: Issues with   current
 authmeth draft.)
References: <5.2.0.9.0.20030513074355.029edd18@127.0.0.1> <5.2.0.9.0.20030512195717.02923988@127.0.0.1> <5.2.0.9.0.20030512195717.02923988@127.0.0.1> <5.2.0.9.0.20030513074355.029edd18@127.0.0.1> <5.2.0.9.0.20030514062827.02823dc8@127.0.0.1>
In-Reply-To: <5.2.0.9.0.20030514062827.02823dc8@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

My preference is for a digest (or similar challenge/response) 
authentication mechanism which allows distinguished names as a form of 
the authentication identity.

- Mark.

Kurt D. Zeilenga wrote:
> At 09:43 PM 5/13/2003, Mark Ennis wrote:
> 
>>With regards to an alternative mandatory-to-implement authentication mechanism which is more secure than using cleartext passwords, I would like to see one which allows for distinguished names as one form of the authentication identity, but would be reluctant to support mandatory implementation of startTLS extended operation to achieve this if it can be avoided.
> 
> 
> Does your desire to avoiding StartTLS outweigh your desire for
> credentials with LDAPDNs?  Or does your desire for credentials
> with LDAPDNs outweigh your desire to avoid StartTLS?
> 
> Kurt 
> 
> 
> 



From owner-ietf-ldapbis@OpenLDAP.org  Wed May 14 20:00:43 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 UAA10650
	for <ldapbis-archive@lists.ietf.org>; Wed, 14 May 2003 20:00: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 h4F02ZEl041119;
	Thu, 15 May 2003 00: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 h4ENvGmi041033;
	Wed, 14 May 2003 23:57:16 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 14 May 2003 23:57:16 +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 h4ENvFEh041023
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 14 May 2003 23:57:15 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 h4ENvAc6096174;
	Wed, 14 May 2003 23:57:11 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030514164309.02945370@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Wed, 14 May 2003 16:54:33 -0700
To: Mark Ennis <mark.ennis@adacel.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: Simple+TLS as mandatory-to-implement (RE: Issues with  
  current authmeth draft.)
Cc: ietf-ldapbis@OpenLDAP.org
In-Reply-To: <3EC2CA3B.7040509@adacel.com>
References: <5.2.0.9.0.20030514062827.02823dc8@127.0.0.1>
 <5.2.0.9.0.20030513074355.029edd18@127.0.0.1>
 <5.2.0.9.0.20030512195717.02923988@127.0.0.1>
 <5.2.0.9.0.20030512195717.02923988@127.0.0.1>
 <5.2.0.9.0.20030513074355.029edd18@127.0.0.1>
 <5.2.0.9.0.20030514062827.02823dc8@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 03:59 PM 5/14/2003, Mark Ennis wrote:
>My preference is for a digest (or similar challenge/response) authentication mechanism which allows distinguished names as a form of the authentication identity.

Such a mechanism is not available to us.

Kurt 



From owner-ietf-ldapbis@OpenLDAP.org  Wed May 14 20:18: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 UAA10897
	for <ldapbis-archive@lists.ietf.org>; Wed, 14 May 2003 20:18: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 h4F0KZEl041709;
	Thu, 15 May 2003 00:20: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 h4F0HaUa041664;
	Thu, 15 May 2003 00:17:36 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 15 May 2003 00:17:36 +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 h4F0HXEh041623
	for <ietf-ldapbis@openldap.org>; Thu, 15 May 2003 00:17:34 GMT
	(envelope-from mark.ennis@adacel.com)
Received: from nexus.adacel.com (Not Verified[10.32.240.1]) by adacel.com with MailMarshal (v5,0,3,91)
	id <B00006829f>; Thu, 15 May 2003 10:14:54 +1000
Received: (qmail 8959 invoked from network); 15 May 2003 00:17:13 -0000
Received: from unknown (HELO adacel.com) (10.32.24.164)
  by nexus.adacel.com with SMTP; 15 May 2003 00:17:13 -0000
Message-ID: <3EC2DC87.5000606@adacel.com>
Date: Thu, 15 May 2003 10:17:11 +1000
From: Mark Ennis <mark.ennis@adacel.com>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
CC: ietf-ldapbis@OpenLDAP.org
Subject: Re: Simple+TLS as mandatory-to-implement (RE: Issues with    current
 authmeth draft.)
References: <5.2.0.9.0.20030514062827.02823dc8@127.0.0.1> <5.2.0.9.0.20030513074355.029edd18@127.0.0.1> <5.2.0.9.0.20030512195717.02923988@127.0.0.1> <5.2.0.9.0.20030512195717.02923988@127.0.0.1> <5.2.0.9.0.20030513074355.029edd18@127.0.0.1> <5.2.0.9.0.20030514062827.02823dc8@127.0.0.1> <5.2.0.9.0.20030514164309.02945370@127.0.0.1>
In-Reply-To: <5.2.0.9.0.20030514164309.02945370@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

We've already had this argument. It is up to the working group to decide 
this. I doubt anyone could claim consensus has been reached on this 
topic so far.

- Mark.

Kurt D. Zeilenga wrote:
> At 03:59 PM 5/14/2003, Mark Ennis wrote:
> 
>>My preference is for a digest (or similar challenge/response) authentication mechanism which allows distinguished names as a form of the authentication identity.
> 
> 
> Such a mechanism is not available to us.
> 
> Kurt 
> 
> 
> 



From owner-ietf-ldapbis@OpenLDAP.org  Thu May 15 01:30: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 BAA15824
	for <ldapbis-archive@lists.ietf.org>; Thu, 15 May 2003 01:30:04 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4F5RxF1053539;
	Thu, 15 May 2003 05:31: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 h4F5HBck053007;
	Thu, 15 May 2003 05:17:11 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 15 May 2003 05:17:11 +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 h4F5HAEh052997
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 15 May 2003 05:17:10 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 h4F5H5c6098302;
	Thu, 15 May 2003 05:17:06 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030514210950.02901f10@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Wed, 14 May 2003 22:14:27 -0700
To: Mark Ennis <mark.ennis@adacel.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: Simple+TLS as mandatory-to-implement (RE: Issues with   
  current authmeth draft.)
Cc: ietf-ldapbis@OpenLDAP.org
In-Reply-To: <3EC2DC87.5000606@adacel.com>
References: <5.2.0.9.0.20030514164309.02945370@127.0.0.1>
 <5.2.0.9.0.20030514062827.02823dc8@127.0.0.1>
 <5.2.0.9.0.20030513074355.029edd18@127.0.0.1>
 <5.2.0.9.0.20030512195717.02923988@127.0.0.1>
 <5.2.0.9.0.20030512195717.02923988@127.0.0.1>
 <5.2.0.9.0.20030513074355.029edd18@127.0.0.1>
 <5.2.0.9.0.20030514062827.02823dc8@127.0.0.1>
 <5.2.0.9.0.20030514164309.02945370@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 05:17 PM 5/14/2003, Mark Ennis wrote:
>We've already had this argument. It is up to the working group to decide this. I doubt anyone could claim consensus has been reached on this topic so far.

The argument we had regarding interpretation in this area
is moot at this point.

In a recent post you stated:
  Current development of the SASL specifications will move the
  SASL specifications in a direction which would not support
  my interpretation of RFC2829.

Exactly!  If the WG were to accept your interpretation, then the
chairs would be forced to declare LDAP's use of DIGEST-MD5 as
unworkable.  The WG would either have to revise RFC 2829 to be
consistent with the revised SASL specifications or choose
another available mechanism.

Now, if the WG accepted my interpretation, it could be argued
that DIGEST-MD5 as specification is workable but just needs
some clarification.  However, as there are some known RFC 2831
specification/interoperability issues, I feel it reasonable
for the WG to consider other available mechanisms.

So, you see, we don't need the WG to decide which interpretation
is correct, we need the WG to decide which of the available
mechanisms should now be the mandatory-to-implement mechanism.

So, what shall it be?

Kurt 



From owner-ietf-ldapbis@OpenLDAP.org  Thu May 15 13:47:10 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 NAA16453
	for <ldapbis-archive@lists.ietf.org>; Thu, 15 May 2003 13:47:09 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4FHifFB096141;
	Thu, 15 May 2003 17:49:05 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 h4FHhZ0L096094;
	Thu, 15 May 2003 17:43:35 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 15 May 2003 17:43:35 +0000
Received: from smtp.avinci.de (smtp.avinci.de [62.80.112.129])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4FHhXEh096076
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 15 May 2003 17:43:34 GMT
	(envelope-from norbert+lists.ietf-ldapbis@burgundy.dyndns.org)
Received: from burgundy.dyndns.org (pD9E21162.dip.t-dialin.net [217.226.17.98])
	(authenticated bits=0)
	by smtp.avinci.de (8.12.7/8.12.7) with ESMTP id h4FHhCDN017575
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 15 May 2003 19:43:13 +0200
Received: from localhost (localhost [127.0.0.1])
	by burgundy.dyndns.org (Postfix) with ESMTP id 3DCDDC2C0
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 15 May 2003 19:43:12 +0200 (CEST)
Received: from [10.10.9.3] (trex.local [10.10.9.3])
	by burgundy.dyndns.org (Postfix) with ESMTP id 6B725C25E
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 15 May 2003 19:43:07 +0200 (CEST)
Date: Thu, 15 May 2003 19:43:12 +0200
From: Norbert Klasen <norbert+lists.ietf-ldapbis@burgundy.dyndns.org>
To: ietf-ldapbis@OpenLDAP.org
Subject: I-D ACTION:draft-klasen-ldap-facs-tel-number-matching-01.txt
Message-ID: <93914061.1053027792@[10.10.9.3]>
X-Mailer: Mulberry/3.0.3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by AMaViS 0.3.12pre8
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

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.


	Title	: LDAP: matching rules for facsimile telephone numbers
	Author(s)	: N. Klasen
	Filename	: draft-klasen-ldap-facs-tel-number-matching-01.txt
	Pages	: 9
	Date		: 2003-5-14
	
Based on changes to the 4th edition of X.500, this document updates
the Lightweight Directory Access Protocol (LDAP). It defines an
equality and a substrings matching rule for the 'Facsimile Telephone
Number' syntax and updates the 'facsimileTelephoneNumber' attribute
type to use them.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-klasen-ldap-facs-tel-number-match
ing-01.txt

To remove yourself from the IETF Announcement list, send a message to
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-klasen-ldap-facs-tel-number-matching-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-klasen-ldap-facs-tel-number-matching-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

<ftp://ftp.ietf.org/internet-drafts/draft-klasen-ldap-facs-tel-number-match
ing-01.txt>


From owner-ietf-ldapbis@OpenLDAP.org  Thu May 15 22:39:01 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 WAA29991
	for <ldapbis-archive@lists.ietf.org>; Thu, 15 May 2003 22:38: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 h4G2ciEl024591;
	Fri, 16 May 2003 02:39: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 h4G2cYms024583;
	Fri, 16 May 2003 02:38:34 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Fri, 16 May 2003 02:38:34 +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 h4G2cWEh024573
	for <ietf-ldapbis@OpenLDAP.org>; Fri, 16 May 2003 02:38:33 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 h4G2cSc6007399;
	Fri, 16 May 2003 02:38:29 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030515193217.0295dbe8@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Thu, 15 May 2003 19:35:48 -0700
To: <steven.legg@adacel.com.au>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: New Version of ASN.1
Cc: <ietf-ldapbis@OpenLDAP.org>
In-Reply-To: <004301c319d3$ae977060$a518200a@osmium.mtwav.adacel.com.au>
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>

BTW, changes made to ASN.1 are discussed here.

http://www.itu.int/ITU-T/studygroups/com17/changing-ASN/index.html

Kurt

At 09:45 PM 5/13/2003, Steven Legg wrote:

>Folks,
>
>A new version of ASN.1 has just been released by the ITU and the previous
>version withdrawn. The ASN.1 working group of the ITU would like us to
>reference the latest version. The new version is fully backward compatible
>and I don't see any reason why we shouldn't reference this new version.
>
>The ASN.1 specifications are available on-line for free at:
>http://www.itu.int/ITU-T/studygroups/com17/languages/index.html
>
>Regards,
>Steven



From owner-ietf-ldapbis@OpenLDAP.org  Fri May 16 14:55:59 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 OAA06863
	for <ldapbis-archive@lists.ietf.org>; Fri, 16 May 2003 14:55:59 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4GIunEl072017;
	Fri, 16 May 2003 18:57: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 h4GIrZP4071943;
	Fri, 16 May 2003 18:53:35 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Fri, 16 May 2003 18:53:35 +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 h4GIrYEh071933
	for <ietf-ldapbis@OpenLDAP.org>; Fri, 16 May 2003 18:53:34 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 h4GIrXc6014223
	for <ietf-ldapbis@OpenLDAP.org>; Fri, 16 May 2003 18:53:33 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030516114643.029ca168@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Fri, 16 May 2003 11:50:53 -0700
To: ietf-ldapbis@OpenLDAP.org
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: IETF ldapbis WG Last Call:
  draft-ietf-ldapbis-user-schema-05.txt
In-Reply-To: <5.2.0.9.0.20030505170904.02aa92c0@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>

Please note that the last call period will close soon....  Also,
if you have reviewed the latest revision of this I-D and find
no problems, you should still comment!  Thanks, Kurt

At 05:12 PM 5/5/2003, Kurt D. Zeilenga wrote:
>This message initiates a LDAPbis Working Group Last Call on the
>document:
>
>          LDAP: User Schema
>          <draft-ietf-ldapbis-user-schema-05.txt>
>
>The purpose of this WG Last Call it to ensure that the Working Group
>has achieved consensus that the document is suitable for publication
>as an IETF Draft Standard.
>
>Please review the document for both technical and editorial problems.
>Technical issues should be discussed on this list.  Editorial issues
>may be sent to the document editor.
>
>The Last Call period will end on Wednesday, May 21, 2003.
>
>Upon completion of the last call, the WG chair(s) will take action
>based upon the consensus of the WG.  Possible actions include:
>
>  1) recommending to the IETF Application Area Directors that the
>     document, after possible editorial or other minor changes, be
>     considered by the IESG for publication as a Draft Standard
>     (which generally involves an IETF-wide Last Call); or
>
>  2) requiring that outstanding issues be adequately addressed prior
>     to further action (including, possibly, another Last Call).
>
>Remember that it is our responsibility as Working Group members to
>ensure the quality of our documents and of the Internet Standards
>process.  So, please read and comment!
>
> - Kurt Zeilenga
>   LDAPbis co-chair 



From owner-ietf-ldapbis@OpenLDAP.org  Fri May 16 16:04:49 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 QAA09665
	for <ldapbis-archive@lists.ietf.org>; Fri, 16 May 2003 16:04:48 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4GK3aEp073703;
	Fri, 16 May 2003 20:06:30 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 h4GJkK8X072955;
	Fri, 16 May 2003 19:46:20 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Fri, 16 May 2003 19:46:20 +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 h4GJkIEh072944
	for <ietf-ldapbis@OpenLDAP.org>; Fri, 16 May 2003 19:46:18 GMT
	(envelope-from MHINCKLEY@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Fri, 16 May 2003 13:45:58 -0600
Message-Id: <sec4eb96.088@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.0 
Date: Fri, 16 May 2003 13:45:42 -0600
From: "Mark Hinckley" <MHINCKLEY@novell.com>
To: <ietf-ldapbis@OpenLDAP.org>
Subject: Re: IETF ldapbis WG Last
	Call:draft-ietf-ldapbis-user-schema-05.txt
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by boole.openldap.org id h4GJkIEh072945
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 have reviewed the user-schema draft, and have the following comments:

2.5 * upper bound on 'description' attribute is 1024.  Any chance of relaxing that value?  I know X.520 specifies this limit, so it probably isn't too likely, but it would be nice.  (I know we can't really change this, but I just had to ask anyway.)

2.18 * 'name' upper bound is shown as 32768.  The 93 version of the X.520 document I have access to lists ub-name value twice, with values of 64 and 32768.  But the 2001 version of the doc only has the value listed as 64.   This does seem overly restrictive to me, so is this intended to be the 32K value instead of 64?

2.16 * 'l' and 2.33 - 'st' * both inherit from 'name' with its limit.  Most of the other items that inherit from 'name' either have the same upper bound defined in X.520, or don't even have their own upper bound definition, just inheriting the value from 'name'.  However, both 'l' and 'st' have explicit upper bounds of 128 given in X.520 (Annex C).  Is there any way to specify that in the definition given here?

3.2 - "C" - If we are deprecating the 'searchGuide' attribute, why is it still part of the Country definition (and enhanceSearchGuide is not?)

3.4 * "domain" * ditto for 'teletexTerminalIdentifier' being deprecated.

3.8 * "organization" * since it has the identical set of  attributes in the MAY list as "organizationalUnit", and the list of attributes on "organizationalUnit" appear to be listed in alphabetical order, why is the same list of attributes given in apparently random order for "organization"?

Generally speaking, is there some reason not to list the attributes of a class definition in alphabetical order?


>>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 05/16/03 12:50PM >>>
Please note that the last call period will close soon....  Also,
if you have reviewed the latest revision of this I-D and find
no problems, you should still comment!  Thanks, Kurt

At 05:12 PM 5/5/2003, Kurt D. Zeilenga wrote:
>This message initiates a LDAPbis Working Group Last Call on the
>document:
>
>          LDAP: User Schema
>          <draft-ietf-ldapbis-user-schema-05.txt>
>
>The purpose of this WG Last Call it to ensure that the Working Group
>has achieved consensus that the document is suitable for publication
>as an IETF Draft Standard.
>
>Please review the document for both technical and editorial problems.
>Technical issues should be discussed on this list.  Editorial issues
>may be sent to the document editor.
>
>The Last Call period will end on Wednesday, May 21, 2003.
>
>Upon completion of the last call, the WG chair(s) will take action
>based upon the consensus of the WG.  Possible actions include:
>
>  1) recommending to the IETF Application Area Directors that the
>     document, after possible editorial or other minor changes, be
>     considered by the IESG for publication as a Draft Standard
>     (which generally involves an IETF-wide Last Call); or
>
>  2) requiring that outstanding issues be adequately addressed prior
>     to further action (including, possibly, another Last Call).
>
>Remember that it is our responsibility as Working Group members to
>ensure the quality of our documents and of the Internet Standards
>process.  So, please read and comment!
>
> - Kurt Zeilenga
>   LDAPbis co-chair 





From owner-ietf-ldapbis@OpenLDAP.org  Fri May 16 17:13:47 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 RAA11002
	for <ldapbis-archive@lists.ietf.org>; Fri, 16 May 2003 17:13: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 h4GLEoF1077328;
	Fri, 16 May 2003 21:15:36 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 h4GLB623077103;
	Fri, 16 May 2003 21:11:06 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Fri, 16 May 2003 21:11:06 +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 h4GLAoEh077074
	for <ietf-ldapbis@OpenLDAP.org>; Fri, 16 May 2003 21:10:50 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 h4GLAoc6014998
	for <ietf-ldapbis@OpenLDAP.org>; Fri, 16 May 2003 21:10:50 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030516131820.02a0ebb8@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Fri, 16 May 2003 14:08:09 -0700
To: ietf-ldapbis@OpenLDAP.org
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: ldapbis-user-schema comments
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 have recently been addressing IESG comments with regard to
an individual submission of mine (zeilenga-ldap-user-schema)
and find that some of these comments (see I-D tracker) apply
to ietf-ldapbis-user-schema as well. 

The title "LDAP: user schema" implies the document scope is
limited to defining schema for representing users in the directory.
However, as defines schema for devices and other objects, the
scope is actually broader.  In my individual I-D, I meant "user
schema" to imply "schema for user applications" (versus "system
schema").  It may be appropriate to consider a change to the title
of this WG document.

Specifications for most attribute types imply they only have single
values yet are defined to hold multiple values.  For example,
the I-D says: CN contains "a name of an object".  However,
CN contains "the names of the object".  We need to review
the specification of each attribute type.

More examples should be useful (both for attribute types
and object classes).

Kurt


 




From owner-ietf-ldapbis@OpenLDAP.org  Mon May 19 00:21:39 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 AAA24885
	for <ldapbis-archive@lists.ietf.org>; Mon, 19 May 2003 00:21: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 h4J4LBEl034002;
	Mon, 19 May 2003 04:22:49 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 h4J4Jtdn033970;
	Mon, 19 May 2003 04:19:55 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 19 May 2003 04:19:55 +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 h4J4JqEh033960
	for <ietf-ldapbis@openldap.org>; Mon, 19 May 2003 04:19:53 GMT
	(envelope-from steven.legg@adacel.com.au)
Received: from nexus.adacel.com (Not Verified[10.32.240.1]) by adacel.com with MailMarshal (v5,0,3,91)
	id <B00006d2a4>; Mon, 19 May 2003 14:16:41 +1000
Received: (qmail 30298 invoked from network); 19 May 2003 04:19:10 -0000
Received: from unknown (HELO osmium) (10.32.24.165)
  by nexus.adacel.com with SMTP; 19 May 2003 04:19:10 -0000
Reply-To: <steven.legg@adacel.com.au>
From: "Steven Legg" <steven.legg@adacel.com.au>
To: "'Mark Hinckley'" <MHINCKLEY@novell.com>, <ietf-ldapbis@OpenLDAP.org>
Subject: RE: IETF ldapbis WG LastCall:draft-ietf-ldapbis-user-schema-05.txt
Date: Mon, 19 May 2003 14:19:27 +1000
Message-ID: <004901c31dbd$d723add0$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
In-Reply-To: <sec4eb96.088@prv-mail20.provo.novell.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2120.0
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


Mark,

Mark Hinckley wrote:
> I have reviewed the user-schema draft, and have the following 
> comments:
> 
> 2.5 * upper bound on 'description' attribute is 1024.  Any 
> chance of relaxing that value?

It is already relaxed. The meaning LDAP applies to the curly braces
following a syntax OID is that a server should allow values of at
least that number of characters. Values with more characters are
permitted.

> I know X.520 specifies this 
> limit, so it probably isn't too likely, but it would be nice.

In X.520 the limit is an upper limit on size, but the limits X.520
imposes are, in any case, non-normative. An implementation is free to
impose whatever upper limits it wants, either higher or lower that
the ones suggested by X.520.

My recommendation is that the user schema draft simply remove all
the upper bounds to avoid confusion. They are not hard limits in
either LDAP or X.500.

>  (I know we can't really change this, but I just had to ask anyway.)

We can change it, so it was worth asking.

Regards,
Steven

> 
> 2.18 * 'name' upper bound is shown as 32768.  The 93 version 
> of the X.520 document I have access to lists ub-name value 
> twice, with values of 64 and 32768.  But the 2001 version of 
> the doc only has the value listed as 64.   This does seem 
> overly restrictive to me, so is this intended to be the 32K 
> value instead of 64?
> 
> 2.16 * 'l' and 2.33 - 'st' * both inherit from 'name' with 
> its limit.  Most of the other items that inherit from 'name' 
> either have the same upper bound defined in X.520, or don't 
> even have their own upper bound definition, just inheriting 
> the value from 'name'.  However, both 'l' and 'st' have 
> explicit upper bounds of 128 given in X.520 (Annex C).  Is 
> there any way to specify that in the definition given here?
> 
> 3.2 - "C" - If we are deprecating the 'searchGuide' 
> attribute, why is it still part of the Country definition 
> (and enhanceSearchGuide is not?)
> 
> 3.4 * "domain" * ditto for 'teletexTerminalIdentifier' being 
> deprecated.
> 
> 3.8 * "organization" * since it has the identical set of  
> attributes in the MAY list as "organizationalUnit", and the 
> list of attributes on "organizationalUnit" appear to be 
> listed in alphabetical order, why is the same list of 
> attributes given in apparently random order for "organization"?
> 
> Generally speaking, is there some reason not to list the 
> attributes of a class definition in alphabetical order?
> 
> 
> >>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 05/16/03 12:50PM >>>
> Please note that the last call period will close soon....  Also,
> if you have reviewed the latest revision of this I-D and find
> no problems, you should still comment!  Thanks, Kurt
> 
> At 05:12 PM 5/5/2003, Kurt D. Zeilenga wrote:
> >This message initiates a LDAPbis Working Group Last Call on the
> >document:
> >
> >          LDAP: User Schema
> >          <draft-ietf-ldapbis-user-schema-05.txt>
> >
> >The purpose of this WG Last Call it to ensure that the Working Group
> >has achieved consensus that the document is suitable for publication
> >as an IETF Draft Standard.
> >
> >Please review the document for both technical and editorial problems.
> >Technical issues should be discussed on this list.  Editorial issues
> >may be sent to the document editor.
> >
> >The Last Call period will end on Wednesday, May 21, 2003.
> >
> >Upon completion of the last call, the WG chair(s) will take action
> >based upon the consensus of the WG.  Possible actions include:
> >
> >  1) recommending to the IETF Application Area Directors that the
> >     document, after possible editorial or other minor changes, be
> >     considered by the IESG for publication as a Draft Standard
> >     (which generally involves an IETF-wide Last Call); or
> >
> >  2) requiring that outstanding issues be adequately addressed prior
> >     to further action (including, possibly, another Last Call).
> >
> >Remember that it is our responsibility as Working Group members to
> >ensure the quality of our documents and of the Internet Standards
> >process.  So, please read and comment!
> >
> > - Kurt Zeilenga
> >   LDAPbis co-chair 
> 
> 
> 
> 


From owner-ietf-ldapbis@OpenLDAP.org  Mon May 19 06:45: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 GAA14878
	for <ldapbis-archive@lists.ietf.org>; Mon, 19 May 2003 06:45:47 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4JA9AF9047393;
	Mon, 19 May 2003 10:17: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 h4JA72nV047273;
	Mon, 19 May 2003 10:07:02 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 19 May 2003 10:07:02 +0000
Received: from nb2.stroeder.com (krl9-d9bb4da1.pool.mediaWays.net [217.187.77.161])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4JA70Eh047258
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 19 May 2003 10:07:00 GMT
	(envelope-from michael@stroeder.com)
Received: from localhost (localhost.stroeder.com [127.0.0.1])
	by nb2.stroeder.com (Postfix) with ESMTP
	id 46397834AA; Mon, 19 May 2003 12:06:34 +0200 (CEST)
Received: from stroeder.com (localhost.stroeder.com [127.0.0.1])
	by nb2.stroeder.com (Postfix) with ESMTP
	id B3F0583498; Mon, 19 May 2003 12:06:33 +0200 (CEST)
Message-ID: <3EC8ACA9.1040906@stroeder.com>
Date: Mon, 19 May 2003 12:06:33 +0200
From: =?ISO-8859-1?Q?Michael_Str=F6der?= <michael@stroeder.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3.1) Gecko/20030425
X-Accept-Language: de-de, de, en-us, en
MIME-Version: 1.0
To: steven.legg@adacel.com.au
Cc: ietf-ldapbis@OpenLDAP.org
Subject: Re: IETF ldapbis WG LastCall:draft-ietf-ldapbis-user-schema-05.txt
References: <004901c31dbd$d723add0$a518200a@osmium.mtwav.adacel.com.au>
In-Reply-To: <004901c31dbd$d723add0$a518200a@osmium.mtwav.adacel.com.au>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by AMaViS 0.3.12pre8
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

Steven Legg wrote:
> 
>>I know X.520 specifies this 
>>limit, so it probably isn't too likely, but it would be nice.
> 
> In X.520 the limit is an upper limit on size,

Why was the sematic of this changed in LDAP? IMO it does not make sense to 
define a "minimum upper bound" at all. I'd rather consider the term to be a 
paradox.

> My recommendation is that the user schema draft simply remove all
> the upper bounds to avoid confusion.

+1

Ciao, Michael.



From owner-ietf-ldapbis@OpenLDAP.org  Mon May 19 14:01:43 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>; Mon, 19 May 2003 14:01:27 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4JI3CEl082416;
	Mon, 19 May 2003 18:03: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 h4JI2o9J082395;
	Mon, 19 May 2003 18:02:50 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 19 May 2003 18:02:50 +0000
Received: from pat.uio.no (pat.uio.no [129.240.130.16])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4JI2kEh082363;
	Mon, 19 May 2003 18:02:47 GMT
	(envelope-from hbf@bombur.uio.no)
Received: from mail-mx1.uio.no ([129.240.10.29])
	by pat.uio.no with esmtp (Exim 2.12 #7)
	id 19HoyD-0005PV-00; Mon, 19 May 2003 20:02:45 +0200
Received: from [129.240.130.14] (helo=mons.uio.no)
	by mail-mx1.uio.no with esmtp (Exim 4.14)
	id 19HoxQ-0002CV-QV; Mon, 19 May 2003 20:01:56 +0200
Received: from bombur.uio.no ([129.240.186.42])
	by mons.uio.no with esmtp (Exim 2.12 #7)
	id 19HoxP-0005xS-00; Mon, 19 May 2003 20:01:55 +0200
Received: from hbf by bombur.uio.no with local (Exim 2.12 #7)
	id 19HowY-0004eS-00; Mon, 19 May 2003 20:01:02 +0200
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Message-Id: <HBF.20030519fr1v@bombur.uio.no>
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Cc: ietf-ldapbis@OpenLDAP.org
Subject: Re: userPassword comment
In-Reply-To: <5.2.0.9.0.20030519102238.02770d00@127.0.0.1>
References: <5.2.0.9.0.20030519102238.02770d00@127.0.0.1>
X-Mailer: VM 6.37 under Emacs 19.34.1
Date: Mon, 19 May 2003 20:01:02 +0200
X-MailScanner-Information: Please contact postmaster@uio.no for more information
X-UiO-MailScanner: Found to be clean
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:
> that applications SHOULD prepare textual strings used as passwords
> before storing them in the directory to improve the likelihood
> that passwords work as expected.   To prepare a textual string,
> the application MUST transcode to Unicode, apply SASLprep, and
> transfer using UTF-8.

SHOULD prepare, but MUST transcode and so on?  Do you mean that
IF it prepares, it MUST do it by transcoding and so on?

Is 'transcode to Unicode, apply SASLprep, and transfer using UTF-8' the
definition of 'to prepare' the string, or can 'prepare' mean something
else?  If the former, how about:

  ...the application SHOULD prepare textual strings used as passwords
  by transcoding them to Unicode, applying SASLprep, and encoding as
  UTF-8.

Though I don't think the schema draft should talk about 'transfer'.
That's a protocol thing.  How about 'encode' as UTF-8?

Finally, where is SASLprep defined?

-- 
Hallvard


From owner-ietf-ldapbis@OpenLDAP.org  Mon May 19 14:18: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 OAA29470
	for <ldapbis-archive@lists.ietf.org>; Mon, 19 May 2003 14:18: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 h4JHdCFD080337;
	Mon, 19 May 2003 17:47: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 h4JHa92Q080205;
	Mon, 19 May 2003 17:36:09 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 19 May 2003 17:36: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 h4JHa3Eh080195
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 19 May 2003 17:36:08 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 h4JHa2c6038761
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 19 May 2003 17:36:03 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030519102238.02770d00@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Mon, 19 May 2003 10:33:18 -0700
To: ietf-ldapbis@OpenLDAP.org
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: userPassword comment
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-ietf-ldapbis-user-schema should say that as userPassword
syntax is octet string and has octetExactMatch equality matching,
that applications SHOULD prepare textual strings used as passwords
before storing them in the directory to improve the likelihood
that passwords work as expected.   To prepare a textual string,
the application MUST transcode to Unicode, apply SASLprep, and
transfer using UTF-8.

This should be applied to simple bind's password field as well.

Kurt




From owner-ietf-ldapbis@OpenLDAP.org  Mon May 19 14:28:36 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 OAA29726
	for <ldapbis-archive@lists.ietf.org>; Mon, 19 May 2003 14:28:36 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4JIRCG7084663;
	Mon, 19 May 2003 18:30: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 h4JILvPY084003;
	Mon, 19 May 2003 18:21:57 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 19 May 2003 18:21:57 +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 h4JILuEh083987
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 19 May 2003 18:21:56 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 h4JILtc6039131;
	Mon, 19 May 2003 18:21:55 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030519110958.029a2e68@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Mon, 19 May 2003 11:19:12 -0700
To: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: userPassword comment
Cc: ietf-ldapbis@OpenLDAP.org
In-Reply-To: <HBF.20030519fr1v@bombur.uio.no>
References: <5.2.0.9.0.20030519102238.02770d00@127.0.0.1>
 <5.2.0.9.0.20030519102238.02770d00@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 11:01 AM 5/19/2003, Hallvard B Furuseth wrote:
>Kurt D. Zeilenga writes:
>> that applications SHOULD prepare textual strings used as passwords
>> before storing them in the directory to improve the likelihood
>> that passwords work as expected.   To prepare a textual string,
>> the application MUST transcode to Unicode, apply SASLprep, and
>> transfer using UTF-8.
>
>SHOULD prepare, but MUST transcode and so on?  Do you mean that
>IF it prepares, it MUST do it by transcoding and so on?

I meant:
  It is RECOMMENDED that applications prepare textual strings
  used as password to improve matching.  Applications which
  prepare textural strings used as password are REQUIRED to
  prepare them as follows:
     a) transcode to Unicode,
     b) apply SASLprep, and
     c) encode as UTF-8.


>Is 'transcode to Unicode, apply SASLprep, and transfer using UTF-8' the
>definition of 'to prepare' the string, or can 'prepare' mean something
>else?  If the former, how about:
>
>  ...the application SHOULD prepare textual strings used as passwords
>  by transcoding them to Unicode, applying SASLprep, and encoding as
>  UTF-8.

I am fine with this as well.

>Though I don't think the schema draft should talk about 'transfer'.
>That's a protocol thing.  How about 'encode' as UTF-8?

encode is fine.

>Finally, where is SASLprep defined?

draft-ietf-sasl-saslprep-xx.txt

Kurt 



From owner-ietf-ldapbis@OpenLDAP.org  Mon May 19 14:43:13 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 OAA00373
	for <ldapbis-archive@lists.ietf.org>; Mon, 19 May 2003 14:43:12 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4JIjCEl094842;
	Mon, 19 May 2003 18:45:14 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 h4JIe0Lm087353;
	Mon, 19 May 2003 18:40:00 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 19 May 2003 18:40:00 +0000
Received: from smtp.avinci.de (smtp.avinci.de [62.80.112.129])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4JIdwEh087297
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 19 May 2003 18:39:59 GMT
	(envelope-from norbert+lists.ietf-ldapbis@burgundy.dyndns.org)
Received: from burgundy.dyndns.org (p5084AFC9.dip.t-dialin.net [80.132.175.201])
	(authenticated bits=0)
	by smtp.avinci.de (8.12.7/8.12.7) with ESMTP id h4JIdWDN006802
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 19 May 2003 20:39:37 +0200
Received: from localhost (localhost [127.0.0.1])
	by burgundy.dyndns.org (Postfix) with ESMTP id 81C6AC2C1
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 19 May 2003 20:39:29 +0200 (CEST)
Received: from [10.10.9.3] (trex.local [10.10.9.3])
	by burgundy.dyndns.org (Postfix) with ESMTP id E17D3C2C0
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 19 May 2003 20:39:25 +0200 (CEST)
Date: Mon, 19 May 2003 20:39:37 +0200
From: Norbert Klasen <norbert+lists.ietf-ldapbis@burgundy.dyndns.org>
To: ietf-ldapbis@OpenLDAP.org
Subject: Re: IETF ldapbis WG Last Call: 
 draft-ietf-ldapbis-user-schema-05.txt
Message-ID: <210020353.1053376777@[10.10.9.3]>
In-Reply-To: <5.2.0.9.0.20030505170904.02aa92c0@127.0.0.1>
References: <5.2.0.9.0.20030505170904.02aa92c0@127.0.0.1>
X-Mailer: Mulberry/3.0.3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by AMaViS 0.3.12pre8
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

Hi,
the schema in many LDAP servers contains an alternate name for those 
attributes, whose name is an abbreviation from the name of the respective 
X.500 attribute type, e.g. 'cn' and 'commonName' or 'st' and 
'stateOrProvinceName'.
Should this be reflected in the user-schema document?

Norbert


From owner-ietf-ldapbis@OpenLDAP.org  Mon May 19 15:13: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 PAA02412
	for <ldapbis-archive@lists.ietf.org>; Mon, 19 May 2003 15:13:20 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4JJFCEp096782;
	Mon, 19 May 2003 19:15: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 h4JJEuP5096756;
	Mon, 19 May 2003 19:14:56 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 19 May 2003 19:14:56 +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 h4JJEeEh096743
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 19 May 2003 19:14:40 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 h4JJEYc6039600;
	Mon, 19 May 2003 19:14:34 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030519115951.0299def0@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Mon, 19 May 2003 12:11:51 -0700
To: Norbert Klasen <norbert+lists.ietf-ldapbis@burgundy.dyndns.org>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: IETF ldapbis WG Last Call: 
  draft-ietf-ldapbis-user-schema-05.txt
Cc: ietf-ldapbis@OpenLDAP.org
In-Reply-To: <210020353.1053376777@[10.10.9.3]>
References: <5.2.0.9.0.20030505170904.02aa92c0@127.0.0.1>
 <5.2.0.9.0.20030505170904.02aa92c0@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 11:39 AM 5/19/2003, Norbert Klasen wrote:
>the schema in many LDAP servers contains an alternate name for those attributes, whose name is an abbreviation from the name of the respective X.500 attribute type, e.g. 'cn' and 'commonName' or 'st' and 'stateOrProvinceName'.  Should this be reflected in the user-schema document?

Personally, I think they should not be listed as that would
require implementations to recognize additional names.  Multiple
names leads to interoperability problems as it is inevitable
that some implementations will not recognize all of them.

Certainly LDAP implementations are allowed to recognize
additional names... but they should not assume others do.

Kurt



From owner-ietf-ldapbis@OpenLDAP.org  Mon May 19 15:18:19 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 PAA02778
	for <ldapbis-archive@lists.ietf.org>; Mon, 19 May 2003 15:18:18 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4JIvCEl095369;
	Mon, 19 May 2003 18:57:17 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 h4JIpXii095198;
	Mon, 19 May 2003 18:51:33 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 19 May 2003 18:51:33 +0000
Received: from nb2.stroeder.com (krl9-d9bb4f3c.pool.mediaWays.net [217.187.79.60])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4JIpVEh095171
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 19 May 2003 18:51:32 GMT
	(envelope-from michael@stroeder.com)
Received: from localhost (localhost.stroeder.com [127.0.0.1])
	by nb2.stroeder.com (Postfix) with ESMTP
	id 11BBA83482; Mon, 19 May 2003 20:51:10 +0200 (CEST)
Received: from stroeder.com (localhost.stroeder.com [127.0.0.1])
	by nb2.stroeder.com (Postfix) with ESMTP
	id 7BC228347A; Mon, 19 May 2003 20:51:09 +0200 (CEST)
Message-ID: <3EC9279D.20007@stroeder.com>
Date: Mon, 19 May 2003 20:51:09 +0200
From: =?ISO-8859-1?Q?Michael_Str=F6der?= <michael@stroeder.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3.1) Gecko/20030425
X-Accept-Language: de-de, de, en-us, en
MIME-Version: 1.0
To: Norbert Klasen <norbert+lists.ietf-ldapbis@burgundy.dyndns.org>
Cc: ietf-ldapbis@OpenLDAP.org
Subject: Re: IETF ldapbis WG Last Call:  draft-ietf-ldapbis-user-schema-05.txt
References: <5.2.0.9.0.20030505170904.02aa92c0@127.0.0.1> <210020353.1053376777@[10.10.9.3]>
In-Reply-To: <210020353.1053376777@[10.10.9.3]>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by AMaViS 0.3.12pre8
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

Norbert Klasen wrote:
> the schema in many LDAP servers contains an alternate name for those 
> attributes, whose name is an abbreviation from the name of the 
> respective X.500 attribute type, e.g. 'cn' and 'commonName' or 'st' and 
> 'stateOrProvinceName'.
> Should this be reflected in the user-schema document?

I guess this will take us to the name registry discussion again.

I'd like to see this aliases mentioned in draft-ietf-ldapbis-user-schema. 
This would make developers aware that these aliases exist.

Ciao, Michael.



From owner-ietf-ldapbis@OpenLDAP.org  Mon May 19 15:54: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 ESMTP id PAA04340
	for <ldapbis-archive@lists.ietf.org>; Mon, 19 May 2003 15:54:27 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4JJpDFV098664;
	Mon, 19 May 2003 19:56:39 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 h4JJjZx3098230;
	Mon, 19 May 2003 19:45:35 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 19 May 2003 19:45:35 +0000
Received: from nb2.stroeder.com (krl9-d9bb4f3c.pool.mediaWays.net [217.187.79.60])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4JJjWEh098159;
	Mon, 19 May 2003 19:45:33 GMT
	(envelope-from michael@stroeder.com)
Received: from localhost (localhost.stroeder.com [127.0.0.1])
	by nb2.stroeder.com (Postfix) with ESMTP
	id C78D88358B; Mon, 19 May 2003 21:45:08 +0200 (CEST)
Received: from stroeder.com (localhost.stroeder.com [127.0.0.1])
	by nb2.stroeder.com (Postfix) with ESMTP
	id 2FC78673B7; Mon, 19 May 2003 21:45:08 +0200 (CEST)
Message-ID: <3EC93444.60208@stroeder.com>
Date: Mon, 19 May 2003 21:45:08 +0200
From: =?ISO-8859-1?Q?Michael_Str=F6der?= <michael@stroeder.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3.1) Gecko/20030425
X-Accept-Language: de-de, de, en-us, en
MIME-Version: 1.0
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Cc: Norbert Klasen <norbert+lists.ietf-ldapbis@burgundy.dyndns.org>,
        ietf-ldapbis@OpenLDAP.org
Subject: Re: IETF ldapbis WG Last Call:   draft-ietf-ldapbis-user-schema-05.txt
References: <5.2.0.9.0.20030505170904.02aa92c0@127.0.0.1> <5.2.0.9.0.20030505170904.02aa92c0@127.0.0.1> <5.2.0.9.0.20030519115951.0299def0@127.0.0.1>
In-Reply-To: <5.2.0.9.0.20030519115951.0299def0@127.0.0.1>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by AMaViS 0.3.12pre8
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 11:39 AM 5/19/2003, Norbert Klasen wrote:
> 
>> the schema in many LDAP servers contains an alternate name for those
>> attributes, whose name is an abbreviation from the name of the
>> respective X.500 attribute type, e.g. 'cn' and 'commonName' or 'st' and
>> 'stateOrProvinceName'.  Should this be reflected in the user-schema
>> document?
> 
> Personally, I think they should not be listed as that would
> require implementations to recognize additional names.

Why would that "require" to recognize additional names? Maybe one could come 
up with a wording listing the mandantory attribute type names and the 
optional aliases?

>  Multiple
> names leads to interoperability problems as it is inevitable
> that some implementations will not recognize all of them.

But there are already multiple names out there in the wild. And sure there 
are already interoperability problems with that. My point is that listing 
the aliases would make implementors aware of it.

> Certainly LDAP implementations are allowed to recognize
> additional names... but they should not assume others do.

IMHO either we'd be able to disallow use of aliases or we have to make 
implementors aware of them.

Ciao, Michael.



From owner-ietf-ldapbis@OpenLDAP.org  Mon May 19 16:55:39 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 QAA05495
	for <ldapbis-archive@lists.ietf.org>; Mon, 19 May 2003 16:55:35 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4JKvDEl004005;
	Mon, 19 May 2003 20:57:40 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 h4JKrnP5003903;
	Mon, 19 May 2003 20:53:49 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 19 May 2003 20:53:49 +0000
Received: from e3.ny.us.ibm.com (e3.ny.us.ibm.com [32.97.182.103])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4JKrlEh003876
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 19 May 2003 20:53:48 GMT
	(envelope-from jmcmeek@us.ibm.com)
Received: from northrelay04.pok.ibm.com (northrelay04.pok.ibm.com [9.56.224.206])
	by e3.ny.us.ibm.com (8.12.9/8.12.2) with ESMTP id h4JKrQE2131926
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 19 May 2003 16:53:27 -0400
Received: from d27ml001.rchland.ibm.com (d01av02.pok.ibm.com [9.56.224.216])
	by northrelay04.pok.ibm.com (8.12.9/NCO/VER6.5) with ESMTP id h4JKrNJp084934
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 19 May 2003 16:53:24 -0400
Subject: Re: IETF ldapbis WG Last Call:    draft-ietf-ldapbis-user-schema-05.txt
To: ietf-ldapbis@OpenLDAP.org
X-Mailer: Lotus Notes Release 5.0.12   February 13, 2003
Message-ID: <OF501F4212.1B377C6C-ON86256D2B.0071B569-86256D2B.0072C20B@us.ibm.com>
From: John McMeeking <jmcmeek@us.ibm.com>
Date: Mon, 19 May 2003 15:53:27 -0500
X-MIMETrack: Serialize by Router on d27ml001/27/M/IBM(Build V602_05052003|May 05, 2003) at
 05/19/2003 15:53:25
MIME-Version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by boole.openldap.org id h4JKrmEh003893
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 would rather not see these aliases added to the user schema draft.

I've seen LDAP servers that recognize commonName as an alias of cn, and was
tempted to say that we ought to list this as optional aliases.  But I've
also seen the headaches that result when applications mix cn and commonName
(or other aliases), particularly when one application is either unaware of
the alias, or unaware of aliases in general.

I don't recall seeing a standard that says commonName is an alias for cn,
just that cn is the LDAP equivalent to X.500 commonName.


John  McMeeking



                                                                                                                                    
                      "Kurt D. Zeilenga"                                                                                            
                      <Kurt@OpenLDAP.org>         To:       Michael Ströder <michael@stroeder.com>                                  
                      Sent by:                    cc:       Norbert Klasen <norbert+lists.ietf-ldapbis@burgundy.dyndns.org>,        
                      owner-ietf-ldapbis@O         ietf-ldapbis@OpenLDAP.org                                                        
                      penLDAP.org                 Subject:  Re: IETF ldapbis WG Last Call:    draft-ietf-ldapbis-user-schema-05.txt 
                                                                                                                                    
                                                                                                                                    
                      05/19/2003 02:56 PM                                                                                           
                                                                                                                                    
                                                                                                                                    




At 12:45 PM 5/19/2003, Michael Ströder wrote:
>Kurt D. Zeilenga wrote:
>>At 11:39 AM 5/19/2003, Norbert Klasen wrote:
>>
>>>the schema in many LDAP servers contains an alternate name for those
>>>attributes, whose name is an abbreviation from the name of the
>>>respective X.500 attribute type, e.g. 'cn' and 'commonName' or 'st' and
>>>'stateOrProvinceName'.  Should this be reflected in the user-schema
>>>document?
>>Personally, I think they should not be listed as that would
>>require implementations to recognize additional names.
>
>Why would that "require" to recognize additional names?

Because its expected that all implementations recognize the
attribute types and other elements by the names listed.

>Maybe one could come up with a wording listing the mandantory attribute
type names and the optional aliases?

Maybe, but why?  Adding additional names only leads to interoperability
problems.  It is far better to have one and only name per schema element.

>> Multiple
>>names leads to interoperability problems as it is inevitable
>>that some implementations will not recognize all of them.
>
>But there are already multiple names out there in the wild.

There are also many implementations which don't recognize the
various names one might find in use in the wild.

>And sure there are already interoperability problems with that.

Well, there are always problems when implementations using names
other than those which the standard track specifications say to
use.  This problem cannot be solved by adding more names.  Instead
we should clarify the specifications that use of other names will
lead to interoperability.

>My point is that listing the aliases would make implementors aware of it.

Implementors shouldn't have to be aware of non-standard names.

>>Certainly LDAP implementations are allowed to recognize
>>additional names... but they should not assume others do.
>
>IMHO either we'd be able to disallow use of aliases or we have to make
implementors aware of them.

I think it unwise to disallow implementations from being
"liberal in what they accept".  However, implementations
should be "strict in what they produce".

Kurt








From owner-ietf-ldapbis@OpenLDAP.org  Mon May 19 17:10: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 RAA05821
	for <ldapbis-archive@lists.ietf.org>; Mon, 19 May 2003 17:10: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 h4JK3CFT099877;
	Mon, 19 May 2003 20:12: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 h4JJxk0l099544;
	Mon, 19 May 2003 19:59:46 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 19 May 2003 19:59:46 +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 h4JJxjEh099534
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 19 May 2003 19:59:45 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 h4JJxgc6039948;
	Mon, 19 May 2003 19:59:42 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030519124528.029c0a38@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Mon, 19 May 2003 12:56:58 -0700
To: Michael =?iso-8859-1?Q?Str=F6der?= <michael@stroeder.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: IETF ldapbis WG Last Call:  
  draft-ietf-ldapbis-user-schema-05.txt
Cc: Norbert Klasen <norbert+lists.ietf-ldapbis@burgundy.dyndns.org>,
        ietf-ldapbis@OpenLDAP.org
In-Reply-To: <3EC93444.60208@stroeder.com>
References: <5.2.0.9.0.20030519115951.0299def0@127.0.0.1>
 <5.2.0.9.0.20030505170904.02aa92c0@127.0.0.1>
 <5.2.0.9.0.20030505170904.02aa92c0@127.0.0.1>
 <5.2.0.9.0.20030519115951.0299def0@127.0.0.1>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by boole.openldap.org id h4JJxjEh099535
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

At 12:45 PM 5/19/2003, Michael Ströder wrote:
>Kurt D. Zeilenga wrote:
>>At 11:39 AM 5/19/2003, Norbert Klasen wrote:
>>
>>>the schema in many LDAP servers contains an alternate name for those
>>>attributes, whose name is an abbreviation from the name of the
>>>respective X.500 attribute type, e.g. 'cn' and 'commonName' or 'st' and
>>>'stateOrProvinceName'.  Should this be reflected in the user-schema
>>>document?
>>Personally, I think they should not be listed as that would
>>require implementations to recognize additional names.
>
>Why would that "require" to recognize additional names?

Because its expected that all implementations recognize the
attribute types and other elements by the names listed.

>Maybe one could come up with a wording listing the mandantory attribute type names and the optional aliases?

Maybe, but why?  Adding additional names only leads to interoperability
problems.  It is far better to have one and only name per schema element.

>> Multiple
>>names leads to interoperability problems as it is inevitable
>>that some implementations will not recognize all of them.
>
>But there are already multiple names out there in the wild.

There are also many implementations which don't recognize the
various names one might find in use in the wild.

>And sure there are already interoperability problems with that.

Well, there are always problems when implementations using names
other than those which the standard track specifications say to
use.  This problem cannot be solved by adding more names.  Instead
we should clarify the specifications that use of other names will
lead to interoperability.

>My point is that listing the aliases would make implementors aware of it.

Implementors shouldn't have to be aware of non-standard names.

>>Certainly LDAP implementations are allowed to recognize
>>additional names... but they should not assume others do.
>
>IMHO either we'd be able to disallow use of aliases or we have to make implementors aware of them.

I think it unwise to disallow implementations from being
"liberal in what they accept".  However, implementations
should be "strict in what they produce".

Kurt 




From owner-ietf-ldapbis@OpenLDAP.org  Tue May 20 08:38: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 IAA10032
	for <ldapbis-archive@lists.ietf.org>; Tue, 20 May 2003 08:38:22 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4KCdIEl052645;
	Tue, 20 May 2003 12:39:51 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 h4KCYHXr052311;
	Tue, 20 May 2003 12:34:17 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 20 May 2003 12:34:17 +0000
Received: from prv-mail25.provo.novell.com (prv-mail25.provo.novell.com [137.65.81.121])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4KCYFEh052234
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 20 May 2003 12:34:15 GMT
	(envelope-from gvithalprasad@novell.com)
Received: from INET-PRV1-MTA by prv-mail25.provo.novell.com
	with Novell_GroupWise; Tue, 20 May 2003 06:33:55 -0600
Message-Id: <sec9cc53.021@prv-mail25.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.0 
Date: Tue, 20 May 2003 06:33:45 -0600
From: "Vithalprasad Gaitonde" <gvithalprasad@novell.com>
To: <ietf-ldapbis@OpenLDAP.org>
Cc: "Sarangthem Chanu" <CSarangthem@novell.com>,
        "Mukesh Nathan" <MNathan@novell.com>,
        "Savitha R" <RSAVITHA@novell.com>
Subject: Re: What Does De-Reference Mean?
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

Kurt,
Going by the same argument,  the rest of the search criteria e.g. the
base dn and scope of the search should also be applied after the alias
has been derferenced to the actual entry
So in the example below,

                  ou=deptB                                             
                     ou=deptA
                        |                                              
                                  |
             alias_teamA - - - - - - - - - - - - - - - - - - - - - - -
- -  - - - >ou= teamA
                                                                       
                                  |
                                                                       
                             ou= DT                                     
                                                             
                                                                       
                                  |
                                                                       
                             Computer object (objectClass=computer)
                                                                       
                                                                        
 
       Search Operation:
       set search base  = deptB               
       set search scope = subtree search 
       set deref aliases  = always
       search for objects of objectClass=computer

Computer object should not be returned as it does not qualify the scope
criteria for ou=deptb as the base.
Correct ?

Prasad

>>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 3/28/2003 5:12:53 AM >>>
It should be clear that each and every entry returned in
response to a search request did match the search filter.  That
is, if the filter is (CN=foo) than each entry returned has "foo"
as a (not necessarily returned) value of an attribute whose
type is CN or a subtype of CN.

When dereferencing during searching (by derefInSearching or
derefAlways), the filter should be matched against the entry which
the alias refers to, not the alias itself.

If the client asks for all alias objects, e.g, (objectClass=alias)
with dereferencing during finding enabled, then no entries should
be returned.  Likewise, when requesting (objectClass=*) with
dereferencing during finding enabled, none of entries returned
should belong to the alias objectClass.

So, to answer your specific question, it is not relevant to
the matching what values of CN the 'alias' has. The values
of the aliased entry are, however, quite relevant.

Kurt

 
At 11:22 AM 3/26/2003, Chris Harding wrote:
>Hi -
>
>The interpretation of the LDAP RFCs as regards dereferencing has
become an issue for the new certification program that The Open Group
plans to launch for LDAP servers. We have discussed it in the Directory
Interoperability Forum, and agreed that we should ask the experts in the
ldapbis group. Accordingly, I would like to ask your help in clarifying
this issue.
>
>Here's the issue. The requirement in the specification is:
>
>       When a server receives a search request with the derefAliases
field
>       set to derefInSearching then it will dereference aliases in
subordinates
>       of the base object in searching.
>
>We have a test suite for use in the certification program. The suite
includes a test of this requirement (which is in fact derived from a
test in BLITS). The test data includes two entries: Jonathan Adams and
Jonny Adams. The Jonny Adams entry is an alias for Jonathan Adams.
>
>The test should check that Jonny Adams is de-referenced and Jonathan
Adams is returned. The question is, should the test search for Jonny or
for Jonathan.
>
>RFC 2251 does not explain dereferencing but defers to X.501.
Unfortunately, X.501 does not seem to explain it very well. My personal
interpretation after reading it is that, whenever a server encounters an
alias entry in the course of a search and dereferencing has been
requested, the server should dereference the alias and carry on
searching from the entry that the alias points to. Under this
interpretation, a search for Jonny should return the same result as a
search for Jonathan - the Jonathan Adams entry.
>
>I don't claim to be an expert on the interpretation of the
specifications - but I hope that experts in the IETF community can shed
light on this!
>
>Please send your comments to the ldapbis list. I will report the
consensus (assuming that one is reached) to the DIF.
>
>Regards,
>
>Chris
>+++++
>
>========================================================================
>           Dr. Christopher J. Harding
>  T H E    Executive Director for the Directory Interoperability
Forum
> O P E N   Apex Plaza, Forbury Road, Reading RG1 1AX, UK
>G R O U P  Mailto:c.harding@opengroup.org Phone: +44 118 902 3018
>           WWW: http://www.opengroup.org Mobile: +44 774 063 1520
>========================================================================
>
>            The Open Group's Consortia Services - Association
Management For I.T.:
>            http://www.opengroup.org/consortia_services 
>
>========================================================================



From owner-ietf-ldapbis@OpenLDAP.org  Tue May 20 13:04:14 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 NAA21461
	for <ldapbis-archive@lists.ietf.org>; Tue, 20 May 2003 13:04:13 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4KGvKFH073812;
	Tue, 20 May 2003 17:03:57 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 h4KGr0Ib073525;
	Tue, 20 May 2003 16:53:00 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 20 May 2003 16:53:00 +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 h4KGqwEh073506
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 20 May 2003 16:52:58 GMT
	(envelope-from jimse@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Tue, 20 May 2003 10:52:37 -0600
Message-Id: <seca08f5.014@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.0 
Date: Tue, 20 May 2003 10:51:15 -0600
From: "Jim Sermersheim" <jimse@novell.com>
To: <skip.slone@lmco.com>,
        "Vithalprasad Gaitonde" <GVithalprasad.BLR3.BANGALORE@novell.com>,
        <ietf-ldapbis@OpenLDAP.org>, <d.w.chadwick@salford.ac.uk>
Cc: "Sarangthem Chanu" <CSarangthem.BLR1.BANGALORE@novell.com>,
        "Mukesh Nathan" <MNathan.BLR3.BANGALORE@novell.com>,
        "Savitha R" <RSAVITHA.BLR3.BANGALORE@novell.com>
Subject: Re: What Does De-Reference Mean?
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

Prasad, All,

The text in X.511 reads:

"If the searchAliases parameter is TRUE, aliases shall be dereferenced,
if the parameter is FALSE, aliases shall not be dereferenced. If the
searchAliases parameter is TRUE, the search shall continue in the
subtree of the aliased entry."

While overly vague (and maybe Skip or David can point to some better
documentation), to me, this means that if searchAliases is TRUE, then 
1) Every alias in the scope of the search is dereferenced. In my mind,
dereferenced implies that the entry is not considered in the search.
2) The search continues in the subtree of the aliased entry. To me, I
don't think this excludes subtrees that were not in the original
subtree.
2.1) If the original base was sub, then the dereferenced entry becomes
the new base for the continued search in the dereferenced subtree.
(effectively, set dereferenced entry as base and go to #1.)

If we are to exclude subtrees that are not held within the original
subtree, then what would the point of searchAliases be, other than to
exclude the alias object (which can be done in the filter anyway)?

I do agree, there is not enough documentation here.

Jim

>>> "Vithalprasad Gaitonde" <gvithalprasad@novell.com> 5/20/03 6:33:45
AM >>>
Kurt,
Going by the same argument,  the rest of the search criteria e.g. the
base dn and scope of the search should also be applied after the alias
has been derferenced to the actual entry
So in the example below,

                  ou=deptB                                            

                     ou=deptA
                        |                                             

                                  |
             alias_teamA - - - - - - - - - - - - - - - - - - - - - - -
- -  - - - >ou= teamA
                                                                      

                                  |
                                                                      

                             ou= DT                                    

                                                             
                                                                      

                                  |
                                                                      

                             Computer object (objectClass=computer)
                                                                      

                                                                       

 
       Search Operation:
       set search base  = deptB               
       set search scope = subtree search 
       set deref aliases  = always
       search for objects of objectClass=computer

Computer object should not be returned as it does not qualify the
scope
criteria for ou=deptb as the base.
Correct ?

Prasad

>>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 3/28/2003 5:12:53 AM >>>
It should be clear that each and every entry returned in
response to a search request did match the search filter.  That
is, if the filter is (CN=foo) than each entry returned has "foo"
as a (not necessarily returned) value of an attribute whose
type is CN or a subtype of CN.

When dereferencing during searching (by derefInSearching or
derefAlways), the filter should be matched against the entry which
the alias refers to, not the alias itself.

If the client asks for all alias objects, e.g, (objectClass=alias)
with dereferencing during finding enabled, then no entries should
be returned.  Likewise, when requesting (objectClass=*) with
dereferencing during finding enabled, none of entries returned
should belong to the alias objectClass.

So, to answer your specific question, it is not relevant to
the matching what values of CN the 'alias' has. The values
of the aliased entry are, however, quite relevant.

Kurt

 
At 11:22 AM 3/26/2003, Chris Harding wrote:
>Hi -
>
>The interpretation of the LDAP RFCs as regards dereferencing has
become an issue for the new certification program that The Open Group
plans to launch for LDAP servers. We have discussed it in the
Directory
Interoperability Forum, and agreed that we should ask the experts in
the
ldapbis group. Accordingly, I would like to ask your help in
clarifying
this issue.
>
>Here's the issue. The requirement in the specification is:
>
>       When a server receives a search request with the derefAliases
field
>       set to derefInSearching then it will dereference aliases in
subordinates
>       of the base object in searching.
>
>We have a test suite for use in the certification program. The suite
includes a test of this requirement (which is in fact derived from a
test in BLITS). The test data includes two entries: Jonathan Adams and
Jonny Adams. The Jonny Adams entry is an alias for Jonathan Adams.
>
>The test should check that Jonny Adams is de-referenced and Jonathan
Adams is returned. The question is, should the test search for Jonny
or
for Jonathan.
>
>RFC 2251 does not explain dereferencing but defers to X.501.
Unfortunately, X.501 does not seem to explain it very well. My
personal
interpretation after reading it is that, whenever a server encounters
an
alias entry in the course of a search and dereferencing has been
requested, the server should dereference the alias and carry on
searching from the entry that the alias points to. Under this
interpretation, a search for Jonny should return the same result as a
search for Jonathan - the Jonathan Adams entry.
>
>I don't claim to be an expert on the interpretation of the
specifications - but I hope that experts in the IETF community can
shed
light on this!
>
>Please send your comments to the ldapbis list. I will report the
consensus (assuming that one is reached) to the DIF.
>
>Regards,
>
>Chris
>+++++
>
>========================================================================
>           Dr. Christopher J. Harding
>  T H E    Executive Director for the Directory Interoperability
Forum
> O P E N   Apex Plaza, Forbury Road, Reading RG1 1AX, UK
>G R O U P  Mailto:c.harding@opengroup.org Phone: +44 118 902 3018
>           WWW: http://www.opengroup.org Mobile: +44 774 063 1520
>========================================================================
>
>            The Open Group's Consortia Services - Association
Management For I.T.:
>            http://www.opengroup.org/consortia_services 
>
>========================================================================



From owner-ietf-ldapbis@OpenLDAP.org  Wed May 21 14:52:40 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 OAA01668
	for <ldapbis-archive@lists.ietf.org>; Wed, 21 May 2003 14:52:40 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4LIjSF1061448;
	Wed, 21 May 2003 18:50:55 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 h4LIeHOo061161;
	Wed, 21 May 2003 18:40:17 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 21 May 2003 18:40:17 +0000
Received: from pat.uio.no (pat.uio.no [129.240.130.16])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4LIeEEh061138
	for <ietf-ldapbis@openldap.org>; Wed, 21 May 2003 18:40:15 GMT
	(envelope-from hbf@bombur.uio.no)
Received: from mail-mx2.uio.no ([129.240.10.30])
	by pat.uio.no with esmtp (Exim 2.12 #7)
	id 19IYVW-0001Vu-00; Wed, 21 May 2003 20:40:10 +0200
Received: from [129.240.130.14] (helo=mons.uio.no)
	by mail-mx2.uio.no with esmtp (Exim 4.14)
	id 19IYVN-0004c9-4b; Wed, 21 May 2003 20:40:01 +0200
Received: from bombur.uio.no ([129.240.186.42])
	by mons.uio.no with esmtp (Exim 2.12 #7)
	id 19IT04-00062L-00; Wed, 21 May 2003 14:47:20 +0200
Received: from hbf by bombur.uio.no with local (Exim 2.12 #7)
	id 19ISzv-00053Y-00; Wed, 21 May 2003 14:47:11 +0200
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Message-Id: <HBF.20030521ddj@bombur.uio.no>
To: steven.legg@adacel.com.au
Cc: ietf-ldapbis@OpenLDAP.org
Subject: Re: Generalized Time/UTC Time need leap seconds
In-Reply-To: <004a01c2ba94$9d780590$a518200a@osmium.mtwav.adacel.com.au>
References: <HBF.20030110genh@bombur.uio.no>
	<004a01c2ba94$9d780590$a518200a@osmium.mtwav.adacel.com.au>
Date: Wed, 21 May 2003 14:47:11 +0200
X-MailScanner-Information: Please contact postmaster@uio.no for more information
X-UiO-MailScanner: Found to be clean
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>

Steven Legg writes:

>>> [Syntaxes] 4.3.13 (Generalized Time) says:
>>> 
>>>       second  = %x30-36 %x30-39                        ; "00" to "59"
>>> 
>>> That should be "00" to "60", since Coordinated Universal Time has
>>> leap seconds.  See e.g. <http://tycho.usno.navy.mil/systime.html>.
> (...)
> The UTCTime type in X.680 doesn't allow for leap seconds (60 seconds
> is an illegal value). I still have to check whether GeneralizedTime
> allows it.

X.680 (07/2002) in
<http://www.itu.int/ITU-T/studygroups/com17/languages/> defers to
ISO 8601, which does allow leap seconds according to
<http://www.cl.cam.ac.uk/~mgk25/iso-time.html>.  I don't have the
actual ISO 8601 document.

-- 
Hallvard



From owner-ietf-ldapbis@OpenLDAP.org  Wed May 21 15:21:11 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 PAA04457
	for <ldapbis-archive@lists.ietf.org>; Wed, 21 May 2003 15:21:10 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4LJFSEl064090;
	Wed, 21 May 2003 19:19: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 h4LJF85J064069;
	Wed, 21 May 2003 19:15:08 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 21 May 2003 19:15:08 +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 h4LJF1Eh064053
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 21 May 2003 19:15:01 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 h4LJF0c6061086
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 21 May 2003 19:15:00 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030521121211.01a5a2b8@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Wed, 21 May 2003 12:12:15 -0700
To: ietf-ldapbis@OpenLDAP.org
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: additional ldapbis-user-schema comments
Mime-Version: 1.0
Content-Type: multipart/mixed;
	boundary="=====================_-1898691624==_"
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>

--=====================_-1898691624==_
Content-Type: text/plain; charset="us-ascii"

See attachment.

Kurt 
--=====================_-1898691624==_
Content-Type: text/plain; name="comments-ietf-ldapbis-user-schema-05.txt";
 x-mac-type="42494E41"; x-mac-creator="74747874"
Content-Disposition: attachment; filename="comments-ietf-ldapbis-user-schema-05.txt"
Content-Transfer-Encoding: base64

PiAgICAgICAgICAgICAgICAgICAgICAgICAgIExEQVA6ICBVc2VyIFNjaGVtYQo+ICAgICAgICAg
ICAgICAgICAgPGRyYWZ0LWlldGYtbGRhcGJpcy11c2VyLXNjaGVtYS0wNT4KPgo+QWJzdHJhY3QK
Pgo+ICAgVGhpcyBkb2N1bWVudCBpcyBhIGludGVncmFsIHBhcnQgb2YgdGhlIExEQVAgdGVjaG5p
Y2FsIHNwZWNpZmljYXRpb24gCj4gICBbUk9BRE1BUF0uICBJdCBwcm92aWRlcyBhbiBvdmVydmll
dyBvZiBhdHRyaWJ1dGUgdHlwZXMgYW5kIG9iamVjdCAKPiAgIGNsYXNzZXMgaW50ZW5kZWQgZm9y
IHVzZSBieSBMREFQIGRpcmVjdG9yeSBjbGllbnRzIGZvciBtYW55IAo+ICAgZGlyZWN0b3J5IHNl
cnZpY2VzLCBzdWNoIGFzLCBXaGl0ZSBQYWdlcy4KCnMvb3ZlcnZpZXcvdGVjaG5pY2FsIHNwZWNp
ZmljYXRpb24vCgo+ICAgT3JpZ2luYWxseSBzcGVjaWZpZWQgdGhlIAo+ICAgSVNPL0lFQyA5NTk0
IGFuZCBYLjUwMCBkb2N1bWVudHMsIHRoZXNlIG9iamVjdHMgYXJlIHdpZGVseSB1c2VkIGFzIGEg
Cj4gICBiYXNpcyBmb3IgdGhlIHNjaGVtYSBpbiBtYW55IExEQVAgZGlyZWN0b3JpZXMuICBUaGlz
IGRvY3VtZW50IGRvZXMgCj4gICBub3QgY292ZXIgYXR0cmlidXRlcyB1c2VkIGZvciB0aGUgYWRt
aW5pc3RyYXRpb24gb2YgZGlyZWN0b3J5IAo+ICAgc2VydmVycywgbm9yIGRvZXMgaXQgaW5jbHVk
ZSBkaXJlY3Rvcnkgb2JqZWN0cyBkZWZpbmVkIGZvciBzcGVjaWZpYyAKPiAgIHVzZXMgaW4gb3Ro
ZXIgZG9jdW1lbnRzLiAgCgpEZWxldGUgY2l0YXRpb24gaW4gQWJzdHJhY3QuClNwZWxsIG91dCBM
REFQIG9uIGZpcnN0IHVzZSBpbiBhYnN0cmFjdC4KCj4xLiAgSW50cm9kdWN0aW9uCj4KPiAgIFRo
aXMgZG9jdW1lbnQgcHJvdmlkZXMgYW4gb3ZlcnZpZXcgb2YgYXR0cmlidXRlIHR5cGVzIGFuZCBv
YmplY3QgCj4gICBjbGFzc2VzIGludGVuZGVkIGZvciB1c2UgYnkgTERBUCBkaXJlY3RvcnkgY2xp
ZW50cyBmb3IgbWFueSAKPiAgIGRpcmVjdG9yeSBzZXJ2aWNlcywgc3VjaCBhcywgV2hpdGUgUGFn
ZXMuCgpTcGVsbCBvdXQgTERBUCBvbiBmaXJzdCB1c2UgaW4gYm9keS4KCj4gICBPcmlnaW5hbGx5
IHNwZWNpZmllZCBpbiAKPiAgIHRoZSBJU08vSUVDIDk1OTQgYW5kIFguNTAwIGRvY3VtZW50cywg
dGhlc2Ugb2JqZWN0cyBhcmUgd2lkZWx5IHVzZWQgCj4gICBhcyBhIGJhc2lzIGZvciB0aGUgc2No
ZW1hIGluIG1hbnkgTERBUCBkaXJlY3Rvcmllcy4KCkFkZCByZWZlcmVuY2VzIHRvIHRoZXNlIGRv
Y3VtZW50cy4KCj4gICBUaGlzIGRvY3VtZW50IAo+ICAgZG9lcyBub3QgY292ZXIgYXR0cmlidXRl
cyB1c2VkIGZvciB0aGUgYWRtaW5pc3RyYXRpb24gb2YgZGlyZWN0b3J5IAo+ICAgc2VydmVycywg
bm9yIGRvZXMgaXQgaW5jbHVkZSBkaXJlY3Rvcnkgb2JqZWN0cyBkZWZpbmVkIGZvciBzcGVjaWZp
YyAKPiAgIHVzZXMgaW4gb3RoZXIgZG9jdW1lbnRzLgo+Cj4xLjEgIFNpdHVhdGlvbgo+Cj4gICBU
aGlzIGRvY3VtZW50IGlzIGEgaW50ZWdyYWwgcGFydCBvZiB0aGUgTERBUCB0ZWNobmljYWwgc3Bl
Y2lmaWNhdGlvbiAKPiAgIFtST0FETUFQXSB3aGljaCBvYnNvbGV0ZXMgdGhlIHByZXZpb3VzbHkg
ZGVmaW5lZCBMREFQIHRlY2huaWNhbCAKPiAgIHNwZWNpZmljYXRpb24gW1JGQzMzNzddIGluIGl0
cyBlbnRpcmV0eS4gIEluIHRlcm1zIG9mIFJGQyAyMjU2LCAKPiAgIFNlY3Rpb25zIDYgYW5kIDgg
b2YgUkZDIDIyNTYgYXJlIG9ic29sZXRlZCBieSBbU3ludGF4ZXNdLiAgCj4gICBTZWN0aW9ucyA1
LjEsIDUuMiwgNy4xIGFuZCA3LjIgb2YgUkZDIDIyNTYgYXJlIG9ic29sZXRlZCBieSBbTW9kZWxz
XS4KPiAgIFRoZSByZW1haW5kZXIgb2YgUkZDIDIyNTYgaXMgb2Jzb2xldGVkIGJ5IHRoaXMgZG9j
dW1lbnQuICBTZWN0aW9ucyAKPiAgIDMuNCBhbmQgNC40IG9mIHRoaXMgZG9jdW1lbnQgc3VwZXJj
ZWRlIHRoZSB0ZWNobmljYWwgc3BlY2lmaWNhdGlvbnMgCj4gICBmb3IgdGhlICdkYycgYXR0cmli
dXRlIHR5cGUgYW5kICdkb21haW4nIG9iamVjdCBjbGFzcyBmb3VuZCBpbiAKPiAgIFJGQyAyMjQ3
LiAgVGhlIHJlbWFpbmRlciBvZiBSRkMgMjI0NyByZW1haW5zIGluIGZvcmNlLgoKVGhvdWdoIGZp
bmUgZm9yIG5vdywgSSBub3RlIHRoYXQgUkZDIDIyNDcgc2hvdWxkIGJlIG9ic29sZXRlZCBieQph
IHJldmlzaW9uIGF0IHRoZSBzYW1lIHRpbWUgdGhpcyBJLUQgaXMgcHVibGlzaGVkLgoKPiAgIEEg
bnVtYmVyIG9mIHNjaGVtYSBlbGVtZW50cyB3aGljaCB3ZXJlIGluY2x1ZGVkIGluIHRoZSBwcmV2
aW91cyAKPiAgIHJldmlzaW9uIG9mIHRoZSBMREFQIFRlY2huaWNhbCBTcGVjaWZpY2F0aW9uIGFy
ZSBub3QgaW5jbHVkZWQgaW4gdGhpcwo+ICAgcmV2aXNpb24gb2YgTERBUC4gIFBLSS1yZWxhdGVk
IHNjaGVtYSBlbGVtZW50cyBhcmUgbm93IHNwZWNpZmllZCBpbiAKPiAgIFtMREFQLVBLSV0uICBV
bmxlc3MgcmVpbnRyb2R1Y2VkIGluIGZ1dHVyZSB0ZWNobmljYWwgc3BlY2lmaWNhdGlvbnMsIAo+
ICAgdGhlIHJlbWFpbmRlciBhcmUgdG8gYmUgY29uc2lkZXJlZCBIaXN0b3JpYy4KPgo+MS4yICBD
b252ZW50aW9ucwo+Cj4gICBUaGUga2V5IHdvcmRzICJNVVNUIiwgIk1VU1QgTk9UIiwgIlJFUVVJ
UkVEIiwgIlNIQUxMIiwgIlNIQUxMIE5PVCIsIAo+ICAgIlNIT1VMRCIsICJTSE9VTEQgTk9UIiwg
IlJFQ09NTUVOREVEIiwgICJNQVkiLCBhbmQgIk9QVElPTkFMIiBpbiB0aGlzCj4gICBkb2N1bWVu
dCBhcmUgdG8gYmUgaW50ZXJwcmV0ZWQgYXMgZGVzY3JpYmVkIGluIFJGQyAyMTE5IFtSRkMyMTE5
XS4KPgo+MS4zICBHZW5lcmFsIElzc3Vlcwo+Cj4gICBUaGlzIGRvY3VtZW50IHJlZmVyZW5jZXMg
U3ludGF4ZXMgZ2l2ZW4gaW4gU2VjdGlvbiAzIG9mIFtTeW50YXhlc10gCj4gICBhbmQgTWF0Y2hp
bmcgUnVsZXMgc3BlY2lmaWVkIGluIFNlY3Rpb24gNCBvZiBbU3ludGF4ZXNdLgo+Cj4gICBUaGUg
ZGVmaW5pdGlvbnMgb2YgQXR0cmlidXRlIFR5cGVzIGFuZCBPYmplY3QgQ2xhc3NlcyBhcmUgd3Jp
dHRlbiAKPiAgIHVzaW5nIHRoZSBBQk5GIGZvcm0gb2YgQXR0cmlidXRlVHlwZURlc2NyaXB0aW9u
IGFuZCAKPiAgIE9iamVjdENsYXNzRGVzY3JpcHRpb24gZ2l2ZW4gaW4gW01vZGVsc10uICBMaW5l
cyBoYXZlIGJlZW4gZm9sZGVkIAo+ICAgZm9yIHJlYWRhYmlsaXR5Lgo+Cj4xLjQgIFNvdXJjZQo+
Cj4gICBUaGUgc2NoZW1hIGRlZmluaXRpb25zIGluIHRoaXMgZG9jdW1lbnQgYXJlIGJhc2VkIG9u
IHRob3NlIGZvdW5kIGluIAo+ICAgdGhlIFguNTAwLXNlcmllcyBbWC41MjBdIGFuZCBbWC41MjFd
IGFuZCBSRkMgMjI0NyBbUkZDMjI0N10sIAo+ICAgc3BlY2lmaWNhbGx5Ogo+Cj4gICAgICAgIFNl
Y3Rpb25zICAgICAgICAgICAgIFNvdXJjZQo+ICAgICAgICA9PT09PT09PT09PT0gICAgICAgICA9
PT09PT09PT09PT09PT09PT0KPiAgICAgICAgMi4xIC0gMi4zICAgICAgICAgICAgWC41MjAgW1gu
NTIwXQo+ICAgICAgICAyLjQgICAgICAgICAgICAgICAgICBSRkMgMjI0NyBbUkZDMjI0N10KPiAg
ICAgICAgMi41IC0gMi40MiAgICAgICAgICAgWC41MjAgW1guNTIwXQo+ICAgICAgICAzLjEgIC0g
My4zICAgICAgICAgICBYLjUyMSBbWC41MjFdCj4gICAgICAgIDMuNCAgICAgICAgICAgICAgICAg
IFJGQyAyMjQ3IFtSRkMyMjQ3XQo+ICAgICAgICAzLjUgLSAzLjEzICAgICAgICAgICBYLjUyMSBb
WC41MjFdCgpBZGQ6CglIb3dldmVyLCB0aGUgZGVzY3JpcHRpb25zIGluIHRoaXMgZG9jdW1lbnQg
U0hBTEwgYmUgY29uc2lkZXJlZAoJZGVmaW5pdGl2ZSBmb3IgdXNlIGluIExEQVAuCgo+Mi4gQXR0
cmlidXRlIFR5cGVzCj4KPiAgIFRoZSBBdHRyaWJ1dGUgVHlwZXMgY29udGFpbmVkIGluIHRoaXMg
c2VjdGlvbiBob2xkIHVzZXIgaW5mb3JtYXRpb24uCj4KPiAgIFRoZXJlIGlzIG5vIHJlcXVpcmVt
ZW50IHRoYXQgc2VydmVycyBpbXBsZW1lbnQgdGhlIGZvbGxvd2luZyAKPiAgIEF0dHJpYnV0ZSBU
eXBlczogCj4KPiAgICAgICBzZWFyY2hHdWlkZQo+ICAgICAgIHRlbGV0ZXhUZXJtaW5hbElkZW50
aWZpZXIKPgo+ICAgSW4gZmFjdCwgdGhlaXIgdXNlIGlzIGdyZWF0bHkgZGlzY291cmFnZWQuCj4K
PiAgIEFuIExEQVAgc2VydmVyIGltcGxlbWVudGF0aW9uIFNIT1VMRCByZWNvZ25pemUgdGhlIHJl
c3Qgb2YgdGhlIAo+ICAgQXR0cmlidXRlIFR5cGVzIGRlc2NyaWJlZCBpbiB0aGlzIHNlY3Rpb24u
Cj4KPjIuMSAgYnVzaW5lc3NDYXRlZ29yeQo+Cj4gICBUaGlzIEF0dHJpYnV0ZSBUeXBlIGRlc2Ny
aWJlcyB0aGUga2luZCBvZiBidXNpbmVzcyBwZXJmb3JtZWQgYnkgCj4gICBhbiBvcmdhbml6YXRp
b24uCgpzL2tpbmQva2luZHMvIGFzIHRoZSBhdHRyaWJ1dGUgaXMgbXVsdGktdmFsdWVkLgpBZGQg
YW4gZXhhbXBsZS4gIChUaGVzZSBjb21tZW50cyBhcHBsaWVzIGdlbmVyYWxseSB0byBtb3N0IG90
aGVyCmF0dHJpYnV0ZSB0eXBlcyBzcGVjaWZpZWQgaW4gdGhpcyBzZWN0aW9uKS4KCj4gICAoIDIu
NS40LjE1IE5BTUUgJ2J1c2luZXNzQ2F0ZWdvcnknIAo+ICAgICAgRVFVQUxJVFkgY2FzZUlnbm9y
ZU1hdGNoCj4gICAgICBTVUJTVFIgY2FzZUlnbm9yZVN1YnN0cmluZ3NNYXRjaAo+ICAgICAgU1lO
VEFYIDEuMy42LjEuNC4xLjE0NjYuMTE1LjEyMS4xLjE1ezEyOH0gKSAKPgo+ICAgVGhlIFNZTlRB
WCBvaWQgaW5kaWNhdGVzIHRoZSBEaXJlY3RvcnkgU3RyaW5nIHN5bnRheC4KCkkgZmluZCB0aGlz
IHdvcmRpbmcgb2RkLCBlc3BlY2lhbGx5IHdpdGggIm9pZCIgYmVpbmcgaW4gbG93ZXIgY2FzZS4K
SWYgcmVmZXJyaW5nIHRvIDxvaWQ+IHByb2R1Y3Rpb24sIHRoZW4gdGhhdCBwcm9ibGVtYXRpYyBh
cyAKdGhlIHByb2R1Y3Rpb24gdG8gdGhlIHJpZ2h0IG9mIFNZTlRBWCBpcyBhIDxudW1lcmljb2lk
PiBub3QgYW4KPG9pZD4uICBPciBvbmUgbWlnaHQgdGhpbmsgdGhhdCBTWU5UQVggaXMgYW4gPG9p
ZD4uICBJIHN1Z2dlc3QKdGhpcyBiZSByZS13cml0dGVuCgogIDEuMy42LjEuNC4xLjE0NjYuMTE1
LjEyMS4xLjE1IHJlZmVycyB0byB0aGUgRGlyZWN0b3J5IFN0cmluZyBzeW50YXguCgpPciwgbGlr
ZSBbbW9kZWxzXSwgc2F5OgoJVGhlICdjYXNlSWdub3JlTWF0Y2gnIGFuZCAnY2FzZUlnbm9yZVN1
YnN0cmluZ3NNYXRjaCcgbWF0Y2hpbmcKCXJ1bGVzIGFuZCB0aGUgRGlyZWN0b3J5IFN0cmluZyAo
MS4zLjYuMS40LjEuMTQ2Ni4xMTUuMTIxLjEuMTUpCglzeW50YXggYXJlIGRlZmluZWQgaW4gW1N5
bnRheGVzXS4KCgo+Mi4yICBjCj4KPiAgIFRoaXMgaXMgdGhlIFguNTIwIFtYLjUyMF0gY291bnRy
eU5hbWUgQXR0cmlidXRlIFR5cGUsIHdoaWNoIGNvbnRhaW5zIAo+ICAgYSB0d28tbGV0dGVyIElT
TyAzMTY2IFtJU08zMTY2XWNvdW50cnkgY29kZS4KClRoaXMgd29yZGluZyBpcyBJIGZpbmQgYWNr
d2FyZCBhcyB0aGlzIHNwZWNpZmljYXRpb24gaXMKc3BlY2lmeWluZyBMREFQIGF0dHJpYnV0ZSB0
eXBlcywgbWFueSBvZiB3aGljaCBhcmUgZGVyaXZlZApmcm9tIFguNTIwIGF0dHJpYnV0ZSB0eXBl
cyBhbmQgaW1wbGllcyB0aGUgaW1wbGVtZW50b3IgbXVzdApyZWFkIFguNTIwIGluIG9yZGVyIHRv
IHN1cHBvcnQgdGhpcyBhdHRyaWJ1dGUgdHlwZS4gIEhlbmNlLApJIGJlbGlldmUgdGhpcyB3b3Vs
ZCBiZSBiZXR0ZXIgd29yZGVkOgoKCVRoZSBjIChjb3VudHJ5TmFtZSkgYXR0cmlidXRlIHR5cGUg
Y29udGFpbnMgYSB0d28tbGV0dGVyCglJU08gMzE2NiBbSVNPMzE2Nl0gY291bnRyeSBjb2RlIChl
LmcuLCAiREUiKS4gIChTb3VyY2U6CglYLjUyMCkKCihUaGlzIGNvbW1lbnQgYXBwbGllcyBnZW5l
cmFsbHkgdG8gbWFueSBvdGhlciBhdHRyaWJ1dGUgdHlwZXMKZGVmaW5lZCBpbiB0aGlzIHNlY3Rp
b24uKQoKPiAgICggMi41LjQuNiBOQU1FICdjJyAKPiAgICAgIFNVUCBuYW1lIAo+ICAgICAgU0lO
R0xFLVZBTFVFICkKPgo+Mi4zICBjbgo+Cj4gICBUaGlzIGlzIHRoZSBYLjUyMCBbWC41MjBdIGNv
bW1vbk5hbWUgQXR0cmlidXRlIFR5cGUsIHdoaWNoIGNvbnRhaW5zIAo+ICAgYSBuYW1lIG9mIGFu
IG9iamVjdC4gIElmIHRoZSBvYmplY3QgY29ycmVzcG9uZHMgdG8gYSBwZXJzb24sIGl0IGlzIAo+
ICAgdHlwaWNhbGx5IHRoZSBwZXJzb24ncyBmdWxsIG5hbWUuCj4KPiAgICggMi41LjQuMyBOQU1F
ICdjbicgCj4gICAgICBTVVAgbmFtZSApCj4KPjIuNCAgZGMKPgo+ICAgVGhlIGRjIChzaG9ydCBm
b3IgZG9tYWluQ29tcG9uZW50KSBhdHRyaWJ1dGUgdHlwZSBpcyBkZWZpbmVkIGFzIAo+ICAgZm9s
bG93czoKPgo+ICAgKCAwLjkuMjM0Mi4xOTIwMDMwMC4xMDAuMS4yNSBOQU1FICdkYycgCj4gICAg
ICBFUVVBTElUWSBjYXNlSWdub3JlSUE1TWF0Y2gKPiAgICAgIFNVQlNUUiBjYXNlSWdub3JlSUE1
U3Vic3RyaW5nc01hdGNoCj4gICAgICBTWU5UQVggMS4zLjYuMS40LjEuMTQ2Ni4xMTUuMTIxLjEu
MjYgCj4gICAgICBTSU5HTEUtVkFMVUUgKQo+Cj4gICBUaGUgdmFsdWUgb2YgdGhpcyBhdHRyaWJ1
dGUgaXMgYSBzdHJpbmcgaG9sZGluZyBvbmUgY29tcG9uZW50IG9mIGEgCj4gICBETlMgZG9tYWlu
IG5hbWUsIGUuZy4gImV4YW1wbGUiIG9yICJjb20iIChidXQgbm90ICJleGFtcGxlLmNvbSIpLgoK
cy9jb21wb25lbnQvY29tcG9uZW50LCBhIDxsYWJlbD4gW1JGQzEwMzRdLAoKKGFuZCBhZGQgbm9y
bWF0aXZlIHJlZmVyZW5jZSBiZWxvdykKCj4gICBUaGUgZW5jb2Rpbmcgb2YgSUE1U3RyaW5nIGZv
ciB1c2UgaW4gTERBUCBpcyBzaW1wbHkKPiAgIHRoZSBjaGFyYWN0ZXJzIG9mIHRoZSBzdHJpbmcg
aXRzZWxmLiAgVGhlIGVxdWFsaXR5IG1hdGNoaW5nIHJ1bGUgaXMgCj4gICBjYXNlIGluc2Vuc2l0
aXZlLCBhcyBpcyB0b2RheSdzIEROUy4KCkFkZDoKCUl0IGlzIG5vdGVkIHRoYXQgdGhlIGRpcmVj
dG9yeSB3aWxsIG5vdCBlbnN1cmUgdGhhdCB2YWx1ZXMgb2YgICAgICAKCXRoaXMgYXR0cmlidXRl
IGNvbmZvcm0gdG8gdGhlIGxhYmVsIHByb2R1Y3Rpb24gW1JGQzEwMzRdLiAgSXQKCWlzIHRoZSBh
cHBsaWNhdGlvbiByZXNwb25zaWJpbGl0eSB0byBlbnN1cmUgZG9tYWlucyBpdCBzdG9yZXMKCWlu
IHRoaXMgYXR0cmlidXRlIGFyZSBhcHByb3ByaWF0ZWx5IHJlcHJlc2VudGVkLgoKCUl0IGlzIGFs
c28gbm90ZWQgdGhhdCBhcHBsaWNhdGlvbnMgc3VwcG9ydGluZyBJbnRlcm5hdGlvbmFsaXplZAoJ
RG9tYWluIE5hbWVzIFNIQUxMIHVzZSB0aGUgVG9BU0NJSSBtZXRob2QgW1JGQzM0OTBdIHRvIHBy
b2R1Y2UKCTxsYWJlbD4gY29tcG9uZW50cyBvZiB0aGUgPGRvbWFpbj4gcHJvZHVjdGlvbi4KCihh
bmQgbGlzdCB0aGUgbm9ybWF0aXZlIHJlZmVyZW5jZXMgYmVsb3cpCgo+Mi41ICBkZXNjcmlwdGlv
bgo+Cj4gICBUaGlzIEF0dHJpYnV0ZSBUeXBlIGNvbnRhaW5zIGEgaHVtYW4tcmVhZGFibGUgZGVz
Y3JpcHRpb24gb2YgCj4gICB0aGUgb2JqZWN0LiAKPgo+ICAgKCAyLjUuNC4xMyBOQU1FICdkZXNj
cmlwdGlvbicgCj4gICAgICBFUVVBTElUWSBjYXNlSWdub3JlTWF0Y2gKPiAgICAgIFNVQlNUUiBj
YXNlSWdub3JlU3Vic3RyaW5nc01hdGNoCj4gICAgICBTWU5UQVggMS4zLjYuMS40LjEuMTQ2Ni4x
MTUuMTIxLjEuMTV7MTAyNH0gKSAKPgo+ICAgVGhlIFNZTlRBWCBvaWQgaW5kaWNhdGVzIHRoZSBE
aXJlY3RvcnkgU3RyaW5nIHN5bnRheC4KPgo+Mi42ICBkZXN0aW5hdGlvbkluZGljYXRvcgo+Cj4g
ICBUaGlzIGF0dHJpYnV0ZSBpcyB1c2VkIGZvciB0aGUgdGVsZWdyYW0gc2VydmljZS4KCkhvdyBp
cyBpdCB1c2VkPyAgU3VnZ2VzdCB5b3UgcGFyYXBoYXNlIHRoZSBYLjUyMCBkZXNjcmlwdGlvbi4K
CVRoZSBEZXN0aW5hdGlvbiBJbmRpY2F0b3IgYXR0cmlidXRlIHR5cGUgc3BlY2lmaWVzIChhY2Nv
cmRpbmcgdG8KCUlUVS1UIFJlYy4gRi4xIGFuZCBDQ0lUVCBSZWMuIEYuMzEpIHRoZSBjb3VudHJ5
IGFuZCBjaXR5IGFzc29jaWF0ZWQKCXdpdGggdGhlIG9iamVjdCAodGhlIGFkZHJlc3NlZSkgbmVl
ZGVkIHRvIHByb3ZpZGUgdGhlIFB1YmxpYwoJVGVsZWdyYW0gU2VydmljZS4gIChTb3VyY2U6IFgu
NTIwKQoKCj4gICAoIDIuNS40LjI3IE5BTUUgJ2Rlc3RpbmF0aW9uSW5kaWNhdG9yJyAKPiAgICAg
IEVRVUFMSVRZIGNhc2VJZ25vcmVNYXRjaAo+ICAgICAgU1VCU1RSIGNhc2VJZ25vcmVTdWJzdHJp
bmdzTWF0Y2gKPiAgICAgIFNZTlRBWCAxLjMuNi4xLjQuMS4xNDY2LjExNS4xMjEuMS40NHsxMjh9
ICkgCj4KPiAgIFRoZSBTWU5UQVggb2lkIGluZGljYXRlcyB0aGUgUHJpbnRhYmxlIFN0cmluZyBz
eW50YXguCj4KPgo+Mi43ICBkaXN0aW5ndWlzaGVkTmFtZQo+Cj4gICBUaGlzIEF0dHJpYnV0ZSBU
eXBlIGlzIG5vdCB1c2VkIGFzIHRoZSBuYW1lIG9mIHRoZSBvYmplY3QgaXRzZWxmLCAKPiAgIGJ1
dCBpdCBpcyBpbnN0ZWFkIGEgYmFzZSB0eXBlIGZyb20gd2hpY2ggYXR0cmlidXRlcyB3aXRoIERO
IHN5bnRheCAKPiAgIGluaGVyaXQuCj4KPiAgIEl0IGlzIHVubGlrZWx5IHRoYXQgdmFsdWVzIG9m
IHRoaXMgdHlwZSBpdHNlbGYgd2lsbCBvY2N1ciBpbiBhbiAKPiAgIGVudHJ5LiAgTERBUCBzZXJ2
ZXIgaW1wbGVtZW50YXRpb25zIHdoaWNoIGRvIG5vdCBzdXBwb3J0IGF0dHJpYnV0ZSAKPiAgIHN1
YnR5cGluZyBuZWVkIG5vdCByZWNvZ25pemUgdGhpcyBhdHRyaWJ1dGUgaW4gcmVxdWVzdHMuICBD
bGllbnQgCj4gICBpbXBsZW1lbnRhdGlvbnMgTVVTVCBOT1QgYXNzdW1lIHRoYXQgTERBUCBzZXJ2
ZXJzIGFyZSBjYXBhYmxlIG9mIAo+ICAgcGVyZm9ybWluZyBhdHRyaWJ1dGUgc3VidHlwaW5nLgo+
Cj4gICAoIDIuNS40LjQ5IE5BTUUgJ2Rpc3Rpbmd1aXNoZWROYW1lJyAKPiAgICAgIEVRVUFMSVRZ
IGRpc3Rpbmd1aXNoZWROYW1lTWF0Y2gKPiAgICAgIFNZTlRBWCAxLjMuNi4xLjQuMS4xNDY2LjEx
NS4xMjEuMS4xMiApCj4KPiAgIFRoZSBTWU5UQVggb2lkIGluZGljYXRlcyB0aGUgRE4gc3ludGF4
Lgo+Cj4yLjggIGRuUXVhbGlmaWVyCj4KPiAgIFRoZSBkblF1YWxpZmllciBBdHRyaWJ1dGUgVHlw
ZSBzcGVjaWZpZXMgZGlzYW1iaWd1YXRpbmcgaW5mb3JtYXRpb24gCj4gICB0byBhZGQgdG8gdGhl
IHJlbGF0aXZlIGRpc3Rpbmd1aXNoZWQgbmFtZSBvZiBhbiBlbnRyeS4gIEl0IGlzIAo+ICAgaW50
ZW5kZWQgZm9yIHVzZSB3aGVuIG1lcmdpbmcgZGF0YSBmcm9tIG11bHRpcGxlIHNvdXJjZXMgaW4g
b3JkZXIgdG8gCj4gICBwcmV2ZW50IGNvbmZsaWN0cyBiZXR3ZWVuIGVudHJpZXMgd2hpY2ggd291
bGQgb3RoZXJ3aXNlIGhhdmUgdGhlIHNhbWUKPiAgIG5hbWUuICBJdCBpcyByZWNvbW1lbmRlZCB0
aGF0IHRoZSB2YWx1ZSBvZiB0aGUgZG5RdWFsaWZpZXIgYXR0cmlidXRlIAo+ICAgYmUgdGhlIHNh
bWUgZm9yIGFsbCBlbnRyaWVzIGZyb20gYSBwYXJ0aWN1bGFyIHNvdXJjZS4KPgo+ICAgKCAyLjUu
NC40NiBOQU1FICdkblF1YWxpZmllcicgCj4gICAgICBFUVVBTElUWSBjYXNlSWdub3JlTWF0Y2gK
PiAgICAgIE9SREVSSU5HIGNhc2VJZ25vcmVPcmRlcmluZ01hdGNoIAo+ICAgICAgU1VCU1RSIGNh
c2VJZ25vcmVTdWJzdHJpbmdzTWF0Y2gKPiAgICAgIFNZTlRBWCAxLjMuNi4xLjQuMS4xNDY2LjEx
NS4xMjEuMS40NCApIAo+Cj4gICBUaGUgU1lOVEFYIG9pZCBpbmRpY2F0ZXMgdGhlIFByaW50YWJs
ZSBTdHJpbmcgc3ludGF4Lgo+Cj4yLjkgIGVuaGFuY2VkU2VhcmNoR3VpZGUKPgo+ICAgVGhpcyBh
dHRyaWJ1dGUgaXMgZm9yIHVzZSBieSBYLjUwMCBjbGllbnRzIGluIGNvbnN0cnVjdGluZyBzZWFy
Y2ggCj4gICBmaWx0ZXJzLgoKZGVsZXRlICJYLjUwMCIgb3IgcmVwbGFjZSB3aXRoICJkaXJlY3Rv
cnkiCgo+ICAgKCAyLjUuNC40NyBOQU1FICdlbmhhbmNlZFNlYXJjaEd1aWRlJwo+ICAgICAgU1lO
VEFYIDEuMy42LjEuNC4xLjE0NjYuMTE1LjEyMS4xLjIxICkgCj4KPiAgIFRoZSBTWU5UQVggb2lk
IGluZGljYXRlcyB0aGUgRW5oYW5jZWQgR3VpZGUgc3ludGF4Lgo+Cj4yLjEwICBmYWNzaW1pbGVU
ZWxlcGhvbmVOdW1iZXIKPgo+ICAgQSB2YWx1ZSBvZiB0aGlzIEF0dHJpYnV0ZSBUeXBlIGlzIGEg
dGVsZXBob25lIG51bWJlciBmb3IgYSBmYWNzaW1pbGUgCj4gICB0ZXJtaW5hbCAoYW5kLCBvcHRp
b25hbGx5LCBpdHMgcGFyYW1ldGVycykuCj4KPiAgICggMi41LjQuMjMgTkFNRSAnZmFjc2ltaWxl
VGVsZXBob25lTnVtYmVyJwo+ICAgICBTWU5UQVggMS4zLjYuMS40LjEuMTQ2Ni4xMTUuMTIxLjEu
MjIgKSAKPgo+ICAgVGhlIFNZTlRBWCBvaWQgaW5kaWNhdGVzIHRoZSBGYWNzaW1pbGUgVGVsZXBo
b25lIE51bWJlciBzeW50YXguCj4KPjIuMTEgIGdlbmVyYXRpb25RdWFsaWZpZXIKPgo+ICAgVGhl
IGdlbmVyYXRpb25RdWFsaWZpZXIgQXR0cmlidXRlIFR5cGUgY29udGFpbnMgdGhlIHBhcnQgb2Yg
YSAKPiAgIHBlcnNvbidzIG5hbWUgd2hpY2ggdHlwaWNhbGx5IGlzIHRoZSBzdWZmaXgsIGFzIGlu
ICJJSUlyZCIuCj4KPiAgICggMi41LjQuNDQgTkFNRSAnZ2VuZXJhdGlvblF1YWxpZmllcicgCj4g
ICAgICBTVVAgbmFtZSApCj4KPjIuMTIgIGdpdmVuTmFtZQo+Cj4gICBUaGUgZ2l2ZW5OYW1lIEF0
dHJpYnV0ZSBUeXBlIGlzIHVzZWQgdG8gaG9sZCB0aGUgcGFydCBvZiBhIHBlcnNvbidzIAo+ICAg
bmFtZSB3aGljaCBpcyBub3QgdGhlaXIgc3VybmFtZSBub3IgbWlkZGxlIG5hbWUuCgpUaGlzIGRl
ZmluaXRpb24gaXMgaW5jb25zaXNlbnQgd2l0aCBYLjUyMCBnaXZlbk5hbWUgd2hpY2ggZG9lc24n
dApleGNsdWRlIG1pZGRsZSBuYW1lIGZyb20gYmVpbmcgY29uc2lkZXJlZCBhIGdpdmVuIG5hbWUu
Cgo+ICAgKCAyLjUuNC40MiBOQU1FICdnaXZlbk5hbWUnIAo+ICAgICAgU1VQIG5hbWUgKQo+Cj4y
LjEzICBob3VzZUlkZW50aWZpZXIKPgo+ICAgVGhpcyBBdHRyaWJ1dGUgVHlwZSBpcyB1c2VkIHRv
IGlkZW50aWZ5IGEgYnVpbGRpbmcgd2l0aGluIGEgbG9jYXRpb24uCj4KPiAgICggMi41LjQuNTEg
TkFNRSAnaG91c2VJZGVudGlmaWVyJyAKPiAgICAgIEVRVUFMSVRZIGNhc2VJZ25vcmVNYXRjaCAK
PiAgICAgIFNVQlNUUiBjYXNlSWdub3JlU3Vic3RyaW5nc01hdGNoIAo+ICAgICAgU1lOVEFYIDEu
My42LjEuNC4xLjE0NjYuMTE1LjEyMS4xLjE1ezMyNzY4fSApIAo+Cj4gICBUaGUgU1lOVEFYIG9p
ZCBpbmRpY2F0ZXMgdGhlIERpcmVjdG9yeSBTdHJpbmcgc3ludGF4Lgo+Cj4yLjE0ICBpbml0aWFs
cwo+Cj4gICBUaGUgaW5pdGlhbHMgQXR0cmlidXRlIFR5cGUgY29udGFpbnMgdGhlIGluaXRpYWxz
IG9mIHNvbWUgb3IgYWxsIG9mIAo+ICAgYW4gaW5kaXZpZHVhbHMgbmFtZXMsIGV4Y2VwdCB0aGUg
c3VybmFtZShzKS4KPgo+ICAgICggMi41LjQuNDMgTkFNRSAnaW5pdGlhbHMnIAo+ICAgICAgU1VQ
IG5hbWUgKQo+Cj4yLjE1ICBpbnRlcm5hdGlvbmFsSVNETk51bWJlcgo+Cj4gICBBIHZhbHVlIG9m
IHRoaXMgQXR0cmlidXRlIFR5cGUgaXMgYW4gSVNETiBhZGRyZXNzLCBhcyBkZWZpbmVkIGluIAo+
ICAgSVRVIFJlY29tbWVuZGF0aW9uIEUuMTY0IFtFLjE2NF0uCj4KPiAgICggMi41LjQuMjUgTkFN
RSAnaW50ZXJuYXRpb25hbElTRE5OdW1iZXInIAo+ICAgICAgRVFVQUxJVFkgbnVtZXJpY1N0cmlu
Z01hdGNoIAo+ICAgICAgU1VCU1RSIG51bWVyaWNTdHJpbmdTdWJzdHJpbmdzTWF0Y2ggCj4gICAg
ICBTWU5UQVggMS4zLjYuMS40LjEuMTQ2Ni4xMTUuMTIxLjEuMzZ7MTZ9ICkgaQo+Cj4gICBUaGUg
U1lOVEFYIG9pZCBpbmRpY2F0ZXMgdGhlIE51bWVyaWMgU3RyaW5nIHN5bnRheC4KPgo+Mi4xNiAg
bAo+Cj4gICBUaGlzIGlzIHRoZSBYLjUyMCBbWC41MjBdIGxvY2FsaXR5TmFtZSBBdHRyaWJ1dGUg
VHlwZSwgd2hpY2ggCj4gICBjb250YWlucyB0aGUgbmFtZSBvZiBhIGxvY2FsaXR5IG9yIHBsYWNl
LCBzdWNoIGFzIGEgY2l0eSwgY291bnR5IG9yIAo+ICAgb3RoZXIgZ2VvZ3JhcGhpYyByZWdpb24u
Cj4KPiAgICAoIDIuNS40LjcgTkFNRSAnbCcgCj4gICAgICBTVVAgbmFtZSApCj4KPjIuMTcgIG1l
bWJlcgo+Cj4gICBBIHZhbHVlIG9mIHRoaXMgQXR0cmlidXRlIFR5cGUgaXMgdGhlIERpc3Rpbmd1
aXNoZWQgTmFtZSBvZiBhbiAKPiAgIG9iamVjdCB0aGF0IGlzIG9uIGEgbGlzdCBvciBpbiBhIGdy
b3VwLgo+Cj4gICAoIDIuNS40LjMxIE5BTUUgJ21lbWJlcicgCj4gICAgICBTVVAgZGlzdGluZ3Vp
c2hlZE5hbWUgKQo+Cj4yLjE4ICBuYW1lCj4KPiAgIFRoZSBuYW1lIEF0dHJpYnV0ZSBUeXBlIGlz
IHRoZSBhdHRyaWJ1dGUgc3VwZXJ0eXBlIGZyb20gd2hpY2ggc3RyaW5nIAo+ICAgQXR0cmlidXRl
IFR5cGVzIHR5cGljYWxseSB1c2VkIGZvciBuYW1pbmcgbWF5IGJlIGZvcm1lZC4gIEl0IGlzIAo+
ICAgdW5saWtlbHkgdGhhdCB2YWx1ZXMgb2YgdGhpcyB0eXBlIGl0c2VsZiB3aWxsIG9jY3VyIGlu
IGFuIGVudHJ5LiAgCj4gICBMREFQIHNlcnZlciBpbXBsZW1lbnRhdGlvbnMgd2hpY2ggZG8gbm90
IHN1cHBvcnQgYXR0cmlidXRlIHN1YnR5cGluZyAKPiAgIG5lZWQgbm90IHJlY29nbml6ZSB0aGlz
IGF0dHJpYnV0ZSBpbiByZXF1ZXN0cy4gIENsaWVudCAKPiAgIGltcGxlbWVudGF0aW9ucyBNVVNU
IE5PVCBhc3N1bWUgdGhhdCBMREFQIHNlcnZlcnMgYXJlIGNhcGFibGUgb2YgCj4gICBwZXJmb3Jt
aW5nIGF0dHJpYnV0ZSBzdWJ0eXBpbmcuCj4KPiAgICggMi41LjQuNDEgTkFNRSAnbmFtZScgCj4g
ICAgICBFUVVBTElUWSBjYXNlSWdub3JlTWF0Y2gKPiAgICAgIFNVQlNUUiBjYXNlSWdub3JlU3Vi
c3RyaW5nc01hdGNoCj4gICAgICBTWU5UQVggMS4zLjYuMS40LjEuMTQ2Ni4xMTUuMTIxLjEuMTV7
MzI3Njh9ICkgCj4KPiAgIFRoZSBTWU5UQVggb2lkIGluZGljYXRlcyB0aGUgRGlyZWN0b3J5IFN0
cmluZyBzeW50YXguCj4KPjIuMTkgIG8KPgo+ICAgVGhpcyBpcyB0aGUgWC41MjAgW1guNTIwXSBv
cmdhbml6YXRpb25OYW1lIEF0dHJpYnV0ZSBUeXBlLCB3aGljaCAKPiAgIGNvbnRhaW5zIHRoZSBu
YW1lIG9mIGFuIG9yZ2FuaXphdGlvbi4KPgo+ICAgKCAyLjUuNC4xMCBOQU1FICdvJyAKPiAgICAg
IFNVUCBuYW1lICkKPgo+Mi4yMCAgb3UKPgo+ICAgVGhpcyBpcyB0aGUgWC41MjAgW1guNTIwXSBv
cmdhbml6YXRpb25hbFVuaXROYW1lIEF0dHJpYnV0ZSBUeXBlLCAKPiAgIHdoaWNoIGNvbnRhaW5z
IHRoZSBuYW1lIG9mIGFuIG9yZ2FuaXphdGlvbmFsIHVuaXQuCj4KPiAgICAoIDIuNS40LjExIE5B
TUUgJ291JyAKPiAgICAgIFNVUCBuYW1lICkKPgo+Mi4yMSAgb3duZXIKPgo+ICAgQSB2YWx1ZSBv
ZiB0aGlzIEF0dHJpYnV0ZSBUeXBlIGlzIHRoZSBEaXN0aW5ndWlzaGVkIE5hbWUgb2YgYW4gCj4g
ICBvYmplY3QgdGhhdCBoYXMgYW4gb3duZXJzaGlwIHJlc3BvbnNpYmlsaXR5IGZvciB0aGUgb2Jq
ZWN0IHRoYXQgCj4gICBpcyBvd25lZC4KPgo+ICAgICggMi41LjQuMzIgTkFNRSAnb3duZXInIAo+
ICAgICAgU1VQIGRpc3Rpbmd1aXNoZWROYW1lICkKPgo+Mi4yMiAgcGh5c2ljYWxEZWxpdmVyeU9m
ZmljZU5hbWUKPgo+ICAgVGhpcyBhdHRyaWJ1dGUgY29udGFpbnMgdGhlIG5hbWUgdGhhdCBhIFBv
c3RhbCBTZXJ2aWNlIHVzZXMgdG8gCj4gICBpZGVudGlmeSBhIHBvc3Qgb2ZmaWNlLgo+Cj4gICAo
IDIuNS40LjE5IE5BTUUgJ3BoeXNpY2FsRGVsaXZlcnlPZmZpY2VOYW1lJyAKPiAgICAgIEVRVUFM
SVRZIGNhc2VJZ25vcmVNYXRjaAo+ICAgICAgU1VCU1RSIGNhc2VJZ25vcmVTdWJzdHJpbmdzTWF0
Y2gKPiAgICAgIFNZTlRBWCAxLjMuNi4xLjQuMS4xNDY2LjExNS4xMjEuMS4xNXsxMjh9ICkgCj4K
PiAgIFRoZSBTWU5UQVggb2lkIGluZGljYXRlcyB0aGUgRGlyZWN0b3J5IFN0cmluZyBzeW50YXgu
Cj4KPjIuMjMgIHBvc3RhbEFkZHJlc3MKPgo+ICAgVGhpcyBhdHRyaWJ1dGUgY29udGFpbnMgYW4g
YWRkcmVzcyB1c2VkIGJ5IGEgUG9zdGFsIFNlcnZpY2UgdG8gCj4gICBwZXJmb3JtIHNlcnZpY2Vz
IGZvciB0aGUgb2JqZWN0Lgo+Cj4gICAoIDIuNS40LjE2IE5BTUUgJ3Bvc3RhbEFkZHJlc3MnIAo+
ICAgICAgRVFVQUxJVFkgY2FzZUlnbm9yZUxpc3RNYXRjaAo+ICAgICAgU1VCU1RSIGNhc2VJZ25v
cmVMaXN0U3Vic3RyaW5nc01hdGNoCj4gICAgICBTWU5UQVggMS41LjYuMS40LjEuMTQ2Ni4xMTUu
MTIxLjEuNDEgKSAKPgo+ICAgVGhlIFNZTlRBWCBvaWQgaW5kaWNhdGVzIHRoZSBQb3N0YWwgQWRk
cmVzcyBzeW50YXguCj4KPjIuMjQgIHBvc3RhbENvZGUKPgo+ICAgVGhpcyBhdHRyaWJ1dGUgY29u
dGFpbnMgYSBjb2RlIHVzZWQgYnkgYSBQb3N0YWwgU2VydmljZSB0byBpZGVudGlmeSAKPiAgIGEg
cG9zdGFsIHNlcnZpY2Ugem9uZSwgc3VjaCBhcyB0aGUgc291dGhlcm4gcXVhZHJhbnQgb2YgYSBj
aXR5Lgo+Cj4gICAoIDIuNS40LjE3IE5BTUUgJ3Bvc3RhbENvZGUnIAo+ICAgICAgRVFVQUxJVFkg
Y2FzZUlnbm9yZU1hdGNoCj4gICAgICBTVUJTVFIgY2FzZUlnbm9yZVN1YnN0cmluZ3NNYXRjaAo+
ICAgICAgU1lOVEFYIDEuNS42LjEuNC4xLjE0NjYuMTE1LjEyMS4xLjE1ezQwfSApIAo+Cj4gICBU
aGUgU1lOVEFYIG9pZCBpbmRpY2F0ZXMgdGhlIERpcmVjdG9yeSBTdHJpbmcgc3ludGF4Lgo+Cj4y
LjI1ICBwb3N0T2ZmaWNlQm94Cj4KPiAgIFRoaXMgYXR0cmlidXRlIGNvbnRhaW5zIHRoZSBudW1i
ZXIgdGhhdCBhIFBvc3RhbCBTZXJ2aWNlIHVzZXMgd2hlbiBhIAo+ICAgY3VzdG9tZXIgYXJyYW5n
ZXMgdG8gcmVjZWl2ZSBtYWlsIGF0IGEgYm94IG9uIHByZW1pc2VzIG9mIHRoZSBQb3N0YWwgCj4g
ICBTZXJ2aWNlLgo+Cj4gICAoIDIuNS40LjE4IE5BTUUgJ3Bvc3RPZmZpY2VCb3gnIAo+ICAgICAg
RVFVQUxJVFkgY2FzZUlnbm9yZU1hdGNoCj4gICAgICBTVUJTVFIgY2FzZUlnbm9yZVN1YnN0cmlu
Z3NNYXRjaAo+ICAgICAgU1lOVEFYIDEuNS42LjEuNC4xLjE0NjYuMTE1LjEyMS4xLjE1ezQwfSAp
IAo+Cj4gICBUaGUgU1lOVEFYIG9pZCBpbmRpY2F0ZXMgdGhlIERpcmVjdG9yeSBTdHJpbmcgc3lu
dGF4Lgo+Cj4yLjI2ICBwcmVmZXJyZWREZWxpdmVyeU1ldGhvZAo+Cj4gICBUaGlzIGF0dHJpYnV0
ZSBjb250YWlucyBhbiBpbmRpY2F0aW9uIG9mIHRoZSBwcmVmZXJyZWQgbWV0aG9kIG9mIAo+ICAg
Z2V0dGluZyBhIG1lc3NhZ2UgdG8gdGhlIG9iamVjdC4KPgo+ICAgKCAyLjUuNC4yOCBOQU1FICdw
cmVmZXJyZWREZWxpdmVyeU1ldGhvZCcKPiAgICAgIFNZTlRBWCAxLjUuNi4xLjQuMS4xNDY2LjEx
NS4xMjEuMS4xNCAKPiAgICAgIFNJTkdMRS1WQUxVRSApCj4KPiAgIFRoZSBTWU5UQVggb2lkIGlu
ZGljYXRlcyB0aGUgRGVsaXZlcnkgTWV0aG9kIHN5bnRheC4KPgo+Mi4yNyAgcmVnaXN0ZXJlZEFk
ZHJlc3MKPgo+ICAgVGhpcyBhdHRyaWJ1dGUgaG9sZHMgYSBwb3N0YWwgYWRkcmVzcyBzdWl0YWJs
ZSBmb3IgcmVjZXB0aW9uIG9mIAo+ICAgdGVsZWdyYW1zIG9yIGV4cGVkaXRlZCBkb2N1bWVudHMs
IHdoZXJlIGl0IGlzIG5lY2Vzc2FyeSB0byBoYXZlIHRoZSAKPiAgIHJlY2lwaWVudCBhY2NlcHQg
ZGVsaXZlcnkuCj4KPiAgICggMi41LjQuMjYgTkFNRSAncmVnaXN0ZXJlZEFkZHJlc3MnIAo+ICAg
ICAgU1VQIHBvc3RhbEFkZHJlc3MKPiAgICAgIFNZTlRBWCAxLjMuNi4xLjQuMS4xNDY2LjExNS4x
MjEuMS40MSApIAo+Cj4gICBUaGUgU1lOVEFYIG9pZCBpbmRpY2F0ZXMgdGhlIFBvc3RhbCBBZGRy
ZXNzIHN5bnRheC4KPgo+Mi4yOCAgcm9sZU9jY3VwYW50Cj4KPiAgIEEgdmFsdWUgb2YgdGhpcyBB
dHRyaWJ1dGUgVHlwZSBpcyB0aGUgRGlzdGluZ3Vpc2hlZCBOYW1lIG9mIGFuIAo+ICAgb2JqZWN0
IChub3JtYWxseSBhIHBlcnNvbikgdGhhdCBmdWxmaWxscyB0aGUgcmVzcG9uc2liaWxpdGllcyBv
ZiBhIAo+ICAgcm9sZSBvYmplY3QuCj4KPiAgICggMi41LjQuMzMgTkFNRSAncm9sZU9jY3VwYW50
JyAKPiAgICAgIFNVUCBkaXN0aW5ndWlzaGVkTmFtZSApCj4KPjIuMjkgIHNlYXJjaEd1aWRlCj4K
PiAgIFRoaXMgQXR0cmlidXRlIFR5cGUgaXMgZm9yIHVzZSBieSBjbGllbnRzIGluIGNvbnN0cnVj
dGluZyBzZWFyY2ggCj4gICBmaWx0ZXJzLiAgSXQgaXMgc3VwZXJzZWRlZCBieSBlbmhhbmNlZFNl
YXJjaEd1aWRlLCBkZXNjcmliZWQgYWJvdmUgCj4gICBpbiBzZWN0aW9uIDIuOS4KPgo+ICAgKCAy
LjUuNC4xNCBOQU1FICdzZWFyY2hHdWlkZScKPiAgICAgIFNZTlRBWCAxLjMuNi4xLjQuMS4xNDY2
LjExNS4xMjEuMS4yNSApICA7IEd1aWRlCj4KPlRoZSBTWU5UQVggb2lkIGluZGljYXRlcyB0aGUg
R3VpZGUgc3ludGF4Lgo+Cj4yLjMwICBzZWVBbHNvCj4KPiAgIEEgdmFsdWUgb2YgdGhpcyBBdHRy
aWJ1dGUgVHlwZSBpcyB0aGUgRGlzdGluZ3Vpc2hlZCBOYW1lIG9mIGFuIAo+ICAgb2JqZWN0IHRo
YXQgaXMgcmVsYXRlZCB0byB0aGUgc3ViamVjdCBvYmplY3QuCj4KPiAgICAoIDIuNS40LjM0IE5B
TUUgJ3NlZUFsc28nIAo+ICAgICAgU1VQIGRpc3Rpbmd1aXNoZWROYW1lICkKPgo+Mi4zMSAgc2Vy
aWFsTnVtYmVyCj4KPiAgIFRoaXMgYXR0cmlidXRlIGNvbnRhaW5zIHRoZSBzZXJpYWwgbnVtYmVy
IG9mIGEgZGV2aWNlLgo+Cj4gICAgKCAyLjUuNC41IE5BTUUgJ3NlcmlhbE51bWJlcicgCj4gICAg
ICBFUVVBTElUWSBjYXNlSWdub3JlTWF0Y2gKPiAgICAgIFNVQlNUUiBjYXNlSWdub3JlU3Vic3Ry
aW5nc01hdGNoCj4gICAgICBTWU5UQVggMS4zLjYuMS40LjEuMTQ2Ni4xMTUuMTIxLjEuNDR7NjR9
ICkgCj4KPiAgIFRoZSBTWU5UQVggb2lkIGluZGljYXRlcyB0aGUgUHJpbnRhYmxlIFN0cmluZyBz
eW50YXguCj4KPjIuMzIgIHNuCj4KPiAgIFRoaXMgaXMgdGhlIFguNTIwIFtYLjUyMF0gc3VybmFt
ZSBBdHRyaWJ1dGUgVHlwZSwgd2hpY2ggY29udGFpbnMgdGhlIAo+ICAgZmFtaWx5IG5hbWUgb2Yg
YSBwZXJzb24uCj4KPiAgICggMi41LjQuNCBOQU1FICdzbicgCj4gICAgICBTVVAgbmFtZSApCj4K
PjIuMzMgIHN0Cj4KPiAgIFRoaXMgaXMgdGhlIFguNTIwIFtYLjUyMF0gc3RhdGVPclByb3ZpbmNl
TmFtZSBhdHRyaWJ1dGUsIHdoaWNoIAo+ICAgY29udGFpbnMgdGhlIGZ1bGwgbmFtZSBvZiBhIHN0
YXRlIG9yIHByb3ZpbmNlLgo+Cj4gICAoIDIuNS40LjggTkFNRSAnc3QnIAo+ICAgICAgU1VQIG5h
bWUgKQo+Cj4yLjM0ICBzdHJlZXQKPgo+ICAgVGhpcyBpcyB0aGUgWC41MjAgW1guNTIwXSBzdHJl
ZXRBZGRyZXNzIGF0dHJpYnV0ZSwgd2hpY2ggY29udGFpbnMgdGhlCj4gICBwaHlzaWNhbCBhZGRy
ZXNzIG9mIHRoZSBvYmplY3QgdG8gd2hpY2ggdGhlIGVudHJ5IGNvcnJlc3BvbmRzLCBzdWNoIAo+
ICAgYXMgYW4gYWRkcmVzcyBmb3IgcGFja2FnZSBkZWxpdmVyeS4KPgo+ICAgKCAyLjUuNC45IE5B
TUUgJ3N0cmVldCcgCj4gICAgICBFUVVBTElUWSBjYXNlSWdub3JlTWF0Y2gKPiAgICAgIFNVQlNU
UiBjYXNlSWdub3JlU3Vic3RyaW5nc01hdGNoCj4gICAgICBTWU5UQVggMS4zLjYuMS40LjEuMTQ2
Ni4xMTUuMTIxLjEuMTV7MTI4fSApIAo+Cj4gICBUaGUgU1lOVEFYIG9pZCBpbmRpY2F0ZXMgdGhl
IERpcmVjdG9yeSBTdHJpbmcgc3ludGF4Lgo+Cj4yLjM1ICB0ZWxlcGhvbmVOdW1iZXIKPgo+ICAg
QSB2YWx1ZSBvZiB0aGlzIEF0dHJpYnV0ZSBUeXBlIGlzIGEgdGVsZXBob25lIG51bWJlciBjb21w
bHlpbmcgd2l0aCAKPiAgIElUVSBSZWNvbW1lbmRhdGlvbiBFLjEyMyBbRS4xMjNdLgo+Cj4gICAo
IDIuNS40LjIwIE5BTUUgJ3RlbGVwaG9uZU51bWJlcicgCj4gICAgIEVRVUFMSVRZIHRlbGVwaG9u
ZU51bWJlck1hdGNoCj4gICAgIFNVQlNUUiB0ZWxlcGhvbmVOdW1iZXJTdWJzdHJpbmdzTWF0Y2gK
PiAgICAgU1lOVEFYIDEuMy42LjEuNC4xLjE0NjYuMTE1LjEyMS4xLjUwezMyfSApIAo+Cj4gICBU
aGUgU1lOVEFYIG9pZCBpbmRpY2F0ZXMgdGhlIFRlbGVwaG9uZSBOdW1iZXIgc3ludGF4Lgo+Cj4y
LjM2ICB0ZWxldGV4VGVybWluYWxJZGVudGlmaWVyCj4KPiAgIFRoZSB3aXRoZHJhd2FsIG9mIFJl
Yy4gRi4yMDAgaGFzIHJlc3VsdGVkIGluIHRoZSB3aXRoZHJhd2FsIG9mIHRoaXMgCj4gICBhdHRy
aWJ1dGUuIAo+Cj4gICAoIDIuNS40LjIyIE5BTUUgJ3RlbGV0ZXhUZXJtaW5hbElkZW50aWZpZXIn
Cj4gICAgIFNZTlRBWCAxLjMuNi4xLjQuMS4xNDY2LjExNS4xMjEuMS41MSApIAo+Cj4gICBUaGUg
U1lOVEFYIG9pZCBpbmRpY2F0ZXMgdGhlIFRlbGV0ZXggVGVybWluYWwgSWRlbnRpZmllciBzeW50
YXguCj4KPjIuMzcgIHRlbGV4TnVtYmVyCj4KPiAgIEEgdmFsdWUgb2YgdGhpcyBBdHRyaWJ1dGUg
VHlwZSBpcyBhIHRlbGV4IG51bWJlciwgY291bnRyeSBjb2RlLCBhbmQgCj4gICBhbnN3ZXJiYWNr
IGNvZGUgb2YgYSB0ZWxleCB0ZXJtaW5hbC4KPgo+ICAgKCAyLjUuNC4yMSBOQU1FICd0ZWxleE51
bWJlcicKPiAgICAgIFNZTlRBWCAxLjMuNi4xLjQuMS4xNDY2LjExNS4xMjEuMS41MiApIAo+Cj4g
ICBUaGUgU1lOVEFYIG9pZCBpbmRpY2F0ZXMgdGhlIFRlbGV4IE51bWJlciBzeW50YXguCj4KPjIu
MzggIHRpdGxlCj4KPiAgIFRoaXMgYXR0cmlidXRlIGNvbnRhaW5zIHRoZSB0aXRsZSwgc3VjaCBh
cyAiVmljZSBQcmVzaWRlbnQiLCBvZiBhIAo+ICAgcGVyc29uIGluIHRoZWlyIG9yZ2FuaXphdGlv
bmFsIGNvbnRleHQuICBUaGUgInBlcnNvbmFsVGl0bGUiCj4gICBhdHRyaWJ1dGUgd291bGQgYmUg
dXNlZCBmb3IgYSBwZXJzb24ncyB0aXRsZSBpbmRlcGVuZGVudCBvZiB0aGVpciAKPiAgIGpvYiBm
dW5jdGlvbi4KPgo+ICAgKCAyLjUuNC4xMiBOQU1FICd0aXRsZScgCj4gICAgICBTVVAgbmFtZSAp
Cj4KPjIuMzkgIHVuaXF1ZU1lbWJlcgo+Cj4gICBBIHZhbHVlIG9mIHRoaXMgQXR0cmlidXRlIFR5
cGUgaXMgdGhlIERpc3Rpbmd1aXNoZWQgTmFtZSBvZiBhbiAKPiAgIG9iamVjdCB0aGF0IGlzIG9u
IGEgbGlzdCBvciBpbiBhIGdyb3VwLCB3aGVyZSB0aGUgUmVsYXRpdmUgCj4gICBEaXN0aW5ndWlz
aGVkIE5hbWUgb2YgdGhlIG9iamVjdCBpbmNsdWRlcyBhIHZhbHVlIHRoYXQgZGlzdGluZ3Vpc2hz
IAo+ICAgYmV0d2VlbiBvYmplY3RzIHdoZW4gYSBkaXN0aW5ndWlzaGVkIG5hbWUgaGFzIGJlZW4g
cmV1c2VkLgo+Cj4gICAoIDIuNS40LjUwIE5BTUUgJ3VuaXF1ZU1lbWJlcicgCj4gICAgICBFUVVB
TElUWSB1bmlxdWVNZW1iZXJNYXRjaAo+ICAgICAgU1lOVEFYIDEuMy42LjEuNC4xLjE0NjYuMTE1
LjEyMS4xLjM0ICkgCj4KPlRoZSBTWU5UQVggb2lkIGluZGljYXRlcyB0aGUgTmFtZSBhbmQgT3B0
aW9uYWwgVUlEIHN5bnRheC4KPgo+Mi40MCAgdXNlclBhc3N3b3JkCj4KPiAgIEEgdmFsdWUgb2Yg
dGhpcyBBdHRyaWJ1dGUgVHlwZSBpcyBhIGNoYXJhY3RlciBzdHJpbmcgdGhhdCBpcyBrbm93biAK
PiAgIG9ubHkgdG8gdGhlIHVzZXIgYW5kIHRoZSBzeXN0ZW0gdG8gd2hpY2ggdGhlIHVzZXIgaGFz
IGFjY2Vzcy4KPgo+ICAgKCAyLjUuNC4zNSBOQU1FICd1c2VyUGFzc3dvcmQnIAo+ICAgICAgRVFV
QUxJVFkgb2N0ZXRTdHJpbmdNYXRjaAo+ICAgICAgU1lOVEFYIDEuMy42LjEuNC4xLjE0NjYuMTE1
LjEyMS4xLjQwezEyOH0gKSAKPgo+ICAgVGhlIFNZTlRBWCBvaWQgaW5kaWNhdGVzIHRoZSBPY3Rl
dCBTdHJpbmcgc3ludGF4Lgo+Cj4gICBQYXNzd29yZHMgYXJlIHN0b3JlZCB1c2luZyBhbiBPY3Rl
dCBTdHJpbmcgc3ludGF4IGFuZCBhcmUgbm90IAo+ICAgZW5jcnlwdGVkLiAgVHJhbnNmZXIgb2Yg
Y2xlYXJ0ZXh0IHBhc3N3b3JkcyBpcyBzdHJvbmdseSBkaXNjb3VyYWdlZCAKPiAgIHdoZXJlIHRo
ZSB1bmRlcmx5aW5nIHRyYW5zcG9ydCBzZXJ2aWNlIGNhbm5vdCBndWFyYW50ZWUgCj4gICBjb25m
aWRlbnRpYWxpdHkgYW5kIG1heSByZXN1bHQgaW4gZGlzY2xvc3VyZSBvZiB0aGUgcGFzc3dvcmQg
dG8gCj4gICB1bmF1dGhvcml6ZWQgcGFydGllcy4KPgo+Mi40MSAgeDEyMUFkZHJlc3MKPgo+ICAg
QSB2YWx1ZSBvZiB0aGlzIEF0dHJpYnV0ZSBUeXBlIGlzIGEgZGF0YSBuZXR3b3JrIGFkZHJlc3Mg
YXMgZGVmaW5lZCAKPiAgIGJ5IElUVSBSZWNvbW1lbmRhdGlvbiBYLjEyMSBbWC4xMjFdLgo+Cj4g
ICAoIDIuNS40LjI0IE5BTUUgJ3gxMjFBZGRyZXNzJyAKPiAgICAgIEVRVUFMSVRZIG51bWVyaWNT
dHJpbmdNYXRjaAo+ICAgICAgU1VCU1RSIG51bWVyaWNTdHJpbmdTdWJzdHJpbmdzTWF0Y2gKPiAg
ICAgIFNZTlRBWCAxLjMuNi4xLjQuMS4xNDY2LjExNS4xMjEuMS4zNnsxNX0gKSAKPgo+ICAgVGhl
IFNZTlRBWCBvaWQgaW5kaWNhdGVzIHRoZSBOdW1lcmljIFN0cmluZyBzeW50YXguCj4KPjIuNDIg
IHg1MDBVbmlxdWVJZGVudGlmaWVyCj4KPiAgIFRoZSB4NTAwVW5pcXVlSWRlbnRpZmllciBBdHRy
aWJ1dGUgVHlwZSBpcyB1c2VkIHRvIGRpc3Rpbmd1aXNoIAo+ICAgYmV0d2VlbiBvYmplY3RzIHdo
ZW4gYSBkaXN0aW5ndWlzaGVkIG5hbWUgaGFzIGJlZW4gcmV1c2VkLiAgSW4gWC41MjAgCj4gICBb
WC41MjBdLCB0aGlzIEF0dHJpYnV0ZSBUeXBlIGlzIGNhbGxlZCB1bmlxdWVJZGVudGlmaWVyLiAg
VGhpcyBpcyBhIAo+ICAgZGlmZmVyZW50IEF0dHJpYnV0ZSBUeXBlIGZyb20gYm90aCB0aGUgInVp
ZCIgYW5kICJ1bmlxdWVJZGVudGlmaWVyIiAKPiAgIEF0dHJpYnV0ZSBUeXBlcy4KPgo+ICAgKCAy
LjUuNC40NSBOQU1FICd4NTAwVW5pcXVlSWRlbnRpZmllcicgCj4gICAgICBFUVVBTElUWSBiaXRT
dHJpbmdNYXRjaAo+ICAgICAgU1lOVEFYIDEuMy42LjEuNC4xLjE0NjYuMTE1LjEyMS4xLjYgKSAK
Pgo+ICAgVGhlIFNZTlRBWCBvaWQgaW5kaWNhdGVzIHRoZSBCaXQgU3RyaW5nIHN5bnRheC4KPgo+
Cj4zLiAgT2JqZWN0IENsYXNzZXMKPgo+ICAgTERBUCBzZXJ2ZXJzIFNIT1VMRCByZWNvZ25pemUg
YWxsIHRoZSBPYmplY3QgQ2xhc3NlcyBsaXN0ZWQgaGVyZSBhcyAKPiAgIHZhbHVlcyBvZiB0aGUg
b2JqZWN0Q2xhc3MgYXR0cmlidXRlLgo+Cj4zLjEgIGFwcGxpY2F0aW9uUHJvY2Vzcwo+Cj4gICBU
aGUgYXBwbGljYXRpb25Qcm9jZXNzIE9iamVjdCBDbGFzcyBkZWZpbml0aW9uIGlzIHRoZSBiYXNp
cyBvZiBhbiAKPiAgIGVudHJ5IHdoaWNoIHJlcHJlc2VudHMgYW4gYXBwbGljYXRpb24gZXhlY3V0
aW5nIGluIGEgY29tcHV0ZXIgc3lzdGVtLgo+Cj4gICAoIDIuNS42LjExIE5BTUUgJ2FwcGxpY2F0
aW9uUHJvY2VzcycgCj4gICAgICBTVVAgdG9wIAo+ICAgICAgU1RSVUNUVVJBTCAKPiAgICAgIE1V
U1QgY24KPiAgICAgIE1BWSAoIHNlZUFsc28gJCAKPiAgICAgICAgICAgIG91ICQgCj4gICAgICAg
ICAgICBsICQgCj4gICAgICAgICAgICBkZXNjcmlwdGlvbiApICkgCj4KPjMuMiAgY291bnRyeQo+
Cj4gICBUaGUgY291bnRyeSBPYmplY3QgQ2xhc3MgZGVmaW5pdGlvbiBpcyB0aGUgYmFzaXMgb2Yg
YW4gZW50cnkgd2hpY2ggCj4gICByZXByZXNlbnRzIGEgY291bnRyeS4KPgo+ICAgKCAyLjUuNi4y
IE5BTUUgJ2NvdW50cnknIAo+ICAgICAgU1VQIHRvcCAKPiAgICAgIFNUUlVDVFVSQUwgCj4gICAg
ICBNVVNUIGMKPiAgICAgIE1BWSAoIHNlYXJjaEd1aWRlICQgCj4gICAgICAgICAgICBkZXNjcmlw
dGlvbiApICkKPgo+My4zICBkZXZpY2UKPgo+ICAgVGhlIGRldmljZSBPYmplY3QgQ2xhc3MgaXMg
dGhlIGJhc2lzIG9mIGFuIGVudHJ5IHdoaWNoIHJlcHJlc2VudHMgCj4gICBhbiBhcHBsaWFuY2Ug
b3IgY29tcHV0ZXIgb3IgbmV0d29yayBlbGVtZW50Lgo+Cj4gICAoIDIuNS42LjE0IE5BTUUgJ2Rl
dmljZScgCj4gICAgICBTVVAgdG9wIAo+ICAgICAgU1RSVUNUVVJBTCAKPiAgICAgIE1VU1QgY24K
PiAgICAgIE1BWSAoIHNlcmlhbE51bWJlciAkIAo+ICAgICAgICAgICAgc2VlQWxzbyAkIAo+ICAg
ICAgICAgICAgb3duZXIgJCAKPiAgICAgICAgICAgIG91ICQgCj4gICAgICAgICAgICBvICQgCj4g
ICAgICAgICAgICBsICQgCj4gICAgICAgICAgICBkZXNjcmlwdGlvbiApICkKPgo+My40ICBkb21h
aW4KPgo+ICAgVGhlIGRvbWFpbiBPYmplY3QgQ2xhc3MgaXMgdGhlIGJhc2lzIG9mIGFuIGVudHJ5
IHdoaWNoIHJlcHJlc2VudHMgYSAKPiAgIHBvcnRpb24gb2YgYSBuZXR3b3JrLCBhcyBvcmdhbml6
ZWQgYnkgRE5TLiAgCj4KPiAgICggMC45LjIzNDIuMTkyMDAzMDAuMTAwLjQuMTMgTkFNRSAnZG9t
YWluJyAKPiAgICAgIFNVUCB0b3AgCj4gICAgICBTVFJVQ1RVUkFMCj4gICAgICBNVVNUIGRjCj4g
ICAgICBNQVkgKCB1c2VyUGFzc3dvcmQgJCBzZWFyY2hHdWlkZSAkIHNlZUFsc28gJCBidXNpbmVz
c0NhdGVnb3J5ICQKPiAgICAgICAgICB4MTIxQWRkcmVzcyAkIHJlZ2lzdGVyZWRBZGRyZXNzICQg
ZGVzdGluYXRpb25JbmRpY2F0b3IgJAo+ICAgICAgICAgIHByZWZlcnJlZERlbGl2ZXJ5TWV0aG9k
ICQgdGVsZXhOdW1iZXIgJAo+ICAgICAgICAgIHRlbGV0ZXhUZXJtaW5hbElkZW50aWZpZXIgJCB0
ZWxlcGhvbmVOdW1iZXIgJAo+ICAgICAgICAgIGludGVybmF0aW9uYWxpU0ROTnVtYmVyICQgIGZh
Y3NpbWlsZVRlbGVwaG9uZU51bWJlciAkIHN0cmVldCAkCj4gICAgICAgICAgcG9zdE9mZmljZUJv
eCAkIHBvc3RhbENvZGUgJCBwb3N0YWxBZGRyZXNzICQKPiAgICAgICAgICBwaHlzaWNhbERlbGl2
ZXJ5T2ZmaWNlTmFtZSAkIHN0ICQgbCAkIGRlc2NyaXB0aW9uICQgbyAkCj4gICAgICAgICAgYXNz
b2NpYXRlZE5hbWUgKSApCj4KPiAgIEFuIGV4YW1wbGUgZW50cnkgd291bGQgYmU6Cj4KPiAgIGRu
OiBkYz10Y3AsZGM9Y3JpdGljYWwtYW5nbGUsZGM9Y29tCj4gICBvYmplY3RDbGFzczogdG9wCj4g
ICBvYmplY3RDbGFzczogZG9tYWluCj4gICBkYzogdGNwCj4gICBkZXNjcmlwdGlvbjogYSBwbGFj
ZWhvbGRlciBlbnRyeSB1c2VkIHdpdGggU1JWIHJlY29yZHMKClRoaXMgc2hvdWxkIGJlIGxlZnQg
dG8gUkZDIDIyNDcgKGFuZCBSRkMgMjI0N2JpcykuCgo+My41ICBncm91cE9mTmFtZXMKPgo+ICAg
VGhlIGdyb3VwT2ZOYW1lcyBPYmplY3QgQ2xhc3MgaXMgdGhlIGJhc2lzIG9mIGFuIGVudHJ5IHdo
aWNoIAo+ICAgcmVwcmVzZW50cyBhIHNldCBvZiBuYW1lZCBvYmplY3RzIGluY2x1ZGluZyBpbmZv
cm1hdGlvbiByZWxhdGVkIHRvIAo+ICAgdGhlIHB1cnBvc2Ugb3IgbWFpbnRlbmFuY2Ugb2YgdGhl
IHNldC4KPgo+ICAgKCAyLjUuNi45IE5BTUUgJ2dyb3VwT2ZOYW1lcycgCj4gICAgICBTVVAgdG9w
IAo+ICAgICAgU1RSVUNUVVJBTCAKPiAgICAgIE1VU1QgKCBtZW1iZXIgJCAKPiAgICAgICAgICAg
ICBjbiApCj4gICAgICBNQVkgKCBidXNpbmVzc0NhdGVnb3J5ICQgCj4gICAgICAgICAgICBzZWVB
bHNvICQgCj4gICAgICAgICAgICBvd25lciAkIAo+ICAgICAgICAgICAgb3UgJCAKPiAgICAgICAg
ICAgIG8gJCAKPiAgICAgICAgICAgIGRlc2NyaXB0aW9uICkgKQo+Cj4zLjYgIGdyb3VwT2ZVbmlx
dWVOYW1lcwo+Cj4gICBUaGUgZ3JvdXBPZlVuaXF1ZU5hbWVzIE9iamVjdCBDbGFzcyBpcyB0aGUg
c2FtZSBhcyB0aGUgZ3JvdXBPZk5hbWVzIAo+ICAgb2JqZWN0IGNsYXNzIGV4Y2VwdCB0aGF0IHRo
ZSBvYmplY3QgbmFtZXMgYXJlIG5vdCByZXBlYXRlZCBvciAKPiAgIHJlYXNzaWduZWQgd2l0aGlu
IGEgc2V0IHNjb3BlLgo+Cj4gICAoIDIuNS42LjE3IE5BTUUgJ2dyb3VwT2ZVbmlxdWVOYW1lcycg
Cj4gICAgICBTVVAgdG9wIAo+ICAgICAgU1RSVUNUVVJBTAo+ICAgICAgTVVTVCAoIHVuaXF1ZU1l
bWJlciAkIAo+ICAgICAgICAgICAgIGNuICkKPiAgICAgIE1BWSAoIGJ1c2luZXNzQ2F0ZWdvcnkg
JCAKPiAgICAgICAgICAgIHNlZUFsc28gJCAKPiAgICAgICAgICAgIG93bmVyICQgCj4gICAgICAg
ICAgICBvdSAkIAo+ICAgICAgICAgICAgbyAkIAo+ICAgICAgICAgICAgZGVzY3JpcHRpb24gKSAp
IAo+Cj4zLjcgIGxvY2FsaXR5Cj4KPiAgIFRoZSBsb2NhbGl0eSBPYmplY3QgQ2xhc3MgaXMgdGhl
IGJhc2lzIG9mIGFuIGVudHJ5IHdoaWNoIAo+ICAgcmVwcmVzZW50cyBhIHBsYWNlIGluIHRoZSBw
aHlzaWNhbCB3b3JsZC4KPgo+ICAgKCAyLjUuNi4zIE5BTUUgJ2xvY2FsaXR5JyAKPiAgICAgIFNV
UCB0b3AgCj4gICAgICBTVFJVQ1RVUkFMCj4gICAgICBNQVkgKCBzdHJlZXQgJCAKPiAgICAgICAg
ICAgIHNlZUFsc28gJCAKPiAgICAgICAgICAgIHNlYXJjaEd1aWRlICQgCj4gICAgICAgICAgICBz
dCAkIAo+ICAgICAgICAgICAgbCAkIAo+ICAgICAgICAgICAgZGVzY3JpcHRpb24gKSApCj4KPjMu
OCAgb3JnYW5pemF0aW9uCj4KPiAgIFRoZSBvcmdhbml6YXRpb24gT2JqZWN0IENsYXNzIGlzIHRo
ZSBiYXNpcyBvZiBhbiBlbnRyeSB3aGljaCAKPiAgIHJlcHJlc2VudHMgYSBzdHJ1Y3R1cmVkIGdy
b3VwIG9mIHBlb3BsZS4KPgo+ICAgKCAyLjUuNi40IE5BTUUgJ29yZ2FuaXphdGlvbicgCj4gICAg
ICBTVVAgdG9wIAo+ICAgICAgU1RSVUNUVVJBTCAKPiAgICAgIE1VU1Qgbwo+ICAgICAgTUFZICgg
dXNlclBhc3N3b3JkICQgc2VhcmNoR3VpZGUgJCBzZWVBbHNvICQgCj4gICAgICAgICAgICBidXNp
bmVzc0NhdGVnb3J5ICQgeDEyMUFkZHJlc3MgJCByZWdpc3RlcmVkQWRkcmVzcyAkIAo+ICAgICAg
ICAgICAgZGVzdGluYXRpb25JbmRpY2F0b3IgJCBwcmVmZXJyZWREZWxpdmVyeU1ldGhvZCAkIAo+
ICAgICAgICAgICAgdGVsZXhOdW1iZXIgJCB0ZWxldGV4VGVybWluYWxJZGVudGlmaWVyICQgdGVs
ZXBob25lTnVtYmVyICQgCj4gICAgICAgICAgICBpbnRlcm5hdGlvbmFsaVNETk51bWJlciAkIGZh
Y3NpbWlsZVRlbGVwaG9uZU51bWJlciAkIAo+ICAgICAgICAgICAgc3RyZWV0ICQgcG9zdE9mZmlj
ZUJveCAkIHBvc3RhbENvZGUgJCAKPiAgICAgICAgICAgIHBvc3RhbEFkZHJlc3MgJCBwaHlzaWNh
bERlbGl2ZXJ5T2ZmaWNlTmFtZSAkIHN0ICQgCj4gICAgICAgICAgICBsICQgZGVzY3JpcHRpb24g
KSApCj4KPjMuOSAgb3JnYW5pemF0aW9uYWxQZXJzb24KPgo+ICAgVGhlIG9yZ2FuaXphdGlvbmFs
UGVyc29uIE9iamVjdCBDbGFzcyBpcyB0aGUgYmFzaXMgb2YgYW4gZW50cnkgd2hpY2ggCj4gICBy
ZXByZXNlbnRzIGEgcGVyc29uIGluIHJlbGF0aW9uIHRvIGFuIG9yZ2FuaXphdGlvbi4gIAo+Cj4g
ICAoIDIuNS42LjcgTkFNRSAnb3JnYW5pemF0aW9uYWxQZXJzb24nIAo+ICAgICAgU1VQIHBlcnNv
biAKPiAgICAgIFNUUlVDVFVSQUwKPiAgICAgIE1BWSAoIHRpdGxlICQgeDEyMUFkZHJlc3MgJCBy
ZWdpc3RlcmVkQWRkcmVzcyAkIAo+ICAgICAgICAgICAgZGVzdGluYXRpb25JbmRpY2F0b3IgJCBw
cmVmZXJyZWREZWxpdmVyeU1ldGhvZCAkIAo+ICAgICAgICAgICAgdGVsZXhOdW1iZXIgJCB0ZWxl
dGV4VGVybWluYWxJZGVudGlmaWVyICQgdGVsZXBob25lTnVtYmVyICQgCj4gICAgICAgICAgICBp
bnRlcm5hdGlvbmFsaVNETk51bWJlciAkIGZhY3NpbWlsZVRlbGVwaG9uZU51bWJlciAkIAo+ICAg
ICAgICAgICAgc3RyZWV0ICQgcG9zdE9mZmljZUJveCAkIHBvc3RhbENvZGUgJCBwb3N0YWxBZGRy
ZXNzICQgCj4gICAgICAgICAgICBwaHlzaWNhbERlbGl2ZXJ5T2ZmaWNlTmFtZSAkIG91ICQgc3Qg
JCBsICkgKQo+Cj4KPgo+Cj4zLjEwICBvcmdhbml6YXRpb25hbFJvbGUKPgo+ICAgVGhlIG9yZ2Fu
aXphdGlvbmFsUm9sZSBPYmplY3QgQ2xhc3MgaXMgdGhlIGJhc2lzIG9mIGFuIGVudHJ5IHdoaWNo
IAo+ICAgcmVwcmVzZW50cyBhIGpvYiBvciBmdW5jdGlvbiBvciBwb3NpdGlvbiBpbiBhbiBvcmdh
bml6YXRpb24uCj4KPiAgICggMi41LjYuOCBOQU1FICdvcmdhbml6YXRpb25hbFJvbGUnIAo+ICAg
ICAgU1VQIHRvcCAKPiAgICAgIFNUUlVDVFVSQUwgCj4gICAgICBNVVNUIGNuCj4gICAgICBNQVkg
KCB4MTIxQWRkcmVzcyAkIHJlZ2lzdGVyZWRBZGRyZXNzICQgZGVzdGluYXRpb25JbmRpY2F0b3Ig
JCAKPiAgICAgICAgICAgIHByZWZlcnJlZERlbGl2ZXJ5TWV0aG9kICQgdGVsZXhOdW1iZXIgJCAK
PiAgICAgICAgICAgIHRlbGV0ZXhUZXJtaW5hbElkZW50aWZpZXIgJCB0ZWxlcGhvbmVOdW1iZXIg
JCAKPiAgICAgICAgICAgIGludGVybmF0aW9uYWxpU0ROTnVtYmVyICQgZmFjc2ltaWxlVGVsZXBo
b25lTnVtYmVyICQgCj4gICAgICAgICAgICBzZWVBbHNvICQgcm9sZU9jY3VwYW50ICQgcHJlZmVy
cmVkRGVsaXZlcnlNZXRob2QgJCAKPiAgICAgICAgICAgIHN0cmVldCAkIHBvc3RPZmZpY2VCb3gg
JCBwb3N0YWxDb2RlICQgcG9zdGFsQWRkcmVzcyAkIAo+ICAgICAgICAgICAgcGh5c2ljYWxEZWxp
dmVyeU9mZmljZU5hbWUgJCBvdSAkIHN0ICQgbCAkIGRlc2NyaXB0aW9uICkgKQo+Cj4zLjExICBv
cmdhbml6YXRpb25hbFVuaXQKPgo+ICAgVGhlIG9yZ2FuaXphdGlvbmFsVW5pdCBPYmplY3QgQ2xh
c3MgaXMgdGhlIGJhc2lzIG9mIGFuIGVudHJ5IHdoaWNoIAo+ICAgcmVwcmVzZW50cyBhIHBpZWNl
IG9mIGFuIG9yZ2FuaXphdGlvbi4KPgo+ICAgKCAyLjUuNi41IE5BTUUgJ29yZ2FuaXphdGlvbmFs
VW5pdCcgCj4gICAgICBTVVAgdG9wIAo+ICAgICAgU1RSVUNUVVJBTCAKPiAgICAgIE1VU1Qgb3UK
PiAgICAgIE1BWSAoIGJ1c2luZXNzQ2F0ZWdvcnkgJCBkZXNjcmlwdGlvbiAkIGRlc3RpbmF0aW9u
SW5kaWNhdG9yICQgCj4gICAgICAgICAgICBmYWNzaW1pbGVUZWxlcGhvbmVOdW1iZXIgJCBpbnRl
cm5hdGlvbmFsaVNETk51bWJlciAkIGwgJCAKPiAgICAgICAgICAgIHBoeXNpY2FsRGVsaXZlcnlP
ZmZpY2VOYW1lICQgcG9zdGFsQWRkcmVzcyAkIHBvc3RhbENvZGUgJCAKPiAgICAgICAgICAgIHBv
c3RPZmZpY2VCb3ggJCBwcmVmZXJyZWREZWxpdmVyeU1ldGhvZCAkIAo+ICAgICAgICAgICAgcmVn
aXN0ZXJlZEFkZHJlc3MgJCBzZWFyY2hHdWlkZSAkIHNlZUFsc28gJCBzdCAkIHN0cmVldCAkIAo+
ICAgICAgICAgICAgdGVsZXBob25lTnVtYmVyICQgdGVsZXRleFRlcm1pbmFsSWRlbnRpZmllciAk
IHRlbGV4TnVtYmVyICQgCj4gICAgICAgICAgICB1c2VyUGFzc3dvcmQgJCB4MTIxQWRkcmVzcyAp
ICkKPgo+My4xMiAgcGVyc29uCj4KPiAgIFRoZSBwZXJzb24gT2JqZWN0IENsYXNzIGlzIHRoZSBi
YXNpcyBvZiBhbiBlbnRyeSB3aGljaCByZXByZXNlbnRzIGEgCj4gICBodW1hbiBiZWluZy4KPgo+
ICAgKCAyLjUuNi42IE5BTUUgJ3BlcnNvbicgCj4gICAgICBTVVAgdG9wIAo+ICAgICAgU1RSVUNU
VVJBTCAKPiAgICAgIE1VU1QgKCBzbiAkIAo+ICAgICAgICAgICAgIGNuICkKPiAgICAgIE1BWSAo
IHVzZXJQYXNzd29yZCAkIAo+ICAgICAgICAgICAgdGVsZXBob25lTnVtYmVyICQgCj4gICAgICAg
ICAgICBzZWVBbHNvICQgCj4gICAgICAgICAgICBkZXNjcmlwdGlvbiApICkgCj4KPjMuMTMgIHJl
c2lkZW50aWFsUGVyc29uCj4KPiAgIFRoZSByZXNpZGVudGlhbFBlcnNvbiBPYmplY3QgQ2xhc3Mg
aXMgdGhlIGJhc2lzIG9mIGFuIGVudHJ5IHdoaWNoIAo+ICAgaW5jbHVkZXMgYSBwZXJzb24ncyBy
ZXNpZGVuY2UgaW4gdGhlIHJlcHJlc2VudGF0aW9uIG9mIHRoZSBwZXJzb24uIAo+Cj4gICAoIDIu
NS42LjEwIE5BTUUgJ3Jlc2lkZW50aWFsUGVyc29uJyAKPiAgICAgIFNVUCBwZXJzb24gCj4gICAg
ICBTVFJVQ1RVUkFMIAo+ICAgICAgTVVTVCBsCj4gICAgICBNQVkgKCBidXNpbmVzc0NhdGVnb3J5
ICQgeDEyMUFkZHJlc3MgJCByZWdpc3RlcmVkQWRkcmVzcyAkIAo+ICAgICAgICAgICBkZXN0aW5h
dGlvbkluZGljYXRvciAkIHByZWZlcnJlZERlbGl2ZXJ5TWV0aG9kICQgCj4gICAgICAgICAgIHRl
bGV4TnVtYmVyICQgdGVsZXRleFRlcm1pbmFsSWRlbnRpZmllciAkIHRlbGVwaG9uZU51bWJlciAk
IAo+ICAgICAgICAgICBpbnRlcm5hdGlvbmFsaVNETk51bWJlciAkIGZhY3NpbWlsZVRlbGVwaG9u
ZU51bWJlciAkIAo+ICAgICAgICAgICBwcmVmZXJyZWREZWxpdmVyeU1ldGhvZCAkIHN0cmVldCAk
IHBvc3RPZmZpY2VCb3ggJCAKPiAgICAgICAgICAgcG9zdGFsQ29kZSAkIHBvc3RhbEFkZHJlc3Mg
JCBwaHlzaWNhbERlbGl2ZXJ5T2ZmaWNlTmFtZSAkIAo+ICAgICAgICAgICBzdCAkIGwgKSApCj4K
Pgo+NC4gIElBTkEgQ29uc2lkZXJhdGlvbnMKPgo+ICAgSXQgaXMgcmVxdWVzdGVkIHRoYXQgdGhl
IEludGVybmV0IEFzc2lnbmVkIE51bWJlcnMgQXV0aG9yaXR5IChJQU5BKQo+ICAgdXBkYXRlIHRo
ZSBMREFQIGRlc2NyaXB0b3JzIHJlZ2lzdHJ5IGFzIGluZGljYXRlZCBpbiB0aGUgZm9sbG93aW5n
Cj4gICB0ZW1wbGF0ZToKPgo+ICAgICAgU3ViamVjdDogUmVxdWVzdCBmb3IgTERBUCBEZXNjcmlw
dG9yIFJlZ2lzdHJhdGlvbiBVcGRhdGUKPiAgICAgIERlc2NyaXB0b3IgKHNob3J0IG5hbWUpOiBz
ZWUgY29tbWVudAo+ICAgICAgT2JqZWN0IElkZW50aWZpZXI6IHNlZSBjb21tZW50Cj4gICAgICBQ
ZXJzb24gJiBlbWFpbCBhZGRyZXNzIHRvIGNvbnRhY3QgZm9yIGZ1cnRoZXIgaW5mb3JtYXRpb246
Cj4gICAgICAgICAgS2F0aHkgRGFsbHkgPGtkYWxseUBtaXRyZS5vcmc+Cj4gICAgICBVc2FnZTog
KEEgPSBBdHRyaWJ1dGUgVHlwZSwgTyA9IE9iamVjdCBDbGFzcykgc2VlIGNvbW1lbnQKPiAgICAg
IFNwZWNpZmljYXRpb246IFJGQyBYWFhYCj4gICAgICBBdXRob3IvQ2hhbmdlIENvbnRyb2xsZXI6
IElFU0cKPgo+ICAgICAgQ29tbWVudHM6Cj4gICAgICAgICBUaGUgZm9sbG93aW5nIGRlc2NyaXB0
b3JzIChzaG9ydCBuYW1lcykgc2hvdWxkIGJlIHVwZGF0ZWQgdG8gCj4gICAgICAgICByZWZlciB0
byBSRkMgWFhYWC4KPgo+ICAgICAgICBOQU1FICAgICAgICAgICAgICAgICAgICAgICAgIFR5cGUg
T0lECj4gICAgICAgIC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSAgICAgLS0tLSAtLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tCj4gICAgICAgICBhcHBsaWNhdGlvblByb2Nlc3MgICAgICAgICAg
IE8gICAgMi41LjYuMTEKPiAgICAgICAgIGJ1c2luZXNzQ2F0ZWdvcnkgICAgICAgICAgICAgQSAg
ICAyLjUuNC4xNQo+ICAgICAgICAgYyAgICAgICAgICAgICAgICAgICAgICAgICAgICBBICAgIDIu
NS40LjYKPiAgICAgICAgIGNuICAgICAgICAgICAgICAgICAgICAgICAgICAgQSAgICAyLjUuNC4z
Cj4gICAgICAgICBjb3VudHJ5ICAgICAgICAgICAgICAgICAgICAgIE8gICAgMi41LjYuMgo+ICAg
ICAgICAgZGMgICAgICAgICAgICAgICAgICAgICAgICAgICBBICAgIDAuOS4yMzQyLjE5MjAwMzAw
LjEwMC4xLjI1Cj4gICAgICAgICBkZXNjcmlwdGlvbiAgICAgICAgICAgICAgICAgIEEgICAgMi41
LjQuMTMKPiAgICAgICAgIGRlc3RpbmF0aW9uSW5kaWNhdG9yICAgICAgICAgQSAgICAyLjUuNC4y
Nwo+ICAgICAgICAgZGV2aWNlICAgICAgICAgICAgICAgICAgICAgICBPICAgIDIuNS42LjE0Cj4g
ICAgICAgICBkaXN0aW5ndWlzaGVkTmFtZSAgICAgICAgICAgIEEgICAgMi41LjQuNDkKPiAgICAg
ICAgIGRuUXVhbGlmaWVyICAgICAgICAgICAgICAgICAgQSAgICAyLjUuNC40Ngo+ICAgICAgICAg
ZG9tYWluICAgICAgICAgICAgICAgICAgICAgICBPICAgIDAuOS4yMzQyLjE5MjAwMzAwLjEwMC40
LjEzCj4gICAgICAgICBlbmhhbmNlZFNlYXJjaEd1aWRlICAgICAgICAgIEEgICAgMi41LjQuNDcK
PiAgICAgICAgIGZhY3NpbWlsZVRlbGVwaG9uZU51bWJlciAgICAgQSAgICAyLjUuNC4yMwo+ICAg
ICAgICAgZ2VuZXJhdGlvblF1YWxpZmllciAgICAgICAgICBBICAgIDIuNS40LjQ0Cj4gICAgICAg
ICBnaXZlbk5hbWUgICAgICAgICAgICAgICAgICAgIEEgICAgMi41LjQuNDIKPiAgICAgICAgIGdy
b3VwT2ZOYW1lcyAgICAgICAgICAgICAgICAgTyAgICAyLjUuNi45Cj4gICAgICAgICBncm91cE9m
VW5pcXVlTmFtZXMgICAgICAgICAgIE8gICAgMi41LjYuMTcKPiAgICAgICAgIGhvdXNlSWRlbnRp
ZmllciAgICAgICAgICAgICAgQSAgICAyLjUuNC41MQo+ICAgICAgICAgaW5pdGlhbHMgICAgICAg
ICAgICAgICAgICAgICBBICAgIDIuNS40LjQzCj4gICAgICAgICBpbnRlcm5hdGlvbmFsSVNETk51
bWJlciAgICAgIEEgICAgMi41LjQuMjUKPiAgICAgICAgIGwgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgQSAgICAyLjUuNC43Cj4gICAgICAgICBsb2NhbGl0eSAgICAgICAgICAgICAgICAgICAg
IE8gICAgMi41LjYuMwo+ICAgICAgICAgbWVtYmVyICAgICAgICAgICAgICAgICAgICAgICBBICAg
IDIuNS40LjMxCj4gICAgICAgICBuYW1lICAgICAgICAgICAgICAgICAgICAgICAgIEEgICAgMi41
LjQuNDEKPiAgICAgICAgIG8gICAgICAgICAgICAgICAgICAgICAgICAgICAgQSAgICAyLjUuNC4x
MAo+ICAgICAgICAgb3JnYW5pemF0aW9uICAgICAgICAgICAgICAgICBPICAgIDIuNS42LjQKPiAg
ICAgICAgIG9yZ2FuaXphdGlvbmFsUGVyc29uICAgICAgICAgTyAgICAyLjUuNi43Cj4gICAgICAg
ICBvcmdhbml6YXRpb25hbFJvbGUgICAgICAgICAgIE8gICAgMi41LjYuOAo+ICAgICAgICAgb3Jn
YW5pemF0aW9uYWxVbml0ICAgICAgICAgICBPICAgIDIuNS42LjUKPiAgICAgICAgIG91ICAgICAg
ICAgICAgICAgICAgICAgICAgICAgQSAgICAyLjUuNC4xMQo+ICAgICAgICAgb3duZXIgICAgICAg
ICAgICAgICAgICAgICAgICBBICAgIDIuNS40LjMyCj4gICAgICAgICBwZXJzb24gICAgICAgICAg
ICAgICAgICAgICAgIE8gICAgMi41LjYuNgo+ICAgICAgICAgcGh5c2ljYWxEZWxpdmVyeU9mZmlj
ZU5hbWUgICBBICAgIDIuNS40LjE5Cj4gICAgICAgICBwb3N0YWxBZGRyZXNzICAgICAgICAgICAg
ICAgIEEgICAgMi41LjQuMTYKPiAgICAgICAgIHBvc3RhbENvZGUgICAgICAgICAgICAgICAgICAg
QSAgICAyLjUuNC4xNwo+ICAgICAgICAgcG9zdE9mZmljZUJveCAgICAgICAgICAgICAgICBBICAg
IDIuNS40LjE4Cj4gICAgICAgICBwcmVmZXJyZWREZWxpdmVyeU1ldGhvZCAgICAgIEEgICAgMi41
LjQuMjgKPiAgICAgICAgIHJlZ2lzdGVyZWRBZGRyZXNzICAgICAgICAgICAgQSAgICAyLjUuNC4y
Ngo+ICAgICAgICAgcmVzaWRlbnRpYWxQZXJzb24gICAgICAgICAgICBPICAgIDIuNS42LjEwCj4g
ICAgICAgICByb2xlT2NjdXBhbnQgICAgICAgICAgICAgICAgIEEgICAgMi41LjQuMzMKPiAgICAg
ICAgIHNlYXJjaEd1aWRlICAgICAgICAgICAgICAgICAgQSAgICAyLjUuNC4xNAo+ICAgICAgICAg
c2VlQWxzbyAgICAgICAgICAgICAgICAgICAgICBBICAgIDIuNS40LjM0Cj4gICAgICAgICBzZXJp
YWxOdW1iZXIgICAgICAgICAgICAgICAgIEEgICAgMi41LjQuNQo+ICAgICAgICAgc24gICAgICAg
ICAgICAgICAgICAgICAgICAgICBBICAgIDIuNS40LjQKPiAgICAgICAgIHN0ICAgICAgICAgICAg
ICAgICAgICAgICAgICAgQSAgICAyLjUuNC44Cj4gICAgICAgICBzdHJlZXQgICAgICAgICAgICAg
ICAgICAgICAgIEEgICAgMi41LjQuOQo+ICAgICAgICAgdGVsZXBob25lTnVtYmVyICAgICAgICAg
ICAgICBBICAgIDIuNS40LjIwCj4gICAgICAgICB0ZWxldGV4VGVybWluYWxJZGVudGlmaWVyICAg
IEEgICAgMi41LjQuMjIKPiAgICAgICAgIHRlbGV4TnVtYmVyICAgICAgICAgICAgICAgICAgQSAg
ICAyLjUuNC4yMQo+ICAgICAgICAgdGl0bGUgICAgICAgICAgICAgICAgICAgICAgICBBICAgIDIu
NS40LjEyCj4gICAgICAgICB1bmlxdWVNZW1iZXIgICAgICAgICAgICAgICAgIEEgICAgMi41LjQu
NTAKPiAgICAgICAgIHVzZXJQYXNzd29yZCAgICAgICAgICAgICAgICAgQSAgICAyLjUuNC4zNQo+
ICAgICAgICAgeDEyMUFkZHJlc3MgICAgICAgICAgICAgICAgICBBICAgIDIuNS40LjI0Cj4gICAg
ICAgICB4NTAwVW5pcXVlSWRlbnRpZmllciAgICAgICAgIEEgICAgMi41LjQuNDUKPgo+Cj41LiAg
U2VjdXJpdHkgQ29uc2lkZXJhdGlvbnMKPgo+ICAgQXR0cmlidXRlcyBvZiBkaXJlY3RvcnkgZW50
cmllcyBhcmUgdXNlZCB0byBwcm92aWRlIGRlc2NyaXB0aXZlIAo+ICAgaW5mb3JtYXRpb24gYWJv
dXQgdGhlIHJlYWwtd29ybGQgb2JqZWN0cyB0aGV5IHJlcHJlc2VudCwgd2hpY2ggY2FuIGJlCj4g
ICBwZW9wbGUsIG9yZ2FuaXphdGlvbnMgb3IgZGV2aWNlcy4gIE1vc3QgY291bnRyaWVzIGhhdmUg
cHJpdmFjeSBsYXdzIAo+ICAgcmVnYXJkaW5nIHRoZSBwdWJsaWNhdGlvbiBvZiBpbmZvcm1hdGlv
biBhYm91dCBwZW9wbGUuCj4KPiAgIFRyYW5zZmVyIG9mIGNsZWFydGV4dCBwYXNzd29yZHMgaXMg
c3Ryb25nbHkgZGlzY291cmFnZWQgd2hlcmUgdGhlIAo+ICAgdW5kZXJseWluZyB0cmFuc3BvcnQg
c2VydmljZSBjYW5ub3QgZ3VhcmFudGVlIGNvbmZpZGVudGlhbGl0eSBhbmQgbWF5Cj4gICByZXN1
bHQgaW4gZGlzY2xvc3VyZSBvZiB0aGUgcGFzc3dvcmQgdG8gdW5hdXRob3JpemVkIHBhcnRpZXMu
Cj4KPiAgIEl0IGlzIHJlcXVpcmVkIHRoYXQgc3Ryb25nIGF1dGhlbnRpY2F0aW9uIGJlIHBlcmZv
cm1lZCBpbiBvcmRlciB0byAKPiAgIG1vZGlmeSBkaXJlY3RvcnkgZW50cmllcyB1c2luZyBMREFQ
LgoKQWRkOiAgVXNlIG9mIGludGVncml0eSBwcm90ZWN0aW9uIGlzIGVuY291cmFnZWQgdG8gcHJl
dmVudCBzZXNzaW9uCgloaWphY2tpbmcuCgo+Cj4KPjYuICBBY2tub3dsZWRnZW1lbnRzCj4KPiAg
IFRoZSBkZWZpbml0aW9ucywgb24gd2hpY2ggdGhpcyBkb2N1bWVudCBpcyBiYXNlZCwgaGF2ZSBi
ZWVuIGRldmVsb3BlZAo+ICAgYnkgY29tbWl0dGVlcyBmb3IgdGVsZWNvbW11bmljYXRpb25zIGFu
ZCBpbnRlcm5hdGlvbmFsIHN0YW5kYXJkcy4gIAo+ICAgTm8gbmV3IGF0dHJpYnV0ZSBkZWZpbml0
aW9ucyBoYXZlIGJlZW4gYWRkZWQuICAKClNpbmNlIHdlJ3ZlIGFkZGVkICdkYycgYW5kICdkb21h
aW4nLCBJIGRvbid0IGJlbGlldmUgdGhpcyBpcyBwcmVjaXNlbHkKdHJ1ZSBhbnkgbW9yZS4gICAg
SSB3b3VsZCBhdHRyaWJ1dGUgJ2RjJyBhbmQgJ2RvbWFpbicgdG8gdGhlIGF1dGhvcnMKUkZDIDEy
NzQgYW5kIHRoZSBMREFQLXNwZWNpZmljIGRlZmluaXRpb24gdG8gdGhlIGF1dGhvcnMgb2YgUkZD
IDIyNDcuCgo+ICAgVGhpcyBkb2N1bWVudCBpcyBhbiB1cGRhdGUgb2YgUkZDIDIyNTYgYnkgTWFy
ayBXYWhsLiAgUkZDIDIyNTYgd2FzIGEKPiAgIHByb2R1Y3Qgb2YgdGhlIElFVEYgQVNJRCBXb3Jr
aW5nIEdyb3VwLgo+Cj4gICBUaGlzIGRvY3VtZW50IGlzIGJhc2VkIHVwb24gaW5wdXQgb2YgdGhl
IElFVEYgTERBUEJJUyB3b3JraW5nIGdyb3VwLgo+ICAgVGhlIGF1dGhvciB3aXNoZXMgdG8gdGhh
bmsgUy4gTGVnZyBhbmQgSy4gWmVpbGVuZ2EgZm9yIHRoZWlyIAo+ICAgc2lnbmlmaWNhbnQgY29u
dHJpYnV0aW9uIHRvIHRoaXMgdXBkYXRlLgo+Cj4KPjcuICBSZWZlcmVuY2VzCj4KPjcuMSAgTm9y
bWF0aXZlCj4KPiAgIFtFLjEyM10gIE5vdGF0aW9uIGZvciBuYXRpb25hbCBhbmQgaW50ZXJuYXRp
b25hbCB0ZWxlcGhvbmUgbnVtYmVycywgCj4gICAgICAgICAgICBJVFUtVCBSZWNvbW1lbmRhdGlv
biBFLjEyMywgMTk4OAo+Cj4gICBbRS4xNjRdICBUaGUgaW50ZXJuYXRpb25hbCBwdWJsaWMgdGVs
ZWNvbW11bmljYXRpb24gbnVtYmVyaW5nIHBsYW4sIAo+ICAgICAgICAgICAgSVRVLVQgUmVjb21t
ZW5kYXRpb24gRS4xNjQsIDE5OTcKPgo+ICAgW0lTTzMxNjZdICBJU08gMzE2NiwgIkNvZGVzIGZv
ciB0aGUgcmVwcmVzZW50YXRpb24gb2YgbmFtZXMgb2YgCj4gICAgICAgICAgICAgIGNvdW50cmll
cyIuCj4KPiAgIFtMREFQLVBLSV0gIENoYWR3aWNrLCBELiBXLiwgTGVnZyBTLiwgIkxEQVAgU2No
ZW1hIGFuZCBTeW50YXhlcyBmb3IgCj4gICAgICAgICAgICAgICBQS0lzIiwgZHJhZnQtaWV0Zi1w
a2l4LWxkYXAtcGtpLXNjaGVtYS14eCAoYSB3b3JrIGluIAo+ICAgICAgICAgICAgICAgcHJvZ3Jl
c3MpCgpJbmZvcm1hdGl2ZS4KCj4gICBbTW9kZWxzXSAgSy4gWmVpbGVuZ2EsICJMREFQOiBUaGUg
TW9kZWxzIiwgZHJhZnQtaWV0Zi1sZGFwYmlzLQo+ICAgICAgICAgICAgIG1vZGVscy14eCAoYSB3
b3JrIGluIHByb2dyZXNzKSAKPgo+ICAgW1JGQzIxMTldICBCcmFkbmVyLCBTLiwgIktleSB3b3Jk
cyBmb3IgdXNlIGluIFJGQ3MgdG8gSW5kaWNhdGUgCj4gICAgICAgICAgICAgIFJlcXVpcmVtZW50
IExldmVscyIsIFJGQyAyMTE5LCBNYXJjaCAxOTk3Cj4KPiAgIFtSRkMzMzc3XSAgSG9kZ2VzLCBK
LiwgTW9yZ2FuLCBSLiwgIkxpZ2h0d2VpZ2h0IERpcmVjdG9yeSBBY2Nlc3MgCj4gICAgICAgICAg
ICAgIFByb3RvY29sICh2Myk6ICBUZWNobmljYWwgU3BlY2lmaWNhdGlvbiIsIFJGQyAzMzc3LCAK
PiAgICAgICAgICAgICAgU2VwdGVtYmVyIDIwMDIKCkluZm9ybWF0aXZlLgoKPi4uLltST0FETUFQ
XSAgWmVpbGVuZ2EsIEsuLCAiTERBUDogIFRlY2huaWNhbCBTcGVjaWZpY2F0aW9uIFJvYWQgTWFw
IiwgCj4gICAgICAgICAgICAgIGRyYWZ0LWlldGYtbGRhcGJpcy1yb2FkbWFwLXh4IChhIHdvcmsg
aW4gcHJvZ3Jlc3MpCj4KPiAgIFtTeW50YXhlc10gIFMuIExlZ2cgKGVkaXRvciksICJMREFQOiBT
eW50YXhlcyIsCj4gICAgICAgICAgICAgICBkcmFmdC1pZXRmLWxkYXBiaXMtc3ludGF4ZXMteHgg
KGEgd29yayBpbiBwcm9ncmVzcykKPgo+ICAgW1guMTIxXSAgSW50ZXJuYXRpb25hbCBudW1iZXJp
bmcgcGxhbiBmb3IgcHVibGljIGRhdGEgbmV0d29ya3MsIAo+ICAgICAgICAgICAgSVRVLVQgUmVj
b21tZW5kYXRpb24gWC4xMjEsIDE5OTYKPgo+ICAgW1guNTA5XSAgVGhlIERpcmVjdG9yeTogIEF1
dGhlbnRpY2F0aW9uIEZyYW1ld29yaywgSVRVLVQgCj4gICAgICAgICAgICBSZWNvbW1lbmRhdGlv
biBYLjUwOSwgMTk5Mwo+Cj4gICBbWC41MjBdICBUaGUgRGlyZWN0b3J5OiBTZWxlY3RlZCBBdHRy
aWJ1dGUgVHlwZXMsIElUVS1UIAo+ICAgICAgICAgICAgUmVjb21tZW5kYXRpb24gWC41MjAsIDE5
OTMKPgo+ICAgW1guNTIxXSAgVGhlIERpcmVjdG9yeTogU2VsZWN0ZWQgT2JqZWN0IENsYXNzZXMu
ICBJVFUtVCAKPiAgICAgICAgICAgIFJlY29tbWVuZGF0aW9uIFguNTIxLCAxOTkzCj4KPjcuMiAg
SW5mb3JtYXRpdmUKPgo+ICAgW1JGQzIyNDddICBLaWxsZSwgUy4sIFdhaGwsIE0uLCBHcmltc3Rh
ZCwgQS4sIEh1YmVyLCBSLiwgYW5kIAo+ICAgICAgU2F0YWx1cmksIFMuLCAiVXNpbmcgRG9tYWlu
cyBpbiBMREFQL1guNTAwIERpc3Rpbmd1aXNoZWQgTmFtZXMiLCAKPiAgICAgIFJGQyAyMjQ3LCBK
YW51YXJ5IDE5OTgKPgo+Cj4KPjguICBBdXRob3IncyBBZGRyZXNzCj4KPiAgIEthdGh5IERhbGx5
Cj4gICBUaGUgTUlUUkUgQ29ycC4KPiAgIDE1NzUgQ29sc2hpcmUgRHIuLCBIMzAwCj4gICBNY0xl
YW4gVkEgMjIxMDIKPiAgIFVTQQo+ICAgCj4gICBQaG9uZTogICsxIDcwMyA4ODMgNjA1OAo+ICAg
RW1haWw6ICBrZGFsbHlAbWl0cmUub3JnCj4KPgo+Cj4gICAgICAgICAgICAgICAgICAgICAgICAg
IEFwcGVuZGl4IEEgIENoYW5nZXMgUkZDIDIyNTYKPgo+ICAgVGhpcyBhcHBlbmRpeCBsaXN0cyB0
aGUgY2hhbmdlcyB0aGF0IGhhdmUgYmVlbiBtYWRlIGZyb20gUkZDIDIyNTYgdG8gCj4gICB0aGlz
IEktRC4gIAo+Cj4gICAgICAxLiAgUmV2aXNlZCB0aGUgU3RhdHVzIG9mIHRoaXMgTWVtby4KCkNh
biBiZSBkcm9wcGVkIChwdXJlbHkgZWRpdG9yaWFsKS4KCj4gICAgICAyLiAgUmVtb3ZlZCB0aGUg
SUVTRyBOb3RlLgo+Cj4gICAgICAzLiAgRGVwZW5kZW5jaWVzIG9uIFJGQyAxMjc0IGhhdmUgYmVl
biBlbGltaW5hdGVkLgo+Cj4gICAgICA0LiAgQWRkZWQgYSBTZWN1cml0eSBDb25zaWRlcmF0aW9u
cyBzZWN0aW9uLCByZXF1aXJpbmcgc3Ryb25nIAo+ICAgICAgICAgIGF1dGhlbnRpY2F0aW9uIGlu
IG9yZGVyIHRvIG1vZGlmeSBkaXJlY3RvcnkgZW50cmllcy4KPgo+ICAgICAgNS4gIERlbGV0ZWQg
dGhlIGNvbmZvcm1hbmNlIHJlcXVpcmVtZW50IGZvciBzdWJzY2hlbWEgb2JqZWN0IAo+ICAgICAg
ICAgIGNsYXNzZXMgaW4gZmF2b3Igb2YgYSBzdGF0ZW1lbnQgaW4gW1N5bnRheGVzXS4KPgo+ICAg
ICAgNi4gIEFkZGVkIGEgVGFibGUgb2YgQ29udGVudHMuCgpFZGl0b3JpYWwuCgo+ICAgICAgNy4g
IEFkZGVkIGV4cGxhbmF0aW9ucyB0byBtYW55IGF0dHJpYnV0ZXMuCj4KPiAgICAgIDguICBSZW1v
dmVkIFNlY3Rpb24gNCwgU3ludGF4ZXMsIGFuZCBTZWN0aW9uIDYsIE1hdGNoaW5nIFJ1bGVzLCAK
PiAgICAgICAgICAobW92ZWQgdG8gW1N5bnRheGVzXSkuCj4KPiAgICAgIDkuICBSZW9yZGVyZWQg
U2VjdGlvbiAzLCBBdHRyaWJ1dGVzLCBhbmQgU2VjdGlvbiA0LCBPYmplY3QgCj4gICAgICAgICAg
Q2xhc3NlcywgYWxwaGFiZXRpY2FsbHkuCgpTZWUgbm90ZSBiZWxvdy4KCj4gICAgICAxMC4gQWRk
ZWQgYW4gZXhwbGFuYXRpb24gZm9yIGVhY2ggb2JqZWN0IGNsYXNzLgoKQ2FuIGJlIGNvbWJpbmVk
IHdpdGggaXRlbSA3LgoKPgo+ICAgICAgMTEuIFJlbW92ZWQgdGhlIGNlcnRpZmljYXRlLXJlbGF0
ZWQgQXR0cmlidXRlIFR5cGVzOiAgCj4gICAgICAgICAgICAgYXV0aG9yaXR5UmV2b2NhdGlvbkxp
c3QsIAo+ICAgICAgICAgICAgIGNBQ2VydGlmaWNhdGUsIAo+ICAgICAgICAgICAgIGNlcnRpZmlj
YXRlUmV2b2NhdGlvbkxpc3QsIAo+ICAgICAgICAgICAgIGNyb3NzQ2VydGlmaWNhdGVQYWlyLCAK
PiAgICAgICAgICAgICBkZWx0YVJldm9jYXRpb25MaXN0LCAKPiAgICAgICAgICAgICBzdXBwb3J0
ZWRBbGdvcml0aG1zLCBhbmQgCj4gICAgICAgICAgICAgdXNlckNlcnRpZmljYXRlLgo+Cj4gICAg
ICAgICAgUmVtb3ZlZCB0aGUgY2VydGlmaWNhdGUtcmVsYXRlZCBPYmplY3QgQ2xhc3NlczogIAo+
ICAgICAgICAgICAgIGNlcnRpZmljYXRpb25BdXRob3JpdHksCj4gICAgICAgICAgICAgY2VydGlm
aWNhdGlvbkF1dGhvcml0eS1WMiwKPiAgICAgICAgICAgICBjUkxEaXN0cmlidXRpb25Qb2ludCwK
PiAgICAgICAgICAgICBzdHJvbmdBdXRoZW50aWNhdGlvblVzZXIsIGFuZAo+ICAgICAgICAgICAg
IHVzZXJTZWN1cml0eUluZm9ybWF0aW9uCj4KPiAgICAgICAgICBOb3RlZCB0aGF0IHRoZXkgYXJl
IGNvdmVyZWQgaW4gUEtJWCBXRyBkb2N1bWVudHMuCgpJIHN1Z2dlc3QgdGhlIGxhc3Qgc2VudGVu
Y2UgYmUgcmVwbGFjZWQgd2l0aDoKCQkgICBMREFQIFBLSSBpcyBub3cgZGlzY3Vzc2VkIGluIFtM
REFQLVBLSV0uCj4KPiAgICAgIDEyLiBSZW1vdmVkIHRoZSBkbWROYW1lIEF0dHJpYnV0ZSBUeXBl
IGFuZCBkbWQgT2JqZWN0IENsYXNzIAo+ICAgICAgICAgIGJlY2F1c2UgdGhleSBhcmUgbm90IGlu
IHRoZSB2ZXJzaW9uIG9mIFguNTAwIHdoaWNoIAo+ICAgICAgICAgIGlzIHJlZmVyZW5jZWQuCgpB
cyBub25lIG9mIHRoZSBpdGVtcyBoYXZlICJiZWNhdXNlIiBzdGF0ZW1lbnRzLCBJIHN1Z2dlc3Qg
dGhpcwpiZSB0cmltbWVkIGFuZCAxMiBiZSBjb21iaW5lZCB3aXRoIDE3LiAgQWx0ZXJuYXRpdmUs
IGFkZCAqdGVyc2UqCnNvbWUgb2YgdGhlICJiZWNhdXNlIiBzdGF0ZW1lbnRzIGl0ZW1zICgxNiwg
MTcsIDE4KS4KCj4uLi4uLi4xMy4gRGVsZXRlZCB0aGUgJ2FsaWFzZWRPYmplY3ROYW1lJyBhbmQg
J29iamVjdENsYXNzJyBhdHRyaWJ1dGUgCj4gICAgICAgICAgdHlwZSBkZWZpbml0aW9ucy4gIFRo
ZXkgYXJlIGluY2x1ZGVkIGluIFtNb2RlbHNdLgoKIF5eXl5eXiA/Cj4KPiAgICAgIDE0LiBEZWxl
dGVkIHRoZSAnYWxpYXMnIGFuZCAndG9wJyBvYmplY3QgY2xhc3MgZGVmaW5pdGlvbnMuICBUaGV5
IAo+ICAgICAgICAgIGFyZSBpbmNsdWRlZCBpbiBbTW9kZWxzXS4KCkl0ZW1zIDEzIGFuZCAxNCBj
YW4gYmUgY29tYmluZWQuCgo+ICAgICAgMTUuIFJlcGxhY2VkIHRoZSBkb2N1bWVudCB0aXRsZS4K
ClN1Z2dlc3QgdGhpcyBiZSBtYWRlIGl0ZW0gMS4KCj4gICAgICAxNi4gQWRkZWQgdGhlICdkYycg
YXR0cmlidXRlIGFuZCB0aGUgJ2RvbWFpbicgb2JqZWN0IGNsYXNzIGZyb20gCj4gICAgICAgICAg
UkZDIDIyNDcuCj4KPiAgICAgIDE3LiBEZWxldGVkIHRoZSAna25vd2xlZGdlSW5mb3JtYXRpb24n
LCAncHJlc2VudGF0aW9uQWRkcmVzcycsIAo+ICAgICAgICAgICdwcm90b2NvbEluZm9ybWF0aW9u
JywgYW5kICdzdXBwb3J0ZWRBcHBsaWNhdGlvbkNvbnRleHQnIAo+ICAgICAgICAgIGF0dHJpYnV0
ZXMuCj4KPiAgICAgIDE4LiBEZWxldGVkIHRoZSAnYXBwbGljYXRpb25FbnRpdHknIGFuZCAnZFNB
JyBvYmplY3QgY2xhc3Nlcy4KCkNhbiBiZSBjb21iaW5lZCB3aXRoIDE3LgoKPiAgICAgIDE5LiBB
ZGRlZCBhbiBJQU5BIENvbnNpZGVyYXRpb25zIHNlY3Rpb24uCgpTdWdnZXN0IGFkZGluZwoJMjAu
IE51bWVyb3VzIGVkaXRpdG9yaWFsIGNoYW5nZXMuCgphbmQgdGhlbiBkcm9wcGluZyA2IGFuZCA5
LgoK
--=====================_-1898691624==_--



From owner-ietf-ldapbis@OpenLDAP.org  Wed May 21 15:23: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 PAA04620
	for <ldapbis-archive@lists.ietf.org>; Wed, 21 May 2003 15:23:01 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4LJLSEl064433;
	Wed, 21 May 2003 19:21:31 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 h4LJK8cN064400;
	Wed, 21 May 2003 19:20:08 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 21 May 2003 19:20:08 +0000
Received: from pat.uio.no (pat.uio.no [129.240.130.16])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4LJK6Eh064389
	for <ietf-ldapbis@openldap.org>; Wed, 21 May 2003 19:20:07 GMT
	(envelope-from hbf@bombur.uio.no)
Received: from mail-mx1.uio.no ([129.240.10.29])
	by pat.uio.no with esmtp (Exim 2.12 #7)
	id 19IZ87-0006RR-00; Wed, 21 May 2003 21:20:03 +0200
Received: from [129.240.201.2] (helo=goggins.uio.no)
	by mail-mx1.uio.no with esmtp (Exim 4.14)
	id 19IZ84-00020R-Qg; Wed, 21 May 2003 21:20:00 +0200
Received: from bombur.uio.no ([129.240.186.42])
	by goggins.uio.no with esmtp (Exim 2.12 #7)
	id 19IZ84-0002A6-00; Wed, 21 May 2003 21:20:00 +0200
Received: from hbf by bombur.uio.no with local (Exim 2.12 #7)
	id 19IZ82-0005wW-00; Wed, 21 May 2003 21:19:58 +0200
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Message-Id: <HBF.20030521ssz6@bombur.uio.no>
To: steven.legg@adacel.com.au
Cc: ietf-ldapbis@OpenLDAP.org
Subject: Re: Generalized Time/UTC Time need leap seconds
In-Reply-To: <HBF.20030521ddj@bombur.uio.no>
References: <HBF.20030110genh@bombur.uio.no>
	<004a01c2ba94$9d780590$a518200a@osmium.mtwav.adacel.com.au>
	<HBF.20030521ddj@bombur.uio.no>
X-Mailer: VM 6.37 under Emacs 19.34.1
Date: Wed, 21 May 2003 21:19:58 +0200
X-MailScanner-Information: Please contact postmaster@uio.no for more information
X-UiO-MailScanner: Found to be clean
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 wrote:
>Steven Legg writes:
> 
>> The UTCTime type in X.680 doesn't allow for leap seconds (60 seconds
>> is an illegal value). I still have to check whether GeneralizedTime
>> allows it.
> 
> X.680 (07/2002) in
> <http://www.itu.int/ITU-T/studygroups/com17/languages/> defers to
> ISO 8601,

For GeneralizedTime, I mean.  X.680 UTCTime does not allow leap seconds.

-- 
Hallvard


From owner-ietf-ldapbis@OpenLDAP.org  Wed May 21 16:16:39 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 QAA07323
	for <ldapbis-archive@lists.ietf.org>; Wed, 21 May 2003 16:16:38 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4LK3TF7067220;
	Wed, 21 May 2003 20:13:55 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 h4LJxhfR066883;
	Wed, 21 May 2003 19:59:43 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 21 May 2003 19:59:43 +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 h4LJxfEh066871
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 21 May 2003 19:59:41 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 h4LJxdc6061400;
	Wed, 21 May 2003 19:59:39 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030521125645.029207d8@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Wed, 21 May 2003 12:56:53 -0700
To: "Vithalprasad Gaitonde" <gvithalprasad@novell.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: What Does De-Reference Mean?
Cc: ietf-ldapbis@OpenLDAP.org
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 05:33 AM 5/20/2003, you wrote:
>Kurt,
>Going by the same argument,  the rest of the search criteria e.g. the
>base dn and scope of the search should also be applied after the alias
>has been derferenced to the actual entry

The base DN is "finding" criteria while the scope and filter
are "searching" criteria, so my argument does not apply to
the base DN but does apply to scope.

I couldn't parse your example, so I won't try to comment as
to how my clarification applies to it.

Kurt


>So in the example below,
>
>                  ou=deptB                                             
>                     ou=deptA
>                        |                                              
>                                  |
>             alias_teamA - - - - - - - - - - - - - - - - - - - - - - -
>- -  - - - >ou= teamA
>                                                                       
>                                  |
>                                                                       
>                             ou= DT                                     
>                                                             
>                                                                       
>                                  |
>                                                                       
>                             Computer object (objectClass=computer)
>                                                                       
>                                                                        
> 
>       Search Operation:
>       set search base  = deptB               
>       set search scope = subtree search 
>       set deref aliases  = always
>       search for objects of objectClass=computer
>
>Computer object should not be returned as it does not qualify the scope
>criteria for ou=deptb as the base.
>Correct ?
>
>Prasad
>
>>>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 3/28/2003 5:12:53 AM >>>
>It should be clear that each and every entry returned in
>response to a search request did match the search filter.  That
>is, if the filter is (CN=foo) than each entry returned has "foo"
>as a (not necessarily returned) value of an attribute whose
>type is CN or a subtype of CN.
>
>When dereferencing during searching (by derefInSearching or
>derefAlways), the filter should be matched against the entry which
>the alias refers to, not the alias itself.
>
>If the client asks for all alias objects, e.g, (objectClass=alias)
>with dereferencing during finding enabled, then no entries should
>be returned.  Likewise, when requesting (objectClass=*) with
>dereferencing during finding enabled, none of entries returned
>should belong to the alias objectClass.
>
>So, to answer your specific question, it is not relevant to
>the matching what values of CN the 'alias' has. The values
>of the aliased entry are, however, quite relevant.
>
>Kurt
>
> 
>At 11:22 AM 3/26/2003, Chris Harding wrote:
>>Hi -
>>
>>The interpretation of the LDAP RFCs as regards dereferencing has
>become an issue for the new certification program that The Open Group
>plans to launch for LDAP servers. We have discussed it in the Directory
>Interoperability Forum, and agreed that we should ask the experts in the
>ldapbis group. Accordingly, I would like to ask your help in clarifying
>this issue.
>>
>>Here's the issue. The requirement in the specification is:
>>
>>       When a server receives a search request with the derefAliases
>field
>>       set to derefInSearching then it will dereference aliases in
>subordinates
>>       of the base object in searching.
>>
>>We have a test suite for use in the certification program. The suite
>includes a test of this requirement (which is in fact derived from a
>test in BLITS). The test data includes two entries: Jonathan Adams and
>Jonny Adams. The Jonny Adams entry is an alias for Jonathan Adams.
>>
>>The test should check that Jonny Adams is de-referenced and Jonathan
>Adams is returned. The question is, should the test search for Jonny or
>for Jonathan.
>>
>>RFC 2251 does not explain dereferencing but defers to X.501.
>Unfortunately, X.501 does not seem to explain it very well. My personal
>interpretation after reading it is that, whenever a server encounters an
>alias entry in the course of a search and dereferencing has been
>requested, the server should dereference the alias and carry on
>searching from the entry that the alias points to. Under this
>interpretation, a search for Jonny should return the same result as a
>search for Jonathan - the Jonathan Adams entry.
>>
>>I don't claim to be an expert on the interpretation of the
>specifications - but I hope that experts in the IETF community can shed
>light on this!
>>
>>Please send your comments to the ldapbis list. I will report the
>consensus (assuming that one is reached) to the DIF.
>>
>>Regards,
>>
>>Chris
>>+++++
>>
>>========================================================================
>>           Dr. Christopher J. Harding
>>  T H E    Executive Director for the Directory Interoperability
>Forum
>> O P E N   Apex Plaza, Forbury Road, Reading RG1 1AX, UK
>>G R O U P  Mailto:c.harding@opengroup.org Phone: +44 118 902 3018
>>           WWW: http://www.opengroup.org Mobile: +44 774 063 1520
>>========================================================================
>>
>>            The Open Group's Consortia Services - Association
>Management For I.T.:
>>            http://www.opengroup.org/consortia_services 
>>
>>========================================================================



From owner-ietf-ldapbis@OpenLDAP.org  Wed May 21 16:18:40 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 QAA07462
	for <ldapbis-archive@lists.ietf.org>; Wed, 21 May 2003 16:18:40 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4LK9SFV067592;
	Wed, 21 May 2003 20:17: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 h4LK9EcU067574;
	Wed, 21 May 2003 20:09:14 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 21 May 2003 20:09:14 +0000
Received: from pat.uio.no (pat.uio.no [129.240.130.16])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4LK9CEh067563
	for <ietf-ldapbis@openldap.org>; Wed, 21 May 2003 20:09:13 GMT
	(envelope-from hbf@bombur.uio.no)
Received: from mail-mx2.uio.no ([129.240.10.30])
	by pat.uio.no with esmtp (Exim 2.12 #7)
	id 19IZtg-0004aA-00
	for ietf-ldapbis@openldap.org; Wed, 21 May 2003 22:09:12 +0200
Received: from [129.240.130.14] (helo=mons.uio.no)
	by mail-mx2.uio.no with esmtp (Exim 4.14)
	id 19IZtd-0003Jl-Dq
	for ietf-ldapbis@openldap.org; Wed, 21 May 2003 22:09:09 +0200
Received: from bombur.uio.no ([129.240.186.42])
	by mons.uio.no with esmtp (Exim 2.12 #7)
	id 19IR3c-000441-00; Wed, 21 May 2003 12:42:52 +0200
Received: from hbf by bombur.uio.no with local (Exim 2.12 #7)
	id 19IR3Y-0004m7-00; Wed, 21 May 2003 12:42:48 +0200
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Message-Id: <HBF.20030521bg8n@bombur.uio.no>
To: ietf-ldapbis@OpenLDAP.org
Subject: [Syntaxes] Generalized Time inconsistent with ASN.1
Date: Wed, 21 May 2003 12:42:48 +0200
X-MailScanner-Information: Please contact postmaster@uio.no for more information
X-UiO-MailScanner: Found to be clean
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>

ASN.1: X.680 (07/2002), section 42, says that 'Z' or timezone in
Generalized Time is optional, and if it is missing the time is local
time.  In the Syntaxes draft, 'Z' or timezone is mandatory.

-- 
Hallvard


From owner-ietf-ldapbis@OpenLDAP.org  Wed May 21 23:21:51 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 XAA16860
	for <ldapbis-archive@lists.ietf.org>; Wed, 21 May 2003 23:21:50 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4M3FVEl091059;
	Thu, 22 May 2003 03:19: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 h4M3AhNw090991;
	Thu, 22 May 2003 03:10:43 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 22 May 2003 03:10:43 +0000
Received: from smtpproxy1.mitre.org (smtpproxy1.mitre.org [192.160.51.75])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4M3AZEh090981
	for <ietf-ldapbis@openldap.org>; Thu, 22 May 2003 03:10:41 GMT
	(envelope-from kdally@mitre.org)
Received: from avsrv1.mitre.org (avsrv1.mitre.org [129.83.20.58])
	by smtpproxy1.mitre.org (8.12.9/8.12.8) with ESMTP id h4M3AKn5018835;
	Wed, 21 May 2003 23:10:21 -0400 (EDT)
Received: from MAILHUB1 (mailhub1.mitre.org [129.83.20.31])
	by smtpsrv1.mitre.org (8.12.9/8.12.8) with ESMTP id h4M3AGOH024267;
	Wed, 21 May 2003 23:10:16 -0400 (EDT)
Received: from wmodempoo1-13.mitre.org (128.29.251.13) by mailhub1.mitre.org with SMTP
        id 2560082; Wed, 21 May 2003 23:10:13 -0400
Message-ID: <3ECC3F94.9633884@mitre.org>
Date: Wed, 21 May 2003 23:10:12 -0400
From: Kathy Dally <kdally@mitre.org>
Organization: The MITRE Corporation
X-Mailer: Mozilla 4.79 [en]C-20020130M  (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
CC: steven.legg@adacel.com.au, ietf-ldapbis@OpenLDAP.org
Subject: Re: Generalized Time/UTC Time need leap seconds
References: <HBF.20030110genh@bombur.uio.no>
		<004a01c2ba94$9d780590$a518200a@osmium.mtwav.adacel.com.au> <HBF.20030521ddj@bombur.uio.no>
Content-Type: text/plain; charset=us-ascii
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

Hi All!

I checked ISO 8601, and it does support leap second.

Thanks,
Kathy


Hallvard B Furuseth wrote:
> 
> Steven Legg writes:
> 
> >>> [Syntaxes] 4.3.13 (Generalized Time) says:
> >>>
> >>>       second  = %x30-36 %x30-39                        ; "00" to "59"
> >>>
> >>> That should be "00" to "60", since Coordinated Universal Time has
> >>> leap seconds.  See e.g. <http://tycho.usno.navy.mil/systime.html>.
> > (...)
> > The UTCTime type in X.680 doesn't allow for leap seconds (60 seconds
> > is an illegal value). I still have to check whether GeneralizedTime
> > allows it.
> 
> X.680 (07/2002) in
> <http://www.itu.int/ITU-T/studygroups/com17/languages/> defers to
> ISO 8601, which does allow leap seconds according to
> <http://www.cl.cam.ac.uk/~mgk25/iso-time.html>.  I don't have the
> actual ISO 8601 document.
> 
> --
> Hallvard



From owner-ietf-ldapbis@OpenLDAP.org  Thu May 22 02:56: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 CAA02536
	for <ldapbis-archive@lists.ietf.org>; Thu, 22 May 2003 02:56:11 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4M6jWF5097306;
	Thu, 22 May 2003 06:54:05 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 h4M6eUOc097058;
	Thu, 22 May 2003 06:40:30 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 22 May 2003 06:40:30 +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 h4M6eREh097025
	for <ietf-ldapbis@openldap.org>; Thu, 22 May 2003 06:40:28 GMT
	(envelope-from steven.legg@adacel.com.au)
Received: from nexus.adacel.com (Not Verified[10.32.240.1]) by adacel.com with MailMarshal (v5,0,3,91)
	id <B000072172>; Thu, 22 May 2003 16:36:54 +1000
Received: (qmail 32738 invoked from network); 22 May 2003 06:39:25 -0000
Received: from unknown (HELO osmium) (10.32.24.165)
  by nexus.adacel.com with SMTP; 22 May 2003 06:39:25 -0000
Reply-To: <steven.legg@adacel.com.au>
From: "Steven Legg" <steven.legg@adacel.com.au>
To: "'Hallvard B Furuseth'" <h.b.furuseth@usit.uio.no>,
        <ietf-ldapbis@OpenLDAP.org>
Subject: RE: [Syntaxes] Generalized Time inconsistent with ASN.1
Date: Thu, 22 May 2003 16:40:04 +1000
Message-ID: <004a01c3202c$fa9a1e40$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
In-Reply-To: <HBF.20030521bg8n@bombur.uio.no>
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


Hallvard,

Hallvard B Furuseth wrote:
> ASN.1: X.680 (07/2002), section 42, says that 'Z' or timezone in
> Generalized Time is optional, and if it is missing the time is local
> time.  In the Syntaxes draft, 'Z' or timezone is mandatory.

It's mandatory in the syntaxes draft because it is mandatory in RFC 2252.
RFC 2252 disallows local time.

Regards,
Steven
 


From owner-ietf-ldapbis@OpenLDAP.org  Thu May 22 08:31: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 IAA11220
	for <ldapbis-archive@lists.ietf.org>; Thu, 22 May 2003 08:31:35 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4MBvYG1014615;
	Thu, 22 May 2003 12:29: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 h4MBqjJp014362;
	Thu, 22 May 2003 11:52:45 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 22 May 2003 11:52:45 +0000
Received: from pat.uio.no (pat.uio.no [129.240.130.16])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4MBqgEh014352
	for <ietf-ldapbis@openldap.org>; Thu, 22 May 2003 11:52:43 GMT
	(envelope-from hbf@bombur.uio.no)
Received: from mail-mx2.uio.no ([129.240.10.30])
	by pat.uio.no with esmtp (Exim 2.12 #7)
	id 19Ioch-0006GT-00; Thu, 22 May 2003 13:52:39 +0200
Received: from [129.240.201.2] (helo=goggins.uio.no)
	by mail-mx2.uio.no with esmtp (Exim 4.14)
	id 19IoYc-0001On-Q5; Thu, 22 May 2003 13:48:26 +0200
Received: from bombur.uio.no ([129.240.186.42])
	by goggins.uio.no with esmtp (Exim 2.12 #7)
	id 19IoYR-0004eI-00; Thu, 22 May 2003 13:48:15 +0200
Received: from hbf by bombur.uio.no with local (Exim 2.12 #7)
	id 19IoYQ-0002fz-00; Thu, 22 May 2003 13:48:14 +0200
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Message-Id: <HBF.20030522msyf@bombur.uio.no>
To: steven.legg@adacel.com.au
Cc: ietf-ldapbis@OpenLDAP.org
Subject: RE: [Syntaxes] Generalized Time inconsistent with ASN.1
In-Reply-To: <004a01c3202c$fa9a1e40$a518200a@osmium.mtwav.adacel.com.au>
References: <HBF.20030521bg8n@bombur.uio.no>
	<004a01c3202c$fa9a1e40$a518200a@osmium.mtwav.adacel.com.au>
X-Mailer: VM 6.37 under Emacs 19.34.1
Date: Thu, 22 May 2003 13:48:14 +0200
X-MailScanner-Information: Please contact postmaster@uio.no for more information
X-UiO-MailScanner: Found to be clean
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>

Steven Legg writes:
>Hallvard B Furuseth wrote:
>> ASN.1: X.680 (07/2002), section 42, says that 'Z' or timezone in
>> Generalized Time is optional, and if it is missing the time is local
>> time.  In the Syntaxes draft, 'Z' or timezone is mandatory.
> 
> It's mandatory in the syntaxes draft because it is mandatory in RFC 2252.
> RFC 2252 disallows local time.

I take it making the time zone optional is too big a change for ldapbis?
How about allowing servers to support local time, but not demainding it?

Or does X.500 disallow local time too?  I've looked at X.500, but all I
could find was X.520 6.3.3 'Generalized Time Match' which refers to
clauses 34.3 b) or c) of CCITT Rec. X.208 | ISO/IEC 8824.

-- 
Hallvard



From owner-ietf-ldapbis@OpenLDAP.org  Thu May 22 08:54: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 IAA11725
	for <ldapbis-archive@lists.ietf.org>; Thu, 22 May 2003 08:54:12 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4MCjYEl018333;
	Thu, 22 May 2003 12:52: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 h4MChScr018164;
	Thu, 22 May 2003 12:43:28 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 22 May 2003 12:43:28 +0000
Received: from nb2.stroeder.com (krl9-d9bb4d10.pool.mediaWays.net [217.187.77.16])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4MChQEh018118
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 22 May 2003 12:43:26 GMT
	(envelope-from michael@stroeder.com)
Received: from localhost (localhost.stroeder.com [127.0.0.1])
	by nb2.stroeder.com (Postfix) with ESMTP
	id 615F769B92; Thu, 22 May 2003 14:43:05 +0200 (CEST)
Received: from stroeder.com (localhost.stroeder.com [127.0.0.1])
	by nb2.stroeder.com (Postfix) with ESMTP
	id 61AEF59326; Thu, 22 May 2003 14:43:04 +0200 (CEST)
Message-ID: <3ECCC5D6.4010908@stroeder.com>
Date: Thu, 22 May 2003 14:43:02 +0200
From: =?ISO-8859-1?Q?Michael_Str=F6der?= <michael@stroeder.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3.1) Gecko/20030425
X-Accept-Language: de-de, de, en-us, en
MIME-Version: 1.0
To: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Cc: ietf-ldapbis@OpenLDAP.org
Subject: Re: [Syntaxes] Generalized Time inconsistent with ASN.1
References: <HBF.20030521bg8n@bombur.uio.no>	<004a01c3202c$fa9a1e40$a518200a@osmium.mtwav.adacel.com.au> <HBF.20030522msyf@bombur.uio.no>
In-Reply-To: <HBF.20030522msyf@bombur.uio.no>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by AMaViS 0.3.12pre8
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

Hallvard B Furuseth wrote:
> 
> I take it making the time zone optional is too big a change for ldapbis?
> How about allowing servers to support local time, but not demainding it?

Personally I'd like to leave it as is since it's well-defined and simple. 
What implementors definitely not need is dealing with yet another optional 
case. We have already way too many "OPTIONALs" in LDAP.

Ciao, Michael.



From owner-ietf-ldapbis@OpenLDAP.org  Thu May 22 09: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 JAA12484
	for <ldapbis-archive@lists.ietf.org>; Thu, 22 May 2003 09:17:18 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4MCpYFP018740;
	Thu, 22 May 2003 13:15:49 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 h4MCpQqM018680;
	Thu, 22 May 2003 12:51:26 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 22 May 2003 12:51:25 +0000
Received: from nb2.stroeder.com (krl9-d9bb4d10.pool.mediaWays.net [217.187.77.16])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4MCpOEh018632
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 22 May 2003 12:51:24 GMT
	(envelope-from michael@stroeder.com)
Received: from localhost (localhost.stroeder.com [127.0.0.1])
	by nb2.stroeder.com (Postfix) with ESMTP
	id 1E2FA6A543; Thu, 22 May 2003 14:51:03 +0200 (CEST)
Received: from stroeder.com (localhost.stroeder.com [127.0.0.1])
	by nb2.stroeder.com (Postfix) with ESMTP
	id D7B2769869; Thu, 22 May 2003 14:51:01 +0200 (CEST)
Message-ID: <3ECCC7B5.9050002@stroeder.com>
Date: Thu, 22 May 2003 14:51:01 +0200
From: =?ISO-8859-1?Q?Michael_Str=F6der?= <michael@stroeder.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3.1) Gecko/20030425
X-Accept-Language: de-de, de, en-us, en
MIME-Version: 1.0
To: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Cc: ietf-ldapbis@OpenLDAP.org
Subject: Re: [Syntaxes] Generalized Time inconsistent with ASN.1
References: <HBF.20030521bg8n@bombur.uio.no>	<004a01c3202c$fa9a1e40$a518200a@osmium.mtwav.adacel.com.au> <HBF.20030522msyf@bombur.uio.no>
In-Reply-To: <HBF.20030522msyf@bombur.uio.no>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by AMaViS 0.3.12pre8
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

Hallvard B Furuseth wrote:
> 
> I take it making the time zone optional is too big a change for ldapbis?

Another one:

user (sitting in Hongkong)
   --HTTP--> web gateway (Germany)
     --LDAP--> LDAP server (U.S.)

Which "local" time should be displayed to the user?

Ciao, Michael.



From owner-ietf-ldapbis@OpenLDAP.org  Thu May 22 09:35:58 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 JAA13447
	for <ldapbis-archive@lists.ietf.org>; Thu, 22 May 2003 09:35:58 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4MDLYF9021084;
	Thu, 22 May 2003 13:34:22 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 h4MDJrte020983;
	Thu, 22 May 2003 13:19:53 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 22 May 2003 13:19:53 +0000
Received: from prv-mail25.provo.novell.com (prv-mail25.provo.novell.com [137.65.81.121])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4MDJqEh020950
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 22 May 2003 13:19:52 GMT
	(envelope-from gvithalprasad@novell.com)
Received: from INET-PRV1-MTA by prv-mail25.provo.novell.com
	with Novell_GroupWise; Thu, 22 May 2003 07:19:31 -0600
Message-Id: <secc7a03.087@prv-mail25.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.0 
Date: Thu, 22 May 2003 07:19:16 -0600
From: "Vithalprasad Gaitonde" <gvithalprasad@novell.com>
To: <ietf-ldapbis@OpenLDAP.org>
Subject: Example in draft-ietf-ldapbis-url-03.txt
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

Section 7 of this document gives an example of (int=\00\00\00\04) and
shows hot the LDAP URL representation for the same.
The use of "int" seems to indicate here that its an integer attribute
which is being talked about. Its unlikely that an integer syntax
attribute will encoded like this.
Though its not technically incorrect, for better readability sake,
would it be a good idea to choose some other attribute name than "int"
like bin (bin=\00\00\00\04) as in section 7 of
draft-ietf-ldapbis-filter-04.txt.

Thanks,
Prasad



From owner-ietf-ldapbis@OpenLDAP.org  Thu May 22 09:42: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 JAA13648
	for <ldapbis-archive@lists.ietf.org>; Thu, 22 May 2003 09:42:50 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4MDVJEl022102;
	Thu, 22 May 2003 13:41: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 h4MDCMQ4020276;
	Thu, 22 May 2003 13:12:22 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 22 May 2003 13:12:22 +0000
Received: from pat.uio.no (pat.uio.no [129.240.130.16])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4MDCEEh020263
	for <ietf-ldapbis@openldap.org>; Thu, 22 May 2003 13:12:15 GMT
	(envelope-from hbf@bombur.uio.no)
Received: from mail-mx2.uio.no ([129.240.10.30])
	by pat.uio.no with esmtp (Exim 2.12 #7)
	id 19Iprg-0003HP-00; Thu, 22 May 2003 15:12:12 +0200
Received: from [129.240.130.14] (helo=mons.uio.no)
	by mail-mx2.uio.no with esmtp (Exim 4.14)
	id 19Ipra-0005cy-Pu; Thu, 22 May 2003 15:12:06 +0200
Received: from bombur.uio.no ([129.240.186.42])
	by mons.uio.no with esmtp (Exim 2.12 #7)
	id 19Ipra-000766-00; Thu, 22 May 2003 15:12:06 +0200
Received: from hbf by bombur.uio.no with local (Exim 2.12 #7)
	id 19IprZ-0005TF-00; Thu, 22 May 2003 15:12:05 +0200
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Message-Id: <HBF.20030522lehn@bombur.uio.no>
To: =?ISO-8859-1?Q?Michael_Str=F6der?= <michael@stroeder.com>
Cc: ietf-ldapbis@OpenLDAP.org
Subject: Re: [Syntaxes] Generalized Time inconsistent with ASN.1
In-Reply-To: <3ECCC7B5.9050002@stroeder.com>
References: <HBF.20030521bg8n@bombur.uio.no>
	<004a01c3202c$fa9a1e40$a518200a@osmium.mtwav.adacel.com.au>
	<HBF.20030522msyf@bombur.uio.no>
	<3ECCC7B5.9050002@stroeder.com>
X-Mailer: VM 6.37 under Emacs 19.34.1
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Date: Thu, 22 May 2003 15:12:05 +0200
X-MailScanner-Information: Please contact postmaster@uio.no for more information
X-UiO-MailScanner: Found to be clean
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by boole.openldap.org id h4MDCFEh020264
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

Michael Ströder writes:
>Hallvard B Furuseth wrote:
>> 
>> I take it making the time zone optional is too big a change for ldapbis?
>
> user (sitting in Hongkong)
>    --HTTP--> web gateway (Germany)
>      --LDAP--> LDAP server (U.S.)
>
> Which "local" time should be displayed to the user?

Time without timezone, I think.  What it means is the user's problem, if
he uses it in such a context.  However, time without timezone can be
useful in genuinely local contexts.  For example, work hours here starts
at 8:00 local time all year, but which timezone that is varies due to
daylight savings time.

-- 
Hallvard



From owner-ietf-ldapbis@OpenLDAP.org  Thu May 22 10:21: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 KAA16046
	for <ldapbis-archive@lists.ietf.org>; Thu, 22 May 2003 10:21: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 h4MDpYFL023643;
	Thu, 22 May 2003 14:21: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 h4MDmDnw023410;
	Thu, 22 May 2003 13:48:13 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 22 May 2003 13:48:13 +0000
Received: from nb2.stroeder.com (krl9-d9bb4d10.pool.mediaWays.net [217.187.77.16])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4MDmBEh023371
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 22 May 2003 13:48:12 GMT
	(envelope-from michael@stroeder.com)
Received: from localhost (localhost.stroeder.com [127.0.0.1])
	by nb2.stroeder.com (Postfix) with ESMTP
	id 40FD26F791; Thu, 22 May 2003 15:47:49 +0200 (CEST)
Received: from stroeder.com (localhost.stroeder.com [127.0.0.1])
	by nb2.stroeder.com (Postfix) with ESMTP
	id 508D56BED6; Thu, 22 May 2003 15:47:48 +0200 (CEST)
Message-ID: <3ECCD504.6040208@stroeder.com>
Date: Thu, 22 May 2003 15:47:48 +0200
From: =?ISO-8859-1?Q?Michael_Str=F6der?= <michael@stroeder.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3.1) Gecko/20030425
X-Accept-Language: de-de, de, en-us, en
MIME-Version: 1.0
To: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Cc: ietf-ldapbis@OpenLDAP.org
Subject: Re: [Syntaxes] Generalized Time inconsistent with ASN.1
References: <HBF.20030521bg8n@bombur.uio.no>	<004a01c3202c$fa9a1e40$a518200a@osmium.mtwav.adacel.com.au>	<HBF.20030522msyf@bombur.uio.no>	<3ECCC7B5.9050002@stroeder.com> <HBF.20030522lehn@bombur.uio.no>
In-Reply-To: <HBF.20030522lehn@bombur.uio.no>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
X-Virus-Scanned: by AMaViS 0.3.12pre8
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by boole.openldap.org id h4MDmCEh023400
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

Hallvard B Furuseth wrote:
 > Michael Ströder writes:
 >
 >>Hallvard B Furuseth wrote:
 >>
 >>>I take it making the time zone optional is too big a change for ldapbis?
 >>
 >>user (sitting in Hongkong)
 >>   --HTTP--> web gateway (Germany)
 >>     --LDAP--> LDAP server (U.S.)
 >>
 >>Which "local" time should be displayed to the user?
 >
 > Time without timezone, I think.

And how should generalizedTimeOrderingMatch be implemented in this scenario?

 >  What it means is the user's problem, if he uses it in such a context.

Sorry, does not make sense to me. Please leave it strictly as defined in 
RFC2252.

 > However, time without timezone can be useful in genuinely local contexts.

How about allow garbage in, produce correct output?
A server implementor MAY decide to accept attribute values for 
GeneralizedTime without time zone. But the server MUST return the attribute 
value with time zone set, the attribute value massaged according to some 
local time zone configuration.

 > For example, work hours here starts
 > at 8:00 local time all year, but which timezone that is varies due to
 > daylight savings time.

Can you imagine all the weird postings to mailing lists with people asking 
how that is supposed to work? We should try to avoid adding yet more blurred 
definitions like the "minimum upper bound" in attribute type declaration...

Ciao, Michael.




From owner-ietf-ldapbis@OpenLDAP.org  Thu May 22 10:38: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 KAA16571
	for <ldapbis-archive@lists.ietf.org>; Thu, 22 May 2003 10:38:40 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4ME3YFx024689;
	Thu, 22 May 2003 14:35: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 h4MDwCGB024318;
	Thu, 22 May 2003 13:58:12 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 22 May 2003 13:58:12 +0000
Received: from netscape.com (r2d2.aoltw.net [64.236.137.26])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4MDwAEh024229
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 22 May 2003 13:58:10 GMT
	(envelope-from mcs@netscape.com)
Received: from judge.mcom.com (judge.nscp.aoltw.net [10.169.8.47])
	by netscape.com (8.10.0/8.10.0) with ESMTP id h4MDvfE26814
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 22 May 2003 06:57:41 -0700 (PDT)
Received: from netscape.com ([10.169.192.44]) by judge.mcom.com
          (Netscape Messaging Server 4.15) with ESMTP id HFAK4902.FHM;
          Thu, 22 May 2003 06:57:45 -0700 
Message-ID: <3ECCD758.30701@netscape.com>
Date: Thu, 22 May 2003 09:57:44 -0400
From: mcs@netscape.com (Mark C Smith)
Organization: Netscape Communications Corp.
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.3) Gecko/20030314
X-Accept-Language: English/United States [en-US],English [en]
MIME-Version: 1.0
To: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
CC: =?ISO-8859-1?Q?Michael_Str=F6der?= <michael@stroeder.com>,
        ietf-ldapbis@OpenLDAP.org
Subject: Re: [Syntaxes] Generalized Time inconsistent with ASN.1
References: <HBF.20030521bg8n@bombur.uio.no>	<004a01c3202c$fa9a1e40$a518200a@osmium.mtwav.adacel.com.au>	<HBF.20030522msyf@bombur.uio.no>	<3ECCC7B5.9050002@stroeder.com> <HBF.20030522lehn@bombur.uio.no>
In-Reply-To: <HBF.20030522lehn@bombur.uio.no>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by boole.openldap.org id h4MDwAEh024307
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

Hallvard B Furuseth wrote:
> Michael Ströder writes:
> 
>>Hallvard B Furuseth wrote:
>>
>>>I take it making the time zone optional is too big a change for ldapbis?
>>
>>user (sitting in Hongkong)
>>   --HTTP--> web gateway (Germany)
>>     --LDAP--> LDAP server (U.S.)
>>
>>Which "local" time should be displayed to the user?
> 
> 
> Time without timezone, I think.  What it means is the user's problem, if
> he uses it in such a context.  However, time without timezone can be
> useful in genuinely local contexts.  For example, work hours here starts
> at 8:00 local time all year, but which timezone that is varies due to
> daylight savings time.

I do no think we should make timezone optional. In my opinion, that is a 
very bad idea and will likely reduce interoperability among LDAP 
implementations. I agree with Michael that things are nice and simple 
and well understood as currently specified.

-- 
Mark Smith
Netscape Directory Product Development
My words are my own, not my employer's.




From owner-ietf-ldapbis@OpenLDAP.org  Thu May 22 11:28:59 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 LAA18453
	for <ldapbis-archive@lists.ietf.org>; Thu, 22 May 2003 11:28:59 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4MF9pGN031548;
	Thu, 22 May 2003 15:26: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 h4MExCoK030575;
	Thu, 22 May 2003 14:59:12 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 22 May 2003 14:59:12 +0000
Received: from pat.uio.no (pat.uio.no [129.240.130.16])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4MEx9Eh030550
	for <ietf-ldapbis@openldap.org>; Thu, 22 May 2003 14:59:10 GMT
	(envelope-from hbf@bombur.uio.no)
Received: from mail-mx1.uio.no ([129.240.10.29])
	by pat.uio.no with esmtp (Exim 2.12 #7)
	id 19IrX7-0000qI-00; Thu, 22 May 2003 16:59:05 +0200
Received: from [129.240.130.14] (helo=mons.uio.no)
	by mail-mx1.uio.no with esmtp (Exim 4.14)
	id 19Ir2F-0003Ul-EX; Thu, 22 May 2003 16:27:11 +0200
Received: from bombur.uio.no ([129.240.186.42])
	by mons.uio.no with esmtp (Exim 2.12 #7)
	id 19Ir2F-0001R9-00; Thu, 22 May 2003 16:27:11 +0200
Received: from hbf by bombur.uio.no with local (Exim 2.12 #7)
	id 19Ir2E-0006Hc-00; Thu, 22 May 2003 16:27:10 +0200
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Message-Id: <HBF.20030522k5at@bombur.uio.no>
To: =?ISO-8859-1?Q?Michael_Str=F6der?= <michael@stroeder.com>
Cc: ietf-ldapbis@OpenLDAP.org
Subject: Re: [Syntaxes] Generalized Time inconsistent with ASN.1
In-Reply-To: <3ECCD504.6040208@stroeder.com>
References: <HBF.20030521bg8n@bombur.uio.no>
	<004a01c3202c$fa9a1e40$a518200a@osmium.mtwav.adacel.com.au>
	<HBF.20030522msyf@bombur.uio.no>
	<3ECCC7B5.9050002@stroeder.com>
	<HBF.20030522lehn@bombur.uio.no>
	<3ECCD504.6040208@stroeder.com>
X-Mailer: VM 6.37 under Emacs 19.34.1
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Date: Thu, 22 May 2003 16:27:10 +0200
X-MailScanner-Information: Please contact postmaster@uio.no for more information
X-UiO-MailScanner: Found to be clean
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by boole.openldap.org id h4MExAEh030552
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

Michael Ströder writes:
>Hallvard B Furuseth wrote:
>>Michael Ströder writes:
>>>
>>>user (sitting in Hongkong)
>>>   --HTTP--> web gateway (Germany)
>>>     --LDAP--> LDAP server (U.S.)
>>>
>>>Which "local" time should be displayed to the user?
>>
>> Time without timezone, I think.
> 
> And how should generalizedTimeOrderingMatch be implemented in this
> scenario?

Comparing local time with timezoned time would be undefined.  Well, the
server could get clever and decide that it's defined if the difference
is the same whatever timezone is used, but I see no need for such
cleverness.

Except I seem to be outvoted on this one anyway, so never mind.

>> However, time without timezone can be useful in genuinely local
>> contexts.
> 
> How about allow garbage in, produce correct output?  A server
> implementor MAY decide to accept attribute values for GeneralizedTime
> without time zone. But the server MUST return the attribute value with
> time zone set, the attribute value massaged according to some local
> time zone configuration.

I don't think so.  From the user's point of view, software that tries to
be smart and silently adds 'missing' information to user input all to
often results in correct data in, garbage out.
		
-- 
Hallvard



From owner-ietf-ldapbis@OpenLDAP.org  Thu May 22 12:42:22 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 MAA20712
	for <ldapbis-archive@lists.ietf.org>; Thu, 22 May 2003 12:42: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 h4MGdZEn039554;
	Thu, 22 May 2003 16:40:10 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 h4MGaixS039429;
	Thu, 22 May 2003 16:36:44 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 22 May 2003 16:36:44 +0000
Received: from netscape.com (c3po.aoltw.net [64.236.137.25])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4MGahEh039378
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 22 May 2003 16:36:43 GMT
	(envelope-from mcs@netscape.com)
Received: from judge.mcom.com (judge.nscp.aoltw.net [10.169.8.47])
	by netscape.com (8.10.0/8.10.0) with ESMTP id h4MGaJn25602
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 22 May 2003 09:36:19 -0700 (PDT)
Received: from netscape.com ([10.169.192.40]) by judge.mcom.com
          (Netscape Messaging Server 4.15) with ESMTP id HFARGI01.7HQ;
          Thu, 22 May 2003 09:36:18 -0700 
Message-ID: <3ECCFC70.3090007@netscape.com>
Date: Thu, 22 May 2003 12:36:00 -0400
From: mcs@netscape.com (Mark C Smith)
Organization: Netscape Communications Corp.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030428 Netscape/7.02+
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Vithalprasad Gaitonde <gvithalprasad@novell.com>
CC: ietf-ldapbis@OpenLDAP.org
Subject: Re: Example in draft-ietf-ldapbis-url-03.txt
References: <secc7a03.087@prv-mail25.provo.novell.com>
In-Reply-To: <secc7a03.087@prv-mail25.provo.novell.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

Vithalprasad Gaitonde wrote:
> Section 7 of this document gives an example of (int=\00\00\00\04) and
> shows hot the LDAP URL representation for the same.
> The use of "int" seems to indicate here that its an integer attribute
> which is being talked about. Its unlikely that an integer syntax
> attribute will encoded like this.
> Though its not technically incorrect, for better readability sake,
> would it be a good idea to choose some other attribute name than "int"
> like bin (bin=\00\00\00\04) as in section 7 of
> draft-ietf-ldapbis-filter-04.txt.

OK, this is a good suggestion.

-- 
Mark Smith
Netscape Directory Product Development
My words are my own, not my employer's.



From owner-ietf-ldapbis@OpenLDAP.org  Thu May 22 21:18: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 VAA07235
	for <ldapbis-archive@lists.ietf.org>; Thu, 22 May 2003 21:18:16 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4N1FcEl070276;
	Fri, 23 May 2003 01:16:30 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 h4N1DOQk070209;
	Fri, 23 May 2003 01:13:24 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Fri, 23 May 2003 01:13:24 +0000
Received: from ausyms50.ca.com ([155.35.248.106])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4N1DMEh070186
	for <ietf-ldapbis@OpenLDAP.org>; Fri, 23 May 2003 01:13:23 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);
	 Fri, 23 May 2003 11:13: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: Example in draft-ietf-ldapbis-url-03.txt
Date: Fri, 23 May 2003 11:13:00 +1000
Message-ID: <1395B4B334FCC143B36AF788E68B63811A63B9@ausyms21.ca.com>
Thread-Topic: Example in draft-ietf-ldapbis-url-03.txt
Thread-Index: AcMggO1uFHbUgHgOR+S3CQxaNSXn3AAR2Bpw
From: "Ramsay, Ron" <Ron.Ramsay@ca.com>
To: "Mark C Smith" <mcs@netscape.com>,
        "Vithalprasad Gaitonde" <gvithalprasad@novell.com>
Cc: <ietf-ldapbis@OpenLDAP.org>
X-OriginalArrivalTime: 23 May 2003 01:13:01.0007 (UTC) FILETIME=[741C5DF0:01C320C8]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by boole.openldap.org id h4N1DNEh070200
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

It's not really a good idea. Binary attributes should be encoded in ASN.1 and this one clearly isn't! What about using 'oct', say.

-----Original Message-----
From: Mark C Smith [mailto:mcs@netscape.com]
Sent: Friday, 23 May 2003 02:36
To: Vithalprasad Gaitonde
Cc: ietf-ldapbis@OpenLDAP.org
Subject: Re: Example in draft-ietf-ldapbis-url-03.txt


Vithalprasad Gaitonde wrote:
> Section 7 of this document gives an example of (int=\00\00\00\04) and
> shows hot the LDAP URL representation for the same.
> The use of "int" seems to indicate here that its an integer attribute
> which is being talked about. Its unlikely that an integer syntax
> attribute will encoded like this.
> Though its not technically incorrect, for better readability sake,
> would it be a good idea to choose some other attribute name than "int"
> like bin (bin=\00\00\00\04) as in section 7 of
> draft-ietf-ldapbis-filter-04.txt.

OK, this is a good suggestion.

-- 
Mark Smith
Netscape Directory Product Development
My words are my own, not my employer's.





From owner-ietf-ldapbis@OpenLDAP.org  Fri May 23 12:00:51 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 MAA10572
	for <ldapbis-archive@lists.ietf.org>; Fri, 23 May 2003 12:00: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 h4NFvhEl050295;
	Fri, 23 May 2003 15:59: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 h4NFudm3050253;
	Fri, 23 May 2003 15:56:39 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Fri, 23 May 2003 15:56:39 +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 h4NFucEh050243
	for <ietf-ldapbis@OpenLDAP.org>; Fri, 23 May 2003 15:56:38 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 h4NFucc6081024
	for <ietf-ldapbis@OpenLDAP.org>; Fri, 23 May 2003 15:56:38 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030523084130.028d44d0@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Fri, 23 May 2003 08:53:51 -0700
To: ietf-ldapbis@OpenLDAP.org
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: LDAPBIS in Vienna
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>

LDAPBIS will be meeting at IETF#57.  A one hour slot has been
requested so that we can discussion remaining issues/next steps
and gather input for determination of consensus.  If you have
some topic needing face-to-face time, please drop Bob and I
a note.

Tschuess!  Kurt



From owner-ietf-ldapbis@OpenLDAP.org  Fri May 23 20:59:21 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 UAA02469
	for <ldapbis-archive@lists.ietf.org>; Fri, 23 May 2003 20:59:20 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4O0vkEl079711;
	Sat, 24 May 2003 00:58: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 h4O0tWaa079703;
	Sat, 24 May 2003 00:55:32 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Sat, 24 May 2003 00:55:32 +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 h4O0tQEh079693
	for <ietf-ldapbis@OpenLDAP.org>; Sat, 24 May 2003 00:55:31 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 h4O0tQc6084582
	for <ietf-ldapbis@OpenLDAP.org>; Sat, 24 May 2003 00:55:26 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030523172043.027d2798@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Fri, 23 May 2003 17:52:38 -0700
To: ietf-ldapbis@OpenLDAP.org
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: adding 'uid' to ldap-user-schema
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>

The absence of 'uid' has been discussed previously but did not
come up during WG Last Call.  As with 'dc', LDAP DN specification
requires implementations to support the 'uid' attribute type.
Hence, either we need to add 'uid' to ldap-user-schema or drop
requirement in the LDAP DN specification.

As we discussed previously,  I believe it reasonable to consider
the absence of 'uid' (and 'dc') in the core specification as
a technical omission.  As you couldn't implement RFC 2253
without them, they can be considered "core" LDAP schema and
hence we can correct the omission.

I propose that following text be added to ldap-user-schema:

  The 'uid' attribute type specifies computer system
  login names associated with the object. (Source: RFC 1274,
  RFC 2798).

    ( 0.9.2342.19200300.100.1.1
      NAME 'uid'
      EQUALITY caseIgnoreMatch
      SUBSTR caseIgnoreSubstringsMatch
      SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )

Additionally, the I-D will need to "update" rfc2798 and
include some text like:
	This document updates RFC 2798 by replacing informative
	description of the 'uid' attribute type, with the
	definitive description provided in Section X.Y of
	this document.

Comments?



From owner-ietf-ldapbis@OpenLDAP.org  Mon May 26 02:49:17 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 CAA03944
	for <ldapbis-archive@lists.ietf.org>; Mon, 26 May 2003 02:49:16 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4Q6k4El049622;
	Mon, 26 May 2003 06:47: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 h4Q6j4j1049145;
	Mon, 26 May 2003 06:45:04 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 26 May 2003 06:45:04 +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 h4Q6iuEh048968
	for <ietf-ldapbis@openldap.org>; Mon, 26 May 2003 06:45:02 GMT
	(envelope-from steven.legg@adacel.com.au)
Received: from nexus.adacel.com (Not Verified[10.32.240.1]) by adacel.com with MailMarshal (v5,0,3,91)
	id <B000076ccf>; Mon, 26 May 2003 16:41:53 +1000
Received: (qmail 26376 invoked from network); 26 May 2003 06:43:26 -0000
Received: from unknown (HELO osmium) (10.32.24.165)
  by nexus.adacel.com with SMTP; 26 May 2003 06:43:26 -0000
Reply-To: <steven.legg@adacel.com.au>
From: "Steven Legg" <steven.legg@adacel.com.au>
To: "'Kathy Dally'" <kdally@mitre.org>,
        "'Hallvard B Furuseth'" <h.b.furuseth@usit.uio.no>
Cc: <ietf-ldapbis@OpenLDAP.org>
Subject: RE: Generalized Time/UTC Time need leap seconds
Date: Mon, 26 May 2003 16:44:32 +1000
Message-ID: <003901c32352$441e6940$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
In-reply-To: <3ECC3F94.9633884@mitre.org>
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


Kathy Dally wrote:
> Hi All!
> 
> I checked ISO 8601, and it does support leap second.

Thanks Kathy. I shall change the ABNF for GeneralizedTime
to allow "60" seconds.

Regards,
Steven

> 
> Thanks,
> Kathy
> 
> 
> Hallvard B Furuseth wrote:
> > 
> > Steven Legg writes:
> > 
> > >>> [Syntaxes] 4.3.13 (Generalized Time) says:
> > >>>
> > >>>       second  = %x30-36 %x30-39                        
> ; "00" to "59"
> > >>>
> > >>> That should be "00" to "60", since Coordinated 
> Universal Time has
> > >>> leap seconds.  See e.g. 
<http://tycho.usno.navy.mil/systime.html>.
> > (...)
> > The UTCTime type in X.680 doesn't allow for leap seconds (60 seconds
> > is an illegal value). I still have to check whether GeneralizedTime
> > allows it.
> 
> X.680 (07/2002) in
> <http://www.itu.int/ITU-T/studygroups/com17/languages/> defers to
> ISO 8601, which does allow leap seconds according to
> <http://www.cl.cam.ac.uk/~mgk25/iso-time.html>.  I don't have the
> actual ISO 8601 document.
> 
> --
> Hallvard




From owner-ietf-ldapbis@OpenLDAP.org  Mon May 26 14:53: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 OAA21050
	for <ldapbis-archive@lists.ietf.org>; Mon, 26 May 2003 14:53: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 h4QIqPEh097510;
	Mon, 26 May 2003 18:52:25 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 h4QIhvIG097062;
	Mon, 26 May 2003 18:43:57 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 26 May 2003 18:43:57 +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 h4QIhuEh097051
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 26 May 2003 18:43:56 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 h4QIhuc6009219
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 26 May 2003 18:43:56 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030523163225.0278b740@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Mon, 26 May 2003 11:41:06 -0700
To: ietf-ldapbis@OpenLDAP.org
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: IETF ldapbis WG Last Call:
  draft-ietf-ldapbis-user-schema-05.txt
In-Reply-To: <5.2.0.9.0.20030505170904.02aa92c0@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>

This message serves to summarize issues to be addressed
before this I-D is progressed.  For each issue, I have suggested
a course of action which I believe to be consistent with WG
consensus.  If you don't believe the this course of action
is appropriate, please comment within the next couple of days.
Otherwise, the chairs will declare these issues resolved and
direct the editor to revise the document accordingly.

KurtZ raised concerns regarding the ommission of an 'uid' attribute
type specification.  He made a proposal to add it.  No one opposed
this proposal, implement it.

MarkH raised concerns regarding suggested upper limits.
StevenL proposed that all suggested upper limits be removed
to avoid confusion.  No one opposed this proposal, implement it.

KurtZ raised concerns regarding internationalization of textual
user passwords.  Kurt proposed that it be recommended that applications
prepare textural passwords by first transcoding them to Unicode,
apply SASLprep, and then encoding them as UTF-8.  Hallvard offered
some word smithing which was found acceptable.  No one opposed this
proposal, implement it.

NorbertK raised concerns regarding alternative names used for
in some implementations which do not appear in the attribute
type's formal description and suggested they be added.  Objections
to the proposal were raised.  The proposal is rejected.

KurtZ provided a laundry list of issues.  For brevity, I will
only summarize technical issues.  There were no opposing comments
to any of his proposals.

KurtZ noted that most attribute types are discussed in single
value terms though are declared as multiple values.  Kurt
proposed that the editor reword each description to reflect
their multi-valued-ness.  Clarify.

KurtZ noted that the description of 'dc' is needs further
clarification.  Clarify as noted.

KurtZ noted 'destinationIndicator' specification does not
include a statement of how the attribute type is used.  Clarify.

KurtZ noted the description of 'givenName' is inconsistent
with that provided in X.520.  Clarify.

KurtZ proposed that the 'domain' object class should not have
been added to the specification.  Remove.

KurtZ raised a security consideration regarding session hijacking.
Add consideration.




From owner-ietf-ldapbis@OpenLDAP.org  Mon May 26 15:47:27 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 PAA23990
	for <ldapbis-archive@lists.ietf.org>; Mon, 26 May 2003 15:47:23 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4QJk8El099233;
	Mon, 26 May 2003 19:46: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 h4QJfNwM099122;
	Mon, 26 May 2003 19:41:23 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 26 May 2003 19:41:23 +0000
Received: from nb2.stroeder.com (krl9-d9bb4cbc.pool.mediaWays.net [217.187.76.188])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4QJeuEh099069;
	Mon, 26 May 2003 19:41:02 GMT
	(envelope-from michael@stroeder.com)
Received: from localhost (localhost.stroeder.com [127.0.0.1])
	by nb2.stroeder.com (Postfix) with ESMTP
	id 0C8DA59BB3; Mon, 26 May 2003 21:40:30 +0200 (CEST)
Received: from stroeder.com (localhost.stroeder.com [127.0.0.1])
	by nb2.stroeder.com (Postfix) with ESMTP
	id 4030359BAD; Mon, 26 May 2003 21:40:29 +0200 (CEST)
Message-ID: <3ED26DAD.4050705@stroeder.com>
Date: Mon, 26 May 2003 21:40:29 +0200
From: =?ISO-8859-1?Q?Michael_Str=F6der?= <michael@stroeder.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3.1) Gecko/20030425
X-Accept-Language: de-de, de, en-us, en
MIME-Version: 1.0
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Cc: ietf-ldapbis@OpenLDAP.org
Subject: Re: IETF ldapbis WG Last Call:  draft-ietf-ldapbis-user-schema-05.txt
References: <5.2.0.9.0.20030523163225.0278b740@127.0.0.1>
In-Reply-To: <5.2.0.9.0.20030523163225.0278b740@127.0.0.1>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by AMaViS 0.3.12pre8
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:
> 
> KurtZ raised a security consideration regarding session hijacking.
> Add consideration.

???

I can only find a this comment in mailing list archive:

"Add: Use of integrity protection is encouraged to prevent session hijacking."

Which session is meant here?

Ciao, Michael.



From owner-ietf-ldapbis@OpenLDAP.org  Mon May 26 16:10:11 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 QAA25048
	for <ldapbis-archive@lists.ietf.org>; Mon, 26 May 2003 16:10:10 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4QK48Et099935;
	Mon, 26 May 2003 20:08: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 h4QK3x7S099895;
	Mon, 26 May 2003 20:03:59 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 26 May 2003 20:03: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 h4QK3wEh099885
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 26 May 2003 20:03:58 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 h4QK3vc6009678;
	Mon, 26 May 2003 20:03:57 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030526125326.0293ac10@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Mon, 26 May 2003 13:01:07 -0700
To: Michael =?iso-8859-1?Q?Str=F6der?= <michael@stroeder.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: IETF ldapbis WG Last Call: 
  draft-ietf-ldapbis-user-schema-05.txt
Cc: ietf-ldapbis@OpenLDAP.org
In-Reply-To: <3ED26DAD.4050705@stroeder.com>
References: <5.2.0.9.0.20030523163225.0278b740@127.0.0.1>
 <5.2.0.9.0.20030523163225.0278b740@127.0.0.1>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by boole.openldap.org id h4QK3wEh099886
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

At 12:40 PM 5/26/2003, Michael Ströder wrote:
>Kurt D. Zeilenga wrote:
>>KurtZ raised a security consideration regarding session hijacking.
>>Add consideration.
>
>???
>
>I can only find a this comment in mailing list archive:

The comment was raised in "the laundry list".
  http://www.openldap.org/lists/ietf-ldapbis/200305/msg00084.html

>"Add: Use of integrity protection is encouraged to prevent session hijacking."
>
>Which session is meant here?

The LDAP session.

If one uses a mechanism such as DIGEST-MD5 without
negotiating integrity protection to authenticate,
a man-in-middle can hijack the session after
authentication completes. 




From owner-ietf-ldapbis@OpenLDAP.org  Mon May 26 16:29:13 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 QAA25757
	for <ldapbis-archive@lists.ietf.org>; Mon, 26 May 2003 16:29:12 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4QKS8El000943;
	Mon, 26 May 2003 20:28:18 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 h4QKRNJY000933;
	Mon, 26 May 2003 20:27:23 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 26 May 2003 20:27:23 +0000
Received: from pat.uio.no (pat.uio.no [129.240.130.16])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4QKRIEh000903;
	Mon, 26 May 2003 20:27:19 GMT
	(envelope-from hbf@bombur.uio.no)
Received: from mail-mx2.uio.no ([129.240.10.30])
	by pat.uio.no with esmtp (Exim 2.12 #7)
	id 19KOYv-00031U-00; Mon, 26 May 2003 22:27:17 +0200
Received: from [129.240.201.2] (helo=goggins.uio.no)
	by mail-mx2.uio.no with esmtp (Exim 4.14)
	id 19KOYt-0005LL-70; Mon, 26 May 2003 22:27:15 +0200
Received: from bombur.uio.no ([129.240.186.42])
	by goggins.uio.no with esmtp (Exim 2.12 #7)
	id 19KOYs-0007jb-00; Mon, 26 May 2003 22:27:14 +0200
Received: from hbf by bombur.uio.no with local (Exim 2.12 #7)
	id 19KOYs-00018z-00; Mon, 26 May 2003 22:27:14 +0200
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Message-Id: <HBF.20030526re7t@bombur.uio.no>
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Cc: Michael =?iso-8859-1?Q?Str=F6der?= <michael@stroeder.com>,
        ietf-ldapbis@OpenLDAP.org
Subject: Re: IETF ldapbis WG Last Call: 
  draft-ietf-ldapbis-user-schema-05.txt
In-Reply-To: <5.2.0.9.0.20030526125326.0293ac10@127.0.0.1>
References: <5.2.0.9.0.20030523163225.0278b740@127.0.0.1>
	<3ED26DAD.4050705@stroeder.com>
	<5.2.0.9.0.20030526125326.0293ac10@127.0.0.1>
X-Mailer: VM 6.37 under Emacs 19.34.1
Date: Mon, 26 May 2003 22:27:14 +0200
X-MailScanner-Information: Please contact postmaster@uio.no for more information
X-UiO-MailScanner: Found to be clean
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:
>>"Add: Use of integrity protection is encouraged to prevent session hijacking."
>>
>>Which session is meant here?
> 
> The LDAP session.
> 
> If one uses a mechanism such as DIGEST-MD5 without
> negotiating integrity protection to authenticate,
> a man-in-middle can hijack the session after
> authentication completes. 

What has that to do with schema?  Sounds like a protocol or authmeth
issue to me.

I'd also like to see this paragraph removed:

   It is required that strong authentication be performed in order to 
   modify directory entries using LDAP.

for the same reason.  I've mentioned that before, IIRC the answer was
that yes, it's covered elsewere - but not as a requirement.  I can't
find the thread now, though.

-- 
Hallvard


From owner-ietf-ldapbis@OpenLDAP.org  Mon May 26 16:53: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 QAA26667
	for <ldapbis-archive@lists.ietf.org>; Mon, 26 May 2003 16:53: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 h4QKq8El001700;
	Mon, 26 May 2003 20:52: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 h4QKkPGf001569;
	Mon, 26 May 2003 20:46:25 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 26 May 2003 20:46:25 +0000
Received: from nb2.stroeder.com (krl9-d9bb4cbc.pool.mediaWays.net [217.187.76.188])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4QKkMEh001525;
	Mon, 26 May 2003 20:46:22 GMT
	(envelope-from michael@stroeder.com)
Received: from localhost (localhost.stroeder.com [127.0.0.1])
	by nb2.stroeder.com (Postfix) with ESMTP
	id 3879E555C2; Mon, 26 May 2003 22:45:53 +0200 (CEST)
Received: from stroeder.com (localhost.stroeder.com [127.0.0.1])
	by nb2.stroeder.com (Postfix) with ESMTP
	id 76F964AF32; Mon, 26 May 2003 22:45:52 +0200 (CEST)
Message-ID: <3ED27D00.6030005@stroeder.com>
Date: Mon, 26 May 2003 22:45:52 +0200
From: =?ISO-8859-1?Q?Michael_Str=F6der?= <michael@stroeder.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3.1) Gecko/20030425
X-Accept-Language: de-de, de, en-us, en
MIME-Version: 1.0
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Cc: ietf-ldapbis@OpenLDAP.org
Subject: Re: IETF ldapbis WG Last Call:   draft-ietf-ldapbis-user-schema-05.txt
References: <5.2.0.9.0.20030523163225.0278b740@127.0.0.1> <5.2.0.9.0.20030523163225.0278b740@127.0.0.1> <5.2.0.9.0.20030526125326.0293ac10@127.0.0.1>
In-Reply-To: <5.2.0.9.0.20030526125326.0293ac10@127.0.0.1>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
X-Virus-Scanned: by AMaViS 0.3.12pre8
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by boole.openldap.org id h4QKkMEh001540
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 D. Zeilenga wrote:
> At 12:40 PM 5/26/2003, Michael Ströder wrote:
> 
>>Kurt D. Zeilenga wrote:
>>
>>>KurtZ raised a security consideration regarding session hijacking.
>>>Add consideration.
>>
>>???
>>"Add: Use of integrity protection is encouraged to prevent session hijacking."
>>
>>Which session is meant here?
> 
> The LDAP session.
> 
> If one uses a mechanism such as DIGEST-MD5 without
> negotiating integrity protection to authenticate,
> a man-in-middle can hijack the session after
> authentication completes. 

Does that really belong into draft-ietf-ldapbis-user-schema?
How does that relate to the schema definitions?

I can understand that one emphasizes security for e.g. userPassword (could 
be added to section 'Security Considerations', generalized and extended). 
But IMHO LDAP session security is out of scope in this document.

Ciao, Michael.




From owner-ietf-ldapbis@OpenLDAP.org  Tue May 27 00:27:47 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 AAA13913
	for <ldapbis-archive@lists.ietf.org>; Tue, 27 May 2003 00:27:47 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4R4MBEl011643;
	Tue, 27 May 2003 04:25:57 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 h4R4JuNX011533;
	Tue, 27 May 2003 04:19:56 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 27 May 2003 04:19:56 +0000
Received: from ausyms50.ca.com ([155.35.248.106])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4R4JqEh011493;
	Tue, 27 May 2003 04:19:53 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, 27 May 2003 14:19:31 +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: IETF ldapbis WG Last Call:  draft-ietf-ldapbis-user-schema-05.txt
Date: Tue, 27 May 2003 14:19:30 +1000
Message-ID: <1395B4B334FCC143B36AF788E68B63811E3CC2@ausyms21.ca.com>
Thread-Topic: IETF ldapbis WG Last Call:  draft-ietf-ldapbis-user-schema-05.txt
Thread-Index: AcMjt/pDnoHHVcrUSV6XGEECdI0aOAATraNQ
From: "Ramsay, Ron" <Ron.Ramsay@ca.com>
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>, <ietf-ldapbis@OpenLDAP.org>
X-OriginalArrivalTime: 27 May 2003 04:19:31.0022 (UTC) FILETIME=[2B8826E0:01C32407]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by boole.openldap.org id h4R4JrEh011504
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 with the resolutions, except for passwords. For passwords, I agree that there was WG consensus. My own opinion, however, is that these are octet strings and that a password matches only if the sequence of octets is the same.

I think I have only seen about five names in messages to the list - is this enough to declare consensus?

Ron

-----Original Message-----
From: Kurt D. Zeilenga [mailto:Kurt@OpenLDAP.org]
Sent: Tuesday, 27 May 2003 04:41
To: ietf-ldapbis@OpenLDAP.org
Subject: Re: IETF ldapbis WG Last Call:
draft-ietf-ldapbis-user-schema-05.txt


This message serves to summarize issues to be addressed
before this I-D is progressed.  For each issue, I have suggested
a course of action which I believe to be consistent with WG
consensus.  If you don't believe the this course of action
is appropriate, please comment within the next couple of days.
Otherwise, the chairs will declare these issues resolved and
direct the editor to revise the document accordingly.

KurtZ raised concerns regarding the ommission of an 'uid' attribute
type specification.  He made a proposal to add it.  No one opposed
this proposal, implement it.

MarkH raised concerns regarding suggested upper limits.
StevenL proposed that all suggested upper limits be removed
to avoid confusion.  No one opposed this proposal, implement it.

KurtZ raised concerns regarding internationalization of textual
user passwords.  Kurt proposed that it be recommended that applications
prepare textural passwords by first transcoding them to Unicode,
apply SASLprep, and then encoding them as UTF-8.  Hallvard offered
some word smithing which was found acceptable.  No one opposed this
proposal, implement it.

NorbertK raised concerns regarding alternative names used for
in some implementations which do not appear in the attribute
type's formal description and suggested they be added.  Objections
to the proposal were raised.  The proposal is rejected.

KurtZ provided a laundry list of issues.  For brevity, I will
only summarize technical issues.  There were no opposing comments
to any of his proposals.

KurtZ noted that most attribute types are discussed in single
value terms though are declared as multiple values.  Kurt
proposed that the editor reword each description to reflect
their multi-valued-ness.  Clarify.

KurtZ noted that the description of 'dc' is needs further
clarification.  Clarify as noted.

KurtZ noted 'destinationIndicator' specification does not
include a statement of how the attribute type is used.  Clarify.

KurtZ noted the description of 'givenName' is inconsistent
with that provided in X.520.  Clarify.

KurtZ proposed that the 'domain' object class should not have
been added to the specification.  Remove.

KurtZ raised a security consideration regarding session hijacking.
Add consideration.






From owner-ietf-ldapbis@OpenLDAP.org  Tue May 27 03:01: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 DAA00150
	for <ldapbis-archive@lists.ietf.org>; Tue, 27 May 2003 03:01: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 h4R6wGEp023906;
	Tue, 27 May 2003 07:00: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 h4R6w5ul023859;
	Tue, 27 May 2003 06:58:05 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 27 May 2003 06:58:05 +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 h4R6w4Eh023849
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 27 May 2003 06:58:04 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 h4R6w1c6013575;
	Tue, 27 May 2003 06:58:01 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030526211940.0297fe10@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Mon, 26 May 2003 23:55:11 -0700
To: "Ramsay, Ron" <Ron.Ramsay@ca.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: RE: IETF ldapbis WG Last Call: 
  draft-ietf-ldapbis-user-schema-05.txt
Cc: <ietf-ldapbis@OpenLDAP.org>
In-Reply-To: <1395B4B334FCC143B36AF788E68B63811E3CC2@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 09:19 PM 5/26/2003, Ramsay, Ron wrote:
>I agree with the resolutions, except for passwords. For passwords, I agree that there was WG consensus.

Noted.

>My own opinion, however, is that these are octet strings and that a password matches only if the sequence of octets is the same.

I note that the requirement is applied by applications on input
to the directory.  To the directory service, they are still
octets strings matched octet-wise.

>I think I have only seen about five names in messages to the list - is this enough to declare consensus?

All the input was enough to gain a good sense of WG consensus
and to suggest courses of action for the WG to consider.
We'll have to wait a few days to see whether we really
have consensus or not.

Kurt




From owner-ietf-ldapbis@OpenLDAP.org  Tue May 27 03:01:46 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 DAA00189
	for <ldapbis-archive@lists.ietf.org>; Tue, 27 May 2003 03:01: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 h4R6wGEr023906;
	Tue, 27 May 2003 07:00: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 h4R6sEoB023570;
	Tue, 27 May 2003 06:54:14 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 27 May 2003 06:54:14 +0000
Received: from nb2.stroeder.com (krl9-d9bb4e37.pool.mediaWays.net [217.187.78.55])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4R6sCEh023532
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 27 May 2003 06:54:12 GMT
	(envelope-from michael@stroeder.com)
Received: from localhost (localhost.stroeder.com [127.0.0.1])
	by nb2.stroeder.com (Postfix) with ESMTP
	id DA2CA59BAE; Tue, 27 May 2003 08:53:47 +0200 (CEST)
Received: from stroeder.com (localhost.stroeder.com [127.0.0.1])
	by nb2.stroeder.com (Postfix) with ESMTP
	id 44D2A59B75; Tue, 27 May 2003 08:53:47 +0200 (CEST)
Message-ID: <3ED30B7B.9080707@stroeder.com>
Date: Tue, 27 May 2003 08:53:47 +0200
From: =?ISO-8859-1?Q?Michael_Str=F6der?= <michael@stroeder.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3.1) Gecko/20030425
X-Accept-Language: de-de, de, en-us, en
MIME-Version: 1.0
To: "Ramsay, Ron" <Ron.Ramsay@ca.com>
Cc: ietf-ldapbis@OpenLDAP.org
Subject: Re: IETF ldapbis WG Last Call:  draft-ietf-ldapbis-user-schema-05.txt
References: <1395B4B334FCC143B36AF788E68B63811E3CC2@ausyms21.ca.com>
In-Reply-To: <1395B4B334FCC143B36AF788E68B63811E3CC2@ausyms21.ca.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by AMaViS 0.3.12pre8
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 agree with the resolutions, except for passwords. For passwords, I
> agree that there was WG consensus. My own opinion, however, is that these
> are octet strings and that a password matches only if the sequence of
> octets is the same.

There was consensus that octet string matching of passwords will not be 
changed to ensure compability with implementations using some kind of local 
definition. But to solve current interoperability issues it is very 
important to recommend a character set/encoding (here UTF-8) for *textual* 
passwords sent by the LDAP client.

There was a thread on this list quite a while ago with subject
"Revisited: NON-ASCII chars in userPassword" started 2001-10-29.

Ciao, Michael.



From owner-ietf-ldapbis@OpenLDAP.org  Tue May 27 03:11:14 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 DAA00627
	for <ldapbis-archive@lists.ietf.org>; Tue, 27 May 2003 03:11:13 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4R7ABEl025020;
	Tue, 27 May 2003 07:10:14 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 h4R76dCX024772;
	Tue, 27 May 2003 07:06:39 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 27 May 2003 07:06:39 +0000
Received: from ausyms50.ca.com ([155.35.248.106])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4R76LEh024706;
	Tue, 27 May 2003 07:06:21 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, 27 May 2003 17:06: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: IETF ldapbis WG Last Call:   draft-ietf-ldapbis-user-schema-05.txt
Date: Tue, 27 May 2003 17:05:59 +1000
Message-ID: <1395B4B334FCC143B36AF788E68B63811E3F7C@ausyms21.ca.com>
Thread-Topic: IETF ldapbis WG Last Call:   draft-ietf-ldapbis-user-schema-05.txt
Thread-Index: AcMkHVSjnsSItcy9RaOe0/YfidfPrAAANwaQ
From: "Ramsay, Ron" <Ron.Ramsay@ca.com>
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Cc: <ietf-ldapbis@OpenLDAP.org>
X-OriginalArrivalTime: 27 May 2003 07:06:00.0110 (UTC) FILETIME=[6D7E04E0:01C3241E]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by boole.openldap.org id h4R76MEh024730
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 note that the requirement is applied by applications on input
to the directory.  To the directory service, they are still
octets strings matched octet-wise."

- Sounds good to me! Thanks for the clarification.

Ron

-----Original Message-----
From: Kurt D. Zeilenga [mailto:Kurt@OpenLDAP.org]
Sent: Tuesday, 27 May 2003 16:55
To: Ramsay, Ron
Cc: ietf-ldapbis@OpenLDAP.org
Subject: RE: IETF ldapbis WG Last Call:
draft-ietf-ldapbis-user-schema-05.txt


At 09:19 PM 5/26/2003, Ramsay, Ron wrote:
>I agree with the resolutions, except for passwords. For passwords, I agree that there was WG consensus.

Noted.

>My own opinion, however, is that these are octet strings and that a password matches only if the sequence of octets is the same.

I note that the requirement is applied by applications on input
to the directory.  To the directory service, they are still
octets strings matched octet-wise.

>I think I have only seen about five names in messages to the list - is this enough to declare consensus?

All the input was enough to gain a good sense of WG consensus
and to suggest courses of action for the WG to consider.
We'll have to wait a few days to see whether we really
have consensus or not.

Kurt






From owner-ietf-ldapbis@OpenLDAP.org  Tue May 27 04:09: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 EAA03486
	for <ldapbis-archive@lists.ietf.org>; Tue, 27 May 2003 04:09:28 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4R7wCFR027312;
	Tue, 27 May 2003 08:07:45 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 h4R7urBp027279;
	Tue, 27 May 2003 07:56:53 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 27 May 2003 07:56:53 +0000
Received: from nb2.stroeder.com (krl9-d9bb4e37.pool.mediaWays.net [217.187.78.55])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4R7ulEh027262
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 27 May 2003 07:56:51 GMT
	(envelope-from michael@stroeder.com)
Received: from localhost (localhost.stroeder.com [127.0.0.1])
	by nb2.stroeder.com (Postfix) with ESMTP
	id B2EAE59BB5; Tue, 27 May 2003 09:56:23 +0200 (CEST)
Received: from stroeder.com (localhost.stroeder.com [127.0.0.1])
	by nb2.stroeder.com (Postfix) with ESMTP
	id 01C7159228; Tue, 27 May 2003 09:56:22 +0200 (CEST)
Message-ID: <3ED31A26.9020608@stroeder.com>
Date: Tue, 27 May 2003 09:56:22 +0200
From: =?ISO-8859-1?Q?Michael_Str=F6der?= <michael@stroeder.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3.1) Gecko/20030425
X-Accept-Language: de-de, de, en-us, en
MIME-Version: 1.0
To: "Ramsay, Ron" <Ron.Ramsay@ca.com>
Cc: ietf-ldapbis@OpenLDAP.org
Subject: Re: IETF ldapbis WG Last Call:  draft-ietf-ldapbis-user-schema-05.txt
References: <1395B4B334FCC143B36AF788E68B63811E3F6E@ausyms21.ca.com>
In-Reply-To: <1395B4B334FCC143B36AF788E68B63811E3F6E@ausyms21.ca.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by AMaViS 0.3.12pre8
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:
> Yes, thanks, I did see the discussion. I am just saying that I wasn't
> moved by it. I don't see how you can actually talk meaningfully about
> 'textual' passwords

I would define 'textual' passwords as passwords manually typed in by a user
on the keyboard or a similar character-based input device. More formally one
could define textual passwords as a character sequence with a known
character set and encoding.

As current practical experience shows arguing that you can stuff anything
(here an arbitrary character sequence and encoding) into an Octet String
leads to bad interoperability of LDAP applications.

At the moment the only almost safe way is to limit passwords to ASCII since
ISO-8859-1 and UTF-8 both used by some applications share the very same byte
encoding for ASCII. But there might be users who don't have a single ASCII
character on their input device...and there might be an application stuffing
UTF-16 into the password.

> - do you scan a password first to see if it is valid
> UTF-8 and, if so, convert it to unicode and apply stringprep?

No, off course!

Usually you can differentiate in the LDAP application where your password 
comes from. Most times the application receives the password from the user 
by some input device/input form etc. And then you know which character set 
it is and you can easily convert it to UTF-8.

> I can't get excited about that.

Let us clarify things:
Octet Strings for passwords are used because there could be a "locally 
defined" mechanism for using arbitrary Octet Strings in Simple Bind (e.g. 
automatically generated tickets, scanned mouse moves, biometric data or 
similar). In this scenario an LDAP application will likely not interact with 
a human user through a keyboard to ask for a password. This is still 
possible with Kurt's recommendation.

Ciao, Michael.



From owner-ietf-ldapbis@OpenLDAP.org  Tue May 27 04:47: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 ESMTP id EAA04634
	for <ldapbis-archive@lists.ietf.org>; Tue, 27 May 2003 04:47:28 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4R8kCEl032136;
	Tue, 27 May 2003 08:46:22 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 h4R8i1m0032064;
	Tue, 27 May 2003 08:44:01 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 27 May 2003 08:44:01 +0000
Received: from nb2.stroeder.com (krl9-d9bb4e37.pool.mediaWays.net [217.187.78.55])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4R8hsEh032008;
	Tue, 27 May 2003 08:43:58 GMT
	(envelope-from michael@stroeder.com)
Received: from localhost (localhost.stroeder.com [127.0.0.1])
	by nb2.stroeder.com (Postfix) with ESMTP
	id 584BC59BBB; Tue, 27 May 2003 10:43:29 +0200 (CEST)
Received: from stroeder.com (localhost.stroeder.com [127.0.0.1])
	by nb2.stroeder.com (Postfix) with ESMTP
	id 99BDA555C0; Tue, 27 May 2003 10:43:28 +0200 (CEST)
Message-ID: <3ED32530.40009@stroeder.com>
Date: Tue, 27 May 2003 10:43:28 +0200
From: =?ISO-8859-1?Q?Michael_Str=F6der?= <michael@stroeder.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3.1) Gecko/20030425
X-Accept-Language: de-de, de, en-us, en
MIME-Version: 1.0
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Cc: ietf-ldapbis@OpenLDAP.org
Subject: multi-valued userPassword (was: IETF ldapbis WG Last Call:  draft-ietf-ldapbis-user-schema-05.txt)
References: <5.2.0.9.0.20030523163225.0278b740@127.0.0.1>
In-Reply-To: <5.2.0.9.0.20030523163225.0278b740@127.0.0.1>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by AMaViS 0.3.12pre8
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

HI!

Another issue:
Any reasonable *and* secure use-case for having multi-valued userPassword?

Maybe it's worth to note in section 'Security Considerations' that multiple 
attribute values for userPassword should be avoided. Especially 
reset/deletion of a password by an admin without knowing the old user 
password gets tricky or impossible if multiple values for different 
applications are present. This also somewhat relates to a similar discussion 
on ldap-ext list about possibly multi-valued attributes in 
draft-behera-ldap-password-policy.

The only use-case I could imagine for having multiple userPassword attribute 
values was working around the Octet String problem storing the *same* 
password with various character sets/encodings.

Ciao, Michael.




From owner-ietf-ldapbis@OpenLDAP.org  Tue May 27 11:15:01 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 LAA16249
	for <ldapbis-archive@lists.ietf.org>; Tue, 27 May 2003 11:15:00 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4RFAEEl062465;
	Tue, 27 May 2003 15:13:54 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 h4RF5EUM062034;
	Tue, 27 May 2003 15:05:14 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 27 May 2003 15:05:14 +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 h4RF4iEh062002
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 27 May 2003 15:04:45 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 h4RF4hc6016424;
	Tue, 27 May 2003 15:04:44 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030527071114.029394a0@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Tue, 27 May 2003 08:01:52 -0700
To: Michael =?iso-8859-1?Q?Str=F6der?= <michael@stroeder.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: multi-valued userPassword (was: IETF ldapbis WG Last Call:
   draft-ietf-ldapbis-user-schema-05.txt)
Cc: ietf-ldapbis@OpenLDAP.org
In-Reply-To: <3ED32530.40009@stroeder.com>
References: <5.2.0.9.0.20030523163225.0278b740@127.0.0.1>
 <5.2.0.9.0.20030523163225.0278b740@127.0.0.1>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by boole.openldap.org id h4RF4jEh062003
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

At 01:43 AM 5/27/2003, Michael Ströder wrote:
>Another issue:
>Any reasonable *and* secure use-case for having multi-valued userPassword?

Yes.  Consider an environment where every month the user was expected
to use a different password generated by some automated system.  During
transitional periods, like say the last and first day of the periods, it
may be reasonable to allow two passwords for the two consecutive periods
to be valid in the system.

>Maybe it's worth to note in section 'Security Considerations' that multiple attribute values for userPassword should be avoided. Especially reset/deletion of a password by an admin without knowing the old user password gets tricky or impossible if multiple values for different applications are present. This also somewhat relates to a similar discussion on ldap-ext list about possibly multi-valued attributes in draft-behera-ldap-password-policy.

First, I note that the descriptive text in section 2.40 (as well as most every
other 2.x section) needs to be updated to describe the attribute type in
multi-valued terms.  It should be noted that when used for authentication
purposes [AuthMeth], the user need only prove she knows one of the values, not
all of the values.

Allowing multiple values obviously does raise a number of security considerations
and these need to be discussed in the document.

Certainly applications which intend to replace the userPassword with new value(s)
should use modify/replaceValues (or modify/deleteAttribute+addAttribute).
Additionally, server implementations should be encouraged to provide
administrative controls which, if enabled, restrict userPassword to one value.

>The only use-case I could imagine for having multiple userPassword attribute values was working around the Octet String problem storing the *same* password with various character sets/encodings.

Supporting legacy systems would be another reason. 




From owner-ietf-ldapbis@OpenLDAP.org  Tue May 27 17:24:30 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 RAA03094
	for <ldapbis-archive@lists.ietf.org>; Tue, 27 May 2003 17:24:29 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4RLGGEt090398;
	Tue, 27 May 2003 21:23: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 h4RLCoDP090051;
	Tue, 27 May 2003 21:12:50 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 27 May 2003 21:12:50 +0000
Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4RLCnEh090038
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 27 May 2003 21:12:49 GMT
	(envelope-from rlmorgan@washington.edu)
Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9])
	by mxout4.cac.washington.edu (8.12.1+UW03.04/8.12.1+UW02.12) with ESMTP id h4RLCmTc009800
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 27 May 2003 14:12:48 -0700
Received: from D-140-142-21-8.dhcp4.washington.edu (D-140-142-21-8.dhcp4.washington.edu [140.142.21.8])
	(authenticated bits=0)
	by smtp.washington.edu (8.12.1+UW03.04/8.12.1+UW02.12) with ESMTP id h4RLCmcx012628
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT)
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 27 May 2003 14:12:48 -0700
Date: Tue, 27 May 2003 14:12:49 -0700 (PDT)
From: "RL 'Bob' Morgan" <rlmorgan@washington.edu>
X-X-Sender: rlmorgan@localhost.localdomain
To: IETF ldapbis WG <ietf-ldapbis@OpenLDAP.org>
Subject: ldapbis WG last call on draft-ietf-ldapbis-dn-10.txt
Message-ID: <Pine.LNX.4.44.0305271355370.6217-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>


This message initiates a LDAPbis Working Group Last Call on the
document:

      LDAP: String Representation of Distinguished Names
             <draft-ietf-ldapbis-dn-10.txt>
                      4 May 2003

The purpose of this WG Last Call it to ensure that the Working Group has
achieved consensus that the document is suitable for publication as an
IETF Draft Standard.

Please review the document for both technical and editorial problems.
Technical issues should be discussed on this list.  Editorial issues may
be sent to the document editor.

(Let me point out that a previous version of this document went through WG
last call quite a while ago.  Subsequently the "short names registry"
issue was reopened.  The current version of this document reflects
apparent current WG consensus to support a registry approach; see section
2.3.  This Last Call is intended to confirm this consensus as well as
solicit any other review.)

The Last Call period will end on Friday, June 13, 2003.

Upon completion of the last call, the WG chair(s) will take action based
upon the consensus of the WG.  Possible actions include:

  1) recommending to the IETF Application Area Directors that the
     document, after possible editorial or other minor changes, be
     considered by the IESG for publication as a Draft Standard
     (which generally involves an IETF-wide Last Call); or

  2) requiring that outstanding issues be adequately addressed prior
     to further action (including, possibly, another Last Call).

Remember that it is our responsibility as Working Group members to
ensure the quality of our documents and of the Internet Standards
process.  So, please read and comment!

 - RL "Bob" Morgan
   LDAPbis co-chair




From owner-ietf-ldapbis@OpenLDAP.org  Wed May 28 07:48: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 HAA25938
	for <ldapbis-archive@lists.ietf.org>; Wed, 28 May 2003 07:48: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 h4SBkLEl062038;
	Wed, 28 May 2003 11:47: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 h4SBjrdi062008;
	Wed, 28 May 2003 11:45:53 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 28 May 2003 11:45:53 +0000
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4SBjpEh061998
	for <ietf-ldapbis@openldap.org>; Wed, 28 May 2003 11:45:52 GMT
	(envelope-from nsyracus@cnri.reston.va.us)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA25606;
	Wed, 28 May 2003 07:45:50 -0400 (EDT)
Message-Id: <200305281145.HAA25606@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: ietf-ldapbis@OpenLDAP.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-ldapbis-strprep-00.txt
Date: Wed, 28 May 2003 07:45:50 -0400
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>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the LDAP (v3) Revision Working Group of the IETF.

	Title		: LDAP: Internationalized String Preparation
	Author(s)	: K. Zeilenga
	Filename	: draft-ietf-ldapbis-strprep-00.txt
	Pages		: 17
	Date		: 2003-5-27
	
The previous Lightweight Directory Access Protocol (LDAP) technical
specifications did not precisely define how string matching is to be
performed.  This lead to a number of usability and interoperability
problems.  This document defines string preparation algorithms for
matching rules defined for use in LDAP.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ldapbis-strprep-00.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-ldapbis-strprep-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-ldapbis-strprep-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2003-5-27145326.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ldapbis-strprep-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-ldapbis-strprep-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-5-27145326.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-ietf-ldapbis@OpenLDAP.org  Wed May 28 21:36:51 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 VAA02327
	for <ldapbis-archive@lists.ietf.org>; Wed, 28 May 2003 21:36:50 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4T1YQEl013578;
	Thu, 29 May 2003 01:35:12 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 h4T1Wr1k013547;
	Thu, 29 May 2003 01:32:53 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 29 May 2003 01:32:53 +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 h4T1WkEh013537
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 29 May 2003 01:32:52 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 h4T1Wkc6032633
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 29 May 2003 01:32:46 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030528181142.02aa2dc8@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Wed, 28 May 2003 18:29:53 -0700
To: ietf-ldapbis@OpenLDAP.org
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: IETF ldapbis WG Last Call:
  draft-ietf-ldapbis-user-schema-05.txt
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 have directed the editor to prepare a revision addressing
outstanding technical issues as previously summarized with
excepted noted below.  Once published, I will ask the WG to
confirm that the changes made adequately address these issues.
Presently, I do not think another WG Last Call will be necessary
as I believe I believe we have WG (good to rough) consensus
on how to resolve outstanding issues, however I will defer
this decision until after the editor has made the changes and
the WG has had an opportunity to consider those changes.

While waiting for the editor to make these changes, I suggest we
turn our energy to reviewing the [Protocol] and [AuthMeth] I-Ds.

-- Kurt, LDAPbis co-chair

At 11:41 AM 5/26/2003, Kurt D. Zeilenga wrote:
>This message serves to summarize issues to be addressed
>before this I-D is progressed.  For each issue, I have suggested
>a course of action which I believe to be consistent with WG
>consensus.  If you don't believe the this course of action
>is appropriate, please comment within the next couple of days.
>Otherwise, the chairs will declare these issues resolved and
>direct the editor to revise the document accordingly.
>
>KurtZ raised concerns regarding the ommission of an 'uid' attribute
>type specification.  He made a proposal to add it.  No one opposed
>this proposal, implement it.
>
>MarkH raised concerns regarding suggested upper limits.
>StevenL proposed that all suggested upper limits be removed
>to avoid confusion.  No one opposed this proposal, implement it.
>
>KurtZ raised concerns regarding internationalization of textual
>user passwords.  Kurt proposed that it be recommended that applications
>prepare textural passwords by first transcoding them to Unicode,
>apply SASLprep, and then encoding them as UTF-8.  Hallvard offered
>some word smithing which was found acceptable.  No one opposed this
>proposal, implement it.
>
>NorbertK raised concerns regarding alternative names used for
>in some implementations which do not appear in the attribute
>type's formal description and suggested they be added.  Objections
>to the proposal were raised.  The proposal is rejected.
>
>KurtZ provided a laundry list of issues.  For brevity, I will
>only summarize technical issues.  There were no opposing comments
>to any of his proposals.
>
>KurtZ noted that most attribute types are discussed in single
>value terms though are declared as multiple values.  Kurt
>proposed that the editor reword each description to reflect
>their multi-valued-ness.  Clarify.
>
>KurtZ noted that the description of 'dc' is needs further
>clarification.  Clarify as noted.
>
>KurtZ noted 'destinationIndicator' specification does not
>include a statement of how the attribute type is used.  Clarify.
>
>KurtZ noted the description of 'givenName' is inconsistent
>with that provided in X.520.  Clarify.
>
>KurtZ proposed that the 'domain' object class should not have
>been added to the specification.  Remove.
>
>KurtZ raised a security consideration regarding session hijacking.
>Add consideration.

MichaelS and HallvardF noted that this was misplaced (belongs in
[Protocol] and/or [AuthMeth]).  The editor should not added
this consideration.

HallvardF noted the statement
   It is required that strong authentication be performed in order to 
   modify directory entries using LDAP.
is also misplaced (also belongs in [Protocol] and/or [AuthMeth]).
The editor should remove this statement.

MichaelS raised an issue with multi-valued userPasswords.  Kurt
suggested considerations be stated.  The editor should add
appropriate considerations.





From owner-ietf-ldapbis@OpenLDAP.org  Fri May 30 10:34:00 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 KAA10558
	for <ldapbis-archive@lists.ietf.org>; Fri, 30 May 2003 10:33: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 h4UEAcF7010308;
	Fri, 30 May 2003 14:26:52 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 h4UE933W010194;
	Fri, 30 May 2003 14:09:03 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Fri, 30 May 2003 14:09:03 +0000
Received: from netscape.com (c3po.aoltw.net [64.236.137.25])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4UE92Eh010150
	for <ietf-ldapbis@OpenLDAP.org>; Fri, 30 May 2003 14:09:02 GMT
	(envelope-from mcs@netscape.com)
Received: from judge.mcom.com (judge.nscp.aoltw.net [10.169.8.47])
	by netscape.com (8.10.0/8.10.0) with ESMTP id h4UE8Zn01863
	for <ietf-ldapbis@OpenLDAP.org>; Fri, 30 May 2003 07:08:35 -0700 (PDT)
Received: from netscape.com ([10.169.192.42]) by judge.mcom.com
          (Netscape Messaging Server 4.15) with ESMTP id HFPDYB01.6AL;
          Fri, 30 May 2003 07:08:35 -0700 
Message-ID: <3ED765E2.4060800@netscape.com>
Date: Fri, 30 May 2003 10:08:34 -0400
From: mcs@netscape.com (Mark C Smith)
Organization: Netscape Communications Corp.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030428 Netscape/7.02+
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Ramsay Ron" <Ron.Ramsay@ca.com>
CC: Vithalprasad Gaitonde <gvithalprasad@novell.com>,
        ietf-ldapbis@OpenLDAP.org
Subject: Re: Example in draft-ietf-ldapbis-url-03.txt
References: <1395B4B334FCC143B36AF788E68B63811A63B9@ausyms21.ca.com>
In-Reply-To: <1395B4B334FCC143B36AF788E68B63811A63B9@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

I don't think I responded to this... 'oct' is a little obscure, but your 
point is well taken. I view "binary" as a very general term, but it does 
carry some historical baggage from the LDAP point of view. Perhaps:

     (four-octet-attr=\00\00\00\04)

:)

-Mark


Ramsay, Ron wrote:
> It's not really a good idea. Binary attributes should be encoded in
 > ASN.1 and this one clearly isn't! What about using 'oct', say.
> 
> -----Original Message-----
> From: Mark C Smith [mailto:mcs@netscape.com]
> Sent: Friday, 23 May 2003 02:36
> To: Vithalprasad Gaitonde
> Cc: ietf-ldapbis@OpenLDAP.org
> Subject: Re: Example in draft-ietf-ldapbis-url-03.txt
> 
> 
> Vithalprasad Gaitonde wrote:
> 
>>Section 7 of this document gives an example of (int=\00\00\00\04) and
>>shows hot the LDAP URL representation for the same.
>>The use of "int" seems to indicate here that its an integer attribute
>>which is being talked about. Its unlikely that an integer syntax
>>attribute will encoded like this.
>>Though its not technically incorrect, for better readability sake,
>>would it be a good idea to choose some other attribute name than "int"
>>like bin (bin=\00\00\00\04) as in section 7 of
>>draft-ietf-ldapbis-filter-04.txt.
> 
> 
> OK, this is a good suggestion.
> 



From owner-ietf-ldapbis@OpenLDAP.org  Fri May 30 18:12: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 SAA01094
	for <ldapbis-archive@lists.ietf.org>; Fri, 30 May 2003 18:12: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 h4UMAeEl045523;
	Fri, 30 May 2003 22:11:12 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 h4UM6C7k045406;
	Fri, 30 May 2003 22:06:12 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Fri, 30 May 2003 22:06:12 +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 h4UM66Eh045396
	for <ietf-ldapbis@OpenLDAP.org>; Fri, 30 May 2003 22:06:11 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 h4UM65c6049389
	for <ietf-ldapbis@OpenLDAP.org>; Fri, 30 May 2003 22:06:05 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030530145501.02a00428@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Fri, 30 May 2003 15:03:11 -0700
To: ietf-ldapbis@OpenLDAP.org
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Protocol and AuthMeth drafts
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>

We really need to focus some review energy on these two drafts.
I'd like for the next revisions, to be produced before the
IETF#57 cut-offs, to be suitable for WG Last Call.  So that
the editor has sufficient time to make appropriate changes,
we need to review and comment within the next few weeks.  So,
please, review and comment now.

Kurt



