From owner-ietf-ldapbis@OpenLDAP.org  Wed Oct  1 12: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 MAA23299
	for <ldapbis-archive@lists.ietf.org>; Wed, 1 Oct 2003 12:54:25 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h91Gi5jq019718;
	Wed, 1 Oct 2003 16:52: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 h91GfJkt019601;
	Wed, 1 Oct 2003 16:41:19 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 1 Oct 2003 16:41:19 +0000
Received: from pat.uio.no (IDENT:7411@pat.uio.no [129.240.130.16])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h91GfEj2019569;
	Wed, 1 Oct 2003 16:41:15 GMT
	(envelope-from hbf@bombur.uio.no)
Received: from mail-mx4.uio.no ([129.240.10.45])
	by pat.uio.no with esmtp (Exim 4.20)
	id 1A4k2J-0003xW-8t; Wed, 01 Oct 2003 18:41:11 +0200
Received: from bombur.uio.no ([129.240.186.42])
	by mail-mx4.uio.no with esmtp (Exim 4.14)
	id 1A4k2G-0002fw-Bt; Wed, 01 Oct 2003 18:41:08 +0200
Received: from hbf by bombur.uio.no with local (Exim 2.12 #7)
	id 1A4k2G-0004fM-00; Wed, 1 Oct 2003 18:41:08 +0200
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Message-Id: <HBF.20031001hh9u@bombur.uio.no>
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Cc: ietf-ldapbis@OpenLDAP.org
Subject: Re: more SASLprep/protocol problems
In-Reply-To: <6.0.0.22.0.20030924062136.03b79fc0@127.0.0.1>
References: <HBF.20030923u8q1@bombur.uio.no>
	<6.0.0.22.0.20030924062136.03b79fc0@127.0.0.1>
X-Mailer: VM 6.37 under Emacs 19.34.1
Date: Wed, 1 Oct 2003 18:41:08 +0200
X-MailScanner-Information: This message has been scanned for viruses/spam. Contact postmaster@uio.no if you have questions about this scanning.
X-UiO-MailScanner: No virus found
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

Kurt D. Zeilenga writes:

> I think here are opposing objectives.   One fraction of the
> community is attempting to improve interoperability between
> independently developed implementations.  One faction is
> attempting to support legacy systems.

Are there some implementations that do prepare passwords, or at least
translate them to UTF-8, and are widely used on non-ASCII or ASCII-
superset sites with hashed passwords, and thus prove that the problem
is smaller than I think?

> (Note: It is possible to split the preparation between the client
> and the server, PLAIN does this (client handles transcoding
> to Unicode and UTF-8 encoding, server handles SASLprep).  With
> LDAP, this is not a good option as the server has no way to
> determine whether the password is textual or not.)

I've seldom wondered about so many things in so short a statement:-)

What do you mean by textual and non-textual passwords, exactly?

Why are PLAIN passwords more textual than LDAP passwords?  Is it simply
because PLAIN _requires_ passwords to be UTF-8 which is presumably text,
while LDAP only will recommend it?

If the server and therefore the sysadmin doesn't know whether to prepare
a bind password or not, how is the client supposed to know - unless the
user tells it?

Which scenario are you thinking of when you say the server doesn't know?
Not that I disagree that client-side preparation is most flexible,
but... usually all passwords will be UTF-8 or none of them will,
depending on how the sysadmin put them there, so the server will know.
OTOH, the server won't know if they should be prepared if the users
stored userPasswords as they pleased, both UTF-8 and non-UTF-8.  But
then you _really_ need a client option to say whether or not to prepare
bind passwords, so I don't suppose that's what you are talking about...
(Hey! That's another argument for recommending that client option!:-)

> How's this?
>
>      The simple form of an AuthenticationChoice specifies a simple
>      password to be used for authentication.  To improve matching
>      of textual passwords, clients SHOULD prepare textual passwords
>      for transfer by transcoding to [Unicode], applying [SASLprep],
>      and encoding as UTF-8.  Clients MAY prepare textual passwords
>      using other algorithms (including null preparation) to support,
>      for instance, legacy systems.  Non-textual passwords MUST NOT
>      be mutated.

I should mention that I do prefer that text over the current one, though
as you know I still want options.  I'd prefer to replace "legacy
systems" with something like "servers using existing hashed password
stores", since "legacy systems" has rather negative connotations.  Also
I wonder what "Non-textual passwords MUST NOT be mutated" means, see
comments above.

-- 
Hallvard


From owner-ietf-ldapbis@OpenLDAP.org  Wed Oct  1 16:10: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 QAA02387
	for <ldapbis-archive@lists.ietf.org>; Wed, 1 Oct 2003 16:10:19 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h91K86jA028853;
	Wed, 1 Oct 2003 20:08: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 h91K6Vqm028815;
	Wed, 1 Oct 2003 20:06:31 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 1 Oct 2003 20:06: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 h91K6Tj2028805
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 1 Oct 2003 20:06:29 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from gypsy.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.9/8.12.9) with ESMTP id h91K6Slg009584;
	Wed, 1 Oct 2003 20:06:29 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.0.22.0.20031001234323.03ef3578@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
Date: Thu, 02 Oct 2003 01:06:13 -0700
To: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: more SASLprep/protocol problems
Cc: ietf-ldapbis@OpenLDAP.org
In-Reply-To: <HBF.20031001hh9u@bombur.uio.no>
References: <HBF.20030923u8q1@bombur.uio.no>
 <6.0.0.22.0.20030924062136.03b79fc0@127.0.0.1>
 <HBF.20031001hh9u@bombur.uio.no>
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>

Hallvard,

This text is intended to bring LDAP into conformance with RFC 2277
(BCP18) as well as improve matching of text as discussed in RFC 3454.

RFC 2277 mandates that protocols support UTF-8 for all character
data. While RFC 2277 allows protocols to support other character set
and encodings forms, LDAP (as currently specified) provides no
mechanism to enable this.  That is, there is no mechanism in LDAP
to negotiate which character set/encoding is in use.

We cannot simply allow implementations to do as this prevents
interoperability (in the IETF sense).
 


At 09:41 AM 10/1/2003, Hallvard B Furuseth wrote:
>Kurt D. Zeilenga writes:
>> I think here are opposing objectives.   One fraction of the
>> community is attempting to improve interoperability between
>> independently developed implementations.  One faction is
>> attempting to support legacy systems.
>
>Are there some implementations that do prepare passwords, or at least
>translate them to UTF-8, and are widely used on non-ASCII or ASCII-
>superset sites with hashed passwords, and thus prove that the problem
>is smaller than I think?

There are many implementations which prepare passwords
in some way....  I know of implementations which:
        transcode EBCDIC to ASCII,
        transcode T.61 to Unicode/UTF-8,
        re-encode UTF-16 to UTF-8,
        apply a Unicode normalization transformation

>> (Note: It is possible to split the preparation between the client
>> and the server, PLAIN does this (client handles transcoding
>> to Unicode and UTF-8 encoding, server handles SASLprep).  With
>> LDAP, this is not a good option as the server has no way to
>> determine whether the password is textual or not.)
>
>I've seldom wondered about so many things in so short a statement:-)
>
>What do you mean by textual and non-textual passwords, exactly?

A textual password consists of character data.

>Why are PLAIN passwords more textual than LDAP passwords?
>Is it simply because PLAIN _requires_ passwords to be UTF-8 which is presumably text, while LDAP only will recommend it?

PLAIN passwords are character data.
LDAP passwords are octet strings which sometimes represent character data.

>If the server and therefore the sysadmin doesn't know whether to prepare
>a bind password or not, how is the client supposed to know - unless the
>user tells it?

Clients (whether used by end-user or sysadmin) have, in
general, knowledge of character set and encodings they are
using to interact with the user.  That knowledge is NOT
communicated by the client to the server.

I note as well that existing external passwords stores do not
maintain knowledge of the character set/encoding used by the
admin, they just store whatever octet string the password-setting
application provides.  The assumption is that the authenticating
application will use the same character set, normalization,
encoding algorithm of the password-setting application.

This assumption is flawed in that;
        a) users may use different platforms and/or platform
          settings then their administrator,
        b) users may use different platforms and/or platform
          settings from time to time.

To deal with this flawed assumption, many deployments are forced
not internationalize.  Instead they use the lowest common
denominator (commonly some subset of ASCII).

The internationalization of LDAP passwords takes this into
account.  The specification preserves the encoding of
printable ASCII passwords.

>Which scenario are you thinking of when you say the server doesn't know?

Most.

>Not that I disagree that client-side preparation is most flexible,
>but... usually all passwords will be UTF-8 or none of them will,
>depending on how the sysadmin put them there, so the server will know.

Clients I have used lately have encoded by password (internally)
using:
        ISO 8559-1, UTF-8, UTF-16, UTF-32.

(I didn't used an EBCDIC client lately).  Luckily the non-UTF-8
clients prepared the password before transferring it.  The server
has no knowledge of this.  It simply treats my password as an
octet string.

>OTOH, the server won't know if they should be prepared if the users
>stored userPasswords as they pleased, both UTF-8 and non-UTF-8.
>But then you _really_ need a client option to say whether or not to prepare
>bind passwords, so I don't suppose that's what you are talking about...

OTOH, say each of my clients just sent password as they pleased
with the expectation that the server deal with.  The problem is,
of course, there is nothing in the protocol which indicates that
the password field is character data and, if so, which character
set/encoding was used.  So, the server would have to guess.

>(Hey! That's another argument for recommending that client option!:-)

Actually, I think you just made a good argument for why we
cannot allow clients to as they please.

>> How's this?
>>
>>      The simple form of an AuthenticationChoice specifies a simple
>>      password to be used for authentication.  To improve matching
>>      of textual passwords, clients SHOULD prepare textual passwords
>>      for transfer by transcoding to [Unicode], applying [SASLprep],
>>      and encoding as UTF-8.  Clients MAY prepare textual passwords
>>      using other algorithms (including null preparation) to support,
>>      for instance, legacy systems.  Non-textual passwords MUST NOT
>>      be mutated.
>
>I should mention that I do prefer that text over the current one, though
>as you know I still want options.  I'd prefer to replace "legacy
>systems" with something like "servers using existing hashed password
>stores", since "legacy systems" has rather negative connotations.

How about s/legacy systems/external password stores/ instead.
I rather not use the term "hashed".

>Also I wonder what "Non-textual passwords MUST NOT be mutated" means, see
>comments above.

It means that implementations are not to alter non-text
(non-character data) passwords. 



From owner-ietf-ldapbis@OpenLDAP.org  Wed Oct  1 16:10: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 QAA02386
	for <ldapbis-archive@lists.ietf.org>; Wed, 1 Oct 2003 16:10:18 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h91K86jC028853;
	Wed, 1 Oct 2003 20:08: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 h91K5xee028770;
	Wed, 1 Oct 2003 20:05:59 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 1 Oct 2003 20:05:59 +0000
Received: from nb2.stroeder.com (krl9-d9bb4c77.pool.mediaWays.net [217.187.76.119])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h91K5qj2028712
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 1 Oct 2003 20:05:57 GMT
	(envelope-from michael@stroeder.com)
Received: from localhost (localhost [127.0.0.1])
	by nb2.stroeder.com (Postfix) with ESMTP id 89B979C5E3
	for <ietf-ldapbis@OpenLDAP.org>; Wed,  1 Oct 2003 22:05:29 +0200 (CEST)
Received: from stroeder.com (localhost [127.0.0.1])
	by nb2.stroeder.com (Postfix) with ESMTP id 714BB19226
	for <ietf-ldapbis@OpenLDAP.org>; Wed,  1 Oct 2003 22:05:28 +0200 (CEST)
Message-ID: <3F7B3388.4080500@stroeder.com>
Date: Wed, 01 Oct 2003 22:05: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.4.1) Gecko/20030910
X-Accept-Language: de-de, de, en-us, en
MIME-Version: 1.0
To: ietf-ldapbis@OpenLDAP.org
Subject: Re: more SASLprep/protocol problems
References: <HBF.20030923u8q1@bombur.uio.no>	<6.0.0.22.0.20030924062136.03b79fc0@127.0.0.1>	<HBF.20030924yebj@bombur.uio.no>	<6.0.0.22.0.20030924234502.03faee48@127.0.0.1> <HBF.20030930pugi@bombur.uio.no>
In-Reply-To: <HBF.20030930pugi@bombur.uio.no>
X-Enigmail-Version: 0.76.6.0
X-Enigmail-Supports: pgp-inline, pgp-mime
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:
>>Clients are to prepare passwords in the same fashion in which
>>the password storage application producing and storing them
>>(or their hashes).  Interoperability with all of these systems
>>is dependent on implementing that rule.
> 
> What preparation?  The systems I know don't modify passwords input by
> the user at all.

Sure they do. Today it's so common and simple that you don't even think
about your keyboard strokes getting translated to your OS' character set
(e.g. Windows Unicode) and again getting translated by the LDAP client to
ASCII or UTF-8 (or ISO-8859-1 in case of Netscape 4.5+).

>>If we remove the statement, a client produces EBCDIC (or even UTF-16)
>>passwords would be fully conformant but fail to interoperate with your
>>ASCII based external password store.
> 
> Not if the client offers an option to prepare passwords.

Uurgs! You wanna let the user decide whether to translate passwords or not?

There was a discussion here about NON-ASCII chars in passwords some time ago 
since many people reported interoperability problems with deployed software 
(e.g. Outlook using UTF-8 vs. Netscape 4.5+ using ISO-8859-1). Please check 
the list's archives. I'm quite happy that there is such a preparation 
statement recommending UTF-8.

Ciao, Michael.



From owner-ietf-ldapbis@OpenLDAP.org  Wed Oct  1 16:21: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 QAA02679
	for <ldapbis-archive@lists.ietf.org>; Wed, 1 Oct 2003 16:21:27 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h91KK6j6029700;
	Wed, 1 Oct 2003 20:20: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 h91KERmp029507;
	Wed, 1 Oct 2003 20:14:27 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 1 Oct 2003 20:14:27 +0000
Received: from nb2.stroeder.com (krl9-d9bb4c77.pool.mediaWays.net [217.187.76.119])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h91KEQj2029489
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 1 Oct 2003 20:14:26 GMT
	(envelope-from michael@stroeder.com)
Received: from localhost (localhost [127.0.0.1])
	by nb2.stroeder.com (Postfix) with ESMTP id 4D23B9C5E1
	for <ietf-ldapbis@OpenLDAP.org>; Wed,  1 Oct 2003 22:14:04 +0200 (CEST)
Received: from stroeder.com (localhost [127.0.0.1])
	by nb2.stroeder.com (Postfix) with ESMTP id 35C5630FD0
	for <ietf-ldapbis@OpenLDAP.org>; Wed,  1 Oct 2003 22:14:03 +0200 (CEST)
Message-ID: <3F7B358A.3060308@stroeder.com>
Date: Wed, 01 Oct 2003 22:14: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.4.1) Gecko/20030910
X-Accept-Language: de-de, de, en-us, en
MIME-Version: 1.0
To: ietf-ldapbis@OpenLDAP.org
Subject: Re: more SASLprep/protocol problems
References: <HBF.20030923u8q1@bombur.uio.no>	<6.0.0.22.0.20030924062136.03b79fc0@127.0.0.1> <HBF.20031001hh9u@bombur.uio.no>
In-Reply-To: <HBF.20031001hh9u@bombur.uio.no>
X-Enigmail-Version: 0.76.6.0
X-Enigmail-Supports: pgp-inline, pgp-mime
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:
> 
> What do you mean by textual and non-textual passwords, exactly?

http://www.openldap.org/lists/ietf-ldapbis/200305/msg00112.html

Ciao, Michael.



From owner-ietf-ldapbis@OpenLDAP.org  Wed Oct  1 16:27: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 QAA02849
	for <ldapbis-archive@lists.ietf.org>; Wed, 1 Oct 2003 16:27:04 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h91KQ6j6030029;
	Wed, 1 Oct 2003 20:26: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 h91KKwSl029739;
	Wed, 1 Oct 2003 20:20:58 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 1 Oct 2003 20:20:58 +0000
Received: from e5.ny.us.ibm.com (e5.ny.us.ibm.com [32.97.182.105])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h91KKuj2029713
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 1 Oct 2003 20:20:56 GMT
	(envelope-from jmcmeek@us.ibm.com)
Received: from northrelay02.pok.ibm.com (northrelay02.pok.ibm.com [9.56.224.150])
	by e5.ny.us.ibm.com (8.12.10/8.12.2) with ESMTP id h91KKZUN645054;
	Wed, 1 Oct 2003 16:20:35 -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.6) with ESMTP id h91KKYeD215136;
	Wed, 1 Oct 2003 16:20:34 -0400
Subject: Re: more SASLprep/protocol problems
To: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>, ietf-ldapbis@OpenLDAP.org
X-Mailer: Lotus Notes Release 5.0.12   February 13, 2003
Message-ID: <OFE48D5E6C.F392BD3F-ON86256DB2.006FAD27-86256DB2.006FBEBF@us.ibm.com>
From: John McMeeking <jmcmeek@us.ibm.com>
Date: Wed, 1 Oct 2003 15:20:31 -0500
X-MIMETrack: Serialize by Router on d27ml001/27/M/IBM(Build V65_08242003|August 24, 2003) at
 10/01/2003 03:20:33 PM
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>





Sorry if there are multiples of this -- mail was having major hiccups ;-(

Hallvard B Furuseth writes:

>> Take, for example, that the external system is EBCDIC based as
>> are existing clients.  It is quite unlikely that any independently
>> developed system would interoperate with such a system.

> True, but at least clients developed _there_ would interoperate with
> both outside systems and their own server if these clients had options
> to both prepare and to not prepare passwords.

> For that matter, these clients developed on the outside of the EBCDIC
> campus would at least _allow_ users to type in passwords that would be
> accepted, if they too had a 'do not prepare' option.  Users would have
> to mess with character tables or something in order to know the right
> character codeds for the passwords, but it could be done.  I'm not sure
> how strong an arugment that is though - I'd like to hear from people on
> EBCDIC systems what they do when they telnet 'home' from an outside
> system.

I believe the OS/400 TELNET server performs code page translation to
convert data as sent for the negotiated mode (probably US ASCII for VT100)
to or from the system code page (an EBCDIC CCSID).  Valid passwords are
limited to the characters that can be entered by the user, exist in the
negotiated mode, and can be converted to the system CCSID.  When I telnet
from my Windows box to OS/400, I assume the Windows telnet client is not
using TELNET 5250 or EBCDIC (help says it supports vt100, vt52, ansi, ...).

================

The OS/400 LDAP server generally assumes passwords in a bind request (or
userPassword attribute, for that matter) are UTF-8.  We have two sources of
passwords:

-  LDAP entries containing a userPassword value.  The bind credentials and
userPassword value are compared as octet strings.  The may compare hashes
of the two values, as we allow the user to control how userPassword values
are stored.

-  Native OS/400 user profiles.  The bind password is converted from UTF-8
to the job CCSID before calling OS/400 authentication services.

The OS/400 LDAP client API, broadly speaking, has two modes:

-  local code page I/O: strings (including password parameter on the simple
bind API) are in the local EBCDIC CCSID on the application side, and
converted to/from UTF-8 to flow in the protocol

- UTF-8 I/O: application works with data in UTF-8 and is responsible for
doing its own data conversion

The server understands how the password store works and performs the
necessary conversions from the credential presented in the bind request to
the form required by the password store.  To some extent, the server
doesn't really care what the credentials are.  And I recall having this
discussion with our then architect a few years ago.  It is very well for
the server to treat credentials as bytes, but people do not enter "bytes"
when they type in a password.  They enter characters that they expect to be
treated the same whether they are entering those characters at an ASCII
system, an EBCDIC system, running in English, German or Chinese, or a Java
application.  The application has to convert a string of characters to a
set of bytes in a consistent way.  We came to the conclusion that textual
credentials, at least, had to be represented in UTF-8.

===============

As to what to do to [PROTOCOL]... I think a SHOULD for
Unicode+SASLPrep+UTF-8 and a SHOULD (MUST?) for the ability for an
application to specify an arbitry octet string to be used as the
credentials is reasonable.

I view the first part as necessary for interoperability between arbitrary
client and server implementations.  The second part may be necessary for a
mix of "new" and "legacy" clients and / or servers, but I tend to view it
more as a bandage on what may have been an overly constrained
implementation.


John  McMeeking



From owner-ietf-ldapbis@OpenLDAP.org  Wed Oct  1 18:36: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 SAA08715
	for <ldapbis-archive@lists.ietf.org>; Wed, 1 Oct 2003 18:36:01 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h91MW7j6036257;
	Wed, 1 Oct 2003 22:34: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 h91MS9pH036147;
	Wed, 1 Oct 2003 22:28:09 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 1 Oct 2003 22:28: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 h91MS8j2036137
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 1 Oct 2003 22:28:08 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from gypsy.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.9/8.12.9) with ESMTP id h91MS8lg010751
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 1 Oct 2003 22:28:08 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.0.22.0.20031002024351.03ff9600@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
Date: Thu, 02 Oct 2003 03:27:52 -0700
To: ietf-ldapbis@OpenLDAP.org
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: more SASLprep/protocol problems
In-Reply-To: <OFE48D5E6C.F392BD3F-ON86256DB2.006FAD27-86256DB2.006FBEBF@
 us.ibm.com>
References: <OFE48D5E6C.F392BD3F-ON86256DB2.006FAD27-86256DB2.006FBEBF@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>

RFC 2277 says:
   All protocols MUST identify, for all character data,
   which charset is in use.

That is, we cannot allow clients to transfer character data in
the protocol without providing the server a protocol mechanism
for reliably determining what charset is use.  My previous
suggestion was flawed in that it allowed character data to
be transferred without identifying which charset is in use.

For this reason, I revise my suggestion:
        The simple form of an AuthenticationChoice specifies a
        simple password to be used for authentication.  Passwords
        consisting of character data (text passwords) SHALL be
       transferred as [UTF-8] encoded [Unicode].  Prior to transfer,
       clients SHOULD prepare text passwords by applying the
       [SASLprep] profile of the [Stringprep] algorithm.  Passwords
        consisting of other data (such as random octets) MUST NOT
        be altered.

Keen eyes will see that I've dropped the "MAY prepare textual
passwords using algorithms".  This was done for the following
reasons.

First, it's implicit in the SHOULD.  As RFC 2119 says, there may
exist valid reasons in particular circumstances to ignore this
SHOULD, but the full implications must be understood and
carefully weighted before choosing a different course.  This
allows alternative approaches.

Secondly, RFC 2119 says of implementations supporting an OPTIONAL
feature MUST be prepared to interoperate with implementations which
don't.   If one client prepares text passwords as RECOMMENDED and
another doesn't, the user will likely only be able to use one
client or the other but not both.

Also, we need to ensure that interoperable implementations of
features, even OPTIONAL features, can be independently developed.
Two clients which both use "null" preparation may fail to
interoperate with the server due to platform differences.
For example, if one client send the text as UTF-16 and
another send same text as UTF-32, authentication will fail
one or both of these clients (assuming the server implements
password matching as specified).

Kurt




From owner-ietf-ldapbis@OpenLDAP.org  Mon Oct  6 02:08: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 CAA15290
	for <ldapbis-archive@lists.ietf.org>; Mon, 6 Oct 2003 02:08:22 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h96646jC057095;
	Mon, 6 Oct 2003 06:06: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 h965olvK056204;
	Mon, 6 Oct 2003 05:50:47 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 6 Oct 2003 05:50: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 h965ohj2056179
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 6 Oct 2003 05:50:44 GMT
	(envelope-from steven.legg@adacel.com.au)
Received: from nexus.adacel.com (Not Verified[10.32.240.1]) by adacel.com with NetIQ MailMarshal (v5.5.3.16)
	id <B0001714ff>; Mon, 06 Oct 2003 15:44:31 +1000
Received: (qmail 31041 invoked from network); 6 Oct 2003 05:38:38 -0000
Received: from unknown (HELO osmium) (10.32.24.165)
  by nexus.adacel.com with SMTP; 6 Oct 2003 05:38:38 -0000
Reply-To: <steven.legg@adacel.com.au>
From: "Steven Legg" <steven.legg@adacel.com.au>
To: <ietf-ldapbis@OpenLDAP.org>
Subject: RE: WG Last Call: draft-ietf-ldapbis-protocol-17.txt [corrected]
Date: Mon, 6 Oct 2003 16:50:20 +1100
Message-ID: <005d01c38bcd$ba767db0$a518200a@osmium.mtwav.adacel.com.au>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0
X-MIMEOLE: Produced By Microsoft MimeOLE V4.72.2120.0
In-Reply-To: <5.2.0.9.0.20030919105440.03bcf5d8@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


Here are some comments on draft-ietf-ldapbis-protocol-17.txt .
They are mostly of an editorial nature.

---------------------------------------


> 1. Introduction 

>    This document details the protocol elements of Lightweight Directory 
                                                   ^ the ?


>    Access Protocol, along with their semantics. Following the 
>    description of protocol elements, it describes the way in which the 
>    protocol is encoded and transferred. 
              ^^ messages are
Or substitute "operations" for "messages".
It doesn't make sense to me to be encoding and transferring a protocol.
It does make sense to me to be encoding and transferring a protocol
message/operation.


>    Prior to Working Group Last Call, this appendix 
>    will be distilled to a summary of changes to RFC 2251. 

doh! :-)


> 3. Protocol Model 
>  
>    The general model adopted by this protocol is one of clients 
>    performing protocol operations against servers. In this model, a 
>    client transmits a protocol request describing the operation to be 
>    performed to a server. The server is then responsible for performing 
>    the necessary operation(s) in the directory. Upon completion of the 
                                       ^
The introduction starts off capitalizing the `d' in directory.
Consistency in the capitalization is desirable, though I don't have a
preference between "Directory" and "directory".


>    The core protocol operations defined in this document can be mapped 
>    to a subset of the X.500 (1997) directory abstract service. However 
>    there is not a one-to-one mapping between LDAP protocol operations 
>    and DAP operations. Server implementations acting as a gateway to 
>    X.500 directories may need to make multiple DAP requests.
                                                             ^ per LDAP request


> 4. Elements of Protocol 
>     
>    The LDAP protocol is described using Abstract Syntax Notation 1 
                                                                   ^ One


>    (ASN.1) [X.680], and is transferred using a subset of ASN.1 Basic 
>    Encoding Rules [X.690]. Section 5.1 specifies how the protocol is 
                                                                    ^^
Suggest: "messages are" or "operations are".


>    In order to support future Standards Track extensions to this 
>    protocol, extensibility is implied where it is allowed (per ASN.1). 
>    In addition, ellipses (...) have been supplied in ASN.1 types that 
>    are explicitly extensible as discussed in [LDAPIANA]. Because of the 
>    implied extensibility, clients and servers MUST (unless otherwise 
>    specified) ignore trailing SEQUENCE elements whose tags they do not 
                                         ^^^^^^^^
Suggest: "components".


> 4.1.3. Distinguished Name and Relative Distinguished Name 
>     
>    An LDAPDN and a RelativeLDAPDN are respectively defined to be the 
>    representation of a distinguished-name and a relative-distinguished-
                                      ^                   ^             ^
Remove the hyphens, the terms are not hyphenated elsewhere in the document.


> 4.1.5. Attribute Value 
>     
>    A field of type AttributeValue is an OCTET STRING containing an 
>    encoded attribute value data type. The value is encoded according to 
                            ^^^^^^^^^^
I would remove the "data type". The data type isn't what is being encoded,
though it controls how the value is encoded.

>    its LDAP-specific encoding definition. The LDAP-specific encoding 
     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Suggest: "the LDAP-specific encoding definition of the corresponding
attribute syntax".


> 4.1.7. Attribute 

>    Each attribute value is distinct in the set (no duplicates). The set 
>    of attribute values is unordered. Implementations MUST NOT reply upon 
                                                                ^^^^^ rely


> 4.1.10. Referral 

>         Referral ::= SEQUENCE OF URL  -- one or more 

The "one or more" constraint can be represented
explicitly as "SEQUENCE SIZE (1..MAX) OF URL".


>    If the client wishes to progress the operation, it MUST follow the 
>    referral by contacting one of the servers.

"If" and "MUST" make this an effective "MAY", e.g.

     "The Client MAY progress the operation by following the referral and
     contacting one of the servers."


>    -    Other aspects of the new request may be the same or different as 
                                                      ^^^^^^^^^^^^^^^^^^^^
Suggest: "same as, or different from,"


> 4.2. Bind Operation 

>    - authentication: information used to authenticate the name, if any, 
>      provided in the Bind Request. This type is extensible as defined 
>      in Section 3.6 of [LDAPIANA]. Servers that do not support a choice 
>      supplied by a client will return authMethodNotSupported in the 
>      resultCode field of the BindResponse. The simple form of an 
>      AuthenticationChoice specifies a simple password to be used for 
>      authentication. To improve matching, applications SHOULD prepare 
>      textual strings used as passwords. Applications which prepare 
>      textural strings used as password are REQUIRED to prepare them by 
       ^^^^^^^^ textual                 ^s


> 4.2.2. Bind Response 

>    The serverSaslCreds are used as part of a SASL-defined bind mechanism 
>    to allow the client to authenticate the server to which it is 
>    communicating, or to perform "challenge-response" authentication. If 
>    the client bound with the simple choice, or the SASL mechanism does 
>    not require the server to return information to the client, then this 
>    field is not to be included in the BindResponse. 
           ^^^^^^^^^ SHALL NOT ?


> 4.5. Search Operation 
>     
>    The Search Operation allows a client to request that a search be 
>    performed on its behalf by a server. This can be used to read 
>    attributes from a single entry, from entries immediately below a 
                                                              ^^^^^
Suggest: "subordinate to"


> 4.5.1. Search Request 

>         SubstringFilter ::= SEQUENCE { 
>                 type            AttributeDescription, 
>                 -- at least one must be present, 
>                 -- initial and final can occur at most once 
>                 substrings      SEQUENCE OF CHOICE { 

The "at least one must be present" constraint can be represented
explicitly as "SEQUENCE SIZE (1..MAX) OF CHOICE".


>    - sizeLimit: A size limit that restricts the maximum number of 
>      entries to be returned as a result of the search. A value of 0 in 
>      this field indicates that no client-requested size limit 
>      restrictions are in effect for the search. Servers may enforce a 
>      maximum number of entries to return. 
>     
>    - timeLimit: A time limit that restricts the maximum time (in 
>      seconds) allowed for a search. A value of 0 in this field 
>      indicates that no client-requested time limit restrictions are in 
>      effect for the search. 

Servers may limit the number of entries returned. Should they not also
be allowed to limit the amount of time spent ?


>      The extensibleMatch is new in this version of LDAP. If the 
>      matchingRule field is absent, the type field MUST be present, and 
>      the equality match is performed for that type. If the type field 
>      is absent and matchingRule is present, the matchValue is compared 
>      against all attributes in an entry which support that 
>      matchingRule, and the matchingRule determines the syntax for the 
>      assertion value (the filter item evaluates to TRUE if it matches 
>      with at least one attribute in the entry, FALSE if it does not 
>      match any attribute in the entry, and Undefined if the 
>      matchingRule is not recognized or the assertionValue cannot be 
>      parsed.) If the type field is present and matchingRule is present, 
>      the matchingRule MUST be one permitted for use with that type, 
                                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Suggest: "suitable for use with that type (see [Syntaxes])".


>    - attributes: A list of the attributes to be returned from each 
>      entry which matches the search filter. LDAPString values of this 
>      field are constrained to the following ABNF: 
>     
>      attributeSelection = noattrs /  
>                          *( attributedescription / specialattr ) 
>     
>      noattrs = %x31 %x2E %x31 ; "1.1" 
>     
>      attributedescription = ; attributedescription from 2.5 of [Models] 

I would leave out the above line and instead add (after the ABNF) the comment:
"The <attributedescription> rule is defined in Section 2.5 of [Models]."


>      Attributes MUST be named at most once in the list, and are 
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^
Suggest: "MUST NOT be named more than once".


>      Client implementors should note that even if all user attributes 
>      are requested, some attributes of the entry may not be included in 
>      search results due to access controls or other restrictions. 
>      Furthermore, servers will not return operational attributes, such 
>      as objectClasses or attributeTypes, unless they are listed by 
>      name, since there may be extremely large number of values for 
>      certain operational attributes. (A list of operational attributes 
>      for use in LDAP is given in [Syntaxes].) 
                                   ^^^^^^^^^^
The operational attributes are now listed in other documents.


> 4.5.2. Search Result 

>         PartialAttributeList ::= SEQUENCE OF SEQUENCE { 
>                 type    AttributeDescription, 
>                 vals    SET OF AttributeValue } 

I thought there was an agreement to consolidate all the SEQUENCEs
of type and vals into one Attribute ASN.1 type, and for there to be only
one "SEQUENCE OF Attribute" ASN.1 type. What happened to that ?


>         SearchResultReference ::= [APPLICATION 19] SEQUENCE OF URL 
>         -- at least one URL element must be present 

The "at least one URL element must be present" constraint can be represented
explicitly as "SEQUENCE SIZE (1..MAX) OF URL".


>    If the server's schema defines a textual name for an attribute type, 
>    it SHOULD use a textual name for attributes of that attribute type by 
>    specifying one of the textual names as the value of the attribute 
>    type. Otherwise, the server uses the object identifier for the 
>    attribute type by specifying the object identifier, in ldapOID form, 
>    as the value of attribute type. If the server determines that 
>    returning a textual name will cause interoperability problems, it 
>    SHOULD return the ldapOID form of the attribute type. 

This paragraph is a bit shaky. Consider this instead:

  "If the server's schema defines short names [Models] for an attribute type
   then the server SHOULD use one of those names in attribute descriptions
   for that attribute type (in preference to using the dotted decimal format
   of the attribute type's object identifier). The server should not use the
   short name if that name is known by the server to be ambiguous, or
   otherwise likely to cause interoperability problems."


> 4.5.3. Continuation References in the Search Result 
>     
>    If the server was able to locate the entry referred to by the 
>    baseObject but was unable to search all the entries in the scope at 
>    and under the baseObject, the server may return one or more 
         ^^^^^
Suggest: "subordinate to".


>    -    Other aspects of the new search request may be the same or 
                                                             ^^^^^^^
>         different as the search request which generated the 
          ^^^^^^^^^^^^
Suggest: "same as, or different from,"


> 4.6. Modify Operation 

>    Parameters of the Modify Request are: 
>     
>    - object: The object to be modified. The value of this field 
>      contains the DN of the entry to be modified. The server will not 
                                                               ^^^^^^^^
SHALL NOT ?


>    The result of the modification attempted by the server upon receipt 
>    of a Modify Request is returned in a Modify Response, defined as 
>    follows: 
>     
>         ModifyResponse ::= [APPLICATION 7] LDAPResult 
>     
>    Upon receipt of a Modify Request, a server will perform the necessary 
>    modifications to the DIT. 

I would swap around the two sentences above.


>    The Modify Operation cannot be used to remove from an entry any of 
>    its distinguished values, those values which form the entry's 
                              ^ i.e.


> 4.7. Add Operation 

>    Parameters of the Add Request are: 
>     
>    - entry: the Distinguished Name of the entry to be added. Note that 
                                                               ^^^^^^^^^
>      the server will not dereference any aliases in locating the entry 
       ^^^^^^^^^^^^^^^^^^^
Suggest: "The server SHALL NOT".


>    The entry named in the entry field of the AddRequest MUST NOT exist 
>    for the AddRequest to succeed. The immediate superior (parent) of the 
                                                                       ^^^
>    object and alias entries to be added MUST exist. For example, if the 
     ^^^^^^^^^^^^^^^^^^^^^^^^
Suggest: "an object or alias entry".


>    Server implementations SHOULD NOT restrict where entries can be 
>    located in the directory unless DIT structure rules are in place. 
>    Some servers MAY allow the administrator to restrict the classes of 
     ^^^^
The "Some" is redundant.


> 4.8. Delete Operation 

>    The Delete Request consists of the Distinguished Name of the entry to 
>    be deleted. Note that the server will not dereference aliases while 
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Suggest: "The server SHALL NOT".

>    resolving the name of the target entry to be removed, and that only 
                                                         ^^^^^^^^^^
And start a new sentence here, "Note that only" etc.


>    The result of the delete attempted by the server upon receipt of a 
>    Delete Request is returned in the Delete Response, defined as 
>    follows: 
>     
>         DelResponse ::= [APPLICATION 11] LDAPResult 
>     
>    Upon receipt of a Delete Request, a server will attempt to perform 
>    the entry removal requested. The result of the delete attempt will be 
>    returned to the client in the Delete Response. 

There is some redundancy here. Try this instead:

   Upon receipt of a Delete Request, a server will attempt to perform 
   the entry removal requested. The result of the delete attempt will be 
   returned to the client in the Delete Response, defined as follows: 

       DelResponse ::= [APPLICATION 11] LDAPResult 


> 4.9. Modify DN Operation 
>     
>    The Modify DN Operation allows a client to change the leftmost (least 
                                                           ^^^^^^^^^^^^^^^
>    significant) component of the name of an entry in the directory, 
     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

I think it would be better to say the "relative distinguished name".


>    Parameters of the Modify DN Request are: 
>     
>    - entry: the Distinguished Name of the entry to be changed. This 
>      entry may or may not have subordinate entries. Note that the 
                                                      ^^^^^^^^^^^^^
>      server will not dereference any aliases in locating the entry to 
       ^^^^^^^^^^^^^^^

Suggest: "The server SHALL NOT".


>    - newrdn: the RDN that will form the leftmost component of the new 
>      name of the entry. 

I think it would be better to say "the new relative distinguished name
of the entry".


>    - newSuperior: if present, this is the Distinguished Name of an 
>      existing object entry which becomes the immediate superior 
>      (parent)of the existing entry. 
               ^
Missing space.


>    The result of the name change attempted by the server upon receipt of 
>    a Modify DN Request is returned in the Modify DN Response, defined as 
>    follows: 
>     
>         ModifyDNResponse ::= [APPLICATION 13] LDAPResult 
>     
>    Upon receipt of a ModifyDNRequest, a server will attempt to perform 
>    the name change. The result of the name change attempt will be 
>    returned to the client in the Modify DN Response. 

See the simplification of the similar text for the Delete Response.


>    If the deleteoldrdn parameter is TRUE, the values forming the old RDN 
>    are deleted from the entry. If the deleteoldrdn parameter is FALSE, 
>    the values forming the old RDN will be retained as non-distinguished 
>    attribute values of the entry. The server may not perform the 
                                               ^^^^^^^^^^^^^^^
Suggest: "MUST fail".

>    operation and return an error in the result code if the setting of 
>    the deleteoldrdn parameter would cause a schema inconsistency in the 
>    entry. 


> 4.10. Compare Operation 

>    - entry: the name of the entry to be compared with. Note that the 
>      server SHOULD NOT dereference any aliases in locating the entry to 
>      be compared with. 

Suggest: "the name of the entry to be compared. The server SHOULD NOT
dereference any aliases in locating the entry to be compared."


>    The result of the compare attempted by the server upon receipt of a 
>    Compare Request is returned in the Compare Response, defined as 
>    follows: 
>     
>         CompareResponse ::= [APPLICATION 15] LDAPResult 
>     
>    Upon receipt of a Compare Request, a server will attempt to perform 
>    the requested comparison using the EQUALITY matching rule for the 
>    attribute type. The result of the comparison will be returned to the 
>    client in the Compare Response.

Redundancy here too.


> 4.12. Extended Operation 

>    Servers list the requestName of all ExtendedRequests they recognize 
            ^ SHALL ?


>    requestValues and responseValues that are defined in terms of ASN.1 
>    and BER encoded according to Section 5.1, also follow the 
>    extensibility rules in Section 4. 

This paragraph restates a condition in a previous paragraph in this section.


> 4.13.2.2. Response other than "success" 

>    If the server does not support TLS (whether by design or by current 
>    configuration), it MUST set the resultCode field to protocolError. 
>    The client's current association is unaffected if the server does not 
>    support TLS. The client MAY proceed with any LDAP operation, or it 
                             ^^^                                  ^^
>    MAY close the connection. 
     ^^^
"MAY" and "or" both suggest optionality. I am left wondering what a client
is supposed to do if it elects to do neither of the MAY actions.
Perhaps the "MAY"s should be downcased.


>    The server MUST return unavailable if it supports TLS but cannot 
>    establish a TLS connection for some reason, e.g. the certificate 
>    server not responding, it cannot contact its TLS implementation, or 
>    if the server is in process of shutting down. The client MAY retry 
                                                              ^^^
>    the StartTLS operation, or it MAY proceed with any other LDAP 
                             ^^^^^^^^^
>    operation, or it MAY close the LDAP connection. 
                ^^^^^^^^^
Same again.


> 4.13.3. Closing a TLS Connection 
>  
>    Two forms of TLS connection closure--graceful and abrupt--are 
                                        ^^                   ^^
Extra spaces needed around the hyphens.


> 4.13.3.1. Graceful Closure 

>    The other party, if it receives a TLS closure alert, MUST immediately 
>    transmit a TLS closure alert.  It will subsequently cease to send TLS 
                                       ^^^^ MUST ?


> 7. Security Considerations 

>    Server implementors should plan for the possibility of an identity or 
                                                                        ^^
The "or" appears to be spurious.

>    associated with an LDAP connection being deleted, renamed, or 
>    modified, and take appropriate actions to prevent insecure side 
>    effects. The way in which this is dealt with is implementation 
>    specific. Likewise, server implementors should plan for the 
>    possibility of an associated identities credentials becoming invalid. 
                                  ^^^^^^^^^^ identity's ?


>    Protocol servers may return referrals which redirect protocol clients 
>    to peer servers. It is possible for a rogue application to inject 
>    such referrals into the data stream in an attempt to redirect a 
>    client to a rogue server. Protocol clients are advised to be aware of 
>    this, and possibly reject referrals when confidentiality measures are 

Is there a "not" missing after the "are" ?

>    in place. Protocol clients are advised to ignore referrals from the 
>    Start TLS operation. 


> 9. Normative References 

>    [LDAPIANA] K. Zeilenga, "IANA Considerations for LDAP", draft-ietf-
>              ldapbis-xx.txt (a work in progress). 

Should be draft-ietf-ldapbis-bcp64-00.txt .


>    [Syntaxes] K. Dally (editor), "LDAP: Syntaxes", draft-ietf-ldapbis-
>              syntaxes-xx.txt, (a work in progress). 

Officially, I'm the editor now, but in any case I thought the normal
practice was to list all the authors.


> 11. IANA Considerations 
>    It is requested that the Internet Assigned Numbers Authority (IANA) 
>    update the occurrence of "RFC XXXX" Appendix B with this RFC number 
                                        ^ in


> Appendix A - LDAP Result Codes 

>    Additional result codes MAY be defined for use with extensions. 

I suggest adding a reference to [LDAPIANA].


> A.1 Non-Error Result Codes 

>    The success, compareTrue, and compare result codes indicate 
>    successful completion (and, hence, are called to as "successful" 
                                            ^^^^^^ referred ?


> A.2 Result Codes 

>         protocolError (2) 

>            For bind operation only, the code may be resulted to indicate 
                                                      ^^^^^^^^ returned ?


>         inappropriateMatching (18) 
>          
>            Indicates that a request cannot be completed due to an 
>            inappropriate matching. 

This doesn't tell me much. The X.511 description is "An attempt was made,
e.g. in a filter, to use a matching rule not defined for the attribute
type concerned".


>         attributeOrValueExists (20) 
>          
>            Indicates that the client supplied an attribute or value to 
>            be added to an entry already exists. 
                                 ^ that


>         inappropriateAuthentication (48) 
>          
>            Indicates the server requires the client which had attempted 
>            to bind anonymously or without supplying credentials to 
>            provide some form of credentials, 

Sentence is truncated.


>         objectClassModsProhibited (69) 

>            For example, this code is returned when a when a client 
                                                ^^^^^^^^^^^^^


Regards,
Steven



From owner-ietf-ldapbis@OpenLDAP.org  Mon Oct  6 20:12: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 UAA29115
	for <ldapbis-archive@lists.ietf.org>; Mon, 6 Oct 2003 20:12:45 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h9708nj6009023;
	Tue, 7 Oct 2003 00:10: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 h9707cdO009011;
	Tue, 7 Oct 2003 00:07:38 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 7 Oct 2003 00:07:38 +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 h9707Zj2009001
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 7 Oct 2003 00:07:36 GMT
	(envelope-from steven.legg@adacel.com.au)
Received: from nexus.adacel.com (Not Verified[10.32.240.1]) by adacel.com with NetIQ MailMarshal (v5.5.3.16)
	id <B00017246e>; Tue, 07 Oct 2003 10:01:19 +1000
Received: (qmail 7425 invoked from network); 6 Oct 2003 23:55:26 -0000
Received: from unknown (HELO osmium) (10.32.24.165)
  by nexus.adacel.com with SMTP; 6 Oct 2003 23:55:26 -0000
Reply-To: <steven.legg@adacel.com.au>
From: "Steven Legg" <steven.legg@adacel.com.au>
To: <ietf-ldapbis@OpenLDAP.org>
Subject: RE: WG Last Call: draft-ietf-ldapbis-protocol-17.txt [corrected]
Date: Tue, 7 Oct 2003 11:07:13 +1100
Message-ID: <002e01c38c66$f6237ea0$a518200a@osmium.mtwav.adacel.com.au>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0
X-MIMEOLE: Produced By Microsoft MimeOLE V4.72.2120.0
In-Reply-To: <5.2.0.9.0.20030919105440.03bcf5d8@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


Folks,

I recently published an Internet draft on an XML rendition of the LDAP
protocol (called XLDAP) that is realized by applying a set of XML
encoding rules to the ASN.1 types in the ASN.1 specification for LDAP
(specifically the ASN.1 in the protocols draft being last-called).

The XML produced is neat and tidy except with respect to the instances
of the member type of a SEQUENCE OF or SET OF ASN.1 type.

Consider this example drawn from the protocols draft:

        AttributeList ::= SEQUENCE OF SEQUENCE { 
                type    AttributeDescription, 
                vals    SET OF AttributeValue } 

Using my Directory XML Encoding Rules (DXER) to encode an attribute list,
each attribute in the list is encoded as an element with the safe, but
bland name of <item>. Using the ITU-T's XML Encoding Rules (XER), each
attribute in the list is encoded as an element with the unappealing name
of <SEQUENCE>.
    
However the situation can be improved since the version of ASN.1 that
the protocols draft is referencing allows an ASN.1 identifier after a
SEQUENCE OF or SET OF and before the definition of the member type.

For example:

        AttributeList ::= SEQUENCE OF attribute SEQUENCE { 
                type    AttributeDescription, 
                vals    SET OF value AttributeValue } 

With this change both DXER and XER would encode each attribute in the list
as an element with the more meaningful name of <attribute>. This change
makes no difference to the BER encoding, so it is neutral to LDAP and does
not represent a new feature.

I would like to see each of the SEQUENCE OF and SET OF definitions in the
LDAP ASN.1 module given a meaningful mnemonic identifier for the member type
so as to facilitate better XML representations of LDAP operations (whether
for XLDAP or any other purpose). If the working group allows it I'll work
with Jim to make the additions.

Regards,
Steven



From owner-ietf-ldapbis@OpenLDAP.org  Tue Oct  7 01:18: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 BAA06556
	for <ldapbis-archive@lists.ietf.org>; Tue, 7 Oct 2003 01:18:50 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h975Epj6017283;
	Tue, 7 Oct 2003 05:16: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 h975CRxV017247;
	Tue, 7 Oct 2003 05:12:27 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 7 Oct 2003 05:12:27 +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 h975CPj2017231
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 7 Oct 2003 05:12:25 GMT
	(envelope-from jimse@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Mon, 06 Oct 2003 23:12:05 -0600
Message-Id: <sf81f6c5.061@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.1 
Date: Mon, 06 Oct 2003 23:11:42 -0600
From: "Jim Sermersheim" <jimse@novell.com>
To: <ietf-ldapbis@OpenLDAP.org>
Subject: RE: WG Last Call: draft-ietf-ldapbis-protocol-17.txt
	[corrected]
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__Part80DE301E.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>

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.

--=__Part80DE301E.0__=
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Sounds good to me. I wasn't aware that ASN.1 allows that.
 
Also, is it any different from:
 
AttributeList ::= SEQUENCE OF Attribute 
 
Attribute ::= SEQUENCE { 
type AttributeDescription, 
vals SET OF value AttributeValue }
 
Jim

>>> "Steven Legg" <steven.legg@adacel.com.au> 10/6/03 6:07:13 PM >>>

Folks,

I recently published an Internet draft on an XML rendition of the LDAP
protocol (called XLDAP) that is realized by applying a set of XML
encoding rules to the ASN.1 types in the ASN.1 specification for LDAP
(specifically the ASN.1 in the protocols draft being last-called).

The XML produced is neat and tidy except with respect to the instances
of the member type of a SEQUENCE OF or SET OF ASN.1 type.

Consider this example drawn from the protocols draft:

AttributeList ::= SEQUENCE OF SEQUENCE { 
type AttributeDescription, 
vals SET OF AttributeValue } 

Using my Directory XML Encoding Rules (DXER) to encode an attribute
list,
each attribute in the list is encoded as an element with the safe, but
bland name of <item>. Using the ITU-T's XML Encoding Rules (XER), each
attribute in the list is encoded as an element with the unappealing
name
of <SEQUENCE>.

However the situation can be improved since the version of ASN.1 that
the protocols draft is referencing allows an ASN.1 identifier after a
SEQUENCE OF or SET OF and before the definition of the member type.

For example:

AttributeList ::= SEQUENCE OF attribute SEQUENCE { 
type AttributeDescription, 
vals SET OF value AttributeValue } 

With this change both DXER and XER would encode each attribute in the
list
as an element with the more meaningful name of <attribute>. This
change
makes no difference to the BER encoding, so it is neutral to LDAP and
does
not represent a new feature.

I would like to see each of the SEQUENCE OF and SET OF definitions in
the
LDAP ASN.1 module given a meaningful mnemonic identifier for the member
type
so as to facilitate better XML representations of LDAP operations
(whether
for XLDAP or any other purpose). If the working group allows it I'll
work
with Jim to make the additions.

Regards,
Steven



--=__Part80DE301E.0__=
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 5.50.4933.1800" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Microsoft Sans Serif">
<DIV>Sounds good to me. I wasn't aware that ASN.1&nbsp;allows that.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Also, is it any different from:</DIV>
<DIV>&nbsp;</DIV>
<DIV>AttributeList ::= SEQUENCE OF Attribute </DIV>
<DIV>&nbsp;</DIV>
<DIV>Attribute ::= SEQUENCE { <BR>type AttributeDescription, <BR>vals SET OF value AttributeValue }</DIV>
<DIV>&nbsp;</DIV>
<DIV>Jim<BR><BR>&gt;&gt;&gt; "Steven Legg" &lt;steven.legg@adacel.com.au&gt; 10/6/03 6:07:13 PM &gt;&gt;&gt;<BR><BR>Folks,<BR><BR>I recently published an Internet draft on an XML rendition of the LDAP<BR>protocol (called XLDAP) that is realized by applying a set of XML<BR>encoding rules to the ASN.1 types in the ASN.1 specification for LDAP<BR>(specifically the ASN.1 in the protocols draft being last-called).<BR><BR>The XML produced is neat and tidy except with respect to the instances<BR>of the member type of a SEQUENCE OF or SET OF ASN.1 type.<BR><BR>Consider this example drawn from the protocols draft:<BR><BR>AttributeList ::= SEQUENCE OF SEQUENCE { <BR>type AttributeDescription, <BR>vals SET OF AttributeValue } <BR><BR>Using my Directory XML Encoding Rules (DXER) to encode an attribute list,<BR>each attribute in the list is encoded as an element with the safe, but<BR>bland name of &lt;item&gt;. Using the ITU-T's XML Encoding Rules (XER), each<BR>attribute in the list is !
 encoded as an element with the unappealing name<BR>of &lt;SEQUENCE&gt;.<BR><BR>However the situation can be improved since the version of ASN.1 that<BR>the protocols draft is referencing allows an ASN.1 identifier after a<BR>SEQUENCE OF or SET OF and before the definition of the member type.<BR><BR>For example:<BR><BR>AttributeList ::= SEQUENCE OF attribute SEQUENCE { <BR>type AttributeDescription, <BR>vals SET OF value AttributeValue } <BR><BR>With this change both DXER and XER would encode each attribute in the list<BR>as an element with the more meaningful name of &lt;attribute&gt;. This change<BR>makes no difference to the BER encoding, so it is neutral to LDAP and does<BR>not represent a new feature.<BR><BR>I would like to see each of the SEQUENCE OF and SET OF definitions in the<BR>LDAP ASN.1 module given a meaningful mnemonic identifier for the member type<BR>so as to facilitate better XML representations of LDAP operations (whether<BR>for XLDAP or any other purpose)!
 . If the working group allows it I'll work<BR>with Jim to make!
  the add

itions.<BR><BR>Regards,<BR>Steven<BR><BR></DIV></BODY></HTML>
--=__Part80DE301E.0__=--


From owner-ietf-ldapbis@OpenLDAP.org  Tue Oct  7 02: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 CAA20752
	for <ldapbis-archive@lists.ietf.org>; Tue, 7 Oct 2003 02:29:12 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h976Kuj6018913;
	Tue, 7 Oct 2003 06:23: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 h976HTjV018848;
	Tue, 7 Oct 2003 06:17:29 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 7 Oct 2003 06:17:29 +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 h976HQj2018833
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 7 Oct 2003 06:17:28 GMT
	(envelope-from steven.legg@adacel.com.au)
Received: from nexus.adacel.com (Not Verified[10.32.240.1]) by adacel.com with NetIQ MailMarshal (v5.5.3.16)
	id <B000172b95>; Tue, 07 Oct 2003 16:11:08 +1000
Received: (qmail 13129 invoked from network); 7 Oct 2003 06:05:16 -0000
Received: from unknown (HELO adacel.com.au) (10.32.24.165)
  by nexus.adacel.com with SMTP; 7 Oct 2003 06:05:16 -0000
Message-ID: <3F825A60.7060105@adacel.com.au>
Date: Tue, 07 Oct 2003 17:17:04 +1100
From: Steven Legg <steven.legg@adacel.com.au>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3.1) Gecko/20030425
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Jim Sermersheim <jimse@novell.com>
CC: ietf-ldapbis@OpenLDAP.org
Subject: Re: WG Last Call: draft-ietf-ldapbis-protocol-17.txt	[corrected]
References: <sf81f6c5.061@prv-mail20.provo.novell.com>
In-Reply-To: <sf81f6c5.061@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


Hi Jim,

Jim Sermersheim wrote:
> Sounds good to me. I wasn't aware that ASN.1 allows that.

It was added after the 1997 edition of ASN.1.

>  
> Also, is it any different from:
>  
> AttributeList ::= SEQUENCE OF Attribute

DXER would still encode each instance of the Attribute ASN.1 type
as an element with the name <item>. In this case XER would instead
encode each instance as an element with the name <Attribute>. Thus
XER is more sensitive to reorganization of the ASN.1 specification
than is DXER.

If the notation were either

    AttributeList ::= SEQUENCE OF attribute Attribute

or

    AttributeList ::= SEQUENCE OF attribute SEQUENCE {
        type  AttributeDescription,
        vals  SET OF value AttributeValue }

then DXER and XER would both use the name <attribute> (in both cases).

Regards,
Steven

>  
> Attribute ::= SEQUENCE {
> type AttributeDescription,
> vals SET OF value AttributeValue }
>  
> Jim
> 
>  >>> "Steven Legg" <steven.legg@adacel.com.au> 10/6/03 6:07:13 PM >>>
> 
> Folks,
> 
> I recently published an Internet draft on an XML rendition of the LDAP
> protocol (called XLDAP) that is realized by applying a set of XML
> encoding rules to the ASN.1 types in the ASN.1 specification for LDAP
> (specifically the ASN.1 in the protocols draft being last-called).
> 
> The XML produced is neat and tidy except with respect to the instances
> of the member type of a SEQUENCE OF or SET OF ASN.1 type.
> 
> Consider this example drawn from the protocols draft:
> 
> AttributeList ::= SEQUENCE OF SEQUENCE {
> type AttributeDescription,
> vals SET OF AttributeValue }
> 
> Using my Directory XML Encoding Rules (DXER) to encode an attribute list,
> each attribute in the list is encoded as an element with the safe, but
> bland name of <item>. Using the ITU-T's XML Encoding Rules (XER), each
> attribute in the list is encoded as an element with the unappealing name
> of <SEQUENCE>.
> 
> However the situation can be improved since the version of ASN.1 that
> the protocols draft is referencing allows an ASN.1 identifier after a
> SEQUENCE OF or SET OF and before the definition of the member type.
> 
> For example:
> 
> AttributeList ::= SEQUENCE OF attribute SEQUENCE {
> type AttributeDescription,
> vals SET OF value AttributeValue }
> 
> With this change both DXER and XER would encode each attribute in the list
> as an element with the more meaningful name of <attribute>. This change
> makes no difference to the BER encoding, so it is neutral to LDAP and does
> not represent a new feature.
> 
> I would like to see each of the SEQUENCE OF and SET OF definitions in the
> LDAP ASN.1 module given a meaningful mnemonic identifier for the member type
> so as to facilitate better XML representations of LDAP operations (whether
> for XLDAP or any other purpose). If the working group allows it I'll work
> with Jim to make the additions.
> 
> Regards,
> Steven
> 



From owner-ietf-ldapbis@OpenLDAP.org  Tue Oct  7 16:43: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 QAA21770
	for <ldapbis-archive@lists.ietf.org>; Tue, 7 Oct 2003 16:43:46 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h97Kd7j6073180;
	Tue, 7 Oct 2003 20:41: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 h97KYb0c073035;
	Tue, 7 Oct 2003 20:34:37 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 7 Oct 2003 20:34:37 +0000
Received: from boole.openldap.org (kurt@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h97KYTj2073024
	for <ietf-ldapbis@openldap.org>; Tue, 7 Oct 2003 20:34:29 GMT
	(envelope-from kurt@boole.openldap.org)
Received: (from kurt@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) id h97KYTgl073023
	for ietf-ldapbis@openldap.org; Tue, 7 Oct 2003 13:34:29 -0700 (PDT)
	(envelope-from kurt)
Date: Thu, 2 Oct 2003 13:48:43 +0200
From: Kurt Zeilenga <Kurt@OpenLDAP.org>
To: ietf-ldapbis@OpenLDAP.org
Subject: protocol review notes [LONG]
Message-ID: <20031002114843.GB590@bahner.com>
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

Below are my review notes.  Some of the issues I raised are
significant and likely somewhat contentious.  These should
be spun off into separate threads.  And, given this post
is quite long, please trim portions extraneous to your
comments from your replies.

Thanks, Kurt


>Internet-Draft                                  Editor:  J. Sermersheim 
>Intended Category: Standard Track                           Novell, Inc 
>Document: draft-ietf-ldapbis-protocol-14.txt                   Jun 2003 
>Obsoletes: RFC 2251                                                     
> 
> 
>                            LDAP: The Protocol 
> 
>Abstract 
> 
>   This document describes the protocol elements, along with their 
>   semantics and encodings, for the Lightweight Directory Access 
>   Protocol (LDAP). LDAP provides access to distributed directory 
>   services that act in accordance with X.500 data and service models. 
>   These protocol elements are based on those described in the X.500 
>   Directory Access Protocol (DAP). 
>    
>1. Introduction 
>    
>   The Directory is "a collection of open systems cooperating to provide 
>   directory services" [X.500]. A Directory user, which may be a human 
>   or other entity, accesses the Directory through a client (or 
>   Directory User Agent (DUA)). The client, on behalf of the directory 
>   user, interacts with one or more servers (or Directory System Agents 
>   (DSA)). Clients interact with servers using a directory access 
>   protocol.  
>    
>   This document details the protocol elements of Lightweight Directory 
>   Access Protocol, along with their semantics. Following the 
>   description of protocol elements, it describes the way in which the 
>   protocol is encoded and transferred. 

Insert (LDAP) after Lightweight Directory Access Protocol.
    
>   This document is an integral part of the LDAP Technical Specification 
>   [Roadmap]. 
>    
>   This document replaces RFC 2251. Appendix C holds a detailed log of 
>   changes to RFC 2251. Prior to Working Group Last Call, this appendix 
>   will be distilled to a summary of changes to RFC 2251. 

This (distill and review) still needs to be done (post WG Last Call).
 
>2. Conventions 
>    
>   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 
>   "SHOULD", "SHOULD NOT", "RECOMMENDED", and "MAY" in this document are 
>   to be interpreted as described in [RFC2119]. 
>   The terms "connection" and "LDAP connection" both refer to the 
>   underlying transport protocol connection between two protocol peers. 
>   The term "TLS connection" refers to a TLS-protected LDAP connection. 
>   The terms "association" and "LDAP association" both refer to the 
>   association of the LDAP connection and the current authentication and 
>   authorization state. 

Insert blank lines between paragraphs.

>3. Protocol Model 
> 
>   The general model adopted by this protocol is one of clients 
>   performing protocol operations against servers. In this model, a 
>   client transmits a protocol request describing the operation to be 
>   performed to a server. The server is then responsible for performing 
>   the necessary operation(s) in the directory. Upon completion of the 
>   operation(s), the server returns a response containing any results or 
>   errors to the requesting client. 
>    
>   Note that although servers are required to return responses whenever 
>   such responses are defined in the protocol, there is no requirement 
>   for synchronous behavior on the part of either clients or servers. 
>   Requests and responses for multiple operations may be exchanged 
>   between a client and server in any order, provided the client 
>   eventually receives a response for every request that requires one. 
> 
>   Note that the core protocol operations defined in this document can 
>   be mapped to a subset of the X.500(1997) directory abstract service. 

s/1997/1993/
                                      
Add (informative) references to [X.500] and [X.511].

>   However there is not a one-to-one mapping between LDAP protocol 
>   operations and DAP operations.

Spell DAP out (first use in body)

>   Server implementations acting as a 
>   gateway to X.500 directories may need to make multiple DAP requests. 

>4. Elements of Protocol 
>    
>   The LDAP protocol is described using Abstract Syntax Notation 1 
>   (ASN.1) [X.680], and is transferred using a subset of ASN.1 Basic 
>   Encoding Rules [X.690]. Section 5.1 specifies how the protocol is 
>   encoded and transferred. 

Insert (BER) after Rules.

>   In order to support future Standards Track extensions to this 
>   protocol, extensibility is implied where it is allowed (per ASN.1). 
>   In addition, ellipses (...) have been supplied in ASN.1 types that 
>   are explicitly extensible as discussed in [LDAPIANA]. Because of the 
>   implied extensibility, clients and servers MUST ignore trailing 
>   SEQUENCE elements whose tags they do not recognize.  
>    
>   Changes to the LDAP protocol other than through the extension 
>   mechanisms described here require a different version number. A 
>   client indicates the version it is using as part of the bind request, 
>   described in section 4.2. If a client has not sent a bind, the server 
>   MUST assume the client is using version 3 or later. 
>    
>   Clients may determine the protocol versions a server supports by 
>   reading the supportedLDAPVersion attribute from the root DSE 
>   [Models].

Spell out DSE on first use.

>   Servers which implement version 3 or later MUST provide 
>   this attribute. 

Drop the MUST.  As the returned contents of the root DSE may be
subject to ACLs, clients need to deal with the case where an LDAPv3
server does not provide a root DSE or does not provide this attribute.
Most clients simply do blind (e.g., no root DSE checks) LDAPv3 binds
instead.

Instead,
	Servers implementing this specification SHOULD provide
	(subject to access controls) this attribute with the value
	"3" (as well as values for other supported versions).

>4.1. Common Elements 
>    
>   This section describes the LDAPMessage envelope PDU (Protocol Data 
>   Unit) format, as well as data type definitions, which are used in the 
>   protocol operations. 
>    
>    
>4.1.1. Message Envelope 
>    
>   For the purposes of protocol exchanges, all protocol operations are 
>   encapsulated in a common envelope, the LDAPMessage, which is defined 
>   as follows: 
>    
>        LDAPMessage ::= SEQUENCE { 
>                messageID       MessageID, 
>                protocolOp      CHOICE { 
>                        bindRequest     BindRequest, 
>                        bindResponse    BindResponse, 
>                        unbindRequest   UnbindRequest, 
>                        searchRequest   SearchRequest, 
>                        searchResEntry  SearchResultEntry, 
>                        searchResDone   SearchResultDone, 
>                        searchResRef    SearchResultReference, 
>  
>                                      
>                        modifyRequest   ModifyRequest, 
>                        modifyResponse  ModifyResponse, 
>                        addRequest      AddRequest, 
>                        addResponse     AddResponse, 
>                        delRequest      DelRequest, 
>                        delResponse     DelResponse, 
>                        modDNRequest    ModifyDNRequest, 
>                        modDNResponse   ModifyDNResponse, 
>                        compareRequest  CompareRequest, 
>                        compareResponse CompareResponse, 
>                        abandonRequest  AbandonRequest, 
>                        extendedReq     ExtendedRequest, 
>                        extendedResp    ExtendedResponse, 
>                        ... }, 
>                controls        [0] Controls OPTIONAL } 
>    
>        MessageID ::= INTEGER (0 .. maxInt) 
>    
>        maxInt INTEGER ::= 2147483647 -- (2^^31 - 1) -- 
>    
>   The function of the LDAPMessage is to provide an envelope containing 
>   common fields required in all protocol exchanges. At this time the 
>   only common fields are the message ID and the controls. 
>    
>   If the server receives a PDU from the client in which the LDAPMessage 
>   SEQUENCE tag cannot be recognized, the messageID cannot be parsed, 
>   the tag of the protocolOp is not recognized as a request, or the 
>   encoding structures or lengths of data fields are found to be 
>   incorrect, then the server MAY return the Notice of Disconnection 
>   described in section 4.4.1, with resultCode protocolError, and MUST 
>   immediately close the connection.  

In some places, the document notes the code value, e.g. "protocolError (2)".
In other paces, it doesn't.  Suggest for consistency that either the
notes always be present or never be present.  (I prefer the latter.)

Also, the MAY implies that implementation of Notice of Disconnect
is OPTIONAL.  That is, servers support for graceful closure support 
is OPTIONAL.  It should be RECOMMENDED.  So, s/MAY/SHOULD.
 
>   In other cases where the client or server cannot parse a PDU, it 
>   SHOULD abruptly close the connection where further communication 
>   (including providing notice) would be pernicious. Otherwise, server 
>   implementations MUST return an appropriate response to the request, 
>   with the resultCode set to protocolError. 
>
>   The ASN.1 type Controls is defined in section 4.1.11. 
>    
>    
>4.1.1.1. Message ID 
>    
>   All LDAPMessage envelopes encapsulating responses contain the 
>   messageID value of the corresponding request LDAPMessage. 
>    
>   The message ID of a request MUST have a non-zero value different from 
>   the values of any other requests outstanding in the LDAP association 
>   of which this message is a part. The zero value is reserved for the 
>   unsolicited notification message. 
>    
>   Typical clients increment a counter for each request. 
>    
>   A client MUST NOT send a request with the same message ID as an 
>   earlier request on the same LDAP association unless it can be 
>   determined that the server is no longer servicing the earlier 
>   request. Otherwise the behavior is undefined. For operations that do 
>   not return responses (unbind, abandon, and abandoned operations), the 
>   client SHOULD assume the operation is in progress until a subsequent 
>   bind request completes. 
> 
> 
>4.1.2. String Types 
>    
>   The LDAPString is a notational convenience to indicate that, although 
>   strings of LDAPString type encode as OCTET STRING types, the 
>   [ISO10646] character set (a superset of [Unicode]) is used, encoded 
>   following the UTF-8 algorithm [RFC2279]. Note that in the UTF-8 

replace UTF-8 reference with draft-yergeau-rfc2279bis.

>   algorithm characters which are the same as ASCII (0x0000 through 
>   0x007F) are represented as that same ASCII character in a single 
>   byte.  The other byte values are used to form a variable-length 
>   encoding of an arbitrary character. 

Suggested replacement text:
	Note that Unicode characters U+0000 through U+007F are the
	same as ASCII 0 through 127, respectively, and have the same
	single octet encoding.  Other Unicode characters have a
	multiple-octet UTF-8 encoding.

(Add a U+ convention note above, borrow as needed from ldapprep.)

>        LDAPString ::= OCTET STRING -- UTF-8 encoded, 
>                                    -- ISO 10646 characters 
>    
>   The LDAPOID is a notational convenience to indicate that the 
>   permitted value of this string is a (UTF-8 encoded) dotted-decimal 
>   representation of an OBJECT IDENTIFIER. Although an LDAPOID is 
>   encoded as an OCTET STRING, values are limited to the definition of 
>   numericoid given in Section 1.3 of [Models]. 

Suggest you wrap the <numericoid> production in angle brackets as
I have done in this comment.  Likewise with other productions defined
using ABNF.

>        LDAPOID ::= OCTET STRING -- Constrained to numericoid [Models] 
>         
>   For example, 
>    
>        1.3.6.1.4.1.1466.1.2.3 
>    
>    
>4.1.3. Distinguished Name and Relative Distinguished Name 
>    
>   An LDAPDN and a RelativeLDAPDN are respectively defined to be the 
>   representation of a distinguished-name and a relative-distinguished-
>   name after encoding according to the specification in [LDAPDN]. 

drop the hyphens and say, in the prose, which productions they
are to conform to.  Suggest you do this in two paragraphs: one
of DNs and one for RDNs.

Also, add "(DN)" and "(RDN)" to introduce these terms for later use in
the document.

>    
>        LDAPDN ::= LDAPString  
>                   -- Constrained to distinguishedName [LDAPDN] 
>    
>        RelativeLDAPDN ::= LDAPString  
>                           -- Constrained to name-component [LDAPDN] 
>    
>    
>4.1.4. Attribute Descriptions 
>    
>   The definition and encoding rules for attribute descriptions are 
>   defined in Section 2.5 of [Models]. Briefly, an attribute description 
>   is an attribute type and zero or more options. 
>  
>                                      
>    
>        AttributeDescription ::= LDAPString 
>                                 -- Constrained to attributedescription 
>                                 -- [Models] 
>         
>   An AttributeDescriptionList describes a list of 0 or more attribute 
>   descriptions. (A list of zero elements has special significance in 
>   the Search request.) 
>    
>        AttributeDescriptionList ::= SEQUENCE OF 
>                AttributeDescription 
>    
> 
>4.1.5. Attribute Value 
>    
>   A field of type AttributeValue is an OCTET STRING containing an 
>   encoded attribute value data type.  The value is encoded according to 
>   its LDAP-specific encoding definition. The LDAP-specific encoding 
>   definitions for different syntaxes and attribute types may be found 
>   in other documents and in particular [Syntaxes]. 
> 
>        AttributeValue ::= OCTET STRING 
>    
>   Note that there is no defined limit on the size of this encoding; 
>   thus protocol values may include multi-megabyte attributes (e.g. 
>   photographs). 
>    
>   Attributes may be defined which have arbitrary and non-printable 
>   syntax. Implementations MUST NOT display nor attempt to decode as 
>   ASN.1, a value if its syntax is not known.

Drop the "as ASN.1".

>   The implementation may 
>   attempt to discover the subschema of the source entry, and retrieve 
>   the values of attributeTypes from it. 

s/the values/descriptions/
    
>   Clients MUST NOT send attribute values in a request that are not 
>   valid according to the syntax defined for the attributes. 
>    
>    
>4.1.6. Attribute Value Assertion 
>    
>   The AttributeValueAssertion type definition is similar to the one in 
>   the X.500 directory standards. It contains an attribute description 
>   and a matching rule assertion value suitable for that type. 
>    
>        AttributeValueAssertion ::= SEQUENCE { 
>                attributeDesc   AttributeDescription, 
>                assertionValue  AssertionValue } 
>    
>        AssertionValue ::= OCTET STRING 
>    
>   The syntax of the AssertionValue depends on the context of the LDAP 
>   operation being performed. For example, the syntax of the EQUALITY 
>   matching rule for an attribute is used when performing a Compare 
>   operation. Often this is the same syntax used for values of the 
>   attribute type, but in some cases the assertion syntax differs from 
>   the value syntax. See objectIdentiferFirstComponentMatch in 
>   [Syntaxes] for an example. 
>    
>    
>4.1.7. Attribute 
>    
>   An attribute consists of an attribute description and one or more 
>   values of that attribute description. (Though attributes MUST have at 
>   least one value when stored, due to access control restrictions the 
>   set may be empty when transferred from the server to the client. This 
>   is described in section 4.5.2, concerning the PartialAttributeList 
>   type.) 

This MUST is inappropriate (especially given that its inside of a
comment).  I suggest dealing not noting this here, but in the
discussion of PartialAttributeList.

    
>        Attribute ::= SEQUENCE { 
>                type    AttributeDescription, 
>                vals    SET OF AttributeValue } 

>   Each attribute value is distinct in the set (no duplicates). The set 
>   of attribute values is unordered. Implementations MUST NOT reply upon 
>   any apparent ordering being repeatable. 

This type is never explicitly used in the protocol.  I suggest
AttributeList be redefined
		AttributeList ::= SEQUENCE OF ATTRIBUTE

I also suggest adding:
	An attribute list is used to hold a set of related attributes
	(such as those of an entry).   While the type is defined as
	a SEQUENCE, no semantics are implied by the ordering.  Implementations
	MUST NOT rely on the ordering being repeatable.

Then I suggest defining PartialAttribute and PartialAttributeList.

    
>4.1.8. Matching Rule Identifier 
>    
>   Matching rules are defined in 4.1.3 of [Models]. A matching rule is 
>   identified in the LDAP protocol by the printable representation of 
>   either its numericoid, or one of its short name descriptors, e.g. 
>   "caseIgnoreIA5Match" or "1.3.6.1.4.1.453.33.33". 
>    
>        MatchingRuleId ::= LDAPString 
>    
>   Servers which support matching rules for use in the extensibleMatch 
>   search filter MUST list the matching rules they implement in 
>   subschema entries, using the matchingRules attributes. The server 
>   SHOULD also list there, using the matchingRuleUse attribute, the 
>   attribute types with which each matching rule can be used. More 
>   information is given in section 4.5 of [Syntaxes]. 
>    
>    
>4.1.9. Result Message 
>    
>   The LDAPResult is the construct used in this protocol to return 
>   success or failure indications from servers to clients. To various 
>   requests, servers will return responses of LDAPResult or responses 
>   containing the components of LDAPResult to indicate the final status 
>   of a protocol operation request. 
>    
>        LDAPResult ::= SEQUENCE { 
>                resultCode              ENUMERATED { 
>                        success                      (0), 
>                        operationsError              (1), 
>                        protocolError                (2), 
>                        timeLimitExceeded            (3), 
>                        sizeLimitExceeded            (4), 
>  
>                                      
>                        compareFalse                 (5), 
>                        compareTrue                  (6), 
>                        authMethodNotSupported       (7), 
>                        strongAuthRequired           (8), 
>                                        -- 9 reserved -- 
>                        referral                     (10), 
>                        adminLimitExceeded           (11), 
>                        unavailableCriticalExtension (12), 
>                        confidentialityRequired      (13), 
>                        saslBindInProgress           (14), 
>                        noSuchAttribute              (16), 
>                        undefinedAttributeType       (17), 
>                        inappropriateMatching        (18), 
>                        constraintViolation          (19), 
>                        attributeOrValueExists       (20), 
>                        invalidAttributeSyntax       (21), 
>                                        -- 22-31 unused -- 
>                        noSuchObject                 (32), 
>                        aliasProblem                 (33), 
>                        invalidDNSyntax              (34), 
>                        -- 35 reserved for undefined isLeaf -- 
>                        aliasDereferencingProblem    (36), 
>                                        -- 37-47 unused -- 
>                        inappropriateAuthentication  (48), 
>                        invalidCredentials           (49), 
>                        insufficientAccessRights     (50), 
>                        busy                         (51), 
>                        unavailable                  (52), 
>                        unwillingToPerform           (53), 
>                        loopDetect                   (54), 
>                                        -- 55-63 unused -- 
>                        namingViolation              (64), 
>                        objectClassViolation         (65), 
>                        notAllowedOnNonLeaf          (66), 
>                        notAllowedOnRDN              (67), 
>                        entryAlreadyExists           (68), 
>                        objectClassModsProhibited    (69), 
>                                -- 70 reserved for CLDAP -- 
>                        affectsMultipleDSAs          (71), 
>                                        -- 72-79 unused -- 
>                        other                        (80), 
>                        ... }, 
>                        -- 81-90 reserved for APIs -- 
>                matchedDN               LDAPDN, 
>                diagnosticMessage       LDAPString, 
>                referral                [3] Referral OPTIONAL } 
>    
>   The result codes enumeration is extensible as defined in Section 3.5 
>   of [LDAPIANA]. The meanings of the result codes are given in Appendix 
>   A. 
>    
>   The diagnosticMessage field of this construct may, at the server's 
>   option, be used to return a string containing a textual, human-
>   readable (terminal control and page formatting characters should be 
>   avoided) diagnostic message. As this diagnostic message is not 
>   standardized, implementations MUST NOT rely on the values returned. 
>   If the server chooses not to return a textual diagnostic, the 
>   diagnosticMessage field of the LDAPResult type MUST contain a zero 
>   length string. 

It might be better to s/contain a zero length string/be empty/.
    
>   For certain result codes (typically, but not restricted to 
>   noSuchObject, aliasProblem, invalidDNSyntax and 
>   aliasDereferencingProblem), the matchedDN field is set to the name of 
>   the lowest entry (object or alias) in the directory that was matched. 
>   If no aliases were dereferenced while attempting to locate the entry, 
>   this will be a truncated form of the name provided, or if aliases 
>   were dereferenced, of the resulting name, as defined in section 12.5 
>   of [X.511]. The matchedDN field contains a zero length string with 
>   all other result codes. 

Because of the "typically" above, suggest the last sentence be replaced
with:
	Otherwise the matchedDN field is empty.
    
>    
>4.1.10. Referral 
>    
>   The referral result code indicates that the contacted server does not 
>   hold the target entry of the request. The referral field is present 
>   in an LDAPResult if the LDAPResult.resultCode field value is 
>   referral, and absent with all other result codes. It contains one or 
>   more references to one or more servers or services that may be 
>   accessed via LDAP or other protocols. Referrals can be returned in 
>   response to any operation request (except unbind and abandon which do 
>   not have responses). At least one URL MUST be present in the 
>   Referral. 

s/URL/URI/ here and below (except when explicitly referring to an
LDAP URL).

>   During a search operation, after the baseObject is located, and 
>   entries are being evaluated, the referral is not returned. Instead, 
>   continuation references, described in section 4.5.3, are returned 
>   when the search scope spans multiple naming contexts, and several 
>   different servers would need to be contacted to complete the 
>   operation. 

>        Referral ::= SEQUENCE OF LDAPURL  -- one or more 
>    
>        LDAPURL ::= LDAPString -- limited to characters permitted in 
>                               -- URLs 
>    

s/LDAPURL/URIstring/ as the element is not restricted to LDAP URLs as
the name would otherwise imply.

>   If the client wishes to progress the operation, it MUST follow the 
>   referral by contacting one of the servers.  If multiple URLs are 
>   present, the client assumes that any URL may be used to progress the 
>   operation. 

The term "server" above may be too LDAP specific.  It may be better
to use the term "service".

>   URLs for servers implementing the LDAP protocol are written according 
>   to [LDAPURL]. If an alias was dereferenced, the <dn> part of the URL 
>   MUST be present, with the new target object name. If the <dn> part is 
>   present, the client MUST use this name in its next request to 
>   progress the operation, and if it is not present the client will use 
>   the same name as in the original request. Some servers (e.g. 
>   participating in distributed indexing) may provide a different filter 
>   in a referral for a search operation. If the filter part of the URL 
>   is present in an LDAPURL, the client MUST use this filter in its next 
>   request to progress this search, and if it is not present the client 
>   MUST use the same filter as it used for that search. Other aspects of 
>   the new request may be the same or different as the request which 
>   generated the referral. 

As discussed on the LDAPEXT when the namedref I-D (now RFC 3296)
was being considered for publication, the LDAP TS is flawed in
that it does not explictly say that absense other URL parts, such
as the scope part, have different semantics than those specified in
RFC 2255 yet provides examples which suggest different semantics of
other absent parts.  This has lead to interoperability problems.

It has also noted there have been interoperability problems when
the DN field has been absent.  This may be caused by the statement
"The SearchResultReference is of the same data type as the Referral"
which impies referrals and referrences have the same semantics.
Howver, an empty DN part in a reference is a continuation names
a root DSE but an empty DN part refers to the entry named in the
search.  

(It was noted that current DN referral semantic disallows one from
generating a referral (for a non-root DSE search) to a root DSE.
However, I don't think anyone ever explained why that capability
(or the capability to continue a search to the root DSE) would
be a useful.  Anyways, I only note this for completeness.)

To resolve the interoperability problems, I suggest the following
changes be made to the specification of references AND search
continuation refererences.
	1) expand the referral and reference text to say that absense
	scope part implies the scope of the search which requested the
	response.
	2) For all operations, RECOMMEND that dn part be provided
	3) For the search operation, RECOMMEND that the scope field
	also be provided.
	4) update examples to be consistent with RFC 3296

Alternatively, change the specification such that the LDAP URL
semantics used in the protocol are the same as defined in
RFC 2255.  That is, an empty DN refers always refers the
root DSE, an empty scope always means baseObject, etc..

>   Note that UTF-8 characters appearing in a DN or search filter may not 
>   be legal for URLs (e.g. spaces) and MUST be escaped using the % 
>   method in [RFC2396]. 

s/DN/DN part/
s/search filter/search filter part/

Actually, it might be better to replace the text with:
	Note that UTF-8 characters appearing in component values, such
	as DN and filter parts, of the URL MUST be escaped in accordance
	with [LDAPURL].
    
>   Other kinds of URLs may be returned, so long as the operation could 
>   be performed using that protocol. 
>    
>    
>4.1.11. Controls 
>    
>   A control is a way to specify extension information for an LDAP 
>   message. A control only alters the semantics of the message it is 
>   attached to. 
>    
>        Controls ::= SEQUENCE OF Control 
>    
>        Control ::= SEQUENCE { 
>                controlType             LDAPOID, 
>                criticality             BOOLEAN DEFAULT FALSE, 
>                controlValue            OCTET STRING OPTIONAL } 
>    
>   The controlType field MUST be a UTF-8 encoded dotted-decimal 
>   representation of an OBJECT IDENTIFIER which uniquely identifies the 
>   control.

Question?  Are there existing control extensions which use one OID
to identify both a request control and a paired response control.
If so (especially if any of these are standard track), the following
should be added ", or a request control and its paired response
control".

> This prevents conflicts between control names. 

s/MUST be a/is the/

>   The criticality field is either TRUE or FALSE and only applies to 
>   request messages that have a corresponding response message. For all 
>   other messages (such as abandonRequest, unbindRequest and all 
>   response messages), the criticality field is treated as FALSE. 

I think this may require some recoding of servers which don't treat
such critical request controls as non-critical.  I would rather just
say:
	For other messages (such as ...), the criticality field SHOULD
	be FALSE.

>   If the server recognizes the control type and it is appropriate for 
>   the operation, the server will make use of the control when 
>   performing the operation. 
>    
>   If the server does not recognize the control type or it is not 
>   appropriate for the operation, and the criticality field is TRUE, the 
>   server MUST NOT perform the operation, and MUST instead return the 
>   resultCode unavailableCriticalExtension. 

Replace with:

	If the server does not recongize the control type or it is
	not appropriate for the operation, and the criticality field
	is TRUE, the server MUST NOT perform the operation and MUST,
	for operations which have responses, return the resultCode
	unavailableCriticalExtension.

>   If the control is unrecognized or inappropriate but the criticality 
>   field is FALSE, the server MUST ignore the control. 
>    
>   The controlValue contains any information associated with the 
>   control, and its format is defined for the control. Implementations 
>   MUST be prepared to handle arbitrary contents of the controlValue 
>   octet string, including zero bytes.  It is absent only if there is no 
>   value information which is associated with a control of its type. 
>    
>   This document does not specify any controls. Controls may be 
>   specified in other documents. The specification of a control consists 
>   of: 

We either need to provide specifications requirements for
each extension mechanism (controls, notices, extended operations,
others) or none.

At this stage, I think it might be best to leave "Guidelines for
LDAP Extensions" to another document.

>   - the OBJECT IDENTIFIER assigned to the control, 
>    
>   - whether the control is always noncritical, always critical, or 
>     critical at the client's option, 

s/critical at the client's option/optionally critical/

>   - the format of the controlValue contents of the control, 

replace with
	- whether the control information associated with the control and,
	  the format of the controlValue contents,

>   - the semantics of the control, 
>    
>   - and optionally, semantics regarding the combination of the control 
>     with other controls. 

Move the "and" from beginning of the last item to the
end of the second to last item.

>   Servers list the controlType of all request controls they recognize 
>   in the supportedControl attribute [Models] in the root DSE. 
>    
>   Controls should not be combined unless the semantics of the 
>   combination has been specified.

Uppercase this SHOULD NOT.  That is, implementatoins SHOULD NOT combine
controls without understanding how they combine.

>   The semantics of control 
>   combinations, if specified, are generally found in the control 
>   specification most recently published. In the absence of combination 
>   semantics, the behavior of the operation is undefined.  

s/combination semantics/a specification of combination semantics/

>   Additionally, the order of a combination of controls in the SEQUENCE 
>   is ignored unless the control specification(s) describe(s) 
>   combination semantics. 

s/describe/prescribe/ ?  Or replace?
    Additionally, the order of a combination of controls in the    
    SEQUENCE implies no semantics unless the specification for        
    that combination defines order-dependent semantics.

>4.2. Bind Operation 
>    
>   The function of the Bind Operation is to allow authentication 
>   information to be exchanged between the client and server.  Prior to 
>   the first BindRequest, the implied identity is anonymous.  Refer to 
>   [AuthMeth] for the authentication-related semantics of this 
>   operation. 

I suggest dropping second sentence as it is covered in in [AuthMeth].
I suggest rewording the second sentence:

    Authententication and security related semantics of this          
    operation are detailed in [AuthMeth].

(I would not say the "implied identity is anonymous" but that
"the LDAP association is anonymous."  That is, the protocol
peers have not established their identities.  Anonymous is not
an identity.)

>   The Bind Request is defined as follows: 
>    
>        BindRequest ::= [APPLICATION 0] SEQUENCE { 
>                version                 INTEGER (1 .. 127), 
>                name                    LDAPDN, 
>                authentication          AuthenticationChoice } 
>    
>        AuthenticationChoice ::= CHOICE { 
>                simple                  [0] OCTET STRING, 
>                                         -- 1 and 2 reserved 
>                sasl                    [3] SaslCredentials, 
>                ... } 
>    
>        SaslCredentials ::= SEQUENCE { 
>                mechanism               LDAPString, 
>                credentials             OCTET STRING OPTIONAL } 
>    
>  
>                                      
>   Parameters of the Bind Request are: 
>    
>   - version: A version number indicating the version of the protocol 
>     to be used in this protocol association. This document describes 
>     version 3 of the LDAP protocol. Note that there is no version 
>     negotiation, and the client just sets this parameter to the 
>     version it desires.

Delete the word "just".

>     If the server does not support the specified 
>     version, it responds with protocolError in the resultCode field of 
>     the BindResponse. 
>    
>   - name: The name of the directory object that the client wishes to 
>     bind as. This field may take on a null value (a zero length 
>     string) for the purposes of anonymous binds ([AuthMeth] section 7) 
>     or when using SASL authentication ([AuthMeth] section 4.3). Server 
>     behavior is undefined when the name is a null value, simple 
>     authentication is used, and a password is specified.  The server 
>     SHOULD NOT perform any alias dereferencing in determining the 
>     object to bind as. 

delete the word "any".
spell SASL out on first use (in body).

>    
>   - authentication: information used to authenticate the name, if any, 
>     provided in the Bind Request. This type is extensible as defined 
>     in Section 3.6 of [LDAPIANA]. Servers that do not support a choice 
>     supplied by a client will return authMethodNotSupported in the 
>     result code of the BindResponse. The simple form of an 
>     AuthenticationChoice specifies a simple password to be used for 
>     authentication. To improve matching, applications SHOULD prepare 
>     textual strings used as passwords. Applications which prepare 
>     textural strings used as password are REQUIRED to prepare them by 
>     transcoding the string to [Unicode], apply [SASLprep], and encode 
>     as UTF-8. 

(see list comments)

>   Authorization is the use of this authentication information when 
>   performing operations. Authorization MAY be affected by factors 
>   outside of the LDAP Bind Request, such as lower layer security 
>   services. 

s/such as/such as factors provided by/

>    
>4.2.1. Processing of the Bind Request 
>    
>   Upon receipt of a BindRequest, the server MUST ensure there are no 
>   outstanding operations in progress on the connection (this simplifies 
>   server implementation).

The note implies the purpose of the MUST is simplify server
implementations.  Per RFC 2119, such MUSTs should be avoided.
However, the real purpose of this MUST is to ensure that operations
received prior to the bind are completed (or abandoned) before the
establishment of a new LDAP association.  The sentence needs some
word smithing.

>   The server then proceeds to authenticate the 
>   client in either a single-step, or multi-step bind process. Each step 
>   requires the server to return a BindResponse to indicate the status 
>   of authentication.  
>    
>   If the client did not bind before sending a request and receives an 
>   operationsError, it may then send a Bind Request. If this also fails 

s/operationsError/operationsError in response to that request/

>   or the client chooses not to bind on the existing connection, it may 
>   close the connection, reopen it and begin again by first sending a 
>   PDU with a Bind Request. This will aid in interoperating with servers 
>   implementing other versions of LDAP. 
>    
>   Clients MAY send multiple Bind Requests on a connection to change 
>   their credentials.

Down case this "MAY".

s/their credentials/authentication and/or security associations or
to complete a multi-stage bind process./

>   Authentication from earlier binds is subsequently 
>   ignored. A failed or abandoned Bind Operation has the effect of 
>   leaving the LDAP association in an anonymous state. To arrive at a 
>   known authentication state after abandoning a bind operation, clients 
>   may unbind, rebind, or make use of the BindResponse.

rebind implies making use of the BindRequest.
unbind, as used here, might be viewed as implying additional
requests may be sent on the same session.

I suggest:
    To arrive at a known authentication state after abandoning a      
    bind operation, the client must issue another bind request
    (or drop the connection and start over).


>   If a SASL 
>   transfer encryption or integrity mechanism has been negotiated, and 
>   that mechanism does not support the changing of credentials from one 
>   identity to another, then the client MUST instead establish a new 
>   connection. 
>    
>   For some SASL authentication mechanisms, it may be necessary for the 
>   client to invoke the BindRequest multiple times. This is indicated by 
>   the server sending a BindResponse with the resultCode set to 
>   saslBindInProgress. This indicates that the server requires the 
>   client to send a new bind request, with the same sasl mechanism, to 
>   continue the authentication process. If at any stage the client 
>   wishes to abort the bind process it MAY unbind and then drop the 
>   underlying connection. Clients MUST NOT invoke operations between two 
>   Bind Requests made as part of a multi-stage bind. 
>    
>   A client may abort a SASL bind negotiation by sending a BindRequest 
>   with a different value in the mechanism field of SaslCredentials, or 
>   an AuthenticationChoice other than sasl. 
>    
>   If the client sends a BindRequest with the sasl mechanism field as an 
>   empty string, the server MUST return a BindResponse with 
>   authMethodNotSupported as the resultCode. This will allow clients to 
>   abort a negotiation if it wishes to try again with the same SASL 
>   mechanism. 
>    
>    
>4.2.2. Bind Response 
>    
>   The Bind Response is defined as follows. 
>    
>        BindResponse ::= [APPLICATION 1] SEQUENCE { 
>             COMPONENTS OF LDAPResult, 
>             serverSaslCreds    [7] OCTET STRING OPTIONAL } 
>    
>   BindResponse consists simply of an indication from the server of the 
>   status of the client's request for authentication. 
>    
>   A successful bind operation is indicated by a BindResponse with a 
>   resultCode set to success (0). Otherwise, an appropriate resultCode 
>   is set in the BindResponse. For bind, the protocolError (2) 
>   resultCode may be used to indicate that the version number supplied 
>   by the client is unsupported. 
> 
>   If the client receives a BindResponse response where the resultCode 
>   was protocolError, it MUST close the connection as the server will be 
>   unwilling to accept further operations. (This is for compatibility 
>   with earlier versions of LDAP, in which the bind was always the first 
>   operation, and there was no negotiation.) 
>  
>   The serverSaslCreds are used as part of a SASL-defined bind mechanism 
>   to allow the client to authenticate the server to which it is 
>   communicating, or to perform "challenge-response" authentication. If 
>   the client bound with the simple choice, or the SASL mechanism does 
>   not require the server to return information to the client, then this 
>   field is not to be included in the result. 
>    
>    
>4.3. Unbind Operation 
>    
>   The function of the Unbind Operation is to terminate an LDAP 
>   association and connection. The Unbind Operation is defined as 
>   follows: 
>    
>        UnbindRequest ::= [APPLICATION 2] NULL 
>    
>   The Unbind Operation has no response defined. Upon transmission of an 
>   UnbindRequest, a protocol client MUST assume that the LDAP 
>   association is terminated.

and close the connection?   Or reword,
	Upon transmission of the UnbindRequest, the client is to consider
	the LDAP association terminated, MUST NOT transmit additional
	LDAP PDUs, and MUST close the connection.

A client shouldn't wait on the server.... it could be a long wait.

>   Upon receipt of an UnbindRequest, a 
>   protocol server MUST assume that the requesting client has terminated 
>   the association and that all outstanding requests may be discarded, 
>   and MUST close the connection. 

Reword,
	Upon receipt of an UnbindRequest, the server is to consider the
	LDAP associated terminated, MUST cease transmission of messages
	to the client, and MUST close the connection.  Any outstanding
	operations are, when possible, abandoned and, when not possible,
	completed without transmission of the response. 


>4.4. Unsolicited Notification 
>    
>   An unsolicited notification is an LDAPMessage sent from the server to 
>   the client which is not in response to any LDAPMessage received by 
>   the server. It is used to signal an extraordinary condition in the 
>   server or in the connection between the client and the server. The 
>   notification is of an advisory nature, and the server will not expect 
>   any response to be returned from the client. 
>    
>   The unsolicited notification is structured as an LDAPMessage in which 
>   the messageID is 0 and protocolOp is of the extendedResp form. The 
>   responseName field of the ExtendedResponse is present.  The LDAPOID 
>   value MUST be unique for this notification, and not be used in any 
>   other situation. 

Replace last two sentences with:
	The responseName field of the ExtendedResponse is always present
	and contains the dotted-decimal representation of the unique
	OBJECT IDENTIFIER corresponding to the notification.
	
>   One unsolicited notification (Notice of Disconnection) is defined in 
>   this document. 
>    
>    
>4.4.1. Notice of Disconnection 
>    
>   This notification may be used by the server to advise the client that 
>   the server is about to close the connection due to an error 
>   condition. Note that this notification is NOT a response to an unbind 
>   requested by the client: the server MUST follow the procedures of 
>   section 4.3.  This notification is intended to assist clients in 
>   distinguishing between an error condition and a transient network 
>   failure.  As with a connection close due to network failure, the 
>   client MUST NOT assume that any outstanding requests which modified 
>   the directory have succeeded or failed. 
>    
>   The responseName is 1.3.6.1.4.1.1466.20036, the response field is 
>   absent, and the resultCode is used to indicate the reason for the 
>   disconnection. 
>    
>   The following resultCode values have these meanings when used in this 
>   notification: 
>    
>   - protocolError: The server has received data from the client in 
>     which the LDAPMessage structure could not be parsed. 
>    
>   - strongAuthRequired: The server has detected that an established 
>     underlying security association protecting communication between 
>     the client and server has unexpectedly failed or been compromised. 
>    
>   - unavailable: This server will stop accepting new connections and 
>     operations on all existing connections, and be unavailable for an 
>     extended period of time. The client may make use of an alternative 
>     server. 
>    
>   After sending this notice, the server MUST close the connection. 

Reword:
	After sending this notice, the server is to consider the LDAP
	association terminated, MUST NOT transmit additional LDAP PDUs,
	and MUST close the connection.


>   After receiving this notice, the client MUST NOT transmit any further 
>   on the connection, and may abruptly close the connection. 

Reword:
	After receiving this notice, the client MUST cease transmitting
	messages to the server and close the connection.
    
>    
>4.5. Search Operation 
>    
>   The Search Operation allows a client to request that a search be 
>   performed on its behalf by a server.

I suggest:
	The Search Operation provides mechanism for a client to request
	and a server to return, subject to access controls and other
    restrictions, a set of entries matching a complex search criteria. 

>   This can be used to read 
>   attributes from a single entry, from entries immediately below a 
>   particular entry, or a whole subtree of entries. 
>    
>    
>4.5.1. Search Request 
>    
>   The Search Request is defined as follows: 
>    
>        SearchRequest ::= [APPLICATION 3] SEQUENCE { 
>                baseObject      LDAPDN, 
>                scope           ENUMERATED { 
>                        baseObject              (0), 
>                        singleLevel             (1), 
>                        wholeSubtree            (2) }, 
>                derefAliases    ENUMERATED { 
>                        neverDerefAliases       (0), 
>                        derefInSearching        (1), 
>                        derefFindingBaseObj     (2), 
>                        derefAlways             (3) }, 
>                sizeLimit       INTEGER (0 .. maxInt), 
>                timeLimit       INTEGER (0 .. maxInt), 
>                typesOnly       BOOLEAN, 
>                filter          Filter, 
>                attributes      AttributeDescriptionList } 
>    
>        Filter ::= CHOICE { 
>                and             [0] SET SIZE (1..MAX) OF Filter, 
>                or              [1] SET SIZE (1..MAX) OF Filter, 
>                not             [2] Filter, 
>                equalityMatch   [3] AttributeValueAssertion, 
>                substrings      [4] SubstringFilter, 
>                greaterOrEqual  [5] AttributeValueAssertion, 
>                lessOrEqual     [6] AttributeValueAssertion, 
>                present         [7] AttributeDescription, 
>                approxMatch     [8] AttributeValueAssertion, 
>                extensibleMatch [9] MatchingRuleAssertion } 
>    
>        SubstringFilter ::= SEQUENCE { 
>                type            AttributeDescription, 
>                -- at least one must be present, 
>                -- initial and final can occur at most once 
>                substrings      SEQUENCE OF CHOICE { 
>                        initial [0] AssertionValue, 
>                        any     [1] AssertionValue, 
>                        final   [2] AssertionValue } } 
>    
>        MatchingRuleAssertion ::= SEQUENCE { 
>                matchingRule    [1] MatchingRuleId OPTIONAL, 
>                type            [2] AttributeDescription OPTIONAL, 
>                matchValue      [3] AssertionValue, 
>                dnAttributes    [4] BOOLEAN DEFAULT FALSE } 
>    
>   Parameters of the Search Request are: 
>    
>   - baseObject: An LDAPDN that is the base object entry relative to 
>     which the search is to be performed. 
>    
>   - scope: An indicator of the scope of the search to be performed. 
>     The semantics of the possible values of this field are identical 
>     to the semantics of the scope field in the X.511 Search Operation. 

Describe each of the possible values of this field in this document and
then note that they are the same as those used in the X.511 operation.

>   - derefAliases: An indicator as to how alias objects (as defined in 
>     [X.501]) are to be handled in searching. The semantics of the 
>     possible values of this field are: 
>    
>             neverDerefAliases: Do not dereference aliases in searching 
>             or in locating the base object of the search. 
>    
>             derefInSearching: While searching, dereference any alias 
>             object subordinate to the base object which is also in the 
>             search scope. The filter is applied to the dereferenced 
>             object(s). If the search scope is wholeSubtree, the search 
>             continues in the subtree of any dereferenced object. 
>             Aliases in that subtree are also dereferenced. Servers 
>             SHOULD detect looping in this process to prevent denial of 
>             service attacks and duplicate entries. 
>              
>  
>                                      
>             derefFindingBaseObj: Dereference aliases in locating the 
>             base object of the search, but not when searching 
>             subordinates of the base object. 
>    
>             derefAlways: Dereference aliases both in searching and in 
>             locating the base object of the search. 
>    
>   - sizeLimit: A size limit that restricts the maximum number of 
>     entries to be returned as a result of the search. A value of 0 in 
>     this field indicates that no client-requested size limit 
>     restrictions are in effect for the search. Servers may enforce a 
>     maximum number of entries to return. 
>    
>   - timeLimit: A time limit that restricts the maximum time (in 
>     seconds) allowed for a search. A value of 0 in this field 
>     indicates that no client-requested time limit restrictions are in 
>     effect for the search. 

As with sizeLimit, may servers enforce a maximun time for the search?
    
>   - typesOnly: An indicator as to whether search results will contain 
>     both attribute descriptions and values, or just attribute 
>     descriptions.

s/will/are to/

>     Setting this field to TRUE causes only attribute 
>     descriptions (no values) to be returned. Setting this field to 
>     FALSE causes both attribute descriptions and values to be 
>     returned. 
>    
>   - filter: A filter that defines the conditions that must be 
>     fulfilled in order for the search to match a given entry. 
>      
>     The 'and', 'or' and 'not' choices can be used to form combinations 
>     of filters. At least one filter element MUST be present in an 
>     'and' or 'or' choice. The others match against individual 
>     attribute values of entries in the scope of the search. 
>     (Implementor's note: the 'not' filter is an example of a tagged 
>     choice in an implicitly-tagged module. In BER this is treated as 
>     if the tag was explicit.) 
>    
>     A server MUST evaluate filters according to the three-valued logic 
>     of X.511 (1993) section 7.8.1. In summary, a filter is evaluated 
>     to either "TRUE", "FALSE" or "Undefined". If the filter evaluates 
>     to TRUE for a particular entry, then the attributes of that entry 
>     are returned as part of the search result (subject to any 
>     applicable access control restrictions). If the filter evaluates 
>     to FALSE or Undefined, then the entry is ignored for the search. 
>      
>     A filter of the "and" choice is TRUE if all the filters in the SET 
>     OF evaluate to TRUE, FALSE if at least one filter is FALSE, and 
>     otherwise Undefined. A filter of the "or" choice is FALSE if all 
>     of the filters in the SET OF evaluate to FALSE, TRUE if at least 
>     one filter is TRUE, and Undefined otherwise. A filter of the "not" 
>     choice is TRUE if the filter being negated is FALSE, FALSE if it 
>     is TRUE, and Undefined if it is Undefined. 
>      
>     The present match evaluates to TRUE where there is an attribute or 
>     subtype of the specified attribute description present in an 
>     entry, and FALSE otherwise (including a presence test with an 
>     unrecognized attribute description.) 
>      
>     The matching rule for equalityMatch filter items is defined by the 
>     EQUALITY matching rule for the attribute type. 
>    
>     The matching rule for AssertionValues in a substrings filter item 
>     is defined by the SUBSTR matching rule for the attribute type. 
>    
>     The matching rule for greaterOrEqual and lessOrEqual filter items 
>     is defined by the ORDERING matching rule for the attribute type. 
>    
>     The matching semantics for approxMatch filter items is 
>     implementation-defined. If approximate matching is not supported 
>     by the server, the filter item should be treated as an 
>     equalityMatch. 

Actually, approxMatch is not 100% implementation defined.   In
particular, the implementation must ensure that all values which
match per the equality rule match per the approximate rule.

>     The extensibleMatch is new in this version of LDAP. If the 
>     matchingRule field is absent, the type field MUST be present, and 
>     the equality match is performed for that type. If the type field 
>     is absent and matchingRule is present, the matchValue is compared 
>     against all attributes in an entry which support that
>     matchingRule, and the matchingRule determines the syntax for the
>     assertion value (the filter item evaluates to TRUE if it matches 
>     with at least one attribute in the entry, FALSE if it does not 
>     match any attribute in the entry, and Undefined if the 
>     matchingRule is not recognized or the assertionValue cannot be 
>     parsed.)

replace "cannot be parsed" with "is invalid."   Also, this shouldn't
be a comment (e.g., remove the wrapping parens).

>     If the type field is present and matchingRule is present, 
>     the matchingRule MUST be one permitted for use with that type, 
>     otherwise the filter item is undefined. If the dnAttributes field 
>     is set to TRUE, the match is applied against all the 
>     AttributeValueAssertions in an entry's distinguished name as well, 
>     and also evaluates to TRUE if there is at least one attribute in 
>     the distinguished name for which the filter item evaluates to 
>     TRUE. (Editors note: The dnAttributes field is present so that 
>     there does not need to be multiple versions of generic matching 
>     rules such as for word matching, one to apply to entries and 
>     another to apply to entries and dn attributes as well). 
>      
>     A filter item evaluates to Undefined when the server would not be 
>     able to determine whether the assertion value matches an entry. If 
>     an attribute description in an equalityMatch, substrings, 
>     greaterOrEqual, lessOrEqual, approxMatch or extensibleMatch filter 
>     is not recognized by the server, a matching rule id in the 
>     extensibleMatch is not recognized by the server, the assertion 
>     value cannot be parsed, or the type of filtering requested is not 
>     implemented, then the filter is Undefined.

s/parsed/invalid/

>     Thus for example if a 
>     server did not recognize the attribute type shoeSize, a filter of 
>     (shoeSize=*) would evaluate to FALSE, and the filters 
>     (shoeSize=12), (shoeSize>=12) and (shoeSize<=12) would evaluate to 
>     Undefined. 
>      
>     Servers MUST NOT return errors if attribute descriptions or 
>     matching rule ids are not recognized, or assertion values cannot 
>     be parsed. More details of filter processing are given in section 
>     7.8 of [X.511]. 

"Cannot be parsed" can mean:
	1) the assertion value is invalid or
	2) the server does not support the assertion syntax.


We likely should elaborate on what "cannot be parsed" means.

>   - attributes: A list of the attributes to be returned from each 
>     entry which matches the search filter. There are two special 
>     values which may be used: an empty list with no attributes, and 
>     the attribute description string "*". Both of these signify that 
>     all user attributes are to be returned. (The "*" allows the client 
>     to request all user attributes in addition to any specified 
>     operational attributes). 
>      
>     Attributes MUST be named at most once in the list, and are 
>     returned at most once in an entry. If there are attribute 
>     descriptions in the list which are not recognized, they are 
>     ignored by the server. 
>      
>     If the client does not want any attributes returned, it can 
>     specify a list containing only the attribute with OID "1.1". This 
>     OID was chosen arbitrarily and does not correspond to any 
>     attribute in use. 

This OID was not chosen arbitrarily.  It was choose because it does
not, and will never, correspond to any attribute in use.  So, replace
the sentence with:
	(This OID was choosen because it is retired.)

(It would be nice if we could provide an informative reference to
some document which states 1.1 is retired.)

>     Client implementors should note that even if all user attributes 
>     are requested, some attributes of the entry may not be included in 
>     search results due to access controls or other restrictions. 

s/some attribute/some attribute (and/or some values of some attributes)/

>     Furthermore, servers will not return operational attributes, such 
>     as objectClasses or attributeTypes, unless they are listed by 
>     name, since there may be extremely large number of values for 
>     certain operational attributes. (A list of operational attributes 
>     for use in LDAP is given in [Syntaxes].) 
>    
>   Note that an X.500 "list"-like operation can be emulated by the 
>   client requesting a one-level LDAP search operation with a filter 
>   checking for the presence of the objectClass attribute, and that an 
>   X.500 "read"-like operation can be emulated by a base object LDAP 
>   search operation with the same filter. A server which provides a 
>   gateway to X.500 is not required to use the Read or List operations, 
>   although it may choose to do so, and if it does, it must provide the 
>   same semantics as the X.500 search operation. 
>    
>    
>4.5.2. Search Result 
>    
>   The results of the search attempted by the server upon receipt of a 
>   Search Request are returned in Search Responses, which are LDAP 
>   messages containing either SearchResultEntry, SearchResultReference, 
>   or SearchResultDone data types. 

Suggest the above sentence be reworded (with further edits below).
	The results of the search operation are returned by the server
	in a series of response PDUs:  zero or more searchResultEntry
	or SearchResultReference messages followed by one searchResultDone
	messages.
	
>    
>        SearchResultEntry ::= [APPLICATION 4] SEQUENCE { 
>                objectName      LDAPDN, 
>                attributes      PartialAttributeList } 
>    
>        PartialAttributeList ::= SEQUENCE OF SEQUENCE { 
>                type    AttributeDescription, 
>                vals    SET OF AttributeValue } 
>  
>                                      
>        -- implementors should note that the PartialAttributeList may 
>        -- have zero elements (if none of the attributes of that entry 
>        -- were requested, or could be returned), and that the vals set 
>        -- may also have zero elements (if types only was requested, or 
>        -- all values were excluded from the result.) 
>    
>        SearchResultReference ::= [APPLICATION 19] SEQUENCE OF LDAPURL 
>        -- at least one LDAPURL element must be present 
>    
>        SearchResultDone ::= [APPLICATION 5] LDAPResult 
>    
>   Upon receipt of a Search Request, a server will perform the necessary 
>   search of the DIT. 

(Spell out DIT on first use.)

This sentence is somewhat redundant with statements above...
but note that a search is not required to perform the necessary
search (for instance, it could return an busy error). 

>   If the LDAP association is operating over a connection-oriented 
>   transport such as TCP, the server will return to the client a 
>   sequence of responses in separate LDAP messages.

As LDAP is "designed for connection-oriented transports" (per 5.2),
think we can drop the If clause.  If and when there is a specification
for connectonless LDAPv3, that specification needs to define how
the LDAP PDUs defined in this document are mapped onto the transport.
(Or, like CLDAPv2, can define its own PDUs). 

>   There may be zero or 
>   more responses containing SearchResultEntry, one for each entry found 
>   during the search. There may also be zero or more responses 
>   containing SearchResultReference, one for each area not explored by 
>   this server during the search. The SearchResultEntry and 
>   SearchResultReference PDUs may come in any order. Following all the 
>   SearchResultReference responses and all SearchResultEntry responses 
>   to be returned by the server, the server will return a response 
>   containing the SearchResultDone, which contains an indication of 
>   success, or detailing any errors that have occurred. 
>    
>   Each entry returned in a SearchResultEntry will contain all 
>   appropriate attributes as specified in the attributes field of the 
>   Search Request. Return of attributes is subject to access control and 
>   other administrative policy. 
>    
>   Some attributes may be constructed by the server and appear in a 
>   SearchResultEntry attribute list, although they are not stored 
>   attributes of an entry. Clients SHOULD NOT assume that all attributes 
>   can be modified, even if permitted by access control. 
>    
>   If the server's schema defines a textual name for an attribute type, 
>   it SHOULD use a textual name for attributes of that attribute type by 
>   specifying one of the textual names as the value of the attribute 
>   type. Otherwise, the server uses the object identifier for the 
>   attribute type by specifying the object identifier, in ldapOID form, 
>   as the value of attribute type. If the server determines that 
>   returning a textual name will cause interoperability problems, it 
>   SHOULD return the ldapOID form of the attribute type. 

"ldapOID form"?  I think you mean <numericoid> form.

>4.5.3. Continuation References in the Search Result 
>    
>   If the server was able to locate the entry referred to by the 
>   baseObject but was unable to search all the entries in the scope at 
>   and under the baseObject, the server may return one or more 
>   SearchResultReference entries, each containing a reference to another 
>   set of servers for continuing the operation. A server MUST NOT return 
>   any SearchResultReference if it has not located the baseObject and 
>   thus has not searched any entries; in this case it would return a 
>   SearchResultDone containing a referral resultCode. 
>    
>   If a server holds a copy or partial copy of the subordinate naming 
>   context, it may use the search filter to determine whether or not to 
>   return a SearchResultReference response. Otherwise 
>   SearchResultReference responses are always returned when in scope. 
>    
>   The SearchResultReference is of the same data type as the Referral. 
>   URLs for servers implementing the LDAP protocol are written according 
>   to [LDAPURL]. The <dn> part MUST be present in the URL, with the new 
>   target object name. The client MUST use this name in its next 
>   request. Some servers (e.g. part of a distributed index exchange 
>   system) may provide a different filter in the URLs of the 
>   SearchResultReference. If the filter part of the URL is present in an 
>   LDAP URL, the client MUST use the new filter in its next request to 
>   progress the search, and if the filter part is absent the client will 
>   use again the same filter. If the originating search scope was 
>   singleLevel, the scope part of the URL will be baseObject. Other 
>   aspects of the new search request may be the same or different as the 
>   search which generated the continuation references. 
>   Other kinds of URLs may be returned so long as the operation could be 
>   performed using that protocol. 

See referral comments.
    
>   The name of an unexplored subtree in a SearchResultReference need not 
>   be subordinate to the base object. 
>    
>   In order to complete the search, the client MUST issue a new search 
>   operation for each SearchResultReference that is returned. Note that 
>   the abandon operation described in section 4.11 applies only to a 
>   particular operation sent on an association between a client and 
>   server, and if the client has multiple outstanding search operations, 
>   it MUST abandon each operation individually. 

I suggest that the MUSTs here be dropped. 
	s/MUST issue/issues/
	s/it MUST abandon each operation individually
	 /each operation needs to be separately abandoned/

>4.5.3.1. Example 
>    

See referral comments.

>   For example, suppose the contacted server (hosta) holds the entry 
>   "DC=Example,DC=NET" and the entry "CN=Manager,DC=Example,DC=NET". It 
>   knows that either LDAP-capable servers (hostb) or (hostc) hold 
>   "OU=People,DC=Example,DC=NET" (one is the master and the other server 
>   a shadow), and that LDAP-capable server (hostd) holds the subtree 
>   "OU=Roles,DC=Example,DC=NET". If a subtree search of 
>   "DC=Example,DC=NET" is requested to the contacted server, it may 
>   return the following: 
>    
>     SearchResultEntry for DC=Example,DC=NET 
>     SearchResultEntry for CN=Manager,DC=Example,DC=NET 
>     SearchResultReference { 
>       ldap://hostb/OU=People,DC=Example,DC=NET 
>       ldap://hostc/OU=People,DC=Example,DC=NET 
>     } 
>     SearchResultReference { 
>       ldap://hostd/OU=Roles,DC=Example,DC=NET 
>     } 
>     SearchResultDone (success) 
>    
>   Client implementors should note that when following a 
>   SearchResultReference, additional SearchResultReference may be 
>   generated. Continuing the example, if the client contacted the server 
>   (hostb) and issued the search for the subtree 
>   "OU=People,DC=Example,DC=NET", the server might respond as follows: 
>    
>     SearchResultEntry for OU=People,DC=Example,DC=NET 
>     SearchResultReference { 
>       ldap://hoste/OU=Managers,OU=People,DC=Example,DC=NET 
>     } 
>     SearchResultReference { 
>       ldap://hostf/OU=Consultants,OU=People,DC=Example,DC=NET 
>     } 
>     SearchResultDone (success) 
>    
>   If the contacted server does not hold the base object for the search, 
>   then it will return a referral to the client. For example, if the 
>   client requests a subtree search of "DC=Example,DC=ORG" to hosta, the 
>    
>     SearchResultDone (referral) { 
>       ldap://hostg/DC=Example,DC=ORG??sub 
>     } 
>    
>    
>4.6. Modify Operation 
>    
>   The Modify Operation allows a client to request that a modification 
>   of an entry be performed on its behalf by a server. The Modify 
>   Request is defined as follows: 
>    
>        ModifyRequest ::= [APPLICATION 6] SEQUENCE { 
>                object          LDAPDN, 
>                modification    SEQUENCE OF SEQUENCE { 
>                        operation       ENUMERATED { 
>                                                add     (0), 
>                                                delete  (1), 
>                                                replace (2) }, 
>                        modification    AttributeTypeAndValues } } 
>    
>        AttributeTypeAndValues ::= SEQUENCE { 
>                type    AttributeDescription, 
>                vals    SET OF AttributeValue } 
>    
>   Parameters of the Modify Request are: 
>    
>   - object: The object to be modified. The value of this field 
>     contains the DN of the entry to be modified. The server will not 
>     perform any alias dereferencing in determining the object to be 
>     modified. 

s/The object/The Distinguished Name of the object/ 

(this partially aligns the text with that of Add.entry description,
more work is likely need to align Modify.object, Add.entry, and
other DN field texts

>   - modification: A list of modifications to be performed on the 
>     entry. The entire list of entry modifications MUST be performed in 
>     the order they are listed, as a single atomic operation. While 
>     individual modifications may violate the directory schema, the 
>     resulting entry after the entire list of modifications is 
>     performed MUST conform to the requirements of the directory 
>     schema. The values that may be taken on by the 'operation' field 
>     in each modification construct have the following semantics 
>     respectively: 
>    
>             add: add values listed to the given attribute, creating the 
>             attribute if necessary; 
>    
>             delete: delete values listed from the given attribute, 
>             removing the entire attribute if no values are listed, or 
>             if all current values of the attribute are listed for 
>             deletion; 
>    
>             replace: replace all existing values of the given attribute 
>             with the new values listed, creating the attribute if it 
>             did not already exist. A replace with no value will delete 
>             the entire attribute if it exists, and is ignored if the 
>             attribute does not exist. 
>    
>   The result of the modification attempted by the server upon receipt 
>   of a Modify Request is returned in a Modify Response, defined as 
>   follows: 
>    
>        ModifyResponse ::= [APPLICATION 7] LDAPResult 
>    
>   Upon receipt of a Modify Request, a server will perform the necessary 
>   modifications to the DIT. 

Note that a server is not required to perform the modifications
to the DIT (for instance, it could return an busy error). 

>   The server will return to the client a single Modify Response 
>   indicating either the successful completion of the DIT modification, 
>   or the reason that the modification failed. Note that due to the 
>   requirement for atomicity in applying the list of modifications in 
>   the Modify Request, the client may expect that no modifications of 
>   the DIT have been performed if the Modify Response received indicates 
>   any sort of error, and that all requested modifications have been 
>   performed if the Modify Response indicates successful completion of 
>   the Modify Operation. If the association changes or the connection 
>   fails, whether the modification occurred or not is indeterminate. 
>    
>   The Modify Operation cannot be used to remove from an entry any of 
>   its distinguished values, those values which form the entry's 
>   relative distinguished name. An attempt to do so will result in the 
>   server returning the error notAllowedOnRDN. The Modify DN Operation 
>   described in section 4.9 is used to rename an entry. 
>    
>   Note that due to the simplifications made in LDAP, there is not a 
>   direct mapping of the modifications in an LDAP ModifyRequest onto the 
>   EntryModifications of a DAP ModifyEntry operation, and different 
>   implementations of LDAP-DAP gateways may use different means of 
>   representing the change. If successful, the final effect of the 
>   operations on the entry MUST be identical. 
>    
>    
>4.7. Add Operation 
>    
>   The Add Operation allows a client to request the addition of an entry 
>   into the directory. The Add Request is defined as follows: 
>    
>        AddRequest ::= [APPLICATION 8] SEQUENCE { 
>                entry           LDAPDN, 
>                attributes      AttributeList } 
>    
>        AttributeList ::= SEQUENCE OF SEQUENCE { 
>                type    AttributeDescription, 
>                vals    SET OF AttributeValue } 
>    
>   Parameters of the Add Request are: 
>    
>   - entry: the Distinguished Name of the entry to be added. Note that 
>     the server will not dereference any aliases in locating the entry 
>     to be added. 
>    
>   - attributes: the list of attributes that make up the content of the 
>     entry being added. Clients MUST include distinguished values 
>     (those forming the entry's own RDN) in this list, the objectClass 
>     attribute, and values of any mandatory attributes of the listed 
>     object classes. Clients MUST NOT supply NO-USER-MODIFICATION 
>     attributes such as the createTimestamp or creatorsName attributes, 
>     since the server maintains these automatically. 
>    
>   The entry named in the entry field of the AddRequest MUST NOT exist 
>   for the AddRequest to succeed. The immediate superior (parent) of the 
>   object and alias entries to be added MUST exist. For example, if the 
>   client attempted to add "CN=JS,DC=Example,DC=NET", the 
>   "DC=Example,DC=NET" entry did not exist, and the "DC=NET" entry did 
>   exist, then the server would return the error noSuchObject with the 
>   matchedDN field containing "DC=NET". If the parent entry exists but 
>   is not in a naming context held by the server, the server SHOULD 
>   return a referral to the server holding the parent entry. 
>    
>   Server implementations SHOULD NOT restrict where entries can be 
>   located in the directory unless DIT structure rules are in place. 
>   Some servers MAY allow the administrator to restrict the classes of 
>   entries which can be added to the directory. 

Drop the MAY.

>   Upon receipt of an Add Request, a server will attempt to add the 
>   requested entry. The result of the add attempt will be returned to 
>   the client in the Add Response, defined as follows: 
>    
>        AddResponse ::= [APPLICATION 9] LDAPResult 
>    
>   A response of success indicates that the new entry is present in the 
>   directory. 
>    
>    
>4.8. Delete Operation 
>    
>   The Delete Operation allows a client to request the removal of an 
>   entry from the directory. The Delete Request is defined as follows: 
>    
>        DelRequest ::= [APPLICATION 10] LDAPDN 
>    
>   The Delete Request consists of the Distinguished Name of the entry to 
>   be deleted. Note that the server will not dereference aliases while 
>   resolving the name of the target entry to be removed, and that only 
>   leaf entries (those with no subordinate entries) can be deleted with 
>   this operation. 
>    
>   The result of the delete attempted by the server upon receipt of a 
>   Delete Request is returned in the Delete Response, defined as 
>   follows: 
>    
>        DelResponse ::= [APPLICATION 11] LDAPResult 
>    
>   Upon receipt of a Delete Request, a server will attempt to perform 
>   the entry removal requested. The result of the delete attempt will be 
>   returned to the client in the Delete Response. 
>    
>    
>4.9. Modify DN Operation 
>    
>   The Modify DN Operation allows a client to change the leftmost (least 
>   significant) component of the name of an entry in the directory, 
>   and/or to move a subtree of entries to a new location in the 
>   directory. The Modify DN Request is defined as follows: 
>    
>        ModifyDNRequest ::= [APPLICATION 12] SEQUENCE { 
>                entry           LDAPDN, 
>                newrdn          RelativeLDAPDN, 
>                deleteoldrdn    BOOLEAN, 
>                newSuperior     [0] LDAPDN OPTIONAL } 
>    
>   Parameters of the Modify DN Request are: 
>    
>   - entry: the Distinguished Name of the entry to be changed. This 
>     entry may or may not have subordinate entries. Note that the 
>     server will not dereference any aliases in locating the entry to 
>     be changed. 
>    
>   - newrdn: the RDN that will form the leftmost component of the new 
>     name of the entry. 
>    
>   - deleteoldrdn: a boolean parameter that controls whether the old 
>     RDN attribute values are to be retained as attributes of the 
>     entry, or deleted from the entry. 
>    
>   - newSuperior: if present, this is the Distinguished Name of an 
>     existing object entry which becomes the immediate superior 
>     (parent)of the existing entry. 
>    
>   The result of the name change attempted by the server upon receipt of 
>   a Modify DN Request is returned in the Modify DN Response, defined as 
>   follows: 
>    
>        ModifyDNResponse ::= [APPLICATION 13] LDAPResult 
>    
>   Upon receipt of a ModifyDNRequest, a server will attempt to perform 
>   the name change. The result of the name change attempt will be 
>   returned to the client in the Modify DN Response. 
>    
>   For example, if the entry named in the "entry" parameter was "cn=John 
>   Smith,c=US", the newrdn parameter was "cn=John Cougar Smith", and the 
>   newSuperior parameter was absent, then this operation would attempt 
>   to rename the entry to be "cn=John Cougar Smith,c=US". If there was 
>   already an entry with that name, the operation would fail with error 
>   code entryAlreadyExists. 
>    
>   The object named in newSuperior MUST exist. For example, if the 
>   client attempted to add "CN=JS,DC=Example,DC=NET", the 
>   "DC=Example,DC=NET" entry did not exist, and the "DC=NET" entry did 
>   exist, then the server would return the error noSuchObject with the 
>   matchedDN field containing "DC=NET". 
> 
>   If the deleteoldrdn parameter is TRUE, the values forming the old RDN 
>   are deleted from the entry. If the deleteoldrdn parameter is FALSE, 
>   the values forming the old RDN will be retained as non-distinguished 
>   attribute values of the entry. The server may not perform the 
>   operation and return an error code if the setting of the deleteoldrdn 
>   parameter would cause a schema inconsistency in the entry. 
>    
>   Note that X.500 restricts the ModifyDN operation to only affect 
>   entries that are contained within a single server. If the LDAP server 
>   is mapped onto DAP, then this restriction will apply, and the 
>   resultCode affectsMultipleDSAs will be returned if this error 
>   occurred. In general clients MUST NOT expect to be able to perform 
>   arbitrary movements of entries and subtrees between servers. 

Add comma after "In general".

I suggest replacing "between servers" with "between naming contexts."
Or reword it "between servers or between naming contexts."  Clients
cannot expect servers to move entries between naming contexts (even
where the server masters both).

>4.10. Compare Operation 
>    
>   The Compare Operation allows a client to compare an assertion 
>   provided with an entry in the directory. The Compare Request is 
>   defined as follows: 
>    
>        CompareRequest ::= [APPLICATION 14] SEQUENCE { 
>                entry           LDAPDN, 
>                ava             AttributeValueAssertion } 
>    
>   Parameters of the Compare Request are: 
>  
>   - entry: the name of the entry to be compared with. Note that the 
>     server SHOULD NOT dereference any aliases in locating the entry to 
>     be compared with. 
>    
>   - ava: the assertion with which an attribute in the entry is to be 
>     compared. 
>    
>   The result of the compare attempted by the server upon receipt of a 
>   Compare Request is returned in the Compare Response, defined as 

>    
>        CompareResponse ::= [APPLICATION 15] LDAPResult 
>    
>   Upon receipt of a Compare Request, a server will attempt to perform 
>   the requested comparison using the EQUALITY matching rule for the 
>   attribute type. The result of the comparison will be returned to the 
>   client in the Compare Response. Note that errors and the result of 
>   comparison are all returned in the same construct. 
>    
>   Note that some directory systems may establish access controls which 
>   permit the values of certain attributes (such as userPassword) to be 
>   compared but not interrogated by other means. 
>    
>    
>4.11. Abandon Operation 
>    
>   The function of the Abandon Operation is to allow a client to request 
>   that the server abandon an outstanding operation. The Abandon Request 
>   is defined as follows: 
>    
>        AbandonRequest ::= [APPLICATION 16] MessageID 
>    
>   The MessageID MUST be that of an operation which was requested 
>   earlier in this LDAP association. The abandon request itself has its 
>   own message id. This is distinct from the id of the earlier operation 
>   being abandoned. 
>    
>   There is no response defined in the Abandon Operation. Upon 
>   transmission of an Abandon Operation, the server MAY abandon the 
>   operation identified by the Message ID in the Abandon Request. 
>   Operation responses are not sent for successfully abandoned 
>   operations. Clients can determine that an operation has been 
>   abandoned by performing a subsequent bind operation. 
>    
>   Abandon and Unbind operations cannot be abandoned. The ability to 
>   abandon other (particularly update) operations is at the discretion 
>   of the server. 
>    
>   In the event that a server receives an Abandon Request on a Search 
>   Operation in the midst of transmitting responses to the search, that 
>   server MUST cease transmitting entry responses to the abandoned 
>   request immediately, and MUST NOT send the SearchResponseDone. Of 
>   course, the server MUST ensure that only properly encoded LDAPMessage 
>   PDUs are transmitted. 
>    
>   Clients MUST NOT send abandon requests for the same operation 
>   multiple times, and MUST also be prepared to receive results from 
>   operations it has abandoned (since these may have been in transit 
>   when the abandon was requested, or are not able to be abandoned). 
>    
>   Servers MUST discard abandon requests for message IDs they do not 
>   recognize, for operations which cannot be abandoned, and for 
>   operations which have already been abandoned. 

This section should like state:
	The Abandon operation applicability is limited to use cases
	where the client does not require a clear indication of
	its outcome.

>4.12. Extended Operation 
>    
>   An extension mechanism has been added in this version of LDAP, in 
>   order to allow additional operations to be defined for services not 
>   available elsewhere in this protocol, for instance digitally signed 
>   operations and results. 
>    
>   The extended operation allows clients to make requests and receive 
>   responses with predefined syntaxes and semantics. These may be 
>   defined in RFCs or be private to particular implementations. Each 
>   request MUST have a unique OBJECT IDENTIFIER assigned to it. 
>    
>        ExtendedRequest ::= [APPLICATION 23] SEQUENCE { 
>                requestName      [0] LDAPOID, 
>                requestValue     [1] OCTET STRING OPTIONAL } 
>    
>   The requestName is a dotted-decimal representation of the OBJECT 
>   IDENTIFIER corresponding to the request. The requestValue is 
>   information in a form defined by that request, encapsulated inside an 
>   OCTET STRING. 
>    
>   The server will respond to this with an LDAPMessage containing the 
>   ExtendedResponse. 
>    
>        ExtendedResponse ::= [APPLICATION 24] SEQUENCE { 
>                COMPONENTS OF LDAPResult, 
>                responseName     [10] LDAPOID OPTIONAL, 
>                response         [11] OCTET STRING OPTIONAL } 
>    
>   If the server does not recognize the request name, it MUST return 
>   only the response fields from LDAPResult, containing the 
>   protocolError result code. 

I note that responseName field would not be provided in this case.
Also, it may not be provided where a response was not assigned an
OID.  I generally recommend that extended operation responses not
have response names as even when the request in recongized it may
be difficult for servers to return the specified response name.
For example, say a server is very overload and desires to return
busy for all new operations.  Requiring the server to parse the
requestName, determine which responseName is appropriate, and
possiblly be required to generate a response value may be overly
burdensome.

(I suspect that requestName field was provided for use with unsolicited
notifications... it likely should have never been used by extended
operations.)

The fact is, clients already have to deal with cases where
the responseName is absent.  So, it seems reasponable that
servers be allowed to not provide the responseName in a
number of other cases as well.  In fact, the responseName
should be extraneous in most cases.  The only case were I
could see in being needed where the extended request could
result in different format response values being generated.
I would consider such extended operation specifications
significantly flawed.

Anways, I suggest rewriting the section:
	An extension mechanism has been added to this version of LDAP
	in order to allow additional operations to be defined for
	services not already available elsewhere in the protocol.
	For example, to add operations to install transport layer
	security (see section 4.13).

	The extended operation allows clients to make requests and
	receive responses with predefined syntaxes and semantics.
	These may be defined in RFCs or be private to a particular
	implementations.

	Each operation consists of an extended response and an
	paired extended requested.

        ExtendedRequest ::= [APPLICATION 23] SEQUENCE {
                requestName      [0] LDAPOID,
                requestValue     [1] OCTET STRING OPTIONAL }
        ExtendedResponse ::= [APPLICATION 24] SEQUENCE {
                COMPONENTS OF LDAPResult,
                responseName     [10] LDAPOID OPTIONAL,
                responseValue    [11] OCTET STRING OPTIONAL }

	The requestname is a dotted-decimal representation of the
	OCTET IDENTIFIER corresponding to the request and to the
	operation.  The responseName is typically not required
	to be present as the syntax and semantics of the
	response (including the format of the responseValue) is
	implicitly known (responses are typically paired with
	requests).

	If the requestName is not recongized by the server, the
	server MUST NOT provide a responseName nor a responseValue
	and MUST return a resultCode of protocolError.  When the
	responseName field is present, it value is dotted-decimal
	representation of, depending on the operation's specification,
	either the OBJECT IDENTIFIER associated with the particular
	response or the OBJECT IDENTIFIER associated with operation.
	If the provided responseName is not recongized the client,
	the client is to treat the response as a protocol error.

	The requestValue and responseValue are used to exchange
	information, encoded into OCTET STRING values, associated
	with the operation as detailed in the operation's
	specification. 

Note that I renamed some of the fields for consistency AND clarity
(Having a field called "response" makes the text confusing).  I don't
see much problem in renaming these fields as any document which used
the old field names will need to be updated anyways to be used with
the revised specification.

Note also that I changed the example as controls seems like a more
approrpiate mechanism for "digitial signed operations".

>4.13. Start TLS Operation 

s/Start TLS/StartTLS/  (so hopefully the RFC-Editor won't require
it to be expanded).
> 
>   The Start Transport Layer Security (StartTLS) operation provides the 
>   ability to establish Transport Layer Security [RFC2246] on an LDAP 
>   connection. 

Insert just before the reference "(TLS)".

Add: The StartTLS operation is defined using the extended operation
mechanism descibed in section 4.12.

Use "StartTLS" not "Start TLS" below.

>4.13.1. Start TLS Request 
>  
>   A client requests TLS establishment by transmitting a Start TLS 
>   request PDU to the server. The Start TLS request is defined in terms 
>   of an ExtendedRequest. The requestName is "1.3.6.1.4.1.1466.20037", 
>   and the requestValue field is absent.   

s/absent/always absent/
    
>   The client MUST NOT send any PDUs on this connection following this 
>   request until it receives a Start TLS extended response. 
>    
>4.13.2. Start TLS Response 
> 
>   When a Start TLS request is made, servers supporting the operation 
>   MUST return a Start TLS response PDU to the requestor.  The Start TLS 
>   response responseName is also "1.3.6.1.4.1.1466.20037", and the 
>   response field is absent.  
>    
>   The server MUST set the resultCode field to either success or one of 
>   the other values outlined in section 4.13.2.2. 
>    
>4.13.2.1. "Success" Response 
> 
>   If the Start TLS Response contains a resultCode of success, this 
>   indicates that the server is willing and able to negotiate TLS. Refer 
>   to section 5.3 of [AuthMeth] for details. 
>    
>4.13.2.2. Response other than "success" 
> 
>   If the ExtendedResponse contains a resultCode other than success, 
>   this indicates that the server is unwilling or unable to negotiate 
>   TLS. The following resultCodes have these meanings for this 
>   operation: 
>    
>   operationsError  (operations sequencing incorrect; e.g. TLS already 
>                     established) 
>    
>   protocolError    (TLS not supported or incorrect PDU structure) 
>    
>   unavailable      (e.g. some major problem with TLS, or server is  
>                     shutting down) 
>    
>   The server MUST return operationsError if the client violates any of 
>   the Start TLS extended operation sequencing requirements described in 
>   section 5.3 of [AuthMeth]. 
>    
>   If the server does not support TLS (whether by design or by current 
>   configuration), it MUST set the resultCode to protocolError. The 
>   client's current association is unaffected if the server does not 
>   support TLS. The client MAY proceed with any LDAP operation, or it 
>   MAY close the connection. 
>    
>   The server MUST return unavailable if it supports TLS but cannot 
>   establish a TLS connection for some reason, e.g. the certificate 
>   server not responding, it cannot contact its TLS implementation, or 
>  
>                                      
>   if the server is in process of shutting down. The client MAY retry 
>   the StartTLS operation, or it MAY proceed with any other LDAP 
>   operation, or it MAY close the LDAP connection. 
> 
>4.13.3. Closing a TLS Connection 
> 
>   Two forms of TLS connection closure--graceful and abrupt--are 
>   supported. 
>    
>4.13.3.1. Graceful Closure 
> 
>   Either the client or server MAY terminate the TLS connection and 
>   leave the LDAP connection intact by sending a TLS closure alert. 
>    
>   Before sending a TLS closure alert, the client MUST either wait for 
>   any outstanding LDAP operations to complete, or explicitly abandon 
>   them.  
>    
>   After the initiator of a close has sent a TLS closure alert, it MUST 
>   discard any TLS messages until it has received a TLS closure alert 
>   from the other party.  It will cease to send TLS Record Protocol 
>   PDUs, and following the receipt of the alert, MAY send and receive 
>   LDAP PDUs. 
>    
>   The other party, if it receives a TLS closure alert, MUST immediately 
>   transmit a TLS closure alert.  It will subsequently cease to send TLS 
>   Record Protocol PDUs, and MAY send and receive LDAP PDUs. 
>    
>4.13.3.2. Abrupt Closure 
> 
>   Either the client or server MAY abruptly close the TLS connection by 
>   dropping the underlying transfer protocol connection. In this 
>   circumstance, a server MAY send the client a Notice of Disconnection 
>   before dropping the underlying LDAP connection. 
>    
>    
>5. Protocol Element Encodings and Transfer 
>    
>   One underlying service is defined here. Clients and servers SHOULD 
>   implement the mapping of LDAP over TCP described in 5.2.1. 

This statement could be read as to mean:
a) Implementation of LDAP over TCP is RECOMMENDED.
b) When implementing LDAP over TCP, the mapping described in 5.2.1
is RECOMMENDED.

I think that if implementations implement LDAP over TCP then they
MUST do so in accordance with 5.2.1.  And I suggest treating whether
implementations are to implment LDAP over TCP as an applicability
issue.  That is, I suggest the paragraph be replaced with:

	One underlying service, LDAP over TCP, is defined here.  This
	service is generally applicable to applications providing
	or consuming X.500-based directory services on the Internet.

	Implementations of LDAP over TCP MUST implement the mapping
	as described in Section 5.2.1.

>5.1. Protocol Encoding 
>    
>   The protocol elements of LDAP are encoded for exchange using the 
>   Basic Encoding Rules (BER) [X.690] of ASN.1 [X.680]. However, due to 
>   the high overhead involved in using certain elements of the BER, the 
>   following additional restrictions are placed on BER-encodings of LDAP 
>   protocol elements: 

It is not clear that all of these restrictions are mandatory to
implement.  I sugggest a single imperative be used to make this
whole section mandatory.  E.g.,
	Elements of LDAP SHALL be encoded for exchange using the
	Basic Encoding Rules (BER) [X.690] of ASN.1 [X.680] with the
	following restrictions:

This makes having per restriction MUSTs are redundant.

(with the rationale stated after the restrictions)

>   (1) Only the definite form of length encoding will be used. 

s/will be/is/

>   (2) OCTET STRING values will be encoded in the primitive form only. 

s/will be/are/

>   (3) If the value of a BOOLEAN type is true, the encoding MUST have 
>       its contents octets set to hex "FF". 

s/MUST have/has/

>   (4) If a value of a type is its default value, it MUST be absent. 
>       Only some BOOLEAN and INTEGER types have default values in this 
>       protocol definition. 

s/MUST be/is/


>   These restrictions do not apply to ASN.1 types encapsulated inside of 
>   OCTET STRING values, such as attribute values, unless otherwise 
>   noted. 

s/noted/stated/

>5.2. Transfer Protocols 
>    
>   This protocol is designed to run over connection-oriented, reliable 
>   transports, with all 8 bits in an octet being significant in the data 
>   stream.
>    
>5.2.1. Transmission Control Protocol (TCP) 
>    
>   The encoded LDAPMessage PDUs are mapped directly onto the TCP 
>   bytestream using the BER-based encoding described in section 5.1. It 
>   is recommended that server implementations running over the TCP 
>   provide a protocol listener on the assigned port, 389. Servers may 
>   instead provide a listener on a different port number. Clients MUST 
>   support contacting servers on any valid TCP port. 
>    
>6. Implementation Guidelines 
>    
>6.1. Server Implementations 
>    
>   The server MUST be capable of recognizing all the mandatory attribute 
>   type names and implement the syntaxes specified in [Syntaxes]. 
>   Servers MAY also recognize additional attribute type names. 

I think this statement is not consistent with [Models].  Also, I
don't servers should be required to implement all the syntaxes specified
in [Syntaxes].  For example, a server which doesn't implement DIT
Content Rules need not implement the DIT Content Rule syntax.

Anyways, I think [Models, Section 7.1] adequately covers this.

>    
>6.2. Client Implementations 
>    
>   Clients that follow referrals or search continuation references MUST 
>   ensure that they do not loop between servers. They MUST NOT 
>   repeatedly contact the same server for the same request with the same 
>   target entry name, scope and filter. Some clients use a counter that 
>   is incremented each time referral handling occurs for an operation, 
>   and these kinds of clients MUST be able to handle a DIT with at least 
>   ten layers of naming contexts between the root and a leaf entry. 

s/referral/referral or references/ (in two places)

Since referrals can be returned for reasons other than naming context
layers, I suggest this be reworded:
	... clients MUST be able to handle 9 layers of referrals or
	references.


The following paragraph should likely be moved to [Models].

>   In the absence of prior agreements with servers, clients SHOULD NOT 
>   assume that servers support any particular schemas beyond those 
>   referenced in section 6.1.

s/schemas/schema elements/

>   Different schemas can have different 
>   attribute types with the same names.

s/schemas/subschemas/

>   The client can retrieve the 
>   subschema entries referenced by the subschemaSubentry attribute in 
>   the entries held by the server. 

s/entries/subentries/
Provide a reference to [Models] for subschema subentries.



>    
>    
>7. Security Considerations 
>    
>   When used with a connection-oriented transport, this version of the 
>   protocol provides facilities for simple authentication using a 
>   cleartext password, as well as any SASL mechanism [RFC2222]. SASL 
>   allows for integrity and privacy services to be negotiated. 

The "When" clause should be dropped to avoid suggesting this
protocol can (directly) be mapped onto a connectless protocol.

>   It is also permitted that the server can return its credentials to 
>   the client, if it chooses to do so. 
>    
>   Use of cleartext password is strongly discouraged where the 
>   underlying transport service cannot guarantee confidentiality and may 
>   result in disclosure of the password to unauthorized parties. 
>    
>   When used with SASL, it should be noted that the name field of the 
>   BindRequest is not protected against modification. Thus if the 
>   distinguished name of the client (an LDAPDN) is agreed through the 
>   negotiation of the credentials, it takes precedence over any value in 
>   the unprotected name field. 

This needs to be expanded to other unprotected fields.

	It should be noted that SASL authentication exchanges do
	provide data confidential nor integrity protection for the
	version or name fields of the bind request nor the resultCode,
	errorMessage, or referral fields of the bind response nor
	of any information contained in controls attached to bind
	request or responses.  Thus information contained in these
	fields SHOULD NOT be relied on unless otherwise protected
	(such as by establishing protections at the transport layer).

We should discuss the precedence bit as part of our [authmeth] review.

>   Implementations which cache attributes and entries obtained via LDAP 
>   MUST ensure that access controls are maintained if that information 
>   is to be provided to multiple clients, since servers may have access 
>   control policies which prevent the return of entries or attributes in 
>   search results except to particular authenticated clients. For 
>   example, caches could serve result information only to the client 
>   whose request caused it to be in the cache. 
>    
>   Protocol servers may return referrals which redirect protocol clients 
>   to peer servers. It is possible for a rogue application to inject 
>   such referrals into the data stream in an attempt to redirect a 
>   client to a rogue server. Protocol clients are advised to be aware of 
>   this, and possibly reject referrals when confidentiality measures are 
>   in place. Protocol clients are advised to ignore referrals from the 
>   Start TLS operation. 

I suggest s/ignore/reject/ here.  I would hope clients would
not simply ignore the referral, but raise an alert to the user.

>8. Acknowledgements 
>    
>   This document is an update to RFC 2251, by Mark Wahl, Tim Howes, and 
>   Steve Kille. Their work along with the input of individuals of the 
>   IETF LDAPEXT, LDUP, LDAPBIS, and other Working Groups is gratefully 
>   acknowledged. 
>    
>    
>9. Normative References 
> 
>   [X.500]   ITU-T Rec. X.500, "The Directory: Overview of Concepts, 
>             Models and Service", 1993.  
>                                      
>   [Roadmap] K. Zeilenga (editor), "LDAP: Technical Specification Road 
>             Map", draft-ietf-ldapbis-roadmap-xx.txt (a work in 
>             progress). 
>    
>   [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 
>             Requirement Levels", RFC 2119, March 1997. 
>     
>   [X.680]   ITU-T Recommendation X.680 (1997) | ISO/IEC 8824-1:1998 
>             Information Technology - Abstract Syntax Notation One 
>             (ASN.1): Specification of basic notation 
>    
>   [X.690]   ITU-T Rec. X.690, "Specification of ASN.1 encoding rules: 
>             Basic, Canonical, and Distinguished Encoding Rules", 1994. 
>    
>   [LDAPIANA] K. Zeilenga, "IANA Considerations for LDAP", draft-ietf-
>             ldapbis-xx.txt (a work in progress). 
>    
>   [ISO10646] Universal Multiple-Octet Coded Character Set (UCS) - 
>             Architecture and Basic Multilingual Plane, ISO/IEC 10646-1 
>             : 1993. 
>    
>   [RFC2279] Yergeau, F., "UTF-8, a transformation format of Unicode 
>             and ISO 10646", RFC 2279, January 1998. 
>    
>   [Models]  K. Zeilenga, "LDAP: The Models", draft-ietf-ldapbis-
>             models-xx.txt (a work in progress). 
>    
>   [LDAPDN]  K. Zeilenga (editor), "LDAP: String Representation of 
>             Distinguished Names", draft-ietf-ldapbis-dn-xx.txt, (a 
>             work in progress). 
>    
>   [Syntaxes] K. Dally (editor), "LDAP: Syntaxes", draft-ietf-ldapbis-
>             syntaxes-xx.txt, (a work in progress). 
>    
>   [X.501]   ITU-T Rec. X.501, "The Directory: Models", 1993. 
>    
>   [X.511]   ITU-T Rec. X.511, "The Directory: Abstract Service 
>             Definition", 1993. 
>    
>   [RFC2396] Berners-Lee, T., Fielding, R., and L. Masinter Uniform 
>             Resource Identifiers (URI): Generic Syntax", RFC 2396, 
>             August 1998. 
>    
>   [AuthMeth] R. Harrison (editor), "LDAP: Authentication Methods", 
>             draft-ietf-ldapbis-authmeth-xx.txt, (a work in progress). 
>    
>   [RFC2222] Meyers, J., "Simple Authentication and Security Layer", 
>             RFC 2222, October 1997. 
>    
>   [SASLPrep] Zeilenga, K., "Stringprep profile for user names and 
>             passwords", draft-ietf-sasl-saslprep-xx.txt, (a work in 
>             progress). 
>    
>    
>  
>                                      
>   [Unicode] The Unicode Consortium, "The Unicode Standard, Version 
>             3.2.0" is defined by "The Unicode Standard, Version 3.0" 
>             (Reading, MA, Addison-Wesley, 2000. ISBN 0-201-61633-5), 
>             as amended by the "Unicode Standard Annex #27: Unicode 
>             3.1" (http://www.unicode.org/reports/tr27/) and by the 
>             "Unicode Standard Annex #28: Unicode 3.2" 
>             (http://www.unicode.org/reports/tr28/). 
>    
> 
> 
>10. Editor's Address 
>    
>   Jim Sermersheim 
>   Novell, Inc. 
>   1800 South Novell Place 
>   Provo, Utah 84606, USA 
>   jimse@novell.com 
>   +1 801 861-3088 
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>  
>                                      
>Appendix A - LDAP Result Codes 
> 
>   This normative appendix details additional considerations regarding 
>   LDAP result codes and provides a brief, general description of each 
>   LDAP result code enumerated in Section 4.1.10. 
>    
>   Additional result codes MAY be defined for use with extensions. 
>   Client implementations SHALL treat any result code which they do not 
>   recognize as an unknown error condition. 
>    
>A.1 Non-Error Result Codes 
>   These result codes (called "non-error" result codes) do not indicate 
>   an error condition: 
>        success(0), 
>        compareTrue(6), 
>        compareFalse(7), 
>        referral(10), and 
>        saslBindInProgress(14). 
>    
>   The success(0), compareTrue(6), and compare(7) result codes indicate 
>   successful completion (and, hence, are called to as "successful" 
>   result codes). 
>    
>   The referral(10) and saslBindInProgress(14) indicate the client is 
>   required to take additional action to complete the operation 
>    
>    
>A.2 Error Result Codes 
>    
>A.3 Classes and Precedence of Error Result Codes 
>    
>   Result codes that indicate error conditions (and, hence, are called 
>   "error" result codes) fall into 6 classes. The following list 
>   specifies the precedence of error classes to be used when more than 
>   one error is detected [X511]: 

s/detected/detected simultaneously/
LDAP may detect error conditions in any order.  (I'm going to
argue below that this precedence stuff be axed.)

>        1) Name Errors (codes 32 - 34, 36)  
>                - a problem related to a name (DN or RDN), 
>        2) Update Errors (codes 64 - 69, 71) 
>                - a problem related to an update operation, 
>        3) Attribute Errors (codes 16 - 21) 
>                - a problem related to a supplied attribute, 
>        4) Security Errors (codes 8, 13, 48 - 50) 
>                - a security related problem, 
>        5) Service Problem (codes 3, 4, 7, 11, 12, 51 - 54, 80) 
>                - a problem related to the provision of the service, and 
>        6) Protocol Problem (codes 1, 2) 
>                - a problem related to protocol structure or semantics. 
>    
>   If the server detects multiple errors simultaneously, the server 
>   SHOULD report the error with the highest precedence. 

This SHOULD is meaningless and pointless.

It's meaningless in that an implementor of a server which is believed
to return a lower precedence code when it detected an condition
calling for a higher precedence code can simply declare that the
conditions were not simultaneously detected.   

It's pointless in that interoperability dictates that clients not
rely on the order of error detection (since servers can detect
errors in any order).

Hence, I believe all meantion off precedence of error codes be
deleted.  However, information about error classes could be kept.
That is, I suggest the above text be replaced with:
	Result codes which indicate error conditions (and, hence,
	are called "error" result codes) fall into 6 classes.
        1) Name Errors (codes 32 - 34, 36)  
                - a problem related to a name (DN or RDN), 
        2) Update Errors (codes 64 - 69, 71) 
                - a problem related to an update operation, 
        3) Attribute Errors (codes 16 - 21) 
                - a problem related to a supplied attribute, 
        4) Security Errors (codes 8, 13, 48 - 50) 
                - a security related problem, 
        5) Service Problem (codes 3, 4, 7, 11, 12, 51 - 54, 80) 
                - a problem related to the provision of the service, and 
        6) Protocol Problem (codes 1, 2) 
                - a problem related to protocol structure or semantics. 
    
	Unlike [X.511], LDAP does not generally restrict the order
	in which error conditions are to be detected or prescribe
	that certain codes have higher precedence than other codes.
	(The above classes are provided for information only.)
	Unless stated otherwise, LDAP servers are free to detect
	error conditions in any order and where multiple errors are
	detected simulanteously, are free to choose which error
	condition should be indicated.  Clients MUST NOT assume the
	error detection order of the server is predicable.

---

Since this lists all codes, it should have a new section heading
	A.4  Descriptions of LDAP Result Codes

>    
>   Existing LDAP result codes are described as follows: 
> 
>        success (0) 
>  
>           Indicates successful completion of an operation. 
>    
>           This result code is normally not returned by the compare 
>           operation, see compareFalse (5) and compareTrue (6). It is 
>           possible that a future extension mechanism would allow this 
>           to be returned by a compare operation. 

Suggest this paragraph be replaced with:
			Note: this code is not used with the compare operation.
			See compareTrue (5) and compareFalse (6).

(no need to say what is possible in future extensions)
>    
>    
>        operationsError (1) 
>    
>           Indicates that the operation is not properly sequenced with 
>           relation to other operations (of same or different type). 
> 
>           For example, this code is returned if the client attempts to 
>           Start TLS [RFC2246] while there are other operations 
>           outstanding or if TLS was already established. 
>            
> 
> 
>        protocolError (2) 
>           Indicates the server received data which has incorrect 
>           structure. 
>            
>           For bind operation only, the code may be resulted to indicate 
>           the server does not support the requested protocol version. 

replace with:
			For bind operation only, this code is also used to indicate
			that the server does not support the requested protocol
			version.
            
> 
>        timeLimitExceeded (3) 
>         
>           Indicates that the time limit specified by the client was 
>           exceeded before the operation could be completed. 
>         
>         
>        sizeLimitExceeded (4) 
>         
>           Indicates that the size limit specified by the client was 
>           exceeded before the operation could be completed. 
>         
>         
>        compareFalse (5) 
>         
>           Indicates that the operation successfully completes and the 
>           assertion has evaluated to FALSE. 
>         
>           This result code is normally only returned by the compare 
>           operation. 

Suggest this sentence be replaced (here and below) with:
		This result code is only used by compare operation.
         
>         
>        compareTrue (6) 
>         
>           Indicates that the operation successfully completes and the 
>           assertion has evaluated to TRUE. 
>         
>           This result code is normally only returned by the compare 
>           operation. 
>         
>         
>        authMethodNotSupported (7) 
>         
>           Indicates that the authentication method or mechanism is not 
>           supported. 
>         
>         
>        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. 
>         
>         
>        referral (10) 
>         
>           Indicates that a referral needs to be chased to complete the 
>           operation (see section 4.1.11). 
>         
>         
>        adminLimitExceeded (11) 
>         
>           Indicates that an administrative limit has been exceeded. 
>         
>         
>        unavailableCriticalExtension (12) 
>         
>           Indicates that server cannot perform a critical extension 
>           (see section 4.1.12). 

s/cannot/is unwilling or unable/

>         
>         
>        confidentialityRequired (13) 
>         
>           Indicates that data confidentiality protections are required. 
>         
>         
>        saslBindInProgress (14) 
>         
>           Indicates the server requires the client to send a new bind 
>           request, with the same SASL mechanism, to continue the 
>           authentication process (see section 4.2). 
>         
>         
>        noSuchAttribute (16) 
>         
>           Indicates that the named entry does not contain the specified 
>           attribute or attribute value. 
>         
>         
>        undefinedAttributeType (17) 
>         
>           Indicates that a request field contains an undefined 
>           attribute type. 

s/undefined attribute type/unrecongized attribute description/

>         
>         
>        inappropriateMatching (18) 
>         
>           Indicates that a request cannot be completed due to an 
>           inappropriate matching. 

delete the word "an".
         
>         
>        constraintViolation (19) 
>         
>           Indicates that the client supplied an attribute value which 
>           does not conform to constraints placed upon it by the data 
>           model. 
>         
>           For example, this code is returned when the multiple values 
>           are supplied to an attribute which has a SINGLE-VALUE 
>           constraint. 
>         
>         
>        attributeOrValueExists (20) 
>         
>           Indicates that the client supplied an attribute or value to 
>           be added to an entry already exists. 
>         
>         
>        invalidAttributeSyntax (21) 
>         
>           Indicates that a purported attribute value does not conform 
>           to the syntax of the attribute. 
>         
>         
>        noSuchObject (32) 
>         
>           Indicates that the object does not exist in the DIT. 
>         
>         
>        aliasProblem (33) 
>         
>           Indicates that an alias problem has occurred. Typically an 
>           alias has been dereferenced which names no object. 

Suggest s/Typically/For example, the code may used to indicate/

>         
>         
>        invalidDNSyntax (34) 
>         
>           Indicates that a LDAPDN or RelativeLDAPDN field (e.g. search 
>           base, target entry, ModifyDN newrdn, etc.) of a request does 
>           not conform to the required syntax or contains attribute 
>           values which do not conform to the syntax of the attribute's 
>           type. 
>         
>        aliasDereferencingProblem (36) 
>         
>           Indicates that a problem occurred while dereferencing an 
>           alias. Typically an alias was encountered in a situation 
>           where it was not allowed or where access was denied. 
>         
>         
>        inappropriateAuthentication (48) 
>         
>           Indicates the server requires the client which had attempted 
>           to bind anonymously or without supplying credentials to 
>           provide some form of credentials, 
>         
>        invalidCredentials (49) 
>         
>           Indicates the supplied password or SASL credentials are 
>           invalid. 

This wording is too narrow.  It doesn't include the bind name
which is part of the creditials when simple bind is used, nor
does it include non-SASL credentials (the LDAP can be extended
to support other methods).

Suggest:
		Indicates that the provided credentials (e.g. the user's
		name and password) are invalid.





>         
>         
>        insufficientAccessRights (50) 
>         
>           Indicates that the client does not have sufficient access 
>           rights to perform the operation. 
>         
>         
>        busy (51) 
>         
>           Indicates that the server is busy. 

Suggest:
			Indicates that the server is too busy to process the
			operation.
         
>        unavailable (52) 
>         
>           Indicates that the server is shutting down or a subsystem 
>           necessary to complete the operation is offline. 
>         
>        unwillingToPerform (53) 
>         
>           Indicates that the server is unwilling to perform the 
>           operation. 
>         
>        loopDetect (54) 
>         
>           Indicates that the server has detected an internal loop. 
>         
>        namingViolation (64) 
>         
>           Indicates that the entry name violates naming restrictions. 

s/entry name/entry's name/
         
>        objectClassViolation (65) 
>         
>           Indicates that the entry violates object class restrictions. 
>         
>         
>        notAllowedOnNonLeaf (66) 
>         
>           Indicates that operation is inappropriately acting upon a 
>           non-leaf entry. 
>         
>         
>        notAllowedOnRDN (67) 
>         
>           Indicates that the operation is inappropriately attempting to 
>           remove a value which forms the entry's relative distinguished 
>           name. 
>         
>         
>        entryAlreadyExists (68) 
>         
>           Indicates that the request cannot be added fulfilled as the 
>           entry already exists. 
>         
>         
>        objectClassModsProhibited (69) 
>         
>           Indicates that the attempt to modify the object class(es) of 
>           an entry objectClass attribute is prohibited. 
>         
>           For example, this code is returned when a when a client 
>           attempts to modify the structural object class of an entry. 

s/when a when a/when a/
         
>         
>        affectsMultipleDSAs (71) 
>         
>           Indicates that the operation cannot be completed as it 
>           affects multiple servers (DSAs). 
>         
>         
>        other (80) 
>         
>           Indicates the server has encountered an internal error. 
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>  
>                                      
>   Appendix B - Complete ASN.1 Definition 
>    
>        This appendix is normative. 
>    
>        Lightweight-Directory-Access-Protocol-V3 DEFINITIONS 
>        IMPLICIT TAGS 
>        EXTENSIBILITY IMPLIED ::= 
>    
>        BEGIN 
>    
>        LDAPMessage ::= SEQUENCE { 
>                messageID       MessageID, 
>                protocolOp      CHOICE { 
>                        bindRequest     BindRequest, 
>                        bindResponse    BindResponse, 
>                        unbindRequest   UnbindRequest, 
>                        searchRequest   SearchRequest, 
>                        searchResEntry  SearchResultEntry, 
>                        searchResDone   SearchResultDone, 
>                        searchResRef    SearchResultReference, 
>                        modifyRequest   ModifyRequest, 
>                        modifyResponse  ModifyResponse, 
>                        addRequest      AddRequest, 
>                        addResponse     AddResponse, 
>                        delRequest      DelRequest, 
>                        delResponse     DelResponse, 
>                        modDNRequest    ModifyDNRequest, 
>                        modDNResponse   ModifyDNResponse, 
>                        compareRequest  CompareRequest, 
>                        compareResponse CompareResponse, 
>                        abandonRequest  AbandonRequest, 
>                        extendedReq     ExtendedRequest, 
>                        extendedResp    ExtendedResponse, 
>                        ... }, 
>                 controls       [0] Controls OPTIONAL } 
>    
>        MessageID ::= INTEGER (0 .. maxInt) 
>    
>        maxInt INTEGER ::= 2147483647 -- (2^^31 - 1) -- 
>    
>        LDAPString ::= OCTET STRING -- UTF-8 encoded, 
>                                    -- [ISO10646] characters 
>    
>        LDAPOID ::= OCTET STRING -- Constrained to numericoid [Models] 
>    
>        LDAPDN ::= LDAPString 
>    
>        RelativeLDAPDN ::= LDAPString 
>    
>        AttributeDescription ::= LDAPString 
>                                 -- Constrained to attributedescription 
>                                 -- [Models] 
>    
>        AttributeDescriptionList ::= SEQUENCE OF 
>                AttributeDescription 
>    
>        AttributeValue ::= OCTET STRING 
>    
>        AttributeValueAssertion ::= SEQUENCE { 
>                attributeDesc   AttributeDescription, 
>                assertionValue  AssertionValue } 
>    
>        AssertionValue ::= OCTET STRING 
>    
>        Attribute ::= SEQUENCE { 
>                type    AttributeDescription, 
>                vals    SET OF AttributeValue } 
>    
>        MatchingRuleId ::= LDAPString 
>    
>        LDAPResult ::= SEQUENCE { 
>                resultCode         ENUMERATED { 
>                             success                      (0), 
>                             operationsError              (1), 
>                             protocolError                (2), 
>                             timeLimitExceeded            (3), 
>                             sizeLimitExceeded            (4), 
>                             compareFalse                 (5), 
>                             compareTrue                  (6), 
>                             authMethodNotSupported       (7), 
>                             strongAuthRequired           (8), 
>                                        -- 9 reserved -- 
>                             referral                     (10), 
>                             adminLimitExceeded           (11), 
>                             unavailableCriticalExtension (12), 
>                             confidentialityRequired      (13), 
>                             saslBindInProgress           (14), 
>                             noSuchAttribute              (16), 
>                             undefinedAttributeType       (17), 
>                             inappropriateMatching        (18), 
>                             constraintViolation          (19), 
>                             attributeOrValueExists       (20), 
>                             invalidAttributeSyntax       (21), 
>                                        -- 22-31 unused -- 
>                             noSuchObject                 (32), 
>                             aliasProblem                 (33), 
>                             invalidDNSyntax              (34), 
>                             -- 35 reserved for undefined isLeaf -- 
>                             aliasDereferencingProblem    (36), 
>                                        -- 37-47 unused -- 
>                             inappropriateAuthentication  (48), 
>                             invalidCredentials           (49), 
>                             insufficientAccessRights     (50), 
>                             busy                         (51), 
>                             unavailable                  (52), 
>                             unwillingToPerform           (53), 
>                             loopDetect                   (54), 
>                                        -- 55-63 unused -- 
>  
>                                      
>                             namingViolation              (64), 
>                             objectClassViolation         (65), 
>                             notAllowedOnNonLeaf          (66), 
>                             notAllowedOnRDN              (67), 
>                             entryAlreadyExists           (68), 
>                             objectClassModsProhibited    (69), 
>                                        -- 70 reserved for CLDAP -- 
>                             affectsMultipleDSAs          (71), 
>                                        -- 72-79 unused -- 
>                             other                        (80), 
>                             ... }, 
>                             -- 81-90 reserved for APIs -- 
>                matchedDN          LDAPDN, 
>                diagnosticMessage  LDAPString, 
>                referral           [3] Referral OPTIONAL } 
>    
>        Referral ::= SEQUENCE OF LDAPURL 
>    
>        LDAPURL ::= LDAPString -- limited to characters permitted in 
>                               -- URLs 
>    
>        Controls ::= SEQUENCE OF Control 
>    
>        Control ::= SEQUENCE { 
>                controlType             LDAPOID, 
>                criticality             BOOLEAN DEFAULT FALSE, 
>                controlValue            OCTET STRING OPTIONAL } 
>    
>        BindRequest ::= [APPLICATION 0] SEQUENCE { 
>                version                 INTEGER (1 .. 127), 
>                name                    LDAPDN, 
>                authentication          AuthenticationChoice } 
>    
>        AuthenticationChoice ::= CHOICE { 
>                simple                  [0] OCTET STRING, 
>                                         -- 1 and 2 reserved 
>                sasl                    [3] SaslCredentials, 
>                ... } 
>    
>        SaslCredentials ::= SEQUENCE { 
>                mechanism               LDAPString, 
>                credentials             OCTET STRING OPTIONAL } 
>    
>        BindResponse ::= [APPLICATION 1] SEQUENCE { 
>             COMPONENTS OF LDAPResult, 
>             serverSaslCreds    [7] OCTET STRING OPTIONAL } 
>    
>        UnbindRequest ::= [APPLICATION 2] NULL 
>    
>        SearchRequest ::= [APPLICATION 3] SEQUENCE { 
>                baseObject      LDAPDN, 
>                scope           ENUMERATED { 
>                        baseObject              (0), 
>                        singleLevel             (1), 
>  
>                                      
>                        wholeSubtree            (2) }, 
>                derefAliases    ENUMERATED { 
>                        neverDerefAliases       (0), 
>                        derefInSearching        (1), 
>                        derefFindingBaseObj     (2), 
>                        derefAlways             (3) }, 
>                sizeLimit       INTEGER (0 .. maxInt), 
>                timeLimit       INTEGER (0 .. maxInt), 
>                typesOnly       BOOLEAN, 
>                filter          Filter, 
>                attributes      AttributeDescriptionList } 
>    
>        Filter ::= CHOICE { 
>                and             [0] SET SIZE (1..MAX) OF Filter, 
>                or              [1] SET SIZE (1..MAX) OF Filter, 
>                not             [2] Filter, 
>                equalityMatch   [3] AttributeValueAssertion, 
>                substrings      [4] SubstringFilter, 
>                greaterOrEqual  [5] AttributeValueAssertion, 
>                lessOrEqual     [6] AttributeValueAssertion, 
>                present         [7] AttributeDescription, 
>                approxMatch     [8] AttributeValueAssertion, 
>                extensibleMatch [9] MatchingRuleAssertion } 
>    
>        SubstringFilter ::= SEQUENCE { 
>                type            AttributeDescription, 
>                -- at least one must be present, 
>                -- initial and final can occur at most once 
>                substrings      SEQUENCE OF CHOICE { 
>                        initial [0] AssertionValue, 
>                        any     [1] AssertionValue, 
>                        final   [2] AssertionValue } } 
>    
>        MatchingRuleAssertion ::= SEQUENCE { 
>                matchingRule    [1] MatchingRuleId OPTIONAL, 
>                type            [2] AttributeDescription OPTIONAL, 
>                matchValue      [3] AssertionValue, 
>                dnAttributes    [4] BOOLEAN DEFAULT FALSE } 
>    
>        SearchResultEntry ::= [APPLICATION 4] SEQUENCE { 
>                objectName      LDAPDN, 
>                attributes      PartialAttributeList } 
>    
>        PartialAttributeList ::= SEQUENCE OF SEQUENCE { 
>                type    AttributeDescription, 
>                vals    SET OF AttributeValue } 
>    
>        SearchResultReference ::= [APPLICATION 19] SEQUENCE OF LDAPURL 
>    
>        SearchResultDone ::= [APPLICATION 5] LDAPResult 
>    
>        ModifyRequest ::= [APPLICATION 6] SEQUENCE { 
>                object          LDAPDN, 
>                modification    SEQUENCE OF SEQUENCE { 
>                        operation       ENUMERATED { 
>                                                add     (0), 
>                                                delete  (1), 
>                                                replace (2) }, 
>                        modification    AttributeTypeAndValues } } 
>    
>        AttributeTypeAndValues ::= SEQUENCE { 
>                type    AttributeDescription, 
>                vals    SET OF AttributeValue } 
>    
>        ModifyResponse ::= [APPLICATION 7] LDAPResult 
>    
>        AddRequest ::= [APPLICATION 8] SEQUENCE { 
>                entry           LDAPDN, 
>                attributes      AttributeList } 
>    
>        AttributeList ::= SEQUENCE OF SEQUENCE { 
>                type    AttributeDescription, 
>                vals    SET OF AttributeValue } 
>    
>        AddResponse ::= [APPLICATION 9] LDAPResult 
>    
>        DelRequest ::= [APPLICATION 10] LDAPDN 
>    
>        DelResponse ::= [APPLICATION 11] LDAPResult 
>    
>        ModifyDNRequest ::= [APPLICATION 12] SEQUENCE { 
>                entry           LDAPDN, 
>                newrdn          RelativeLDAPDN, 
>                deleteoldrdn    BOOLEAN, 
>                newSuperior     [0] LDAPDN OPTIONAL } 
>    
>        ModifyDNResponse ::= [APPLICATION 13] LDAPResult 
>    
>        CompareRequest ::= [APPLICATION 14] SEQUENCE { 
>                entry           LDAPDN, 
>                ava             AttributeValueAssertion } 
>    
>        CompareResponse ::= [APPLICATION 15] LDAPResult 
>    
>        AbandonRequest ::= [APPLICATION 16] MessageID 
>    
>        ExtendedRequest ::= [APPLICATION 23] SEQUENCE { 
>                requestName      [0] LDAPOID, 
>                requestValue     [1] OCTET STRING OPTIONAL } 
>    
>        ExtendedResponse ::= [APPLICATION 24] SEQUENCE { 
>                COMPONENTS OF LDAPResult, 
>                responseName     [10] LDAPOID OPTIONAL, 
>                response         [11] OCTET STRING OPTIONAL } 
>    
>        END 
>
>


From owner-ietf-ldapbis@OpenLDAP.org  Tue Oct  7 19: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 TAA27617
	for <ldapbis-archive@lists.ietf.org>; Tue, 7 Oct 2003 19:28:58 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h97NQvj6082133;
	Tue, 7 Oct 2003 23:27: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 h97NLOCi082090;
	Tue, 7 Oct 2003 23:21:24 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 7 Oct 2003 23:21:24 +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 h97NLLj2082059;
	Tue, 7 Oct 2003 23:21:22 GMT
	(envelope-from jimse@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Tue, 07 Oct 2003 17:21:01 -0600
Message-Id: <sf82f5fd.076@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.1 
Date: Tue, 07 Oct 2003 17:20:47 -0600
From: "Jim Sermersheim" <jimse@novell.com>
To: <ietf-ldapbis@OpenLDAP.org>, <Kurt@OpenLDAP.org>
Subject: Re: protocol review notes [LONG]
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__PartC19F705F.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>

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.

--=__PartC19F705F.0__=
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Was your message truncated? I only see comments through 4.1.11

--=__PartC19F705F.0__=
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 5.50.4933.1800" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Microsoft Sans Serif">
<DIV>Was your message truncated? I only see comments through 4.1.11</DIV></BODY></HTML>
--=__PartC19F705F.0__=--


From owner-ietf-ldapbis@OpenLDAP.org  Tue Oct  7 19:42: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 TAA28027
	for <ldapbis-archive@lists.ietf.org>; Tue, 7 Oct 2003 19:42:54 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h97NcujU083200;
	Tue, 7 Oct 2003 23:41: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 h97NYeZw082667;
	Tue, 7 Oct 2003 23:34:40 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 7 Oct 2003 23:34:40 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h97NYdj2082655
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 7 Oct 2003 23:34:39 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from gypsy.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.9/8.12.9) with ESMTP id h97NYYlg071854;
	Tue, 7 Oct 2003 23:34:35 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.0.22.0.20031008041847.03a77f30@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
Date: Wed, 08 Oct 2003 04:34:17 -0700
To: <steven.legg@adacel.com.au>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: RE: WG Last Call: draft-ietf-ldapbis-protocol-17.txt
  [corrected]
Cc: <ietf-ldapbis@OpenLDAP.org>
In-Reply-To: <002e01c38c66$f6237ea0$a518200a@osmium.mtwav.adacel.com.au>
References: <5.2.0.9.0.20030919105440.03bcf5d8@127.0.0.1>
 <002e01c38c66$f6237ea0$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>

In the AttributeList case, I rather the ASN.1 be changed
to:
        AttributeList ::= SEQUENCE OF Attribute

where Attribute is as currently defined.

Kurt


At 05:07 PM 10/6/2003, Steven Legg wrote:

>Folks,
>
>I recently published an Internet draft on an XML rendition of the LDAP
>protocol (called XLDAP) that is realized by applying a set of XML
>encoding rules to the ASN.1 types in the ASN.1 specification for LDAP
>(specifically the ASN.1 in the protocols draft being last-called).
>
>The XML produced is neat and tidy except with respect to the instances
>of the member type of a SEQUENCE OF or SET OF ASN.1 type.
>
>Consider this example drawn from the protocols draft:
>
>        AttributeList ::= SEQUENCE OF SEQUENCE { 
>                type    AttributeDescription, 
>                vals    SET OF AttributeValue } 
>
>Using my Directory XML Encoding Rules (DXER) to encode an attribute list,
>each attribute in the list is encoded as an element with the safe, but
>bland name of <item>. Using the ITU-T's XML Encoding Rules (XER), each
>attribute in the list is encoded as an element with the unappealing name
>of <SEQUENCE>.
>    
>However the situation can be improved since the version of ASN.1 that
>the protocols draft is referencing allows an ASN.1 identifier after a
>SEQUENCE OF or SET OF and before the definition of the member type.
>
>For example:
>
>        AttributeList ::= SEQUENCE OF attribute SEQUENCE { 
>                type    AttributeDescription, 
>                vals    SET OF value AttributeValue } 
>
>With this change both DXER and XER would encode each attribute in the list
>as an element with the more meaningful name of <attribute>. This change
>makes no difference to the BER encoding, so it is neutral to LDAP and does
>not represent a new feature.
>
>I would like to see each of the SEQUENCE OF and SET OF definitions in the
>LDAP ASN.1 module given a meaningful mnemonic identifier for the member type
>so as to facilitate better XML representations of LDAP operations (whether
>for XLDAP or any other purpose). If the working group allows it I'll work
>with Jim to make the additions.
>
>Regards,
>Steven



From owner-ietf-ldapbis@OpenLDAP.org  Tue Oct  7 19:42: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 TAA28043
	for <ldapbis-archive@lists.ietf.org>; Tue, 7 Oct 2003 19:42:57 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h97NcujS083200;
	Tue, 7 Oct 2003 23:41: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 h97NXkVM082539;
	Tue, 7 Oct 2003 23:33:46 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 7 Oct 2003 23:33: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 h97NXjj2082529
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 7 Oct 2003 23:33:45 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from gypsy.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.9/8.12.9) with ESMTP id h97NXjlg071824
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 7 Oct 2003 23:33:45 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.0.22.0.20031008042231.03a76ad8@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
Date: Wed, 08 Oct 2003 04:33:28 -0700
To: ietf-ldapbis@OpenLDAP.org
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: protocol review notes [LONG]
In-Reply-To: <20031002114843.GB590@bahner.com>
References: <20031002114843.GB590@bahner.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 04:48 AM 10/2/2003, Kurt Zeilenga wrote:
>>Document: draft-ietf-ldapbis-protocol-14.txt                   Jun 2003 

Yikes...  In merging comments between my old notes and new
notes file, I just have gone the wrong direction.  (Now I
know why I vague sense of deja vu last night.)  Sorry,
if I raised issues already addressed in -17.  I'll quickly
review changes since to see if I have concerns with the
new text.

Kurt 



From owner-ietf-ldapbis@OpenLDAP.org  Tue Oct  7 20:28: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 UAA29201
	for <ldapbis-archive@lists.ietf.org>; Tue, 7 Oct 2003 20:28:58 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h980Qvj6085561;
	Wed, 8 Oct 2003 00:27: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 h980QKXV085552;
	Wed, 8 Oct 2003 00:26:20 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 8 Oct 2003 00:26: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 h980QHj2085521;
	Wed, 8 Oct 2003 00:26:18 GMT
	(envelope-from jimse@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Tue, 07 Oct 2003 18:25:57 -0600
Message-Id: <sf830535.002@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.1 
Date: Tue, 07 Oct 2003 18:25:45 -0600
From: "Jim Sermersheim" <jimse@novell.com>
To: <ietf-ldapbis@OpenLDAP.org>, <Kurt@OpenLDAP.org>
Subject: Re: protocol review notes [LONG]
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__Part144AA599.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>

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.

--=__Part144AA599.0__=
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Oh good, because as I was reading some of the comments I had some
thoughts like, "hmm, I thought I already addressed that--I guess I need
to do it over". I'll ignore those comments and wait for your fixed
ones.

>>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 10/8/03 5:33:28 AM >>>
At 04:48 AM 10/2/2003, Kurt Zeilenga wrote:
>>Document: draft-ietf-ldapbis-protocol-14.txt Jun 2003 

Yikes... In merging comments between my old notes and new
notes file, I just have gone the wrong direction. (Now I
know why I vague sense of deja vu last night.) Sorry,
if I raised issues already addressed in -17. I'll quickly
review changes since to see if I have concerns with the
new text.

Kurt 


--=__Part144AA599.0__=
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 5.50.4933.1800" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Microsoft Sans Serif">Oh good, because as I was reading some of the comments I had some thoughts like, "hmm, I thought I already addressed that--I guess I need to do it over". I'll ignore those comments and wait for your fixed ones.<BR><BR>&gt;&gt;&gt; "Kurt D. Zeilenga" &lt;Kurt@OpenLDAP.org&gt; 10/8/03 5:33:28 AM &gt;&gt;&gt;<BR>At 04:48 AM 10/2/2003, Kurt Zeilenga wrote:<BR>&gt;&gt;Document: draft-ietf-ldapbis-protocol-14.txt Jun 2003 <BR><BR>Yikes... In merging comments between my old notes and new<BR>notes file, I just have gone the wrong direction. (Now I<BR>know why I vague sense of deja vu last night.) Sorry,<BR>if I raised issues already addressed in -17. I'll quickly<BR>review changes since to see if I have concerns with the<BR>new text.<BR><BR>Kurt <BR><BR></BODY></HTML>
--=__Part144AA599.0__=--


From owner-ietf-ldapbis@OpenLDAP.org  Tue Oct  7 21:24:08 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 VAA00623
	for <ldapbis-archive@lists.ietf.org>; Tue, 7 Oct 2003 21:24:05 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h981Kvj6088485;
	Wed, 8 Oct 2003 01:21: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 h981J8t9088458;
	Wed, 8 Oct 2003 01:19:08 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 8 Oct 2003 01:19:08 +0000
Received: from boole.openldap.org (kurt@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h981J0j2088440
	for <ietf-ldapbis@openldap.org>; Wed, 8 Oct 2003 01:19:00 GMT
	(envelope-from kurt@boole.openldap.org)
Received: (from kurt@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) id h981J0PK088439
	for ietf-ldapbis@openldap.org; Tue, 7 Oct 2003 18:19:00 -0700 (PDT)
	(envelope-from kurt)
Date: Tue, 7 Oct 2003 21:48:43 +0000
From: Kurt Zeilenga <Kurt@OpenLDAP.org>
To: ietf-ldapbis@OpenLDAP.org
Subject: REVISED protocol review notes [LONG]
Message-ID: <20031002114843.GB590.bogus@openldap.org>
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>

Okay... I've updated my notes for -17.

Again, some of the issues I raised are significant and likely
somewhat contentious.  These should be spun off into separate
threads.  And, given this post is quite long, please trim
portions extraneous to your comments from your replies.

Thanks, Kurt

>Internet-Draft                                  Editor:  J. Sermersheim 
>Intended Category: Standard Track                           Novell, Inc 
>Document: draft-ietf-ldapbis-protocol-17.txt                   Sep 2003 
>Obsoletes: RFC 2251                                                     
> 
> 
>                            LDAP: The Protocol 
>Abstract 
> 
>   This document describes the protocol elements, along with their 
>   semantics and encodings, for the Lightweight Directory Access 
>   Protocol (LDAP). LDAP provides access to distributed directory 
>   services that act in accordance with X.500 data and service models. 
>   These protocol elements are based on those described in the X.500 
>   Directory Access Protocol (DAP). 
>    
>    
>    
> 
>1. Introduction 
>    
>   The Directory is "a collection of open systems cooperating to provide 
>   directory services" [X.500]. A Directory user, which may be a human 
>   or other entity, accesses the Directory through a client (or 
>   Directory User Agent (DUA)). The client, on behalf of the directory 
>   user, interacts with one or more servers (or Directory System Agents 
>   (DSA)). Clients interact with servers using a directory access 
>   protocol.  
>    
>   This document details the protocol elements of Lightweight Directory 
>   Access Protocol, along with their semantics. Following the 
>   description of protocol elements, it describes the way in which the 
>   protocol is encoded and transferred. 

Insert (LDAP) after Lightweight Directory Access Protocol.

>   This document is an integral part of the LDAP Technical Specification 
>   [Roadmap]. 
>    
>   This document replaces RFC 2251. Appendix C holds a detailed log of 
>   changes to RFC 2251. Prior to Working Group Last Call, this appendix 
>   will be distilled to a summary of changes to RFC 2251. 

This (distill and review) still needs to be done (post WG Last Call).
    
>2. Conventions 
>    
>   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 
>   "SHOULD", "SHOULD NOT", "RECOMMENDED", and "MAY" in this document are 
>   to be interpreted as described in [RFC2119]. 
>   The terms "connection" and "LDAP connection" both refer to the 
>   underlying transport protocol connection between two protocol peers. 
>   The term "TLS connection" refers to a TLS-protected LDAP connection. 
>   The terms "association" and "LDAP association" both refer to the 
>   association of the LDAP connection and its current authentication and 
>   authorization state. 
 
Insert blank lines between paragraphs.
> 
>3. Protocol Model 
> 
>   The general model adopted by this protocol is one of clients 
>   performing protocol operations against servers. In this model, a 
>   client transmits a protocol request describing the operation to be 
>   performed to a server. The server is then responsible for performing 
>   the necessary operation(s) in the directory. Upon completion of the 
>   operation(s), the server returns a response containing an appropriate 
>   result code to the requesting client. 
>    
>   Although servers are required to return responses whenever such 
>   responses are defined in the protocol, there is no requirement for 
>   synchronous behavior on the part of either clients or servers. 
>   Requests and responses for multiple operations may be exchanged 
>
>  
>                                      
>   between a client and server in any order, provided the client 
>   eventually receives a response for every request that requires one. 
> 
>   The core protocol operations defined in this document can be mapped 
>   to a subset of the X.500 (1997) directory abstract service. However 
>   there is not a one-to-one mapping between LDAP protocol operations 
>   and DAP operations. Server implementations acting as a gateway to 
>   X.500 directories may need to make multiple DAP requests. 
 
s/ (1997)/(1993)/

Spell DAP out.

>4. Elements of Protocol 
>    
>   The LDAP protocol is described using Abstract Syntax Notation 1 
>   (ASN.1) [X.680], and is transferred using a subset of ASN.1 Basic 
>   Encoding Rules [X.690]. Section 5.1 specifies how the protocol is 
>   encoded and transferred. 

Insert "(BER)" after "Rules".
 
>   In order to support future Standards Track extensions to this 
>   protocol, extensibility is implied where it is allowed (per ASN.1). 
>   In addition, ellipses (...) have been supplied in ASN.1 types that 
>   are explicitly extensible as discussed in [LDAPIANA]. Because of the 
>   implied extensibility, clients and servers MUST (unless otherwise 
>   specified) ignore trailing SEQUENCE elements whose tags they do not 
>   recognize.  
>    
>   Changes to the LDAP protocol other than through the extension 
>   mechanisms described here require a different version number. A 
>   client indicates the version it is using as part of the bind request, 
>   described in section 4.2. If a client has not sent a bind, the server 
>   MUST assume the client is using version 3 or later. 
>    
>   Clients may determine the protocol versions a server supports by 
>   reading the supportedLDAPVersion attribute from the root DSE 
>   [Models]. Servers which implement version 3 or later MUST provide 
>   this attribute. 

Spell out DSE on first use.

Drop the MUST.  As the returned contents of the root DSE may be     
subject to ACLs, clients need to deal with the case where an LDAPv3      
server does not provide a root DSE or does not provide this attribute.
Most clients simply do blind (e.g., no root DSE checks) LDAPv3 binds
instead.

>4.1. Common Elements 
>    
>   This section describes the LDAPMessage envelope PDU (Protocol Data 
>   Unit) format, as well as data type definitions, which are used in the 
>   protocol operations. 
>    
>    
>4.1.1. Message Envelope 
>    
>   For the purposes of protocol exchanges, all protocol operations are 
>   encapsulated in a common envelope, the LDAPMessage, which is defined 
>   as follows: 
>    
>        LDAPMessage ::= SEQUENCE { 
>                messageID       MessageID, 
>                protocolOp      CHOICE { 
>                        bindRequest     BindRequest, 
>  
>                                      
>                        bindResponse    BindResponse, 
>                        unbindRequest   UnbindRequest, 
>                        searchRequest   SearchRequest, 
>                        searchResEntry  SearchResultEntry, 
>                        searchResDone   SearchResultDone, 
>                        searchResRef    SearchResultReference, 
>                        modifyRequest   ModifyRequest, 
>                        modifyResponse  ModifyResponse, 
>                        addRequest      AddRequest, 
>                        addResponse     AddResponse, 
>                        delRequest      DelRequest, 
>                        delResponse     DelResponse, 
>                        modDNRequest    ModifyDNRequest, 
>                        modDNResponse   ModifyDNResponse, 
>                        compareRequest  CompareRequest, 
>                        compareResponse CompareResponse, 
>                        abandonRequest  AbandonRequest, 
>                        extendedReq     ExtendedRequest, 
>                        extendedResp    ExtendedResponse, 
>                        ... }, 
>                controls        [0] Controls OPTIONAL } 
>    
>        MessageID ::= INTEGER (0 .. maxInt) 
>    
>        maxInt INTEGER ::= 2147483647 -- (2^^31 - 1) -- 
>    
>   The function of the LDAPMessage is to provide an envelope containing 
>   common fields required in all protocol exchanges. At this time the 
>   only common fields are the message ID and the controls. 
>    
>   If the server receives a PDU from the client in which the LDAPMessage 
>   SEQUENCE tag cannot be recognized, the messageID cannot be parsed, 
>   the tag of the protocolOp is not recognized as a request, or the 
>   encoding structures or lengths of data fields are found to be 
>   incorrect, then the server MAY return the Notice of Disconnection 
>   described in section 4.4.1, with the resultCode set to protocolError, 
>   and MUST immediately close the connection.  

In some places, the document notes the code value, e.g. "protocolError (2)".
In other paces, it doesn't.  Suggest for consistency that either the
notes always be present or never be present.

Also, the MAY implies that implementation of Notice of Disconnect   
is OPTIONAL.  That is, servers support for graceful closure support
is OPTIONAL.  It should be RECOMMENDED.  So, s/MAY/SHOULD.

>    
>   In other cases where the client or server cannot parse a PDU, it 
>   SHOULD abruptly close the connection where further communication 
>   (including providing notice) would be pernicious. Otherwise, server 
>   implementations MUST return an appropriate response to the request, 
>   with the resultCode set to protocolError. 
>    
>   The ASN.1 type Controls is defined in section 4.1.11. 
>    
>    
>4.1.1.1. Message ID 
>    
>   All LDAPMessage envelopes encapsulating responses contain the 
>   messageID value of the corresponding request LDAPMessage. 
>    
>   The message ID of a request MUST have a non-zero value different from 
>   the values of any other requests outstanding in the LDAP association 
>  
>                                      
>   of which this message is a part. The zero value is reserved for the 
>   unsolicited notification message. 
>    
>   Typical clients increment a counter for each request. 
>    
>   A client MUST NOT send a request with the same message ID as an 
>   earlier request on the same LDAP association unless it can be 
>   determined that the server is no longer servicing the earlier 
>   request. Otherwise the behavior is undefined. For operations that do 
>   not return responses (unbind, abandon, and abandoned operations), the 
>   client SHOULD assume the operation is in progress until a subsequent 
>   bind request completes. 
> 
> 
>4.1.2. String Types 
>    
>   The LDAPString is a notational convenience to indicate that, although 
>   strings of LDAPString type encode as OCTET STRING types, the 
>   [ISO10646] character set (a superset of [Unicode]) is used, encoded 
>   following the UTF-8 algorithm [RFC2279]. Note that in the UTF-8 
>   algorithm characters which are the same as ASCII (0x0000 through 
>   0x007F) are represented as that same ASCII character in a single 
>   byte. The other byte values are used to form a variable-length 
>   encoding of an arbitrary character. 

replace UTF-8 reference with draft-yergeau-rfc2279bis.

Suggested replacement text:
    Note that Unicode characters U+0000 through U+007F are the
    same as ASCII 0 through 127, respectively, and have the same
    single octet encoding.  Other Unicode characters have a
    multiple-octet UTF-8 encoding.

(Add a U+ convention note above, borrow as needed from the
stringprep documents).

>    
>        LDAPString ::= OCTET STRING -- UTF-8 encoded, 
>                                    -- ISO 10646 characters 
>    
>   The LDAPOID is a notational convenience to indicate that the 
>   permitted value of this string is a (UTF-8 encoded) dotted-decimal 
>   representation of an OBJECT IDENTIFIER. Although an LDAPOID is 
>   encoded as an OCTET STRING, values are limited to the definition of 
>   numericoid given in Section 1.3 of [Models]. 
>    
>        LDAPOID ::= OCTET STRING -- Constrained to numericoid [Models] 

Suggest you wrap the <numericoid> production in angle brackets as           
I have done in this comment.  Likewise with other productions defined
using ABNF.

>   For example, 
>    
>        1.3.6.1.4.1.1466.1.2.3 
>    
>    
>4.1.3. Distinguished Name and Relative Distinguished Name 
>    
>   An LDAPDN and a RelativeLDAPDN are respectively defined to be the 
>   representation of a distinguished-name and a relative-distinguished-
>   name after encoding according to the specification in [LDAPDN]. 

drop the hyphens and say, in the prose, which productions they
are to conform to.  Suggest you do this in two paragraphs: one
of DNs and one for RDNs.

Also, add "(DN)" and "(RDN)" to introduce these terms for later use in
the document.

>    
>        LDAPDN ::= LDAPString  
>                   -- Constrained to distinguishedName [LDAPDN] 
>    
>        RelativeLDAPDN ::= LDAPString  
>                           -- Constrained to name-component [LDAPDN] 
>    
>    
>  
>                                      
>4.1.4. Attribute Descriptions 
>    
>   The definition and encoding rules for attribute descriptions are 
>   defined in Section 2.5 of [Models]. Briefly, an attribute description 
>   is an attribute type and zero or more options. 
>    
>        AttributeDescription ::= LDAPString 
>                                 -- Constrained to attributedescription 
>                                 -- [Models] 
>         
> 
>4.1.5. Attribute Value 
>    
>   A field of type AttributeValue is an OCTET STRING containing an 
>   encoded attribute value data type. The value is encoded according to 
>   its LDAP-specific encoding definition. The LDAP-specific encoding 
>   definitions for different syntaxes and attribute types may be found 
>   in other documents and in particular [Syntaxes]. 
> 
>        AttributeValue ::= OCTET STRING 
>    
>   Note that there is no defined limit on the size of this encoding; 
>   thus protocol values may include multi-megabyte attributes (e.g. 
>   photographs). 
>    
>   Attributes may be defined which have arbitrary and non-printable 
>   syntax. Implementations MUST NOT display nor attempt to decode as 
>   ASN.1, a value if its syntax is not known. The implementation may 
>   attempt to discover the subschema of the source entry, and retrieve 
>   the values of attributeTypes from it. 

Delete "as ASN.1".

s/values of attributeTypes/descriptions of attribute types/

Add "as discussed in [Models]".

>   Clients MUST NOT send attribute values in a request that are not 
>   valid according to the syntax defined for the attributes. 
>    
>    
>4.1.6. Attribute Value Assertion 
>    
>   The AttributeValueAssertion type definition is similar to the one in 
>   the X.500 directory standards. It contains an attribute description 
>   and a matching rule assertion value suitable for that type. 
>    
>        AttributeValueAssertion ::= SEQUENCE { 
>                attributeDesc   AttributeDescription, 
>                assertionValue  AssertionValue } 
>    
>        AssertionValue ::= OCTET STRING 
>    
>   The syntax of the AssertionValue depends on the context of the LDAP 
>   operation being performed. For example, the syntax of the EQUALITY 
>   matching rule for an attribute is used when performing a Compare 
>   operation. Often this is the same syntax used for values of the 
>   attribute type, but in some cases the assertion syntax differs from 
>   the value syntax. See objectIdentiferFirstComponentMatch in 
>   [Syntaxes] for an example. 
>  
>                                      
>    
>    
>4.1.7. Attribute 
>    
>   An attribute consists of an attribute description and one or more 
>   values of that attribute description. (Though attributes MUST have at 
>   least one value when stored, due to access control restrictions the 
>   set may be empty when transferred from the server to the client. This 
>   is described in section 4.5.2, concerning the PartialAttributeList 
>   type.) 

This MUST is inappropriate (especially given that its inside of a
comment).  I suggest dealing not noting this here, but in the          
discussion of PartialAttributeList.

>    
>        Attribute ::= SEQUENCE { 
>                type    AttributeDescription, 
>                vals    SET OF AttributeValue } 
>    
>   Each attribute value is distinct in the set (no duplicates). The set 
>   of attribute values is unordered. Implementations MUST NOT reply upon 
>   any apparent ordering being repeatable. 
>    

This type is never explicitly used in the protocol.  I suggest       
AttributeList be redefined
        AttributeList ::= SEQUENCE OF ATTRIBUTE                       
 
I also suggest adding:                                
    An attribute list is used to hold a set of related attributes
    (such as those of an entry).   While the type is defined as      
    a SEQUENCE, no semantics are implied by the ordering.  Implementations
    MUST NOT rely on the ordering being repeatable.
    
Then I suggest defining PartialAttribute and PartialAttributeList.
    
>4.1.8. Matching Rule Identifier 
>    
>   Matching rules are defined in 4.1.3 of [Models]. A matching rule is 
>   identified in the LDAP protocol by the printable representation of 
>   either its numericoid, or one of its short name descriptors, e.g. 
>   "caseIgnoreIA5Match" or "1.3.6.1.4.1.453.33.33". 
>    
>        MatchingRuleId ::= LDAPString 
>    
>    
>4.1.9. Result Message 
>    
>   The LDAPResult is the construct used in this protocol to return 
>   success or failure indications from servers to clients. To various 
>   requests, servers will return responses of LDAPResult or responses 
>   containing the components of LDAPResult to indicate the final status 
>   of a protocol operation request. 
>    
>        LDAPResult ::= SEQUENCE { 
>                resultCode              ENUMERATED { 
>                        success                      (0), 
>                        operationsError              (1), 
>                        protocolError                (2), 
>                        timeLimitExceeded            (3), 
>                        sizeLimitExceeded            (4), 
>                        compareFalse                 (5), 
>                        compareTrue                  (6), 
>                        authMethodNotSupported       (7), 
>                        strongAuthRequired           (8), 
>                                        -- 9 reserved -- 
>                        referral                     (10), 
>                        adminLimitExceeded           (11), 
>                        unavailableCriticalExtension (12), 
>                        confidentialityRequired      (13), 
>  
>                                      
>                        saslBindInProgress           (14), 
>                        noSuchAttribute              (16), 
>                        undefinedAttributeType       (17), 
>                        inappropriateMatching        (18), 
>                        constraintViolation          (19), 
>                        attributeOrValueExists       (20), 
>                        invalidAttributeSyntax       (21), 
>                                        -- 22-31 unused -- 
>                        noSuchObject                 (32), 
>                        aliasProblem                 (33), 
>                        invalidDNSyntax              (34), 
>                        -- 35 reserved for undefined isLeaf -- 
>                        aliasDereferencingProblem    (36), 
>                                        -- 37-47 unused -- 
>                        inappropriateAuthentication  (48), 
>                        invalidCredentials           (49), 
>                        insufficientAccessRights     (50), 
>                        busy                         (51), 
>                        unavailable                  (52), 
>                        unwillingToPerform           (53), 
>                        loopDetect                   (54), 
>                                        -- 55-63 unused -- 
>                        namingViolation              (64), 
>                        objectClassViolation         (65), 
>                        notAllowedOnNonLeaf          (66), 
>                        notAllowedOnRDN              (67), 
>                        entryAlreadyExists           (68), 
>                        objectClassModsProhibited    (69), 
>                                -- 70 reserved for CLDAP -- 
>                        affectsMultipleDSAs          (71), 
>                                        -- 72-79 unused -- 
>                        other                        (80), 
>                        ... }, 
>                        -- 81-90 reserved for APIs -- 
>                matchedDN               LDAPDN, 
>                diagnosticMessage       LDAPString, 
>                referral                [3] Referral OPTIONAL } 
>    
>   The resultCode enumeration is extensible as defined in Section 3.5 of 
>   [LDAPIANA]. The meanings of the result codes are given in Appendix A. 
>   If a server detects multiple errors for an operation, only one result 
>   code is returned. The server should return the result code that best 
>   indicates the nature of the error encountered. 
>    
>   The diagnosticMessage field of this construct may, at the server's 
>   option, be used to return a string containing a textual, human-
>   readable (terminal control and page formatting characters should be 
>   avoided) diagnostic message. As this diagnostic message is not 
>   standardized, implementations MUST NOT rely on the values returned. 
>   If the server chooses not to return a textual diagnostic, the 
>   diagnosticMessage field of the LDAPResult type MUST contain a zero 
>   length string. 
>    

It might be better to s/contain a zero length string/be empty/.
  
>   For certain result codes (typically, but not restricted to 
>   noSuchObject, aliasProblem, invalidDNSyntax and 
>   aliasDereferencingProblem), the matchedDN field is set to the name of 
>   the lowest entry (object or alias) in the directory that was matched. 
>   If no aliases were dereferenced while attempting to locate the entry, 
>   this will be a truncated form of the name provided, or if aliases 
>   were dereferenced, of the resulting name, as defined in section 12.5 
>   of [X.511]. Unless otherwise defined, the matchedDN field contains a 
>   zero length string with all other result codes. 
    

Because of the "typically" above, suggest the last sentence be replaced  
with:
    Otherwise the matchedDN field is empty.

That is, drop the "with all other result codes".

>4.1.10. Referral 
>    
>   The referral result code indicates that the contacted server does not 
>   hold the target entry of the request. The referral field is present 
>   in an LDAPResult if the resultCode field value is referral, and 
>   absent with all other result codes. It contains one or more 
>   references to one or more servers or services that may be accessed 
>   via LDAP or other protocols. Referrals can be returned in response to 
>   any operation request (except unbind and abandon which do not have 
>   responses). At least one URL MUST be present in the Referral. 

s/URL/URI/ here and below (except when explicitly referring to an
LDAP URL).

>   During a search operation, after the baseObject is located, and 
>   entries are being evaluated, the referral is not returned. Instead, 
>   continuation references, described in section 4.5.3, are returned 
>   when the search scope spans multiple naming contexts, and several 
>   different servers would need to be contacted to complete the 
>   operation. 
>    
>        Referral ::= SEQUENCE OF URL  -- one or more 
>    
>        URL ::= LDAPString     -- limited to characters permitted in 
>                               -- URLs 
>    
s/LDAPURL/URIstring/ as the element is not restricted to LDAP URLs as
the name would otherwise imply.

>   If the client wishes to progress the operation, it MUST follow the 
>   referral by contacting one of the servers. If multiple URLs are 
>   present, the client assumes that any URL may be used to progress the 
>   operation. 

The term "server" above may be too LDAP specific.  It may be better
to use the term "service".
    
>   A URL for a server implementing LDAP and accessible via [TCP]/[IP] 
>   (v4 or v6) is written as an LDAP URL according to [LDAPURL].  
>    
>   When an LDAP URL is used, the following instructions are followed: 
>   -    If an alias was dereferenced, the <dn> part of the URL MUST be 
>        present, with the new target object name. Note that UTF-8 
>        characters appearing in a DN or search filter may not be legal 
>        for URLs (e.g. spaces) and MUST be escaped using the % method in 
>        [RFC2396].  
>   -    If the <dn> part is present, the client MUST use this name in 
>        its next request to progress the operation, and if it is not 
>        present the client will use the same name as in the original 
>        request.  
>   -    Some servers (e.g. participating in distributed indexing) may 
>        provide a different filter in a URL of a referral for a search 
>        operation. 
>   -    If the filter part of the LDAP URL is present, the client MUST 
>        use this filter in its next request to progress this search, and 
>        if it is not present the client MUST use the same filter as it 
>        used for that search. 

s/filter part/<filter> part/

>   -    Other aspects of the new request may be the same or different as 
>        the request which generated the referral. 

As discussed on the LDAPEXT when the namedref I-D (now RFC 3296)
was being considered for publication, the LDAP TS is flawed in      
that it does not explictly say that absense other URL parts, such  
as the scope part, have different semantics than those specified in      
RFC 2255 yet provides examples which suggest different semantics of      
other absent parts.  This has lead to interoperability problems.         

It has also noted there have been interoperability problems when        
the DN field has been absent.  This may be caused by the statement    
"The SearchResultReference is of the same data type as the Referral"
which impies referrals and referrences have the same semantics.
Howver, an empty DN part in a reference is a continuation names          
a root DSE but an empty DN part refers to the entry named in the
search.

(It was noted that current DN referral semantic disallows one from
generating a referral (for a non-root DSE search) to a root DSE.
However, I don't think anyone ever explained why that capability
(or the capability to continue a search to the root DSE) would           
be a useful.  Anyways, I only note this for completeness.)             

To resolve the interoperability problems, I suggest the following       
changes be made to the specification of references AND search     
continuation refererences.
    1) expand the referral and reference text to say that absense        
    scope part implies the scope of the search which requested the
    response.
    2) For all operations, RECOMMEND that dn part be provided
    3) For the search operation, RECOMMEND that the scope field  
    also be provided.
    4) update examples to be consistent with RFC 3296

>    
>   Other kinds of URLs may be returned, so long as the operation could 
>   be performed using that protocol. The definition of such URLs and 
>   instructions on their use is left to future specifications. 
>    
>    
>4.1.11. Controls 

This section should be reorganized such that the discussion
of what a control specification consists of follows this
document's specification of control syntax and semantics.

>    
>   A control is a way to specify extension information for an LDAP 
>   message. A control only alters the semantics of the message it is 
>   attached to. 
>    
>        Controls ::= SEQUENCE OF Control 
>    
>        Control ::= SEQUENCE { 
>                controlType             LDAPOID, 
>                criticality             BOOLEAN DEFAULT FALSE, 
>                controlValue            OCTET STRING OPTIONAL } 
>    
>   The controlType field MUST be a UTF-8 encoded dotted-decimal 
>   representation of an OBJECT IDENTIFIER which uniquely identifies the 
>   control. This prevents conflicts between control names. 

s/MUST be a/is the/

Question?  Are there existing control extensions which use one OID
to identify both a request control and a paired response control.
If so (especially if any of these are standard track), the following
should be added ", or a request control and its paired response
control".

>    
>   The criticality field is either TRUE or FALSE and only applies to 
>   request messages that have a corresponding response message. For all 
>   other messages (such as abandonRequest, unbindRequest and all 
>   response messages), the criticality field is treated as FALSE. 

I think this may require some recoding of implementations which
don't treat such critical request controls as non-critical.  I would
rather just say:

    For other messages (such as ...), the criticality field SHOULD     
    be FALSE.

>   If the server recognizes the control type and it is appropriate for 
>   the operation, the server will make use of the control when 
>   performing the operation. 
>    
>   If the server does not recognize the control type or it is not 
>   appropriate for the operation, and the criticality field is TRUE, the 
>   server MUST NOT perform the operation, and MUST instead set the 
>   resultCode to unavailableCriticalExtension. 


Replace with:

    If the server does not recongize the control type or it is
    not appropriate for the operation, and the criticality field
    is TRUE, the server MUST NOT perform the operation and MUST,
    for operations which have responses, return the resultCode
    unavailableCriticalExtension.

>    
>   If the control is unrecognized or inappropriate but the criticality 
>   field is FALSE, the server MUST ignore the control. 
>    
>   The controlValue contains any information associated with the 
>   control. Its format is defined by the specification of the control. 
>   Implementations MUST be prepared to handle arbitrary contents of the 
>   controlValue octet string, including zero bytes. It is absent only if 
>   there is no value information which is associated with a control of 
>   its type. controlValues that are defined in terms of ASN.1 and BER 
>   encoded according to Section 5.1, also follow the extensibility rules 
>   in Section 4. 
>
>   This document does not specify any controls. Controls may be 
>   specified in other documents. The specification of a control consists 
>   of: 
>    
>   - the OBJECT IDENTIFIER assigned to the control, 
>    
>   - whether the control is always non critical, always critical, or 
>     critical at the client's option, 

s/critical at the client's option/optionally critical/
    
>   - the format of the controlValue contents of the control, 

replace with
    - whether there is control information associated with the control
	and, if so, the format of the controlValue contents,
>    
>   - the semantics of the control, 
>    
>   - and optionally, semantics regarding the combination of the control 
>     with other controls. 

Move the "and" from beginning of the last item to the
end of the second to last item.


>   Servers list the controlType of all request controls they recognize 
>   in the supportedControl attribute [Models] in the root DSE. 
> 
>   Controls should not be combined unless the semantics of the 
>   combination has been specified.

Uppercase this SHOULD NOT.  That is, implementatoins SHOULD NOT combine
controls without understanding how they combine.

>   The semantics of control 
>   combinations, if specified, are generally found in the control 
>   specification most recently published. In the absence of combination 
>   semantics, the behavior of the operation is undefined.  
>   Additionally, the order of a combination of controls in the SEQUENCE 
>   is ignored unless the control specification(s) describe(s) 
>   combination semantics. 

Replace last with
    Additionally, the order of a combination of controls in the
    SEQUENCE implies no semantics unless the specification for
    that combination defines order-dependent semantics. 
>    
>    
>4.2. Bind Operation 
>    
>   The function of the Bind Operation is to allow authentication 
>   information to be exchanged between the client and server. Prior to 
>   the first BindRequest, the implied identity is anonymous. Refer to 
>   [AuthMeth] for the authentication-related semantics of this 
>   operation.  

I suggest dropping second sentence as it is covered in in [AuthMeth].
I suggest rewording the second sentence:

    Authententication and security related semantics of this
    operation are detailed in [AuthMeth].

(I would not say the "implied identity is anonymous" but that
"the LDAP association is anonymous."  That is, the protocol
peers have not established their identities.  Anonymous is not
an identity.)

>   The Bind Request is defined as follows: 
>    
>        BindRequest ::= [APPLICATION 0] SEQUENCE { 
>                version                 INTEGER (1 .. 127), 
>                name                    LDAPDN, 
>                authentication          AuthenticationChoice } 
>    
>        AuthenticationChoice ::= CHOICE { 
>                simple                  [0] OCTET STRING, 
>                                         -- 1 and 2 reserved 
>                sasl                    [3] SaslCredentials, 
>                ... } 
>  
>                                      
>    
>        SaslCredentials ::= SEQUENCE { 
>                mechanism               LDAPString, 
>                credentials             OCTET STRING OPTIONAL } 
>    
>   Parameters of the Bind Request are: 
>    
>   - version: A version number indicating the version of the protocol 
>     to be used in this protocol association. This document describes 
>     version 3 of the LDAP protocol. Note that there is no version 
>     negotiation, and the client just sets this parameter to the 
>     version it desires. If the server does not support the specified 
>     version, it MUST respond with protocolError in the resultCode 
>     field of the BindResponse. 

delete the word "just".

>   - name: The name of the directory object that the client wishes to 
>     bind as. This field may take on a null value (a zero length 
>     string) for the purposes of anonymous binds ([AuthMeth] section 7) 
>     or when using SASL authentication ([AuthMeth] section 4.3). Server 
>     behavior is undefined when the name is a null value, simple 
>     authentication is used, and a password is specified. The server 
>     SHOULD NOT perform any alias dereferencing in determining the 
>     object to bind as. 

delete the word "any".
spell out SASL on first use (in body).

>   - authentication: information used to authenticate the name, if any, 
>     provided in the Bind Request. This type is extensible as defined 
>     in Section 3.6 of [LDAPIANA]. Servers that do not support a choice 
>     supplied by a client will return authMethodNotSupported in the 
>     resultCode field of the BindResponse. The simple form of an 
>     AuthenticationChoice specifies a simple password to be used for 
>     authentication. To improve matching, applications SHOULD prepare 
>     textual strings used as passwords. Applications which prepare 
>     textural strings used as password are REQUIRED to prepare them by 
>     transcoding the string to [Unicode], apply [SASLprep], and encode 
>     as UTF-8. 
    
(see list comments)

>   Authorization is the use of this authentication information when 
>   performing operations. Authorization MAY be affected by factors 
>   outside of the LDAP Bind Request, such as lower layer security 
>   services. 

s/such as/such as factors provided by/
>    
>    
>4.2.1. Processing of the Bind Request 
>    
>   Upon receipt of a BindRequest, the server MUST ensure there are no 
>   outstanding operations in progress on the connection (this simplifies 
>   server implementation).

The note implies the purpose of the MUST is simplify server    
implementations.  Per RFC 2119, such MUSTs should be avoided.
However, the real purpose of this MUST is to ensure that operations
received prior to the bind are completed (or abandoned) before the
establishment of a new LDAP association.  The sentence needs some
word smithing.

>   To do this, the server may cause them to be 
>   abandoned or allow them to finish. The server then proceeds to 
>   authenticate the client in either a single-step, or multi-step bind 
>   process. Each step requires the server to return a BindResponse to 
>   indicate the status of authentication.  
>    
>   If the client did not bind before sending a request and receives an 
>   operationsError, it may then send a Bind Request. If this also fails 

s/operationsError/operationsError in response to that request/
>                                      
>   or the client chooses not to bind on the existing connection, it may 
>   close the connection, reopen it and begin again by first sending a 
>   PDU with a Bind Request. This will aid in interoperating with servers 
>   implementing other versions of LDAP. 
>    
>   Clients MAY send multiple Bind Requests on a connection to change 
>   their credentials.


Down case this "MAY".

s/their credentials/authentication and/or security associations or
to complete a multi-stage bind process./

>   Authentication from earlier binds is subsequently ignored. 

>   For some SASL authentication mechanisms, it may be necessary for the 
>   client to invoke the BindRequest multiple times. This is indicated by 
>   the server sending a BindResponse with the resultCode set to 
>   saslBindInProgress. This indicates that the server requires the 
>   client to send a new bind request, with the same sasl mechanism, to 
>   continue the authentication process. If at any stage the client 
>   wishes to abort the bind process it MAY unbind and then drop the 
>   underlying connection. Clients MUST NOT invoke operations between two 
>   Bind Requests made as part of a multi-stage bind. 
>    
>   A client may abort a SASL bind negotiation by sending a BindRequest 
>   with a different value in the mechanism field of SaslCredentials, or 
>   an AuthenticationChoice other than sasl. 
>    
>   If the client sends a BindRequest with the sasl mechanism field as an 
>   empty string, the server MUST return a BindResponse with 
>   authMethodNotSupported as the resultCode. This will allow clients to 
>   abort a negotiation if it wishes to try again with the same SASL 
>   mechanism. 
>    
>   A failed Bind Operation has the effect of leaving the connection in 
>   an anonymous state. An abandoned Bind operation also has the effect 
>   of leaving the connection in an anonymous state when (and if) the 
>   server processes the abandonment of the bind.  Client implementers 
>   should note that the client has no way of being sure when (or if) an 
>   abandon request succeeds, therefore, to arrive at a known 
>   authentication state after abandoning a bind operation, clients may 
>   either unbind (which results in the underlying connection being 
>   closed) or by issuing a bind request and then examining the 
>   BindResponse returned by the server. 
>    
>4.2.2. Bind Response 
>    
>   The Bind Response is defined as follows. 
>    
>        BindResponse ::= [APPLICATION 1] SEQUENCE { 
>             COMPONENTS OF LDAPResult, 
>             serverSaslCreds    [7] OCTET STRING OPTIONAL } 
>    
>   BindResponse consists simply of an indication from the server of the 
>   status of the client's request for authentication. 
>    
>   A successful bind operation is indicated by a BindResponse with a 
>   resultCode set to success. Otherwise, an appropriate result code is 
>   set in the BindResponse. For bind, the protocolError result code may 
>  
>                                      
>   be used to indicate that the version number supplied by the client is 
>   unsupported. 
> 
>   If the client receives a BindResponse response where the resultCode 
>   field is protocolError, it MUST close the connection as the server 
>   will be unwilling to accept further operations. (This is for 
>   compatibility with earlier versions of LDAP, in which the bind was 
>   always the first operation, and there was no negotiation.) 
>    
>   The serverSaslCreds are used as part of a SASL-defined bind mechanism 
>   to allow the client to authenticate the server to which it is 
>   communicating, or to perform "challenge-response" authentication. If 
>   the client bound with the simple choice, or the SASL mechanism does 
>   not require the server to return information to the client, then this 
>   field is not to be included in the BindResponse. 
>    
>    
>4.3. Unbind Operation 
>    
>   The function of the Unbind Operation is to terminate an LDAP 
>   association and connection. The Unbind Operation is defined as 
>   follows: 
>    
>        UnbindRequest ::= [APPLICATION 2] NULL 
>    
>   The Unbind Operation has no response defined. Upon transmission of an 
>   UnbindRequest, a protocol client MUST assume that the LDAP 
>   association is terminated.

and close the connection?   Or reword,
    Upon transmission of the UnbindRequest, the client is to consider   
    the LDAP association terminated, MUST NOT transmit additional      
    LDAP PDUs, and MUST close the connection.
               
A client shouldn't wait on the server.... it could be a long wait. 

>   Upon receipt of an UnbindRequest, a 
>   protocol server MUST assume that the requesting client has terminated 
>   the association and that all outstanding requests may be discarded, 
>   and MUST close the connection. 
>    

Reword,
    Upon receipt of an UnbindRequest, the server is to consider the
    LDAP associated terminated, MUST cease transmission of messages
    to the client, and MUST close the connection.  Any outstanding
    operations are, when possible, abandoned and, when not possible,
    completed without transmission of the response.

>    
>4.4. Unsolicited Notification 
>    
>   An unsolicited notification is an LDAPMessage sent from the server to 
>   the client which is not in response to any LDAPMessage received by 
>   the server. It is used to signal an extraordinary condition in the 
>   server or in the connection between the client and the server. The 
>   notification is of an advisory nature, and the server will not expect 
>   any response to be returned from the client. 
>    
>   The unsolicited notification is structured as an LDAPMessage in which 
>   the messageID is 0 and protocolOp is of the extendedResp form. The 
>   responseName field of the ExtendedResponse is present. The LDAPOID 
>   value MUST be unique for this notification, and not be used in any 
>   other situation. 

Replace last two sentences with:
    The responseName field of the ExtendedResponse is always present
    and contains the dotted-decimal representation of the unique
    OBJECT IDENTIFIER corresponding to the notification.

>   One unsolicited notification (Notice of Disconnection) is defined in 
>   this document. 
>    
>    
>4.4.1. Notice of Disconnection 
>    
>   This notification may be used by the server to advise the client that 
>   the server is about to close the connection due to an error 
>   condition. Note that this notification is NOT a response to an unbind 
>   requested by the client: the server MUST follow the procedures of 
>   section 4.3. This notification is intended to assist clients in 
>   distinguishing between an error condition and a transient network 
>   failure. As with a connection close due to network failure, the 
>   client MUST NOT assume that any outstanding requests which modified 
>   the directory have succeeded or failed. 
>    
>   The responseName is 1.3.6.1.4.1.1466.20036, the response field is 
>   absent, and the resultCode is used to indicate the reason for the 
>   disconnection. 
>    
>   The following result codes have these meanings when used in this 
>   notification: 
>    
>   - protocolError: The server has received data from the client in 
>     which the LDAPMessage structure could not be parsed. 
>    
>   - strongAuthRequired: The server has detected that an established 
>     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. 
>    
>   - unavailable: This server will stop accepting new connections and 
>     operations on all existing connections, and be unavailable for an 
>     extended period of time. The client may make use of an alternative 
>     server. 
>    
>   After sending this notice, the server MUST close the connection. 

Reword:
    After sending this notice, the server is to consider the LDAP      
    association terminated, MUST NOT transmit additional LDAP PDUs,
    and MUST close the connection.

>   After receiving this notice, the client MUST NOT transmit any further 
>   on the connection, and may abruptly close the connection. 

Reword:
    Upon receiving this notice, the client MUST cease transmitting
    messages to the server and close the connection.


Insert here a statement as to what a specification of a Notice
of Disconnect consists of.

>    
>    
>4.5. Search Operation 
>    
>   The Search Operation allows a client to request that a search be 
>   performed on its behalf by a server.

I suggest:
    The Search Operation provides mechanism for a client to request
    and a server to return, subject to access controls and other         
    restrictions, a set of entries matching a complex search criteria.

>   This can be used to read 
>   attributes from a single entry, from entries immediately below a 
>   particular entry, or a whole subtree of entries. 
>    
>    
>4.5.1. Search Request 
>    
>   The Search Request is defined as follows: 
>    
>        SearchRequest ::= [APPLICATION 3] SEQUENCE { 
>                baseObject      LDAPDN, 
>                scope           ENUMERATED { 
>                        baseObject              (0), 
>                        singleLevel             (1), 
>                        wholeSubtree            (2) }, 
>                derefAliases    ENUMERATED { 
>  
>                                      
>                        neverDerefAliases       (0), 
>                        derefInSearching        (1), 
>                        derefFindingBaseObj     (2), 
>                        derefAlways             (3) }, 
>                sizeLimit       INTEGER (0 .. maxInt), 
>                timeLimit       INTEGER (0 .. maxInt), 
>                typesOnly       BOOLEAN, 
>                filter          Filter, 
>                attributes      AttributeSelection } 
>    
>        AttributeSelection ::= SEQUENCE OF 
>                LDAPString 
>                -- constrained to the attributeSelection below  
>    
>        Filter ::= CHOICE { 
>                and             [0] SET SIZE (1..MAX) OF Filter, 
>                or              [1] SET SIZE (1..MAX) OF Filter, 
>                not             [2] Filter, 
>                equalityMatch   [3] AttributeValueAssertion, 
>                substrings      [4] SubstringFilter, 
>                greaterOrEqual  [5] AttributeValueAssertion, 
>                lessOrEqual     [6] AttributeValueAssertion, 
>                present         [7] AttributeDescription, 
>                approxMatch     [8] AttributeValueAssertion, 
>                extensibleMatch [9] MatchingRuleAssertion } 
>    
>        SubstringFilter ::= SEQUENCE { 
>                type            AttributeDescription, 
>                -- at least one must be present, 
>                -- initial and final can occur at most once 
>                substrings      SEQUENCE OF CHOICE { 
>                        initial [0] AssertionValue, 
>                        any     [1] AssertionValue, 
>                        final   [2] AssertionValue } } 
>    
>        MatchingRuleAssertion ::= SEQUENCE { 
>                matchingRule    [1] MatchingRuleId OPTIONAL, 
>                type            [2] AttributeDescription OPTIONAL, 
>                matchValue      [3] AssertionValue, 
>                dnAttributes    [4] BOOLEAN DEFAULT FALSE } 
>    
>   Parameters of the Search Request are: 
>    
>   - baseObject: An LDAPDN that is the base object entry relative to 
>     which the search is to be performed. 
>    
>   - scope: An indicator of the scope of the search to be performed. 
>     The semantics of the possible values of this field are identical 
>     to the semantics of the scope field in the X.511 Search Operation. 
>    

Describe each of the possible values of this field in this document and
then note that they are the same as those used in the X.511 operation.

>   - derefAliases: An indicator as to how alias objects (as defined in 
>     [X.501]) are to be handled in searching. The semantics of the 
>     possible values of this field are: 
>    
>             neverDerefAliases: Do not dereference aliases in searching 
>             or in locating the base object of the search. 
>    
>             derefInSearching: While searching, dereference any alias 
>             object subordinate to the base object which is also in the 
>             search scope. The filter is applied to the dereferenced 
>             object(s). If the search scope is wholeSubtree, the search 
>             continues in the subtree of any dereferenced object. 
>             Aliases in that subtree are also dereferenced. Servers 
>             SHOULD detect looping in this process to prevent denial of 
>             service attacks and duplicate entries. 
>              
>             derefFindingBaseObj: Dereference aliases in locating the 
>             base object of the search, but not when searching 
>             subordinates of the base object. 
>    
>             derefAlways: Dereference aliases both in searching and in 
>             locating the base object of the search. 
>    
>   - sizeLimit: A size limit that restricts the maximum number of 
>     entries to be returned as a result of the search. A value of 0 in 
>     this field indicates that no client-requested size limit 
>     restrictions are in effect for the search. Servers may enforce a 
>     maximum number of entries to return. 
>    
>   - timeLimit: A time limit that restricts the maximum time (in 
>     seconds) allowed for a search. A value of 0 in this field 
>     indicates that no client-requested time limit restrictions are in 
>     effect for the search. 

As with sizeLimit, may servers enforce a maximun time for the search?

>   - typesOnly: An indicator as to whether search results will contain 
>     both attribute descriptions and values, or just attribute 
>     descriptions. Setting this field to TRUE causes only attribute 
>     descriptions (no values) to be returned. Setting this field to 
>     FALSE causes both attribute descriptions and values to be 
>     returned. 

s/will/are to/

>   - filter: A filter that defines the conditions that must be 
>     fulfilled in order for the search to match a given entry. 
>      
>     The 'and', 'or' and 'not' choices can be used to form combinations 
>     of filters. At least one filter element MUST be present in an 
>     'and' or 'or' choice. The others match against individual 
>     attribute values of entries in the scope of the search. 
>     (Implementor's note: the 'not' filter is an example of a tagged 
>     choice in an implicitly-tagged module. In BER this is treated as 
>     if the tag was explicit.) 
>    
>     A server MUST evaluate filters according to the three-valued logic 
>     of X.511 (1993) section 7.8.1. In summary, a filter is evaluated 
>     to either "TRUE", "FALSE" or "Undefined". If the filter evaluates 
>     to TRUE for a particular entry, then the attributes of that entry 
>     are returned as part of the search result (subject to any 
>     applicable access control restrictions). If the filter evaluates 
>     to FALSE or Undefined, then the entry is ignored for the search. 
>      
>     A filter of the "and" choice is TRUE if all the filters in the SET 
>     OF evaluate to TRUE, FALSE if at least one filter is FALSE, and 
>     otherwise Undefined. A filter of the "or" choice is FALSE if all 
>     of the filters in the SET OF evaluate to FALSE, TRUE if at least 
>     one filter is TRUE, and Undefined otherwise. A filter of the "not" 
>     choice is TRUE if the filter being negated is FALSE, FALSE if it 
>     is TRUE, and Undefined if it is Undefined. 
>      
>     The present match evaluates to TRUE where there is an attribute or 
>     subtype of the specified attribute description present in an 
>     entry, and FALSE otherwise (including a presence test with an 
>     unrecognized attribute description.) 
>      
>     The matching rule for equalityMatch filter items is defined by the 
>     EQUALITY matching rule for the attribute type. 
>    
>     The matching rule for AssertionValues in a substrings filter item 
>     is defined by the SUBSTR matching rule for the attribute type. 
>     Note that the AssertionValue in a substrings filter item MUST 
>     conform to the assertion syntax of the EQUALITY matching rule for 
>     the attribute type rather than the assertion syntax of the SUBSTR 
>     matching rule for the attribute type.  The entire SubstringFilter 
>     is converted into an assertion value of the substrings matching 
>     rule prior to applying the rule. 
>    
>     The matching rule for greaterOrEqual and lessOrEqual filter items 
>     is defined by the ORDERING matching rule for the attribute type. 
>    
>     The matching semantics for approxMatch filter items is 
>     implementation-defined. If approximate matching is not supported 
>     by the server, the filter item should be treated as an 
>     equalityMatch. 

approxMatch is not 100% implementation defined.   In particular,
the implementation must ensure that all values which match per the
equality rule match per the approximate rule.

>     The extensibleMatch is new in this version of LDAP. If the 
>     matchingRule field is absent, the type field MUST be present, and 
>     the equality match is performed for that type. If the type field 
>     is absent and matchingRule is present, the matchValue is compared 
>     against all attributes in an entry which support that 
>     matchingRule, and the matchingRule determines the syntax for the 
>     assertion value (the filter item evaluates to TRUE if it matches 
>     with at least one attribute in the entry, FALSE if it does not 
>     match any attribute in the entry, and Undefined if the 
>     matchingRule is not recognized or the assertionValue cannot be 
>     parsed.)

replace "cannot be parsed" with "is invalid."   Also, this shouldn't
be a comment (e.g., remove the wrapping parens).

>     If the type field is present and matchingRule is present, 
>     the matchingRule MUST be one permitted for use with that type, 
>     otherwise the filter item is undefined. If the dnAttributes field 
>     is set to TRUE, the match is applied against all the 
>     AttributeValueAssertions in an entry's distinguished name as well, 
>     and also evaluates to TRUE if there is at least one attribute in 
>     the distinguished name for which the filter item evaluates to 
>     TRUE. (Editors note: The dnAttributes field is present so that 
>     there does not need to be multiple versions of generic matching 
>     rules such as for word matching, one to apply to entries and 
>     another to apply to entries and dn attributes as well). 
>      
>     A filter item evaluates to Undefined when the server would not be 
>     able to determine whether the assertion value matches an entry. If 
>     an attribute description in an equalityMatch, substrings, 
>     greaterOrEqual, lessOrEqual, approxMatch or extensibleMatch filter 
>     is not recognized by the server, a matching rule id in the 
>     extensibleMatch is not recognized by the server, the assertion 
>     value cannot be parsed, or the type of filtering requested is not 
s/parsed/invalid/
>     implemented, then the filter is Undefined. Thus for example if a 
>     server did not recognize the attribute type shoeSize, a filter of 
>     (shoeSize=*) would evaluate to FALSE, and the filters 
>     (shoeSize=12), (shoeSize>=12) and (shoeSize<=12) would evaluate to 
>     Undefined. 
>      


>     Servers MUST NOT return errors if attribute descriptions or 
>     matching rule ids are not recognized, or assertion values cannot 
>     be parsed. More details of filter processing are given in section 
>     7.8 of [X.511]. 

"Cannot be parsed" can mean:              
    1) the assertion value is invalid or
    2) the server does not support the assertion syntax.                
 
We likely should elaborate on what "cannot be parsed" means.

>   - attributes: A list of the attributes to be returned from each 
>     entry which matches the search filter. LDAPString values of this 
>     field are constrained to the following ABNF: 
>    
>     attributeSelection = noattrs /  
>                         *( attributedescription / specialattr ) 
>    
>     noattrs = %x31 %x2E %x31 ; "1.1" 
>    
>     attributedescription = ; attributedescription from 2.5 of [Models] 
>    
>     specialattr = ASTERISK 
>    
>     ASTERISK = %x2A ; asterisk ("*") 
>    
>     There are two special values which may be used: an empty list with 
>     no attributes, and the attribute description string "*". Both of 
>     these signify that all user attributes are to be returned. (The 
>     "*" allows the client to request all user attributes in addition 
>     to any specified operational attributes). 
>      
>     Attributes MUST be named at most once in the list, and are 
>     returned at most once in an entry. If there are attribute 
>     descriptions in the list which are not recognized, they are 
>     ignored by the server. 
>      
>     If the client does not want any attributes returned, it can 
>     specify a list containing only the attribute with OID "1.1". This 
>     OID was chosen arbitrarily and does not correspond to any 
>     attribute in use. 

This OID was not chosen arbitrarily.  It was choose because it does   
not, and will never, correspond to any attribute in use.  So, replace 
the sentence with:
    (This OID was choosen because it is retired.)                      

(It would be nice if we could provide an informative reference to
some document which states 1.1 is retired.)

>      
>     Client implementors should note that even if all user attributes 
>     are requested, some attributes of the entry may not be included in 
>  
s/some attribute/some attribute (and/or some values of some attributes)/

>     search results due to access controls or other restrictions. 
>     Furthermore, servers will not return operational attributes, such 
>     as objectClasses or attributeTypes, unless they are listed by 
>     name, since there may be extremely large number of values for 
>     certain operational attributes. (A list of operational attributes 
>     for use in LDAP is given in [Syntaxes].) 
>    
>   Note that an X.500 "list"-like operation can be emulated by the 
>   client requesting a one-level LDAP search operation with a filter 
>   checking for the presence of the objectClass attribute, and that an 
>   X.500 "read"-like operation can be emulated by a base object LDAP 
>   search operation with the same filter. A server which provides a 
>   gateway to X.500 is not required to use the Read or List operations, 
>   although it may choose to do so, and if it does, it must provide the 
>   same semantics as the X.500 search operation. 
>    
>    
>4.5.2. Search Result 
>    
>   The results of the search attempted by the server upon receipt of a 
>   Search Request are returned in Search Responses, which are LDAP 
>   messages containing SearchResultEntry, SearchResultReference, or 
>   SearchResultDone data types. 

Suggest the above sentence be reworded (with further edits below).
    The results of the search operation are returned by the server
    in a series of response PDUs:  zero or more searchResultEntry   
    or SearchResultReference messages followed by one searchResultDone
    messages.

>    
>        SearchResultEntry ::= [APPLICATION 4] SEQUENCE { 
>                objectName      LDAPDN, 
>                attributes      PartialAttributeList } 
>    
>        PartialAttributeList ::= SEQUENCE OF SEQUENCE { 
>                type    AttributeDescription, 
>                vals    SET OF AttributeValue } 
>        -- implementors should note that the PartialAttributeList may 
>        -- have zero elements (if none of the attributes of that entry 
>        -- were requested, or could be returned), and that the vals set 
>        -- may also have zero elements (if types only was requested, or 
>        -- all values were excluded from the result.) 
>    
>        SearchResultReference ::= [APPLICATION 19] SEQUENCE OF URL 
>        -- at least one URL element must be present 
>    
>        SearchResultDone ::= [APPLICATION 5] LDAPResult 
>    
>   Upon receipt of a Search Request, a server will perform the necessary 
>   search of the DIT. 

Spell out DIT.

This sentence is somewhat redundant with statements above...          
also note that a search is not required to perform the necessary       
search (for instance, it could return an busy error).

>   The server will return to the client a sequence of responses in 
>   separate LDAP messages. There may be zero or more responses 
>   containing SearchResultEntry, one for each entry found during the 
>   search. There may also be zero or more responses containing 
>   SearchResultReference, one for each area not explored by this server 
>   during the search. The SearchResultEntry and SearchResultReference 
>   PDUs may come in any order. Following all the SearchResultReference 
>   responses and all SearchResultEntry responses to be returned by the 
>   server, the server will return a response containing the 
>   SearchResultDone, which contains an indication of success, or 
>   detailing any errors that have occurred. 
>    
>   Each entry returned in a SearchResultEntry will contain all 
>   appropriate attributes as specified in the attributes field of the 
>   Search Request. Return of attributes is subject to access control and 
>   other administrative policy. 
>    
>   Some attributes may be constructed by the server and appear in a 
>   SearchResultEntry attribute list, although they are not stored 
>   attributes of an entry. Clients SHOULD NOT assume that all attributes 
>   can be modified, even if permitted by access control. 
>    
>   If the server's schema defines a textual name for an attribute type, 
>   it SHOULD use a textual name for attributes of that attribute type by 
>   specifying one of the textual names as the value of the attribute 
>   type. Otherwise, the server uses the object identifier for the 
>   attribute type by specifying the object identifier, in ldapOID form, 
>   as the value of attribute type. If the server determines that 
>   returning a textual name will cause interoperability problems, it 
>   SHOULD return the ldapOID form of the attribute type. 

"ldapOID form"?  I think you mean <numericoid> form. 
    
>4.5.3. Continuation References in the Search Result 
    
(see referral comments)

>   If the server was able to locate the entry referred to by the 
>   baseObject but was unable to search all the entries in the scope at 
>   and under the baseObject, the server may return one or more 
>   SearchResultReference entries, each containing a reference to another 
>   set of servers for continuing the operation. A server MUST NOT return 
>   any SearchResultReference if it has not located the baseObject and 
>   thus has not searched any entries; in this case it would return a 
>   SearchResultDone containing a referral result code. 
>    
>   If a server holds a copy or partial copy of the subordinate naming 
>   context, it may use the search filter to determine whether or not to 
>   return a SearchResultReference response. Otherwise 
>   SearchResultReference responses are always returned when in scope. 
>    
>   The SearchResultReference is of the same data type as the Referral.  
>    
>   A URL for a server implementing LDAP and accessible via [TCP]/[IP] 
>   (v4 or v6) is written as an LDAP URL according to [LDAPURL].  
>    
>   When an LDAP URL is used, the following instructions are followed: 
>   -    The <dn> part of the URL MUST be present, with the new target 
>        object name. The client MUST use this name when following the 
>        referral. Note that UTF-8 characters appearing in a DN or search 
>        filter may not be legal for URLs (e.g. spaces) and MUST be 
>        escaped using the % method in [RFC2396].  
>   -    Some servers (e.g. participating in distributed indexing) may 
>        provide a different filter in a URL of a SearchResultReference. 
>   -    If the filter part of the URL is present, the client MUST use 
>        this filter in its next request to progress this search, and if 
>  
>                                      
>        it is not present the client MUST use the same filter as it used 
>        for that search.  
>   -    If the originating search scope was singleLevel, the scope part 
>        of the URL will be baseObject. 
>   -    Other aspects of the new search request may be the same or 
>        different as the search request which generated the 
>        SearchResultReference. 
>   -    The name of an unexplored subtree in a SearchResultReference 
>        need not be subordinate to the base object. 
> 
>   Other kinds of URLs may be returned, so long as the operation could 
>   be performed using that protocol. The definition of such URLs and 
>   instructions on their use is left to future specifications. 
> 
>   In order to complete the search, the client MUST issue a new search 
>   operation for each SearchResultReference that is returned. Note that 
>   the abandon operation described in section 4.11 applies only to a 
>   particular operation sent on an association between a client and 
>   server, and if the client has multiple outstanding search operations, 
>   it MUST abandon each operation individually. 

I suggest these MUSTs here be dropped.
	s/MUST issue/issues/
    s/it MUST abandon each operation individually       
     /each operation needs to be separately abandoned/
    
>4.5.3.1. Example 

see referral comments

>    
>   For example, suppose the contacted server (hosta) holds the entry 
>   "DC=Example,DC=NET" and the entry "CN=Manager,DC=Example,DC=NET". It 
>   knows that either LDAP-capable servers (hostb) or (hostc) hold 
>   "OU=People,DC=Example,DC=NET" (one is the master and the other server 
>   a shadow), and that LDAP-capable server (hostd) holds the subtree 
>   "OU=Roles,DC=Example,DC=NET". If a subtree search of 
>   "DC=Example,DC=NET" is requested to the contacted server, it may 
>   return the following: 
>    
>     SearchResultEntry for DC=Example,DC=NET 
>     SearchResultEntry for CN=Manager,DC=Example,DC=NET 
>     SearchResultReference { 
>       ldap://hostb/OU=People,DC=Example,DC=NET 
>       ldap://hostc/OU=People,DC=Example,DC=NET } 
>     SearchResultReference { 
>       ldap://hostd/OU=Roles,DC=Example,DC=NET } 
>     SearchResultDone (success) 
>    
>   Client implementors should note that when following a 
>   SearchResultReference, additional SearchResultReference may be 
>   generated. Continuing the example, if the client contacted the server 
>   (hostb) and issued the search for the subtree 
>   "OU=People,DC=Example,DC=NET", the server might respond as follows: 
>    
>     SearchResultEntry for OU=People,DC=Example,DC=NET 
>     SearchResultReference { 
>       ldap://hoste/OU=Managers,OU=People,DC=Example,DC=NET } 
>     SearchResultReference { 
>       ldap://hostf/OU=Consultants,OU=People,DC=Example,DC=NET } 
>     SearchResultDone (success) 
>  
>                                      
>    
>   If the contacted server does not hold the base object for the search, 
>   then it will return a referral to the client. For example, if the 
>   client requests a subtree search of "DC=Example,DC=ORG" to hosta, the 
>   server may return only a SearchResultDone containing a referral. 
>    
>     SearchResultDone (referral) { 
>       ldap://hostg/DC=Example,DC=ORG??sub } 
>    
>    
>4.6. Modify Operation 
>    
>   The Modify Operation allows a client to request that a modification 
>   of an entry be performed on its behalf by a server. The Modify 
>   Request is defined as follows: 
>    
>        ModifyRequest ::= [APPLICATION 6] SEQUENCE { 
>                object          LDAPDN, 
>                changes         SEQUENCE OF SEQUENCE { 
>                        operation       ENUMERATED { 
>                                                add     (0), 
>                                                delete  (1), 
>                                                replace (2) }, 
>                        modification    Attribute } } 
> 
>   Parameters of the Modify Request are: 
>    
>   - object: The object to be modified. The value of this field 
>     contains the DN of the entry to be modified. The server will not 
>     perform any alias dereferencing in determining the object to be 
>     modified. 

s/The object/The Distinguished Name of the object/

(this partially aligns the text with that of Add.entry description,      
more work is likely need to align Modify.object, Add.entry, and         
other DN field texts

>   - changes: A list of modifications to be performed on the entry. The 
>     entire list of modifications MUST be performed in the order they 
>     are listed, as a single atomic operation. While individual 
>     modifications may violate certain aspects of the directory schema 
>     (such as the object class definition and DIT content rule), the 
>     resulting entry after the entire list of modifications is 
>     performed MUST conform to the requirements of the directory 
>     schema. 
>    
>   -   operation: Used to specify the type of modification being 
>       performed. Each operation type acts on the following 
>       modification. The values of this field have the following  
>       semantics respectively: 
>    
>             add: add values listed to the modification attribute, 
>             creating the attribute if necessary; 
>    
>             delete: delete values listed from the modification 
>             attribute, removing the entire attribute if no values are 
>             listed, or if all current values of the attribute are 
>             listed for deletion; 
>    
>  
>                                      
>             replace: replace all existing values of the modification 
>             attribute with the new values listed, creating the 
>             attribute if it did not already exist. A replace with no 
>             value will delete the entire attribute if it exists, and is 
>             ignored if the attribute does not exist. 
>    
>   -   modification: An Attribute (which may have an empty SET of vals) 
>       used to hold the Attribute Type or Attribute Type and values 
>       being modified. 
>    
>   The result of the modification attempted by the server upon receipt 
>   of a Modify Request is returned in a Modify Response, defined as 
>   follows: 
>    
>        ModifyResponse ::= [APPLICATION 7] LDAPResult 
>    
>   Upon receipt of a Modify Request, a server will perform the necessary 
>   modifications to the DIT. 

Note that a server is not required to perform the modifications
to the DIT (for instance, it could return an busy error).

>   The server will return to the client a single Modify Response 
>   indicating either the successful completion of the DIT modification, 
>   or the reason that the modification failed. Note that due to the 
>   requirement for atomicity in applying the list of modifications in 
>   the Modify Request, the client may expect that no modifications of 
>   the DIT have been performed if the Modify Response received indicates 
>   any sort of error, and that all requested modifications have been 
>   performed if the Modify Response indicates successful completion of 
>   the Modify Operation. If the association changes or the connection 
>   fails, whether the modification occurred or not is indeterminate. 
>    
>   The Modify Operation cannot be used to remove from an entry any of 
>   its distinguished values, those values which form the entry's 
>   relative distinguished name. An attempt to do so will result in the 
>   server returning the notAllowedOnRDN result code. The Modify DN 
>   Operation described in section 4.9 is used to rename an entry. 
>    
>   Note that due to the simplifications made in LDAP, there is not a 
>   direct mapping of the changes in an LDAP ModifyRequest onto the 
>   changes of a DAP ModifyEntry operation, and different implementations 
>   of LDAP-DAP gateways may use different means of representing the 
>   change. If successful, the final effect of the operations on the 
>   entry MUST be identical. 
>    
>    
>4.7. Add Operation 
>    
>   The Add Operation allows a client to request the addition of an entry 
>   into the directory. The Add Request is defined as follows: 
>    
>        AddRequest ::= [APPLICATION 8] SEQUENCE { 
>                entry           LDAPDN, 
>                attributes      AttributeList } 
>    
>        AttributeList ::= SEQUENCE OF SEQUENCE { 
>  
>                                      
>                type    AttributeDescription, 
>                vals    SET OF AttributeValue } 
>    
>   Parameters of the Add Request are: 
>    
>   - entry: the Distinguished Name of the entry to be added. Note that 
>     the server will not dereference any aliases in locating the entry 
>     to be added. 
>    
>   - attributes: the list of attributes that make up the content of the 
>     entry being added. Clients MUST include distinguished values 
>     (those forming the entry's own RDN) in this list, the objectClass 
>     attribute, and values of any mandatory attributes of the listed 
>     object classes. Clients MUST NOT supply NO-USER-MODIFICATION 
>     attributes such as the createTimestamp or creatorsName attributes, 
>     since the server maintains these automatically. 
>    
>   The entry named in the entry field of the AddRequest MUST NOT exist 
>   for the AddRequest to succeed. The immediate superior (parent) of the 
>   object and alias entries to be added MUST exist. For example, if the 
>   client attempted to add "CN=JS,DC=Example,DC=NET", the 
>   "DC=Example,DC=NET" entry did not exist, and the "DC=NET" entry did 
>   exist, then the server would return the noSuchObject result code with 
>   the matchedDN field containing "DC=NET". If the parent entry exists 
>   but is not in a naming context held by the server, the server SHOULD 
>   return a referral to the server holding the parent entry. 
>    
>   Server implementations SHOULD NOT restrict where entries can be 
>   located in the directory unless DIT structure rules are in place. 
>   Some servers MAY allow the administrator to restrict the classes of 
>   entries which can be added to the directory. 

drop the MAY.

>    
>   Upon receipt of an Add Request, a server will attempt to add the 
>   requested entry. The result of the add attempt will be returned to 
>   the client in the Add Response, defined as follows: 
>    
>        AddResponse ::= [APPLICATION 9] LDAPResult 
>    
>   A response of success indicates that the new entry is present in the 
>   directory. 
>    
>    
>4.8. Delete Operation 
>    
>   The Delete Operation allows a client to request the removal of an 
>   entry from the directory. The Delete Request is defined as follows: 
>    
>        DelRequest ::= [APPLICATION 10] LDAPDN 
>    
>   The Delete Request consists of the Distinguished Name of the entry to 
>   be deleted. Note that the server will not dereference aliases while 
>   resolving the name of the target entry to be removed, and that only 
>   leaf entries (those with no subordinate entries) can be deleted with 
>   this operation. 
>  
>                                      
>    
>   The result of the delete attempted by the server upon receipt of a 
>   Delete Request is returned in the Delete Response, defined as 
>   follows: 
>    
>        DelResponse ::= [APPLICATION 11] LDAPResult 
>    
>   Upon receipt of a Delete Request, a server will attempt to perform 
>   the entry removal requested. The result of the delete attempt will be 
>   returned to the client in the Delete Response. 
>    
>    
>4.9. Modify DN Operation 
>    
>   The Modify DN Operation allows a client to change the leftmost (least 
>   significant) component of the name of an entry in the directory, 
>   and/or to move a subtree of entries to a new location in the 
>   directory. The Modify DN Request is defined as follows: 
>    
>        ModifyDNRequest ::= [APPLICATION 12] SEQUENCE { 
>                entry           LDAPDN, 
>                newrdn          RelativeLDAPDN, 
>                deleteoldrdn    BOOLEAN, 
>                newSuperior     [0] LDAPDN OPTIONAL } 
>    
>   Parameters of the Modify DN Request are: 
>    
>   - entry: the Distinguished Name of the entry to be changed. This 
>     entry may or may not have subordinate entries. Note that the 
>     server will not dereference any aliases in locating the entry to 
>     be changed. 
>    
>   - newrdn: the RDN that will form the leftmost component of the new 
>     name of the entry. 
>    
>   - deleteoldrdn: a boolean parameter that controls whether the old 
>     RDN attribute values are to be retained as attributes of the 
>     entry, or deleted from the entry. 
>    
>   - newSuperior: if present, this is the Distinguished Name of an 
>     existing object entry which becomes the immediate superior 
>     (parent)of the existing entry. 
>    
>   The result of the name change attempted by the server upon receipt of 
>   a Modify DN Request is returned in the Modify DN Response, defined as 
>   follows: 
>    
>        ModifyDNResponse ::= [APPLICATION 13] LDAPResult 
>    
>   Upon receipt of a ModifyDNRequest, a server will attempt to perform 
>   the name change. The result of the name change attempt will be 
>   returned to the client in the Modify DN Response. 
>    
>
>  
>                                      
>   For example, if the entry named in the "entry" parameter was "cn=John 
>   Smith,c=US", the newrdn parameter was "cn=John Cougar Smith", and the 
>   newSuperior parameter was absent, then this operation would attempt 
>   to rename the entry to be "cn=John Cougar Smith,c=US". If there was 
>   already an entry with that name, the operation would fail with the 
>   entryAlreadyExists result code. 
>    
>   The object named in newSuperior MUST exist. For example, if the 
>   client attempted to add "CN=JS,DC=Example,DC=NET", the 
>   "DC=Example,DC=NET" entry did not exist, and the "DC=NET" entry did 
>   exist, then the server would return the noSuchObject result code with 
>   the matchedDN field containing "DC=NET". 
> 
>   If the deleteoldrdn parameter is TRUE, the values forming the old RDN 
>   are deleted from the entry. If the deleteoldrdn parameter is FALSE, 
>   the values forming the old RDN will be retained as non-distinguished 
>   attribute values of the entry. The server may not perform the 
>   operation and return an error in the result code if the setting of 
>   the deleteoldrdn parameter would cause a schema inconsistency in the 
>   entry. 
>    
>   Note that X.500 restricts the ModifyDN operation to only affect 
>   entries that are contained within a single server. If the LDAP server 
>   is mapped onto DAP, then this restriction will apply, and the 
>   affectsMultipleDSAs result code will be returned if this error 
>   occurred. In general clients MUST NOT expect to be able to perform 
>   arbitrary movements of entries and subtrees between servers. 

Add comma after "In general".

I suggest replacing "between servers" with "between naming contexts."
Or reword it "between servers or between naming contexts."  Clients      
cannot expect servers to move entries between naming contexts (even
where the server masters both).

>4.10. Compare Operation 
>    
>   The Compare Operation allows a client to compare an assertion 
>   provided with an entry in the directory. The Compare Request is 
>   defined as follows: 
>    
>        CompareRequest ::= [APPLICATION 14] SEQUENCE { 
>                entry           LDAPDN, 
>                ava             AttributeValueAssertion } 
>    
>   Parameters of the Compare Request are: 
>    
>   - entry: the name of the entry to be compared with. Note that the 
>     server SHOULD NOT dereference any aliases in locating the entry to 
>     be compared with. 
>    
>   - ava: the assertion with which an attribute in the entry is to be 
>     compared. 
>    
>   The result of the compare attempted by the server upon receipt of a 
>   Compare Request is returned in the Compare Response, defined as 
>   follows: 
>    
>        CompareResponse ::= [APPLICATION 15] LDAPResult 
>    
>  
>                                      
>   Upon receipt of a Compare Request, a server will attempt to perform 
>   the requested comparison using the EQUALITY matching rule for the 
>   attribute type. The result of the comparison will be returned to the 
>   client in the Compare Response. In the event that the attribute or 
>   subtype is not present in the entry, the resultCode field is set to 
>   noSuchAttribute. If the attribute is unknown, the resultCode is set 
>   to undefinedAttributeType. Note that errors and the result of 
>   comparison are all returned in the same construct. 
>    
>   Note that some directory systems may establish access controls which 
>   permit the values of certain attributes (such as userPassword) to be 
>   compared but not interrogated by other means. 
>    
>    
>4.11. Abandon Operation 
>    
>   The function of the Abandon Operation is to allow a client to request 
>   that the server abandon an outstanding operation. The Abandon Request 
>   is defined as follows: 
>    
>        AbandonRequest ::= [APPLICATION 16] MessageID 
>    
>   The MessageID MUST be that of an operation which was requested 
>   earlier in this LDAP association. The abandon request itself has its 
>   own message id. This is distinct from the id of the earlier operation 
>   being abandoned. 
>    
>   There is no response defined in the Abandon operation. Upon receipt 
>   of an AbandonRequest, the server MAY abandon the operation identified 
>   by the MessageID. Operation responses are not sent for successfully 
>   abandoned operations, thus a client SHOULD NOT use the Abandon 
>   operation when it needs an indication of whether the operation was 
>   abandoned. For example, if a client performs an update operation 
>   (Add, Modify, or ModifyDN), and it needs to know whether the 
>   directory has changed due to the operation, it should not use the 
>   Abandon operation to cancel the update operation. 

It might be better to reword the SHOULD NOT (which is implementation
imperative) as an applicability statement.  For example,
    The Abandon operation applicability is limited to use cases
    where the client does not require a clear indication of
    its outcome.
>    
>   Abandon and Unbind operations cannot be abandoned. The ability to 
>   abandon other (particularly update) operations is at the discretion 
>   of the server. 
>    
>   In the event that a server receives an Abandon Request on a Search 
>   Operation in the midst of transmitting responses to the search, that 
>   server MUST cease transmitting entry responses to the abandoned 
>   request immediately, and MUST NOT send the SearchResponseDone. Of 
>   course, the server MUST ensure that only properly encoded LDAPMessage 
>   PDUs are transmitted. 
>    
>   Clients MUST NOT send abandon requests for the same operation 
>   multiple times, and MUST also be prepared to receive results from 
>   operations it has abandoned (since these may have been in transit 
>   when the abandon was requested, or are not able to be abandoned). 
>    
>   Servers MUST discard abandon requests for message IDs they do not 
>   recognize, for operations which cannot be abandoned, and for 
>   operations which have already been abandoned. 

>    
>    
>4.12. Extended Operation 
>    
>   An extension mechanism has been added in this version of LDAP, in 
>   order to allow additional operations to be defined for services not 
>   available elsewhere in this protocol, for instance digitally signed 
>   operations and results. 
>    
>   The extended operation allows clients to make requests and receive 
>   responses with predefined syntaxes and semantics. These may be 
>   defined in RFCs or be private to particular implementations. Each 
>   request MUST have a unique OBJECT IDENTIFIER assigned to it. 
>    
>        ExtendedRequest ::= [APPLICATION 23] SEQUENCE { 
>                requestName      [0] LDAPOID, 
>                requestValue     [1] OCTET STRING OPTIONAL } 
>    
>   The requestName is a dotted-decimal representation of the OBJECT 
>   IDENTIFIER corresponding to the request. The requestValue is 
>   information in a form defined by that request, encapsulated inside an 
>   OCTET STRING. 
>    
>   The server will respond to this with an LDAPMessage containing the 
>   ExtendedResponse. 
>    
>        ExtendedResponse ::= [APPLICATION 24] SEQUENCE { 
>                COMPONENTS OF LDAPResult, 
>                responseName     [10] LDAPOID OPTIONAL, 
>                responseValue    [11] OCTET STRING OPTIONAL } 
>    
>   If the server does not recognize the request name, it MUST return 
>   only the response fields from LDAPResult, containing the 
>   protocolError result code. 

I note that responseName field would not be provided in this case.
Also, it may not be provided where a response was not assigned an
OID.  I generally recommend that extended operation responses not
have response names as even when the request in recongized it may
be difficult for servers to return the specified response name.
For example, say a server is very overload and desires to return
busy for all new operations.  Requiring the server to parse the
requestName, determine which responseName is appropriate, and
possiblly be required to generate a response value may be overly
burdensome.

(I suspect that requestName field was provided for use with unsolicited
notifications... it likely should have never been used by extended
operations.)

The fact is, clients already have to deal with cases where the
responseName is absent.  So, it seems reasponable that servers be
allowed to not provide the responseName in a number of other cases
as well.  In fact, the responseName should be extraneous in most
cases.  The only case were I could see in being needed where the
extended request could result in different format response values
being generated.  I would consider such extended operation
specifications significantly flawed.

Anyways, I suggest replacing the above with:
    An extension mechanism has been added to this version of LDAP
    in order to allow additional operations to be defined for        
    services not already available elsewhere in the protocol.   
    For example, to add operations to install transport layer
    security (see section 4.13).

    The extended operation allows clients to make requests and
    receive responses with predefined syntaxes and semantics.
    These may be defined in RFCs or be private to a particular
    implementations.

    Each operation consists of an extended response and an
    paired extended requested.

        ExtendedRequest ::= [APPLICATION 23] SEQUENCE {
                requestName      [0] LDAPOID,
                requestValue     [1] OCTET STRING OPTIONAL }
        ExtendedResponse ::= [APPLICATION 24] SEQUENCE {
                COMPONENTS OF LDAPResult,
                responseName     [10] LDAPOID OPTIONAL,
                responseValue    [11] OCTET STRING OPTIONAL }

    The requestname is a dotted-decimal representation of the
    OCTET IDENTIFIER corresponding to the request and to the
    operation.  The responseName is typically not required
    to be present as the syntax and semantics of the
    response (including the format of the responseValue) is
    implicitly known (responses are typically paired with
    requests).

    If the requestName is not recongized by the server, the
    server MUST NOT provide a responseName nor a responseValue
    and MUST return a resultCode of protocolError.  When the
    responseName field is present, it value is dotted-decimal
    representation of, depending on the operation's specification,
    either the OBJECT IDENTIFIER associated with the particular
    response or the OBJECT IDENTIFIER associated with operation.
    If the provided responseName is not recongized the client,
    the client is to treat the response as a protocol error.

Note also that I changed the example as controls seems like a more
approrpiate mechanism for "digitial signed operations".


>   The requestValue and responseValue fields contain any information 
>   associated with the operation. The format of these fields is defined 
>   by the specification of the extended operation. Implementations MUST 
>   be prepared to handle arbitrary contents of these fields, including 
>   zero bytes. Values that are defined in terms of ASN.1 and BER encoded 
>   according to Section 5.1, also follow the extensibility rules in 
>   Section 4. 
>    
>   Extended operations may be specified in other documents. The 
>   specification of an extended operation consists of: 
>    
>   - the OBJECT IDENTIFIER assigned to the ExtendedRequest.requestName 
>     (and possibly ExtendedResponse.responseName), 

The use of "ExtendedRequest." and "ExtendedResponse." is inconsistent
with the rest of the text and unnecessary.   Trim them.

>   - the format of the contents of the requestValue and responseValue 
>     (if any), 
>  
>   - the semantics of the operation, 
>    
>   Servers list the requestName of all ExtendedRequests they recognize 
>   in the supportedExtension attribute [Models] in the root DSE. 

This sentence is misplaced.  It should be moved to a paragraph
above the which starts "Extended operations may be specified in other
documents".

>   requestValues and responseValues that are defined in terms of ASN.1 
>   and BER encoded according to Section 5.1, also follow the 
>   extensibility rules in Section 4. 

>    
>    
>4.13. Start TLS Operation 

s/Start TLS/StartTLS/  (so hopefully the RFC-Editor won't require
it to be expanded).

>   The Start Transport Layer Security (StartTLS) operation provides the 
>   ability to establish Transport Layer Security [RFC2246] on an LDAP 
>   connection. 

Insert "(TLS)" just before the reference.

Add: The StartTLS operation is defined using the extended operation
mechanism descibed in section 4.12.

Use "StartTLS" not "Start TLS" below. 

>4.13.1. Start TLS Request 
> 
>   A client requests TLS establishment by transmitting a Start TLS 
>   request PDU to the server. The Start TLS request is defined in terms 
>   of an ExtendedRequest. The requestName is "1.3.6.1.4.1.1466.20037", 
>   and the requestValue field is absent.   

s/absent/always absent/
>    
>   The client MUST NOT send any PDUs on this connection following this 
>   request until it receives a Start TLS extended response. 
>    
>4.13.2. Start TLS Response 
> 
>   When a Start TLS request is made, servers supporting the operation 
>   MUST return a Start TLS response PDU to the requestor.  The Start TLS 
>   response responseName is also "1.3.6.1.4.1.1466.20037", and the 
>   response field is absent.  
>    
>   The server MUST set the resultCode field to either success or one of 
>   the other values outlined in section 4.13.2.2. 
>    
>4.13.2.1. "Success" Response 
> 
>   If the Start TLS Response contains a result code of success, this 
>   indicates that the server is willing and able to negotiate TLS. Refer 
>   to section 5.3 of [AuthMeth] for details. 
>    
>4.13.2.2. Response other than "success" 
> 
>   If the ExtendedResponse contains a result code other than success, 
>   this indicates that the server is unwilling or unable to negotiate 
>   TLS. The following result codes have these meanings for this 
>   operation: 
>    
>   - operationsError: operations sequencing incorrect; e.g. TLS already 
>     established) 
>
>  
>                                      
>    
>   - protocolError: (TLS not supported or incorrect PDU structure) 
>    
>   - unavailable: (e.g. some major problem with TLS, or server is 
>     shutting down) 
>    
>   The server MUST return operationsError if the client violates any of 
>   the Start TLS extended operation sequencing requirements described in 
>   section 5.3 of [AuthMeth]. 
>    
>   If the server does not support TLS (whether by design or by current 
>   configuration), it MUST set the resultCode field to protocolError. 
>   The client's current association is unaffected if the server does not 
>   support TLS. The client MAY proceed with any LDAP operation, or it 
>   MAY close the connection. 
>    
>   The server MUST return unavailable if it supports TLS but cannot 
>   establish a TLS connection for some reason, e.g. the certificate 
>   server not responding, it cannot contact its TLS implementation, or 
>   if the server is in process of shutting down. The client MAY retry 
>   the StartTLS operation, or it MAY proceed with any other LDAP 
>   operation, or it MAY close the LDAP connection. 
> 
>4.13.3. Closing a TLS Connection 
> 
>   Two forms of TLS connection closure--graceful and abrupt--are 
>   supported. 
>    
>4.13.3.1. Graceful Closure 
> 
>   Either the client or server MAY terminate the TLS connection and 
>   leave the LDAP connection intact by sending a TLS closure alert. 
>    
>   Before sending a TLS closure alert, the client MUST either wait for 
>   any outstanding LDAP operations to complete, or explicitly abandon 
>   them.  
>    
>   After the initiator of a close has sent a TLS closure alert, it MUST 
>   discard any TLS messages until it has received a TLS closure alert 
>   from the other party.  It will cease to send TLS Record Protocol 
>   PDUs, and following the receipt of the alert, MAY send and receive 
>   LDAP PDUs. 
>    
>   The other party, if it receives a TLS closure alert, MUST immediately 
>   transmit a TLS closure alert.  It will subsequently cease to send TLS 
>   Record Protocol PDUs, and MAY send and receive LDAP PDUs. 
>    
>   After the TLS connection has been closed, the server MUST NOT send 
>   responses to any request message received before the TLS closure. 
>    
>4.13.3.2. Abrupt Closure 
> 
>
>  
>                                      
>   Either the client or server MAY abruptly close the TLS connection by 
>   dropping the underlying transfer protocol connection. In this 
>   circumstance, a server MAY send the client a Notice of Disconnection 
>   before dropping the underlying LDAP connection. 
>    
>    
>5. Protocol Element Encodings and Transfer 
>    
>   One underlying service is defined here. Clients and servers SHOULD 
>   implement the mapping of LDAP over [TCP] described in 5.2.1. 
>    
This statement could be read as to mean:
a) Implementation of LDAP over TCP is RECOMMENDED.
b) When implementing LDAP over TCP, the mapping described in 5.2.1
is RECOMMENDED.
 
I think that if implementations implement LDAP over TCP then they      
MUST do so in accordance with 5.2.1.  And I suggest treating whether
implementations are to implment LDAP over TCP as an applicability
issue.  That is, I suggest the paragraph be replaced with:         
 
    One underlying service, LDAP over TCP, is defined here.  This   
    service is generally applicable to applications providing
    or consuming X.500-based directory services on the Internet.

    Implementations of LDAP over TCP MUST implement the mapping          
    as described in Section 5.2.1
>    
>5.1. Protocol Encoding 
>    
>   The protocol elements of LDAP are encoded for exchange using the 
>   Basic Encoding Rules (BER) [X.690] of ASN.1 [X.680]. However, due to 
>   the high overhead involved in using certain elements of the BER, the 
>   following additional restrictions are placed on BER-encodings of LDAP 
>   protocol elements: 

It is not clear that all of these restrictions are mandatory to        
implement.  I sugggest a single imperative be used to make this
whole section mandatory.  E.g.,
    Elements of LDAP SHALL be encoded for exchange using the            
    Basic Encoding Rules (BER) [X.690] of ASN.1 [X.680] with the      
    following restrictions:

with the rationale stated after the restrictions.  This makes having
per restriction MUSTs are redundant.

>    
>   (1) Only the definite form of length encoding will be used. 

s/will be/is/
>    
>   (2) OCTET STRING values will be encoded in the primitive form only. 

s/will be/are/
>    
>   (3) If the value of a BOOLEAN type is true, the encoding MUST have 
>       its contents octets set to hex "FF". 

s/MUST have/has/
>    
>   (4) If a value of a type is its default value, it MUST be absent. 
>       Only some BOOLEAN and INTEGER types have default values in this 
>       protocol definition. 

s/MUST be/is/
    
>   These restrictions do not apply to ASN.1 types encapsulated inside of 
>   OCTET STRING values, such as attribute values, unless otherwise 
>   noted. 

s/noted/stated/
>    
>    
>5.2. Transfer Protocols 
>    
>   This protocol is designed to run over connection-oriented, reliable 
>   transports, with all 8 bits in an octet being significant in the data 
>   stream. 
>    
>    
>5.2.1. Transmission Control Protocol (TCP) 
>    
>   The encoded LDAPMessage PDUs are mapped directly onto the [TCP] 
>   bytestream using the BER-based encoding described in section 5.1. It 
>   is recommended that server implementations running over the TCP 
>   provide a protocol listener on the assigned port, 389. Servers may 
>   instead provide a listener on a different port number. Clients MUST 
>   support contacting servers on any valid TCP port. 
>    
>    
>6. Implementation Guidelines 
>  
>6.1. Server Implementations 
>    
>   The server MUST be capable of recognizing all the mandatory attribute 
>   types specified in [Models], and implement the syntaxes used by those 
>   attributes specified in [Syntaxes]. Servers MAY also recognize 
>   additional attribute type names. 
    
I think this statement is not consistent with [Models].  Also, I
don't servers should be required to implement all the syntaxes specified
in [Syntaxes].  For example, a server which doesn't implement DIT
Content Rules need not implement the DIT Content Rule syntax.        

Anyways, I think [Models, Section 7.1] adequately covers this.
    
>6.2. Client Implementations 
>    
>   Clients that follow referrals or search continuation references MUST 
>   ensure that they do not loop between servers. They MUST NOT 
>   repeatedly contact the same server for the same request with the same 
>   target entry name, scope and filter. Some clients use a counter that 
>   is incremented each time referral handling occurs for an operation, 
>   and these kinds of clients MUST be able to handle at least ten nested 
>   referrals between the root and a leaf entry. 

s/referral/referral or references/ (in two places)                 
              
Since referrals can be returned for reasons other than naming context
layers, I suggest this be reworded:
    ... clients MUST be able to handle 9 layers of referrals or
    references.


The following paragraph should likely be moved to [Models].
>   In the absence of prior agreements with servers, clients SHOULD NOT 
>   assume that servers support any particular schemas beyond those 

s/schemas/schema elements/

>   referenced in section 6.1. Different schemas can have different 
>   attribute types with the same names. The client can retrieve the 
>   subschema entries referenced by the subschemaSubentry attribute in 
>   the entries held by the server. 

s/schemas/subschemas/

>    
>7. Security Considerations 
>    
>   This version of the protocol provides facilities for simple 
>   authentication using a cleartext password, as well as any SASL 
>   mechanism [RFC2222]. SASL allows for integrity and privacy services 
>   to be negotiated. 
>    
>   It is also permitted that the server can return its credentials to 
>   the client, if it chooses to do so. 
>    
>   Use of cleartext password is strongly discouraged where the 
>   underlying transport service cannot guarantee confidentiality and may 
>   result in disclosure of the password to unauthorized parties. 
>    
>   Requirements of authentication methods, SASL mechanisms, and TLS are 
>   described in [AUTHMETH]. 
>    
>   When used with SASL, it should be noted that the name field of the 
>   BindRequest is not protected against modification. Thus if the 
>   distinguished name of the client (an LDAPDN) is agreed through the 
>   negotiation of the credentials, it takes precedence over any value in 
>   the unprotected name field. 

This needs to be expanded to other unprotected fields.

    It should be noted that SASL authentication exchanges do
    provide data confidential nor integrity protection for the
    version or name fields of the bind request nor the resultCode,
    errorMessage, or referral fields of the bind response nor
    of any information contained in controls attached to bind           
    request or responses.  Thus information contained in these 
    fields SHOULD NOT be relied on unless otherwise protected            
    (such as by establishing protections at the transport layer).       

We should discuss the precedence bit as part of our [authmeth] review. 

>    
>   Server implementors should plan for the possibility of an identity or 
>   associated with an LDAP connection being deleted, renamed, or 
>   modified, and take appropriate actions to prevent insecure side 
>   effects. The way in which this is dealt with is implementation 
>   specific. Likewise, server implementors should plan for the 
>   possibility of an associated identities credentials becoming invalid. 

I suggest the middle sentence be moved to the end and reworded:
	The way in which these issues are addressed are application
	and/or implementation specification.

>   Implementations which cache attributes and entries obtained via LDAP 
>   MUST ensure that access controls are maintained if that information 
>   is to be provided to multiple clients, since servers may have access 
>   control policies which prevent the return of entries or attributes in 
>   search results except to particular authenticated clients. For 
>   example, caches could serve result information only to the client 
>   whose request caused it to be in the cache. 
>    
>   Protocol servers may return referrals which redirect protocol clients 
>   to peer servers. It is possible for a rogue application to inject 
>   such referrals into the data stream in an attempt to redirect a 
>   client to a rogue server. Protocol clients are advised to be aware of 
>   this, and possibly reject referrals when confidentiality measures are 
>   in place. Protocol clients are advised to ignore referrals from the 
>   Start TLS operation. 


I suggest s/ignore/reject/ here.  I would hope clients would
not simply ignore the referral, but raise an alert to the user.
    
>   Protocol peers MUST be prepared to handle invalid and arbitrary 
>   length protocol encodings. A number of LDAP security advisories are 
>   available through [CERT]. 
>    
>    
>8. Acknowledgements 
>    
>   This document is an update to RFC 2251, by Mark Wahl, Tim Howes, and 
>   Steve Kille. Their work along with the input of individuals of the 
>   IETF LDAPEXT, LDUP, LDAPBIS, and other Working Groups is gratefully 
>   acknowledged. 
>    
>    
>9. Normative References 
> 
>   [X.500]   ITU-T Rec. X.500, "The Directory: Overview of Concepts, 
>             Models and Service", 1993.  
>    
>   [Roadmap] K. Zeilenga (editor), "LDAP: Technical Specification Road 
>             Map", draft-ietf-ldapbis-roadmap-xx.txt (a work in 
>             progress). 

s/K. Zeilenga/Zeilenga, K./  (and likewise below)

>   [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 
>             Requirement Levels", RFC 2119, March 1997. 
>     
>   [X.680]   ITU-T Recommendation X.680 (07/2002) | ISO/IEC 8824-1:2002 
>             "Information Technology - Abstract Syntax Notation One 
>             (ASN.1): Specification of basic notation" 
>    
>   [X.690]   ITU-T Rec. X.690 (07/2002) | ISO/IEC 8825-1:2002, 
>             "Information technology - ASN.1 encoding rules: 
>             Specification of Basic Encoding Rules (BER), Canonical 
>             Encoding Rules (CER) and Distinguished Encoding Rules 
>             (DER)", 2002. 
> 
>   [LDAPIANA] K. Zeilenga, "IANA Considerations for LDAP", draft-ietf-
>             ldapbis-xx.txt (a work in progress). 
>    
>   [ISO10646] Universal Multiple-Octet Coded Character Set (UCS) - 
>             Architecture and Basic Multilingual Plane, ISO/IEC 10646-1 
>             : 1993. 
>    
>   [RFC2279] Yergeau, F., "UTF-8, a transformation format of Unicode 
>             and ISO 10646", RFC 2279, January 1998. 
>    
>   [Models]  K. Zeilenga, "LDAP: The Models", draft-ietf-ldapbis-
>             models-xx.txt (a work in progress). 
>    
>   [LDAPDN]  K. Zeilenga (editor), "LDAP: String Representation of 
>             Distinguished Names", draft-ietf-ldapbis-dn-xx.txt, (a 
>             work in progress). 
>    
>   [Syntaxes] K. Dally (editor), "LDAP: Syntaxes", draft-ietf-ldapbis-
>             syntaxes-xx.txt, (a work in progress). 
>    
>   [X.501]   ITU-T Rec. X.501, "The Directory: Models", 1993. 
>    
>   [X.511]   ITU-T Rec. X.511, "The Directory: Abstract Service 
>             Definition", 1993. 
>    
>   [RFC2396] Berners-Lee, T., Fielding, R., and L. Masinter Uniform 
>             Resource Identifiers (URI): Generic Syntax", RFC 2396, 
>             August 1998. 
>    
>   [AuthMeth] R. Harrison (editor), "LDAP: Authentication Methods", 
>             draft-ietf-ldapbis-authmeth-xx.txt, (a work in progress). 
>    
>   [RFC2222] Meyers, J., "Simple Authentication and Security Layer", 
>             RFC 2222, October 1997. 
>    
>   [SASLPrep] Zeilenga, K., "Stringprep profile for user names and 
>             passwords", draft-ietf-sasl-saslprep-xx.txt, (a work in 
>             progress). 
>    
>    
>   [Unicode] The Unicode Consortium, "The Unicode Standard, Version 
>             3.2.0" is defined by "The Unicode Standard, Version 3.0" 
>             (Reading, MA, Addison-Wesley, 2000. ISBN 0-201-61633-5), 
>             as amended by the "Unicode Standard Annex #27: Unicode 
>             3.1" (http://www.unicode.org/reports/tr27/) and by the 
>             "Unicode Standard Annex #28: Unicode 3.2" 
>             (http://www.unicode.org/reports/tr28/). 
>    
>   [TCP]     Postel, J., "Transmission Control Protocol", STD7, 
>             September 1981 

Provide RFC number as well.
>    
>   [IP]      Postel, J., "Internet Protocol", STD5, September 1981 
>    
>  
>10. Informative References 
>    
>   [CERT]    the CERT(R) Center, (http://www.cert.org) 

Only one informative reference?

>11. IANA Considerations 
>   It is requested that the Internet Assigned Numbers Authority (IANA) 
>   update the occurrence of "RFC XXXX" Appendix B with this RFC number 
>   at publication. 
> 
>12. Editor's Address 
>    
>   Jim Sermersheim 
>   Novell, Inc. 
>   1800 South Novell Place 
>   Provo, Utah 84606, USA 
>   jimse@novell.com 
>   +1 801 861-3088 
>
>
>
>  
>                                      
>Appendix A - LDAP Result Codes 
> 
>   This normative appendix details additional considerations regarding 
>   LDAP result codes and provides a brief, general description of each 
>   LDAP result code enumerated in Section 4.1.10. 
>    
>   Additional result codes MAY be defined for use with extensions. 
>   Client implementations SHALL treat any result code which they do not 
>   recognize as an unknown error condition. 
>    
>A.1 Non-Error Result Codes 
>   These result codes (called "non-error" result codes) do not indicate 
>   an error condition: 
>        success (0), 
>        compareTrue (6), 
>        compareFalse (7), 
>        referral (10), and 
>        saslBindInProgress (14). 
>    
>   The success, compareTrue, and compare result codes indicate 
>   successful completion (and, hence, are called to as "successful" 
>   result codes). 
>    
>   The referral and saslBindInProgress result codes indicate the client 
>   is required to take additional action to complete the operation 
>    
>    
>A.2 Result Codes 
>   Existing LDAP result codes are described as follows: 

Insert empty line between section header and text.

>        success (0) 
>         
>           Indicates successful completion of an operation. 
>    
>           This result code is normally not returned by the compare 
>           operation, see compareFalse and compareTrue. It is possible 
>           that a future extension mechanism would allow this to be 
>           returned by a compare operation. 
>    
Suggest this paragraph be replaced with:
            Note: this code is not used with the compare operation.
            See compareTrue (5) and compareFalse (6).        

(no need to say what is possible in future extensions)
>    
>        operationsError (1) 
>    
>           Indicates that the operation is not properly sequenced with 
>           relation to other operations (of same or different type). 
> 
>           For example, this code is returned if the client attempts to 
>           Start TLS [RFC2246] while there are other operations 
>           outstanding or if TLS was already established. 
>            
> 
> 
>        protocolError (2) 
> 
>           Indicates the server received data which has incorrect 
>           structure. 
>            
>           For bind operation only, the code may be resulted to indicate 
>           the server does not support the requested protocol version. 
>

replace with:
            For bind operation only, this code is also used to indicate
            that the server does not support the requested protocol
            version.
> 
>        timeLimitExceeded (3) 
>         
>           Indicates that the time limit specified by the client was 
>           exceeded before the operation could be completed. 
>         
>         
>        sizeLimitExceeded (4) 
>         
>           Indicates that the size limit specified by the client was 
>           exceeded before the operation could be completed. 
>         
>         
>        compareFalse (5) 
>         
>           Indicates that the operation successfully completes and the 
>           assertion has evaluated to FALSE. 
>         
>           This result code is normally only returned by the compare 
>           operation. 
>         

Suggest this sentence be replaced (here and below) with:
        This result code is only used by compare operation.

>        compareTrue (6) 
>         
>           Indicates that the operation successfully completes and the 
>           assertion has evaluated to TRUE. 
>         
>           This result code is normally only returned by the compare 
>           operation. 
>         
>         
>        authMethodNotSupported (7) 
>         
>           Indicates that the authentication method or mechanism is not 
>           supported. 
>         
>         
>        strongAuthRequired (8) 
>         
>           Indicates that the server has detected that an established 
>           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. 
>         
>        referral (10) 
>                                      
>           Indicates that a referral needs to be chased to complete the 
>           operation (see section 4.1.11). 
>         
>         
>        adminLimitExceeded (11) 
>         
>           Indicates that an administrative limit has been exceeded. 
>         
>         
>        unavailableCriticalExtension (12) 
>         
>           Indicates that server cannot perform a critical extension 
>           (see section 4.1.12). 
>         
s/cannot/is unwilling or unable/
>         
>        confidentialityRequired (13) 
>         
>           Indicates that data confidentiality protections are required. 
>         
>         
>        saslBindInProgress (14) 
>         
>           Indicates the server requires the client to send a new bind 
>           request, with the same SASL mechanism, to continue the 
>           authentication process (see section 4.2). 
>         
>         
>        noSuchAttribute (16) 
>         
>           Indicates that the named entry does not contain the specified 
>           attribute or attribute value. 
>         
>         
>        undefinedAttributeType (17) 
>         
>           Indicates that a request field contains an undefined 
>           attribute type. 


s/undefined attribute type/unrecongized attribute description/

>         
>         
>        inappropriateMatching (18) 
>         
>           Indicates that a request cannot be completed due to an 
>           inappropriate matching. 
>         
delete "an".
>         
>        constraintViolation (19) 
>         
>           Indicates that the client supplied an attribute value which 
>           does not conform to constraints placed upon it by the data 
>           model. 
>         
>           For example, this code is returned when the multiple values 
>           are supplied to an attribute which has a SINGLE-VALUE 
>           constraint. 
>  
>         
>        attributeOrValueExists (20) 
>         
>           Indicates that the client supplied an attribute or value to 
>           be added to an entry already exists. 
>         
>         
>        invalidAttributeSyntax (21) 
>         
>           Indicates that a purported attribute value does not conform 
>           to the syntax of the attribute. 
>         
>         
>        noSuchObject (32) 
>         
>           Indicates that the object does not exist in the DIT. 
>         
>         
>        aliasProblem (33) 
>         
>           Indicates that an alias problem has occurred. Typically an 
>           alias has been dereferenced which names no object. 
>         
Suggest s/Typically/For example, the code may used to indicate/
>         
>        invalidDNSyntax (34) 
>         
>           Indicates that a LDAPDN or RelativeLDAPDN field (e.g. search 
>           base, target entry, ModifyDN newrdn, etc.) of a request does 
>           not conform to the required syntax or contains attribute 
>           values which do not conform to the syntax of the attribute's 
>           type. 
>         
>         
>        aliasDereferencingProblem (36) 
>         
>           Indicates that a problem occurred while dereferencing an 
>           alias. Typically an alias was encountered in a situation 
>           where it was not allowed or where access was denied. 
>         
>         
>        inappropriateAuthentication (48) 
>         
>           Indicates the server requires the client which had attempted 
>           to bind anonymously or without supplying credentials to 
>           provide some form of credentials, 
>         
>         
>        invalidCredentials (49) 
>         
>           Indicates the supplied password or SASL credentials are 
>           invalid. 
>         
This wording is too narrow.  It doesn't include the bind name          
which is part of the creditials when simple bind is used, nor    
does it include non-SASL credentials (the LDAP can be extended
to support other methods).

Suggest:    
        Indicates that the provided credentials (e.g. the user's
        name and password) are invalid.

>         
>  
>                                      
>        insufficientAccessRights (50) 
>         
>           Indicates that the client does not have sufficient access 
>           rights to perform the operation. 
>         
>         
>        busy (51) 
>         
>           Indicates that the server is busy. 
>         

Suggest:
            Indicates that the server is too busy to process the
            operation.
>         
>        unavailable (52) 
>         
>           Indicates that the server is shutting down or a subsystem 
>           necessary to complete the operation is offline. 
>         
>         
>        unwillingToPerform (53) 
>         
>           Indicates that the server is unwilling to perform the 
>           operation. 
>         
>         
>        loopDetect (54) 
>         
>           Indicates that the server has detected an internal loop. 
>         
>         
>        namingViolation (64) 
>         
>           Indicates that the entry name violates naming restrictions. 

s/entry name/entry's name/
>         
>        objectClassViolation (65) 
>         
>           Indicates that the entry violates object class restrictions. 
>         
>         
>        notAllowedOnNonLeaf (66) 
>         
>           Indicates that operation is inappropriately acting upon a 
>           non-leaf entry. 
>         
>         
>        notAllowedOnRDN (67) 
>         
>           Indicates that the operation is inappropriately attempting to 
>           remove a value which forms the entry's relative distinguished 
>           name. 
>         
>         
>        entryAlreadyExists (68) 
>         
>           Indicates that the request cannot be added fulfilled as the 
>           entry already exists. 
>  
>         
>        objectClassModsProhibited (69) 
>         
>           Indicates that the attempt to modify the object class(es) of 
>           an entry objectClass attribute is prohibited. 
>         
>           For example, this code is returned when a when a client 
>           attempts to modify the structural object class of an entry. 
>         
s/when a when a/when a/
>         
>        affectsMultipleDSAs (71) 
>         
>           Indicates that the operation cannot be completed as it 
>           affects multiple servers (DSAs). 
>         
>         
>        other (80) 
>         
>           Indicates the server has encountered an internal error. 
>


From owner-ietf-ldapbis@OpenLDAP.org  Tue Oct  7 21:56: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 VAA01236
	for <ldapbis-archive@lists.ietf.org>; Tue, 7 Oct 2003 21:56:04 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h981ivjk089293;
	Wed, 8 Oct 2003 01:54: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 h981iUaO089271;
	Wed, 8 Oct 2003 01:44:30 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 8 Oct 2003 01:44: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 h981iPj2089241
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 8 Oct 2003 01:44:25 GMT
	(envelope-from steven.legg@adacel.com.au)
Received: from nexus.adacel.com (Not Verified[10.32.240.1]) by adacel.com with NetIQ MailMarshal (v5.5.3.16)
	id <B00017400f>; Wed, 08 Oct 2003 11:38:01 +1000
Received: (qmail 1779 invoked from network); 8 Oct 2003 01:32:09 -0000
Received: from unknown (HELO adacel.com.au) (10.32.24.165)
  by nexus.adacel.com with SMTP; 8 Oct 2003 01:32:09 -0000
Message-ID: <3F836BE3.8030903@adacel.com.au>
Date: Wed, 08 Oct 2003 12:44:03 +1100
From: Steven Legg <steven.legg@adacel.com.au>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3.1) Gecko/20030425
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
CC: ietf-ldapbis@OpenLDAP.org
Subject: Re: WG Last Call: draft-ietf-ldapbis-protocol-17.txt  [corrected]
References: <5.2.0.9.0.20030919105440.03bcf5d8@127.0.0.1> <002e01c38c66$f6237ea0$a518200a@osmium.mtwav.adacel.com.au> <6.0.0.22.0.20031008041847.03a77f30@127.0.0.1>
In-Reply-To: <6.0.0.22.0.20031008041847.03a77f30@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:
> In the AttributeList case, I rather the ASN.1 be changed
> to:
>         AttributeList ::= SEQUENCE OF Attribute
> 
> where Attribute is as currently defined.

Which in the context of the current discussion would be amended to:

    AttributeList ::= SEQUENCE OF attribute Attribute

Regards,
Steven

> 
> Kurt
> 
> 
> At 05:07 PM 10/6/2003, Steven Legg wrote:
> 
> 
>>Folks,
>>
>>I recently published an Internet draft on an XML rendition of the LDAP
>>protocol (called XLDAP) that is realized by applying a set of XML
>>encoding rules to the ASN.1 types in the ASN.1 specification for LDAP
>>(specifically the ASN.1 in the protocols draft being last-called).
>>
>>The XML produced is neat and tidy except with respect to the instances
>>of the member type of a SEQUENCE OF or SET OF ASN.1 type.
>>
>>Consider this example drawn from the protocols draft:
>>
>>       AttributeList ::= SEQUENCE OF SEQUENCE { 
>>               type    AttributeDescription, 
>>               vals    SET OF AttributeValue } 
>>
>>Using my Directory XML Encoding Rules (DXER) to encode an attribute list,
>>each attribute in the list is encoded as an element with the safe, but
>>bland name of <item>. Using the ITU-T's XML Encoding Rules (XER), each
>>attribute in the list is encoded as an element with the unappealing name
>>of <SEQUENCE>.
>>   
>>However the situation can be improved since the version of ASN.1 that
>>the protocols draft is referencing allows an ASN.1 identifier after a
>>SEQUENCE OF or SET OF and before the definition of the member type.
>>
>>For example:
>>
>>       AttributeList ::= SEQUENCE OF attribute SEQUENCE { 
>>               type    AttributeDescription, 
>>               vals    SET OF value AttributeValue } 
>>
>>With this change both DXER and XER would encode each attribute in the list
>>as an element with the more meaningful name of <attribute>. This change
>>makes no difference to the BER encoding, so it is neutral to LDAP and does
>>not represent a new feature.
>>
>>I would like to see each of the SEQUENCE OF and SET OF definitions in the
>>LDAP ASN.1 module given a meaningful mnemonic identifier for the member type
>>so as to facilitate better XML representations of LDAP operations (whether
>>for XLDAP or any other purpose). If the working group allows it I'll work
>>with Jim to make the additions.
>>
>>Regards,
>>Steven
> 
> 
> 
> 



From owner-ietf-ldapbis@OpenLDAP.org  Tue Oct  7 22:06: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 WAA01531
	for <ldapbis-archive@lists.ietf.org>; Tue, 7 Oct 2003 22:06:26 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h9822vj6090951;
	Wed, 8 Oct 2003 02:04: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 h981xh7p090744;
	Wed, 8 Oct 2003 01:59:43 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 8 Oct 2003 01: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 h981xej2090733
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 8 Oct 2003 01:59:41 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from gypsy.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.9/8.12.9) with ESMTP id h981xblg073276;
	Wed, 8 Oct 2003 01:59:37 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.0.22.0.20031008062239.03ac8e60@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
Date: Wed, 08 Oct 2003 06:59:20 -0700
To: <steven.legg@adacel.com.au>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: RE: Steven's protocol comments
Cc: <ietf-ldapbis@OpenLDAP.org>
In-Reply-To: <005d01c38bcd$ba767db0$a518200a@osmium.mtwav.adacel.com.au>
References: <5.2.0.9.0.20030919105440.03bcf5d8@127.0.0.1>
 <005d01c38bcd$ba767db0$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>

At 10:50 PM 10/5/2003, Steven Legg wrote:
>Here are some comments on draft-ietf-ldapbis-protocol-17.txt .
>They are mostly of an editorial nature.

I'm mostly fine with Steven's suggestions...  but have a few
comments here and there to add. - Kurt


>>    If the client wishes to progress the operation, it MUST follow the 
>>    referral by contacting one of the servers.
>
>"If" and "MUST" make this an effective "MAY", e.g.
>
>     "The Client MAY progress the operation by following the referral and
>     contacting one of the servers."

I think this MAY could be downcased.

>> 4.2.2. Bind Response 
>
>>    The serverSaslCreds are used as part of a SASL-defined bind mechanism 
>>    to allow the client to authenticate the server to which it is 
>>    communicating, or to perform "challenge-response" authentication. If 
>>    the client bound with the simple choice, or the SASL mechanism does 
>>    not require the server to return information to the client, then this 
>>    field is not to be included in the BindResponse. 
>           ^^^^^^^^^ SHALL NOT ?

Yes.

>>    - sizeLimit: A size limit that restricts the maximum number of 
>>      entries to be returned as a result of the search. A value of 0 in 
>>      this field indicates that no client-requested size limit 
>>      restrictions are in effect for the search. Servers may enforce a 
>>      maximum number of entries to return. 
>>     
>>    - timeLimit: A time limit that restricts the maximum time (in 
>>      seconds) allowed for a search. A value of 0 in this field 
>>      indicates that no client-requested time limit restrictions are in 
>>      effect for the search. 
>
>Servers may limit the number of entries returned. Should they not also
>be allowed to limit the amount of time spent ?

Yes.  But it could be argued that these are really administrative
limits which, when exceeded, should be indicated by the
adminLimitExceeded error.  However, for historical reasons,
I have no problem continuing to allow use of these codes to
indicate such.


>>      Client implementors should note that even if all user attributes 
>>      are requested, some attributes of the entry may not be included in 
>>      search results due to access controls or other restrictions. 
>>      Furthermore, servers will not return operational attributes, such 
>>      as objectClasses or attributeTypes, unless they are listed by 
>>      name, since there may be extremely large number of values for 
>>      certain operational attributes. (A list of operational attributes 
>>      for use in LDAP is given in [Syntaxes].) 
>                                   ^^^^^^^^^^
>The operational attributes are now listed in other documents.

[Models].  Suggest the note be reworded:
  ([Models] details commonly supported operational attribute types.)

>> 4.5.2. Search Result 
>
>>         PartialAttributeList ::= SEQUENCE OF SEQUENCE { 
>>                 type    AttributeDescription, 
>>                 vals    SET OF AttributeValue } 
>
>I thought there was an agreement to consolidate all the SEQUENCEs
>of type and vals into one Attribute ASN.1 type, and for there to be only
>one "SEQUENCE OF Attribute" ASN.1 type. What happened to that ?

In my comment, I suggested an approach which doesn't consolidate
attributes and partial attribute types.  However, I don't have
any particular problem with taking a consolidation approach.

>>    If the server's schema defines a textual name for an attribute type, 
>>    it SHOULD use a textual name for attributes of that attribute type by 
>>    specifying one of the textual names as the value of the attribute 
>>    type. Otherwise, the server uses the object identifier for the 
>>    attribute type by specifying the object identifier, in ldapOID form, 
>>    as the value of attribute type. If the server determines that 
>>    returning a textual name will cause interoperability problems, it 
>>    SHOULD return the ldapOID form of the attribute type. 
>
>This paragraph is a bit shaky. Consider this instead:
>
>  "If the server's schema defines short names [Models] for an attribute type
>   then the server SHOULD use one of those names in attribute descriptions
>   for that attribute type (in preference to using the dotted decimal format
>   of the attribute type's object identifier). The server should not use the
>   short name if that name is known by the server to be ambiguous, or
>   otherwise likely to cause interoperability problems."

I think the "should not" should be a "SHOULD NOT".

>> 4.12. Extended Operation 
>
>>    Servers list the requestName of all ExtendedRequests they recognize 
>            ^ SHALL ?

No.  First, "all" is too strong.  Servers should be allowed
to restrict the set of values by access or other
administrative controls and/or by current available and/or
other factors.

And since no great harm is caused by not providing a value
(especially given they are rarely used by clients), a
SHALL is way too strong.

I suggest deleting "all" and s/recognize/support/.

(It would be inappropriate to publish a value which you
recognized but didn't support).


>> 4.13.2.2. Response other than "success" 
>
>>    If the server does not support TLS (whether by design or by current 
>>    configuration), it MUST set the resultCode field to protocolError. 
>>    The client's current association is unaffected if the server does not 
>>    support TLS. The client MAY proceed with any LDAP operation, or it 
>                             ^^^                                  ^^
>>    MAY close the connection. 
>     ^^^
>"MAY" and "or" both suggest optionality. I am left wondering what a client
>is supposed to do if it elects to do neither of the MAY actions.
>Perhaps the "MAY"s should be downcased.

Downcase them.

>>    The server MUST return unavailable if it supports TLS but cannot 
>>    establish a TLS connection for some reason, e.g. the certificate 
>>    server not responding, it cannot contact its TLS implementation, or 
>>    if the server is in process of shutting down. The client MAY retry 
>                                                              ^^^
>>    the StartTLS operation, or it MAY proceed with any other LDAP 
>                             ^^^^^^^^^
>>    operation, or it MAY close the LDAP connection. 
>                ^^^^^^^^^
>Same again.

same: down case.


>>    The other party, if it receives a TLS closure alert, MUST immediately 
>>    transmit a TLS closure alert.  It will subsequently cease to send TLS 
>                                       ^^^^ MUST ?

Please consider the replace text I offer in my comments. 



From owner-ietf-ldapbis@OpenLDAP.org  Tue Oct  7 22:10: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 WAA01592
	for <ldapbis-archive@lists.ietf.org>; Tue, 7 Oct 2003 22:10:01 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h9828vj6091227;
	Wed, 8 Oct 2003 02:09: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 h9826nHh091156;
	Wed, 8 Oct 2003 02:06:49 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 8 Oct 2003 02:06:49 +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 h9826lj2091146
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 8 Oct 2003 02:06:47 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from gypsy.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.9/8.12.9) with ESMTP id h9826llg073393
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 8 Oct 2003 02:06:47 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.0.22.0.20031008070251.03b06bb8@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
Date: Wed, 08 Oct 2003 07:06:30 -0700
To: ietf-ldapbis@OpenLDAP.org
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: unprotected fields security consideration (Was: REVISED
  protocol review notes [LONG])
In-Reply-To: <20031002114843.GB590.bogus@openldap.org>
References: <20031002114843.GB590.bogus@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>

The first sentence of my suggestion should read "do not provide",
not "do provide".  --Kurt

At 02:48 PM 10/7/2003, Kurt Zeilenga wrote:
>>   When used with SASL, it should be noted that the name field of the 
>>   BindRequest is not protected against modification. Thus if the 
>>   distinguished name of the client (an LDAPDN) is agreed through the 
>>   negotiation of the credentials, it takes precedence over any value in 
>>   the unprotected name field. 
>
>This needs to be expanded to other unprotected fields.
>
>    It should be noted that SASL authentication exchanges do
>    provide data confidential nor integrity protection for the
>    version or name fields of the bind request nor the resultCode,
>    errorMessage, or referral fields of the bind response nor
>    of any information contained in controls attached to bind           
>    request or responses.  Thus information contained in these 
>    fields SHOULD NOT be relied on unless otherwise protected            
>    (such as by establishing protections at the transport layer).       
>
>We should discuss the precedence bit as part of our [authmeth] review. 



From owner-ietf-ldapbis@OpenLDAP.org  Wed Oct  8 10:18: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 KAA16848
	for <ldapbis-archive@lists.ietf.org>; Wed, 8 Oct 2003 10:18:28 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h98E32je022129;
	Wed, 8 Oct 2003 14:15: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 h98E1Uwd021750;
	Wed, 8 Oct 2003 14:01:30 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 8 Oct 2003 14:01:30 +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 h98E1Qj2021688;
	Wed, 8 Oct 2003 14:01:27 GMT
	(envelope-from RHARRISON@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Wed, 08 Oct 2003 08:01:06 -0600
Message-Id: <sf83c442.029@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.1 
Date: Wed, 08 Oct 2003 07:28:10 -0600
From: "Roger Harrison" <RHARRISON@novell.com>
To: "Steve Sonntag" <VTAG.PRV-3.PROVO@novell.com>, <Kurt@OpenLDAP.org>
Cc: <ietf-ldapbis@OpenLDAP.org>
Subject: Re: authmeth - user & client usage
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__Part39678FFA.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>

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.

--=__Part39678FFA.0__=
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

I'll review my usage of the terms "client" and "user" and try to
consistently user the term client to mean an executing LDAP client
application and the term user to mean a human being interacting with a
client application.
 
Roger

>>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 12/6/2001 2:26:37 PM >>>
At 01:02 PM 2001-12-06, Steve Sonntag wrote:
>>
>>
>>>>> "Kurt D. Zeilenga" < Kurt@OpenLDAP.org > 06-Dec-01 1:43:10 PM
>>>
>>Here are my personal thoughts on this.
>>
>>It may be useful to distinguish between the user (a human or
>>application entity) and the client (director user agent).
>>
>>It would be inappropriate to distinguish components of the client,
>>in particular which portions are part of APIs shared between
>>multiple clients and portions specific to the particular client.
>>
>>Kurt
>
>Agreed, I had no intent of identifying or separating client
>components,

Good, but...

>but instead wanted only to identify what is the responsibility of the
>application/user
>versus the LDAP client protocol agent.

these terms ("application/user" and "client protocol agent") I
find confusing as "application" implies an "implementation" not
an entity acting as a human.



--=__Part39678FFA.0__=
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.1264" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Tahoma">
<DIV>I'll review my usage of the terms "client" and "user" and try to 
consistently user the term client to mean an executing LDAP client application 
and the term user to mean a human being interacting with a client 
application.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Roger<BR><BR>&gt;&gt;&gt; "Kurt D. Zeilenga" &lt;Kurt@OpenLDAP.org&gt; 
12/6/2001 2:26:37 PM &gt;&gt;&gt;<BR>At 01:02 PM 2001-12-06, Steve Sonntag 
wrote:<BR>&gt;&gt;<BR>&gt;&gt;<BR>&gt;&gt;&gt;&gt;&gt; "Kurt D. Zeilenga" 
&lt;<U> <A href="mailto:Kurt@OpenLDAP.org">Kurt@OpenLDAP.org</A></U> &gt; 
06-Dec-01 1:43:10 PM &gt;&gt;&gt;<BR>&gt;&gt;Here are my personal thoughts on 
this.<BR>&gt;&gt;<BR>&gt;&gt;It may be useful to distinguish between the user (a 
human or<BR>&gt;&gt;application entity) and the client (director user 
agent).<BR>&gt;&gt;<BR>&gt;&gt;It would be inappropriate to distinguish 
components of the client,<BR>&gt;&gt;in particular which portions are part of 
APIs shared between<BR>&gt;&gt;multiple clients and portions specific to the 
particular client.<BR>&gt;&gt;<BR>&gt;&gt;Kurt<BR>&gt;<BR>&gt;Agreed, I had no 
intent of identifying or separating client<BR>&gt;components,<BR><BR>Good, 
but...<BR><BR>&gt;but instead wanted only to identify what is the responsibility 
of the<BR>&gt;application/user<BR>&gt;versus the LDAP client protocol 
agent.<BR><BR>these terms ("application/user" and "client protocol agent") 
I<BR>find confusing as "application" implies an "implementation" not<BR>an 
entity acting as a human.<BR><BR></DIV></BODY></HTML>

--=__Part39678FFA.0__=--


From owner-ietf-ldapbis@OpenLDAP.org  Wed Oct  8 10:28: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 KAA17347
	for <ldapbis-archive@lists.ietf.org>; Wed, 8 Oct 2003 10:28:47 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h98ER2j6026278;
	Wed, 8 Oct 2003 14:27: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 h98ELOMZ025922;
	Wed, 8 Oct 2003 14:21:24 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 8 Oct 2003 14:21:24 +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 h98ELNj2025907
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 8 Oct 2003 14:21:23 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from gypsy.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.9/8.12.9) with ESMTP id h98ELLlg078948;
	Wed, 8 Oct 2003 14:21:21 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.0.22.0.20031008191309.03abc278@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
Date: Wed, 08 Oct 2003 19:21:04 -0700
To: "Roger Harrison" <RHARRISON@novell.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: authmeth - user & client usage
Cc: "Steve Sonntag" <VTAG.PRV-3.PROVO@novell.com>, <ietf-ldapbis@OpenLDAP.org>
In-Reply-To: <sf83c442.029@prv-mail20.provo.novell.com>
References: <sf83c442.029@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 06:28 AM 10/8/2003, Roger Harrison wrote:
>these terms ("application/user" and "client protocol agent") I
>find confusing as "application" implies an "implementation" not
>an entity acting as a human.

Actually, it's confusing to use "application" to refer to an
"implementation" and, even more so, just to client implementations.

Here is, I think, a good example of an appropriate use of the
term application (in the context of LDAP specifications):
    PKI is an application of the directory which places
    specific requirements upon clients and servers implementations.

Kurt 



From owner-ietf-ldapbis@OpenLDAP.org  Wed Oct  8 13:59: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 NAA29837
	for <ldapbis-archive@lists.ietf.org>; Wed, 8 Oct 2003 13:59:02 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h98HjQjS047844;
	Wed, 8 Oct 2003 17:57: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 h98HbKRb047506;
	Wed, 8 Oct 2003 17:37:20 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 8 Oct 2003 17:37: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 h98HbHj2047487
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 8 Oct 2003 17:37:17 GMT
	(envelope-from RHARRISON@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Wed, 08 Oct 2003 11:35:19 -0600
Message-Id: <sf83f677.099@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.1 
Date: Wed, 08 Oct 2003 11:30:13 -0600
From: "Roger Harrison" <RHARRISON@novell.com>
To: <Alexey.Melnikov@isode.com>
Cc: <ietf-ldapbis@OpenLDAP.org>
Subject: Re: Comments about draft-ietf-ldapbis-authmeth-06.txt
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__Part2F7199B5.1__="
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.

--=__Part2F7199B5.1__=
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

> More comments:
>
> 1). In 4.1.4
>
> If the client or server decides that the level of authentication or
> privacy is not high enough for it to continue, it SHOULD gracefully
> close the TLS connection immediately after the TLS negotiation has
> completed (see [Protocol] section 4.13.3.1 and section 4.2.3 below).
> If the client decides to continue, it MAY attempt to Start TLS
> again,
>
> I though this is not allowed as it contradicts text in
>
> >5.1.1. Requesting to Start TLS on an LDAP Association
> >
> > The client MAY send the Start TLS extended request at any time
after
> > establishing an LDAP association, except that in the following
cases
> > the client MUST NOT send a Start TLS extended request:
> >
> > - if TLS is currently established on the connection, or
> > - during a multi-stage SASL negotiation, or
> > - if there are any LDAP operations outstanding on the
> > connection.
> >
>
> The text is ambiguous. either the client will have to perform
graceful
> TLS closure and then restart TLS, or the client is allowed to
restart
> TLS without TLS closure, even though TLS is already negotiated.
 
The client needs to perform graceful TLS closure and then restart TLS.
I've adjusted the texxt in 4.4.1 to reflect this.

>
> 2).
>
> >4.2.3. TLS Connection Closure Effects
> >
> > Closure of the TLS session MUST cause the LDAP association to move
> > to an anonymous authentication and authorization state regardless
of
> > the state established over TLS and regardless of the
authentication
> > and authorization state prior to TLS session establishment.
>
> Ok, this was discussed before, so I might be missing some context.
> But is there any good reason for this?
 
This has been discussed before. Leaving the authorization state
unchanged isn't feasible because it could open security holes (high
level of authorization with lack of TLS protection). The best I can
tell, there are really only two reasonable alternatives:
 
1. restore the authorization state that existed just prior to
initiation of TLS session establish
2. go to anonymous authorization state
 
#1 may be difficult for servers to implement, so #2 was chosen as the
default action.  It also guarantees a well-known state upon TLS
closure.

>
> 3).
> >7.3.1. "simple" Authentication Choice
> >
> > DSAs that map the DN sent in the bind request to a directory entry
> > with an associated set of one or more passwords will compare the
> > presented password to the set of passwords associated with that
> > entry. If there is a match, then the server will respond with
> > resultCode success, otherwise the server will respond with
> > resultCode invalidCredentials.
>
> Does this allow for hashed passwords?
 
Yes. It doesn't say anything about how the password values are stored,
only that they must be capable of being compared. If the server has
stored the value in hashed format, it can do a compare by hashing the
presented password value and then comparing the resulting value with the
stored value.

>
> =========
>
> Editorial:
>
> 1). In 4.1.:
>
> Note that the precise effects, on a client's authorization identity,
> of establishing TLS on an LDAP association are described in detail
> in section 4.5.
>
> No such section.
>
> There is a reference to 4.5.1.2 in some other place as well.
 
Thanks for the catch. I've fixed these up.

>
> 2).
>
> >G.32 Clarification on use of SASL mechanisms
> >
> > Section 3.3.1: BTW, what _are_ the "ANONYMOUS" and "PLAIN" SASL
> > mechanisms? They are not defined in RFC2222. If you refer to other
> > SASL mechanisms than those in rfc2222, Maybe you should only list
> > which mechanisms _are_used, instead of which ones are _not.
(Source:
> > Hallvard Furuseth)
>
> Changes to Normative References section should deal with this issue.
>
> Add:
>
> [ANONYMOUS] Zeilenga, K.,"Anonymous SASL Mechanism",
> draft-zeilenga-sasl-anon-xx.txt, a work in progress.
>
> [PLAIN] Zeilenga, K.,"Plain SASL Mechanism",
> draft-zeilenga-sasl-plain-xx.txt, a work in progress.
> (this will replace plain definition in RFC 2595)
>
 
I've removed all normative references to specific SASL mechanisms
except the mandatory DIGEST-MD5 mechanism.  I've added the reference to
[PLAIN] as an informative reference because it is mentioned only
tangentially in the draft.  [ANONYMOUS] is no longer referenced in the
draft.

> Replace:
> [RFC2831] Leach, P. and C. Newman, "Using Digest Authentication as
> a SASL Mechanism", RFC 2831, May 2000.
> with
> [RFC2831] Leach, P., Newman, C., Melnikov, A., "Using Digest
> Authentication as
> a SASL Mechanism", draft-ietf-sasl-rfc2831bis-xx.txt, a work in
> progress.
 
Got it.

>
> Alexey
>

--=__Part2F7199B5.1__=
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.1264" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Tahoma">
<DIV>&gt; More comments:<BR>&gt;<BR>&gt; 1). In 4.1.4<BR>&gt;<BR>&gt; If the 
client or server decides that the level of authentication or<BR>&gt; privacy is 
not high enough for it to continue, it SHOULD gracefully<BR>&gt; close the TLS 
connection immediately after the TLS negotiation has<BR>&gt; completed (see 
[Protocol] section 4.13.3.1 and section 4.2.3 below).<BR>&gt; If the client 
decides to continue, it MAY attempt to Start TLS<BR>&gt; again,<BR>&gt;<BR>&gt; 
I though this is not allowed as it contradicts text in<BR>&gt;<BR>&gt; 
&gt;5.1.1. Requesting to Start TLS on an LDAP Association<BR>&gt; &gt;<BR>&gt; 
&gt; The client MAY send the Start TLS extended request at any time 
after<BR>&gt; &gt; establishing an LDAP association, except that in the 
following cases<BR>&gt; &gt; the client MUST NOT send a Start TLS extended 
request:<BR>&gt; &gt;<BR>&gt; &gt; - if TLS is currently established on the 
connection, or<BR>&gt; &gt; - during a multi-stage SASL negotiation, or<BR>&gt; 
&gt; - if there are any LDAP operations outstanding on the<BR>&gt; &gt; 
connection.<BR>&gt; &gt;<BR>&gt;<BR>&gt; The text is ambiguous. either the 
client will have to perform graceful<BR>&gt; TLS closure and then restart TLS, 
or the client is allowed to restart<BR>&gt; TLS without TLS closure, even though 
TLS is already negotiated.</DIV>
<DIV>&nbsp;</DIV>
<DIV>The client needs to perform graceful TLS closure and then restart TLS. I've 
adjusted the texxt in 4.4.1 to reflect this.</DIV>
<DIV><BR>&gt;<BR>&gt; 2).<BR>&gt;<BR>&gt; &gt;4.2.3. TLS Connection Closure 
Effects<BR>&gt; &gt;<BR>&gt; &gt; Closure of the TLS session MUST cause the LDAP 
association to move<BR>&gt; &gt; to an anonymous authentication and 
authorization state regardless of<BR>&gt; &gt; the state established over TLS 
and regardless of the authentication<BR>&gt; &gt; and authorization state prior 
to TLS session establishment.<BR>&gt;<BR>&gt; Ok, this was discussed before, so 
I might be missing some context.<BR>&gt; But is there any good reason for 
this?</DIV>
<DIV>&nbsp;</DIV>
<DIV>This has been discussed before. Leaving&nbsp;the authorization state 
unchanged isn't feasible because it could open security holes (high level of 
authorization with lack of TLS protection). The best I can tell, there are 
really only two reasonable alternatives:</DIV>
<DIV>&nbsp;</DIV>
<DIV>1. restore the authorization state that existed just prior to initiation of 
TLS session establish</DIV>
<DIV>2. go to anonymous authorization state</DIV>
<DIV>&nbsp;</DIV>
<DIV>#1 may be difficult for servers to implement, so #2 was chosen as the 
default action.&nbsp; It also guarantees a well-known state upon TLS 
closure.</DIV>
<DIV><BR>&gt;<BR>&gt; 3).<BR>&gt; &gt;7.3.1. "simple" Authentication 
Choice<BR>&gt; &gt;<BR>&gt; &gt; DSAs that map the DN sent in the bind request 
to a directory entry<BR>&gt; &gt; with an associated set of one or more 
passwords will compare the<BR>&gt; &gt; presented password to the set of 
passwords associated with that<BR>&gt; &gt; entry. If there is a match, then the 
server will respond with<BR>&gt; &gt; resultCode success, otherwise the server 
will respond with<BR>&gt; &gt; resultCode invalidCredentials.<BR>&gt;<BR>&gt; 
Does this allow for hashed passwords?</DIV>
<DIV>&nbsp;</DIV>
<DIV>Yes. It doesn't say anything about how the password values are stored, only 
that they must be capable of being compared. If the server has stored the value 
in hashed format, it can do a compare by hashing the presented password value 
and then comparing the resulting value with the stored value.</DIV>
<DIV><BR>&gt;<BR>&gt; =========<BR>&gt;<BR>&gt; Editorial:<BR>&gt;<BR>&gt; 1). 
In 4.1.:<BR>&gt;<BR>&gt; Note that the precise effects, on a client's 
authorization identity,<BR>&gt; of establishing TLS on an LDAP association are 
described in detail<BR>&gt; in section 4.5.<BR>&gt;<BR>&gt; No such 
section.<BR>&gt;<BR>&gt; There is a reference to 4.5.1.2 in some other place as 
well.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Thanks for the catch. I've fixed these up.</DIV>
<DIV><BR>&gt;<BR>&gt; 2).<BR>&gt;<BR>&gt; &gt;G.32 Clarification on use of SASL 
mechanisms<BR>&gt; &gt;<BR>&gt; &gt; Section 3.3.1: BTW, what _are_ the 
"ANONYMOUS" and "PLAIN" SASL<BR>&gt; &gt; mechanisms? They are not defined in 
RFC2222. If you refer to other<BR>&gt; &gt; SASL mechanisms than those in 
rfc2222, Maybe you should only list<BR>&gt; &gt; which mechanisms _are_used, 
instead of which ones are _not. (Source:<BR>&gt; &gt; Hallvard 
Furuseth)<BR>&gt;<BR>&gt; Changes to Normative References section should deal 
with this issue.<BR>&gt;<BR>&gt; Add:<BR>&gt;<BR>&gt; [ANONYMOUS] Zeilenga, 
K.,"Anonymous SASL Mechanism",<BR>&gt; draft-zeilenga-sasl-anon-xx.txt, a work 
in progress.</DIV>
<DIV>&gt;<BR>&gt; [PLAIN] Zeilenga, K.,"Plain SASL Mechanism",<BR>&gt; 
draft-zeilenga-sasl-plain-xx.txt, a work in progress.<BR>&gt; (this will replace 
plain definition in RFC 2595)<BR>&gt;</DIV>
<DIV>&nbsp;</DIV>
<DIV>I've removed all normative references to specific SASL mechanisms except 
the mandatory DIGEST-MD5 mechanism.&nbsp; I've added the reference to [PLAIN] as 
an informative reference because it is mentioned only tangentially in the 
draft.&nbsp; [ANONYMOUS] is no longer referenced in the draft.</DIV>
<DIV><BR>&gt; Replace:<BR>&gt; [RFC2831] Leach, P. and C. Newman, "Using Digest 
Authentication as<BR>&gt; a SASL Mechanism", RFC 2831, May 2000.<BR>&gt; 
with<BR>&gt; [RFC2831] Leach, P., Newman, C., Melnikov, A., "Using 
Digest<BR>&gt; Authentication as<BR>&gt; a SASL Mechanism", 
draft-ietf-sasl-rfc2831bis-xx.txt, a work in<BR>&gt; progress.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Got it.</DIV>
<DIV><BR>&gt;<BR>&gt; Alexey<BR>&gt;</DIV></BODY></HTML>

--=__Part2F7199B5.1__=--


From owner-ietf-ldapbis@OpenLDAP.org  Wed Oct  8 14:05: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 OAA00122
	for <ldapbis-archive@lists.ietf.org>; Wed, 8 Oct 2003 14:05:59 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h98I33j2049556;
	Wed, 8 Oct 2003 18:03:03 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 h98HseTm048468;
	Wed, 8 Oct 2003 17:54:40 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 8 Oct 2003 17:54:40 +0000
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h98HsXj2048452
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 8 Oct 2003 17:54:35 GMT
	(envelope-from Alexey.Melnikov@isode.com)
Received: from isode.com (shiny.isode.com [62.3.217.250]) by rufus.isode.com
          via TCP (with SMTP (internal)) with ESMTP;
          Wed, 8 Oct 2003 18:54:19 +0100
Message-ID: <3F844F4A.6050208@isode.com>
Date: Wed, 08 Oct 2003 18:54:18 +0100
From: Alexey Melnikov <Alexey.Melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Roger Harrison <RHARRISON@novell.com>
CC: ietf-ldapbis@OpenLDAP.org
Subject: Re: Comments about draft-ietf-ldapbis-authmeth-06.txt
References: <sf83f677.098@prv-mail20.provo.novell.com>
In-Reply-To: <sf83f677.098@prv-mail20.provo.novell.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Roger Harrison wrote:

> > 2).
> > >4.2.3. TLS Connection Closure Effects
> > >
> > > Closure of the TLS session MUST cause the LDAP association to move
> > > to an anonymous authentication and authorization state regardless of
> > > the state established over TLS and regardless of the authentication
> > > and authorization state prior to TLS session establishment.
> >
> > Ok, this was discussed before, so I might be missing some context.
> > But is there any good reason for this?
>  
> This has been discussed before. Leaving the authorization state 
> unchanged isn't feasible because it could open security holes (high 
> level of authorization with lack of TLS protection). The best I can 
> tell, there are really only two reasonable alternatives:
>  
> 1. restore the authorization state that existed just prior to 
> initiation of TLS session establish
> 2. go to anonymous authorization state
>  
> #1 may be difficult for servers to implement, so #2 was chosen as the 
> default action.  It also guarantees a well-known state upon TLS closure.

I think you should add the explanation you gave me to the document.

The reason why I've asked this questions is as follows. Imagine that the 
client used TLS and than authenticated using GSSAPI (Kerberos) or 
DIGEST-MD5.
Then the client decides to close TLS. Why is suddenly authentication 
information is invalid, it wasn't derived from TLS information in the 
first place?
This is just an unexpected behavior.

I guess the answer to this might be "Doctor, it hurts when I do this." - 
"Don't do this".

Regards, 
Alexey
Alexey Melnikov
__________________________________________
Isode Limited, http://www.isode.com

Cell: +44 7753759732

IETF standard related pages:
http://orthanc.ab.ca/mel/devel/Links.html

Personal Home Page: http://orthanc.ab.ca/mel
__________________________________________





From owner-ietf-ldapbis@OpenLDAP.org  Wed Oct  8 14:28:53 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01452
	for <ldapbis-archive@lists.ietf.org>; Wed, 8 Oct 2003 14:28:52 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h98IR3j6051209;
	Wed, 8 Oct 2003 18:27: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 h98IMEex051051;
	Wed, 8 Oct 2003 18:22:14 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 8 Oct 2003 18:22:14 +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 h98IMBj2050978;
	Wed, 8 Oct 2003 18:22:11 GMT
	(envelope-from RHARRISON@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Wed, 08 Oct 2003 12:21:51 -0600
Message-Id: <sf84015f.093@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.1 
Date: Wed, 08 Oct 2003 12:16:43 -0600
From: "Roger Harrison" <RHARRISON@novell.com>
To: <Kurt@OpenLDAP.org>
Cc: <ietf-ldapbis@OpenLDAP.org>
Subject: Re: [authmeth] use of SASL "PLAIN" witih LDAP
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__Part1C42AA9B.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>

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.

--=__Part1C42AA9B.0__=
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

In authmeth -07 I've stated the following to clarify this:
 
"LDAP allows authentication via any SASL mechanism [SASL]. As LDAP
includes native anonymous and plaintext authentication methods, the
"ANONYMOUS" [ANONYMOUS] and "PLAIN" [PLAIN] SASL mechanisms are
typically not used with LDAP."
 
Roger

>>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 6/28/2003 10:52:05 PM >>>
At 08:55 AM 6/28/2003, Roger Harrison wrote:
>In my conversations with WG members, I have learned that at least one
LDAP server implementer has found the SASL "PLAIN" mechanism useful in
authenticating to legacy systems that do not represent authentication
identities as DNs.

PLAIN is also useful where proxy authorization is need.

>[authmeth] section 3.3.1 implicitly disallows the use of the SASL
"PLAIN" mechanism with LDAP:
> 
>"As LDAP includes native anonymous and plaintext authentication
methods, the "ANONYMOUS" and "PLAIN" SASL mechanisms are not used with
LDAP."

Note that Section 4 of RFC 2829 implied that PLAIN may be used (with
TLS).

>Should we remove the reference to "PLAIN" in this section to allow the
use of the SASL "PLAIN" mechanism?

I suggest inserting the word 'typically' (or 'generally') in the
quoted sentence. That is,
As LDAP includes native anonymous and plaintext authentication
methods, the "ANONYMOUS" and "PLAIN" SASL mechanisms are typically
not used with LDAP.

This allows use of PLAIN (and ANONYMOUS) in atypical situations
while still noting to implementors that these mechanisms have limited
applicability.

Kurt 



--=__Part1C42AA9B.0__=
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.1264" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Tahoma">
<DIV>In authmeth -07 I've stated the following to clarify this:</DIV>
<DIV>&nbsp;</DIV>
<DIV>"LDAP allows authentication via any SASL mechanism [SASL]. As LDAP includes 
native anonymous and plaintext authentication methods, the "ANONYMOUS" 
[ANONYMOUS] and "PLAIN" [PLAIN] SASL mechanisms are typically not used with 
LDAP."</DIV>
<DIV>&nbsp;</DIV>
<DIV>Roger<BR><BR>&gt;&gt;&gt; "Kurt D. Zeilenga" &lt;Kurt@OpenLDAP.org&gt; 
6/28/2003 10:52:05 PM &gt;&gt;&gt;<BR>At 08:55 AM 6/28/2003, Roger Harrison 
wrote:<BR>&gt;In my conversations with WG members, I have learned that at least 
one LDAP server implementer has found the SASL "PLAIN" mechanism useful in 
authenticating to legacy systems that do not represent authentication identities 
as DNs.<BR><BR>PLAIN is also useful where proxy authorization is 
need.<BR><BR>&gt;[authmeth] section 3.3.1 implicitly disallows the use of the 
SASL "PLAIN" mechanism with LDAP:<BR>&gt; <BR>&gt;"As LDAP includes native 
anonymous and plaintext authentication methods, the "ANONYMOUS" and "PLAIN" SASL 
mechanisms are not used with LDAP."<BR><BR>Note that Section 4 of RFC 2829 
implied that PLAIN may be used (with TLS).<BR><BR>&gt;Should we remove the 
reference to "PLAIN" in this section to allow the use of the SASL "PLAIN" 
mechanism?<BR><BR>I suggest inserting the word 'typically' (or 'generally') in 
the<BR>quoted sentence. That is,<BR>As LDAP includes native anonymous and 
plaintext authentication<BR>methods, the "ANONYMOUS" and "PLAIN" SASL mechanisms 
are typically<BR>not used with LDAP.<BR><BR>This allows use of PLAIN (and 
ANONYMOUS) in atypical situations<BR>while still noting to implementors that 
these mechanisms have limited<BR>applicability.<BR><BR>Kurt 
<BR><BR></DIV></BODY></HTML>

--=__Part1C42AA9B.0__=--


From owner-ietf-ldapbis@OpenLDAP.org  Wed Oct  8 17:18:34 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 RAA09683
	for <ldapbis-archive@lists.ietf.org>; Wed, 8 Oct 2003 17:18:33 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h98LF5j6060952;
	Wed, 8 Oct 2003 21:16:53 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h98L9JvV060216;
	Wed, 8 Oct 2003 21:09:19 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 8 Oct 2003 21:09:19 +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 h98L9Fj2060122;
	Wed, 8 Oct 2003 21:09:15 GMT
	(envelope-from RHARRISON@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Wed, 08 Oct 2003 15:08:50 -0600
Message-Id: <sf842882.027@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.1 
Date: Wed, 08 Oct 2003 14:26:44 -0600
From: "Roger Harrison" <RHARRISON@novell.com>
To: <Kurt@OpenLDAP.org>, <michael@stroeder.com>
Cc: <ietf-ldapbis@OpenLDAP.org>
Subject: Re: [authmeth] secure derivations of server hostname
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__PartB4EA0214.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>

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.

--=__PartB4EA0214.0__=
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Based on the list traffic that has occurred on this subject, I've changed =
the wording for authmeth -08 to read:
=20
"The client MUST use the server provided by the user (or other trusted =
entity) as the value to compare against the server name as expressed in =
the server's certificate. A hostname derived from the user input is to be =
considered provided by the user only if derived in a secure fashion (e.g., =
DNSSEC)."
=20
Note that I've excluded the explicit provision for derivations confirmed =
by the user because I believe that (1) Michael's concerns regarding the =
nearly automatic user acceptance of confirmation messages are real and (2) =
if user confirmation of a derived name is considered a secure enough =
derivation for a particular application, the remaining text still leaves =
that as an option without encouraging its use.
=20
Roger

>>> Michael Str=F6der <michael@stroeder.com> 6/30/2003 4:14:53 PM >>>
Kurt D. Zeilenga wrote:
>=20
> And with regards to mappings of "localhost" (or 127.0.0.1 or ::1), I
> view the security considerations to a local matter (that is, it may
> be secure in some environments, not in others).

If it's only secure in a minority of systems that's not a strong argument.

> This text:
> "The client MUST use the server hostname it used to open the
> LDAP connection as the value to compare against the server name as
> expressed in the server's certificate. The client MUST NOT use any
> other derived form of name including the server's canonical DNS name."
> is problematic for a couple of reasons.
>=20
> First, it says "the server hostname it used to open the LDAP connection"
> instead of "the server hostname provided by the user (or application
> entity or other trusted entity)".

Yes, the wording should be changed.

> Second, derivation is fine if the result is confirmed by the user.

Well, given all the misconfigured systems today human user are trained =
to=20
happily click away every alert box with "OK" just to step forward. :-/

> So, I'm thinking this should be reworded.
> The client MUST use the server hostname provided by the user (or other =
trusted
> entity) as the value to compare against the server name as expressed in =
the
> server's certificate. A hostname derived from the user input is to be =
considered
> provided by the user only if derived in a secure fashion (e.g., DNSSEC) =
or confirmed
> by the user.

I'd prefer to drop the note about user confirmation for the reason =
above.=20
IMHO the common work-around with SSL-related dialog boxes appearing all =
the=20
time asking the user for confirmation with most times very unclear =
language=20
should not be mentioned in such a standard.

Ciao, Michael.




--=__PartB4EA0214.0__=
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1"=
>
<META content=3D"MSHTML 6.00.2800.1264" name=3DGENERATOR></HEAD>
<BODY style=3D"MARGIN: 4px 4px 1px; FONT: 10pt Tahoma">
<DIV>Based on the list traffic that has occurred on this subject, I've =
changed=20
the wording for authmeth -08 to read:</DIV>
<DIV>&nbsp;</DIV>
<DIV>"The client MUST use the server provided by the user (or other =
trusted=20
entity) as the value to compare against the server name as expressed in =
the=20
server's certificate. A hostname derived from the user input is to be =
considered=20
provided by the user only if derived in a secure fashion (e.g., DNSSEC)."</=
DIV>
<DIV>&nbsp;</DIV>
<DIV>Note that I've excluded the explicit provision for derivations =
confirmed by=20
the user because I believe that (1) Michael's concerns regarding the =
nearly=20
automatic user acceptance of confirmation messages&nbsp;are real and =
(2)&nbsp;if=20
user confirmation of a derived name is considered a secure enough =
derivation for=20
a particular application, the remaining text still leaves that as an =
option=20
without encouraging its use.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Roger<BR><BR>&gt;&gt;&gt; Michael Str=F6der &lt;michael@stroeder.com&g=
t;=20
6/30/2003 4:14:53 PM &gt;&gt;&gt;<BR>Kurt D. Zeilenga wrote:<BR>&gt; =
<BR>&gt;=20
And with regards to mappings of "localhost" (or 127.0.0.1 or ::1), =
I<BR>&gt;=20
view the security considerations to a local matter (that is, it may<BR>&gt;=
 be=20
secure in some environments, not in others).<BR><BR>If it's only secure in =
a=20
minority of systems that's not a strong argument.<BR><BR>&gt; This =
text:<BR>&gt;=20
"The client MUST use the server hostname it used to open the<BR>&gt; =
LDAP=20
connection as the value to compare against the server name as<BR>&gt; =
expressed=20
in the server's certificate. The client MUST NOT use any<BR>&gt; other =
derived=20
form of name including the server's canonical DNS name."<BR>&gt; is =
problematic=20
for a couple of reasons.<BR>&gt; <BR>&gt; First, it says "the server =
hostname it=20
used to open the LDAP connection"<BR>&gt; instead of "the server =
hostname=20
provided by the user (or application<BR>&gt; entity or other trusted=20
entity)".<BR><BR>Yes, the wording should be changed.<BR><BR>&gt; Second,=20=

derivation is fine if the result is confirmed by the user.<BR><BR>Well, =
given=20
all the misconfigured systems today human user are trained to <BR>happily =
click=20
away every alert box with "OK" just to step forward. :-/<BR><BR>&gt; So, =
I'm=20
thinking this should be reworded.<BR>&gt; The client MUST use the =
server=20
hostname provided by the user (or other trusted<BR>&gt; entity) as the =
value to=20
compare against the server name as expressed in the<BR>&gt; server's=20
certificate. A hostname derived from the user input is to be considered<BR>=
&gt;=20
provided by the user only if derived in a secure fashion (e.g., DNSSEC) =
or=20
confirmed<BR>&gt; by the user.<BR><BR>I'd prefer to drop the note about =
user=20
confirmation for the reason above. <BR>IMHO the common work-around with=20
SSL-related dialog boxes appearing all the <BR>time asking the user for=20
confirmation with most times very unclear language <BR>should not be =
mentioned=20
in such a standard.<BR><BR>Ciao, Michael.<BR><BR></DIV></BODY></HTML>

--=__PartB4EA0214.0__=--


From owner-ietf-ldapbis@OpenLDAP.org  Thu Oct  9 03:15:33 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA09682
	for <ldapbis-archive@lists.ietf.org>; Thu, 9 Oct 2003 03:15:32 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h997CPj2003642;
	Thu, 9 Oct 2003 07:12: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 h9970T90002722;
	Thu, 9 Oct 2003 07:00:29 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 9 Oct 2003 07:00:29 +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 h9970Sj2002698
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 9 Oct 2003 07:00:28 GMT
	(envelope-from jimse@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Thu, 09 Oct 2003 01:00:08 -0600
Message-Id: <sf84b318.007@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.1 
Date: Thu, 09 Oct 2003 00:59:46 -0600
From: "Jim Sermersheim" <jimse@novell.com>
To: <ietf-ldapbis@OpenLDAP.org>
Subject: Models: modifying subschema subentry
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__PartA7F91072.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>

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.

--=__PartA7F91072.0__=
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

In Section 4.4, there is: "To read schema attributes
  from the subschema (sub)entry, clients MUST issue a base object
search
  where the filter is "(objectClass=subschema)" [Filters] and the list
  of attributes includes the names of the desired schema attributes
(as
  they are operational).  This filter allows LDAP servers which
gateway
  to X.500 to detect that subentry information is being requested."
 
The last bit is interesting. This is so the LDAP server knows that the
client is reading a subentry as opposed to a directory entry. This
presumes that there are cases where the LDAP server needs to know the
difference, and this special filter is given as that way.
 
Earlier in Section 4.2 it says "Servers MAY allow subschema
modification.  Procedures for subschema modification are discussed in
Section 14.5 of [X.501]."
 
This is new text (was not in RFC 2251). This does not consider the case
where the LDAP server needs to know the difference (as above) and
doesn't provide a way for the client to convey the difference.
 
Jim


--=__PartA7F91072.0__=
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 5.50.4933.1800" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Microsoft Sans Serif">
<DIV>In Section 4.4, there is: "To read schema attributes<BR>&nbsp; from the subschema (sub)entry, clients MUST issue a base object search<BR>&nbsp; where the filter is "(objectClass=subschema)" [Filters] and the list<BR>&nbsp; of attributes includes the names of the desired schema attributes (as<BR>&nbsp; they are operational).&nbsp; This filter allows LDAP servers which gateway<BR>&nbsp; to X.500 to detect that subentry information is being requested."</DIV>
<DIV>&nbsp;</DIV>
<DIV>The last bit is interesting. This is so the LDAP server knows that the client is reading a subentry as opposed to a directory entry. This presumes that there are cases where the LDAP server needs to know the difference, and this special filter is given as that way.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Earlier in Section 4.2 it says "Servers MAY allow subschema modification.&nbsp; Procedures for subschema modification are discussed in Section 14.5 of [X.501]."</DIV>
<DIV>&nbsp;</DIV>
<DIV>This is new text (was not in RFC 2251). This does not consider the case where the LDAP server needs to know the difference (as above) and doesn't provide a way for the client to convey the difference.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Jim<BR></DIV></BODY></HTML>
--=__PartA7F91072.0__=--


From owner-ietf-ldapbis@OpenLDAP.org  Thu Oct  9 06:11:54 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA14336
	for <ldapbis-archive@lists.ietf.org>; Thu, 9 Oct 2003 06:11:54 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h999v9jW019851;
	Thu, 9 Oct 2003 10:10: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 h999v1r7019841;
	Thu, 9 Oct 2003 09:57:01 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 9 Oct 2003 09:57:01 +0000
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h999uwj2019830
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 9 Oct 2003 09:56:59 GMT
	(envelope-from Alexey.Melnikov@isode.com)
Received: from isode.com (shiny.isode.com [62.3.217.250]) by rufus.isode.com
          via TCP (with SMTP (internal)) with ESMTP;
          Thu, 9 Oct 2003 10:56:49 +0100
Message-ID: <3F8530DF.9040200@isode.com>
Date: Thu, 09 Oct 2003 10:56:47 +0100
From: Alexey Melnikov <Alexey.Melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Roger Harrison <RHARRISON@novell.com>
CC: ietf-ldapbis@OpenLDAP.org
Subject: Re: Comments about draft-ietf-ldapbis-authmeth-06.txt
References: <sf83f677.098@prv-mail20.provo.novell.com> <3F844F4A.6050208@isode.com>
In-Reply-To: <3F844F4A.6050208@isode.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Alexey Melnikov wrote:

> Roger Harrison wrote:
>
>> > 2).
>> > >4.2.3. TLS Connection Closure Effects
>> > >
>> > > Closure of the TLS session MUST cause the LDAP association to move
>> > > to an anonymous authentication and authorization state regardless of
>> > > the state established over TLS and regardless of the authentication
>> > > and authorization state prior to TLS session establishment.
>> >
>> > Ok, this was discussed before, so I might be missing some context.
>> > But is there any good reason for this?
>>  
>> This has been discussed before. Leaving the authorization state 
>> unchanged isn't feasible because it could open security holes (high 
>> level of authorization with lack of TLS protection). The best I can 
>> tell, there are really only two reasonable alternatives:
>>  
>> 1. restore the authorization state that existed just prior to 
>> initiation of TLS session establish
>> 2. go to anonymous authorization state
>>  
>> #1 may be difficult for servers to implement, so #2 was chosen as the 
>> default action.  It also guarantees a well-known state upon TLS closure.
>
>
> I think you should add the explanation you gave me to the document.
>
> The reason why I've asked this questions is as follows. Imagine that 
> the client used TLS and than authenticated using GSSAPI (Kerberos) or 
> DIGEST-MD5.
> Then the client decides to close TLS. Why is suddenly authentication 
> information is invalid, it wasn't derived from TLS information in the 
> first place?
> This is just an unexpected behavior. 

This reminded me:

1). LDAP has to state how TLS and SASL security layers are stacked.
2). When you close TLS, do you want to also remove a SASL security layer?
 Usually a SASL security layer state is stored separately from the SASL 
authentication state, so you can keep it.
 If you decide to remove it, you need to define at what point the data 
is no longer protected.

Cheers,

Alexey
__________________________________________
Isode Limited, http://www.isode.com

Cell: +44 7753759732

IETF standard related pages:
http://orthanc.ab.ca/mel/devel/Links.html

Personal Home Page: http://orthanc.ab.ca/mel
__________________________________________




From owner-ietf-ldapbis@OpenLDAP.org  Thu Oct  9 12: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 MAA28458
	for <ldapbis-archive@lists.ietf.org>; Thu, 9 Oct 2003 12:47:26 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h99GgAj4052025;
	Thu, 9 Oct 2003 16:43: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 h99GQlgI050293;
	Thu, 9 Oct 2003 16:26:47 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 9 Oct 2003 16:26:47 +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 h99GQjj2050282
	for <ietf-ldapbis@openldap.org>; Thu, 9 Oct 2003 16:26:45 GMT
	(envelope-from dinaras@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 MAA26821;
	Thu, 9 Oct 2003 12:26:34 -0400 (EDT)
Message-Id: <200310091626.MAA26821@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-authmeth-07.txt
Date: Thu, 09 Oct 2003 12:26:34 -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: Authentication Methods and Connection Level 
			  Security Mechanism
	Author(s)	: R. Harrison
	Filename	: draft-ietf-ldapbis-authmeth-07.txt
	Pages		: 50
	Date		: 2003-10-9
	
This document describes LDAPv3 (Lightweight Directory Access 
Protocol v3) authentication methods and connection level security 
mechanisms that are required of all conforming LDAPv3 server 
implementations and makes recommendations for combinations of these 
mechanisms to be used in various deployment circumstances.  
Among the mechanisms described are 
- various forms of authentication including anonymous 
authentication, password-based authentication, and certificate 
based authentication 
- the use of SASL mechanisms with LDAPv3 
- the use of TLS (Transport Layer Security) with LDAPv3 
- the various authentication and authorization states through 
which a connection to an LDAP server may pass and the actions 
that trigger these state changes.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ldapbis-authmeth-07.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-authmeth-07.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-authmeth-07.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-10-9122604.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ldapbis-authmeth-07.txt

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

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

--OtherAccess--

--NextPart--




From owner-ietf-ldapbis@OpenLDAP.org  Thu Oct  9 18:00: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 SAA12691
	for <ldapbis-archive@lists.ietf.org>; Thu, 9 Oct 2003 18:00:20 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h99Lx2j2077657;
	Thu, 9 Oct 2003 21:59: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 h99LkXsa076365;
	Thu, 9 Oct 2003 21:46:33 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 9 Oct 2003 21:46:33 +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 h99LkVj2076354
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 9 Oct 2003 21:46:32 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from gypsy.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.9/8.12.9) with ESMTP id h99LkVlg043526
	for <ietf-ldapbis@openldap.org>; Thu, 9 Oct 2003 21:46:31 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.0.22.0.20031009143358.03820940@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
Date: Thu, 09 Oct 2003 14:45:59 -0700
To: ietf-ldapbis@OpenLDAP.org
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: unbind not the anti-bind
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 naming of the unbind operation has lead some to think
it is the opposite of bind operation.  While at one
time (long before LDAPv3) it might have been, it is not
in LDAPv3.  A suggest the following note be added to the
Unbind section (and possible a similar statement to the Bind
section).

	It should be noted that the Unbind operation is
	not the antithesis of the Bind operation as the
	name implies.  The naming of these operations
	is historical.  The Bind operation should be
	thought of as the "authenticate" operation.
	The Unbind operation should be thought of as the
	"quit" operation.

Kurt



From owner-ietf-ldapbis@OpenLDAP.org  Thu Oct  9 19:54: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 TAA17703
	for <ldapbis-archive@lists.ietf.org>; Thu, 9 Oct 2003 19:54:04 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h99NpEj6089870;
	Thu, 9 Oct 2003 23:52: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 h99NoAt6089798;
	Thu, 9 Oct 2003 23:50:10 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 9 Oct 2003 23:50:10 +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 h99No7j2089760
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 9 Oct 2003 23:50:08 GMT
	(envelope-from steven.legg@adacel.com.au)
Received: from nexus.adacel.com (Not Verified[10.32.240.1]) by adacel.com with NetIQ MailMarshal (v5.5.3.16)
	id <B000176d79>; Fri, 10 Oct 2003 09:44:25 +1000
Received: (qmail 17137 invoked from network); 9 Oct 2003 23:37:34 -0000
Received: from unknown (HELO adacel.com.au) (10.32.24.165)
  by nexus.adacel.com with SMTP; 9 Oct 2003 23:37:34 -0000
Message-ID: <3F85F415.1020007@adacel.com.au>
Date: Fri, 10 Oct 2003 10:49:41 +1100
From: Steven Legg <steven.legg@adacel.com.au>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3.1) Gecko/20030425
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Jim Sermersheim <jimse@novell.com>
CC: ietf-ldapbis@OpenLDAP.org
Subject: Re: Models: modifying subschema subentry
References: <sf84b318.007@prv-mail20.provo.novell.com>
In-Reply-To: <sf84b318.007@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


Jim,

Jim Sermersheim wrote:
> In Section 4.4, there is: "To read schema attributes
>   from the subschema (sub)entry, clients MUST issue a base object search
>   where the filter is "(objectClass=subschema)" [Filters] and the list
>   of attributes includes the names of the desired schema attributes (as
>   they are operational).  This filter allows LDAP servers which gateway
>   to X.500 to detect that subentry information is being requested."
>  
> The last bit is interesting. This is so the LDAP server knows that the 
> client is reading a subentry as opposed to a directory entry. This 
> presumes that there are cases where the LDAP server needs to know the 
> difference, and this special filter is given as that way.

The case where the LDAP server needs to know the difference is when it
translates the LDAP search into a DAP or DSP search. A DAP/DSP base object
search of a subentry will return noSuchEntry if the subentries bit of the
ServiceControls options is not set (which seems to be an unnecessary
condition, but is there nonetheless). The LDAP server needs to have some
way of deciding whether or not to set the subentries bit. The filter on
objectClass is that way.

>  
> Earlier in Section 4.2 it says "Servers MAY allow subschema 
> modification.  Procedures for subschema modification are discussed in 
> Section 14.5 of [X.501]."
>  
> This is new text (was not in RFC 2251). This does not consider the case 
> where the LDAP server needs to know the difference (as above) and 
> doesn't provide a way for the client to convey the difference.

The subentries bit is ignored for DAP/DSP operations other than search
and list, so a DAP/DSP modify will operate on the base object regardless of
whether it is a subentry or entry.

It would have been nice if X.500 ignored the subentries bit for base
object searches as well.

Regards,
Steven

>  
> Jim



From owner-ietf-ldapbis@OpenLDAP.org  Thu Oct  9 22:50: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 WAA22200
	for <ldapbis-archive@lists.ietf.org>; Thu, 9 Oct 2003 22:50:25 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h9A2n5j2002896;
	Fri, 10 Oct 2003 02: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 h9A2Y5PG001393;
	Fri, 10 Oct 2003 02:34:05 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Fri, 10 Oct 2003 02:34:05 +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 h9A2Y4j2001377
	for <ietf-ldapbis@OpenLDAP.org>; Fri, 10 Oct 2003 02:34:04 GMT
	(envelope-from jimse@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Thu, 09 Oct 2003 20:33:44 -0600
Message-Id: <sf85c628.002@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.1 
Date: Thu, 09 Oct 2003 20:33:26 -0600
From: "Jim Sermersheim" <jimse@novell.com>
To: <ietf-ldapbis@OpenLDAP.org>
Subject: Re: unbind not the anti-bind
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__PartADF31966.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>

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.

--=__PartADF31966.0__=
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Good clarification.

>>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 10/9/03 3:45:59 PM >>>
The naming of the unbind operation has lead some to think
it is the opposite of bind operation. While at one
time (long before LDAPv3) it might have been, it is not
in LDAPv3. A suggest the following note be added to the
Unbind section (and possible a similar statement to the Bind
section).

It should be noted that the Unbind operation is
not the antithesis of the Bind operation as the
name implies. The naming of these operations
is historical. The Bind operation should be
thought of as the "authenticate" operation.
The Unbind operation should be thought of as the
"quit" operation.

Kurt



--=__PartADF31966.0__=
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 5.50.4933.1800" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Microsoft Sans Serif">
<DIV>Good clarification.</DIV>
<DIV><BR>&gt;&gt;&gt; "Kurt D. Zeilenga" &lt;Kurt@OpenLDAP.org&gt; 10/9/03 3:45:59 PM &gt;&gt;&gt;<BR>The naming of the unbind operation has lead some to think<BR>it is the opposite of bind operation. While at one<BR>time (long before LDAPv3) it might have been, it is not<BR>in LDAPv3. A suggest the following note be added to the<BR>Unbind section (and possible a similar statement to the Bind<BR>section).<BR><BR>It should be noted that the Unbind operation is<BR>not the antithesis of the Bind operation as the<BR>name implies. The naming of these operations<BR>is historical. The Bind operation should be<BR>thought of as the "authenticate" operation.<BR>The Unbind operation should be thought of as the<BR>"quit" operation.<BR><BR>Kurt<BR><BR></DIV></BODY></HTML>
--=__PartADF31966.0__=--


From owner-ietf-ldapbis@OpenLDAP.org  Fri Oct 10 03:17: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 DAA12141
	for <ldapbis-archive@lists.ietf.org>; Fri, 10 Oct 2003 03:17:26 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h9A7Elj2020825;
	Fri, 10 Oct 2003 07: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 h9A71IHK019293;
	Fri, 10 Oct 2003 07:01:18 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Fri, 10 Oct 2003 07:01:18 +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 h9A71Ej2019175
	for <ietf-ldapbis@OpenLDAP.org>; Fri, 10 Oct 2003 07:01:16 GMT
	(envelope-from steven.legg@adacel.com.au)
Received: from nexus.adacel.com (Not Verified[10.32.240.1]) by adacel.com with NetIQ MailMarshal (v5.5.3.16)
	id <B000177632>; Fri, 10 Oct 2003 16:55:34 +1000
Received: (qmail 26601 invoked from network); 10 Oct 2003 06:48:44 -0000
Received: from unknown (HELO adacel.com.au) (10.32.24.165)
  by nexus.adacel.com with SMTP; 10 Oct 2003 06:48:44 -0000
Message-ID: <3F865925.3020908@adacel.com.au>
Date: Fri, 10 Oct 2003 18:00:53 +1100
From: Steven Legg <steven.legg@adacel.com.au>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3.1) Gecko/20030425
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
CC: ietf-ldapbis@OpenLDAP.org
Subject: Re: Steven's protocol comments
References: <5.2.0.9.0.20030919105440.03bcf5d8@127.0.0.1> <005d01c38bcd$ba767db0$a518200a@osmium.mtwav.adacel.com.au> <6.0.0.22.0.20031008062239.03ac8e60@127.0.0.1>
In-Reply-To: <6.0.0.22.0.20031008062239.03ac8e60@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,

Kurt D. Zeilenga wrote:
> At 10:50 PM 10/5/2003, Steven Legg wrote:
> 
>> Here are some comments on draft-ietf-ldapbis-protocol-17.txt .
>> They are mostly of an editorial nature.
> 
> 
> I'm mostly fine with Steven's suggestions...  but have a few
> comments here and there to add. - Kurt
> 
> 
>>>    If the client wishes to progress the operation, it MUST follow the 
>>>    referral by contacting one of the servers.
>>
>>
>> "If" and "MUST" make this an effective "MAY", e.g.
>>
>>     "The Client MAY progress the operation by following the referral and
>>     contacting one of the servers."
> 
> 
> I think this MAY could be downcased.

No objection.


>>>    If the server's schema defines a textual name for an attribute 
>>> type,    it SHOULD use a textual name for attributes of that 
>>> attribute type by    specifying one of the textual names as the value 
>>> of the attribute    type. Otherwise, the server uses the object 
>>> identifier for the    attribute type by specifying the object 
>>> identifier, in ldapOID form,    as the value of attribute type. If 
>>> the server determines that    returning a textual name will cause 
>>> interoperability problems, it    SHOULD return the ldapOID form of 
>>> the attribute type. 
>>
>>
>> This paragraph is a bit shaky. Consider this instead:
>>
>>  "If the server's schema defines short names [Models] for an attribute 
>> type
>>   then the server SHOULD use one of those names in attribute descriptions
>>   for that attribute type (in preference to using the dotted decimal 
>> format
>>   of the attribute type's object identifier). The server should not 
>> use the
>>   short name if that name is known by the server to be ambiguous, or
>>   otherwise likely to cause interoperability problems."
> 
> 
> I think the "should not" should be a "SHOULD NOT".

I thought of that but decided against it because the second sentence
is discussing a circumstance in which the preceding SHOULD would be
disregarded by an implementor. It seems inappropriate to me to have two
opposing implementation imperatives addressing the same point.

> 
>>> 4.12. Extended Operation 
>>
>>
>>>    Servers list the requestName of all ExtendedRequests they recognize 
>>
>>            ^ SHALL ?
> 
> 
> No.  First, "all" is too strong.  Servers should be allowed
> to restrict the set of values by access or other
> administrative controls and/or by current available and/or
> other factors.

Agreed.

> And since no great harm is caused by not providing a value
> (especially given they are rarely used by clients), a
> SHALL is way too strong.

A "MAY" then ?

> I suggest deleting "all" and s/recognize/support/.
> 
> (It would be inappropriate to publish a value which you
> recognized but didn't support).


Regards,
Steven



From owner-ietf-ldapbis@OpenLDAP.org  Fri Oct 10 12:25: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 MAA05741
	for <ldapbis-archive@lists.ietf.org>; Fri, 10 Oct 2003 12:25:21 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h9AGLvj4057452;
	Fri, 10 Oct 2003 16:23:38 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h9AGAHdq056901;
	Fri, 10 Oct 2003 16:10:17 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Fri, 10 Oct 2003 16:10:17 +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 h9AGAFj2056881
	for <ietf-ldapbis@OpenLDAP.org>; Fri, 10 Oct 2003 16:10:15 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from gypsy.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.9/8.12.9) with ESMTP id h9AGAAlg053573;
	Fri, 10 Oct 2003 16:10:11 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.0.22.0.20031010090528.02bb76c8@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
Date: Fri, 10 Oct 2003 09:09:37 -0700
To: Steven Legg <steven.legg@adacel.com.au>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: Steven's protocol comments
Cc: ietf-ldapbis@OpenLDAP.org
In-Reply-To: <3F865925.3020908@adacel.com.au>
References: <5.2.0.9.0.20030919105440.03bcf5d8@127.0.0.1>
 <005d01c38bcd$ba767db0$a518200a@osmium.mtwav.adacel.com.au>
 <6.0.0.22.0.20031008062239.03ac8e60@127.0.0.1>
 <3F865925.3020908@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>

At 12:00 AM 10/10/2003, Steven Legg wrote:
>>And since no great harm is caused by not providing a value
>>(especially given they are rarely used by clients), a
>>SHALL is way too strong.
>
>A "MAY" then ?

I think a good case can be made that support for
feature discovery mechanisms should be RECOMMENDED.

Kurt 



From owner-ietf-ldapbis@OpenLDAP.org  Mon Oct 13 13:52:15 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17309
	for <ldapbis-archive@lists.ietf.org>; Mon, 13 Oct 2003 13:52:12 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9DHXaIY008687;
	Mon, 13 Oct 2003 17:48:55 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9DHVWRK008261;
	Mon, 13 Oct 2003 17:31:32 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 13 Oct 2003 17:31:32 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9DHVIHS008205
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 13 Oct 2003 17:31:18 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from gypsy.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.9/8.12.9) with ESMTP id h9DHVIlg088671
	for <ietf-ldapbis@openldap.org>; Mon, 13 Oct 2003 17:31:18 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.0.22.0.20031013102917.039f73a8@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
Date: Mon, 13 Oct 2003 10:30:41 -0700
To: ietf-ldapbis@OpenLDAP.org
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Summary: WG Last Call: draft-ietf-ldapbis-protocol-17.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>

Due to the large number of issues raised, the chairs have
decided to ask the Editor to produce a revised I-D
to address the numerous issues raised.  The I-D will be
subjected to another WG Last Call review prior to
progression.

Kurt, LDAPbis co-chair



From owner-ietf-ldapbis@OpenLDAP.org  Mon Oct 13 21:56: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 VAA09411
	for <ldapbis-archive@lists.ietf.org>; Mon, 13 Oct 2003 21:56:21 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9E1pVHg050137;
	Tue, 14 Oct 2003 01:54:26 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9E1o8AH050100;
	Tue, 14 Oct 2003 01:50:08 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 14 Oct 2003 01:50:08 +0000
Received: from boole.openldap.org (kurt@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9E1o3HS050084
	for <ietf-ldapbis@openldap.org>; Tue, 14 Oct 2003 01:50:03 GMT
	(envelope-from kurt@boole.openldap.org)
Received: (from kurt@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) id h9E1o3YW050083
	for ietf-ldapbis@openldap.org; Mon, 13 Oct 2003 18:50:03 -0700 (PDT)
	(envelope-from kurt)
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9E1lWHS049826
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 14 Oct 2003 01:47:32 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from gypsy.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.9/8.12.9) with ESMTP id h9E1lWlg094242
	for <ietf-ldapbis@openldap.org>; Tue, 14 Oct 2003 01:47:32 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.0.22.0.20031013182123.03a700e0@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
Date: Mon, 13 Oct 2003 18:46:54 -0700
To: ietf-ldapbis@OpenLDAP.org
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: authmeth: raw review notes
In-Reply-To: <200310140120.h9E1KR3u093994@pretender.boolean.net>
References: <200310140120.h9E1KR3u093994@pretender.boolean.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

Below are my review notes for -07....  a mix of editorial
and technical concerns. 

Kurt

>From draft-ietf-ldapbis-authmeth-07.txt:
> 
> 
>                      LDAP: Authentication Methods 
>                                  and  
>                  Connection Level Security Mechanisms 
> 
>Abstract 
>    
>   This document describes LDAPv3 (Lightweight Directory Access 
>   Protocol v3) authentication methods and connection level security 
>   mechanisms that are required of all conforming LDAPv3 server 
>   implementations and makes recommendations for combinations of these 
>   mechanisms to be used in various deployment circumstances.  
>    

Suggest s/LDAPv3/LDAP/ throughout document for both consistency
within document and across entire technical specification.

>   Among the mechanisms described are 
>      
>     - various forms of authentication including anonymous 
>       authentication, password-based authentication, and certificate 
>       based authentication 
>     - the use of SASL mechanisms with LDAPv3 
>     - the use of TLS (Transport Layer Security) with LDAPv3 
>     - the various authentication and authorization states through 
>       which a connection to an LDAP server may pass and the actions 
>       that trigger these state changes. 

Spell SASL out.  Suggest you use the format
	Transport Layer Security (TLS)
for introducing acronyms.

Suggest this list be replaced with:
  This document details the simple Bind authentication method including
  anonymous, unauthenticated, and plain-text password methods and the
  SASL (Simple Authentication and Security Layer) Bind authentication
  method including the use of DIGEST-MD5 and EXTERNAL mechanisms.
  This document also details establishment of TLS (Transport Layer
  Security) using the Start TLS operation.

Note that we need to be careful when using the term "simple"
authentication choice as the simple authentication choice
supports three modes (two of which produce anonymous associations).
It likely appropriate to define three terms to refer to each of
the modes (maybe in protocol) and then use those terms when
referring to a particular mode of the "simple" authenication choice.
It is import to distinguish anonymous and unauthenticated modes
as servers may allow one but not the other (allowing unauthenticated
bind can be problematic).  (See section 3.2 suggestion.)

>1. Introduction 
    
LDAP and other terms (SASL, TLS, PDU, GSSAPI, DSE) needs to be spelled
out on first use in body (even if introduced in Abstract).

>   This document is an integral part of the LDAP Technical 
>   Specification [ROADMAP]. This document replaces RFC 2829 and 
>   portions of RFC 2830. Changes to RFC 2829 are summarized in Appendix 
>   C and changes to RFC 2830 are summarized in Appendix D. 

I suggest this paragraph be moved to the end of the Introduction.

>   LDAPv3 is a powerful access protocol for directories. It offers 
>   means of searching, retrieving and manipulating directory content, 
>   and ways to access a rich set of security functions. 
> 
>   It is vital that these security functions be interoperable among all 
>   LDAP clients and servers on the Internet; therefore there has to be 
>   a minimum subset of security functions that is common to all 
>   implementations that claim LDAPv3 conformance. 
> 
>   Basic threats to an LDAP directory service include: 
> 
>   (1) Unauthorized access to directory data via data-retrieval 
>       operations, 
> 
>   (2) Unauthorized access to reusable client authentication 
>       information by monitoring others' access, 
> 
>   (3) Unauthorized access to directory data by monitoring others' 
>       access, 
> 
>   (4) Unauthorized modification of directory data, 
> 
>   (5) Unauthorized modification of configuration information, 
>    
>   (6) Unauthorized or excessive use of resources (denial of service), 
>       and 
> 
>   (7) Spoofing of directory: Tricking a client into believing that 
>       information came from the directory when in fact it did not, 
>       either by modifying data in transit or misdirecting the client's 
>       connection. Also, tricking a client into sending privileged 
>       information to a hostile entity that appears to be the directory 
>       but is not. 
> 
>   Threats (1), (4), (5) and (6) are due to hostile clients. Threats 
>   (2), (3) and (7) are due to hostile agents on the path between 
>   client and server or hostile agents posing as a server. 
> 
>   The LDAP protocol suite can be protected with the following security 
>   mechanisms: 

s/protocol suite//  (the P in LDAP stands for Protocol and suite is
meaningless in this context)

>   (1) Client authentication by means of the SASL [SASL] mechanism set, 
>       possibly backed by the TLS [RFC2246] credentials exchange 
>       mechanism, 
> 
>   (2) Client authorization by means of access control based on the 
>       requestor's authenticated identity, 
> 
>   (3) Data integrity protection by means of the TLS protocol or SASL 
>       mechanisms that provide data integrity services, 
>
> 
>   (4) Data confidentiality protection against snooping by means of the 
>       TLS protocol or SASL mechanisms that provide data 
>       confidentiality services, 
>
>   (5) Server resource usage limitation by means of administrative 
>       service limits configured on the server, and 
> 
>   (6) Server authentication by means of the TLS protocol or SASL 
>       mechanism. 
> 
>   At the moment, imposition of access controls is done by means 
>   outside the scope of the LDAPv3 protocol. 
>    
>   It seems clear that allowing any implementation, faced with the 
>   above requirements, to simply pick and choose among the possible 
>   alternatives is not a strategy that is likely to lead to 
>   interoperability. In the absence of mandates, clients will be 
>   written that do not support any security function supported by the 
>   server, or worse, they will support only mechanisms like the LDAPv3 
>   simple bind using clear text passwords that provide inadequate 
>   security for most circumstances. 
> 
>   Given the presence of the Directory, there is a strong desire to see 
>   mechanisms where identities take the form of an LDAP distinguished 
>   name [LDAPDN] and authentication data can be stored in the 
>   directory.  This means that this data must be updated outside the 
>   protocol or only updated in sessions well protected against 
>   snooping. It is also desirable to allow authentication methods to 
>   carry authorization identities based on existing--non-LDAP DN--forms 
>   of user identities for backwards compatibility with non-LDAP-based 
>   authentication services. 
>    
>   The set of security mechanisms provided in LDAPv3 and described in 
>   this document is intended to meet the security needs for a wide 
>   range of deployment scenarios and still provide a high degree of 
>   interoperability among various LDAPv3 implementations and 
>   deployments. Appendix A contains example deployment scenarios that 
>   list the mechanisms that might be used to achieve a reasonable level 
>   of security in various circumstances. 
> 
>2. Conventions Used in this Document 
>    
>2.1. Glossary of Terms 
>    
>   The following terms are used in this document. To aid the reader, 
>   these terms are defined here. 
>    
>     - "user" represents any application which is an LDAP client using 
>       the directory to retrieve or store information. 

A couple of problems with this definition of user.  Aside from the
confusing use of "application" here, this basically equates "user"
with "client".   Given this definition, what does "user-oriented client"
mean.

I think it would be better to define "user" as follows

	The human or application entity which is accessing the directory
	using a directory client.  A directory client (or client) is
    also known as a directory user agent (DUA).

>     - "connection" and "LDAP connection" both refer to the underlying 
>       transport protocol connection between two protocol peers.  
>      
>     - "TLS connection" refers to a TLS-protected LDAP connection.  
>      
>     - "association" and "LDAP association" both refer to the 
>       association of the LDAP connection and its current 
>       authentication and authorization state. 
>    
>2.2. Security Terms and Concepts 
>    
>   In general, security terms in this document are used consistently 
>   with the definitions provided in [RFC2828]. In addition, several 
>   terms and concepts relating to security, authentication, and 
>   authorization are presented in Appendix B of this document. While 
>   the formal definition of these terms and concepts is outside the 
>   scope of this document, an understanding of them is prerequisite to 
>   understanding much of the material in this document. Readers who are 
>   unfamiliar with security-related concepts are encouraged to review 
>   Appendix B before reading the remainder of this document. 
> 
>2.3. Keywords 
>    
>   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 
>   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 
>   document are to be interpreted as described in RFC 2119 [RFC2119]. 
> 
>3. Bind Operation 
>     
>   The Bind operation defined in section 4.2 of [Protocol] allows 
>   authentication information to be exchanged between the client and 
>   server.  
>    
>3.1. Unbound Connection Treated as Anonymous ("Implied Anonymous Bind") 
>    
>   Unlike LDAP version 2, the client need not send a Bind Request in 
>   the first PDU of the connection. The client may send any operation 
>   request prior to binding, and the server MUST treat it as if it had 
>   been performed after an anonymous bind operation.  If the server 
>   requires that the client bind before browsing or modifying the 
>   directory, the server MAY reject a request other than binding, 
>   unbinding or an extended request with the "operationsError" result. 

(note: don't wrap result codes with quotes... they aren't strings.)

I have a number of concerns with how this statement is worded.
	- An "unbound connection" is a confusing term as a "bound"
	can mean "established".
    - server may reject most extended requests with operationsError
	when issued prior to the bind operation.
	- protocol issues should be left to [Protocol]. 

I suggest merging the section into the parent section and
replacing the paragraph (that is, this would become the second
paragraph of section 3).

	The Bind Operation is used to establish a new LDAP association.
	The new LDAP association is established upon successful
	completion of the authentication exchange.  During any
	authentication exchange and prior to the successful completion
	of first operation, the sesssion has an anonymous LDAP
	association.

(leaving protocol issues (e.g., operationsError) to [Protocol]).

>3.2. Simple Authentication  
>    
>   The simple authentication option provides minimal authentication 
>   facilities, with the contents of the authentication field consisting 
>   only of a cleartext password.

s/option/choice/
Also needs to expanded to discuss different simple authentication
modes.

	The simple authentication choice provides minimal facilities
	for establishing an anonymous association or for establishing an
    LDAP association based upon creditials consisting of a name (in the
    form of a DN) and a password.

	The simple authentication choice provides two different methods
	for establishing an anonymous association: anonymous simple
    bind (or anonymous bind) and unauthenticated simple bind (or
	unauthenticated bind).

	The simple authentication choice provides one method for establishing
	a non-anonymous association: simple password bind.

>   Note that the use of cleartext 
>   passwords is strongly discouraged over open networks when the 
>   underlying transport service cannot guarantee confidentiality (see 
>   section 8).  

>3.3. SASL Authentication Profile 
>    
>   LDAP allows authentication via any SASL mechanism [SASL]. As LDAP 
>   includes native anonymous and plaintext authentication methods, the 
>   "ANONYMOUS" [ANONYMOUS] and "PLAIN" [PLAIN] SASL mechanisms are 
>   typically not used with LDAP. 
> 
>   Each protocol that utilizes SASL services is required to supply 
>   certain information profiling the way they are exposed through the 
>   protocol ([SASL] section 5). This section explains how each of these 
>   profiling requirements are met by LDAPv3. 
>    
>3.3.1. SASL Service Name for LDAP 
> 
>   The SASL service name for LDAPv3 is "ldap", which has been 
>   registered with the IANA as a GSSAPI service name. 

We need to request IANA update the GSSAPI service name registry
to point to [ROADMAP] and this document.  Suggest this be addressed
in the IANA Considerations section of this document.

>3.3.2. SASL authentication initiation and protocol exchange 
>    
>   SASL authentication is initiated via an LDAP bind request 
>   ([Protocol] section 4.2) with the following parameters: 
>    
>      - The version is 3. 
>      - The AuthenticationChoice is sasl.  
>      - The mechanism element of the SaslCredentials sequence contains 
>        the value of the desired SASL mechanism.  
>      - The optional credentials field of of the SaslCredentials 

s/of of/of/
>        sequence may be used to provide an initial client response for 
>        mechanisms that are defined to have the client send data first 
>        (see [SASL] sections 5 and 6.1). 
>    
>   In general, a SASL authentication protocol exchange consists of a 
>   series of server challenges and client responses, the contents of 

I think the word "protocol" can be dropped here.

>   which are specific to and defined by the SASL mechanism. Thus for 
>   some SASL authentication mechanisms, it may be necessary for the 
>   client to respond to one or more server challenges by invoking the 
>   BindRequest multiple times. A challenge is indicated by the server 
>   sending a BindResponse with the resultCode set to 
>   saslBindInProgress. This indicates that the server requires the 
>   client to send a new bind request, with the same sasl mechanism to 
>   continue the authentication process. 
>
>   To the encapsulating protocol, these challenges and responses are 
>   opaque binary tokens of arbitrary length. LDAP servers use the 
>   serverSaslCreds field, an OCTET STRING, in a bind response message 
>   to transmit each challenge. LDAP clients use the credentials field, 
>   an OCTET STRING, in the SaslCredentials sequence of a bind request 
>   message to transmit each response. Note that unlike some Internet 
>   application protocols where SASL is used, LDAP is not text-based, 
>   thus no Base64 transformations are performed on these challenge and 
>   response values. 
>    
>   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. 
>    
>   A client may abort a SASL bind negotiation by sending a BindRequest 
>   with a different value in the mechanism field of SaslCredentials, or 
>   an AuthenticationChoice other than sasl.  
>        
>   If the client sends a BindRequest with the sasl mechanism field as 
>   an empty string, the server MUST return a BindResponse with 
>   authMethodNotSuppored as the resultCode. This will allow clients to 
>   abort a negotiation if it wishes to try again with the same SASL 
>   mechanism. 
>    
>   The server indicates completion of the SASL challenge-response 
>   exchange  by responding with a bind response in which the resultCode 
>   is either success, or an error indication. 

s/exchange  by/exchange by/  (remove extra space)

>   The serverSaslCreds field in the bind response can be used to 
>   include an optional challenge with a success notification for 
>   mechanisms which are defined to have the server send additional data 
>   along with the indication of successful completion. 
> 
>3.3.3. Octet where negotiated security mechanisms take effect 
>    
>   If any SASL-based integrity or confidentiality services are enabled, 
>   they take effect following the transmission by the server and 
>   reception by the client of the final BindResponse with a resultCode 
>   of success.  

s/integrity or confidentiality services/security layers/

I suggest this be reworded
	When negotiated, SASL security layers take effect following the
	transmission by the server and reception by the client of the
	final BindResponse in the exchange.

>3.3.4. Determination of supported SASL mechanisms 
>    
>   An LDAP client may determine the SASL mechanisms a server supports 
>   by performing a search request on the root DSE, requesting the 
>   supportedSASLMechanisms attribute. The values of this attribute, if 
>   any, list the mechanisms the server supports. 

Add note (or reference) here regarding checking supportedSASLMechanisms
post-bind to prevent downgrade attacks.
 
>3.3.5. Rules for using SASL security layers 
>    
>   If a SASL security layer is negotiated, the client MUST discard all 
>   information about the server fetched prior to the initiation of the 
>   SASL negotiation.

Too strong: I suggest SHOULD instead of MUST because a client,
understanding the implications of not doing so, should be allowed
not to discard certain infornmation fetched prior to the initiation.
In fact, how could the client compare before/after advertised SASL
mechanisms (and other features) if it was required to discard the
before information prior to the check.

Too broad: this mandates that information obtained in a secure
information be discarded.  There is no good reason to mandate this.
Suggest "all" be replaced with "information not otherwise secured"
or something.  Without this, this requirement could be viewed as
requiring implementations to discard information (such as identity
information learned through secure lower-level mechanisms).

>   If the client is configured to support multiple 
>   SASL mechanisms, it SHOULD fetch the supportedSASLmechanisms list 
>   both before and after the SASL security layer is negotiated. This 
>   allows the client to detect active attacks that remove supported 
>   SASL mechanisms from the supportedSASLMechanisms list and allows the 
>   client to ensure that it is using the best mechanism supported by 
>   both client and server. (This requirement is a SHOULD to allow for 
>   environments where the supportedSASLMechanisms list is provided to 
>   the client through a different trusted source, e.g. as part of a 
>   digitally signed object.) 

>   If a lower level security layer (such as TLS) is negotiated, any 
>   SASL security services SHALL be layered on top of such security 
>   layers regardless of the order of their negotiation. 
> 
>3.3.6. Use of EXTERNAL SASL Mechanism 
>    
>   A client can use the "EXTERNAL" SASL mechanism to request the LDAP 
>   server to make use of security credentials exchanged by a lower 
>   layer. If a TLS session has not been established between the client 
>   and server prior to making the SASL EXTERNAL Bind request and there 
>   is no other external source of authentication credentials (e.g. IP-
>   level security [RFC2401]), or if during the process of establishing 
>   the TLS session, the server did not request the client's 
>   authentication credentials, the SASL EXTERNAL bind MUST fail with a 
>   resultCode of inappropriateAuthentication.

This should be more simply worded:
	If authentication creditials have not been established at a lower-level
	(such as by TLS authentication), the SASL EXTERNAL bind MUST fail
	with a resultCode of inapprorpiateAuthentication.

>   Any client authentication 
>   and authorization state of the LDAP association is lost, so the LDAP 
>   association is in an anonymous state after the failure (see 
>   [Protocol] section 4.2.1). 


>3.4. SASL Authorization Identity 
> 
>   The authorization identity is carried as part of the SaslCredentials 
>   credentials field in the Bind request and response. 

Some mechanisms don't support authorization identities.
 
>   When the "EXTERNAL" SASL mechanism is being negotiated, if the 
>   credentials field is present, it contains an authorization identity 
>   of the authzId form described below. 

Delete "of the ..." here and (see below)
> 
>   Other mechanisms define the location of the authorization identity 
>   in the credentials field. 

add:
	In either case, the authorization identity is represented
	in the authzId form described below.

>3.4.1. Authorization Identity Syntax 
>    
>   The authorization identity is a string in the UTF-8 character set,  
>   corresponding to the following ABNF grammar [RFC2234]: 

s/in the UTF-8 character set/of [UTF-8] encoded [Unicode] characters/

>   ; Specific predefined authorization (authz) id schemes are 
>   ; defined below -- new schemes may be defined in the future. 
> 
>   authzId = dnAuthzId / uAuthzId 
> 
>   DNCOLON  = %x64 %x6e %x3a ; "dn:" 
>   UCOLON = %x75 %x3a ; "u:" 
>    
>   ; distinguished-name-based authz id. 
>   dnAuthzId = DNCOLON dn 
>   dn = utf8string    ; with syntax defined in [LDAPDN] section 3. 
> 
>   ; unspecified authorization id, UTF-8 encoded. 
> 
>   uAuthzId = UCOLON userid 
>   userid = utf8string    ; syntax unspecified 
>    
>   The dnAuthzId choice allows client applications to assert 
>   authorization identities in the form of a distinguished name.

add "to be matched in accordance with the distinguishedName
matching rule [Syntaxes]."

>  The 
>   decision to allow or disallow an authentication identity to have 
>   access to the requested authorization identity is a matter of local 
>   policy ([SASL] section 4.2). For this reason there is no requirement 
>   that the asserted dn be that of an entry in directory. 
>    
>   The uAuthzId choice allows for compatibility with client 
>   applications that wish to assert an authorization identity to a 
>   local directory but do not have that identity in distinguished name 
>   form. The format of utf8string is defined as only a sequence of UTF-
>   8 encoded ISO 10646 characters, and further interpretation is 
>   subject to prior agreement between the client and server. 

We need to say how two uAuthzIds are to be compared.  In particular,
we should require uAuthzIds be prepared using SASLprep before being
compared octet-wise.
 
>   For example, the userid could identify a user of a specific 
>   directory service, or be a login name or the local-part of an RFC 
>   822 email address. In general, a uAuthzId MUST NOT be assumed to be 
>   globally unique. 

The "in general" qualification to a MUST NOT implies that the MUST
NOT can be ignored in some cases.  Suggest dropping the "in general"
and s/MUST NOT/SHOULD NOT/.

>   Additional authorization identity schemes MAY be defined in future 
>   versions of this document. 

s/MAY/may/

>3.5. SASL Integrity and Privacy Protections 

It would be better to use the term "security layers" here.
SASL securary layers can offer a wide range of protective
services.

>   Any negotiated SASL integrity and privacy protections SHALL start on 
>   the first octet of the first LDAP PDU following successful 
>   completion of the SASL bind operation. If lower level security layer 
>   is negotiated, such as TLS, any SASL security services SHALL be 
>   layered on top of such security layers regardless of the order of 
>   their negotiation. 
> 
>4. Start TLS Operation 
>    
>   The Start Transport Layer Security (StartTLS) operation defined in 
>   section 4.13 of [Protocol] provides the ability to establish 
>   Transport Layer Security [RFC2246] on an LDAP association. 

Update the TLS reference to refer to draft-ietf-tls-rfc2246-bis-xx.txt.

>4.1. Sequencing of the Start TLS Operation 
> 
>   This section describes the overall procedures clients and servers 
>   must follow for TLS establishment. These procedures take into 
>   consideration various aspects of the overall security of the LDAP 
>   association including discovery of resultant security level and 
>   assertion of the client's authorization identity. 
> 
>   Note that the precise effects, on a client's authorization identity, 
>   of establishing TLS on an LDAP association are described in detail 
>   in section 4.2. 
> 
>4.1.1. Requesting to Start TLS on an LDAP Association 

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

Suggest:
	The client may send the Start TLS request at any time after establishing
	the LDAP connection except:
		- when TLS is currently established on the connection,
		- when a multi-stage SASL negotiation is in progress on the connection, or
		- when there are one or more outstanding LDAP operations on the connection.

(Note the downcasing of the MAY and removal of the MUST.  The MUST is
removed because servers are required to handle these cases.)

>   The result of violating any of these requirements is a resultCode of 
>   operationsError, as described in [Protocol] section 4.13.2.2. Client 
>   implementers should note that it is possible to get back a 
>   resultCode of success in the case where LDAP operations are 
>   outstanding on the connection at the time a Start TLS operation 
>   request is sent by the client but they are processed by the server 
>   prior to its receiving the Start TLS request from the client. 
>   Implementors should ensure that they do not inadvertently depend 
>   upon this race condition for proper functioning of their 
>   applications. 

I think the last two sentences need to be reworded a bit. I'll offer
text later (after I think about it a bit).

>   In particular, there is no requirement that the client have or have 
>   not already performed a Bind operation before sending a Start TLS 
>   operation request. The client may have already performed a Bind 
>   operation when it sends a Start TLS request, or the client might 
>   have not yet bound. 
>    
>   If the client did not establish a TLS connection before sending any 
>   other requests, and the server requires the client to establish a 
>   TLS connection before performing a particular request, the server 
>   MUST reject that request by sending a resultCode of 
>   confidentialityRequired or strongAuthRequired. In response, the 
>   client MAY send a Start TLS extended request, or it MAY choose to 
>   close the connection. 

Or issue other requests (such as issue SASL bind request).

I think the sentence can be deleted.

>4.1.2. Starting TLS 
> 
>   The server will return an extended response with the resultCode of 
>   success if it is willing and able to negotiate TLS.  It will return 
>   other resultCodes (documented in [Protocol] section 4.13.2.2) if it 
>   is unable to do so. 
>    
>   In the successful case, the client (which has ceased to transfer 
>   LDAP requests on the connection) MUST either begin a TLS negotiation 
>   or close the connection. The client will send PDUs in the TLS Record 
>   Protocol directly over the underlying transport connection to the 
>   server to initiate TLS negotiation [RFC2246]. 

Likely should state server requirements here as well.

> 
>4.1.3. TLS Version Negotiation 
> 
>   Negotiating the version of TLS or SSL to be used is a part of the 
>   TLS Handshake Protocol, as documented in [RFC2246]. Please refer to 
>   that document for details. 
> 
>4.1.4. Discovery of Resultant Security Level 
> 
>   After a TLS connection is established on an LDAP association, both 
>   parties MUST individually decide whether or not to continue based on 
>   the privacy level achieved. Ascertaining the TLS connection's 
>   privacy level is implementation dependent, and accomplished by 
>   communicating with one's respective local TLS implementation. 

s/privacy/security/

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

s/privacy/security level/

>   If the client decides to continue, it MAY gracefully close the TLS 
>   connection and attempt to Start TLS again, it MAY send an unbind 
>   request, or it MAY send any other LDAP request. 

s/MAY/may/
 
>4.1.5. Assertion of Client's Authorization Identity 
> 
>   The client MAY, upon receipt of a Start TLS response indicating 
>   success, assert that a specific authorization identity be utilized 
>   in determining the client's authorization status. The client 
>   accomplishes this via an LDAP Bind request specifying a SASL 
>   mechanism of "EXTERNAL" [SASL] (see section 4.2.2 below). 

This section seems redundant with information in 4.2.

>4.1.6. Server Identity Check 
> 
>   The client MUST check its understanding of the server's hostname 
>   against the server's identity as presented in the server's 
>   Certificate message in order to prevent man-in-the-middle attacks. 
> 
>   Matching is performed according to these rules: 
>    
>     - The client MUST use the server hostname it used to open the LDAP 
>       connection as the value to compare against the server name as 
>       expressed in the server's certificate.  The client MUST NOT use 
>       any other derived form of name (including that derived by DNS 
>       canonicalization). 
>    
>     - If a subjectAltName extension of type dNSName is present in the 
>       certificate, it SHOULD be used as the source of the server's 
>       identity. 
>    
>     - Matching is case-insensitive. 
>    
>     - The "*" wildcard character is allowed.  If present, it applies 
>       only to the left-most name component. 
>    
>       For example, *.bar.com would match a.bar.com and b.bar.com, but 
>       it would not match a.x.bar.com nor would it match bar.com.  If 
>       more than one identity of a given type is present in the 
>       certificate (e.g. more than one dNSName name), a match in any 
>       one of the set is considered acceptable. 
>    
>   If the hostname does not match the dNSName-based identity in the 
>   certificate per the above check, user-oriented clients SHOULD either 
>   notify the user (clients MAY give the user the opportunity to 
>   continue with the connection in any case) or terminate the 
>   connection and indicate that the server's identity is suspect. 

s/MAY/may/

>   Automated clients SHOULD close the connection, returning and/or 
>   logging an error indicating that the server's identity is suspect. 


>   Beyond the server identity checks described in this section, clients 
>   SHOULD be prepared to do further checking to ensure that the server 
>   is authorized to provide the service it is observed to provide. The 
>   client MAY need to make use of local policy information. 

s/MAY/may/
 
>4.1.7. Refresh of Server Capabilities Information 
> 
>   Upon TLS session establishment, the client MUST discard all 
>   information about the server fetched prior to the initiation of the 
>   TLS negotiation and MUST refresh any cached server capabilities 
>   information (e.g. from the server's root DSE; see [Model] section 
>   5.1). This is necessary to protect against active-intermediary 
>   attacks that may have altered any server capabilities information 
>   retrieved prior to TLS establishment.  

See 3.3.5 comments.

>   The server MAY advertise different capabilities after TLS 
>   establishment. In particular, the value of supportedSASLMechanisms 
>   MAY be different after TLS has been negotiated (specifically, the 
>   EXTERNAL and PLAIN [PLAIN] mechanisms are likely to be listed only 
>   after a TLS negotiation has been performed). 

s/MAY/may/ (in both cases)   That way, the sentences imply the need
for clients to deal with the case where different capabilities are
published.  Otherwise, these sentences imply that the differences
don't matter (as MAY implies a "truly optional" feature).
 
>4.2. Effects of TLS on a Client's Authorization Identity 
> 
>   This section describes the effects on a client's authorization 
>   identity brought about by establishing TLS on an LDAP association. 
>   The default effects are described first, and next the facilities for 
>   client assertion of authorization identity are discussed including 
>   error conditions. Finally, the effects of closing the TLS connection 
>   are described. 
> 
>   Authorization identities and related concepts are described in 
>   Appendix B. 
> 
>4.2.1. Default Effects 
>    
>   Upon establishment of the TLS session onto the LDAP association, any 
>   previously established authentication and authorization identities 
>   MUST remain in force, including anonymous state. This holds even in 
>   the case where the server requests client authentication via TLS -- 
>   e.g. requests the client to supply its certificate during TLS 
>   negotiation (see [RFC2246]). 

This MUST does not take into consider the servers right to change
the LDAP association.   That is, a server could return an appropriate
error code (such as strongAuthRequired) for all operations subsequent
to the Start TLS indicating that it consider the previously establish
LDAP association inappropriate.   As the protocol provides a mechanism
for the server to indicate to the client that the previous LDAP
association is inadequate, we've covered the key interoperability
concerns and, hence, the MUST is not needed.   I think a SHOULD with
note would be more appropriate.  The note would include (or reference)
a discussion of how servers indicate invalidated associations).

>4.2.2. Client Assertion of Authorization Identity 
>    
>   A client MAY either implicitly request that its LDAP authorization 
>   identity be derived from its authenticated TLS credentials or it MAY 
>   explicitly provide an authorization identity and assert that it be 
>   used in combination with its authenticated TLS credentials. The 
>   former is known as an implicit assertion, and the latter as an 
>   explicit assertion. 

First, s/MAY/may in both cases above.

Second, note that the client cannot assume the server uses TLS
established creditials to derive or otherwise establish the
LDAP association.  EXTERNAL means the server is to use lower-level
creditials in establishing the LDAP association.  The server can
use those provided by any lower layer.  From a protocol interoperability
point of view, it doesn't matter which.  The server just says "yea"
or "nay."

>4.2.2.1. Implicit Assertion 
>    
>   An implicit authorization identity assertion is accomplished after 
>   TLS establishment by invoking a Bind request of the SASL form using 
>   the "EXTERNAL" mechanism name [SASL] [Protocol] that SHALL NOT 
>   include the optional credentials octet string (found within the 
>   SaslCredentials sequence in the Bind Request).

s/SASL form/sasl choice [Protocol]/ and s/[SASL] [Protocol]/[SASL]/

>   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. 
>    
>4.2.2.2. Explicit Assertion 
>    
>   An explicit authorization identity assertion is accomplished after 
>   TLS establishment by invoking a Bind request of the SASL form using 
>   the "EXTERNAL" mechanism name [SASL] [Protocol] that SHALL include 
>   the credentials octet string. This string MUST be constructed as 
>   documented in section 3.4.1. 
>    
>   The server MUST verify that the client's authentication identity as 
>   supplied in its TLS credentials is permitted to be mapped to the 
>   asserted authorization identity. The server MUST reject the Bind 
>   operation with an invalidCredentials resultCode in the Bind response 
>   if the client is not so authorized. 
>    
>4.2.2.3. Error Conditions 
>    
>   Additionally, with either form of assertion, if a TLS session has 
>   not been established between the client and server prior to making 
>   the SASL EXTERNAL Bind request and there is no other external source 
>   of authentication credentials (e.g. IP-level security [RFC2401]), or 
>   if during the process of establishing the TLS session, the server 
>   did not request the client's authentication credentials, the SASL 
>   EXTERNAL bind MUST fail with a result code of 
>   inappropriateAuthentication. 

redundant with 3.3.6.
    
>   After the above Bind operation failures, any client authentication 
>   and authorization state of the LDAP association is lost (see 
>   [Protocol] section 4.2.1), so the LDAP association is in an 
>   anonymous state after the failure.  The TLS session state is 
>   unaffected, though a server MAY end the TLS session, via a TLS 
>   close_notify message, based on the Bind failure (as it MAY at any 
>   time). 
>    
>4.2.3. TLS Connection Closure Effects 
>    
>   Closure of the TLS session MUST cause the LDAP association to move 
>   to an anonymous authentication and authorization state regardless of 
>   the state established over TLS and regardless of the authentication 
>   and authorization state prior to TLS session establishment. 
> 
>    
>5. LDAP Association State Transition Tables 

I still need to review this table.  When I was reviewing Jeff's orginals,
I found it easier to separate TLS state from the LDAP association state.
This separation, I think, is good because EXTERNAL doesn't necessarily
rely on TLS state.

>   To comprehensively diagram the various authentication and TLS states 
>   through which an LDAP association may pass, this section provides a 
>   state transition table to represent a state diagram for the various 
>   states through which an LDAP association may pass during the course 
>   of its existence and the actions that cause these changes in state. 
>    
>5.1. LDAP Association States 
>    
>   The following table lists the valid LDAP association states and 
>   provides a description of each state. The ID for each state is used 
>   in the state transition table in section 5.4. 
> 
>   ID State Description 
>   -- -------------------------------------------------------------- 
>   S1 Anonymous 
>       no Authentication  ID is associated with the LDAP connection 
>       no Authorization ID is in force 
>       No security layer is in effect. 
>       No TLS credentials have been provided 
>       TLS: no Creds, OFF] 
>   S2 no Auth ID 
>       no AuthZ ID 
>       [TLS: no Creds, ON] 
>   S3 no Auth ID 
>       no AuthZ ID 
>       [TLS: Creds Auth ID "I", ON] 
>   S4 Auth ID = Xn 
>       AuthZ ID= Y 
>       [TLS: no Creds, OFF] 
>   S5 Auth ID = Xn 
>       AuthZ ID= Yn 
>       [TLS: no Creds, ON] 
>   S6 Auth ID = Xn 
>       AuthZ ID= Yn 
>       [TLS: Creds Auth ID "I", ON] 
>   S7 Auth ID = I 
>       AuthZ ID= J 
>       [TLS: Creds Auth ID "I", ON] 
>   S8 Auth ID = I 
>       AuthZ ID= K 
>       [TLS: Creds Auth ID "I", ON] 
> 
>5.2. Actions that Affect LDAP Association State 
>    
>   The following table lists the actions that can affect the state of 
>   an LDAP association. The ID for each action is used in the state 
>   transition table in section 5.4. 
>    
>   ID Action 
>
> 
> 
>   -- ------------------------------------------------ 
>   A1 Client binds anonymously 
>   A2 Inappropriate authentication: client attempts an anonymous 
>       bind or a bind without supplying credentials to a server that 
>       requires the client to provide some form of credentials. 
>   A3 Client Start TLS request 
>       Server: client auth NOT required 
>   A4 Client: Start TLS request 
>       Server: client creds requested 
>       Client: [TLS creds: Auth ID "I"] 
>   A5 Client or Server: send TLS closure alert ([Protocol] section 
>       X) 
>   A6 Client: Bind w/simple password or SASL mechanism (e.g. DIGEST-
>       MD5 password, Kerberos, etc., except EXTERNAL [Auth ID "X" 
>       maps to AuthZ ID "Y"] 
>   A7 Client Binds SASL EXTERNAL with credentials: AuthZ ID "J" 
>       [Explicit Assertion (section 4.2.1.2.2)] 
>   A8 Client Bind SASL EXTERNAL without credentials [Implicit 
>       Assertion (section 4.2.1.2.1)] 
>   A9 Client abandons a bind operation or bind operation fails 
>                                                  
>5.3. Decisions Used in Making LDAP Association State Changes 
>    
>   Certain changes in the state of an LDAP association are only allowed 
>   if the server can affirmatively answer a question. These questions 
>   are applied as part of the criteria for allowing or disallowing a 
>   state change in the state transition table in section 5.4.  
> 
>   ID Decision Question 
>   -- -------------------------------------------------------------- 
>   D1 Can TLS Credentials Auth ID "I" be mapped to AuthZ ID "J"? 
>   D2 Can a valid AuthZ ID "K" be derived from TLS Credentials Auth 
>       ID "I"? 
> 
>5.4. LDAP Association State Transition Table 
>    
>   The LDAP Association table below lists the valid states for an LDAP 
>   association and the actions that could affect them. For any given 
>   row in the table, the Current State column gives the state of an 
>   LDAP association, the Action column gives an action that could 
>   affect the state of an LDAP assocation, and the Next State column 
>   gives the resulting state of an LDAP association after the action 
>   occurs. 
>    
>   The initial state for the state machine described in this table is 
>   S1. 
> 
>   Current                 Next   
>    State  Action         State Comment 
>   ------- -------------  ----- ----------------------------------- 
>      S1    A1              S1    
>      S1    A2              S1   Error: Inappropriate authentication 
>      S1    A3              S2    
> 
> 
>      S1    A4              S3    
>      S1    A6              S4    
>      S1    A7               ?   identity could be provided by 
>                                  another underlying mechanism such 
>                                  as IPSec. 
>      S1    A8               ?   identity could be provided by 
>                                  another underlying mechanism such 
>                                  as IPSec. 
>      S2    A1              S2    
>      S2    A2              S2   Error: Inappropriate authentication 
>      S2    A5              S1    
>      S2    A6              S5    
>      S2    A7               ?   identity could be provided by 
>                                  another underlying mechanism such 
>                                  as IPSec. 
>      S2    A8               ?   identity could be provided by 
>                                  another underlying mechanism such 
>                                  as IPSec. 
>      S3    A1              S3    
>      S3    A2              S3   Error: Inappropriate authentication 
>      S3    A5              S1    
>      S3    A6              S6    
>      S3    A7 and D1=NO    S3   Error: InvalidCredentials 
>      S3    A7 and D1=YES   S7    
>      S3    A8 and D2=NO    S3   Error: InvalidCredentials 
>      S3    A8 and D2=YES   S8    
>      S4    A1              S1    
>      S4    A2              S1   Error: Inappropriate Authentication 
>      S4    A3              S5    
>      S4    A4              S6    
>      S4    A5              S1    
>      S4    A6              S4    
>      S4    A7               ?   identity could be provided by 
>                                  another underlying mechanism such 
>                                  as IPSec. 
>      S4    A8               ?   identity could be provided by 
>                                  another underlying mechanism such 
>                                  as IPSec. 
>      S5    A1              S2    
>      S5    A2              S2   Error: Inappropriate Authentication 
>      S5    A5              S1    
>      S5    A6              S5    
>      S5    A7               ?   identity could be provided by 
>                                  another underlying mechanism such 
>                                  as IPSec. 
>      S5    A8               ?   identity could be provided by 
>                                  another underlying mechanism such 
>                                  as IPSec. 
>      S6    A1              S3    
>      S6    A2              S2   Error: Inappropriate Authentication 
>      S6    A5              S1    
>      S6    A6              S6    
> 
> 
>      S6    A7 and D1=NO    S6   Error: InvalidCredentials 
>      S6    A7 and D1=YES   S7    
>      S6    A8 and D2=NO    S3   Error: InvalidCredentials 
>      S6    A8 and D2=YES   S8    
>      S7    A1              S3    
>      S7    A2              S2   Error: Inappropriate Authentication 
>      S7    A5              S1    
>      S7    A6              S6    
>      S7    A7              S7    
>      S7    A8 and D2=NO    S3   Error: InvalidCredentials 
>      S7    A8 and D2=YES   S8    
>      S8    A1              S3    
>      S8    A2              S2   Error: Inappropriate Authentication 
>      S8    A5              S1    
>      S8    A6              S6    
>      S8    A7 and D1=NO    S6   Error: InvalidCredentials 
>      S8    A7 and D1=YES   S7    
>      S8    A8              S8    
>     Any   A9              S1   See [Protocol] section 4.2.1. 
> 
> 
>6. Anonymous Authentication 
> 
>   Directory operations that modify entries or access protected 
>   attributes or entries generally require client authentication. 
>   Clients that do not intend to perform any of these operations 
>   typically use anonymous authentication. Servers SHOULD NOT allow 
>   clients with anonymous authentication to modify directory entries or 
>   access sensitive information in directory entries. 
> 
>   LDAP implementations MUST support anonymous authentication, as 
>   defined in section 6.1. 

I think this should be a SHOULD.  A client which only implements
DIGEST-MD5 authentication should be considered fully compliant.
Otherwise, we're requiring clients which only need to implement
DIGEST-MD5 (say because they update the directory) to implement
anonymous authentication.

Now, I think server implementations MUST support anonymous authentication.

>   LDAP implementations MAY support anonymous authentication with TLS, 
>   as defined in section 6.2. 
> 
>   While there MAY be access control restrictions to prevent access to 
>   directory entries, an LDAP server SHOULD allow an anonymously-bound 
>   client to retrieve the supportedSASLMechanisms attribute of the root 
>   DSE. 
> 
>   An LDAP server MAY use other information about the client provided 
>   by the lower layers or external means to grant or deny access even 
>   to anonymously authenticated clients. 

s/even//

>6.1. Anonymous Authentication Procedure 
> 
>   An LDAPv3 client that has not successfully completed a bind 
>   operation on a connection is anonymously authenticated. See section 
>   3.1. 
> 
>   An LDAP client MAY also choose to explicitly bind anonymously. A 
>   client that wishes to do so MUST choose the simple authentication 
>   option in the Bind Request and set the password to be of zero 
>   length. (This is often done by LDAPv2 clients.) Typically the name 
>   is also of zero length.  

I think we also need to RECOMMEND the name to be zero length.
A non-zero length name with empty password is considered an
unauthenticated bind.  The server may treat these differently
than anonymous binds.

>6.2. Anonymous Authentication and TLS 
> 
>   An LDAP client MAY use the Start TLS operation (section 5) to 
>   negotiate the use of TLS security [RFC2246]. If the client has not 
>   bound beforehand, then until the client uses the EXTERNAL SASL 
>   mechanism to negotiate the recognition of the client's certificate, 
>   the client is anonymously authenticated. 
> 
>   Recommendations on TLS ciphersuites are given in section 9. 
> 
>   An LDAP server which requests that clients provide their certificate 
>   during TLS negotiation MAY use a local security policy to determine 
>   whether to successfully complete TLS negotiation if the client did 
>   not present a certificate which could be validated. 
> 
>7. Password-based Authentication 
>    
>   This section discusses various options for performing password-based 
>   authentication to LDAPv3 compliant servers and the environments 
>   suitable for their use. 
> 
>7.1. Simple Authentication 
> 
>   The LDAP "simple" authentication choice is not suitable for 
>   authentication in environments where there is no network or 
>   transport layer confidentiality.  LDAP implementations SHOULD support 
>   authentication with the "simple" authentication choice when the 
>   connection is protected against eavesdropping using TLS, as defined 
>   in section 4. LDAP implementations SHOULD NOT support authentication 
>   with the "simple" authentication choice unless the data on the 
>   connection is protected using TLS or other data confidentiality and 
>   data integrity protection. 
> 
>7.2. Digest Authentication 
>    
>   LDAP servers that implement any authentication method or mechanism 
>   (other than simple anonymous bind) MUST implement the SASL 
>   DIGEST-MD5 mechanism [DigestAuth]. 
>    
>   Support for subsequent authentication is OPTIONAL in clients and 
>   servers. 
>    
>   Implementors must take care to ensure that they maintain the 
>   semantics of the DIGEST-MD5 specification even when handling data 
>   that has different semantics in the LDAP protocol. 
>   For example, the SASL DIGEST-MD5 authentication mechanism utilizes 
>   realm and username values ([DigestAuth section 2.1) which are 
>   syntactically simple strings and semsantically simple realm and 
>   username values. These values are not LDAP DNs, and there is no 
>   requirement that they be represented or treated as such. Username 
>   and realm values that look like LDAP DNs in form, e.g. "cn=bob, 
>   o=Ace Industry ", are syntactically allowed, however DIGEST-MD5 
>   treats them as simple strings for comparison purposes. To illustrate 
>   further, the two DNs "cn=bob, o=Ace Industry" (space between RDNs) 
>   and "cn=bob,o=Ace Industry" (no space between RDNs) would be 
>   equivalent when being compared semantically as LDAP DNs, however 
>   they are not equivalent if they were used to represent username 
>   values in DIGEST-MD5 because simple octet-wise comparision semantics 
>   are used by DIGEST-MD5.  
>    
> 
>7.3. "simple" authentication choice under TLS encryption 
>    
>   Following the negotiation of an appropriate TLS ciphersuite 
>   providing connection confidentiality [RFC2246], a client MAY 
>   authenticate to a directory that supports the simple authentication 
>   choice by performing a simple bind operation 
>    
>   Simple authentication with TLS encryption protection is performed as 
>   follows:   
>    
>      1. The client will use the Start TLS operation [Protocol] to 
>        negotiate the use of TLS security [RFC2246] on the connection 
>        to the LDAP server. The client need not have bound to the 
>        directory beforehand. 
>      
>         For the subsequent authentication procedure to be performed 
>         securely, the client and server MUST negotiate a ciphersuite 
>         which contains a bulk encryption algorithm of appropriate 
>         strength. Recommendations on cipher suites are given in 
>         section 9. 
>    
>      2. Following the successful completion of TLS negotiation, the 
>         client MUST send an LDAP bind request with the version number 
>         of 3, the name field containing a DN, and the "simple" 
>         authentication choice, containing a password. 
>    
>7.3.1. "simple" Authentication Choice  
> 
>   DSAs that map the DN sent in the bind request to a directory entry 
>   with an associated set of one or more passwords will compare the 
>   presented password to the set of passwords associated with that 
>   entry. If the presented password matches any member of that set, 
>   then the server will respond with resultCode success, otherwise the 
>   server will respond with resultCode invalidCredentials. 
>    
>7.4. Other authentication choices with TLS 
>    
>   It is also possible, following the negotiation of TLS, to perform a 
>   SASL authentication that does not involve the exchange of plaintext 
>   reusable passwords. In this case the client and server need not 
>   negotiate a ciphersuite that provides confidentiality if the only 
>   service required is data integrity. 
>    
> 
> 
>8. Certificate-based authentication 
> 
>   LDAP server implementations SHOULD support authentication via a 
>   client certificate in TLS, as defined in section 8.1. 
> 
>8.1. Certificate-based authentication with TLS 
> 
>   A user who has a public/private key pair in which the public key has 
>   been signed by a Certification Authority may use this key pair to 
>   authenticate to the directory server if the user's certificate is 
>   requested by the server. The user's certificate subject field SHOULD 
>   be the name of the user's directory entry, and the Certification 
>   Authority that issued the user's certificate must be sufficiently 
>   trusted by the directory server in order for the server to process 
>   the certificate. The means by which servers validate certificate 
>   paths is outside the scope of this document. 
> 
>   A server MAY support mappings for certificates in which the subject 
>   field name is different from the name of the user's directory entry. 
>   A server which supports mappings of names MUST be capable of being 
>   configured to support certificates for which no mapping is required. 
> 
>   The client will use the Start TLS operation [Protocol] to negotiate 
>   the use of TLS security [RFC2246] on the connection to the LDAP 
>   server. The client need not have bound to the directory beforehand. 
> 
>   In the TLS negotiation, the server MUST request a certificate. The 
>   client will provide its certificate to the server, and the server 
>   MUST perform a private key-based encryption, proving it has the 
>   private key associated with the certificate. 
> 
>   In deployments that require protection of sensitive data in transit, 
>   the client and server MUST negotiate a ciphersuite that contains a 
>   bulk encryption algorithm of appropriate strength. Recommendations 
>   of cipher suites are given in section 9. 
> 
>   The server MUST verify that the client's certificate is valid. The 
>   server will normally check that the certificate is issued by a known 
>   certification authority (CA), and that none of the certificates on 
>   the client's certificate chain are invalid or revoked. There are 
>   several procedures by which the server can perform these checks. 
> 
>   Following the successful completion of TLS negotiation, the client 
>   will send an LDAP bind request with the SASL "EXTERNAL" mechanism. 
> 
>9. TLS Ciphersuites 
> 
>   A client or server that supports TLS MUST support 
>   TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA and MAY support other ciphersuites 
>   offering equivalent or better protection. 
>    
>   Several issues should be considered when selecting TLS ciphersuites 
>   that are appropriate for use in a given circumstance. These issues 
>   include the following: 
> 
> 
>    
>     - The ciphersuite's ability to provide adequate confidentiality 
>       protection for passwords and other data sent over the LDAP 
>       connection. Client and server implementers should recognize that 
>       some TLS ciphersuites provide no confidentiality protection 
>       while other ciphersuites that do provide confidentiality 
>       protection may be vulnerable to being cracked using brute force 
>       methods, especially in light of ever-increasing CPU speeds that 
>       reduce the time needed to successfully mount such attacks. 
>      
>       Client and server implementers SHOULD carefully consider the 
>       value of the password or data being protected versus the level 
>       of confidentially protection provided by the ciphersuite to 
>       ensure that the level of protection afforded by the ciphersuite 
>       is appropriate. 
>      
>     - The ciphersuite's vulnerability (or lack thereof) to man-in-the-
>       middle attacks. Ciphersuites vulnerable to man-in-the-middle 
>       attacks SHOULD NOT be used to protect passwords or sensitive 
>       data, unless the network configuration is such that the danger 
>       of a man-in-the-middle attack is tolerable. 
> 
>9.1. TLS Ciphersuites Recommendations 
>    
>   As of the writing of this document, the following recommendations 
>   regarding TLS ciphersuites are applicable. Because circumstances are 
>   constantly changing, this list must not be considered exhaustive, 
>   but is hoped that it will serve as a useful starting point for 
>   implementers.  
>    
>   The following ciphersuites defined in [RFC2246] MUST NOT be used for 
>   confidentiality protection of passwords or data: 
> 
>         TLS_NULL_WITH_NULL_NULL 
>         TLS_RSA_WITH_NULL_MD5 
>         TLS_RSA_WITH_NULL_SHA 
> 
>   The following ciphersuites defined in [RFC2246] can be cracked 
>   easily (less than a day of CPU time on a standard CPU in 2000) and 
>   are NOT RECOMMENDED for use in confidentiality protection of 
>   passwords or data. 
> 
>         TLS_RSA_EXPORT_WITH_RC4_40_MD5 
>         TLS_RSA_EXPORT_WITH_RC2_CBC_40_MD5 
>         TLS_RSA_EXPORT_WITH_DES40_CBC_SHA 
>         TLS_DH_DSS_EXPORT_WITH_DES40_CBC_SHA 
>         TLS_DH_RSA_EXPORT_WITH_DES40_CBC_SHA 
>         TLS_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA 
>         TLS_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA 
>         TLS_DH_anon_EXPORT_WITH_RC4_40_MD5 
>         TLS_DH_anon_EXPORT_WITH_DES40_CBC_SHA 
> 
>   The following ciphersuites are vulnerable to man-in-the-middle 
>   attacks: 
> 
> 
> 
>         TLS_DH_anon_EXPORT_WITH_RC4_40_MD5 
>         TLS_DH_anon_WITH_RC4_128_MD5 
>         TLS_DH_anon_EXPORT_WITH_DES40_CBC_SHA 
>         TLS_DH_anon_WITH_DES_CBC_SHA 
>         TLS_DH_anon_WITH_3DES_EDE_CBC_SHA 
> 
>    
> 
>10. Security Considerations 
>    
>   Security issues are discussed throughout this memo; the 
>   (unsurprising) conclusion is that mandatory security is important 
>   and that session confidentiality protection is required when 
>   snooping is a problem. 
>    
>   Servers are encouraged to prevent modifications by anonymous users. 
>   Servers may also wish to minimize denial of service attacks by 
>   timing out idle connections, and returning the unwillingToPerform 
>   result code rather than performing computationally expensive 
>   operations requested by unauthorized clients. 
>    
>   Operational experience shows that clients can misuse unauthenticated 
>   access (simple bind with name but no password).  For example, a 
>   client program might authenticate a user via LDAP and then grant 
>   access to information not stored in the directory on the basis of 
>   completing a successful bind. Some implementations will return a 
>   success response to a simple bind that consists of a user name and 
>   an empty password thus leaving the impression that the client has 
>   successfully authenticated the identity represented by the user 
>   name, when in reality, the directory server has simply performed an 
>   anonymous bind.  For this reason, servers SHOULD by default reject 
>   authentication requests that have a DN with an empty password with 
>   an error of invalidCredentials. 
>    
>   Access control SHOULD always be applied when reading sensitive 
>   information or updating directory information. 
> 
>   A connection on which the client has not performed the Start TLS 
>   operation or negotiated a suitable SASL mechanism for connection 
>   integrity and encryption services is subject to man-in-the-middle 
>   attacks to view and modify information in transit. 
>    
>10.1.  Start TLS Security Considerations 
>    
>   The goals of using the TLS protocol with LDAP are to ensure 
>   connection confidentiality and integrity, and to optionally provide 
>   for authentication. TLS expressly provides these capabilities, as 
>   described in [RFC2246]. 
>    
>   All security gained via use of the Start TLS operation is gained by 
>   the use of TLS itself. The Start TLS operation, on its own, does not 
>   provide any additional security. 
>    
> 
> 
>   Once established, TLS only provides for and ensures confidentiality 
>   and integrity of the operations and data in transit over the LDAP 
>   association--and only if the implementations on the client and 
>   server support and negotiate it. The use of TLS does not provide or 
>   ensure for confidentiality and/or non-repudiation of the data housed 
>   by an LDAP-based directory server. Nor does it secure the data from 
>   inspection by the server administrators.  
>     
>   The level of security provided though the use of TLS depends 
>   directly on both the quality of the TLS implementation used and the 
>   style of usage of that implementation. Additionally, an active-
>   intermediary attacker can remove the Start TLS extended operation 
>   from the supportedExtension attribute of the root DSE. Therefore, 
>   both parties SHOULD independently ascertain and consent to the 
>   security level achieved once TLS is established and before beginning 
>   use of the TLS connection. For example, the security level of the 
>   TLS connection might have been negotiated down to plaintext. 
>    
>   Clients SHOULD either warn the user when the security level achieved 
>   does not provide confidentiality and/or integrity protection, or be 
>   configurable to refuse to proceed without an acceptable level of 
>   security. 
>    
>   Client and server implementors SHOULD take measures to ensure proper 
>   protection of credentials and other confidential data where such 
>   measures are not otherwise provided by the TLS implementation. 
>    
>   Server implementors SHOULD allow for server administrators to elect 
>   whether and when connection confidentiality and/or integrity is 
>   required, as well as elect whether and when client authentication 
>   via TLS is required. 
>    
>   Additional security considerations relating to the EXTERNAL 
>   mechanism to negotiate TLS can be found in [SASL] and [RFC2246]. 
>    
>11. IANA Considerations 
>    
>   The following IANA considerations apply to this document: 
>    
>   [To be completed] 
>    
>Contributors 
>    
>   This document combines information originally contained in RFC 2829 
>   and RFC 2830. The editor acknowledges the work of Harald Tveit 
>   Alvestrand, Jeff Hodges, Tim Howes, Steve Kille, RL "Bob" Morgan , 
>   and Mark Wahl, each of whom authored one or more of these documents. 
>    
>Acknowledgements 
> 
>   This document is based upon input of the IETF LDAP Revision working 
>   group. The contributions and suggestions made by its members in 
>   shaping the contents and technical accuracy of this document is 
>   greatly appreciated. 
> 
> 
>    
>Normative References 
> 
>   [RFC2119] Bradner, S., "Key Words for use in RFCs to Indicate 
>       Requirement Levels", BCP 14, RFC 2119, March 1997. 
>    
>   [RFC2234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax 
>       Specifications: ABNF", RFC 2234, November 1997. 
> 
>   [RFC2246] Dierks, T. and C. Allen. "The TLS Protocol Version 1.0", 
>       RFC 2246, January 1999. 

Reference 2246bis I-D instead.
 
>   [DigestAuth] Leach, P. C. Newman, and A. Melnikov, "Using Digest 
>      Authentication as a SASL Mechanism", draft-ietf-sasl-rfc2831bis-
>      xx.txt, a work in progress.  
>    
>   [LDAPDN] Zeilenga, Kurt D. (editor), "LDAP: String Representation of 
>      Distinguished Names", draft-ietf-ldapbis-dn-xx.txt, a work in 
>      progress. 
>    
>   [Model] Zeilenga, Kurt D. (editor), "LDAP: Directory Information 
>       Models", draft-ietf-ldapbis-models-xx.txt, a work in progress. 
>    
>   [Protocol] Sermersheim, J., "LDAP: The Protocol", draft-ietf-
>       ldapbis-protocol-xx.txt, a work in progress. 
>    
>   [ROADMAP] K. Zeilenga, "LDAP: Technical Specification Road Map", 
>       draft-ietf-ldapbis-roadmap-xx.txt, a work in progress. 
>   [SASL] Melnikov, A. (editor), "Simple Authentication and Security 
>       Layer (SASL)", draft-ietf-sasl-rfc2222bis-xx.txt, a work in 
>       progress. 
>    
>    
>     
>Informative References 
> 
>   [ANONYMOUS] Zeilenga, K.,"Anonymous SASL Mechanism", draft-zeilenga-
>       sasl-anon-xx.txt, a work in progress. 
>    
>   [PLAIN] Zeilenga, K.,"Plain SASL Mechanism", draft-zeilenga-sasl-
>       plain-xx.txt, a work in progress. 
>    
>    [RFC2828] Shirey, R., "Internet Security Glossary", RFC 2828, May 
>       2000. 
>    
>   [RFC2401] Kent, S. and R. Atkinson, "Security Architecture for the 
>       Internet Protocol", RFC 2401, November 1998. 
> 
> 
>Author's Address 
> 
>   Roger Harrison 
>   Novell, Inc. 
>   1800 S. Novell Place 
> 
> 
>   Provo, UT 84606 
>   +1 801 861 2642 
>   roger_harrison@novell.com 
> 
>Full Copyright Statement 
> 
>   Copyright (C) The Internet Society (2003). All Rights Reserved. 
> 
>   This document and translations of it may be copied and furnished to 
>   others, and derivative works that comment on or otherwise explain it 
>   or assist in its implementation may be prepared, copied, published 
>   and distributed, in whole or in part, without restriction of any 
>   kind, provided that the above copyright notice and this paragraph 
>   are included on all such copies and derivative works. However, this 
>   document itself may not be modified in any way, such as by removing 
>   the copyright notice or references to the Internet Society or other 
>   Internet organizations, except as needed for the purpose of 
>   developing Internet standards in which case the procedures for 
>   copyrights defined in the Internet Standards process must be 
>   followed, or as required to translate it into languages other than 
>   English. 
> 
>   The limited permissions granted above are perpetual and will not be 
>   revoked by the Internet Society or its successors or assigns. 
> 
>   This document and the information contained herein is provided on an 
>   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 
>   TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 
>   BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 
>   HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 
>   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 
>    
>Appendix A. Example Deployment Scenarios 
> 
>   The following scenarios are typical for LDAP directories on the 
>   Internet, and have different security requirements. (In the 
>   following discussion, "sensitive data" refers to information whose 
>   disclosure, alteration, destruction, or loss would adversely affect 
>   the interests or business of its owner or user. Also note that there 
>   may be data that is protected but not sensitive.) This is not 
>   intended to be a comprehensive list; other scenarios are possible, 
>   especially on physically protected networks. 
>    
>   (1) A read-only directory, containing no sensitive data, accessible 
>       to "anyone", and TCP connection hijacking or IP spoofing is not 
>       a problem. Anonymous authentication, described in section 7, is 
>       suitable for this type of deployment, and requires no additional 
>       security functions except administrative service limits. 
> 
>   (2) A read-only directory containing no sensitive data; read access 
>       is granted based on identity. TCP connection hijacking is not 
>       currently a problem. This scenario requires data confidentiality 
>       for sensitive authentication information AND data integrity for 
>       all authentication information. 
> 
>   (3) A read-only directory containing no sensitive data; and the 
>       client needs to ensure the identity of the directory server and 
>       that the directory data is not modified while being returned 
>       from the server. A data origin authentication service AND data 
>       integrity service are required. 
> 
>   (4) A read-write directory, containing no sensitive data; read 
>       access is available to "anyone", update access to properly 
>       authorized persons. TCP connection hijacking is not currently a 
>       problem. This scenario requires data confidentiality for 
>       sensitive authentication information AND data integrity for all 
>       authentication information. 
>    
>   (5) A directory containing sensitive data. This scenario requires 
>       data confidentiality protection AND secure authentication. 
> 
>Appendix B. Authentication and Authorization: Definitions and Concepts 
> 
>   This appendix defines basic terms, concepts, and interrelationships 
>   regarding authentication, authorization, credentials, and identity. 
>   These concepts are used in describing how various security 
>   approaches are utilized in client authentication and authorization. 
> 
>B.1. Access Control Policy 
> 
>   An access control policy is a set of rules defining the protection 
>   of resources, generally in terms of the capabilities of persons or 
>   other entities accessing those resources. A common expression of an 
>   access control policy is an access control list. Security objects 
>   and mechanisms, such as those described here, enable the expression 
>   of access control policies and their enforcement. Access control 
>   policies are typically expressed in terms of access control factors 
>   as described below. 
> 
>B.2. Access Control Factors 
> 
>   A request, when it is being processed by a server, may be associated 
>   with a wide variety of security-related factors (section 4.2 of 
>   [Protocol]). The server uses these factors to determine whether and 
>   how to process the request. These are called access control factors 
>   (ACFs). They might include source IP address, encryption strength, 
>   the type of operation being requested, time of day, etc. Some 
>   factors may be specific to the request itself, others may be 
>   associated with the connection via which the request is transmitted, 
>   others (e.g. time of day) may be "environmental". 
> 
>   Access control policies are expressed in terms of access control 
>   factors. E.g., a request having ACFs i,j,k can perform operation Y 
>   on resource Z. The set of ACFs that a server makes available for 
>   such expressions is implementation-specific. 
> 
>B.3. Authentication, Credentials, Identity 
> 
>   Authentication credentials are the evidence supplied by one party to 
>   another, asserting the identity of the supplying party (e.g. a user) 
>   who is attempting to establish an association with the other party 
>   (typically a server). Authentication is the process of generating, 
>   transmitting, and verifying these credentials and thus the identity 
>   they assert. 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. 
> 
>B.4. Authorization Identity 
> 
>   An authorization identity is one kind of access control factor. It 
>   is the name of the user or other entity that requests that 
>   operations be performed. Access control policies are often expressed 
>   in terms of authorization identities; e.g., entity X can perform 
>   operation Y on resource Z. 
> 
>   The authorization identity bound to an association is often exactly 
>   the same as the authentication identity presented by the client, but 
>   it may be different. SASL allows clients to specify an authorization 
>   identity distinct from the authentication identity asserted by the 
>   client's 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 [SASL]. Also, 
>   the form of authentication identity supplied by a service like TLS 
>   may not correspond to the authorization identities used to express a 
>   server's access control policy, requiring a server-specific mapping 
>   to be done. The method by which a server composes and validates an 
>   authorization identity from the authentication credentials supplied 
>   by a client is implementation-specific. 
 


From owner-ietf-ldapbis@OpenLDAP.org  Tue Oct 14 10:18:08 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 KAA11650
	for <ldapbis-archive@lists.ietf.org>; Tue, 14 Oct 2003 10:18:07 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9EEFYI6075582;
	Tue, 14 Oct 2003 14:16:26 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9EECAwS075141;
	Tue, 14 Oct 2003 14:12:10 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 14 Oct 2003 14:12:10 +0000
Received: from pat.uio.no (IDENT:7411@pat.uio.no [129.240.130.16])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9EEBrHS075039
	for <ietf-ldapbis@openldap.org>; Tue, 14 Oct 2003 14:11:54 GMT
	(envelope-from hbf@bombur.uio.no)
Received: from mail-mx6.uio.no ([129.240.10.47] ident=[cefgg+7imscqlxPxB57zolsfXiuqyxH2])
	by pat.uio.no with esmtp (Exim 4.20)
	id 1A9Ptu-0001ei-46
	for ietf-ldapbis@openldap.org; Tue, 14 Oct 2003 16:11:50 +0200
Received: from bombur.uio.no ([129.240.186.42])
	by mail-mx6.uio.no with esmtp (Exim 4.14)
	id 1A9PtY-0001di-MM; Tue, 14 Oct 2003 16:11:28 +0200
Received: from hbf by bombur.uio.no with local (Exim 2.12 #7)
	id 1A9PtY-00038F-00; Tue, 14 Oct 2003 16:11:28 +0200
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Message-Id: <HBF.20031014pk3@bombur.uio.no>
To: ietf-ldapbis@OpenLDAP.org
Subject: authmeth-07 issues
Date: Tue, 14 Oct 2003 16:11:28 +0200
X-MailScanner-Information: This message has been scanned for viruses/spam. Contact postmaster@uio.no if you have questions about this scanning.
X-UiO-MailScanner: No virus found
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

Sometimes you say that to achieve X, one MUST do Y and then Z.  I think
this is a misuse of the "MUST" keyword.  Instead, say that one can
achieve X by doing Y and then Z.  In particular when the "to achive X,"
part seems to be indicated by the section header rather than stated
explicitly before the MUST.  I comment the instances I found below.

The information in sections 3-9 is rather confusingly arranged.
This is difficult to follow, and also leads to redundancy:
  bind/anonymous (3), SASL (3.3), EXTERNAL (3.3.6), SASL,
  TLS (4), EXTERNAL (4.1.5), TLS, EXTERNAL (4.2.2), bind (4.2.2.3), TLS,
  transition table (5),
  bind/anonymous again (6),
  simple bind (7.1), SASL DIGEST-MD5 (7.2), bind/TLS (7.3-4),
  TLS/EXTERNAL (8),
  TLS (9).
I suggest you rearrange it something like this:
  TLS, with nothing but a one-sentence forward reference to EXTERNAL,
  bind in general (e.g. error conditions),
  unbound connections,
  simple and anonymous bind,
  SASL,
    EXTERNAL,
    DIGEST-MD5,
    other SASL methods,
  transition table,
  TLS ciphersuites (section 9) here, or with the TLS section above?
Some comments about this follow below.

> 3.1. Unbound Connection Treated as Anonymous ("Implied Anonymous Bind")
>
>    (...) If the server
>    requires that the client bind before browsing or modifying the
>    directory, the server MAY reject a request other than binding,
>    unbinding or an extended request with the "operationsError" result.

"extended request"?  It should be allowed to reject extended requests
other than the StartTLS extended request.

Also abandon should be in the list above, since it cannot respond with
"operationsError".

Finally, I suggest you rephrase the above "If..." sentence to simply
say: "Over an anonymous LDAP association [or LDAP connection?], the
server MAY reject a request other than...".  That also takes care of
requests after a failed bind, and after TLS closure.  The "if the server
requires..." part is implicit in the rest of the sentence and can be
dropped.

> 3.2. Simple Authentication

Move the info about anonymous auth to a subsection of this.

>    The simple authentication option provides minimal authentication
>    facilities, with the contents of the authentication field consisting
>    only of a cleartext password.

Should this section mention how SASLprep is used on auth password and
DN?

> 3.3. SASL Authentication Profile
>
>    As LDAP
>    includes native anonymous and plaintext authentication methods, the
>    "ANONYMOUS" [ANONYMOUS] and "PLAIN" [PLAIN] SASL mechanisms are
>    typically not used with LDAP.

Why mention them at all?  They are not mentioned in rfc2222bis, so there
is no need for a disclaimer.

> 3.3.2. SASL authentication initiation and protocol exchange

>    client to respond to one or more server challenges by invoking the
>    BindRequest multiple times.

I think "the" should be dropped.

>    A client may abort a SASL bind negotiation by sending a BindRequest
>    with a different value in the mechanism field of SaslCredentials, or
>    an AuthenticationChoice other than sasl.

That new bindRequest is then started instead?

> 3.3.3. Octet where negotiated security mechanisms take effect
>
>    If any SASL-based integrity or confidentiality services are enabled,
>    they take effect following the transmission by the server and
>    reception by the client of the final BindResponse with a resultCode
>    of success.

Merge this with 3.5.

> 3.3.5. Rules for using SASL security layers

>    If the client is configured to support multiple
>    SASL mechanisms,

No, "If the client makes use of supportedSASLmechanisms,"

It might be support multiple SASL mechanisms in a way such that the
choice is controlled by something else than supportedSASLmechanisms,
e.g. by the user.

>    it SHOULD fetch the supportedSASLmechanisms list
>    both before and after the SASL security layer is negotiated.

>    If a lower level security layer (such as TLS) is negotiated, any
>    SASL security services SHALL be layered on top of such security
>    layers regardless of the order of their negotiation.

This is repeated in 3.5.  Delete one of the texts.
Actually, I suggest 3.5 is moved here.

> 3.3.6. Use of EXTERNAL SASL Mechanism

Move this section down to the rest of the text about EXTERNAL.

>    If a TLS session has not been established between the client
>    and server prior to making the SASL EXTERNAL Bind request

No, if there is no current TLS session.  A TLS session might have been
establised prior to the bind and then closed.  I don't think one should
use credentials from it in that case.

>    if during the process of establishing
>    the TLS session, the server did not request the client's
>    authentication credentials,

"authentication credentials" = "certificate"?  In 8.1 you say "the
server MUST request a certificate".  IIRC, yet another place you imply
that the client need not send a certificate even if the server requested
it.  I don't know what is right.  Maybe "the server did not request"
should be "if the client did not send"?

>    the SASL EXTERNAL bind MUST fail with a
>    resultCode of inappropriateAuthentication.

>    Any client authentication
>    and authorization state of the LDAP association is lost, so the LDAP
>    association is in an anonymous state after the failure (see
>    [Protocol] section 4.2.1).

This is not specific to EXTERNAL.  It should be moved to a section about
bind (and bind failure) in genereal.

> 3.4. SASL Authorization Identity
>
>    The authorization identity is carried as part of the SaslCredentials
>    credentials field in the Bind request and response.

What does it mean to have an authz id in the response?  Can it be
different from the authz identity that the client requested, or
something?  Will some clients need to check that the authz id it
received, is the one it wanted?

>    When the "EXTERNAL" SASL mechanism is being negotiated, if the
>    credentials field is present, it contains an authorization identity
>    of the authzId form described below.
>
>    Other mechanisms define the location of the authorization identity
>    in the credentials field.

I have trouble with what "other mechanisms" you refer to after all.
I suggest you reword as:

    "SASL mechanisms that use an authorization identity, define where
    in the credentials field it is found".

Then move the previous paragraph (about EXTERNAL authz id) to the
section about EXTERNAL, or swap the two paragraphs.

> 3.4.1. Authorization Identity Syntax

Rename this section, it is about more than authz id _syntax_.

> 3.5. SASL Integrity and Privacy Protections
>
>    Any negotiated SASL integrity and privacy protections SHALL start on
>    the first octet of the first LDAP PDU following successful
>    completion of the SASL bind operation.

3.3.3 said that.

State the effect of a failed SASL bind or a non-SASL bind on an existing
SASL security layer.  I expect it would be something like this:

  A bindRequest (successful or not) which is not successfully abandoned,
  cancels [is that the right word?] any previously established SASL
  security layer, so that the bindResponse is sent without that layer.

[Or - if there are outstanding, possibly-abandoned requests, will the
client know when the security layer gets cancelled?  Does the layer
itself necessarily contain a "cancel" operation so the client can tell?]

  TLS closure also cancels the SASL security layer.

[seems natural since the connection moves to anonymous state.]

>    If lower level security layer
>    is negotiated, such as TLS, any SASL security services SHALL be
>    layered on top of such security layers regardless of the order of
>    their negotiation.

3.3.5 said that.

> 4.1. Sequencing of the Start TLS Operation

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

No, in 4.2.1: It has no effect.  EXTERNAL has effect, but that's the
bind operation, not the start TLS operation.
Just delete this paragraph.

> 4.1.1. Requesting to Start TLS on an LDAP Association

>    In particular, there is no requirement that the client have or have
>    not already performed a Bind operation before sending a Start TLS
>    operation request. The client may have already performed a Bind
>    operation when it sends a Start TLS request, or the client might
>    have not yet bound.

The second sentence is redundant.  Delete it.

>    If the client did not establish a TLS connection before sending any
>    other requests, and the server requires the client to establish a
>    TLS connection before performing a particular request, the server
>    MUST reject that request by sending a resultCode of

"If the server wishes...then it MUST".  Don't say that.  You can replace
the above with:

     If a TLS connection is not established, the server MAY reject
     any request other than Start TLS [, unbind?] and abandon by
     sending...

>    confidentialityRequired or strongAuthRequired.

strongAuthRequired sounds wrong.  Auth is bind, and bind won't help.

>    In response, the
>    client MAY send a Start TLS extended request, or it MAY choose to
>    close the connection.

Delete this, it is obvious from the above.

> 4.1.4. Discovery of Resultant Security Level

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

Is there any problem if the client and the server initiate TLS closure
at the same time?

>    If the client decides to continue, it MAY gracefully close the TLS
>    connection and attempt to Start TLS again, it MAY send an unbind
>    request, or it MAY send any other LDAP request.

This paragraph seems redundant to me.  But if you keep it, reword to:

    "If the client decides to continue after TLS closure, it MAY..."

since it might have been the server which closed TLS.

> 4.1.5. Assertion of Client's Authorization Identity
>
>    The client MAY, upon receipt of a Start TLS response indicating
>    success,

no, after a successful TLS connection has been established.  The
response might be success but the following TLS negotiation might fail.

Besides, it may do this with (at least) IPv6 too.

>    assert that a specific authorization identity be utilized
>    in determining the client's authorization status. The client
>    accomplishes this via an LDAP Bind request specifying a SASL
>    mechanism of "EXTERNAL" [SASL] (see section 4.2.2 below).

However, I think this entire section should be deleted.  You mention
EXTERNAL enough places as it is.

> 4.1.6. Server Identity Check

>    The
>    client MAY need to make use of local policy information.

s/MAY/may/.

> 4.2. Effects of TLS on a Client's Authorization Identity
>
>    This section describes the effects on a client's authorization
>    identity brought about by establishing TLS on an LDAP association.

It has no effect.

> 4.2.1. Default Effects

Rename.  "Default" is something which can be overridden.  EXTERNAL
does not override the effect of TLS, it is a separate operation.

> 4.2.2. Client Assertion of Authorization Identity

Move this and subsections to one section about EXTERNAL.  No need to
have a separate section about EXTERNAL for TLS.

> 4.2.2.1. Implicit Assertion
> 4.2.2.2. Explicit Assertion

>    An implicit authorization identity assertion is accomplished after
>    TLS establishment

Is implicit (and 4.2.2.2 explicit) association a TLS term, or do the
terms apply to EXTERNAL with e.g. IPv6 too?

>    by invoking a Bind request of the SASL form using
>    the "EXTERNAL" mechanism name [SASL] [Protocol] that SHALL NOT
>    include the optional credentials octet string (found within the

s/that SHALL NOT include/which does not include/.  Similar for 4.2.2.2.
Since you define implicit/explicit assertion by how it is done.

> 4.2.2.3. Error Conditions

>    Additionally, with either form of assertion, if a TLS session has
>    not been established between the client and server prior to making
>    the SASL EXTERNAL Bind request and there is no other external source
>    of authentication credentials (e.g. IP-level security [RFC2401]), or
>    if during the process of establishing the TLS session, the server
>    did not request the client's authentication credentials, the SASL
>    EXTERNAL bind MUST fail with a result code of
>    inappropriateAuthentication.

Delete, you already said that in 3.3.6.

>    After the above Bind operation failures, any client authentication
>    and authorization state of the LDAP association is lost (see
>    [Protocol] section 4.2.1), so the LDAP association is in an
>    anonymous state after the failure.  The TLS session state is
>    unaffected, though a server MAY end the TLS session, via a TLS
>    close_notify message, based on the Bind failure (as it MAY at any
>    time).

Move to a section about bind.  It applies to bind in general, not to
just TLS/EXTERNAL.

> 6. Anonymous Authentication

Move to subsection of 3.2 (simple auth)

>    LDAP implementations MUST support anonymous authentication, as
>    defined in section 6.1.
>
>    LDAP implementations MAY support anonymous authentication with TLS,
>    as defined in section 6.2.

Huh?  What's the point of allowing anon/TLS to be unsupported?
Clients might want to use TLS for data integrity or something, but
they can still be read-only and have no need to bind.

> 6.1. Anonymous Authentication Procedure

>    An LDAP client MAY also choose to explicitly bind anonymously. A
>    client that wishes to do so MUST choose the simple authentication
>    option in the Bind Request (...)

"If the client wishes, it MUST".  Don't say that.  Try:

     An LDAP client MAY also choose to explicitly bind anonymously, by
     choosing the simple authentication
     option in the Bind Request (...)

> 6.2. Anonymous Authentication and TLS

>    An LDAP client MAY use the Start TLS operation (section 5) to
>    negotiate the use of TLS security [RFC2246]. If the client has not
>    bound beforehand, then until the client uses the EXTERNAL SASL
>    mechanism to negotiate the recognition of the client's certificate,
>    the client is anonymously authenticated.

What's the point of this paragraph?  The reader knows this already.

>    Recommendations on TLS ciphersuites are given in section 9.
>
>    An LDAP server which requests that clients provide their certificate
>    during TLS negotiation MAY use a local security policy to determine
>    whether to successfully complete TLS negotiation if the client did
>    not present a certificate which could be validated.

The the above two paragraphs have noting to do with anonymous auth.
Move them.

> 7.1. Simple Authentication
>
>    LDAP implementations SHOULD NOT support authentication
>    with the "simple" authentication choice

and a non-empty password

>    unless the data on the
>    connection is protected using TLS or other data confidentiality and
>    data integrity protection.

> 7.2. Digest Authentication

>    Support for subsequent authentication

     as defined in DIGEST-MD5 [DIGEST-MD5]

[Added because a reader might have no idea what you are talking about
otherwise.]

>    is OPTIONAL in clients and
>    servers.

>    o=Ace Industry ", are syntactically allowed, however DIGEST-MD5

Remove space before <">.

> 7.3. "simple" authentication choice under TLS encryption

What's the point of this section?  You just say that we can do simple
auth with TLS by doing TLS and then simple auth.  That has been said
before.  And it's already stated that the server shouldn't accept them
in the reverse order.

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

Move this to the section about simple auth.  Maybe mention that
server-side passwords should be prepared with SASLprep.

> 7.4. Other authentication choices with TLS
>
>    It is also possible, following the negotiation of TLS, to perform a
>    SASL authentication that does not involve the exchange of plaintext
>    reusable passwords. In this case the client and server need not
>    negotiate a ciphersuite that provides confidentiality if the only
>    service required is data integrity.

I don't see the point of this paragraph either.
If you mean EXTERNAL, we know that.  If you mean DIGEST-MD5, we know
that too - and we don't need TLS for that, though TLS doesn't hurt.
Also, with "negotiate a ciphersuite", do you mean TLS ciphersuite or
SASL cipersuite?

> 8. Certificate-based authentication
>
>    LDAP server implementations SHOULD support authentication via a
>    client certificate in TLS, as defined in section 8.1.

This should probably be moved to the discussion about EXTERNAL.

> 8.1. Certificate-based authentication with TLS

This section is confusing, it mixes up info about TLS, EXTERNAL, and
bind in general.  This info should be split out to three such different
sections at different places in the document.

>    A user who has a public/private key pair in which the public key has
>    been signed by a Certification Authority

I'm not sure how this works.  Can't the server have a store of trusted
unsigned certificates?

>    may use this key pair to
>    authenticate to the directory server if the user's certificate is
>    requested by the server.

>    The user's certificate subject field SHOULD
>    be the name of the user's directory entry,

Why?  Certificate handling (like OpenSSL) can be completely separate
from the LDAP directory.  You even say below that how to validate the
certificate path is out of scope for LDAP.

>    A server MAY support mappings for certificates in which the subject
>    field name is different from the name of the user's directory entry.

Yes...

>    A server which supports mappings of names MUST be capable of being
>    configured to support certificates for which no mapping is required.

Why?

>    The client will use the Start TLS operation [Protocol] to negotiate
>    the use of TLS security [RFC2246] on the connection to the LDAP
>    server.

Said that before.

>    The client need not have bound to the directory beforehand.

Said that before too.

>    In the TLS negotiation, the server MUST request a certificate. The
>    client will provide its certificate to the server,

I've certainly used LDAP/TLS without client certificates.  Do you mean
that IF one wishes to do certificate-based auth, this must be done?  If
so, you should instead say that the client can do cert-based auth by
sending a cert during TLS establishment and then an EXTERNAL bind.
Though I suspect this is redundant; you say a lot about EXTERNAL
elsewhere.

>    and the server
>    MUST perform a private key-based encryption, proving it has the
>    private key associated with the certificate.

private key-based encryption of what?

>    In deployments that require protection of sensitive data in transit,
>    the client and server MUST negotiate a ciphersuite that contains a
>    bulk encryption algorithm of appropriate strength. Recommendations
>    of cipher suites are given in section 9.

What has this to do with certificate-based auth?

>    Following the successful completion of TLS negotiation, the client
>    will send an LDAP bind request with the SASL "EXTERNAL" mechanism.

if it wants to do cert-based auth.

> 9. TLS Ciphersuites

>    A client or server that supports TLS MUST support
>    TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA and MAY support other ciphersuites
>    offering equivalent or better protection.

does this imply that it MUST NOT support ciphersuites with poorer
protection?

> 10. Security Considerations

I think you should say that if the connection is already bound when
startTLS is performed, servers SHOULD reject operations that follow
StartTLS other than bind, unbind and abandon (with strongAuthRequired?).

bind before startTLS is an insecure combination, and that an attacker
also may insert a bind before a startTLS when the client expects to do
anonymous operations with TLS.

Or SHOULD the server reject these operations even if the connection is
anonymous?  The attacker could have inserted an anonymous bind, though
that doesn't seem like much of a problem.

> Normative References

>    [ROADMAP] K. Zeilenga, "LDAP: Technical Specification Road Map",
>        draft-ietf-ldapbis-roadmap-xx.txt, a work in progress.

Insert a blank line here.

>    [SASL] Melnikov, A. (editor), "Simple Authentication and Security
>        Layer (SASL)", draft-ietf-sasl-rfc2222bis-xx.txt, a work in
>        progress.

> Informative References

>     [RFC2828] Shirey, R., "Internet Security Glossary", RFC 2828, May

This line is indented one space too much.

> B.1. Access Control Policy
>
>    An access control policy is a set of rules defining the protection
>    of resources, generally in terms of the capabilities of persons or
>    other entities accessing those resources. A common expression of an
>    access control policy is an access control list.

So what's an access control list? :-)

>    Security objects
>    and mechanisms, such as those described here, enable the expression
>    of access control policies and their enforcement.

>    Access control
>    policies are typically expressed in terms of access control factors
>    as described below.

Delete this.  You say this again under B.2, except the "typically" is
left out.  I suggest you move B.2 above B.1, but put the last paragraph
of B.2 under B.1 instead of B.2.

> B.2. Access Control Factors
>
>    A request, when it is being processed by a server, may be associated
>    with a wide variety of security-related factors (section 4.2 of
>    [Protocol]). The server uses these factors to determine whether and
>    how to process the request. These are called access control factors
>    (ACFs). They might include source IP address, encryption strength,
>    the type of operation being requested, time of day, etc. Some
>    factors may be specific to the request itself, others may be
>    associated with the connection via which the request is transmitted,
>    others (e.g. time of day) may be "environmental".
>
>    Access control policies are expressed in terms of access control
>    factors. E.g., a request having ACFs i,j,k can perform operation Y
>    on resource Z. The set of ACFs that a server makes available for
>    such expressions is implementation-specific.

> Appendix C. RFC 2829 Change History
> Appendix D. RFC 2830 Change History

I presume most of these chapters will be deleted from the final RFC?
If so, will you keep the main changes and rename the chapters to
something like "Changes since RFC xxxx"?

-- 
Hallvard


From owner-ietf-ldapbis@OpenLDAP.org  Tue Oct 14 10:51: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 KAA13155
	for <ldapbis-archive@lists.ietf.org>; Tue, 14 Oct 2003 10:51:01 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9EEjYIG079143;
	Tue, 14 Oct 2003 14:49:49 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9EEei79078726;
	Tue, 14 Oct 2003 14:40:44 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 14 Oct 2003 14:40:44 +0000
Received: from pat.uio.no (IDENT:7411@pat.uio.no [129.240.130.16])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9EEeSHS078706
	for <ietf-ldapbis@openldap.org>; Tue, 14 Oct 2003 14:40:28 GMT
	(envelope-from hbf@bombur.uio.no)
Received: from mail-mx3.uio.no ([129.240.10.44])
	by pat.uio.no with esmtp (Exim 4.20)
	id 1A9QLZ-0005Tt-Fi
	for ietf-ldapbis@openldap.org; Tue, 14 Oct 2003 16:40:25 +0200
Received: from bombur.uio.no ([129.240.186.42])
	by mail-mx3.uio.no with esmtp (Exim 4.14)
	id 1A9QLT-0006P8-EA
	for ietf-ldapbis@openldap.org; Tue, 14 Oct 2003 16:40:19 +0200
Received: from hbf by bombur.uio.no with local (Exim 2.12 #7)
	id 1A9QLT-0003BV-00
	for ietf-ldapbis@OpenLDAP.org; Tue, 14 Oct 2003 16:40:19 +0200
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Message-Id: <HBF.2003101487b@bombur.uio.no>
To: ietf-ldapbis@OpenLDAP.org
Subject: updating as anonymous
Date: Tue, 14 Oct 2003 16:40:19 +0200
X-MailScanner-Information: This message has been scanned for viruses/spam. Contact postmaster@uio.no if you have questions about this scanning.
X-UiO-MailScanner: No virus found
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

I think this belongs in [Protocol], not in [authmeth]:

   6. Anonymous Authentication 

   Servers SHOULD NOT allow
   clients with anonymous authentication to modify directory entries or
   access sensitive information in directory entries.

This is about the update operations, not about the bind operation.

I guess the same applies to this:

   10. Security Considerations 

   Servers are encouraged to prevent modifications by anonymous users. 

though I don't think that's important.

-- 
Hallvard


From owner-ietf-ldapbis@OpenLDAP.org  Tue Oct 14 12:35: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 MAA18406
	for <ldapbis-archive@lists.ietf.org>; Tue, 14 Oct 2003 12:35:29 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9EGXeHW086139;
	Tue, 14 Oct 2003 16:34:07 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9EGV92q086062;
	Tue, 14 Oct 2003 16:31:09 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 14 Oct 2003 16:31:09 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9EGV1HS086047
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 14 Oct 2003 16:31:01 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from gypsy.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.9/8.12.9) with ESMTP id h9EGV0lg000366
	for <ietf-ldapbis@openldap.org>; Tue, 14 Oct 2003 16:31:00 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.0.22.0.20031014090108.03af1a28@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
Date: Tue, 14 Oct 2003 09:30:18 -0700
To: ietf-ldapbis@OpenLDAP.org
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: LDAPBIS @ IETF#58
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>

While the chairs hope that the WG can resolve most of the
remaining technical issues through list discussions, a few
may require face-to-face time to resolve. Hence, a request
for a one hour slot has been requested.

The chairs will publish an agenda after consulting with
editors as to which issues are believed to require
face-to-face time to resolve.  If you have issues which
you believe require face-to-face time to resolve, please
contact the chairs.

Kurt, LDAPBIS co-chair



From owner-ietf-ldapbis@OpenLDAP.org  Tue Oct 14 14:54: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 OAA23731
	for <ldapbis-archive@lists.ietf.org>; Tue, 14 Oct 2003 14:53:59 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9EIpaHW092314;
	Tue, 14 Oct 2003 18:52:32 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9EIncWS092174;
	Tue, 14 Oct 2003 18:49:38 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 14 Oct 2003 18:49:38 +0000
Received: from pat.uio.no (IDENT:7411@pat.uio.no [129.240.130.16])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9EInTHS092161
	for <ietf-ldapbis@openldap.org>; Tue, 14 Oct 2003 18:49:30 GMT
	(envelope-from hbf@bombur.uio.no)
Received: from mail-mx3.uio.no ([129.240.10.44])
	by pat.uio.no with esmtp (Exim 4.20)
	id 1A9UEY-0001zG-BX
	for ietf-ldapbis@openldap.org; Tue, 14 Oct 2003 20:49:26 +0200
Received: from bombur.uio.no ([129.240.186.42])
	by mail-mx3.uio.no with esmtp (Exim 4.14)
	id 1A9UEU-0003LY-6b
	for ietf-ldapbis@openldap.org; Tue, 14 Oct 2003 20:49:22 +0200
Received: from hbf by bombur.uio.no with local (Exim 2.12 #7)
	id 1A9UET-0003lo-00
	for ietf-ldapbis@OpenLDAP.org; Tue, 14 Oct 2003 20:49:21 +0200
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Message-Id: <HBF.20031014v2bd@bombur.uio.no>
To: ietf-ldapbis@OpenLDAP.org
Subject: Re: authmeth-07 issues
In-Reply-To: <HBF.20031014pk3@bombur.uio.no>
References: <HBF.20031014pk3@bombur.uio.no>
X-Mailer: VM 6.37 under Emacs 19.34.1
Date: Tue, 14 Oct 2003 20:49:21 +0200
X-MailScanner-Information: This message has been scanned for viruses/spam. Contact postmaster@uio.no if you have questions about this scanning.
X-UiO-MailScanner: No virus found
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

I just realized that my last message was written in a rather demanding
tone.  Sorry about that.  Didn't mean to appoint myself the dictator of
ldapbis.

-- 
Hallvard


From owner-ietf-ldapbis@OpenLDAP.org  Wed Oct 15 07:37:08 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 HAA25418
	for <ldapbis-archive@lists.ietf.org>; Wed, 15 Oct 2003 07:37:07 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9FBXgHW047847;
	Wed, 15 Oct 2003 11:34:29 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9FBTHiP047722;
	Wed, 15 Oct 2003 11:29:17 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 15 Oct 2003 11:29:17 +0000
Received: from pat.uio.no (IDENT:7411@pat.uio.no [129.240.130.16])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9FBTFHS047712
	for <ietf-ldapbis@openldap.org>; Wed, 15 Oct 2003 11:29:16 GMT
	(envelope-from hbf@bombur.uio.no)
Received: from mail-mx4.uio.no ([129.240.10.45])
	by pat.uio.no with esmtp (Exim 4.20)
	id 1A9jq4-0005vb-6f
	for ietf-ldapbis@openldap.org; Wed, 15 Oct 2003 13:29:12 +0200
Received: from bombur.uio.no ([129.240.186.42])
	by mail-mx4.uio.no with esmtp (Exim 4.14)
	id 1A9jpS-0004zt-4H
	for ietf-ldapbis@openldap.org; Wed, 15 Oct 2003 13:28:34 +0200
Received: from hbf by bombur.uio.no with local (Exim 2.12 #7)
	id 1A9jpR-0006H3-00
	for ietf-ldapbis@OpenLDAP.org; Wed, 15 Oct 2003 13:28:33 +0200
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Message-Id: <HBF.20031015ecya@bombur.uio.no>
To: ietf-ldapbis@OpenLDAP.org
Subject: Re: authmeth-07 issues
In-Reply-To: <HBF.20031014pk3@bombur.uio.no>
References: <HBF.20031014pk3@bombur.uio.no>
X-Mailer: VM 6.37 under Emacs 19.34.1
Date: Wed, 15 Oct 2003 13:28:33 +0200
X-MailScanner-Information: This message has been scanned for viruses/spam. Contact postmaster@uio.no if you have questions about this scanning.
X-UiO-MailScanner: No virus found
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

I wrote:

> State the effect of a failed SASL bind or a non-SASL bind on an existing
> SASL security layer.  I expect it would be something like this:
> 
>   A bindRequest (successful or not) which is not successfully abandoned,
>   cancels [is that the right word?] any previously established SASL
>   security layer, so that the bindResponse is sent without that layer.
> 
> [Or - if there are outstanding, possibly-abandoned requests, will the
> client know when the security layer gets cancelled?  Does the layer
> itself necessarily contain a "cancel" operation so the client can tell?]

Sorry, I was thinking of ease of SASL implementations when I wrote this.
A way which would be predictable is for the layer to be cancelled after
the server response.  I don't know _which_ server response though...
I'll take this to the SASL list (ietf-sasl@imc.org).

-- 
Hallvard


From owner-ietf-ldapbis@OpenLDAP.org  Tue Oct 21 01:23: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 BAA23758
	for <ldapbis-archive@lists.ietf.org>; Tue, 21 Oct 2003 01:23:31 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9L5GTHm070396;
	Tue, 21 Oct 2003 05:22:39 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9L5EgTW070363;
	Tue, 21 Oct 2003 05:14:42 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 21 Oct 2003 05:14:42 +0000
Received: from prv-mail20.provo.novell.com (prv-mail20.provo.novell.com [137.65.81.122])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9L5EdHS070318;
	Tue, 21 Oct 2003 05:14:39 GMT
	(envelope-from jimse@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Mon, 20 Oct 2003 23:14:18 -0600
Message-Id: <sf946c4a.047@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.2 Beta
Date: Mon, 20 Oct 2003 23:13:47 -0600
From: "Jim Sermersheim" <jimse@novell.com>
To: <steven.legg@adacel.com.au>, <Kurt@OpenLDAP.org>
Cc: <ietf-ldapbis@OpenLDAP.org>
Subject: RE: Steven's protocol comments
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__Part98C63E9B.1__="
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.

--=__Part98C63E9B.1__=
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

>>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 10/8/03 7:59:20 AM >>>
<snip>

>> 4.13.3.1. Graceful Closure 
>> The other party, if it receives a TLS closure alert, MUST
immediately 
>> transmit a TLS closure alert. It will subsequently cease to send TLS

>> ^^^^ MUST ?
>
>Please consider the replace text I offer in my comments. 

Kurt, I didn't see any replacement text in your comments for this
section.
 
 
Jim


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

<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 5.50.4933.1800" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Microsoft Sans Serif">
<DIV>&gt;&gt;&gt; "Kurt D. Zeilenga" &lt;Kurt@OpenLDAP.org&gt; 10/8/03 7:59:20 AM &gt;&gt;&gt;<BR>&lt;snip&gt;<BR><BR>&gt;&gt; 4.13.3.1. Graceful Closure </DIV>
<DIV>&gt;&gt; The other party, if it receives a TLS closure alert, MUST immediately <BR>&gt;&gt; transmit a TLS closure alert. It will subsequently cease to send TLS <BR>&gt;&gt; ^^^^ MUST ?<BR>&gt;<BR>&gt;Please consider the replace text I offer in my comments. <BR></DIV>
<DIV>Kurt, I didn't see any replacement text in your comments for this section.</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>Jim<BR></DIV></BODY></HTML>
--=__Part98C63E9B.1__=--


From owner-ietf-ldapbis@OpenLDAP.org  Tue Oct 21 01:41: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 BAA24085
	for <ldapbis-archive@lists.ietf.org>; Tue, 21 Oct 2003 01:41:19 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9L5eTHW071596;
	Tue, 21 Oct 2003 05:40:34 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9L5eB7i071580;
	Tue, 21 Oct 2003 05:40:11 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 21 Oct 2003 05:40:11 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9L5eAHS071570
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 21 Oct 2003 05:40:10 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from gypsy.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.9/8.12.9) with ESMTP id h9L5e8lg082256;
	Tue, 21 Oct 2003 05:40:08 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.0.22.0.20031020222524.03e67e28@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
Date: Mon, 20 Oct 2003 22:39:34 -0700
To: "Jim Sermersheim" <jimse@novell.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: RE: Steven's protocol comments
Cc: <steven.legg@adacel.com.au>, <ietf-ldapbis@OpenLDAP.org>
In-Reply-To: <sf946c4a.047@prv-mail20.provo.novell.com>
References: <sf946c4a.047@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 10:13 PM 10/20/2003, Jim Sermersheim wrote:
>>>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 10/8/03 7:59:20 AM >>>
><snip>
>
>>> 4.13.3.1. Graceful Closure 
>>> The other party, if it receives a TLS closure alert, MUST immediately 
>>> transmit a TLS closure alert. It will subsequently cease to send TLS 
>>> ^^^^ MUST ?
>>
>>Please consider the replace text I offer in my comments. 
>Kurt, I didn't see any replacement text in your comments for this section.

Sorry, how about?
        The other party, upon receipt of a TLS closure alert, SHALL
        immediately send a TLS closure alert and then terminate the
        TLS connection.   The LDAP connection remains established
        unless subsequently terminated.



From owner-ietf-ldapbis@OpenLDAP.org  Tue Oct 21 02:04: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 CAA29081
	for <ldapbis-archive@lists.ietf.org>; Tue, 21 Oct 2003 02:04:28 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9L5qTHw072345;
	Tue, 21 Oct 2003 06:03:43 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9L5naeN072281;
	Tue, 21 Oct 2003 05:49:36 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 21 Oct 2003 05:49:36 +0000
Received: from prv-mail20.provo.novell.com (prv-mail20.provo.novell.com [137.65.81.122])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9L5nYHS072251;
	Tue, 21 Oct 2003 05:49:34 GMT
	(envelope-from jimse@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Mon, 20 Oct 2003 23:49:13 -0600
Message-Id: <sf947479.071@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.2 Beta
Date: Mon, 20 Oct 2003 23:48:51 -0600
From: "Jim Sermersheim" <jimse@novell.com>
To: <Kurt@OpenLDAP.org>
Cc: <steven.legg@adacel.com.au>, <ietf-ldapbis@OpenLDAP.org>
Subject: RE: Steven's protocol comments
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__PartD8867ED3.1__="
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.

--=__PartD8867ED3.1__=
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Hmm, I think Steven needs to comment on why he was questioning the
MUST.

>>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 10/20/03 11:39:34 PM >>>
At 10:13 PM 10/20/2003, Jim Sermersheim wrote:
>>>> "Kurt D. Zeilenga" < Kurt@OpenLDAP.org > 10/8/03 7:59:20 AM >>>
><snip>
>
>>> 4.13.3.1. Graceful Closure 
>>> The other party, if it receives a TLS closure alert, MUST
immediately 
>>> transmit a TLS closure alert. It will subsequently cease to send
TLS 
>>> ^^^^ MUST ?
>>
>>Please consider the replace text I offer in my comments. 
>Kurt, I didn't see any replacement text in your comments for this
section.

Sorry, how about?
The other party, upon receipt of a TLS closure alert, SHALL
immediately send a TLS closure alert and then terminate the
TLS connection. The LDAP connection remains established
unless subsequently terminated.


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

<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 5.50.4933.1800" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Microsoft Sans Serif">Hmm, I think Steven needs to comment on why he was questioning the MUST.<BR><BR>&gt;&gt;&gt; "Kurt D. Zeilenga" &lt;Kurt@OpenLDAP.org&gt; 10/20/03 11:39:34 PM &gt;&gt;&gt;<BR>At 10:13 PM 10/20/2003, Jim Sermersheim wrote:<BR>&gt;&gt;&gt;&gt; "Kurt D. Zeilenga" &lt;<U> <A href="mailto:Kurt@OpenLDAP.org">Kurt@OpenLDAP.org</A></U> &gt; 10/8/03 7:59:20 AM &gt;&gt;&gt;<BR>&gt;&lt;snip&gt;<BR>&gt;<BR>&gt;&gt;&gt; 4.13.3.1. Graceful Closure <BR>&gt;&gt;&gt; The other party, if it receives a TLS closure alert, MUST immediately <BR>&gt;&gt;&gt; transmit a TLS closure alert. It will subsequently cease to send TLS <BR>&gt;&gt;&gt; ^^^^ MUST ?<BR>&gt;&gt;<BR>&gt;&gt;Please consider the replace text I offer in my comments. <BR>&gt;Kurt, I didn't see any replacement text in your comments for this section.<BR><BR>Sorry, how about?<BR>The other party, upon receipt of a TLS closure alert, SHALL<BR>immediately send a TLS closu!
 re alert and then terminate the<BR>TLS connection. The LDAP connection remains established<BR>unless subsequently terminated.<BR><BR></BODY></HTML>
--=__PartD8867ED3.1__=--


From owner-ietf-ldapbis@OpenLDAP.org  Tue Oct 21 02:05: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 CAA00228
	for <ldapbis-archive@lists.ietf.org>; Tue, 21 Oct 2003 02:05:37 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9L5wSHm072643;
	Tue, 21 Oct 2003 06:04:37 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9L5qVwB072374;
	Tue, 21 Oct 2003 05:52:31 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 21 Oct 2003 05:52:31 +0000
Received: from prv-mail20.provo.novell.com (prv-mail20.provo.novell.com [137.65.81.122])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9L5qSHS072336;
	Tue, 21 Oct 2003 05:52:28 GMT
	(envelope-from jimse@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Mon, 20 Oct 2003 23:52:08 -0600
Message-Id: <sf947528.088@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.2 Beta
Date: Mon, 20 Oct 2003 23:51:45 -0600
From: "Jim Sermersheim" <jimse@novell.com>
To: <Kurt@OpenLDAP.org>
Cc: <steven.legg@adacel.com.au>, <ietf-ldapbis@OpenLDAP.org>
Subject: RE: Steven's protocol comments
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__Part6B35CD61.1__="
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.

--=__Part6B35CD61.1__=
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

I'm assuming that Steven had an issue with the fact that we're requiring
a protocol peer to send back a TLS closure alert, when really the
recipient may wish to just close the underlying connection. My current
wording basically says that if the recipient of the initial TLS closure
alert wishes to allow the underlying LDAP connection, *then* it must
immediately send its own TLS closure alter, etc.
 
Jim

>>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 10/20/03 11:39:34 PM >>>
At 10:13 PM 10/20/2003, Jim Sermersheim wrote:
>>>> "Kurt D. Zeilenga" < Kurt@OpenLDAP.org > 10/8/03 7:59:20 AM >>>
><snip>
>
>>> 4.13.3.1. Graceful Closure 
>>> The other party, if it receives a TLS closure alert, MUST
immediately 
>>> transmit a TLS closure alert. It will subsequently cease to send
TLS 
>>> ^^^^ MUST ?
>>
>>Please consider the replace text I offer in my comments. 
>Kurt, I didn't see any replacement text in your comments for this
section.

Sorry, how about?
The other party, upon receipt of a TLS closure alert, SHALL
immediately send a TLS closure alert and then terminate the
TLS connection. The LDAP connection remains established
unless subsequently terminated.



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

<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 5.50.4933.1800" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Microsoft Sans Serif">
<DIV>I'm assuming that Steven had an issue with the fact that we're requiring a protocol peer to send back a TLS closure alert, when really the recipient may wish to just close the underlying connection. My current wording basically says that if the recipient of the initial TLS closure alert wishes to allow the underlying LDAP connection, *then* it must immediately send its own TLS closure alter, etc.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Jim<BR><BR>&gt;&gt;&gt; "Kurt D. Zeilenga" &lt;Kurt@OpenLDAP.org&gt; 10/20/03 11:39:34 PM &gt;&gt;&gt;<BR>At 10:13 PM 10/20/2003, Jim Sermersheim wrote:<BR>&gt;&gt;&gt;&gt; "Kurt D. Zeilenga" &lt;<U> <A href="mailto:Kurt@OpenLDAP.org">Kurt@OpenLDAP.org</A></U> &gt; 10/8/03 7:59:20 AM &gt;&gt;&gt;<BR>&gt;&lt;snip&gt;<BR>&gt;<BR>&gt;&gt;&gt; 4.13.3.1. Graceful Closure <BR>&gt;&gt;&gt; The other party, if it receives a TLS closure alert, MUST immediately <BR>&gt;&gt;&gt; transmit a TLS closure alert. It will subsequently cease to send TLS <BR>&gt;&gt;&gt; ^^^^ MUST ?<BR>&gt;&gt;<BR>&gt;&gt;Please consider the replace text I offer in my comments. <BR>&gt;Kurt, I didn't see any replacement text in your comments for this section.<BR><BR>Sorry, how about?<BR>The other party, upon receipt of a TLS closure alert, SHALL<BR>immediately send a TLS closure alert and then terminate the<BR>TLS connection. The LDAP connection remains established<BR>unless subsequently terminated.<BR><B!
 R></DIV></BODY></HTML>
--=__Part6B35CD61.1__=--


From owner-ietf-ldapbis@OpenLDAP.org  Tue Oct 21 02:17: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 CAA07190
	for <ldapbis-archive@lists.ietf.org>; Tue, 21 Oct 2003 02:17:10 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9L6GTHa074612;
	Tue, 21 Oct 2003 06:16:34 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9L6EN7j074523;
	Tue, 21 Oct 2003 06:14:23 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 21 Oct 2003 06:14:23 +0000
Received: from prv-mail20.provo.novell.com (prv-mail20.provo.novell.com [137.65.81.122])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9L6EKHS074487;
	Tue, 21 Oct 2003 06:14:20 GMT
	(envelope-from jimse@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Tue, 21 Oct 2003 00:14:00 -0600
Message-Id: <sf947a48.068@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.2 Beta
Date: Tue, 21 Oct 2003 00:13:26 -0600
From: "Jim Sermersheim" <jimse@novell.com>
To: <Kurt@OpenLDAP.org>
Cc: <steven.legg@adacel.com.au>, <ietf-ldapbis@OpenLDAP.org>
Subject: RE: Steven's protocol comments
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__Part9BC53D96.1__="
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.

--=__Part9BC53D96.1__=
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Ok, I finally read Steven's comments with a fixed pitch font so I could
see what he was *actually* pointing out. He was asking if the "will"
shoul dbe a MUST, which your re-wording does seem to cover.
 
Sorry for the noise.

>>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 10/20/03 11:39:34 PM >>>
At 10:13 PM 10/20/2003, Jim Sermersheim wrote:
>>>> "Kurt D. Zeilenga" < Kurt@OpenLDAP.org > 10/8/03 7:59:20 AM >>>
><snip>
>
>>> 4.13.3.1. Graceful Closure 
>>> The other party, if it receives a TLS closure alert, MUST
immediately 
>>> transmit a TLS closure alert. It will subsequently cease to send
TLS 
>>> ^^^^ MUST ?
>>
>>Please consider the replace text I offer in my comments. 
>Kurt, I didn't see any replacement text in your comments for this
section.

Sorry, how about?
The other party, upon receipt of a TLS closure alert, SHALL
immediately send a TLS closure alert and then terminate the
TLS connection. The LDAP connection remains established
unless subsequently terminated.



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

<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 5.50.4933.1800" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Microsoft Sans Serif">
<DIV>Ok, I finally read Steven's comments with a fixed pitch font so I could see what he was *actually* pointing out. He was asking if the "will" shoul dbe a MUST, which your re-wording does seem to cover.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Sorry for the noise.<BR><BR>&gt;&gt;&gt; "Kurt D. Zeilenga" &lt;Kurt@OpenLDAP.org&gt; 10/20/03 11:39:34 PM &gt;&gt;&gt;<BR>At 10:13 PM 10/20/2003, Jim Sermersheim wrote:<BR>&gt;&gt;&gt;&gt; "Kurt D. Zeilenga" &lt;<U> <A href="mailto:Kurt@OpenLDAP.org">Kurt@OpenLDAP.org</A></U> &gt; 10/8/03 7:59:20 AM &gt;&gt;&gt;<BR>&gt;&lt;snip&gt;<BR>&gt;<BR>&gt;&gt;&gt; 4.13.3.1. Graceful Closure <BR>&gt;&gt;&gt; The other party, if it receives a TLS closure alert, MUST immediately <BR>&gt;&gt;&gt; transmit a TLS closure alert. It will subsequently cease to send TLS <BR>&gt;&gt;&gt; ^^^^ MUST ?<BR>&gt;&gt;<BR>&gt;&gt;Please consider the replace text I offer in my comments. <BR>&gt;Kurt, I didn't see any replacement text in your comments for this section.<BR><BR>Sorry, how about?<BR>The other party, upon receipt of a TLS closure alert, SHALL<BR>immediately send a TLS closure alert and then terminate the<BR>TLS connection. The LDAP connection remains established<BR>unless subsequently !
 terminated.<BR><BR></DIV></BODY></HTML>
--=__Part9BC53D96.1__=--


From owner-ietf-ldapbis@OpenLDAP.org  Tue Oct 21 02:17: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 CAA07242
	for <ldapbis-archive@lists.ietf.org>; Tue, 21 Oct 2003 02:17:25 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9L6GTHc074612;
	Tue, 21 Oct 2003 06:16:34 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9L6DFli074420;
	Tue, 21 Oct 2003 06:13:15 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 21 Oct 2003 06:13:15 +0000
Received: from adacel.com (gunsmoke.adacel.com.au [210.11.130.7])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9L6DDHS074391
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 21 Oct 2003 06:13:13 GMT
	(envelope-from steven.legg@adacel.com.au)
Received: from nexus.adacel.com (Not Verified[10.32.240.1]) by adacel.com with NetIQ MailMarshal (v5.5.3.16)
	id <B000185e83>; Tue, 21 Oct 2003 16:07:13 +1000
Received: (qmail 15639 invoked from network); 21 Oct 2003 06:12:51 -0000
Received: from unknown (HELO adacel.com.au) (10.32.24.165)
  by nexus.adacel.com with SMTP; 21 Oct 2003 06:12:51 -0000
Message-ID: <3F94CE62.3010104@adacel.com.au>
Date: Tue, 21 Oct 2003 17:12:50 +1100
From: Steven Legg <steven.legg@adacel.com.au>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3.1) Gecko/20030425
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Jim Sermersheim <jimse@novell.com>
CC: Kurt@OpenLDAP.org, ietf-ldapbis@OpenLDAP.org
Subject: Re: Steven's protocol comments
References: <sf947479.069@prv-mail20.provo.novell.com>
In-Reply-To: <sf947479.069@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


Jim,

I was actually questioning the "It will subsequently cease", but
the pointer got moved by all the quoting. The sentence looked like an
implementation imperative in which case I was suggesting a rewording
to "It MUST subsequently cease". Kurt's rewording resolves my (minor)
concern.

Regards,
Steven

Jim Sermersheim wrote:
> Hmm, I think Steven needs to comment on why he was questioning the MUST.
> 
>  >>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 10/20/03 11:39:34 PM >>>
> At 10:13 PM 10/20/2003, Jim Sermersheim wrote:
>  >>>> "Kurt D. Zeilenga" <_ Kurt@OpenLDAP.org 
> <mailto:Kurt@OpenLDAP.org>_ > 10/8/03 7:59:20 AM >>>
>  ><snip>
>  >
>  >>> 4.13.3.1. Graceful Closure
>  >>> The other party, if it receives a TLS closure alert, MUST immediately
>  >>> transmit a TLS closure alert. It will subsequently cease to send TLS
>  >>> ^^^^ MUST ?
>  >>
>  >>Please consider the replace text I offer in my comments.
>  >Kurt, I didn't see any replacement text in your comments for this section.
> 
> Sorry, how about?
> The other party, upon receipt of a TLS closure alert, SHALL
> immediately send a TLS closure alert and then terminate the
> TLS connection. The LDAP connection remains established
> unless subsequently terminated.
> 



From owner-ietf-ldapbis@OpenLDAP.org  Tue Oct 21 02:47: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 CAA08262
	for <ldapbis-archive@lists.ietf.org>; Tue, 21 Oct 2003 02:47:22 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9L6kTHW076506;
	Tue, 21 Oct 2003 06:46:37 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9L6jJ1p076429;
	Tue, 21 Oct 2003 06:45:19 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 21 Oct 2003 06:45:19 +0000
Received: from prv-mail20.provo.novell.com (prv-mail20.provo.novell.com [137.65.81.122])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9L6jGHS076392;
	Tue, 21 Oct 2003 06:45:16 GMT
	(envelope-from jimse@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Tue, 21 Oct 2003 00:44:56 -0600
Message-Id: <sf948188.085@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.2 Beta
Date: Tue, 21 Oct 2003 00:44:27 -0600
From: "Jim Sermersheim" <jimse@novell.com>
To: <steven.legg@adacel.com.au>, <Kurt@OpenLDAP.org>
Cc: <ietf-ldapbis@OpenLDAP.org>
Subject: RE: Steven's protocol comments
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__PartCD936BDB.1__="
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.

--=__PartCD936BDB.1__=
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

>>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 10/8/03 7:59:20 AM >>>
<SNIP>
>> If the client wishes to progress the operation, it MUST follow the 
>> referral by contacting one of the servers.
>>
>>"If" and "MUST" make this an effective "MAY", e.g.
>>
>> "The Client MAY progress the operation by following the referral
and
>> contacting one of the servers."
>
>I think this MAY could be downcased.

First, I don't agree that the If and MUST equals a MAY. It says that
"If X is to happen, Y MUST be done"
 
Second (which makes my first statement moot), I agree that this doesn't
seem to have interoperability repercussions, so a rewording and removal
of MUST seems appropriate.
 
Jim

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

<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 5.50.4933.1800" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Microsoft Sans Serif">
<DIV>&gt;&gt;&gt; "Kurt D. Zeilenga" &lt;Kurt@OpenLDAP.org&gt; 10/8/03 7:59:20 AM &gt;&gt;&gt;<BR>&lt;SNIP&gt;</DIV>
<DIV>&gt;&gt; If the client wishes to progress the operation, it MUST follow the <BR>&gt;&gt; referral by contacting one of the servers.<BR>&gt;&gt;<BR>&gt;&gt;"If" and "MUST" make this an effective "MAY", e.g.<BR>&gt;&gt;<BR>&gt;&gt; "The Client MAY progress the operation by following the referral and<BR>&gt;&gt; contacting one of the servers."<BR>&gt;<BR>&gt;I think this MAY could be downcased.<BR></DIV>
<DIV>First, I don't agree that the If and MUST equals a MAY. It says that "If X is to happen, Y MUST be done"</DIV>
<DIV>&nbsp;</DIV>
<DIV>Second (which makes my first&nbsp;statement moot), I agree that this doesn't seem to have interoperability repercussions, so a rewording and removal of MUST seems appropriate.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Jim</DIV></BODY></HTML>
--=__PartCD936BDB.1__=--


From owner-ietf-ldapbis@OpenLDAP.org  Tue Oct 21 23:07: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 XAA25161
	for <ldapbis-archive@lists.ietf.org>; Tue, 21 Oct 2003 23:07:12 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9M34cHW091706;
	Wed, 22 Oct 2003 03:05:25 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9M324CO091608;
	Wed, 22 Oct 2003 03:02:04 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 22 Oct 2003 03:02:04 +0000
Received: from prv-mail20.provo.novell.com (prv-mail20.provo.novell.com [137.65.81.122])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9M320HS091574;
	Wed, 22 Oct 2003 03:02:00 GMT
	(envelope-from jimse@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Tue, 21 Oct 2003 21:01:40 -0600
Message-Id: <sf959eb4.022@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.2 Beta
Date: Tue, 21 Oct 2003 21:01:23 -0600
From: "Jim Sermersheim" <jimse@novell.com>
To: <ietf-ldapbis@OpenLDAP.org>, <Kurt@OpenLDAP.org>
Subject: Re: REVISED protocol review notes [LONG]
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__Part227C8513.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>

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.

--=__Part227C8513.0__=
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

>>> Kurt Zeilenga <Kurt@OpenLDAP.org> 10/7/03 3:48:43 PM >>>
>>    
>>        Attribute ::= SEQUENCE { 
>>                type    AttributeDescription, 
>>                vals    SET OF AttributeValue } 
>>    
>>   Each attribute value is distinct in the set (no duplicates). The
set 
>>   of attribute values is unordered. Implementations MUST NOT reply
upon 
>>   any apparent ordering being repeatable. 
>>    
>
>This type is never explicitly used in the protocol.  
 
It is the type for ModifyRequest.changes.modification

--=__Part227C8513.0__=
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 5.50.4933.1800" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Microsoft Sans Serif">
<DIV>&gt;&gt;&gt; Kurt Zeilenga &lt;Kurt@OpenLDAP.org&gt; 10/7/03 3:48:43 PM &gt;&gt;&gt;<BR>&gt;&gt;&nbsp;&nbsp;&nbsp; <BR>&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Attribute ::= SEQUENCE { <BR>&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; type&nbsp;&nbsp;&nbsp; AttributeDescription, <BR>&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; vals&nbsp;&nbsp;&nbsp; SET OF AttributeValue } <BR>&gt;&gt;&nbsp;&nbsp;&nbsp; <BR>&gt;&gt;&nbsp;&nbsp; Each attribute value is distinct in the set (no duplicates). The set <BR>&gt;&gt;&nbsp;&nbsp; of attribute values is unordered. Implementations MUST NOT reply upon <BR>&gt;&gt;&nbsp;&nbsp; any apparent ordering being repeatable. <BR>&gt;&gt;&nbsp;&nbsp;&nbsp; <BR>&gt;<BR>&gt;This type is never explicitly used in the protocol.&nbsp; </DIV>
<DIV>&nbsp;</DIV>
<DIV>It is the type for ModifyRequest.changes.modification</DIV></BODY></HTML>
--=__Part227C8513.0__=--


From owner-ietf-ldapbis@OpenLDAP.org  Tue Oct 21 23:23: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 XAA25646
	for <ldapbis-archive@lists.ietf.org>; Tue, 21 Oct 2003 23:23:40 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9M3MaHm092593;
	Wed, 22 Oct 2003 03:22:45 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9M3HtfY092173;
	Wed, 22 Oct 2003 03:17:55 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 22 Oct 2003 03:17:55 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9M3HoHS092159
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 22 Oct 2003 03:17:54 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from gypsy.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.9/8.12.9) with ESMTP id h9M3Hjlg096689;
	Wed, 22 Oct 2003 03:17:45 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.0.22.0.20031021201414.03e81e48@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
Date: Tue, 21 Oct 2003 20:17:11 -0700
To: "Jim Sermersheim" <jimse@novell.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: REVISED protocol review notes [LONG]
Cc: <ietf-ldapbis@OpenLDAP.org>
In-Reply-To: <sf959eb4.022@prv-mail20.provo.novell.com>
References: <sf959eb4.022@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:01 PM 10/21/2003, Jim Sermersheim wrote:
>>>> Kurt Zeilenga <Kurt@OpenLDAP.org> 10/7/03 3:48:43 PM >>>
>>>    
>>>        Attribute ::= SEQUENCE { 
>>>                type    AttributeDescription, 
>>>                vals    SET OF AttributeValue } 
>>>    
>>>   Each attribute value is distinct in the set (no duplicates). The set 
>>>   of attribute values is unordered. Implementations MUST NOT reply upon 
>>>   any apparent ordering being repeatable. 
>>>    
>>
>>This type is never explicitly used in the protocol.  
> 
>It is the type for ModifyRequest.changes.modification

Okay... but I note that ModifyRequest.changes.modification is
a partial attribute.   I assume your other changes to clarify
Attribute may be partial will lead to PartialAttributeList
fading away.

Kurt




From owner-ietf-ldapbis@OpenLDAP.org  Tue Oct 21 23:53: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 XAA26286
	for <ldapbis-archive@lists.ietf.org>; Tue, 21 Oct 2003 23:53:30 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9M3qaHa093884;
	Wed, 22 Oct 2003 03:52:47 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9M3os6I093866;
	Wed, 22 Oct 2003 03:50:54 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 22 Oct 2003 03:50:54 +0000
Received: from prv-mail20.provo.novell.com (prv-mail20.provo.novell.com [137.65.81.122])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9M3opHS093835;
	Wed, 22 Oct 2003 03:50:51 GMT
	(envelope-from jimse@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Tue, 21 Oct 2003 21:50:31 -0600
Message-Id: <sf95aa27.025@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.2 Beta
Date: Tue, 21 Oct 2003 21:50:11 -0600
From: "Jim Sermersheim" <jimse@novell.com>
To: <Kurt@OpenLDAP.org>
Cc: <ietf-ldapbis@OpenLDAP.org>
Subject: Re: REVISED protocol review notes [LONG]
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

Actually my current plan is to define both:
     Attribute ::= SEQUENCE {
             type    AttributeDescription,
             vals    SET SIZE (1..MAX) OF AttributeValue }
and
     PartialAttribute ::= SEQUENCE {
             type    AttributeDescription,
             vals    SET OF AttributeValue }

and use them in the appropriate places.

Does this sound reasonable?

Jim

>>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 10/21/03 9:17:11 PM >>>
At 08:01 PM 10/21/2003, Jim Sermersheim wrote:
>>>> Kurt Zeilenga < Kurt@OpenLDAP.org > 10/7/03 3:48:43 PM >>>
>>> 
>>> Attribute ::= SEQUENCE { 
>>> type AttributeDescription, 
>>> vals SET OF AttributeValue } 
>>> 
>>> Each attribute value is distinct in the set (no duplicates). The
set 
>>> of attribute values is unordered. Implementations MUST NOT reply
upon 
>>> any apparent ordering being repeatable. 
>>> 
>>
>>This type is never explicitly used in the protocol. 
> 
>It is the type for ModifyRequest.changes.modification

Okay... but I note that ModifyRequest.changes.modification is
a partial attribute. I assume your other changes to clarify
Attribute may be partial will lead to PartialAttributeList
fading away.

Kurt





From owner-ietf-ldapbis@OpenLDAP.org  Tue Oct 21 23:53:34 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 XAA26304
	for <ldapbis-archive@lists.ietf.org>; Tue, 21 Oct 2003 23:53:33 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9M3qaHc093884;
	Wed, 22 Oct 2003 03:52:47 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9M3lXc1093682;
	Wed, 22 Oct 2003 03:47:33 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 22 Oct 2003 03:47:33 +0000
Received: from prv-mail20.provo.novell.com (prv-mail20.provo.novell.com [137.65.81.122])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9M3lWHS093671
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 22 Oct 2003 03:47:32 GMT
	(envelope-from jimse@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Tue, 21 Oct 2003 21:47:11 -0600
Message-Id: <sf95a95f.001@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.2 Beta
Date: Tue, 21 Oct 2003 21:46:55 -0600
From: "Jim Sermersheim" <jimse@novell.com>
To: <steven.legg@adacel.com.au>, <ietf-ldapbis@OpenLDAP.org>
Subject: RE: WG Last Call: draft-ietf-ldapbis-protocol-17.txt
	[corrected]
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

>>> "Steven Legg" <steven.legg@adacel.com.au> 10/5/03 11:50:20 PM >>>
>> 4.6. Modify Operation 
>
>>    Parameters of the Modify Request are: 
>>     
>>    - object: The object to be modified. The value of this field 
>>      contains the DN of the entry to be modified. The server will
not 
>                                                              
^^^^^^^^
>SHALL NOT ?

These are all on many operations. I think SHALL NOT is too strong. I
suspect there are implementations that allow the alias to be
dereferenced (whether by control, local policy, or both).

Do you think there is an interoperability issue here? If so, would
SHOULD NOT suffice?

Jim


From owner-ietf-ldapbis@OpenLDAP.org  Wed Oct 22 00:29: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 AAA27028
	for <ldapbis-archive@lists.ietf.org>; Wed, 22 Oct 2003 00:29:47 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9M4GbI6094962;
	Wed, 22 Oct 2003 04:29:01 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9M4CsRa094805;
	Wed, 22 Oct 2003 04:12:54 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 22 Oct 2003 04:12:54 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9M4CqHS094794
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 22 Oct 2003 04:12:52 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from gypsy.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.9/8.12.9) with ESMTP id h9M4Colg097121;
	Wed, 22 Oct 2003 04:12:50 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.0.22.0.20031021205409.03ea1048@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
Date: Tue, 21 Oct 2003 21:12:15 -0700
To: "Jim Sermersheim" <jimse@novell.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: REVISED protocol review notes [LONG]
Cc: <ietf-ldapbis@OpenLDAP.org>
In-Reply-To: <sf95aa27.025@prv-mail20.provo.novell.com>
References: <sf95aa27.025@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:50 PM 10/21/2003, Jim Sermersheim wrote:
>Actually my current plan is to define both:
>     Attribute ::= SEQUENCE {
>             type    AttributeDescription,
>             vals    SET SIZE (1..MAX) OF AttributeValue }
>and
>     PartialAttribute ::= SEQUENCE {
>             type    AttributeDescription,
>             vals    SET OF AttributeValue }
>
>and use them in the appropriate places.
>Does this sound reasonable?

Well, I had thought this made sense (as I suggest in my notes).

However, as almost all uses should be PartialAttribute
and not Attribute, it may make more sense just to have
Attribute and make it more clear that all uses allow can
be partial (not all values) and a few uses allow it to be
empty (no values).

(objectClass is an example of an attribute where not all
values are required to be transferred.)

Kurt



From owner-ietf-ldapbis@OpenLDAP.org  Wed Oct 22 00:37: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 AAA27181
	for <ldapbis-archive@lists.ietf.org>; Wed, 22 Oct 2003 00:37:36 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9M4YeHa097900;
	Wed, 22 Oct 2003 04:37:02 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9M4VOqW097097;
	Wed, 22 Oct 2003 04:31:24 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 22 Oct 2003 04:31:24 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9M4VMHS097083
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 22 Oct 2003 04:31:22 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from gypsy.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.9/8.12.9) with ESMTP id h9M4VFlg097362;
	Wed, 22 Oct 2003 04:31:15 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.0.22.0.20031021211747.03e8faf8@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
Date: Tue, 21 Oct 2003 21:30:40 -0700
To: "Jim Sermersheim" <jimse@novell.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: RE: WG Last Call: draft-ietf-ldapbis-protocol-17.txt
  [corrected]
Cc: <steven.legg@adacel.com.au>, <ietf-ldapbis@OpenLDAP.org>
In-Reply-To: <sf95a95f.001@prv-mail20.provo.novell.com>
References: <sf95a95f.001@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:46 PM 10/21/2003, Jim Sermersheim wrote:
>>>> "Steven Legg" <steven.legg@adacel.com.au> 10/5/03 11:50:20 PM >>>
>>> 4.6. Modify Operation 
>>
>>>    Parameters of the Modify Request are: 
>>>     
>>>    - object: The object to be modified. The value of this field 
>>>      contains the DN of the entry to be modified. The server will
>not 
>>                                                              
>^^^^^^^^
>>SHALL NOT ?
>
>These are all on many operations. I think SHALL NOT is too strong. I
>suspect there are implementations that allow the alias to be
>dereferenced (whether by control, local policy, or both).
>
>Do you think there is an interoperability issue here? If so, would
>SHOULD NOT suffice?

I think, no.  A server which deferences the alias not only
prevents modification of the the alias object, it might
(quite inappropriately) modify the aliased object.  A
SHALL NOT here is appropriate as without it one could
not administrate alias objects in an interoperable fashion.
This applies to all other update operations as well.

Kurt 



From owner-ietf-ldapbis@OpenLDAP.org  Wed Oct 22 01:19: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 BAA28050
	for <ldapbis-archive@lists.ietf.org>; Wed, 22 Oct 2003 01:19:25 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9M5GfHW099459;
	Wed, 22 Oct 2003 05:17:28 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9M5GBH9099448;
	Wed, 22 Oct 2003 05:16:11 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 22 Oct 2003 05:16:11 +0000
Received: from prv-mail20.provo.novell.com (prv-mail20.provo.novell.com [137.65.81.122])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9M5G5HS099355;
	Wed, 22 Oct 2003 05:16:06 GMT
	(envelope-from jimse@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Tue, 21 Oct 2003 23:15:45 -0600
Message-Id: <sf95be21.079@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.2 Beta
Date: Tue, 21 Oct 2003 23:15:31 -0600
From: "Jim Sermersheim" <jimse@novell.com>
To: <Kurt@OpenLDAP.org>
Cc: <ietf-ldapbis@OpenLDAP.org>
Subject: Re: REVISED protocol review notes [LONG]
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__PartB0EE1463.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>

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.

--=__PartB0EE1463.0__=
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

I have Attribute (at least one attribute value) being used by
AttributeList, which is used by AddRequest.
 
You're not saying that objectClass may have zero values in an add
request are you?
 
I have PartialAttribute being used by PartialAttributeList and by
ModifyRequest.changes.modification.
 
We could pare it down to a single definition (without the SIZE), and
add documentation where its needed, but these two definitions are more
precise.
 
Jim
 
>>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 10/21/03 10:12:15 PM >>>
At 08:50 PM 10/21/2003, Jim Sermersheim wrote:
>Actually my current plan is to define both:
> Attribute ::= SEQUENCE {
> type AttributeDescription,
> vals SET SIZE (1..MAX) OF AttributeValue }
>and
> PartialAttribute ::= SEQUENCE {
> type AttributeDescription,
> vals SET OF AttributeValue }
>
>and use them in the appropriate places.
>Does this sound reasonable?

Well, I had thought this made sense (as I suggest in my notes).

However, as almost all uses should be PartialAttribute
and not Attribute, it may make more sense just to have
Attribute and make it more clear that all uses allow can
be partial (not all values) and a few uses allow it to be
empty (no values).

(objectClass is an example of an attribute where not all
values are required to be transferred.)

Kurt



--=__PartB0EE1463.0__=
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 5.50.4933.1800" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Microsoft Sans Serif">
<DIV>I have Attribute (at least one attribute value) being used by AttributeList, which is used by AddRequest.</DIV>
<DIV>&nbsp;</DIV>
<DIV>You're not saying that objectClass may have zero values in an add request are you?</DIV>
<DIV>&nbsp;</DIV>
<DIV>I have PartialAttribute being used by PartialAttributeList and by ModifyRequest.changes.modification.</DIV>
<DIV>&nbsp;</DIV>
<DIV>We could pare it down to a single definition (without the SIZE), and add documentation where its needed, but these two definitions are&nbsp;more precise.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Jim</DIV>
<DIV>&nbsp;</DIV>
<DIV>&gt;&gt;&gt; "Kurt D. Zeilenga" &lt;Kurt@OpenLDAP.org&gt; 10/21/03 10:12:15 PM &gt;&gt;&gt;<BR>At 08:50 PM 10/21/2003, Jim Sermersheim wrote:<BR>&gt;Actually my current plan is to define both:<BR>&gt; Attribute ::= SEQUENCE {<BR>&gt; type AttributeDescription,<BR>&gt; vals SET SIZE (1..MAX) OF AttributeValue }<BR>&gt;and<BR>&gt; PartialAttribute ::= SEQUENCE {<BR>&gt; type AttributeDescription,<BR>&gt; vals SET OF AttributeValue }<BR>&gt;<BR>&gt;and use them in the appropriate places.<BR>&gt;Does this sound reasonable?<BR><BR>Well, I had thought this made sense (as I suggest in my notes).<BR><BR>However, as almost all uses should be PartialAttribute<BR>and not Attribute, it may make more sense just to have<BR>Attribute and make it more clear that all uses allow can<BR>be partial (not all values) and a few uses allow it to be<BR>empty (no values).<BR><BR>(objectClass is an example of an attribute where not all<BR>values are required to be transferred.)<BR><BR>Kurt<BR><BR!
 ></DIV></BODY></HTML>
--=__PartB0EE1463.0__=--


From owner-ietf-ldapbis@OpenLDAP.org  Wed Oct 22 01:54: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 BAA28652
	for <ldapbis-archive@lists.ietf.org>; Wed, 22 Oct 2003 01:54:31 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9M5qbHW000881;
	Wed, 22 Oct 2003 05:53:39 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9M5mdOM000775;
	Wed, 22 Oct 2003 05:48:39 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 22 Oct 2003 05:48:39 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9M5mYHS000759
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 22 Oct 2003 05:48:38 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from gypsy.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.9/8.12.9) with ESMTP id h9M5mXlg097827;
	Wed, 22 Oct 2003 05:48:33 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.0.22.0.20031021224342.03eca5a8@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
Date: Tue, 21 Oct 2003 22:47:59 -0700
To: "Jim Sermersheim" <jimse@novell.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: REVISED protocol review notes [LONG]
Cc: <ietf-ldapbis@OpenLDAP.org>
In-Reply-To: <sf95be21.079@prv-mail20.provo.novell.com>
References: <sf95be21.079@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>

I'm fine with having both... having the explicit size constraint on
AddRequest.attributes will be nice.

At 10:15 PM 10/21/2003, Jim Sermersheim wrote:
>You're not saying that objectClass may have zero values in an add request are you?

No.  Just saying that Attribute can be partial in the sense of
not holding all values.

Kurt 



From owner-ietf-ldapbis@OpenLDAP.org  Wed Oct 22 03:11: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 DAA27161
	for <ldapbis-archive@lists.ietf.org>; Wed, 22 Oct 2003 03:11:00 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9M74bHW007181;
	Wed, 22 Oct 2003 07:07:31 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9M73Asr007125;
	Wed, 22 Oct 2003 07:03:10 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 22 Oct 2003 07:03:10 +0000
Received: from adacel.com (gunsmoke.adacel.com.au [210.11.130.7])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9M734HS007098
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 22 Oct 2003 07:03:08 GMT
	(envelope-from steven.legg@adacel.com.au)
Received: from nexus.adacel.com (Not Verified[10.32.240.1]) by adacel.com with NetIQ MailMarshal (v5.5.3.16)
	id <B0001873db>; Wed, 22 Oct 2003 16:56:56 +1000
Received: (qmail 9962 invoked from network); 22 Oct 2003 07:02:42 -0000
Received: from unknown (HELO adacel.com.au) (10.32.24.165)
  by nexus.adacel.com with SMTP; 22 Oct 2003 07:02:42 -0000
Message-ID: <3F962B91.9080608@adacel.com.au>
Date: Wed, 22 Oct 2003 18:02:41 +1100
From: Steven Legg <steven.legg@adacel.com.au>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3.1) Gecko/20030425
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
CC: Jim Sermersheim <jimse@novell.com>, ietf-ldapbis@OpenLDAP.org
Subject: Re: WG Last Call: draft-ietf-ldapbis-protocol-17.txt  [corrected]
References: <sf95a95f.001@prv-mail20.provo.novell.com> <6.0.0.22.0.20031021211747.03e8faf8@127.0.0.1>
In-Reply-To: <6.0.0.22.0.20031021211747.03e8faf8@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


I agree completely with Kurt.

Kurt D. Zeilenga wrote:
> At 08:46 PM 10/21/2003, Jim Sermersheim wrote:
> 
>>>>>"Steven Legg" <steven.legg@adacel.com.au> 10/5/03 11:50:20 PM >>>
>>>>
>>>>4.6. Modify Operation 
>>>
>>>>   Parameters of the Modify Request are: 
>>>>    
>>>>   - object: The object to be modified. The value of this field 
>>>>     contains the DN of the entry to be modified. The server will
>>
>>not 
>>
>>>                                                             
>>
>>^^^^^^^^
>>
>>>SHALL NOT ?
>>
>>These are all on many operations. I think SHALL NOT is too strong. I
>>suspect there are implementations that allow the alias to be
>>dereferenced (whether by control, local policy, or both).
>>
>>Do you think there is an interoperability issue here? If so, would
>>SHOULD NOT suffice?
> 
> 
> I think, no.  A server which deferences the alias not only
> prevents modification of the the alias object, it might
> (quite inappropriately) modify the aliased object.  A
> SHALL NOT here is appropriate as without it one could
> not administrate alias objects in an interoperable fashion.
> This applies to all other update operations as well.
> 
> Kurt 
> 
> 
> 



From owner-ietf-ldapbis@OpenLDAP.org  Wed Oct 22 03:26: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 DAA27486
	for <ldapbis-archive@lists.ietf.org>; Wed, 22 Oct 2003 03:26:19 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9M7MbHW007716;
	Wed, 22 Oct 2003 07:23:16 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9M7HP1I007540;
	Wed, 22 Oct 2003 07:17:25 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 22 Oct 2003 07:17:25 +0000
Received: from adacel.com (gunsmoke.adacel.com.au [210.11.130.7])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9M7HNHS007522
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 22 Oct 2003 07:17:23 GMT
	(envelope-from steven.legg@adacel.com.au)
Received: from nexus.adacel.com (Not Verified[10.32.240.1]) by adacel.com with NetIQ MailMarshal (v5.5.3.16)
	id <B00018741d>; Wed, 22 Oct 2003 17:11:16 +1000
Received: (qmail 11275 invoked from network); 22 Oct 2003 07:17:01 -0000
Received: from unknown (HELO adacel.com.au) (10.32.24.165)
  by nexus.adacel.com with SMTP; 22 Oct 2003 07:17:01 -0000
Message-ID: <3F962EEC.4060102@adacel.com.au>
Date: Wed, 22 Oct 2003 18:17:00 +1100
From: Steven Legg <steven.legg@adacel.com.au>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3.1) Gecko/20030425
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Jim Sermersheim <jimse@novell.com>
CC: Kurt@OpenLDAP.org, ietf-ldapbis@OpenLDAP.org
Subject: Re: REVISED protocol review notes [LONG]
References: <sf95aa27.025@prv-mail20.provo.novell.com>
In-Reply-To: <sf95aa27.025@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


Jim,

Jim Sermersheim wrote:
> Actually my current plan is to define both:
>      Attribute ::= SEQUENCE {
>              type    AttributeDescription,
>              vals    SET SIZE (1..MAX) OF AttributeValue }
> and
>      PartialAttribute ::= SEQUENCE {
>              type    AttributeDescription,
>              vals    SET OF AttributeValue }
> 
> and use them in the appropriate places.
> 
> Does this sound reasonable?

Yes, but you could also do this:

     PartialAttribute ::= SEQUENCE {
         type    AttributeDescription,
         vals    SET OF AttributeValue }

     Attribute ::= PartialAttribute(WITH COMPONENTS {..., vals (SIZE(1..MAX))})

You could also in-line the right hand side of the Attribute assignment
statement everywhere Attribute is needed and then rename PartialAttribute
to just Attribute.

By the way, are you intending to put identifiers into each of
the SET OF and SEQUENCE OF notations ? I so, do you want me to
make some appropriate suggestions ?

Regards,
Steven

> 
> Jim
> 
> 
>>>>"Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 10/21/03 9:17:11 PM >>>
> 
> At 08:01 PM 10/21/2003, Jim Sermersheim wrote:
> 
>>>>>Kurt Zeilenga < Kurt@OpenLDAP.org > 10/7/03 3:48:43 PM >>>
>>>>
>>>>Attribute ::= SEQUENCE { 
>>>>type AttributeDescription, 
>>>>vals SET OF AttributeValue } 
>>>>
>>>>Each attribute value is distinct in the set (no duplicates). The
> 
> set 
> 
>>>>of attribute values is unordered. Implementations MUST NOT reply
> 
> upon 
> 
>>>>any apparent ordering being repeatable. 
>>>>
>>>
>>>This type is never explicitly used in the protocol. 
>>
>>It is the type for ModifyRequest.changes.modification
> 
> 
> Okay... but I note that ModifyRequest.changes.modification is
> a partial attribute. I assume your other changes to clarify
> Attribute may be partial will lead to PartialAttributeList
> fading away.
> 
> Kurt
> 
> 
> 
> 
> 



From owner-ietf-ldapbis@OpenLDAP.org  Wed Oct 22 11:31: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 LAA14501
	for <ldapbis-archive@lists.ietf.org>; Wed, 22 Oct 2003 11:31:22 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9MFMeI6041200;
	Wed, 22 Oct 2003 15:29:50 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9MFM9mr041115;
	Wed, 22 Oct 2003 15:22:09 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 22 Oct 2003 15:22:09 +0000
Received: from prv-mail20.provo.novell.com (prv-mail20.provo.novell.com [137.65.81.122])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9MFLwHS041019;
	Wed, 22 Oct 2003 15:21:58 GMT
	(envelope-from jimse@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Wed, 22 Oct 2003 09:21:37 -0600
Message-Id: <sf964c21.050@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.2 Beta
Date: Wed, 22 Oct 2003 09:21:15 -0600
From: "Jim Sermersheim" <jimse@novell.com>
To: <steven.legg@adacel.com.au>, <Kurt@OpenLDAP.org>
Cc: <ietf-ldapbis@OpenLDAP.org>
Subject: Re: WG Last Call: draft-ietf-ldapbis-protocol-17.txt 
	[corrected]
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__Part1A44BE7B.1__="
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.

--=__Part1A44BE7B.1__=
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Bah.
 
Yeah, after reading these reasons I also agree. I still think it's
appropriate for a control to exist that can be used by the client to
override this behavior. But in that case, the control definition updates
the spec, right?
 
Jim

>>> Steven Legg <steven.legg@adacel.com.au> 10/22/03 1:02:41 AM >>>

I agree completely with Kurt.

Kurt D. Zeilenga wrote:
> At 08:46 PM 10/21/2003, Jim Sermersheim wrote:
> 
>>>>>"Steven Legg" < steven.legg@adacel.com.au > 10/5/03 11:50:20 PM
>>>
>>>>
>>>>4.6. Modify Operation 
>>>
>>>> Parameters of the Modify Request are: 
>>>> 
>>>> - object: The object to be modified. The value of this field 
>>>> contains the DN of the entry to be modified. The server will
>>
>>not 
>>
>>> 
>>
>>^^^^^^^^
>>
>>>SHALL NOT ?
>>
>>These are all on many operations. I think SHALL NOT is too strong. I
>>suspect there are implementations that allow the alias to be
>>dereferenced (whether by control, local policy, or both).
>>
>>Do you think there is an interoperability issue here? If so, would
>>SHOULD NOT suffice?
> 
> 
> I think, no. A server which deferences the alias not only
> prevents modification of the the alias object, it might
> (quite inappropriately) modify the aliased object. A
> SHALL NOT here is appropriate as without it one could
> not administrate alias objects in an interoperable fashion.
> This applies to all other update operations as well.
> 
> Kurt 
> 
> 
> 



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

<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 5.50.4933.1800" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Microsoft Sans Serif">
<DIV>Bah.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Yeah, after reading these reasons I also agree. I still think it's appropriate for a control to exist that can be used by the client to override this behavior. But in that case, the control definition updates the spec, right?</DIV>
<DIV>&nbsp;</DIV>
<DIV>Jim<BR><BR>&gt;&gt;&gt; Steven Legg &lt;steven.legg@adacel.com.au&gt; 10/22/03 1:02:41 AM &gt;&gt;&gt;<BR><BR>I agree completely with Kurt.<BR><BR>Kurt D. Zeilenga wrote:<BR>&gt; At 08:46 PM 10/21/2003, Jim Sermersheim wrote:<BR>&gt; <BR>&gt;&gt;&gt;&gt;&gt;"Steven Legg" &lt;<U> <A href="mailto:steven.legg@adacel.com.au">steven.legg@adacel.com.au</A></U> &gt; 10/5/03 11:50:20 PM &gt;&gt;&gt;<BR>&gt;&gt;&gt;&gt;<BR>&gt;&gt;&gt;&gt;4.6. Modify Operation <BR>&gt;&gt;&gt;<BR>&gt;&gt;&gt;&gt; Parameters of the Modify Request are: <BR>&gt;&gt;&gt;&gt; <BR>&gt;&gt;&gt;&gt; - object: The object to be modified. The value of this field <BR>&gt;&gt;&gt;&gt; contains the DN of the entry to be modified. The server will<BR>&gt;&gt;<BR>&gt;&gt;not <BR>&gt;&gt;<BR>&gt;&gt;&gt; <BR>&gt;&gt;<BR>&gt;&gt;^^^^^^^^<BR>&gt;&gt;<BR>&gt;&gt;&gt;SHALL NOT ?<BR>&gt;&gt;<BR>&gt;&gt;These are all on many operations. I think SHALL NOT is too strong. I<BR>&gt;&gt;suspect there are implementations tha!
 t allow the alias to be<BR>&gt;&gt;dereferenced (whether by control, local policy, or both).<BR>&gt;&gt;<BR>&gt;&gt;Do you think there is an interoperability issue here? If so, would<BR>&gt;&gt;SHOULD NOT suffice?<BR>&gt; <BR>&gt; <BR>&gt; I think, no. A server which deferences the alias not only<BR>&gt; prevents modification of the the alias object, it might<BR>&gt; (quite inappropriately) modify the aliased object. A<BR>&gt; SHALL NOT here is appropriate as without it one could<BR>&gt; not administrate alias objects in an interoperable fashion.<BR>&gt; This applies to all other update operations as well.<BR>&gt; <BR>&gt; Kurt <BR>&gt; <BR>&gt; <BR>&gt; <BR><BR></DIV></BODY></HTML>
--=__Part1A44BE7B.1__=--


From owner-ietf-ldapbis@OpenLDAP.org  Wed Oct 22 11:38: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 LAA14709
	for <ldapbis-archive@lists.ietf.org>; Wed, 22 Oct 2003 11:38:30 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9MFYeIK042568;
	Wed, 22 Oct 2003 15:37:43 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9MFUv5n042029;
	Wed, 22 Oct 2003 15:30:57 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 22 Oct 2003 15:30:57 +0000
Received: from prv-mail20.provo.novell.com (prv-mail20.provo.novell.com [137.65.81.122])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9MFUlHS041942;
	Wed, 22 Oct 2003 15:30:47 GMT
	(envelope-from jimse@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Wed, 22 Oct 2003 09:30:27 -0600
Message-Id: <sf964e33.019@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.2 Beta
Date: Wed, 22 Oct 2003 09:29:58 -0600
From: "Jim Sermersheim" <jimse@novell.com>
To: <steven.legg@adacel.com.au>
Cc: <ietf-ldapbis@OpenLDAP.org>, <Kurt@OpenLDAP.org>
Subject: Re: REVISED protocol review notes [LONG]
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__Part055BA166.1__="
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.

--=__Part055BA166.1__=
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

>>> Steven Legg <steven.legg@adacel.com.au> 10/22/03 1:17:00 AM >>>
>Yes, but you could also do this:
>
>PartialAttribute ::= SEQUENCE {
>type AttributeDescription,
>vals SET OF AttributeValue }
>
>Attribute ::= PartialAttribute(WITH COMPONENTS {..., vals
(SIZE(1..MAX))})

Wow. This looks cool... but having never seen such a thing, I had to do
a double take. What do others think about using this kind of
definition?

>You could also in-line the right hand side of the Attribute
assignment
>statement everywhere Attribute is needed and then rename
PartialAttribute
>to just Attribute.

True, it's only used in one place right now (AttributeList)

>By the way, are you intending to put identifiers into each of
>the SET OF and SEQUENCE OF notations ? I so, do you want me to
>make some appropriate suggestions ?

I think so, but I wanted to ping the list one more time about this
before deciding.
 
Jim

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

<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 5.50.4933.1800" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Microsoft Sans Serif">
<DIV>&gt;&gt;&gt; Steven Legg &lt;steven.legg@adacel.com.au&gt; 10/22/03 1:17:00 AM &gt;&gt;&gt;<BR>&gt;Yes, but you could also do this:<BR>&gt;<BR>&gt;PartialAttribute ::= SEQUENCE {<BR>&gt;type AttributeDescription,<BR>&gt;vals SET OF AttributeValue }<BR>&gt;<BR>&gt;Attribute ::= PartialAttribute(WITH COMPONENTS {..., vals (SIZE(1..MAX))})<BR></DIV>
<DIV>Wow. This looks cool... but having never seen such a thing, I had to do a double take. What do others think about using this kind of definition?</DIV>
<DIV><BR>&gt;You could also in-line the right hand side of the Attribute assignment<BR>&gt;statement everywhere Attribute is needed and then rename PartialAttribute<BR>&gt;to just Attribute.<BR></DIV>
<DIV>True, it's only used in one place right now (AttributeList)</DIV>
<DIV><BR>&gt;By the way, are you intending to put identifiers into each of<BR>&gt;the SET OF and SEQUENCE OF notations ? I so, do you want me to<BR>&gt;make some appropriate suggestions ?<BR></DIV>
<DIV>I think so, but I wanted to ping the list one more time about this before deciding.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Jim</DIV></BODY></HTML>
--=__Part055BA166.1__=--


From owner-ietf-ldapbis@OpenLDAP.org  Wed Oct 22 20: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 UAA09400
	for <ldapbis-archive@lists.ietf.org>; Wed, 22 Oct 2003 20:13:46 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9N0AhHW094753;
	Thu, 23 Oct 2003 00:11:13 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9N06f2s094665;
	Thu, 23 Oct 2003 00:06:41 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 23 Oct 2003 00:06:41 +0000
Received: from adacel.com (gunsmoke.adacel.com.au [210.11.130.7])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9N06YHS094633
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 23 Oct 2003 00:06:39 GMT
	(envelope-from steven.legg@adacel.com.au)
Received: from nexus.adacel.com (Not Verified[10.32.240.1]) by adacel.com with NetIQ MailMarshal (v5.5.3.16)
	id <B000188231>; Thu, 23 Oct 2003 10:00:21 +1000
Received: (qmail 10572 invoked from network); 23 Oct 2003 00:06:13 -0000
Received: from unknown (HELO adacel.com.au) (10.32.24.165)
  by nexus.adacel.com with SMTP; 23 Oct 2003 00:06:13 -0000
Message-ID: <3F971B74.7020903@adacel.com.au>
Date: Thu, 23 Oct 2003 11:06:12 +1100
From: Steven Legg <steven.legg@adacel.com.au>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3.1) Gecko/20030425
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Jim Sermersheim <jimse@novell.com>
CC: ietf-ldapbis@OpenLDAP.org, Kurt@OpenLDAP.org
Subject: Re: REVISED protocol review notes [LONG]
References: <sf964e33.019@prv-mail20.provo.novell.com>
In-Reply-To: <sf964e33.019@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


Jim,

Jim Sermersheim wrote:
>  >>> Steven Legg <steven.legg@adacel.com.au> 10/22/03 1:17:00 AM >>>
>  >Yes, but you could also do this:
>  >
>  >PartialAttribute ::= SEQUENCE {
>  >type AttributeDescription,
>  >vals SET OF AttributeValue }
>  >
>  >Attribute ::= PartialAttribute(WITH COMPONENTS {..., vals (SIZE(1..MAX))})
> Wow. This looks cool... but having never seen such a thing, I had to do 
> a double take.

You might like to add an ASN.1 comment for good measure since the notation
is infrequently used, e.g.

     -- must contain at least one attribute value --

Regards,
Steven



From owner-ietf-ldapbis@OpenLDAP.org  Wed Oct 22 20:17: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 UAA09725
	for <ldapbis-archive@lists.ietf.org>; Wed, 22 Oct 2003 20:17:25 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9N0GhHW094892;
	Thu, 23 Oct 2003 00:16:49 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9N0BoXk094777;
	Thu, 23 Oct 2003 00:11:50 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 23 Oct 2003 00:11:50 +0000
Received: from adacel.com (gunsmoke.adacel.com.au [210.11.130.7])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9N0BmHS094764
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 23 Oct 2003 00:11:49 GMT
	(envelope-from steven.legg@adacel.com.au)
Received: from nexus.adacel.com (Not Verified[10.32.240.1]) by adacel.com with NetIQ MailMarshal (v5.5.3.16)
	id <B00018824d>; Thu, 23 Oct 2003 10:05:36 +1000
Received: (qmail 11009 invoked from network); 23 Oct 2003 00:11:28 -0000
Received: from unknown (HELO adacel.com.au) (10.32.24.165)
  by nexus.adacel.com with SMTP; 23 Oct 2003 00:11:28 -0000
Message-ID: <3F971CAF.9080409@adacel.com.au>
Date: Thu, 23 Oct 2003 11:11:27 +1100
From: Steven Legg <steven.legg@adacel.com.au>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3.1) Gecko/20030425
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Jim Sermersheim <jimse@novell.com>
CC: ietf-ldapbis@OpenLDAP.org
Subject: Re: WG Last Call: draft-ietf-ldapbis-protocol-17.txt 	[corrected]
References: <sf964c21.050@prv-mail20.provo.novell.com>
In-Reply-To: <sf964c21.050@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


Jim,

Jim Sermersheim wrote:
> Bah.
>  
> Yeah, after reading these reasons I also agree. I still think it's 
> appropriate for a control to exist that can be used by the client to 
> override this behavior. But in that case, the control definition updates 
> the spec, right?

Yes. I see nothing that would prevent such a control being defined
(outside LDAPbis, of course).

Regards,
Steven

>  
> Jim
> 
>  >>> Steven Legg <steven.legg@adacel.com.au> 10/22/03 1:02:41 AM >>>
> 
> I agree completely with Kurt.
> 
> Kurt D. Zeilenga wrote:
>  > At 08:46 PM 10/21/2003, Jim Sermersheim wrote:
>  >
>  >>>>>"Steven Legg" <_ steven.legg@adacel.com.au 
> <mailto:steven.legg@adacel.com.au>_ > 10/5/03 11:50:20 PM >>>
>  >>>>
>  >>>>4.6. Modify Operation
>  >>>
>  >>>> Parameters of the Modify Request are:
>  >>>>
>  >>>> - object: The object to be modified. The value of this field
>  >>>> contains the DN of the entry to be modified. The server will
>  >>
>  >>not
>  >>
>  >>>
>  >>
>  >>^^^^^^^^
>  >>
>  >>>SHALL NOT ?
>  >>
>  >>These are all on many operations. I think SHALL NOT is too strong. I
>  >>suspect there are implementations tha! t allow the alias to be
>  >>dereferenced (whether by control, local policy, or both).
>  >>
>  >>Do you think there is an interoperability issue here? If so, would
>  >>SHOULD NOT suffice?
>  >
>  >
>  > I think, no. A server which deferences the alias not only
>  > prevents modification of the the alias object, it might
>  > (quite inappropriately) modify the aliased object. A
>  > SHALL NOT here is appropriate as without it one could
>  > not administrate alias objects in an interoperable fashion.
>  > This applies to all other update operations as well.
>  >
>  > Kurt
>  >
>  >
>  >
> 



From owner-ietf-ldapbis@OpenLDAP.org  Wed Oct 22 21:31: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 VAA12458
	for <ldapbis-archive@lists.ietf.org>; Wed, 22 Oct 2003 21:31:13 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9N1SiHW097213;
	Thu, 23 Oct 2003 01:30:16 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9N1S6GX097191;
	Thu, 23 Oct 2003 01:28:06 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 23 Oct 2003 01:28:06 +0000
Received: from ausyms50.ca.com (mail30.ca.com [155.35.248.106])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9N1ReHS097143;
	Thu, 23 Oct 2003 01:27:41 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.6713);
	 Thu, 23 Oct 2003 11:27:19 +1000
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C39904.CC9E5779"
Subject: RE: REVISED protocol review notes [LONG]
Date: Thu, 23 Oct 2003 11:27:18 +1000
Message-ID: <1395B4B334FCC143B36AF788E68B6381A76F17@ausyms21.ca.com>
Thread-Topic: REVISED protocol review notes [LONG]
Thread-Index: AcOYsnXKo5F2li4ES2umuA6OdAZ8KwAUZLxg
From: "Ramsay, Ron" <Ron.Ramsay@ca.com>
To: "Jim Sermersheim" <jimse@novell.com>, <steven.legg@adacel.com.au>
Cc: <ietf-ldapbis@OpenLDAP.org>, <Kurt@OpenLDAP.org>
X-OriginalArrivalTime: 23 Oct 2003 01:27:19.0171 (UTC) FILETIME=[CCD18D30:01C39904]
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 multi-part message in MIME format.

------_=_NextPart_001_01C39904.CC9E5779
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I don't know what version of ASN.1 LDAPv3 should require. For X.500 it's =
the 1993 version, isn't it? But I don't remember any statement about =
ASN.1. I wouldn't like the ASN.1 issue to create a moving target.

-----Original Message-----
From: owner-ietf-ldapbis@OpenLDAP.org =
[mailto:owner-ietf-ldapbis@OpenLDAP.org]On Behalf Of Jim Sermersheim
Sent: Thursday, 23 October 2003 01:30
To: steven.legg@adacel.com.au
Cc: ietf-ldapbis@OpenLDAP.org; Kurt@OpenLDAP.org
Subject: Re: REVISED protocol review notes [LONG]


>>> Steven Legg <steven.legg@adacel.com.au> 10/22/03 1:17:00 AM >>>
>Yes, but you could also do this:
>
>PartialAttribute ::=3D SEQUENCE {
>type AttributeDescription,
>vals SET OF AttributeValue }
>
>Attribute ::=3D PartialAttribute(WITH COMPONENTS {..., vals =
(SIZE(1..MAX))})

Wow. This looks cool... but having never seen such a thing, I had to do =
a double take. What do others think about using this kind of definition?

>You could also in-line the right hand side of the Attribute assignment
>statement everywhere Attribute is needed and then rename =
PartialAttribute
>to just Attribute.

True, it's only used in one place right now (AttributeList)

>By the way, are you intending to put identifiers into each of
>the SET OF and SEQUENCE OF notations ? I so, do you want me to
>make some appropriate suggestions ?

I think so, but I wanted to ping the list one more time about this =
before deciding.
=20
Jim


------_=_NextPart_001_01C39904.CC9E5779
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<META content=3D"MSHTML 6.00.2800.1264" name=3DGENERATOR></HEAD>
<BODY style=3D"MARGIN: 4px 4px 1px; FONT: 10pt Microsoft Sans Serif">
<DIV><SPAN class=3D211502101-23102003>I don't know what version of ASN.1 =
LDAPv3=20
should require. For X.500 it's the 1993 version, isn't it? But I don't =
remember=20
any statement about ASN.1. I wouldn't like the ASN.1 issue to create a =
moving=20
target.</SPAN></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT=20
  face=3DTahoma>-----Original Message-----<BR><B>From:</B>=20
  owner-ietf-ldapbis@OpenLDAP.org =
[mailto:owner-ietf-ldapbis@OpenLDAP.org]<B>On=20
  Behalf Of </B>Jim Sermersheim<BR><B>Sent:</B> Thursday, 23 October =
2003=20
  01:30<BR><B>To:</B> steven.legg@adacel.com.au<BR><B>Cc:</B>=20
  ietf-ldapbis@OpenLDAP.org; Kurt@OpenLDAP.org<BR><B>Subject:</B> Re: =
REVISED=20
  protocol review notes [LONG]<BR><BR></FONT></DIV>
  <DIV>&gt;&gt;&gt; Steven Legg &lt;steven.legg@adacel.com.au&gt; =
10/22/03=20
  1:17:00 AM &gt;&gt;&gt;<BR>&gt;Yes, but you could also do=20
  this:<BR>&gt;<BR>&gt;PartialAttribute ::=3D SEQUENCE {<BR>&gt;type=20
  AttributeDescription,<BR>&gt;vals SET OF AttributeValue=20
  }<BR>&gt;<BR>&gt;Attribute ::=3D PartialAttribute(WITH COMPONENTS =
{..., vals=20
  (SIZE(1..MAX))})<BR></DIV>
  <DIV>Wow. This looks cool... but having never seen such a thing, I had =
to do a=20
  double take. What do others think about using this kind of =
definition?</DIV>
  <DIV><BR>&gt;You could also in-line the right hand side of the =
Attribute=20
  assignment<BR>&gt;statement everywhere Attribute is needed and then =
rename=20
  PartialAttribute<BR>&gt;to just Attribute.<BR></DIV>
  <DIV>True, it's only used in one place right now (AttributeList)</DIV>
  <DIV><BR>&gt;By the way, are you intending to put identifiers into =
each=20
  of<BR>&gt;the SET OF and SEQUENCE OF notations ? I so, do you want me=20
  to<BR>&gt;make some appropriate suggestions ?<BR></DIV>
  <DIV>I think so, but I wanted to ping the list one more time about =
this before=20
  deciding.</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>Jim</DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C39904.CC9E5779--


From owner-ietf-ldapbis@OpenLDAP.org  Wed Oct 22 21:55: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 VAA13409
	for <ldapbis-archive@lists.ietf.org>; Wed, 22 Oct 2003 21:55:16 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9N1qiHW097712;
	Thu, 23 Oct 2003 01:53:01 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9N1mnR5097679;
	Thu, 23 Oct 2003 01:48:49 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 23 Oct 2003 01:48:49 +0000
Received: from prv-mail20.provo.novell.com (prv-mail20.provo.novell.com [137.65.81.122])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9N1mjHS097642;
	Thu, 23 Oct 2003 01:48:45 GMT
	(envelope-from jimse@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Wed, 22 Oct 2003 19:48:25 -0600
Message-Id: <sf96df09.011@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.2 Beta
Date: Wed, 22 Oct 2003 19:48:05 -0600
From: "Jim Sermersheim" <jimse@novell.com>
To: <steven.legg@adacel.com.au>, <Ron.Ramsay@ca.com>
Cc: <ietf-ldapbis@OpenLDAP.org>, <Kurt@OpenLDAP.org>
Subject: RE: REVISED protocol review notes [LONG]
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__PartB6E81345.2__="
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.

--=__PartB6E81345.2__=
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

The current LDAPBis documents (well, at least the protocol document)
references the 2002 version of X.680
 
Jim

>>> "Ramsay, Ron" <Ron.Ramsay@ca.com> 10/22/03 7:27:18 PM >>>

I don't know what version of ASN.1 LDAPv3 should require. For X.500
it's the 1993 version, isn't it? But I don't remember any statement
about ASN.1. I wouldn't like the ASN.1 issue to create a moving target.
-----Original Message-----
From: owner-ietf-ldapbis@OpenLDAP.org
[mailto:owner-ietf-ldapbis@OpenLDAP.org]On Behalf Of Jim Sermersheim
Sent: Thursday, 23 October 2003 01:30
To: steven.legg@adacel.com.au
Cc: ietf-ldapbis@OpenLDAP.org; Kurt@OpenLDAP.org
Subject: Re: REVISED protocol review notes [LONG]


>>> Steven Legg <steven.legg@adacel.com.au> 10/22/03 1:17:00 AM >>>
>Yes, but you could also do this:
>
>PartialAttribute ::= SEQUENCE {
>type AttributeDescription,
>vals SET OF AttributeValue }
>
>Attribute ::= PartialAttribute(WITH COMPONENTS {..., vals
(SIZE(1..MAX))})

Wow. This looks cool... but having never seen such a thing, I had to do
a double take. What do others think about using this kind of
definition?

>You could also in-line the right hand side of the Attribute
assignment
>statement everywhere Attribute is needed and then rename
PartialAttribute
>to just Attribute.

True, it's only used in one place right now (AttributeList)

>By the way, are you intending to put identifiers into each of
>the SET OF and SEQUENCE OF notations ? I so, do you want me to
>make some appropriate suggestions ?

I think so, but I wanted to ping the list one more time about this
before deciding.
 
Jim


--=__PartB6E81345.2__=
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 5.50.4933.1800" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Microsoft Sans Serif">
<DIV>The current LDAPBis documents (well, at least the protocol document) references the 2002 version of X.680</DIV>
<DIV>&nbsp;</DIV>
<DIV>Jim<BR><BR>&gt;&gt;&gt; "Ramsay, Ron" &lt;Ron.Ramsay@ca.com&gt; 10/22/03 7:27:18 PM &gt;&gt;&gt;<BR></DIV>
<DIV style="FONT: 10pt Microsoft Sans Serif; COLOR: #000000">
<DIV><SPAN class=211502101-23102003>I don't know what version of ASN.1 LDAPv3 should require. For X.500 it's the 1993 version, isn't it? But I don't remember any statement about ASN.1. I wouldn't like the ASN.1 issue to create a moving target.</SPAN></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma>-----Original Message-----<BR><B>From:</B> owner-ietf-ldapbis@OpenLDAP.org [mailto:owner-ietf-ldapbis@OpenLDAP.org]<B>On Behalf Of </B>Jim Sermersheim<BR><B>Sent:</B> Thursday, 23 October 2003 01:30<BR><B>To:</B> steven.legg@adacel.com.au<BR><B>Cc:</B> ietf-ldapbis@OpenLDAP.org; Kurt@OpenLDAP.org<BR><B>Subject:</B> Re: REVISED protocol review notes [LONG]<BR><BR></FONT></DIV>
<DIV>&gt;&gt;&gt; Steven Legg &lt;steven.legg@adacel.com.au&gt; 10/22/03 1:17:00 AM &gt;&gt;&gt;<BR>&gt;Yes, but you could also do this:<BR>&gt;<BR>&gt;PartialAttribute ::= SEQUENCE {<BR>&gt;type AttributeDescription,<BR>&gt;vals SET OF AttributeValue }<BR>&gt;<BR>&gt;Attribute ::= PartialAttribute(WITH COMPONENTS {..., vals (SIZE(1..MAX))})<BR></DIV>
<DIV>Wow. This looks cool... but having never seen such a thing, I had to do a double take. What do others think about using this kind of definition?</DIV>
<DIV><BR>&gt;You could also in-line the right hand side of the Attribute assignment<BR>&gt;statement everywhere Attribute is needed and then rename PartialAttribute<BR>&gt;to just Attribute.<BR></DIV>
<DIV>True, it's only used in one place right now (AttributeList)</DIV>
<DIV><BR>&gt;By the way, are you intending to put identifiers into each of<BR>&gt;the SET OF and SEQUENCE OF notations ? I so, do you want me to<BR>&gt;make some appropriate suggestions ?<BR></DIV>
<DIV>I think so, but I wanted to ping the list one more time about this before deciding.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Jim</DIV></BLOCKQUOTE></DIV></BODY></HTML>
--=__PartB6E81345.2__=--


From owner-ietf-ldapbis@OpenLDAP.org  Wed Oct 22 22:20: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 WAA14423
	for <ldapbis-archive@lists.ietf.org>; Wed, 22 Oct 2003 22:20:22 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9N2AiHu099786;
	Thu, 23 Oct 2003 02:18:25 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9N25h1Z098957;
	Thu, 23 Oct 2003 02:05:43 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 23 Oct 2003 02:05:43 +0000
Received: from adacel.com (gunsmoke.adacel.com.au [210.11.130.7])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9N25eHS098930
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 23 Oct 2003 02:05:42 GMT
	(envelope-from steven.legg@adacel.com.au)
Received: from nexus.adacel.com (Not Verified[10.32.240.1]) by adacel.com with NetIQ MailMarshal (v5.5.3.16)
	id <B00018847f>; Thu, 23 Oct 2003 11:59:27 +1000
Received: (qmail 23545 invoked from network); 23 Oct 2003 02:05:19 -0000
Received: from unknown (HELO adacel.com.au) (10.32.24.165)
  by nexus.adacel.com with SMTP; 23 Oct 2003 02:05:19 -0000
Message-ID: <3F97375F.1080000@adacel.com.au>
Date: Thu, 23 Oct 2003 13:05:19 +1100
From: Steven Legg <steven.legg@adacel.com.au>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3.1) Gecko/20030425
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Ramsay, Ron" <Ron.Ramsay@ca.com>
CC: ietf-ldapbis@OpenLDAP.org
Subject: Re: REVISED protocol review notes [LONG]
References: <1395B4B334FCC143B36AF788E68B6381A76F17@ausyms21.ca.com>
In-Reply-To: <1395B4B334FCC143B36AF788E68B6381A76F17@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,

Ramsay, Ron wrote:
> I don't know what version of ASN.1 LDAPv3 should require. For X.500 it's 
> the 1993 version, isn't it? But I don't remember any statement about 
> ASN.1. I wouldn't like the ASN.1 issue to create a moving target.

At the request of the ITU-T ASN.1 working group we are referencing the
latest version of ASN.1. Since this version is fully backward compatible
with the version referenced by X.500:1993, and introduces no harmful effects,
we've agreed to the request. The version of ASN.1 referenced by X.500:1993
has been withdrawn by the ITU.

BTW, the "wow, cool" notation has been part of ASN.1 since at least 1993,
possibly longer.

Regards,
Steven

> 
>     -----Original Message-----
>     *From:* owner-ietf-ldapbis@OpenLDAP.org
>     [mailto:owner-ietf-ldapbis@OpenLDAP.org]*On Behalf Of *Jim Sermersheim
>     *Sent:* Thursday, 23 October 2003 01:30
>     *To:* steven.legg@adacel.com.au
>     *Cc:* ietf-ldapbis@OpenLDAP.org; Kurt@OpenLDAP.org
>     *Subject:* Re: REVISED protocol review notes [LONG]
> 
>      >>> Steven Legg <steven.legg@adacel.com.au> 10/22/03 1:17:00 AM >>>
>      >Yes, but you could also do this:
>      >
>      >PartialAttribute ::= SEQUENCE {
>      >type AttributeDescription,
>      >vals SET OF AttributeValue }
>      >
>      >Attribute ::= PartialAttribute(WITH COMPONENTS {..., vals
>     (SIZE(1..MAX))})
>     Wow. This looks cool... but having never seen such a thing, I had to
>     do a double take. What do others think about using this kind of
>     definition?
> 
>      >You could also in-line the right hand side of the Attribute assignment
>      >statement everywhere Attribute is needed and then rename
>     PartialAttribute
>      >to just Attribute.
>     True, it's only used in one place right now (AttributeList)
> 
>      >By the way, are you intending to put identifiers into each of
>      >the SET OF and SEQUENCE OF notations ? I so, do you want me to
>      >make some appropriate suggestions ?
>     I think so, but I wanted to ping the list one more time about this
>     before deciding.
>      
>     Jim



From owner-ietf-ldapbis@OpenLDAP.org  Wed Oct 22 22:26: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 WAA14536
	for <ldapbis-archive@lists.ietf.org>; Wed, 22 Oct 2003 22:26:39 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9N2MiHW002023;
	Thu, 23 Oct 2003 02:25:18 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9N2LtOR001914;
	Thu, 23 Oct 2003 02:21:55 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 23 Oct 2003 02:21:55 +0000
Received: from prv-mail20.provo.novell.com (prv-mail20.provo.novell.com [137.65.81.122])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9N2LrHS001845
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 23 Oct 2003 02:21:53 GMT
	(envelope-from jimse@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Wed, 22 Oct 2003 20:21:33 -0600
Message-Id: <sf96e6cd.046@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.2 Beta
Date: Wed, 22 Oct 2003 20:21:12 -0600
From: "Jim Sermersheim" <jimse@novell.com>
To: <steven.legg@adacel.com.au>, <ietf-ldapbis@OpenLDAP.org>
Subject: RE: WG Last Call: draft-ietf-ldapbis-protocol-17.txt
	[corrected]
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

So, the changes would produce these types, correct?
 
AttributeSelection ::= SEQUENCE OF selection LDAPString

Attribute ::= SEQUENCE {
   type    AttributeDescription,
   vals    SET SIZE (1..MAX) OF value AttributeValue }

Referral ::= SEQUENCE SIZE (1..MAX) OF url URL

Controls ::= SEQUENCE OF control Control

Filter ::= CHOICE {
   and             [0] SET SIZE (1..MAX) OF filter Filter,
   or              [1] SET SIZE (1..MAX) OF filter Filter,
   not             [2] Filter,
   equalityMatch   [3] AttributeValueAssertion,
   substrings      [4] SubstringFilter,
   greaterOrEqual  [5] AttributeValueAssertion,
   lessOrEqual     [6] AttributeValueAssertion,
   present         [7] AttributeDescription,
   approxMatch     [8] AttributeValueAssertion,
   extensibleMatch [9] MatchingRuleAssertion }

SubstringFilter ::= SEQUENCE {
   type            AttributeDescription,
   -- at least one must be present,
   -- initial and final can occur at most once
   substrings      SEQUENCE SIZE (1..MAX) OF substring CHOICE {
      initial [0] AssertionValue,
      any     [1] AssertionValue,
      final   [2] AssertionValue } }

PartialAttributeList ::= SEQUENCE OF partialAttribute PartialAttribute

PartialAttribute ::= SEQUENCE {
   type   AttributeDescription,
   vals   SET OF value AttributeValue }

SearchResultReference ::= 
   [APPLICATION 19] SEQUENCE SIZE (1..MAX) OF url URL

ModifyRequest ::= [APPLICATION 6] SEQUENCE {
   object          LDAPDN,
   changes         SEQUENCE OF change SEQUENCE {
      operation       ENUMERATED {
         add     (0),
         delete  (1),
         replace (2) },
      modification    PartialAttribute } }

AttributeList ::= SEQUENCE OF attribute Attribute

I'll do this unless there are objections.
 
Jim

>>> "Steven Legg" <steven.legg@adacel.com.au> 10/6/03 6:07:13 PM >>>

Folks,

I recently published an Internet draft on an XML rendition of the LDAP
protocol (called XLDAP) that is realized by applying a set of XML
encoding rules to the ASN.1 types in the ASN.1 specification for LDAP
(specifically the ASN.1 in the protocols draft being last-called).

The XML produced is neat and tidy except with respect to the instances
of the member type of a SEQUENCE OF or SET OF ASN.1 type.

Consider this example drawn from the protocols draft:

AttributeList ::= SEQUENCE OF SEQUENCE { 
type AttributeDescription, 
vals SET OF AttributeValue } 

Using my Directory XML Encoding Rules (DXER) to encode an attribute
list,
each attribute in the list is encoded as an element with the safe, but
bland name of <item>. Using the ITU-T's XML Encoding Rules (XER), each
attribute in the list is encoded as an element with the unappealing
name
of <SEQUENCE>.

However the situation can be improved since the version of ASN.1 that
the protocols draft is referencing allows an ASN.1 identifier after a
SEQUENCE OF or SET OF and before the definition of the member type.

For example:

AttributeList ::= SEQUENCE OF attribute SEQUENCE { 
type AttributeDescription, 
vals SET OF value AttributeValue } 

With this change both DXER and XER would encode each attribute in the
list
as an element with the more meaningful name of <attribute>. This
change
makes no difference to the BER encoding, so it is neutral to LDAP and
does
not represent a new feature.

I would like to see each of the SEQUENCE OF and SET OF definitions in
the
LDAP ASN.1 module given a meaningful mnemonic identifier for the member
type
so as to facilitate better XML representations of LDAP operations
(whether
for XLDAP or any other purpose). If the working group allows it I'll
work
with Jim to make the additions.

Regards,
Steven




From owner-ietf-ldapbis@OpenLDAP.org  Wed Oct 22 22:58:08 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 WAA15569
	for <ldapbis-archive@lists.ietf.org>; Wed, 22 Oct 2003 22:58:08 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9N2qiHu002970;
	Thu, 23 Oct 2003 02:57:21 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9N2lZt5002745;
	Thu, 23 Oct 2003 02:47:35 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 23 Oct 2003 02:47:35 +0000
Received: from adacel.com (gunsmoke.adacel.com.au [210.11.130.7])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9N2lWHS002731
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 23 Oct 2003 02:47:33 GMT
	(envelope-from steven.legg@adacel.com.au)
Received: from nexus.adacel.com (Not Verified[10.32.240.1]) by adacel.com with NetIQ MailMarshal (v5.5.3.16)
	id <B000188565>; Thu, 23 Oct 2003 12:41:19 +1000
Received: (qmail 28303 invoked from network); 23 Oct 2003 02:47:11 -0000
Received: from unknown (HELO adacel.com.au) (10.32.24.165)
  by nexus.adacel.com with SMTP; 23 Oct 2003 02:47:11 -0000
Message-ID: <3F97412E.1050305@adacel.com.au>
Date: Thu, 23 Oct 2003 13:47:10 +1100
From: Steven Legg <steven.legg@adacel.com.au>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3.1) Gecko/20030425
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Jim Sermersheim <jimse@novell.com>
CC: ietf-ldapbis@OpenLDAP.org
Subject: Re: WG Last Call: draft-ietf-ldapbis-protocol-17.txt	[corrected]
References: <sf96e6cd.046@prv-mail20.provo.novell.com>
In-Reply-To: <sf96e6cd.046@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


Jim,

You've chosen the identifiers I would choose except in one case
(see below).

Jim Sermersheim wrote:
> So, the changes would produce these types, correct?
>  
> AttributeSelection ::= SEQUENCE OF selection LDAPString
> 
> Attribute ::= SEQUENCE {
>    type    AttributeDescription,
>    vals    SET SIZE (1..MAX) OF value AttributeValue }
> 
> Referral ::= SEQUENCE SIZE (1..MAX) OF url URL
> 
> Controls ::= SEQUENCE OF control Control
> 
> Filter ::= CHOICE {
>    and             [0] SET SIZE (1..MAX) OF filter Filter,
>    or              [1] SET SIZE (1..MAX) OF filter Filter,
>    not             [2] Filter,
>    equalityMatch   [3] AttributeValueAssertion,
>    substrings      [4] SubstringFilter,
>    greaterOrEqual  [5] AttributeValueAssertion,
>    lessOrEqual     [6] AttributeValueAssertion,
>    present         [7] AttributeDescription,
>    approxMatch     [8] AttributeValueAssertion,
>    extensibleMatch [9] MatchingRuleAssertion }
> 
> SubstringFilter ::= SEQUENCE {
>    type            AttributeDescription,
>    -- at least one must be present,
>    -- initial and final can occur at most once
>    substrings      SEQUENCE SIZE (1..MAX) OF substring CHOICE {
>       initial [0] AssertionValue,
>       any     [1] AssertionValue,
>       final   [2] AssertionValue } }
> 
> PartialAttributeList ::= SEQUENCE OF partialAttribute PartialAttribute

I would just use "attribute" rather than "partialAttribute".

Regards,
Steven

> 
> PartialAttribute ::= SEQUENCE {
>    type   AttributeDescription,
>    vals   SET OF value AttributeValue }
> 
> SearchResultReference ::= 
>    [APPLICATION 19] SEQUENCE SIZE (1..MAX) OF url URL
> 
> ModifyRequest ::= [APPLICATION 6] SEQUENCE {
>    object          LDAPDN,
>    changes         SEQUENCE OF change SEQUENCE {
>       operation       ENUMERATED {
>          add     (0),
>          delete  (1),
>          replace (2) },
>       modification    PartialAttribute } }
> 
> AttributeList ::= SEQUENCE OF attribute Attribute
> 
> I'll do this unless there are objections.
>  
> Jim
> 
> 
>>>>"Steven Legg" <steven.legg@adacel.com.au> 10/6/03 6:07:13 PM >>>
> 
> 
> Folks,
> 
> I recently published an Internet draft on an XML rendition of the LDAP
> protocol (called XLDAP) that is realized by applying a set of XML
> encoding rules to the ASN.1 types in the ASN.1 specification for LDAP
> (specifically the ASN.1 in the protocols draft being last-called).
> 
> The XML produced is neat and tidy except with respect to the instances
> of the member type of a SEQUENCE OF or SET OF ASN.1 type.
> 
> Consider this example drawn from the protocols draft:
> 
> AttributeList ::= SEQUENCE OF SEQUENCE { 
> type AttributeDescription, 
> vals SET OF AttributeValue } 
> 
> Using my Directory XML Encoding Rules (DXER) to encode an attribute
> list,
> each attribute in the list is encoded as an element with the safe, but
> bland name of <item>. Using the ITU-T's XML Encoding Rules (XER), each
> attribute in the list is encoded as an element with the unappealing
> name
> of <SEQUENCE>.
> 
> However the situation can be improved since the version of ASN.1 that
> the protocols draft is referencing allows an ASN.1 identifier after a
> SEQUENCE OF or SET OF and before the definition of the member type.
> 
> For example:
> 
> AttributeList ::= SEQUENCE OF attribute SEQUENCE { 
> type AttributeDescription, 
> vals SET OF value AttributeValue } 
> 
> With this change both DXER and XER would encode each attribute in the
> list
> as an element with the more meaningful name of <attribute>. This
> change
> makes no difference to the BER encoding, so it is neutral to LDAP and
> does
> not represent a new feature.
> 
> I would like to see each of the SEQUENCE OF and SET OF definitions in
> the
> LDAP ASN.1 module given a meaningful mnemonic identifier for the member
> type
> so as to facilitate better XML representations of LDAP operations
> (whether
> for XLDAP or any other purpose). If the working group allows it I'll
> work
> with Jim to make the additions.
> 
> Regards,
> Steven
> 
> 
> 
> 



From owner-ietf-ldapbis@OpenLDAP.org  Wed Oct 22 22:58: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 WAA15599
	for <ldapbis-archive@lists.ietf.org>; Wed, 22 Oct 2003 22:58:39 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9N2qiHs002970;
	Thu, 23 Oct 2003 02:57:21 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9N2q4m3002927;
	Thu, 23 Oct 2003 02:52:04 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 23 Oct 2003 02:52:04 +0000
Received: from prv-mail20.provo.novell.com (prv-mail20.provo.novell.com [137.65.81.122])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9N2q2HS002907
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 23 Oct 2003 02:52:02 GMT
	(envelope-from jimse@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Wed, 22 Oct 2003 20:51:42 -0600
Message-Id: <sf96edde.048@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.2 Beta
Date: Wed, 22 Oct 2003 20:51:34 -0600
From: "Jim Sermersheim" <jimse@novell.com>
To: <steven.legg@adacel.com.au>
Cc: <ietf-ldapbis@OpenLDAP.org>
Subject: Re: WG Last Call:
	draft-ietf-ldapbis-protocol-17.txt	[corrected]
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__PartA4FA0126.1__="
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.

--=__PartA4FA0126.1__=
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Agreed.

>>> Steven Legg <steven.legg@adacel.com.au> 10/22/03 8:47:10 PM >>>

Jim,

You've chosen the identifiers I would choose except in one case
(see below).

Jim Sermersheim wrote:
> So, the changes would produce these types, correct?
> 
> AttributeSelection ::= SEQUENCE OF selection LDAPString
> 
> Attribute ::= SEQUENCE {
> type AttributeDescription,
> vals SET SIZE (1..MAX) OF value AttributeValue }
> 
> Referral ::= SEQUENCE SIZE (1..MAX) OF url URL
> 
> Controls ::= SEQUENCE OF control Control
> 
> Filter ::= CHOICE {
> and [0] SET SIZE (1..MAX) OF filter Filter,
> or [1] SET SIZE (1..MAX) OF filter Filter,
> not [2] Filter,
> equalityMatch [3] AttributeValueAssertion,
> substrings [4] SubstringFilter,
> greaterOrEqual [5] AttributeValueAssertion,
> lessOrEqual [6] AttributeValueAssertion,
> present [7] AttributeDescription,
> approxMatch [8] AttributeValueAssertion,
> extensibleMatch [9] MatchingRuleAssertion }
> 
> SubstringFilter ::= SEQUENCE {
> type AttributeDescription,
> -- at least one must be present,
> -- initial and final can occur at most once
> substrings SEQUENCE SIZE (1..MAX) OF substring CHOICE {
> initial [0] AssertionValue,
> any [1] AssertionValue,
> final [2] AssertionValue } }
> 
> PartialAttributeList ::= SEQUENCE OF partialAttribute
PartialAttribute

I would just use "attribute" rather than "partialAttribute".

Regards,
Steven

> 
> PartialAttribute ::= SEQUENCE {
> type AttributeDescription,
> vals SET OF value AttributeValue }
> 
> SearchResultReference ::= 
> [APPLICATION 19] SEQUENCE SIZE (1..MAX) OF url URL
> 
> ModifyRequest ::= [APPLICATION 6] SEQUENCE {
> object LDAPDN,
> changes SEQUENCE OF change SEQUENCE {
> operation ENUMERATED {
> add (0),
> delete (1),
> replace (2) },
> modification PartialAttribute } }
> 
> AttributeList ::= SEQUENCE OF attribute Attribute
> 
> I'll do this unless there are objections.
> 
> Jim
> 
> 
>>>>"Steven Legg" < steven.legg@adacel.com.au > 10/6/03 6:07:13 PM >>>
> 
> 
> Folks,
> 
> I recently published an Internet draft on an XML rendition of the
LDAP
> protocol (called XLDAP) that is realized by applying a set of XML
> encoding rules to the ASN.1 types in the ASN.1 specification for
LDAP
> (specifically the ASN.1 in the protocols draft being last-called).
> 
> The XML produced is neat and tidy except with respect to the
instances
> of the member type of a SEQUENCE OF or SET OF ASN.1 type.
> 
> Consider this example drawn from the protocols draft:
> 
> AttributeList ::= SEQUENCE OF SEQUENCE { 
> type AttributeDescription, 
> vals SET OF AttributeValue } 
> 
> Using my Directory XML Encoding Rules (DXER) to encode an attribute
> list,
> each attribute in the list is encoded as an element with the safe,
but
> bland name of <item>. Using the ITU-T's XML Encoding Rules (XER),
each
> attribute in the list is encoded as an element with the unappealing
> name
> of <SEQUENCE>.
> 
> However the situation can be improved since the version of ASN.1
that
> the protocols draft is referencing allows an ASN.1 identifier after
a
> SEQUENCE OF or SET OF and before the definition of the member type.
> 
> For example:
> 
> AttributeList ::= SEQUENCE OF attribute SEQUENCE { 
> type AttributeDescription, 
> vals SET OF value AttributeValue } 
> 
> With this change both DXER and XER would encode each attribute in
the
> list
> as an element with the more meaningful name of <attribute>. This
> change
> makes no difference to the BER encoding, so it is neutral to LDAP
and
> does
> not represent a new feature.
> 
> I would like to see each of the SEQUENCE OF and SET OF definitions
in
> the
> LDAP ASN.1 module given a meaningful mnemonic identifier for the
member
> type
> so as to facilitate better XML representations of LDAP operations
> (whether
> for XLDAP or any other purpose). If the working group allows it I'll
> work
> with Jim to make the additions.
> 
> Regards,
> Steven
> 
> 
> 
> 


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

<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 5.50.4933.1800" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Microsoft Sans Serif">Agreed.<BR><BR>&gt;&gt;&gt; Steven Legg &lt;steven.legg@adacel.com.au&gt; 10/22/03 8:47:10 PM &gt;&gt;&gt;<BR><BR>Jim,<BR><BR>You've chosen the identifiers I would choose except in one case<BR>(see below).<BR><BR>Jim Sermersheim wrote:<BR>&gt; So, the changes would produce these types, correct?<BR>&gt; <BR>&gt; AttributeSelection ::= SEQUENCE OF selection LDAPString<BR>&gt; <BR>&gt; Attribute ::= SEQUENCE {<BR>&gt; type AttributeDescription,<BR>&gt; vals SET SIZE (1..MAX) OF value AttributeValue }<BR>&gt; <BR>&gt; Referral ::= SEQUENCE SIZE (1..MAX) OF url URL<BR>&gt; <BR>&gt; Controls ::= SEQUENCE OF control Control<BR>&gt; <BR>&gt; Filter ::= CHOICE {<BR>&gt; and [0] SET SIZE (1..MAX) OF filter Filter,<BR>&gt; or [1] SET SIZE (1..MAX) OF filter Filter,<BR>&gt; not [2] Filter,<BR>&gt; equalityMatch [3] AttributeValueAssertion,<BR>&gt; substrings [4] SubstringFilter,<BR>&gt; greaterOrEqual [5] AttributeValueA!
 ssertion,<BR>&gt; lessOrEqual [6] AttributeValueAssertion,<BR>&gt; present [7] AttributeDescription,<BR>&gt; approxMatch [8] AttributeValueAssertion,<BR>&gt; extensibleMatch [9] MatchingRuleAssertion }<BR>&gt; <BR>&gt; SubstringFilter ::= SEQUENCE {<BR>&gt; type AttributeDescription,<BR>&gt; -- at least one must be present,<BR>&gt; -- initial and final can occur at most once<BR>&gt; substrings SEQUENCE SIZE (1..MAX) OF substring CHOICE {<BR>&gt; initial [0] AssertionValue,<BR>&gt; any [1] AssertionValue,<BR>&gt; final [2] AssertionValue } }<BR>&gt; <BR>&gt; PartialAttributeList ::= SEQUENCE OF partialAttribute PartialAttribute<BR><BR>I would just use "attribute" rather than "partialAttribute".<BR><BR>Regards,<BR>Steven<BR><BR>&gt; <BR>&gt; PartialAttribute ::= SEQUENCE {<BR>&gt; type AttributeDescription,<BR>&gt; vals SET OF value AttributeValue }<BR>&gt; <BR>&gt; SearchResultReference ::= <BR>&gt; [APPLICATION 19] SEQUENCE SIZE (1..MAX) OF url URL<BR>&gt; <BR>&gt; ModifyRe!
 quest ::= [APPLICATION 6] SEQUENCE {<BR>&gt; object LDAPDN,<BR!
 >&gt; ch

anges SEQUENCE OF change SEQUENCE {<BR>&gt; operation ENUMERATED {<BR>&gt; add (0),<BR>&gt; delete (1),<BR>&gt; replace (2) },<BR>&gt; modification PartialAttribute } }<BR>&gt; <BR>&gt; AttributeList ::= SEQUENCE OF attribute Attribute<BR>&gt; <BR>&gt; I'll do this unless there are objections.<BR>&gt; <BR>&gt; Jim<BR>&gt; <BR>&gt; <BR>&gt;&gt;&gt;&gt;"Steven Legg" &lt;<U> <A href="mailto:steven.legg@adacel.com.au">steven.legg@adacel.com.au</A></U> &gt; 10/6/03 6:07:13 PM &gt;&gt;&gt;<BR>&gt; <BR>&gt; <BR>&gt; Folks,<BR>&gt; <BR>&gt; I recently published an Internet draft on an XML rendition of the LDAP<BR>&gt; protocol (called XLDAP) that is realized by applying a set of XML<BR>&gt; encoding rules to the ASN.1 types in the ASN.1 specification for LDAP<BR>&gt; (specifically the ASN.1 in the protocols draft being last-called).<BR>&gt; <BR>&gt; The XML produced is neat and tidy except with respect to the instances<BR>&gt; of the member type of a SEQUENCE OF or SET OF ASN.1 type!
 .<BR>&gt; <BR>&gt; Consider this example drawn from the protocols draft:<BR>&gt; <BR>&gt; AttributeList ::= SEQUENCE OF SEQUENCE { <BR>&gt; type AttributeDescription, <BR>&gt; vals SET OF AttributeValue } <BR>&gt; <BR>&gt; Using my Directory XML Encoding Rules (DXER) to encode an attribute<BR>&gt; list,<BR>&gt; each attribute in the list is encoded as an element with the safe, but<BR>&gt; bland name of &lt;item&gt;. Using the ITU-T's XML Encoding Rules (XER), each<BR>&gt; attribute in the list is encoded as an element with the unappealing<BR>&gt; name<BR>&gt; of &lt;SEQUENCE&gt;.<BR>&gt; <BR>&gt; However the situation can be improved since the version of ASN.1 that<BR>&gt; the protocols draft is referencing allows an ASN.1 identifier after a<BR>&gt; SEQUENCE OF or SET OF and before the definition of the member type.<BR>&gt; <BR>&gt; For example:<BR>&gt; <BR>&gt; AttributeList ::= SEQUENCE OF attribute SEQUENCE { <BR>&gt; type AttributeDescription, <BR>&gt; vals SET OF value!
  AttributeValue } <BR>&gt; <BR>&gt; With this change both DXER!
  and XER

 would encode each attribute in the<BR>&gt; list<BR>&gt; as an element with the more meaningful name of &lt;attribute&gt;. This<BR>&gt; change<BR>&gt; makes no difference to the BER encoding, so it is neutral to LDAP and<BR>&gt; does<BR>&gt; not represent a new feature.<BR>&gt; <BR>&gt; I would like to see each of the SEQUENCE OF and SET OF definitions in<BR>&gt; the<BR>&gt; LDAP ASN.1 module given a meaningful mnemonic identifier for the member<BR>&gt; type<BR>&gt; so as to facilitate better XML representations of LDAP operations<BR>&gt; (whether<BR>&gt; for XLDAP or any other purpose). If the working group allows it I'll<BR>&gt; work<BR>&gt; with Jim to make the additions.<BR>&gt; <BR>&gt; Regards,<BR>&gt; Steven<BR>&gt; <BR>&gt; <BR>&gt; <BR>&gt; <BR><BR></BODY></HTML>
--=__PartA4FA0126.1__=--


From owner-ietf-ldapbis@OpenLDAP.org  Wed Oct 22 23:19: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 XAA16116
	for <ldapbis-archive@lists.ietf.org>; Wed, 22 Oct 2003 23:19:26 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9N3AnHo005175;
	Thu, 23 Oct 2003 03:18:31 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9N35N6X004874;
	Thu, 23 Oct 2003 03:05:23 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 23 Oct 2003 03:05:23 +0000
Received: from prv-mail20.provo.novell.com (prv-mail20.provo.novell.com [137.65.81.122])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9N35LHS004837
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 23 Oct 2003 03:05:22 GMT
	(envelope-from jimse@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Wed, 22 Oct 2003 21:05:01 -0600
Message-Id: <sf96f0fd.035@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.2 Beta
Date: Wed, 22 Oct 2003 21:04:43 -0600
From: "Jim Sermersheim" <jimse@novell.com>
To: <ietf-ldapbis@OpenLDAP.org>
Subject: Protocol: MUST provide supportedVersion
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__PartDE807B5B.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>

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.

--=__PartDE807B5B.0__=
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Kurt wrote:
>>   Clients may determine the protocol versions a server supports by 
>>   reading the supportedLDAPVersion attribute from the root DSE 
>>   [Models]. Servers which implement version 3 or later MUST provide

>>   this attribute. 
>
>Drop the MUST.  As the returned contents of the root DSE may be     
>subject to ACLs, clients need to deal with the case where an LDAPv3   
  
>server does not provide a root DSE or does not provide this
attribute.
>Most clients simply do blind (e.g., no root DSE checks) LDAPv3 binds
>instead.

This imperative has been here all along. I worry that there are clients
that already rely on this MUST in order to discover the protocol
version, rather than using the Bind/failover method.
 
Jim

--=__PartDE807B5B.0__=
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 5.50.4933.1800" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Microsoft Sans Serif">
<DIV>Kurt wrote:</DIV>
<DIV>&gt;&gt;&nbsp;&nbsp; Clients may determine the protocol versions a server supports by <BR>&gt;&gt;&nbsp;&nbsp; reading the supportedLDAPVersion attribute from the root DSE <BR>&gt;&gt;&nbsp;&nbsp; [Models]. Servers which implement version 3 or later MUST provide <BR>&gt;&gt;&nbsp;&nbsp; this attribute. <BR>&gt;<BR>&gt;Drop the MUST.&nbsp; As the returned contents of the root DSE may be&nbsp;&nbsp;&nbsp;&nbsp; <BR>&gt;subject to ACLs, clients need to deal with the case where an LDAPv3&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <BR>&gt;server does not provide a root DSE or does not provide this attribute.<BR>&gt;Most clients simply do blind (e.g., no root DSE checks) LDAPv3 binds<BR>&gt;instead.<BR></DIV>
<DIV>This imperative has been here all along. I worry that there are clients that already rely on this MUST in order to discover the protocol version, rather than using the Bind/failover method.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Jim</DIV></BODY></HTML>
--=__PartDE807B5B.0__=--


From owner-ietf-ldapbis@OpenLDAP.org  Thu Oct 23 00:31: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 AAA18718
	for <ldapbis-archive@lists.ietf.org>; Thu, 23 Oct 2003 00:31:48 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9N4SjHW010297;
	Thu, 23 Oct 2003 04:29:05 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9N4PTvb010263;
	Thu, 23 Oct 2003 04:25:29 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 23 Oct 2003 04:25:29 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9N4PSHS010253
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 23 Oct 2003 04:25:28 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from gypsy.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.9/8.12.9) with ESMTP id h9N4PLlg011491;
	Thu, 23 Oct 2003 04:25:21 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.0.22.0.20031022204808.02b59298@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
Date: Wed, 22 Oct 2003 21:24:45 -0700
To: "Jim Sermersheim" <jimse@novell.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: Protocol: MUST provide supportedVersion
Cc: <ietf-ldapbis@OpenLDAP.org>
In-Reply-To: <sf96f0fd.035@prv-mail20.provo.novell.com>
References: <sf96f0fd.035@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>


>I worry that there are clients that already rely on this MUST in order to discover the protocol version, rather than using the Bind/failover method.

RFC 2251 didn't say supportedLDAPversion **always** had to be
provided when requested.  RFC 2251 allowed:
        servers to require binding before searching
        servers to require start tls before searching
        servers to subject returned attributes to ACLS
                (including, specifically, root DSE attributes)
        etc.

and, hence, implicitly required clients deal with these cases.

A client which doesn't will run into interoperability problems. 
Access controls upon the root DSE are common. Administrative
restrictions requiring bind before search are fairly common.
Administrative restrictions requiring startTLS before search
are fairly common.  Etc..

If we accept the argument that a "MUST provide" is necessary for interoperability, then we not only keep the MUST be we must
disallow the RFC 2251 allowed behaviors listed above. 

If we reject the argument, then just need to drop the MUST.
It might be appropriate to clarify again that search returns
are subject to all kinds of administrative policies, but I think
we've covered that repeatedly.

Kurt



From owner-ietf-ldapbis@OpenLDAP.org  Thu Oct 23 10:38: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 KAA25976
	for <ldapbis-archive@lists.ietf.org>; Thu, 23 Oct 2003 10:38:10 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9NESmHc038588;
	Thu, 23 Oct 2003 14:36:07 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9NEPVRO038301;
	Thu, 23 Oct 2003 14:25:31 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 23 Oct 2003 14:25:31 +0000
Received: from e2.ny.us.ibm.com (e2.ny.us.ibm.com [32.97.182.102])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9NEPTHS038270
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 23 Oct 2003 14:25:29 GMT
	(envelope-from jmcmeek@us.ibm.com)
Received: from northrelay02.pok.ibm.com (northrelay02.pok.ibm.com [9.56.224.150])
	by e2.ny.us.ibm.com (8.12.10/8.12.2) with ESMTP id h9NEP3hp353646;
	Thu, 23 Oct 2003 10:25:03 -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.6) with ESMTP id h9NEP1eQ229314;
	Thu, 23 Oct 2003 10:25:02 -0400
Subject: Re: REVISED protocol review notes [LONG]
To: "Jim Sermersheim" <jimse@novell.com>
Cc: ietf-ldapbis@OpenLDAP.org
X-Mailer: Lotus Notes Release 5.0.12   February 13, 2003
Message-ID: <OF0BD829A3.8978FA5F-ON86256DC8.004E69A5-86256DC8.004F31B2@us.ibm.com>
From: John McMeeking <jmcmeek@us.ibm.com>
Date: Thu, 23 Oct 2003 09:24:59 -0500
X-MIMETrack: Serialize by Router on d27ml001/27/M/IBM(Release 6.5|September 18, 2003) at
 10/23/2003 09:25:01 AM
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 h9NEPTHS038291
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 we all really ought to get up to date on ASN.1.  And I can see
where this ASN.1 feature could be pretty useful, particularly for refining
a more complex (or at least longer) definition.

In this particular case, I don't the advantage over separate definitions.
It isn't any shorter.  And it's already been suggested that it be
accompanied by further explanation since it isn't obvious to those readers
that are not up to date.

John  McMeeking



                                                                                                                       
                      "Jim Sermersheim"                                                                                
                      <jimse@novell.com>          To:       <steven.legg@adacel.com.au>                                
                      Sent by:                    cc:       <ietf-ldapbis@OpenLDAP.org>, <Kurt@OpenLDAP.org>           
                      owner-ietf-ldapbis@O        Subject:  Re: REVISED protocol review notes [LONG]                   
                      penLDAP.org                                                                                      
                                                                                                                       
                                                                                                                       
                      10/22/2003 10:29 AM                                                                              
                                                                                                                       
                                                                                                                       





>>> Steven Legg <steven.legg@adacel.com.au> 10/22/03 1:17:00 AM >>>
>Yes, but you could also do this:
>
>PartialAttribute ::= SEQUENCE {
>type AttributeDescription,
>vals SET OF AttributeValue }
>
>Attribute ::= PartialAttribute(WITH COMPONENTS {..., vals (SIZE(1..MAX))})
Wow. This looks cool... but having never seen such a thing, I had to do a
double take. What do others think about using this kind of definition?

>You could also in-line the right hand side of the Attribute assignment
>statement everywhere Attribute is needed and then rename PartialAttribute
>to just Attribute.
True, it's only used in one place right now (AttributeList)

>By the way, are you intending to put identifiers into each of
>the SET OF and SEQUENCE OF notations ? I so, do you want me to
>make some appropriate suggestions ?
I think so, but I wanted to ping the list one more time about this before
deciding.

Jim





From owner-ietf-ldapbis@OpenLDAP.org  Sun Oct 26 07:28:08 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 HAA16149
	for <ldapbis-archive@lists.ietf.org>; Sun, 26 Oct 2003 07:28:08 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9QCNCHW044649;
	Sun, 26 Oct 2003 12:25:44 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9QCJL56044440;
	Sun, 26 Oct 2003 12:19:21 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Sun, 26 Oct 2003 12:19:21 +0000
Received: from new_bruno (bruno.gric.com [216.231.202.145])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9QCJJHS044365
	for <ietf-ldapbis@OpenLDAP.org>; Sun, 26 Oct 2003 12:19:19 GMT
	(envelope-from d.w.chadwick@salford.ac.uk)
Received: from salford.ac.uk (1Cust179.tnt3.dca5.da.uu.net [67.249.210.179])
	by new_bruno (8.12.7/8.12.7) with ESMTP id h9QCHrM4015978
	for <ietf-ldapbis@OpenLDAP.org>; Sun, 26 Oct 2003 04:17:58 -0800 (PST)
Message-ID: <3F9BBB94.BBE78984@salford.ac.uk>
Date: Sun, 26 Oct 2003 12:18:28 +0000
From: David Chadwick <d.w.chadwick@salford.ac.uk>
Organization: University of Salford
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: LDAP BIS <ietf-ldapbis@OpenLDAP.org>
Subject: New text for X.501
Content-Type: multipart/mixed;
 boundary="------------AD40955E977236082675D039"
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 multi-part message in MIME format.
--------------AD40955E977236082675D039
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Dear LDAPers

At the recent Geneva meeting of the X.500 group, Defect Report 303 was
discussed. This concerns the fact that a user cannot be guaranteed that
the information presented to LDAP/X.500 server in an update operation is
subsequently returned unaltered in a Search operation. Due to this, in
the PKIX work we are adding text to the IDs specifically to say that for
X.509 certificates and CRLs the data must not be altered by the LDAP
server. The X.500 group is going to go one step further than this and
state that no attributes must be altered by the server and must be
returned exactly as presented, although a server may store a
canonicalised form for efficient matching if it so desires.

The defect report can only address the 1997 and 2001 versions of X.500,
since the 1993 version that LDAP is based in is no longer supported by
ITU-T/ISO.

Here is the gist of the proposed text to fix the defect report.

Stored attribute values must be held as supplied. We propose to add text
to X.501 in clause 8.5 and in 8.8.1, where we will point out that
rationalizations to stored values for the purposes of matching do not
effect the stored value. We will also add text to clause 6.1 of x.520
stating that the rationalizations describe in the matching rules are
ephemeral, for the purpose of the match only, and will not affect the
stored value.

Regards

David

-- 

*****************************************************************

David W. Chadwick, BSc PhD
Professor of Information Systems Security
IS Institute, University of Salford, Salford M5 4WT
Tel: +44 161 295 5351  Fax +44 01484 532930
Mobile: +44 77 96 44 7184
Email: D.W.Chadwick@salford.ac.uk
Home Page:  http://www.salford.ac.uk/its024/chadwick.htm
Research Web site: http://sec.isi.salford.ac.uk
Entrust key validation string: MLJ9-DU5T-HV8J
PGP Key ID is 0xBC238DE5

*****************************************************************
--------------AD40955E977236082675D039
Content-Type: text/x-vcard; charset=us-ascii;
 name="d.w.chadwick.vcf"
Content-Description: Card for David Chadwick
Content-Disposition: attachment;
 filename="d.w.chadwick.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Chadwick;David
tel;cell:+44 77 96 44 7184
tel;fax:+44 1484 532930
tel;home:+44 1484 352238
tel;work:+44 161 295 5351
x-mozilla-html:FALSE
url:http://sec.isi.salford.ac.uk
org:University of Salford;IS Institute
version:2.1
email;internet:d.w.chadwick@salford.ac.uk
title:Professor of Information Security
adr;quoted-printable:;;The Crescent=0D=0A;Salford;Greater Manchester;M5 4WT;England
note;quoted-printable:Research Projects: http://sec.isi.salford.ac.uk=0D=0A=0D=0AEntrust key validation string: CJ94-LKWD-BSXB ...........=0D=0A=0D=0APGP Key ID is 0xBC238DE5
x-mozilla-cpt:;-18752
fn:David Chadwick
end:vcard

--------------AD40955E977236082675D039--



From owner-ietf-ldapbis@OpenLDAP.org  Sun Oct 26 18:55:42 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05357
	for <ldapbis-archive@lists.ietf.org>; Sun, 26 Oct 2003 18:55:41 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9QNrGHW060033;
	Sun, 26 Oct 2003 23:54:34 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9QNq5ik060024;
	Sun, 26 Oct 2003 23:52:05 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Sun, 26 Oct 2003 23:52:05 +0000
Received: from adacel.com (gunsmoke.adacel.com.au [210.11.130.7])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9QNpwHS060010
	for <ietf-ldapbis@OpenLDAP.org>; Sun, 26 Oct 2003 23:51:59 GMT
	(envelope-from steven.legg@adacel.com.au)
Received: from nexus.adacel.com (Not Verified[10.32.240.1]) by adacel.com with NetIQ MailMarshal (v5.5.3.16)
	id <B00018ce1a>; Mon, 27 Oct 2003 10:45:16 +1100
Received: (qmail 10428 invoked from network); 26 Oct 2003 23:51:37 -0000
Received: from unknown (HELO adacel.com.au) (10.32.24.165)
  by nexus.adacel.com with SMTP; 26 Oct 2003 23:51:37 -0000
Message-ID: <3F9C5E08.1040104@adacel.com.au>
Date: Mon, 27 Oct 2003 10:51:36 +1100
From: Steven Legg <steven.legg@adacel.com.au>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3.1) Gecko/20030425
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: David Chadwick <d.w.chadwick@salford.ac.uk>
CC: LDAP BIS <ietf-ldapbis@OpenLDAP.org>, OSIdirectory@az05.bull.com
Subject: Re: New text for X.501
References: <3F9BBB94.BBE78984@salford.ac.uk>
In-Reply-To: <3F9BBB94.BBE78984@salford.ac.uk>
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


David,

David Chadwick wrote:
> Dear LDAPers
> 
> At the recent Geneva meeting of the X.500 group, Defect Report 303 was
> discussed. This concerns the fact that a user cannot be guaranteed that
> the information presented to LDAP/X.500 server in an update operation is
> subsequently returned unaltered in a Search operation. Due to this, in
> the PKIX work we are adding text to the IDs specifically to say that for
> X.509 certificates and CRLs the data must not be altered by the LDAP
> server. The X.500 group is going to go one step further than this and
> state that no attributes must be altered by the server and must be
> returned exactly as presented,

I think this change is ill-advised, as the requirement cannot be enforced
in a mixed LDAP/X.500 distributed environment. An attribute value that is
entered in an LDAP-specific encoding has to be transformed into BER to be
carried in DSP or DISP. There is no guarantee that the exact LDAP-specific
encoding of the original attribute value will be reconstructed by the
receiving DSA. Preservation of the exact encoding of PKI attributes can
only be made to work in the general case because the LDAP encoding and the
X.500 encoding is the same - BER. For most syntaxes this is not the case.

The XED specifications introduce a third way of encoding directory data (DXER),
which only increases the difficulty of preserving the original encoding.

If the X.500 standards add this requirement then, as a practical necessity,
I will have to disregard it. However, I will continue to preserve the abstract
value of attribute values to the extent that it is possible to do so.

Regards,
Steven

> although a server may store a
> canonicalised form for efficient matching if it so desires.
> 
> The defect report can only address the 1997 and 2001 versions of X.500,
> since the 1993 version that LDAP is based in is no longer supported by
> ITU-T/ISO.
> 
> Here is the gist of the proposed text to fix the defect report.
> 
> Stored attribute values must be held as supplied. We propose to add text
> to X.501 in clause 8.5 and in 8.8.1, where we will point out that
> rationalizations to stored values for the purposes of matching do not
> effect the stored value. We will also add text to clause 6.1 of x.520
> stating that the rationalizations describe in the matching rules are
> ephemeral, for the purpose of the match only, and will not affect the
> stored value.
> 
> Regards
> 
> David
> 



From owner-ietf-ldapbis@OpenLDAP.org  Sun Oct 26 20:43: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 UAA07684
	for <ldapbis-archive@lists.ietf.org>; Sun, 26 Oct 2003 20:43:46 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9R1fHHW062900;
	Mon, 27 Oct 2003 01:41:36 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9R1e8Dq062885;
	Mon, 27 Oct 2003 01:40:08 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 27 Oct 2003 01:40:08 +0000
Received: from ausyms50.ca.com ([155.35.248.106])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9R1e6HS062862
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 27 Oct 2003 01:40:06 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.6713);
	 Mon, 27 Oct 2003 12:39:45 +1100
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: New text for X.501
Date: Mon, 27 Oct 2003 12:39:44 +1100
Message-ID: <1395B4B334FCC143B36AF788E68B6381A9A3D2@ausyms21.ca.com>
Thread-Topic: New text for X.501
Thread-Index: AcOcHI2Y9szf/ZgHSPe+/nTUc77HewADR+Ew
From: "Ramsay, Ron" <Ron.Ramsay@ca.com>
To: "Steven Legg" <steven.legg@adacel.com.au>,
        "David Chadwick" <d.w.chadwick@salford.ac.uk>
Cc: "LDAP BIS" <ietf-ldapbis@OpenLDAP.org>, <OSIdirectory@az05.bull.com>
X-OriginalArrivalTime: 27 Oct 2003 01:39:45.0041 (UTC) FILETIME=[330B4810:01C39C2B]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by boole.openldap.org id h9R1e7HS062876
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 would be interesting to see which syntaxes can't be preserved.

Assuming that the access protocol is LDAP, directoryString can be mapped because X.500 has the UTF8String option. Any LDAP type whose encoding is ASN.1 can also be mapped. Integers can be mapped.

PrintableString synataxes seem not to be mappable, except that the characters should be able to be transcribed as they should already be printable.

G3Fax, audio, jpeg all go across as octet string.

Actually, I would think the only problem would be with data provided from non-LDAP sources.

I think it is clear that X.500 can make the requirement.

LDAP can make the requirement but servers may not be able to conform to it, but, from the LDAP perspective, there is nothing to prevent them conforming.

Ron

-----Original Message-----
From: owner-ietf-ldapbis@OpenLDAP.org
[mailto:owner-ietf-ldapbis@OpenLDAP.org]On Behalf Of Steven Legg
Sent: Monday, 27 October 2003 10:52
To: David Chadwick
Cc: LDAP BIS; OSIdirectory@az05.bull.com
Subject: Re: New text for X.501



David,

David Chadwick wrote:
> Dear LDAPers
> 
> At the recent Geneva meeting of the X.500 group, Defect Report 303 was
> discussed. This concerns the fact that a user cannot be guaranteed that
> the information presented to LDAP/X.500 server in an update operation is
> subsequently returned unaltered in a Search operation. Due to this, in
> the PKIX work we are adding text to the IDs specifically to say that for
> X.509 certificates and CRLs the data must not be altered by the LDAP
> server. The X.500 group is going to go one step further than this and
> state that no attributes must be altered by the server and must be
> returned exactly as presented,

I think this change is ill-advised, as the requirement cannot be enforced
in a mixed LDAP/X.500 distributed environment. An attribute value that is
entered in an LDAP-specific encoding has to be transformed into BER to be
carried in DSP or DISP. There is no guarantee that the exact LDAP-specific
encoding of the original attribute value will be reconstructed by the
receiving DSA. Preservation of the exact encoding of PKI attributes can
only be made to work in the general case because the LDAP encoding and the
X.500 encoding is the same - BER. For most syntaxes this is not the case.

The XED specifications introduce a third way of encoding directory data (DXER),
which only increases the difficulty of preserving the original encoding.

If the X.500 standards add this requirement then, as a practical necessity,
I will have to disregard it. However, I will continue to preserve the abstract
value of attribute values to the extent that it is possible to do so.

Regards,
Steven

> although a server may store a
> canonicalised form for efficient matching if it so desires.
> 
> The defect report can only address the 1997 and 2001 versions of X.500,
> since the 1993 version that LDAP is based in is no longer supported by
> ITU-T/ISO.
> 
> Here is the gist of the proposed text to fix the defect report.
> 
> Stored attribute values must be held as supplied. We propose to add text
> to X.501 in clause 8.5 and in 8.8.1, where we will point out that
> rationalizations to stored values for the purposes of matching do not
> effect the stored value. We will also add text to clause 6.1 of x.520
> stating that the rationalizations describe in the matching rules are
> ephemeral, for the purpose of the match only, and will not affect the
> stored value.
> 
> Regards
> 
> David
> 





From owner-ietf-ldapbis@OpenLDAP.org  Sun Oct 26 23:56: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 XAA12134
	for <ldapbis-archive@lists.ietf.org>; Sun, 26 Oct 2003 23:56:50 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9R4rIHW067617;
	Mon, 27 Oct 2003 04:54:08 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9R4mEM2067564;
	Mon, 27 Oct 2003 04:48:14 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 27 Oct 2003 04:48:14 +0000
Received: from adacel.com (gunsmoke.adacel.com.au [210.11.130.7])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9R4mAHS067529
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 27 Oct 2003 04:48:11 GMT
	(envelope-from steven.legg@adacel.com.au)
Received: from nexus.adacel.com (Not Verified[10.32.240.1]) by adacel.com with NetIQ MailMarshal (v5.5.3.16)
	id <B00018d2df>; Mon, 27 Oct 2003 15:41:26 +1100
Received: (qmail 6053 invoked from network); 27 Oct 2003 04:47:49 -0000
Received: from unknown (HELO adacel.com.au) (10.32.24.165)
  by nexus.adacel.com with SMTP; 27 Oct 2003 04:47:49 -0000
Message-ID: <3F9CA374.9090907@adacel.com.au>
Date: Mon, 27 Oct 2003 15:47:48 +1100
From: Steven Legg <steven.legg@adacel.com.au>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3.1) Gecko/20030425
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Ramsay, Ron" <Ron.Ramsay@ca.com>
CC: David Chadwick <d.w.chadwick@salford.ac.uk>,
        LDAP BIS <ietf-ldapbis@OpenLDAP.org>
Subject: Re: New text for X.501
References: <1395B4B334FCC143B36AF788E68B6381A9A3D2@ausyms21.ca.com>
In-Reply-To: <1395B4B334FCC143B36AF788E68B6381A9A3D2@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,

Ramsay, Ron wrote:
 > It would be interesting to see which syntaxes can't be preserved.

Of the syntaxes defined in the syntaxes draft, values of the ones
prefixed with an asterisk are not guaranteed to be preserved by a
transformation from the LDAP-specific encoding to the BER encoding and
back to the LDAP-specific encoding. This is because they allow a variable
number of spaces, or contain case-insensitive labels, or allow short names
for OIDs.

* AttributeTypeDescription
* Bit String
* Boolean
   Country String
* DeliveryMethod
   Directory String
* DIT Content Rule Description
* DIT Structure Rule Description
* DN
* Enhanced Guide
* Facsimile Telephone Number
   Fax
   GeneralizedTime
* Guide
   IA5String
   Integer
   JPEG
* LDAP Syntax Description
* Matching Rule Description
* Matching Rule Use Description
* Name and Optional UID
* Name Form Description
   Numeric String
* Object Class Description
   Octet String
* OID
   Other Mailbox
* Postal Address
   Printable String
   Substring Assertion
   Telephone Number
* Teletex Terminal Identifier
   Telex Number
   UTC Time


Values of none of the LDAP syntaxes above can be guaranteed to be
preserved under a transformation from BER to LDAP-specific encoding
and back to BER (e.g. an LDIF dump and reload) since, in the very least,
the original BER encoding has a choice of the short form or the long
form for encoding lengths, and knowledge of this choice is lost in the
transformation from BER to LDAP-specific encoding.

 >
 > Assuming that the access protocol is LDAP, directoryString can be mapped
 > because X.500 has the UTF8String option. Any LDAP type whose encoding is
 > ASN.1 can also be mapped. Integers can be mapped.
 >
 > PrintableString synataxes seem not to be mappable, except that the
 > characters should be able to be transcribed as they should already be
 > printable.
 >
 > G3Fax, audio, jpeg all go across as octet string.
 >
 > Actually, I would think the only problem would be with data provided from
 > non-LDAP sources.
 >
 > I think it is clear that X.500 can make the requirement.

It is clear to me that it cannot.

Regards,
Steven

 >
 > LDAP can make the requirement but servers may not be able to conform to it,
 > but, from the LDAP perspective, there is nothing to prevent them conforming.
 >
 > Ron
 >
 > -----Original Message-----
 > From: owner-ietf-ldapbis@OpenLDAP.org
 > [mailto:owner-ietf-ldapbis@OpenLDAP.org]On Behalf Of Steven Legg
 > Sent: Monday, 27 October 2003 10:52
 > To: David Chadwick
 > Cc: LDAP BIS; OSIdirectory@az05.bull.com
 > Subject: Re: New text for X.501
 >
 >
 >
 > David,
 >
 > David Chadwick wrote:
 >
 >>Dear LDAPers
 >>
 >>At the recent Geneva meeting of the X.500 group, Defect Report 303 was
 >>discussed. This concerns the fact that a user cannot be guaranteed that
 >>the information presented to LDAP/X.500 server in an update operation is
 >>subsequently returned unaltered in a Search operation. Due to this, in
 >>the PKIX work we are adding text to the IDs specifically to say that for
 >>X.509 certificates and CRLs the data must not be altered by the LDAP
 >>server. The X.500 group is going to go one step further than this and
 >>state that no attributes must be altered by the server and must be
 >>returned exactly as presented,
 >
 >
 > I think this change is ill-advised, as the requirement cannot be enforced
 > in a mixed LDAP/X.500 distributed environment. An attribute value that is
 > entered in an LDAP-specific encoding has to be transformed into BER to be
 > carried in DSP or DISP. There is no guarantee that the exact LDAP-specific
 > encoding of the original attribute value will be reconstructed by the
 > receiving DSA. Preservation of the exact encoding of PKI attributes can
 > only be made to work in the general case because the LDAP encoding and the
 > X.500 encoding is the same - BER. For most syntaxes this is not the case.
 >
 > The XED specifications introduce a third way of encoding directory data
(DXER),
 > which only increases the difficulty of preserving the original encoding.
 >
 > If the X.500 standards add this requirement then, as a practical necessity,
 > I will have to disregard it. However, I will continue to preserve the abstract
 > value of attribute values to the extent that it is possible to do so.
 >
 > Regards,
 > Steven
 >
 >
 >>although a server may store a
 >>canonicalised form for efficient matching if it so desires.
 >>
 >>The defect report can only address the 1997 and 2001 versions of X.500,
 >>since the 1993 version that LDAP is based in is no longer supported by
 >>ITU-T/ISO.
 >>
 >>Here is the gist of the proposed text to fix the defect report.
 >>
 >>Stored attribute values must be held as supplied. We propose to add text
 >>to X.501 in clause 8.5 and in 8.8.1, where we will point out that
 >>rationalizations to stored values for the purposes of matching do not
 >>effect the stored value. We will also add text to clause 6.1 of x.520
 >>stating that the rationalizations describe in the matching rules are
 >>ephemeral, for the purpose of the match only, and will not affect the
 >>stored value.
 >>
 >>Regards
 >>
 >>David
 >>
 >
 >
 >
 >
 >
 >





From owner-ietf-ldapbis@OpenLDAP.org  Mon Oct 27 00:19: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 AAA12699
	for <ldapbis-archive@lists.ietf.org>; Mon, 27 Oct 2003 00:19:17 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9R5HIHW068127;
	Mon, 27 Oct 2003 05:17:27 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9R5FtKD068114;
	Mon, 27 Oct 2003 05:15:55 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 27 Oct 2003 05:15:55 +0000
Received: from prv-mail20.provo.novell.com (prv-mail20.provo.novell.com [137.65.81.122])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9R5FpHS068083;
	Mon, 27 Oct 2003 05:15:51 GMT
	(envelope-from jimse@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Sun, 26 Oct 2003 22:15:31 -0700
Message-Id: <sf9c4783.045@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.2 Beta
Date: Sun, 26 Oct 2003 22:15:01 -0700
From: "Jim Sermersheim" <jimse@novell.com>
To: <ietf-ldapbis@OpenLDAP.org>, <Kurt@OpenLDAP.org>
Subject: Re: REVISED protocol review notes [LONG]
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__PartA7F909C5.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>

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.

--=__PartA7F909C5.0__=
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

>>> Kurt Zeilenga <Kurt@OpenLDAP.org> 10/7/03 3:48:43 PM >>>
>Insert here <end of 4.4.1> a statement as to what a specification of a
Notice
>of Disconnect consists of.

Are you saying that we should mention that other specifications may
also define different "Notice of Disconnect" operations, and then
provide guidelines for those specifications? I'm not sure what the
benefit is.
 
Jim

--=__PartA7F909C5.0__=
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 5.50.4933.1800" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Microsoft Sans Serif">
<DIV>&gt;&gt;&gt; Kurt Zeilenga &lt;Kurt@OpenLDAP.org&gt; 10/7/03 3:48:43 PM &gt;&gt;&gt;<BR>&gt;Insert here &lt;end of 4.4.1&gt; a statement as to what a specification of a Notice<BR>&gt;of Disconnect consists of.<BR></DIV>
<DIV>Are you saying that we should mention that other specifications may also define different "Notice of Disconnect" operations, and then provide guidelines for those specifications? I'm not sure what the benefit is.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Jim</DIV></BODY></HTML>
--=__PartA7F909C5.0__=--


From owner-ietf-ldapbis@OpenLDAP.org  Mon Oct 27 00:42: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 AAA13345
	for <ldapbis-archive@lists.ietf.org>; Mon, 27 Oct 2003 00:42:30 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9R5fIHW068617;
	Mon, 27 Oct 2003 05:41:32 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9R5cXNi068570;
	Mon, 27 Oct 2003 05:38:33 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 27 Oct 2003 05:38:33 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9R5cWHS068560
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 27 Oct 2003 05:38:32 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from gypsy.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.9/8.12.9) with ESMTP id h9R5cVlg059298;
	Mon, 27 Oct 2003 05:38:31 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.0.22.0.20031026213013.02b064b0@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
Date: Sun, 26 Oct 2003 21:37:49 -0800
To: "Jim Sermersheim" <jimse@novell.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: REVISED protocol review notes [LONG]
Cc: <ietf-ldapbis@OpenLDAP.org>
In-Reply-To: <sf9c4783.045@prv-mail20.provo.novell.com>
References: <sf9c4783.045@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 09:15 PM 10/26/2003, Jim Sermersheim wrote:
>>>> Kurt Zeilenga <Kurt@OpenLDAP.org> 10/7/03 3:48:43 PM >>>
>>Insert here <end of 4.4.1> a statement as to what a specification of a Notice
>>of Disconnect consists of.
>Are you saying that we should mention that other specifications may also define different "Notice of Disconnect" operations, and then provide guidelines for those specifications? I'm not sure what the benefit is.

Sorry, I intended to suggest that guidelines for "Unsolicited
Notifications" (in general) should be added (in 4.4).  The
guidelines should be similar to those for Extended Operations
and Controls.

Kurt 



From owner-ietf-ldapbis@OpenLDAP.org  Mon Oct 27 00:48: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 AAA13535
	for <ldapbis-archive@lists.ietf.org>; Mon, 27 Oct 2003 00:48:12 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9R5lIHW068754;
	Mon, 27 Oct 2003 05:47:20 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9R5g6QL068672;
	Mon, 27 Oct 2003 05:42:06 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 27 Oct 2003 05:42:06 +0000
Received: from ausyms50.ca.com (mail30.ca.com [155.35.248.106])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9R5g3HS068628
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 27 Oct 2003 05:42:03 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.6713);
	 Mon, 27 Oct 2003 16:41:42 +1100
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: New text for X.501
Date: Mon, 27 Oct 2003 16:41:42 +1100
Message-ID: <1395B4B334FCC143B36AF788E68B6381A9A7CF@ausyms21.ca.com>
Thread-Topic: New text for X.501
Thread-Index: AcOcRYDYEuAmw5ZFRgGs1KLFy2+syQABcjuw
From: "Ramsay, Ron" <Ron.Ramsay@ca.com>
To: "Steven Legg" <steven.legg@adacel.com.au>
Cc: "David Chadwick" <d.w.chadwick@salford.ac.uk>,
        "LDAP BIS" <ietf-ldapbis@OpenLDAP.org>
X-OriginalArrivalTime: 27 Oct 2003 05:41:42.0417 (UTC) FILETIME=[00131010:01C39C4D]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by boole.openldap.org id h9R5g4HS068662
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

Steven,

OK, there is a problem with OIDs. But I don't see any problem with spaces. Suppose that an X.500 directory has the required property, that data is always returned in the form it was received. Suppose also that the LDAP interface desires to have the same property. It receives a string value of syntax directoryString. It does not remove any spaces, or change case, but creates the X.500 DirectoryString type using the choice UTF8String. This value is stored without change, according to our assumption. When this value is requested, the X.500 directory supplies this stored value. The LDAP front-end can now extract the string and send it. The client will then receive it exactly as it was provided.

I don't understand the part about LDIF. You don't intend to dump an X.500 directory to an LDIF file, do you? There would seem little ambiguity if an LDAP directory is dumped to LDIF.

But, yes, object identifies are a problem.

Ron

-----Original Message-----
From: Steven Legg [mailto:steven.legg@adacel.com.au]
Sent: Monday, 27 October 2003 15:48
To: Ramsay, Ron
Cc: David Chadwick; LDAP BIS
Subject: Re: New text for X.501



Ron,

Ramsay, Ron wrote:
 > It would be interesting to see which syntaxes can't be preserved.

Of the syntaxes defined in the syntaxes draft, values of the ones
prefixed with an asterisk are not guaranteed to be preserved by a
transformation from the LDAP-specific encoding to the BER encoding and
back to the LDAP-specific encoding. This is because they allow a variable
number of spaces, or contain case-insensitive labels, or allow short names
for OIDs.

* AttributeTypeDescription
* Bit String
* Boolean
   Country String
* DeliveryMethod
   Directory String
* DIT Content Rule Description
* DIT Structure Rule Description
* DN
* Enhanced Guide
* Facsimile Telephone Number
   Fax
   GeneralizedTime
* Guide
   IA5String
   Integer
   JPEG
* LDAP Syntax Description
* Matching Rule Description
* Matching Rule Use Description
* Name and Optional UID
* Name Form Description
   Numeric String
* Object Class Description
   Octet String
* OID
   Other Mailbox
* Postal Address
   Printable String
   Substring Assertion
   Telephone Number
* Teletex Terminal Identifier
   Telex Number
   UTC Time


Values of none of the LDAP syntaxes above can be guaranteed to be
preserved under a transformation from BER to LDAP-specific encoding
and back to BER (e.g. an LDIF dump and reload) since, in the very least,
the original BER encoding has a choice of the short form or the long
form for encoding lengths, and knowledge of this choice is lost in the
transformation from BER to LDAP-specific encoding.

 >
 > Assuming that the access protocol is LDAP, directoryString can be mapped
 > because X.500 has the UTF8String option. Any LDAP type whose encoding is
 > ASN.1 can also be mapped. Integers can be mapped.
 >
 > PrintableString synataxes seem not to be mappable, except that the
 > characters should be able to be transcribed as they should already be
 > printable.
 >
 > G3Fax, audio, jpeg all go across as octet string.
 >
 > Actually, I would think the only problem would be with data provided from
 > non-LDAP sources.
 >
 > I think it is clear that X.500 can make the requirement.

It is clear to me that it cannot.

Regards,
Steven

 >
 > LDAP can make the requirement but servers may not be able to conform to it,
 > but, from the LDAP perspective, there is nothing to prevent them conforming.
 >
 > Ron
 >
 > -----Original Message-----
 > From: owner-ietf-ldapbis@OpenLDAP.org
 > [mailto:owner-ietf-ldapbis@OpenLDAP.org]On Behalf Of Steven Legg
 > Sent: Monday, 27 October 2003 10:52
 > To: David Chadwick
 > Cc: LDAP BIS; OSIdirectory@az05.bull.com
 > Subject: Re: New text for X.501
 >
 >
 >
 > David,
 >
 > David Chadwick wrote:
 >
 >>Dear LDAPers
 >>
 >>At the recent Geneva meeting of the X.500 group, Defect Report 303 was
 >>discussed. This concerns the fact that a user cannot be guaranteed that
 >>the information presented to LDAP/X.500 server in an update operation is
 >>subsequently returned unaltered in a Search operation. Due to this, in
 >>the PKIX work we are adding text to the IDs specifically to say that for
 >>X.509 certificates and CRLs the data must not be altered by the LDAP
 >>server. The X.500 group is going to go one step further than this and
 >>state that no attributes must be altered by the server and must be
 >>returned exactly as presented,
 >
 >
 > I think this change is ill-advised, as the requirement cannot be enforced
 > in a mixed LDAP/X.500 distributed environment. An attribute value that is
 > entered in an LDAP-specific encoding has to be transformed into BER to be
 > carried in DSP or DISP. There is no guarantee that the exact LDAP-specific
 > encoding of the original attribute value will be reconstructed by the
 > receiving DSA. Preservation of the exact encoding of PKI attributes can
 > only be made to work in the general case because the LDAP encoding and the
 > X.500 encoding is the same - BER. For most syntaxes this is not the case.
 >
 > The XED specifications introduce a third way of encoding directory data
(DXER),
 > which only increases the difficulty of preserving the original encoding.
 >
 > If the X.500 standards add this requirement then, as a practical necessity,
 > I will have to disregard it. However, I will continue to preserve the abstract
 > value of attribute values to the extent that it is possible to do so.
 >
 > Regards,
 > Steven
 >
 >
 >>although a server may store a
 >>canonicalised form for efficient matching if it so desires.
 >>
 >>The defect report can only address the 1997 and 2001 versions of X.500,
 >>since the 1993 version that LDAP is based in is no longer supported by
 >>ITU-T/ISO.
 >>
 >>Here is the gist of the proposed text to fix the defect report.
 >>
 >>Stored attribute values must be held as supplied. We propose to add text
 >>to X.501 in clause 8.5 and in 8.8.1, where we will point out that
 >>rationalizations to stored values for the purposes of matching do not
 >>effect the stored value. We will also add text to clause 6.1 of x.520
 >>stating that the rationalizations describe in the matching rules are
 >>ephemeral, for the purpose of the match only, and will not affect the
 >>stored value.
 >>
 >>Regards
 >>
 >>David
 >>
 >
 >
 >
 >
 >
 >







From owner-ietf-ldapbis@OpenLDAP.org  Mon Oct 27 01:37: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 BAA15088
	for <ldapbis-archive@lists.ietf.org>; Mon, 27 Oct 2003 01:37:20 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9R6ZIHW070973;
	Mon, 27 Oct 2003 06:35:37 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9R6Xj00070960;
	Mon, 27 Oct 2003 06:33:45 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 27 Oct 2003 06:33:45 +0000
Received: from adacel.com (gunsmoke.adacel.com.au [210.11.130.7])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9R6XgHS070950
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 27 Oct 2003 06:33:43 GMT
	(envelope-from steven.legg@adacel.com.au)
Received: from nexus.adacel.com (Not Verified[10.32.240.1]) by adacel.com with NetIQ MailMarshal (v5.5.3.16)
	id <B00018d485>; Mon, 27 Oct 2003 17:27:08 +1100
Received: (qmail 17024 invoked from network); 27 Oct 2003 06:33:21 -0000
Received: from unknown (HELO adacel.com.au) (10.32.24.165)
  by nexus.adacel.com with SMTP; 27 Oct 2003 06:33:21 -0000
Message-ID: <3F9CBC2F.7000004@adacel.com.au>
Date: Mon, 27 Oct 2003 17:33:19 +1100
From: Steven Legg <steven.legg@adacel.com.au>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3.1) Gecko/20030425
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Ramsay, Ron" <Ron.Ramsay@ca.com>
CC: David Chadwick <d.w.chadwick@salford.ac.uk>,
        LDAP BIS <ietf-ldapbis@OpenLDAP.org>
Subject: Re: New text for X.501
References: <1395B4B334FCC143B36AF788E68B6381A9A7CF@ausyms21.ca.com>
In-Reply-To: <1395B4B334FCC143B36AF788E68B6381A9A7CF@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,

Ramsay, Ron wrote:
> Steven,
> 
> OK, there is a problem with OIDs. But I don't see any problem with spaces.

I was talking about, for example, Attribute Type Description where there
are optional spaces separating the fields. The number and position of the
spaces gets lost in a transformation from LDAP-specific encoding to BER
encoding.

 > Suppose that an X.500 directory has the required property, that data is
 > always returned in the form it was received. Suppose also that the LDAP
 > interface desires to have the same property. It receives a string value
 > of syntax directoryString. It does not remove any spaces, or change case,
 > but creates the X.500 DirectoryString type using the choice UTF8String.
 > This value is stored without change, according to our assumption. When
 > this value is requested, the X.500 directory supplies this stored value.
 > The LDAP front-end can now extract the string and send it. The client will
 > then receive it exactly as it was provided.
> 
> I don't understand the part about LDIF. You don't intend to dump an X.500
 > directory to an LDIF file, do you?

I chose the LDIF case as a familiar example where the BER -> LDAP-specific -> BER
transformation would occur. The X.500 - LDAP alignment work may have created
other situations where a BER encoding gets turned into an LDAP-specific
encoding which is fetched back as BER. I haven't seen the specification
so I don't know for sure, but if such situations exist then requiring the
preservation of the original encoding is even more dubious.

 > There would seem little ambiguity if an
 > LDAP directory is dumped to LDIF.
> 
> But, yes, object identifies are a problem.

As are optional space separators and case-insensitive labels.
The majority of LDAP syntaxes thwart value preservation in
a mixed environment in one way or another.

Regards,
Steven

> 
> Ron
> 
> -----Original Message-----
> From: Steven Legg [mailto:steven.legg@adacel.com.au]
> Sent: Monday, 27 October 2003 15:48
> To: Ramsay, Ron
> Cc: David Chadwick; LDAP BIS
> Subject: Re: New text for X.501
> 
> 
> 
> Ron,
> 
> Ramsay, Ron wrote:
>  > It would be interesting to see which syntaxes can't be preserved.
> 
> Of the syntaxes defined in the syntaxes draft, values of the ones
> prefixed with an asterisk are not guaranteed to be preserved by a
> transformation from the LDAP-specific encoding to the BER encoding and
> back to the LDAP-specific encoding. This is because they allow a variable
> number of spaces, or contain case-insensitive labels, or allow short names
> for OIDs.
> 
> * AttributeTypeDescription
> * Bit String
> * Boolean
>    Country String
> * DeliveryMethod
>    Directory String
> * DIT Content Rule Description
> * DIT Structure Rule Description
> * DN
> * Enhanced Guide
> * Facsimile Telephone Number
>    Fax
>    GeneralizedTime
> * Guide
>    IA5String
>    Integer
>    JPEG
> * LDAP Syntax Description
> * Matching Rule Description
> * Matching Rule Use Description
> * Name and Optional UID
> * Name Form Description
>    Numeric String
> * Object Class Description
>    Octet String
> * OID
>    Other Mailbox
> * Postal Address
>    Printable String
>    Substring Assertion
>    Telephone Number
> * Teletex Terminal Identifier
>    Telex Number
>    UTC Time
> 
> 
> Values of none of the LDAP syntaxes above can be guaranteed to be
> preserved under a transformation from BER to LDAP-specific encoding
> and back to BER (e.g. an LDIF dump and reload) since, in the very least,
> the original BER encoding has a choice of the short form or the long
> form for encoding lengths, and knowledge of this choice is lost in the
> transformation from BER to LDAP-specific encoding.
> 
>  >
>  > Assuming that the access protocol is LDAP, directoryString can be mapped
>  > because X.500 has the UTF8String option. Any LDAP type whose encoding is
>  > ASN.1 can also be mapped. Integers can be mapped.
>  >
>  > PrintableString synataxes seem not to be mappable, except that the
>  > characters should be able to be transcribed as they should already be
>  > printable.
>  >
>  > G3Fax, audio, jpeg all go across as octet string.
>  >
>  > Actually, I would think the only problem would be with data provided from
>  > non-LDAP sources.
>  >
>  > I think it is clear that X.500 can make the requirement.
> 
> It is clear to me that it cannot.
> 
> Regards,
> Steven
> 
>  >
>  > LDAP can make the requirement but servers may not be able to conform to it,
>  > but, from the LDAP perspective, there is nothing to prevent them conforming.
>  >
>  > Ron
>  >
>  > -----Original Message-----
>  > From: owner-ietf-ldapbis@OpenLDAP.org
>  > [mailto:owner-ietf-ldapbis@OpenLDAP.org]On Behalf Of Steven Legg
>  > Sent: Monday, 27 October 2003 10:52
>  > To: David Chadwick
>  > Cc: LDAP BIS; OSIdirectory@az05.bull.com
>  > Subject: Re: New text for X.501
>  >
>  >
>  >
>  > David,
>  >
>  > David Chadwick wrote:
>  >
>  >>Dear LDAPers
>  >>
>  >>At the recent Geneva meeting of the X.500 group, Defect Report 303 was
>  >>discussed. This concerns the fact that a user cannot be guaranteed that
>  >>the information presented to LDAP/X.500 server in an update operation is
>  >>subsequently returned unaltered in a Search operation. Due to this, in
>  >>the PKIX work we are adding text to the IDs specifically to say that for
>  >>X.509 certificates and CRLs the data must not be altered by the LDAP
>  >>server. The X.500 group is going to go one step further than this and
>  >>state that no attributes must be altered by the server and must be
>  >>returned exactly as presented,
>  >
>  >
>  > I think this change is ill-advised, as the requirement cannot be enforced
>  > in a mixed LDAP/X.500 distributed environment. An attribute value that is
>  > entered in an LDAP-specific encoding has to be transformed into BER to be
>  > carried in DSP or DISP. There is no guarantee that the exact LDAP-specific
>  > encoding of the original attribute value will be reconstructed by the
>  > receiving DSA. Preservation of the exact encoding of PKI attributes can
>  > only be made to work in the general case because the LDAP encoding and the
>  > X.500 encoding is the same - BER. For most syntaxes this is not the case.
>  >
>  > The XED specifications introduce a third way of encoding directory data
> (DXER),
>  > which only increases the difficulty of preserving the original encoding.
>  >
>  > If the X.500 standards add this requirement then, as a practical necessity,
>  > I will have to disregard it. However, I will continue to preserve the abstract
>  > value of attribute values to the extent that it is possible to do so.
>  >
>  > Regards,
>  > Steven
>  >
>  >
>  >>although a server may store a
>  >>canonicalised form for efficient matching if it so desires.
>  >>
>  >>The defect report can only address the 1997 and 2001 versions of X.500,
>  >>since the 1993 version that LDAP is based in is no longer supported by
>  >>ITU-T/ISO.
>  >>
>  >>Here is the gist of the proposed text to fix the defect report.
>  >>
>  >>Stored attribute values must be held as supplied. We propose to add text
>  >>to X.501 in clause 8.5 and in 8.8.1, where we will point out that
>  >>rationalizations to stored values for the purposes of matching do not
>  >>effect the stored value. We will also add text to clause 6.1 of x.520
>  >>stating that the rationalizations describe in the matching rules are
>  >>ephemeral, for the purpose of the match only, and will not affect the
>  >>stored value.
>  >>
>  >>Regards
>  >>
>  >>David
>  >>
>  >
>  >
>  >
>  >
>  >
>  >
> 
> 
> 
> 
> 
> 



From owner-ietf-ldapbis@OpenLDAP.org  Mon Oct 27 01:42: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 BAA15239
	for <ldapbis-archive@lists.ietf.org>; Mon, 27 Oct 2003 01:42:52 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9R6fIHW071162;
	Mon, 27 Oct 2003 06:41:20 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9R6cZxe071083;
	Mon, 27 Oct 2003 06:38:35 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 27 Oct 2003 06:38:35 +0000
Received: from ausyms50.ca.com (mail30.ca.com [155.35.248.106])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9R6cTHS071072
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 27 Oct 2003 06:38:30 GMT
	(envelope-from Ron.Ramsay@ca.com)
Received: from ausyms21.ca.com ([155.35.201.5]) by ausyms50.ca.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Mon, 27 Oct 2003 17:38:29 +1100
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: New text for X.501
Date: Mon, 27 Oct 2003 17:38:28 +1100
Message-ID: <1395B4B334FCC143B36AF788E68B6381A9A8C7@ausyms21.ca.com>
Thread-Topic: New text for X.501
Thread-Index: AcOcVDzAXpzRFVwSTH+CSd98ZLObXwAAKHWw
From: "Ramsay, Ron" <Ron.Ramsay@ca.com>
To: "Steven Legg" <steven.legg@adacel.com.au>
Cc: "David Chadwick" <d.w.chadwick@salford.ac.uk>,
        "LDAP BIS" <ietf-ldapbis@OpenLDAP.org>
X-OriginalArrivalTime: 27 Oct 2003 06:38:29.0317 (UTC) FILETIME=[EEBEBF50:01C39C54]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by boole.openldap.org id h9R6cUHS071073
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

Yes, you're right.

-----Original Message-----
From: Steven Legg [mailto:steven.legg@adacel.com.au]
Sent: Monday, 27 October 2003 17:33
To: Ramsay, Ron
Cc: David Chadwick; LDAP BIS
Subject: Re: New text for X.501



Ron,

Ramsay, Ron wrote:
> Steven,
> 
> OK, there is a problem with OIDs. But I don't see any problem with spaces.

I was talking about, for example, Attribute Type Description where there
are optional spaces separating the fields. The number and position of the
spaces gets lost in a transformation from LDAP-specific encoding to BER
encoding.

 > Suppose that an X.500 directory has the required property, that data is
 > always returned in the form it was received. Suppose also that the LDAP
 > interface desires to have the same property. It receives a string value
 > of syntax directoryString. It does not remove any spaces, or change case,
 > but creates the X.500 DirectoryString type using the choice UTF8String.
 > This value is stored without change, according to our assumption. When
 > this value is requested, the X.500 directory supplies this stored value.
 > The LDAP front-end can now extract the string and send it. The client will
 > then receive it exactly as it was provided.
> 
> I don't understand the part about LDIF. You don't intend to dump an X.500
 > directory to an LDIF file, do you?

I chose the LDIF case as a familiar example where the BER -> LDAP-specific -> BER
transformation would occur. The X.500 - LDAP alignment work may have created
other situations where a BER encoding gets turned into an LDAP-specific
encoding which is fetched back as BER. I haven't seen the specification
so I don't know for sure, but if such situations exist then requiring the
preservation of the original encoding is even more dubious.

 > There would seem little ambiguity if an
 > LDAP directory is dumped to LDIF.
> 
> But, yes, object identifies are a problem.

As are optional space separators and case-insensitive labels.
The majority of LDAP syntaxes thwart value preservation in
a mixed environment in one way or another.

Regards,
Steven

> 
> Ron
> 
> -----Original Message-----
> From: Steven Legg [mailto:steven.legg@adacel.com.au]
> Sent: Monday, 27 October 2003 15:48
> To: Ramsay, Ron
> Cc: David Chadwick; LDAP BIS
> Subject: Re: New text for X.501
> 
> 
> 
> Ron,
> 
> Ramsay, Ron wrote:
>  > It would be interesting to see which syntaxes can't be preserved.
> 
> Of the syntaxes defined in the syntaxes draft, values of the ones
> prefixed with an asterisk are not guaranteed to be preserved by a
> transformation from the LDAP-specific encoding to the BER encoding and
> back to the LDAP-specific encoding. This is because they allow a variable
> number of spaces, or contain case-insensitive labels, or allow short names
> for OIDs.
> 
> * AttributeTypeDescription
> * Bit String
> * Boolean
>    Country String
> * DeliveryMethod
>    Directory String
> * DIT Content Rule Description
> * DIT Structure Rule Description
> * DN
> * Enhanced Guide
> * Facsimile Telephone Number
>    Fax
>    GeneralizedTime
> * Guide
>    IA5String
>    Integer
>    JPEG
> * LDAP Syntax Description
> * Matching Rule Description
> * Matching Rule Use Description
> * Name and Optional UID
> * Name Form Description
>    Numeric String
> * Object Class Description
>    Octet String
> * OID
>    Other Mailbox
> * Postal Address
>    Printable String
>    Substring Assertion
>    Telephone Number
> * Teletex Terminal Identifier
>    Telex Number
>    UTC Time
> 
> 
> Values of none of the LDAP syntaxes above can be guaranteed to be
> preserved under a transformation from BER to LDAP-specific encoding
> and back to BER (e.g. an LDIF dump and reload) since, in the very least,
> the original BER encoding has a choice of the short form or the long
> form for encoding lengths, and knowledge of this choice is lost in the
> transformation from BER to LDAP-specific encoding.
> 
>  >
>  > Assuming that the access protocol is LDAP, directoryString can be mapped
>  > because X.500 has the UTF8String option. Any LDAP type whose encoding is
>  > ASN.1 can also be mapped. Integers can be mapped.
>  >
>  > PrintableString synataxes seem not to be mappable, except that the
>  > characters should be able to be transcribed as they should already be
>  > printable.
>  >
>  > G3Fax, audio, jpeg all go across as octet string.
>  >
>  > Actually, I would think the only problem would be with data provided from
>  > non-LDAP sources.
>  >
>  > I think it is clear that X.500 can make the requirement.
> 
> It is clear to me that it cannot.
> 
> Regards,
> Steven
> 
>  >
>  > LDAP can make the requirement but servers may not be able to conform to it,
>  > but, from the LDAP perspective, there is nothing to prevent them conforming.
>  >
>  > Ron
>  >
>  > -----Original Message-----
>  > From: owner-ietf-ldapbis@OpenLDAP.org
>  > [mailto:owner-ietf-ldapbis@OpenLDAP.org]On Behalf Of Steven Legg
>  > Sent: Monday, 27 October 2003 10:52
>  > To: David Chadwick
>  > Cc: LDAP BIS; OSIdirectory@az05.bull.com
>  > Subject: Re: New text for X.501
>  >
>  >
>  >
>  > David,
>  >
>  > David Chadwick wrote:
>  >
>  >>Dear LDAPers
>  >>
>  >>At the recent Geneva meeting of the X.500 group, Defect Report 303 was
>  >>discussed. This concerns the fact that a user cannot be guaranteed that
>  >>the information presented to LDAP/X.500 server in an update operation is
>  >>subsequently returned unaltered in a Search operation. Due to this, in
>  >>the PKIX work we are adding text to the IDs specifically to say that for
>  >>X.509 certificates and CRLs the data must not be altered by the LDAP
>  >>server. The X.500 group is going to go one step further than this and
>  >>state that no attributes must be altered by the server and must be
>  >>returned exactly as presented,
>  >
>  >
>  > I think this change is ill-advised, as the requirement cannot be enforced
>  > in a mixed LDAP/X.500 distributed environment. An attribute value that is
>  > entered in an LDAP-specific encoding has to be transformed into BER to be
>  > carried in DSP or DISP. There is no guarantee that the exact LDAP-specific
>  > encoding of the original attribute value will be reconstructed by the
>  > receiving DSA. Preservation of the exact encoding of PKI attributes can
>  > only be made to work in the general case because the LDAP encoding and the
>  > X.500 encoding is the same - BER. For most syntaxes this is not the case.
>  >
>  > The XED specifications introduce a third way of encoding directory data
> (DXER),
>  > which only increases the difficulty of preserving the original encoding.
>  >
>  > If the X.500 standards add this requirement then, as a practical necessity,
>  > I will have to disregard it. However, I will continue to preserve the abstract
>  > value of attribute values to the extent that it is possible to do so.
>  >
>  > Regards,
>  > Steven
>  >
>  >
>  >>although a server may store a
>  >>canonicalised form for efficient matching if it so desires.
>  >>
>  >>The defect report can only address the 1997 and 2001 versions of X.500,
>  >>since the 1993 version that LDAP is based in is no longer supported by
>  >>ITU-T/ISO.
>  >>
>  >>Here is the gist of the proposed text to fix the defect report.
>  >>
>  >>Stored attribute values must be held as supplied. We propose to add text
>  >>to X.501 in clause 8.5 and in 8.8.1, where we will point out that
>  >>rationalizations to stored values for the purposes of matching do not
>  >>effect the stored value. We will also add text to clause 6.1 of x.520
>  >>stating that the rationalizations describe in the matching rules are
>  >>ephemeral, for the purpose of the match only, and will not affect the
>  >>stored value.
>  >>
>  >>Regards
>  >>
>  >>David
>  >>
>  >
>  >
>  >
>  >
>  >
>  >
> 
> 
> 
> 
> 
> 





From owner-ietf-ldapbis@OpenLDAP.org  Mon Oct 27 02:28:06 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA29151
	for <ldapbis-archive@lists.ietf.org>; Mon, 27 Oct 2003 02:28:05 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9R7NIHc072532;
	Mon, 27 Oct 2003 07:26:58 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9R7JDAg072274;
	Mon, 27 Oct 2003 07:19:13 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 27 Oct 2003 07:19:13 +0000
Received: from prv-mail20.provo.novell.com (prv-mail20.provo.novell.com [137.65.81.122])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9R7J0HS072242
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 27 Oct 2003 07:19:00 GMT
	(envelope-from jimse@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Mon, 27 Oct 2003 00:18:40 -0700
Message-Id: <sf9c6460.021@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.2 Beta
Date: Mon, 27 Oct 2003 00:18:03 -0700
From: "Jim Sermersheim" <jimse@novell.com>
To: <ietf-ldapbis@OpenLDAP.org>
Subject: Re: Submission of draft-ietf-ldapbis-protocol-18.txt
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__PartB6E818BB.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>

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.

--=__PartB6E818BB.0__=
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

All,
 
I was able to submit a new version of the protocol doc with many of the
recently suggested edits, but I was unable to complete the work.
 
What I'll do is continue to edit and identify contentious issues which
we can address in Minneapolis. I should have something waiting for
November 10th, when the I-D Editor opens the floodgates back up.
 
Jim

--=__PartB6E818BB.0__=
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 5.50.4933.1800" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Microsoft Sans Serif">
<DIV>All,</DIV>
<DIV>&nbsp;</DIV>
<DIV>I was able to submit a new version of the protocol doc with many of the recently suggested edits, but I was unable to complete the work.</DIV>
<DIV>&nbsp;</DIV>
<DIV>What I'll do is continue to edit and identify contentious issues which we can address in Minneapolis. I should have something waiting for November 10th, when the I-D Editor opens the floodgates back up.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Jim</DIV></BODY></HTML>
--=__PartB6E818BB.0__=--


From owner-ietf-ldapbis@OpenLDAP.org  Mon Oct 27 02:29: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 CAA29172
	for <ldapbis-archive@lists.ietf.org>; Mon, 27 Oct 2003 02:29:10 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9R7HJHi072164;
	Mon, 27 Oct 2003 07:26:59 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9R7FmtL072128;
	Mon, 27 Oct 2003 07:15:48 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 27 Oct 2003 07:15:48 +0000
Received: from nb2.stroeder.com (du-006-009.access.de.clara.net [212.82.229.9])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9R7FiHS072114
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 27 Oct 2003 07:15:46 GMT
	(envelope-from michael@stroeder.com)
Received: from localhost (localhost [127.0.0.1])
	by nb2.stroeder.com (Postfix) with ESMTP id 28C127F013
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 27 Oct 2003 07:14:55 +0100 (CET)
Received: from stroeder.com (localhost [127.0.0.1])
	by nb2.stroeder.com (Postfix) with ESMTP id C67D12C3AE
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 27 Oct 2003 07:14:51 +0100 (CET)
Message-ID: <3F9CB7DB.1050107@stroeder.com>
Date: Mon, 27 Oct 2003 07:14:51 +0100
From: =?ISO-8859-1?Q?Michael_Str=F6der?= <michael@stroeder.com>
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)
X-Accept-Language: de-de, de, en-us, en
MIME-Version: 1.0
To: LDAP BIS <ietf-ldapbis@OpenLDAP.org>
Subject: LDAP based on X.500 '93 (was: New text for X.501)
References: <3F9BBB94.BBE78984@salford.ac.uk>
In-Reply-To: <3F9BBB94.BBE78984@salford.ac.uk>
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

David Chadwick wrote:
> 
> The defect report can only address the 1997 and 2001 versions of X.500,
> since the 1993 version that LDAP is based in is no longer supported by
> ITU-T/ISO.

Is it possible to update the X.500 version LDAP is based on
within LDAPbis work items?

Ciao, Michael.



From owner-ietf-ldapbis@OpenLDAP.org  Mon Oct 27 03:13: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 DAA00437
	for <ldapbis-archive@lists.ietf.org>; Mon, 27 Oct 2003 03:13:37 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9R8BJHW075070;
	Mon, 27 Oct 2003 08:11:43 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9R8B9VO075062;
	Mon, 27 Oct 2003 08:11:09 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 27 Oct 2003 08:11:09 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9R8B8HS075052
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 27 Oct 2003 08:11:08 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from gypsy.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.9/8.12.9) with ESMTP id h9R8B8lg060662;
	Mon, 27 Oct 2003 08:11:08 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.0.22.0.20031026234626.02b1c240@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
Date: Mon, 27 Oct 2003 00:10:25 -0800
To: Michael =?iso-8859-1?Q?Str=F6der?= <michael@stroeder.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: LDAP based on X.500 '93 (was: New text for X.501)
Cc: LDAP BIS <ietf-ldapbis@OpenLDAP.org>
In-Reply-To: <3F9CB7DB.1050107@stroeder.com>
References: <3F9BBB94.BBE78984@salford.ac.uk>
 <3F9CB7DB.1050107@stroeder.com>
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 h9R8B8HS075053
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 10:14 PM 10/26/2003, Michael Ströder wrote:
>David Chadwick wrote:
>>The defect report can only address the 1997 and 2001 versions of X.500,
>>since the 1993 version that LDAP is based in is no longer supported by
>>ITU-T/ISO.
>
>Is it possible to update the X.500 version LDAP is based on
>within LDAPbis work items?

As previously discussed, since LDAP was not designed for newer
versions of X.500, no, the references cannot be simply updated.
We'd have to detail which of changes to X.500 were applicable
and which were not.  This would get quite messy.

Kurt 




From owner-ietf-ldapbis@OpenLDAP.org  Mon Oct 27 06:50: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 GAA07967
	for <ldapbis-archive@lists.ietf.org>; Mon, 27 Oct 2003 06:50:18 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9RBlKHW083198;
	Mon, 27 Oct 2003 11:47:54 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9RBigGI083146;
	Mon, 27 Oct 2003 11:44:42 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 27 Oct 2003 11:44:42 +0000
Received: from new_bruno (bruno.gric.com [216.231.202.145])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9RBicHS083064;
	Mon, 27 Oct 2003 11:44:38 GMT
	(envelope-from d.w.chadwick@salford.ac.uk)
Received: from salford.ac.uk (1Cust117.tnt22.dca5.da.uu.net [65.235.0.117])
	by new_bruno (8.12.7/8.12.7) with ESMTP id h9RBhB71013633;
	Mon, 27 Oct 2003 03:43:12 -0800 (PST)
Message-ID: <3F9D0447.2956D490@salford.ac.uk>
Date: Mon, 27 Oct 2003 11:40:55 +0000
From: David Chadwick <d.w.chadwick@salford.ac.uk>
Organization: University of Salford
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
CC: Michael =?iso-8859-1?Q?Str=F6der?= <michael@stroeder.com>,
        LDAP BIS 
	<ietf-ldapbis@OpenLDAP.org>
Subject: Re: LDAP based on X.500 '93 (was: New text for X.501)
References: <3F9BBB94.BBE78984@salford.ac.uk> <3F9CB7DB.1050107@stroeder.com> <6.0.0.22.0.20031026234626.02b1c240@127.0.0.1>
Content-Type: multipart/mixed;
 boundary="------------16103270732297ADF1C8F086"
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 multi-part message in MIME format.
--------------16103270732297ADF1C8F086
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Kurt

Michaels message is ambiguous. I thought he was asking if the LDAP group
could update the X.500(93) standard, not update its references to point
to the 97 standard.

regards

david

"Kurt D. Zeilenga" wrote:
> 
> At 10:14 PM 10/26/2003, Michael Ströder wrote:
> >David Chadwick wrote:
> >>The defect report can only address the 1997 and 2001 versions of X.500,
> >>since the 1993 version that LDAP is based in is no longer supported by
> >>ITU-T/ISO.
> >
> >Is it possible to update the X.500 version LDAP is based on
> >within LDAPbis work items?
> 
> As previously discussed, since LDAP was not designed for newer
> versions of X.500, no, the references cannot be simply updated.
> We'd have to detail which of changes to X.500 were applicable
> and which were not.  This would get quite messy.
> 
> Kurt

-- 

*****************************************************************

David W. Chadwick, BSc PhD
Professor of Information Systems Security
IS Institute, University of Salford, Salford M5 4WT
Tel: +44 161 295 5351  Fax +44 01484 532930
Mobile: +44 77 96 44 7184
Email: D.W.Chadwick@salford.ac.uk
Home Page:  http://www.salford.ac.uk/its024/chadwick.htm
Research Web site: http://sec.isi.salford.ac.uk
Entrust key validation string: MLJ9-DU5T-HV8J
PGP Key ID is 0xBC238DE5

*****************************************************************
--------------16103270732297ADF1C8F086
Content-Type: text/x-vcard; charset=us-ascii;
 name="d.w.chadwick.vcf"
Content-Description: Card for David Chadwick
Content-Disposition: attachment;
 filename="d.w.chadwick.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Chadwick;David
tel;cell:+44 77 96 44 7184
tel;fax:+44 1484 532930
tel;home:+44 1484 352238
tel;work:+44 161 295 5351
x-mozilla-html:FALSE
url:http://sec.isi.salford.ac.uk
org:University of Salford;IS Institute
version:2.1
email;internet:d.w.chadwick@salford.ac.uk
title:Professor of Information Security
adr;quoted-printable:;;The Crescent=0D=0A;Salford;Greater Manchester;M5 4WT;England
note;quoted-printable:Research Projects: http://sec.isi.salford.ac.uk=0D=0A=0D=0AEntrust key validation string: CJ94-LKWD-BSXB ...........=0D=0A=0D=0APGP Key ID is 0xBC238DE5
x-mozilla-cpt:;-18752
fn:David Chadwick
end:vcard

--------------16103270732297ADF1C8F086--




From owner-ietf-ldapbis@OpenLDAP.org  Mon Oct 27 06:55: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 GAA08138
	for <ldapbis-archive@lists.ietf.org>; Mon, 27 Oct 2003 06:55:06 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9RBrKHW083473;
	Mon, 27 Oct 2003 11:53:22 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9RBmCoQ083253;
	Mon, 27 Oct 2003 11:48:12 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 27 Oct 2003 11:48:12 +0000
Received: from new_bruno (bruno.gric.com [216.231.202.145])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9RBmAHS083208
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 27 Oct 2003 11:48:10 GMT
	(envelope-from d.w.chadwick@salford.ac.uk)
Received: from salford.ac.uk (1Cust117.tnt22.dca5.da.uu.net [65.235.0.117])
	by new_bruno (8.12.7/8.12.7) with ESMTP id h9RBgs71013630;
	Mon, 27 Oct 2003 03:42:57 -0800 (PST)
Message-ID: <3F9D0384.E2C0790C@salford.ac.uk>
Date: Mon, 27 Oct 2003 11:37:40 +0000
From: David Chadwick <d.w.chadwick@salford.ac.uk>
Organization: University of Salford
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Steven Legg <steven.legg@adacel.com.au>
CC: LDAP BIS <ietf-ldapbis@OpenLDAP.org>, OSIdirectory@az05.bull.com
Subject: Re: New text for X.501
References: <3F9BBB94.BBE78984@salford.ac.uk> <3F9C5E08.1040104@adacel.com.au>
Content-Type: multipart/mixed;
 boundary="------------0C934A70CFABE110C0C39BEC"
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 multi-part message in MIME format.
--------------0C934A70CFABE110C0C39BEC
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Steven

We are talking about the abstract values and not the encoded values.
X.500 does not mandate any particular ASN.1 encoding rules except in the
case of the X.509 attributes which must be DER (and even this was later
realised to be a bug, but it is too late to change it now). DSAs/LDAP
servers will typically store local representations of abstract values
and what these are is not stated, its implementation dependent (although
in some cases such as the X.509 attributes, they will have to store the
encoded values so as to preserve the signatures). Whether the transfer
syntax is BER, LDAP or XER should be irrelevant to the abstract value.
Does this help to clarify what the intention is

regards

David


Steven Legg wrote:
> 
> David,
> 
> David Chadwick wrote:
> > Dear LDAPers
> >
> > At the recent Geneva meeting of the X.500 group, Defect Report 303 was
> > discussed. This concerns the fact that a user cannot be guaranteed that
> > the information presented to LDAP/X.500 server in an update operation is
> > subsequently returned unaltered in a Search operation. Due to this, in
> > the PKIX work we are adding text to the IDs specifically to say that for
> > X.509 certificates and CRLs the data must not be altered by the LDAP
> > server. The X.500 group is going to go one step further than this and
> > state that no attributes must be altered by the server and must be
> > returned exactly as presented,
> 
> I think this change is ill-advised, as the requirement cannot be enforced
> in a mixed LDAP/X.500 distributed environment. An attribute value that is
> entered in an LDAP-specific encoding has to be transformed into BER to be
> carried in DSP or DISP. There is no guarantee that the exact LDAP-specific
> encoding of the original attribute value will be reconstructed by the
> receiving DSA. Preservation of the exact encoding of PKI attributes can
> only be made to work in the general case because the LDAP encoding and the
> X.500 encoding is the same - BER. For most syntaxes this is not the case.
> 
> The XED specifications introduce a third way of encoding directory data (DXER),
> which only increases the difficulty of preserving the original encoding.
> 
> If the X.500 standards add this requirement then, as a practical necessity,
> I will have to disregard it. However, I will continue to preserve the abstract
> value of attribute values to the extent that it is possible to do so.
> 
> Regards,
> Steven
> 
> > although a server may store a
> > canonicalised form for efficient matching if it so desires.
> >
> > The defect report can only address the 1997 and 2001 versions of X.500,
> > since the 1993 version that LDAP is based in is no longer supported by
> > ITU-T/ISO.
> >
> > Here is the gist of the proposed text to fix the defect report.
> >
> > Stored attribute values must be held as supplied. We propose to add text
> > to X.501 in clause 8.5 and in 8.8.1, where we will point out that
> > rationalizations to stored values for the purposes of matching do not
> > effect the stored value. We will also add text to clause 6.1 of x.520
> > stating that the rationalizations describe in the matching rules are
> > ephemeral, for the purpose of the match only, and will not affect the
> > stored value.
> >
> > Regards
> >
> > David
> >

-- 

*****************************************************************

David W. Chadwick, BSc PhD
Professor of Information Systems Security
IS Institute, University of Salford, Salford M5 4WT
Tel: +44 161 295 5351  Fax +44 01484 532930
Mobile: +44 77 96 44 7184
Email: D.W.Chadwick@salford.ac.uk
Home Page:  http://www.salford.ac.uk/its024/chadwick.htm
Research Web site: http://sec.isi.salford.ac.uk
Entrust key validation string: MLJ9-DU5T-HV8J
PGP Key ID is 0xBC238DE5

*****************************************************************
--------------0C934A70CFABE110C0C39BEC
Content-Type: text/x-vcard; charset=us-ascii;
 name="d.w.chadwick.vcf"
Content-Description: Card for David Chadwick
Content-Disposition: attachment;
 filename="d.w.chadwick.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Chadwick;David
tel;cell:+44 77 96 44 7184
tel;fax:+44 1484 532930
tel;home:+44 1484 352238
tel;work:+44 161 295 5351
x-mozilla-html:FALSE
url:http://sec.isi.salford.ac.uk
org:University of Salford;IS Institute
version:2.1
email;internet:d.w.chadwick@salford.ac.uk
title:Professor of Information Security
adr;quoted-printable:;;The Crescent=0D=0A;Salford;Greater Manchester;M5 4WT;England
note;quoted-printable:Research Projects: http://sec.isi.salford.ac.uk=0D=0A=0D=0AEntrust key validation string: CJ94-LKWD-BSXB ...........=0D=0A=0D=0APGP Key ID is 0xBC238DE5
x-mozilla-cpt:;-18752
fn:David Chadwick
end:vcard

--------------0C934A70CFABE110C0C39BEC--





From owner-ietf-ldapbis@OpenLDAP.org  Mon Oct 27 07:46: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 HAA10308
	for <ldapbis-archive@lists.ietf.org>; Mon, 27 Oct 2003 07:46:16 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9RCfLHW086998;
	Mon, 27 Oct 2003 12:44:08 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9RCebNE086949;
	Mon, 27 Oct 2003 12:40:37 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 27 Oct 2003 12:40:37 +0000
Received: from nb2.stroeder.com (du-041-110.access.de.clara.net [213.221.78.110] (may be forged))
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9RCeWHS086914;
	Mon, 27 Oct 2003 12:40:33 GMT
	(envelope-from michael@stroeder.com)
Received: from localhost (localhost [127.0.0.1])
	by nb2.stroeder.com (Postfix) with ESMTP
	id 1C9317F058; Mon, 27 Oct 2003 13:34:54 +0100 (CET)
Received: from stroeder.com (localhost [127.0.0.1])
	by nb2.stroeder.com (Postfix) with ESMTP
	id 10C527F043; Mon, 27 Oct 2003 13:34:53 +0100 (CET)
Message-ID: <3F9D10EC.5000601@stroeder.com>
Date: Mon, 27 Oct 2003 13:34:52 +0100
From: =?ISO-8859-1?Q?Michael_Str=F6der?= <michael@stroeder.com>
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)
X-Accept-Language: de-de, de, en-us, en
MIME-Version: 1.0
To: David Chadwick <d.w.chadwick@salford.ac.uk>
Cc: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>,
        LDAP BIS <ietf-ldapbis@OpenLDAP.org>
Subject: Re: LDAP based on X.500 '93
References: <3F9BBB94.BBE78984@salford.ac.uk> <3F9CB7DB.1050107@stroeder.com> <6.0.0.22.0.20031026234626.02b1c240@127.0.0.1> <3F9D0447.2956D490@salford.ac.uk>
In-Reply-To: <3F9D0447.2956D490@salford.ac.uk>
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 h9RCeXHS086920
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

David Chadwick wrote:
> 
> Michaels message is ambiguous. I thought he was asking if the LDAP group
> could update the X.500(93) standard, not update its references to point
> to the 97 standard.

Sorry for confusion.

Kurt got it right. I was *not* asking for updating X.500(93).

Ciao, Michael.


> "Kurt D. Zeilenga" wrote:
> 
>>At 10:14 PM 10/26/2003, Michael Ströder wrote:
>>
>>>David Chadwick wrote:
>>>
>>>>The defect report can only address the 1997 and 2001 versions of X.500,
>>>>since the 1993 version that LDAP is based in is no longer supported by
>>>>ITU-T/ISO.
>>>
>>>Is it possible to update the X.500 version LDAP is based on
>>>within LDAPbis work items?
>>
>>As previously discussed, since LDAP was not designed for newer
>>versions of X.500, no, the references cannot be simply updated.
>>We'd have to detail which of changes to X.500 were applicable
>>and which were not.  This would get quite messy.
>>
>>Kurt




From owner-ietf-ldapbis@OpenLDAP.org  Mon Oct 27 15:08: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 PAA04921
	for <ldapbis-archive@lists.ietf.org>; Mon, 27 Oct 2003 15:08:29 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9RK6eHS013116;
	Mon, 27 Oct 2003 20:06:44 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9RJshc1012461;
	Mon, 27 Oct 2003 19:54:43 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 27 Oct 2003 19:54:43 +0000
Received: from pat.uio.no (IDENT:7411@pat.uio.no [129.240.130.16])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9RJseHS012445
	for <ietf-ldapbis@openldap.org>; Mon, 27 Oct 2003 19:54:40 GMT
	(envelope-from hbf@bombur.uio.no)
Received: from mail-mx2.uio.no ([129.240.10.30])
	by pat.uio.no with esmtp (Exim 4.20)
	id 1AEDRk-0000T6-R2
	for ietf-ldapbis@openldap.org; Mon, 27 Oct 2003 20:54:36 +0100
Received: from bombur.uio.no ([129.240.186.42])
	by mail-mx2.uio.no with esmtp (Exim 4.14)
	id 1AEDRi-0006yE-Ug; Mon, 27 Oct 2003 20:54:34 +0100
Received: from hbf by bombur.uio.no with local (Exim 2.12 #7)
	id 1AEDRi-0002Ak-00; Mon, 27 Oct 2003 20:54:34 +0100
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Message-Id: <HBF.200310276iv@bombur.uio.no>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: ietf-ldapbis@OpenLDAP.org
Subject: Re: authmeth-07 issues
In-Reply-To: <HBF.20031014pk3@bombur.uio.no>
References: <HBF.20031014pk3@bombur.uio.no>
X-Mailer: VM 6.37 under Emacs 19.34.1
Date: Mon, 27 Oct 2003 20:54:34 +0100
X-MailScanner-Information: This message has been scanned for viruses/spam. Contact postmaster@uio.no if you have questions about this scanning.
X-UiO-MailScanner: No virus found
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

I wrote:

> State the effect of a failed SASL bind or a non-SASL bind on an
> existing SASL security layer.

Never mind, there is no need.  In the SASL list, Alexey Melnikov (the
[SASL] author) said that the layer can only be cancelled/replaced after
a subsequent authentication completes successfully.  So the LDAP bind is
done while the old layer is in effect.

However, that means that after a _failed_ LDAP bind, the connection will
be left anonymous (because [Authmeth] and [Protocol] say so), but with
the old SASL layer still in effect.  That's ugly, but I don't see that
anything can be done about it.

-- 
Hallvard


From owner-ietf-ldapbis@OpenLDAP.org  Mon Oct 27 16:20: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 QAA11129
	for <ldapbis-archive@lists.ietf.org>; Mon, 27 Oct 2003 16:20:37 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9RLHNHW018752;
	Mon, 27 Oct 2003 21:18:54 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9RLGw9m018736;
	Mon, 27 Oct 2003 21:16:58 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 27 Oct 2003 21:16:58 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9RLGrHS018705
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 27 Oct 2003 21:16:57 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from gypsy.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.9/8.12.9) with ESMTP id h9RLGrlg068054;
	Mon, 27 Oct 2003 21:16:53 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.0.22.0.20031027130022.02bc7e68@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
Date: Mon, 27 Oct 2003 13:16:09 -0800
To: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: authmeth-07 issues
Cc: ietf-ldapbis@OpenLDAP.org
In-Reply-To: <HBF.200310276iv@bombur.uio.no>
References: <HBF.20031014pk3@bombur.uio.no>
 <HBF.200310276iv@bombur.uio.no>
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:54 AM 10/27/2003, Hallvard B Furuseth wrote:
>I wrote:
>
>> State the effect of a failed SASL bind or a non-SASL bind on an
>> existing SASL security layer.
>
>Never mind, there is no need.  In the SASL list, Alexey Melnikov (the
>[SASL] author) said that the layer can only be cancelled/replaced after
>a subsequent authentication completes successfully.  So the LDAP bind is
>done while the old layer is in effect.
>
>However, that means that after a _failed_ LDAP bind, the connection will
>be left anonymous (because [Authmeth] and [Protocol] say so), but with
>the old SASL layer still in effect.  That's ugly, but I don't see that
>anything can be done about it.

Actually, I think the current SASL I-D says old layers are not
to be left installed after a subsequent authentication.   This
is counter to what RFC 2829 said (it left them installed).

I note that layer removal likely should be consistent across
all forms of LDAP authentication.  If old SASL layers are removed
upon subsequent SASL authentication, I think they also should
be upon subsequent non-SASL authentication.

Anyways, as there is a strong argument that LDAP must use SASL as
specified in its revision, I advise those who have concerns as to
whether the layers should be left installed or not voice those
concerns on the SASL WG mailing list.

Kurt 



From owner-ietf-ldapbis@OpenLDAP.org  Mon Oct 27 22:08: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 WAA05247
	for <ldapbis-archive@lists.ietf.org>; Mon, 27 Oct 2003 22:08:17 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9S35QHW034556;
	Tue, 28 Oct 2003 03:05:47 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9S331lQ034539;
	Tue, 28 Oct 2003 03:03:01 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 28 Oct 2003 03:03:01 +0000
Received: from adacel.com (gunsmoke.adacel.com.au [210.11.130.7])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9S32tHS034509
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 28 Oct 2003 03:02:59 GMT
	(envelope-from steven.legg@adacel.com.au)
Received: from nexus.adacel.com (Not Verified[10.32.240.1]) by adacel.com with NetIQ MailMarshal (v5.5.3.16)
	id <B00018e7ce>; Tue, 28 Oct 2003 13:56:15 +1100
Received: (qmail 19073 invoked from network); 28 Oct 2003 03:02:34 -0000
Received: from unknown (HELO adacel.com.au) (10.32.24.165)
  by nexus.adacel.com with SMTP; 28 Oct 2003 03:02:34 -0000
Message-ID: <3F9DDC49.6040403@adacel.com.au>
Date: Tue, 28 Oct 2003 14:02:33 +1100
From: Steven Legg <steven.legg@adacel.com.au>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3.1) Gecko/20030425
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: David Chadwick <d.w.chadwick@salford.ac.uk>
CC: LDAP BIS <ietf-ldapbis@OpenLDAP.org>
Subject: Re: New text for X.501
References: <3F9BBB94.BBE78984@salford.ac.uk> <3F9C5E08.1040104@adacel.com.au> <3F9D0384.E2C0790C@salford.ac.uk>
In-Reply-To: <3F9D0384.E2C0790C@salford.ac.uk>
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


David,

David Chadwick wrote:
> Steven
> 
> We are talking about the abstract values and not the encoded values.
> X.500 does not mandate any particular ASN.1 encoding rules except in the
> case of the X.509 attributes which must be DER (and even this was later
> realised to be a bug, but it is too late to change it now). DSAs/LDAP
> servers will typically store local representations of abstract values
> and what these are is not stated, its implementation dependent (although
> in some cases such as the X.509 attributes, they will have to store the
> encoded values so as to preserve the signatures). Whether the transfer
> syntax is BER, LDAP or XER should be irrelevant to the abstract value.
> Does this help to clarify what the intention is

Yes, though you should be aware that there are cases where even the
abstract value can't be preserved. The chosen alternative in a DirectoryString
isn't guaranteed to be preserved in a transformation from BER to LDAP-specific
to BER. This affects the Directory String syntax, as well as various syntaxes
that have embedded DirectoryString components. The chosen alternative is
inconsequential for directory purposes, but changing it is, by strict definition,
a change to the abstract value.

Regards,
Steven

> 
> regards
> 
> David
> 
> 
> Steven Legg wrote:
> 
>>David,
>>
>>David Chadwick wrote:
>>
>>>Dear LDAPers
>>>
>>>At the recent Geneva meeting of the X.500 group, Defect Report 303 was
>>>discussed. This concerns the fact that a user cannot be guaranteed that
>>>the information presented to LDAP/X.500 server in an update operation is
>>>subsequently returned unaltered in a Search operation. Due to this, in
>>>the PKIX work we are adding text to the IDs specifically to say that for
>>>X.509 certificates and CRLs the data must not be altered by the LDAP
>>>server. The X.500 group is going to go one step further than this and
>>>state that no attributes must be altered by the server and must be
>>>returned exactly as presented,
>>
>>I think this change is ill-advised, as the requirement cannot be enforced
>>in a mixed LDAP/X.500 distributed environment. An attribute value that is
>>entered in an LDAP-specific encoding has to be transformed into BER to be
>>carried in DSP or DISP. There is no guarantee that the exact LDAP-specific
>>encoding of the original attribute value will be reconstructed by the
>>receiving DSA. Preservation of the exact encoding of PKI attributes can
>>only be made to work in the general case because the LDAP encoding and the
>>X.500 encoding is the same - BER. For most syntaxes this is not the case.
>>
>>The XED specifications introduce a third way of encoding directory data (DXER),
>>which only increases the difficulty of preserving the original encoding.
>>
>>If the X.500 standards add this requirement then, as a practical necessity,
>>I will have to disregard it. However, I will continue to preserve the abstract
>>value of attribute values to the extent that it is possible to do so.
>>
>>Regards,
>>Steven
>>
>>
>>>although a server may store a
>>>canonicalised form for efficient matching if it so desires.
>>>
>>>The defect report can only address the 1997 and 2001 versions of X.500,
>>>since the 1993 version that LDAP is based in is no longer supported by
>>>ITU-T/ISO.
>>>
>>>Here is the gist of the proposed text to fix the defect report.
>>>
>>>Stored attribute values must be held as supplied. We propose to add text
>>>to X.501 in clause 8.5 and in 8.8.1, where we will point out that
>>>rationalizations to stored values for the purposes of matching do not
>>>effect the stored value. We will also add text to clause 6.1 of x.520
>>>stating that the rationalizations describe in the matching rules are
>>>ephemeral, for the purpose of the match only, and will not affect the
>>>stored value.
>>>
>>>Regards
>>>
>>>David
>>>
> 
> 



From owner-ietf-ldapbis@OpenLDAP.org  Mon Oct 27 22:24:34 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 WAA05539
	for <ldapbis-archive@lists.ietf.org>; Mon, 27 Oct 2003 22:24:33 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9S3NQHW034927;
	Tue, 28 Oct 2003 03:23:30 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9S3KoHf034880;
	Tue, 28 Oct 2003 03:20:50 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 28 Oct 2003 03:20:50 +0000
Received: from ausyms50.ca.com (mail30.ca.com [155.35.248.106])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9S3KdHS034866
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 28 Oct 2003 03: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.6713);
	 Tue, 28 Oct 2003 14:20:17 +1100
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: New text for X.501
Date: Tue, 28 Oct 2003 14:20:17 +1100
Message-ID: <1395B4B334FCC143B36AF788E68B6381ABC19C@ausyms21.ca.com>
Thread-Topic: New text for X.501
Thread-Index: AcOdAGpN+9Wh8+XiRwiiyd/Tb6amjAAAI4rg
From: "Ramsay, Ron" <Ron.Ramsay@ca.com>
To: "Steven Legg" <steven.legg@adacel.com.au>,
        "David Chadwick" <d.w.chadwick@salford.ac.uk>
Cc: "LDAP BIS" <ietf-ldapbis@OpenLDAP.org>
X-OriginalArrivalTime: 28 Oct 2003 03:20:17.0713 (UTC) FILETIME=[6935BA10:01C39D02]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by boole.openldap.org id h9S3KmHS034871
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

Steven,

I must protest that DirectoryString is one of the cases where the abstract value can be preserved. In order to break it you have had to go X.500 -> LDAP -> X.500 and I don't see how this can be justified. LDAP is an access protocol, so we should never have the case to which you referred.

On another matter, does PostalAddress allow spaces either side of the '$'? If it doesn't, then this also is a syntax for which values can be preserved.

Also, relating to the syntaxes that cannot be preserved, your previous example seemed to concern configuration items like schema. While it may be appropriate to configure LDAP directories using LDAP, I don't know that this should be the case with X.500 directories. However, this still leaves items like SearchGuide.

Ron

-----Original Message-----
From: owner-ietf-ldapbis@OpenLDAP.org
[mailto:owner-ietf-ldapbis@OpenLDAP.org]On Behalf Of Steven Legg
Sent: Tuesday, 28 October 2003 14:03
To: David Chadwick
Cc: LDAP BIS
Subject: Re: New text for X.501



David,

David Chadwick wrote:
> Steven
> 
> We are talking about the abstract values and not the encoded values.
> X.500 does not mandate any particular ASN.1 encoding rules except in the
> case of the X.509 attributes which must be DER (and even this was later
> realised to be a bug, but it is too late to change it now). DSAs/LDAP
> servers will typically store local representations of abstract values
> and what these are is not stated, its implementation dependent (although
> in some cases such as the X.509 attributes, they will have to store the
> encoded values so as to preserve the signatures). Whether the transfer
> syntax is BER, LDAP or XER should be irrelevant to the abstract value.
> Does this help to clarify what the intention is

Yes, though you should be aware that there are cases where even the
abstract value can't be preserved. The chosen alternative in a DirectoryString
isn't guaranteed to be preserved in a transformation from BER to LDAP-specific
to BER. This affects the Directory String syntax, as well as various syntaxes
that have embedded DirectoryString components. The chosen alternative is
inconsequential for directory purposes, but changing it is, by strict definition,
a change to the abstract value.

Regards,
Steven

> 
> regards
> 
> David
> 
> 
> Steven Legg wrote:
> 
>>David,
>>
>>David Chadwick wrote:
>>
>>>Dear LDAPers
>>>
>>>At the recent Geneva meeting of the X.500 group, Defect Report 303 was
>>>discussed. This concerns the fact that a user cannot be guaranteed that
>>>the information presented to LDAP/X.500 server in an update operation is
>>>subsequently returned unaltered in a Search operation. Due to this, in
>>>the PKIX work we are adding text to the IDs specifically to say that for
>>>X.509 certificates and CRLs the data must not be altered by the LDAP
>>>server. The X.500 group is going to go one step further than this and
>>>state that no attributes must be altered by the server and must be
>>>returned exactly as presented,
>>
>>I think this change is ill-advised, as the requirement cannot be enforced
>>in a mixed LDAP/X.500 distributed environment. An attribute value that is
>>entered in an LDAP-specific encoding has to be transformed into BER to be
>>carried in DSP or DISP. There is no guarantee that the exact LDAP-specific
>>encoding of the original attribute value will be reconstructed by the
>>receiving DSA. Preservation of the exact encoding of PKI attributes can
>>only be made to work in the general case because the LDAP encoding and the
>>X.500 encoding is the same - BER. For most syntaxes this is not the case.
>>
>>The XED specifications introduce a third way of encoding directory data (DXER),
>>which only increases the difficulty of preserving the original encoding.
>>
>>If the X.500 standards add this requirement then, as a practical necessity,
>>I will have to disregard it. However, I will continue to preserve the abstract
>>value of attribute values to the extent that it is possible to do so.
>>
>>Regards,
>>Steven
>>
>>
>>>although a server may store a
>>>canonicalised form for efficient matching if it so desires.
>>>
>>>The defect report can only address the 1997 and 2001 versions of X.500,
>>>since the 1993 version that LDAP is based in is no longer supported by
>>>ITU-T/ISO.
>>>
>>>Here is the gist of the proposed text to fix the defect report.
>>>
>>>Stored attribute values must be held as supplied. We propose to add text
>>>to X.501 in clause 8.5 and in 8.8.1, where we will point out that
>>>rationalizations to stored values for the purposes of matching do not
>>>effect the stored value. We will also add text to clause 6.1 of x.520
>>>stating that the rationalizations describe in the matching rules are
>>>ephemeral, for the purpose of the match only, and will not affect the
>>>stored value.
>>>
>>>Regards
>>>
>>>David
>>>
> 
> 





From owner-ietf-ldapbis@OpenLDAP.org  Mon Oct 27 23:44: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 XAA09104
	for <ldapbis-archive@lists.ietf.org>; Mon, 27 Oct 2003 23:44:40 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9S4fQHW036776;
	Tue, 28 Oct 2003 04:42:03 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9S4ZeXa036594;
	Tue, 28 Oct 2003 04:35:40 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 28 Oct 2003 04:35:40 +0000
Received: from adacel.com (gunsmoke.adacel.com.au [210.11.130.7])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9S4ZcHS036577
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 28 Oct 2003 04:35:38 GMT
	(envelope-from steven.legg@adacel.com.au)
Received: from nexus.adacel.com (Not Verified[10.32.240.1]) by adacel.com with NetIQ MailMarshal (v5.5.3.16)
	id <B00018e94e>; Tue, 28 Oct 2003 15:21:00 +1100
Received: (qmail 27801 invoked from network); 28 Oct 2003 04:27:19 -0000
Received: from unknown (HELO adacel.com.au) (10.32.24.165)
  by nexus.adacel.com with SMTP; 28 Oct 2003 04:27:19 -0000
Message-ID: <3F9DF026.6060809@adacel.com.au>
Date: Tue, 28 Oct 2003 15:27:18 +1100
From: Steven Legg <steven.legg@adacel.com.au>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3.1) Gecko/20030425
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Ramsay, Ron" <Ron.Ramsay@ca.com>
CC: LDAP BIS <ietf-ldapbis@OpenLDAP.org>
Subject: Re: New text for X.501
References: <1395B4B334FCC143B36AF788E68B6381ABC19C@ausyms21.ca.com>
In-Reply-To: <1395B4B334FCC143B36AF788E68B6381ABC19C@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,

Ramsay, Ron wrote:
> I must protest that DirectoryString is one of the cases where the
 > abstract value can be preserved. In order to break it you have had
 > to go X.500 -> LDAP -> X.500 and I don't see how this can be justified.
 > LDAP is an access protocol, so we should never have the case to which
 > you referred.

This transformation occurs if an X.500 DSA uses LDIF to dump and reload
data. It also occurs if an X.500 DSA uses LDAP to chain to a subordinate
(LDAP-only) DSA.

> On another matter, does PostalAddress allow spaces either side of the
 > '$'? If it doesn't, then this also is a syntax for which values can be
 > preserved.

The problem with PostalAddress is the need to escape any '$' character
in the abstract value. The escape sequence is case insensitive and could
be case inverted by LDAP -> BER -> LDAP.

> Also, relating to the syntaxes that cannot be preserved, your previous
 > example seemed to concern configuration items like schema. While it may
 > be appropriate to configure LDAP directories using LDAP, I don't know
 > that this should be the case with X.500 directories.

It's a necessity. There are LDAP applications that configure the schema
they need by using LDAP to modify the subschema subentry. Our directory
server let's them do it.

Regards,
Steven

 > However, this still leaves items like SearchGuide.
> 
> Ron
> 
> -----Original Message-----
> From: owner-ietf-ldapbis@OpenLDAP.org
> [mailto:owner-ietf-ldapbis@OpenLDAP.org]On Behalf Of Steven Legg
> Sent: Tuesday, 28 October 2003 14:03
> To: David Chadwick
> Cc: LDAP BIS
> Subject: Re: New text for X.501
> 
> 
> 
> David,
> 
> David Chadwick wrote:
> 
>>Steven
>>
>>We are talking about the abstract values and not the encoded values.
>>X.500 does not mandate any particular ASN.1 encoding rules except in the
>>case of the X.509 attributes which must be DER (and even this was later
>>realised to be a bug, but it is too late to change it now). DSAs/LDAP
>>servers will typically store local representations of abstract values
>>and what these are is not stated, its implementation dependent (although
>>in some cases such as the X.509 attributes, they will have to store the
>>encoded values so as to preserve the signatures). Whether the transfer
>>syntax is BER, LDAP or XER should be irrelevant to the abstract value.
>>Does this help to clarify what the intention is
> 
> 
> Yes, though you should be aware that there are cases where even the
> abstract value can't be preserved. The chosen alternative in a DirectoryString
> isn't guaranteed to be preserved in a transformation from BER to LDAP-specific
> to BER. This affects the Directory String syntax, as well as various syntaxes
> that have embedded DirectoryString components. The chosen alternative is
> inconsequential for directory purposes, but changing it is, by strict definition,
> a change to the abstract value.
> 
> Regards,
> Steven
> 
> 
>>regards
>>
>>David
>>
>>
>>Steven Legg wrote:
>>
>>
>>>David,
>>>
>>>David Chadwick wrote:
>>>
>>>
>>>>Dear LDAPers
>>>>
>>>>At the recent Geneva meeting of the X.500 group, Defect Report 303 was
>>>>discussed. This concerns the fact that a user cannot be guaranteed that
>>>>the information presented to LDAP/X.500 server in an update operation is
>>>>subsequently returned unaltered in a Search operation. Due to this, in
>>>>the PKIX work we are adding text to the IDs specifically to say that for
>>>>X.509 certificates and CRLs the data must not be altered by the LDAP
>>>>server. The X.500 group is going to go one step further than this and
>>>>state that no attributes must be altered by the server and must be
>>>>returned exactly as presented,
>>>
>>>I think this change is ill-advised, as the requirement cannot be enforced
>>>in a mixed LDAP/X.500 distributed environment. An attribute value that is
>>>entered in an LDAP-specific encoding has to be transformed into BER to be
>>>carried in DSP or DISP. There is no guarantee that the exact LDAP-specific
>>>encoding of the original attribute value will be reconstructed by the
>>>receiving DSA. Preservation of the exact encoding of PKI attributes can
>>>only be made to work in the general case because the LDAP encoding and the
>>>X.500 encoding is the same - BER. For most syntaxes this is not the case.
>>>
>>>The XED specifications introduce a third way of encoding directory data (DXER),
>>>which only increases the difficulty of preserving the original encoding.
>>>
>>>If the X.500 standards add this requirement then, as a practical necessity,
>>>I will have to disregard it. However, I will continue to preserve the abstract
>>>value of attribute values to the extent that it is possible to do so.
>>>
>>>Regards,
>>>Steven
>>>
>>>
>>>
>>>>although a server may store a
>>>>canonicalised form for efficient matching if it so desires.
>>>>
>>>>The defect report can only address the 1997 and 2001 versions of X.500,
>>>>since the 1993 version that LDAP is based in is no longer supported by
>>>>ITU-T/ISO.
>>>>
>>>>Here is the gist of the proposed text to fix the defect report.
>>>>
>>>>Stored attribute values must be held as supplied. We propose to add text
>>>>to X.501 in clause 8.5 and in 8.8.1, where we will point out that
>>>>rationalizations to stored values for the purposes of matching do not
>>>>effect the stored value. We will also add text to clause 6.1 of x.520
>>>>stating that the rationalizations describe in the matching rules are
>>>>ephemeral, for the purpose of the match only, and will not affect the
>>>>stored value.
>>>>
>>>>Regards
>>>>
>>>>David
>>>>
>>
>>
> 
> 
> 
> 
> 



From owner-ietf-ldapbis@OpenLDAP.org  Tue Oct 28 00:21: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 AAA11699
	for <ldapbis-archive@lists.ietf.org>; Tue, 28 Oct 2003 00:21:07 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9S5HQHW038604;
	Tue, 28 Oct 2003 05:17:40 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9S5CRne038496;
	Tue, 28 Oct 2003 05:12:27 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 28 Oct 2003 05:12:27 +0000
Received: from ausyms50.ca.com (mail30.ca.com [155.35.248.106])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9S5COHS038486
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 28 Oct 2003 05:12: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.6713);
	 Tue, 28 Oct 2003 16:12:13 +1100
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: New text for X.501
Date: Tue, 28 Oct 2003 16:12:12 +1100
Message-ID: <1395B4B334FCC143B36AF788E68B6381ABC386@ausyms21.ca.com>
Thread-Topic: New text for X.501
Thread-Index: AcOdDeUYMcBVsZlSSpaPIgfepwF7ZgAAuotw
From: "Ramsay, Ron" <Ron.Ramsay@ca.com>
To: "Steven Legg" <steven.legg@adacel.com.au>
Cc: "LDAP BIS" <ietf-ldapbis@OpenLDAP.org>
X-OriginalArrivalTime: 28 Oct 2003 05:12:13.0099 (UTC) FILETIME=[0BE44FB0:01C39D12]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by boole.openldap.org id h9S5CPHS038487
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 Steven,

I must continue to object.

1) If you use LDAP to chain then we have (for a chained update) LDAP --> X.500 --> LDAP, not X.500 --> LDAP --> X.500!

2) Isn't the postal address escape just '\$'? I don't see the problem with case.

Dumping to LDIF and configuring using LDAP are not X.500-type operations and so require no comment!

Ron

-----Original Message-----
From: owner-ietf-ldapbis@OpenLDAP.org
[mailto:owner-ietf-ldapbis@OpenLDAP.org]On Behalf Of Steven Legg
Sent: Tuesday, 28 October 2003 15:27
To: Ramsay, Ron
Cc: LDAP BIS
Subject: Re: New text for X.501



Ron,

Ramsay, Ron wrote:
> I must protest that DirectoryString is one of the cases where the
 > abstract value can be preserved. In order to break it you have had
 > to go X.500 -> LDAP -> X.500 and I don't see how this can be justified.
 > LDAP is an access protocol, so we should never have the case to which
 > you referred.

This transformation occurs if an X.500 DSA uses LDIF to dump and reload
data. It also occurs if an X.500 DSA uses LDAP to chain to a subordinate
(LDAP-only) DSA.

> On another matter, does PostalAddress allow spaces either side of the
 > '$'? If it doesn't, then this also is a syntax for which values can be
 > preserved.

The problem with PostalAddress is the need to escape any '$' character
in the abstract value. The escape sequence is case insensitive and could
be case inverted by LDAP -> BER -> LDAP.

> Also, relating to the syntaxes that cannot be preserved, your previous
 > example seemed to concern configuration items like schema. While it may
 > be appropriate to configure LDAP directories using LDAP, I don't know
 > that this should be the case with X.500 directories.

It's a necessity. There are LDAP applications that configure the schema
they need by using LDAP to modify the subschema subentry. Our directory
server let's them do it.

Regards,
Steven

 > However, this still leaves items like SearchGuide.
> 
> Ron
> 
> -----Original Message-----
> From: owner-ietf-ldapbis@OpenLDAP.org
> [mailto:owner-ietf-ldapbis@OpenLDAP.org]On Behalf Of Steven Legg
> Sent: Tuesday, 28 October 2003 14:03
> To: David Chadwick
> Cc: LDAP BIS
> Subject: Re: New text for X.501
> 
> 
> 
> David,
> 
> David Chadwick wrote:
> 
>>Steven
>>
>>We are talking about the abstract values and not the encoded values.
>>X.500 does not mandate any particular ASN.1 encoding rules except in the
>>case of the X.509 attributes which must be DER (and even this was later
>>realised to be a bug, but it is too late to change it now). DSAs/LDAP
>>servers will typically store local representations of abstract values
>>and what these are is not stated, its implementation dependent (although
>>in some cases such as the X.509 attributes, they will have to store the
>>encoded values so as to preserve the signatures). Whether the transfer
>>syntax is BER, LDAP or XER should be irrelevant to the abstract value.
>>Does this help to clarify what the intention is
> 
> 
> Yes, though you should be aware that there are cases where even the
> abstract value can't be preserved. The chosen alternative in a DirectoryString
> isn't guaranteed to be preserved in a transformation from BER to LDAP-specific
> to BER. This affects the Directory String syntax, as well as various syntaxes
> that have embedded DirectoryString components. The chosen alternative is
> inconsequential for directory purposes, but changing it is, by strict definition,
> a change to the abstract value.
> 
> Regards,
> Steven
> 
> 
>>regards
>>
>>David
>>
>>
>>Steven Legg wrote:
>>
>>
>>>David,
>>>
>>>David Chadwick wrote:
>>>
>>>
>>>>Dear LDAPers
>>>>
>>>>At the recent Geneva meeting of the X.500 group, Defect Report 303 was
>>>>discussed. This concerns the fact that a user cannot be guaranteed that
>>>>the information presented to LDAP/X.500 server in an update operation is
>>>>subsequently returned unaltered in a Search operation. Due to this, in
>>>>the PKIX work we are adding text to the IDs specifically to say that for
>>>>X.509 certificates and CRLs the data must not be altered by the LDAP
>>>>server. The X.500 group is going to go one step further than this and
>>>>state that no attributes must be altered by the server and must be
>>>>returned exactly as presented,
>>>
>>>I think this change is ill-advised, as the requirement cannot be enforced
>>>in a mixed LDAP/X.500 distributed environment. An attribute value that is
>>>entered in an LDAP-specific encoding has to be transformed into BER to be
>>>carried in DSP or DISP. There is no guarantee that the exact LDAP-specific
>>>encoding of the original attribute value will be reconstructed by the
>>>receiving DSA. Preservation of the exact encoding of PKI attributes can
>>>only be made to work in the general case because the LDAP encoding and the
>>>X.500 encoding is the same - BER. For most syntaxes this is not the case.
>>>
>>>The XED specifications introduce a third way of encoding directory data (DXER),
>>>which only increases the difficulty of preserving the original encoding.
>>>
>>>If the X.500 standards add this requirement then, as a practical necessity,
>>>I will have to disregard it. However, I will continue to preserve the abstract
>>>value of attribute values to the extent that it is possible to do so.
>>>
>>>Regards,
>>>Steven
>>>
>>>
>>>
>>>>although a server may store a
>>>>canonicalised form for efficient matching if it so desires.
>>>>
>>>>The defect report can only address the 1997 and 2001 versions of X.500,
>>>>since the 1993 version that LDAP is based in is no longer supported by
>>>>ITU-T/ISO.
>>>>
>>>>Here is the gist of the proposed text to fix the defect report.
>>>>
>>>>Stored attribute values must be held as supplied. We propose to add text
>>>>to X.501 in clause 8.5 and in 8.8.1, where we will point out that
>>>>rationalizations to stored values for the purposes of matching do not
>>>>effect the stored value. We will also add text to clause 6.1 of x.520
>>>>stating that the rationalizations describe in the matching rules are
>>>>ephemeral, for the purpose of the match only, and will not affect the
>>>>stored value.
>>>>
>>>>Regards
>>>>
>>>>David
>>>>
>>
>>
> 
> 
> 
> 
> 





From owner-ietf-ldapbis@OpenLDAP.org  Tue Oct 28 00:58: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 AAA14064
	for <ldapbis-archive@lists.ietf.org>; Tue, 28 Oct 2003 00:58:34 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9S5rQHW040083;
	Tue, 28 Oct 2003 05:54:47 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9S5nib8039909;
	Tue, 28 Oct 2003 05:49:44 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 28 Oct 2003 05:49:44 +0000
Received: from adacel.com (gunsmoke.adacel.com.au [210.11.130.7])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9S5neHS039867
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 28 Oct 2003 05:49:41 GMT
	(envelope-from steven.legg@adacel.com.au)
Received: from nexus.adacel.com (Not Verified[10.32.240.1]) by adacel.com with NetIQ MailMarshal (v5.5.3.16)
	id <B00018ead4>; Tue, 28 Oct 2003 16:42:59 +1100
Received: (qmail 3696 invoked from network); 28 Oct 2003 05:49:19 -0000
Received: from unknown (HELO adacel.com.au) (10.32.24.165)
  by nexus.adacel.com with SMTP; 28 Oct 2003 05:49:19 -0000
Message-ID: <3F9E035E.8030903@adacel.com.au>
Date: Tue, 28 Oct 2003 16:49:18 +1100
From: Steven Legg <steven.legg@adacel.com.au>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3.1) Gecko/20030425
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Ramsay, Ron" <Ron.Ramsay@ca.com>
CC: LDAP BIS <ietf-ldapbis@OpenLDAP.org>
Subject: Re: New text for X.501
References: <1395B4B334FCC143B36AF788E68B6381ABC386@ausyms21.ca.com>
In-Reply-To: <1395B4B334FCC143B36AF788E68B6381ABC386@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,

Ramsay, Ron wrote:
> I must continue to object.
> 
> 1) If you use LDAP to chain then we have (for a chained update)
 > LDAP --> X.500 --> LDAP, not X.500 --> LDAP --> X.500!

A DAP modify comes in. The X.500 DSA determines the target entry is in
another DSA (LDAP-only). It chains the modify to the other DSA as an
LDAP modify (X.500 -> LDAP). The other DSA stores the new attribute
values in the LDAP-specific encoding. The user submits a DAP read of
the same target entry. The X.500 DSA chains the read as an LDAP search
to the other DSA, which responds with the attribute values in the
LDAP-specific encoding. The X.500 DSA reformats the attribute values in
BER (LDAP -> X.500) to return to the user.

Overall the values have been through X.500 -> LDAP -> X.500.

> 2) Isn't the postal address escape just '\$'? I don't see the problem with case.

The escape sequence is \24, but I got the wrong character. The backslash has
to be escaped as well. The escape sequence for *it* is either \5C or \5c.

> Dumping to LDIF and configuring using LDAP are not X.500-type operations
 > and so require no comment!

Paying customers don't care about such demarcations.

Regards,
Steven

> 
> Ron
> 
> -----Original Message-----
> From: owner-ietf-ldapbis@OpenLDAP.org
> [mailto:owner-ietf-ldapbis@OpenLDAP.org]On Behalf Of Steven Legg
> Sent: Tuesday, 28 October 2003 15:27
> To: Ramsay, Ron
> Cc: LDAP BIS
> Subject: Re: New text for X.501
> 
> 
> 
> Ron,
> 
> Ramsay, Ron wrote:
> 
>>I must protest that DirectoryString is one of the cases where the
> 
>  > abstract value can be preserved. In order to break it you have had
>  > to go X.500 -> LDAP -> X.500 and I don't see how this can be justified.
>  > LDAP is an access protocol, so we should never have the case to which
>  > you referred.
> 
> This transformation occurs if an X.500 DSA uses LDIF to dump and reload
> data. It also occurs if an X.500 DSA uses LDAP to chain to a subordinate
> (LDAP-only) DSA.
> 
> 
>>On another matter, does PostalAddress allow spaces either side of the
> 
>  > '$'? If it doesn't, then this also is a syntax for which values can be
>  > preserved.
> 
> The problem with PostalAddress is the need to escape any '$' character
> in the abstract value. The escape sequence is case insensitive and could
> be case inverted by LDAP -> BER -> LDAP.
> 
> 
>>Also, relating to the syntaxes that cannot be preserved, your previous
> 
>  > example seemed to concern configuration items like schema. While it may
>  > be appropriate to configure LDAP directories using LDAP, I don't know
>  > that this should be the case with X.500 directories.
> 
> It's a necessity. There are LDAP applications that configure the schema
> they need by using LDAP to modify the subschema subentry. Our directory
> server let's them do it.
> 
> Regards,
> Steven
> 
>  > However, this still leaves items like SearchGuide.
> 
>>Ron
>>
>>-----Original Message-----
>>From: owner-ietf-ldapbis@OpenLDAP.org
>>[mailto:owner-ietf-ldapbis@OpenLDAP.org]On Behalf Of Steven Legg
>>Sent: Tuesday, 28 October 2003 14:03
>>To: David Chadwick
>>Cc: LDAP BIS
>>Subject: Re: New text for X.501
>>
>>
>>
>>David,
>>
>>David Chadwick wrote:
>>
>>
>>>Steven
>>>
>>>We are talking about the abstract values and not the encoded values.
>>>X.500 does not mandate any particular ASN.1 encoding rules except in the
>>>case of the X.509 attributes which must be DER (and even this was later
>>>realised to be a bug, but it is too late to change it now). DSAs/LDAP
>>>servers will typically store local representations of abstract values
>>>and what these are is not stated, its implementation dependent (although
>>>in some cases such as the X.509 attributes, they will have to store the
>>>encoded values so as to preserve the signatures). Whether the transfer
>>>syntax is BER, LDAP or XER should be irrelevant to the abstract value.
>>>Does this help to clarify what the intention is
>>
>>
>>Yes, though you should be aware that there are cases where even the
>>abstract value can't be preserved. The chosen alternative in a DirectoryString
>>isn't guaranteed to be preserved in a transformation from BER to LDAP-specific
>>to BER. This affects the Directory String syntax, as well as various syntaxes
>>that have embedded DirectoryString components. The chosen alternative is
>>inconsequential for directory purposes, but changing it is, by strict definition,
>>a change to the abstract value.
>>
>>Regards,
>>Steven
>>
>>
>>
>>>regards
>>>
>>>David
>>>
>>>
>>>Steven Legg wrote:
>>>
>>>
>>>
>>>>David,
>>>>
>>>>David Chadwick wrote:
>>>>
>>>>
>>>>
>>>>>Dear LDAPers
>>>>>
>>>>>At the recent Geneva meeting of the X.500 group, Defect Report 303 was
>>>>>discussed. This concerns the fact that a user cannot be guaranteed that
>>>>>the information presented to LDAP/X.500 server in an update operation is
>>>>>subsequently returned unaltered in a Search operation. Due to this, in
>>>>>the PKIX work we are adding text to the IDs specifically to say that for
>>>>>X.509 certificates and CRLs the data must not be altered by the LDAP
>>>>>server. The X.500 group is going to go one step further than this and
>>>>>state that no attributes must be altered by the server and must be
>>>>>returned exactly as presented,
>>>>
>>>>I think this change is ill-advised, as the requirement cannot be enforced
>>>>in a mixed LDAP/X.500 distributed environment. An attribute value that is
>>>>entered in an LDAP-specific encoding has to be transformed into BER to be
>>>>carried in DSP or DISP. There is no guarantee that the exact LDAP-specific
>>>>encoding of the original attribute value will be reconstructed by the
>>>>receiving DSA. Preservation of the exact encoding of PKI attributes can
>>>>only be made to work in the general case because the LDAP encoding and the
>>>>X.500 encoding is the same - BER. For most syntaxes this is not the case.
>>>>
>>>>The XED specifications introduce a third way of encoding directory data (DXER),
>>>>which only increases the difficulty of preserving the original encoding.
>>>>
>>>>If the X.500 standards add this requirement then, as a practical necessity,
>>>>I will have to disregard it. However, I will continue to preserve the abstract
>>>>value of attribute values to the extent that it is possible to do so.
>>>>
>>>>Regards,
>>>>Steven
>>>>
>>>>
>>>>
>>>>
>>>>>although a server may store a
>>>>>canonicalised form for efficient matching if it so desires.
>>>>>
>>>>>The defect report can only address the 1997 and 2001 versions of X.500,
>>>>>since the 1993 version that LDAP is based in is no longer supported by
>>>>>ITU-T/ISO.
>>>>>
>>>>>Here is the gist of the proposed text to fix the defect report.
>>>>>
>>>>>Stored attribute values must be held as supplied. We propose to add text
>>>>>to X.501 in clause 8.5 and in 8.8.1, where we will point out that
>>>>>rationalizations to stored values for the purposes of matching do not
>>>>>effect the stored value. We will also add text to clause 6.1 of x.520
>>>>>stating that the rationalizations describe in the matching rules are
>>>>>ephemeral, for the purpose of the match only, and will not affect the
>>>>>stored value.
>>>>>
>>>>>Regards
>>>>>
>>>>>David
>>>>>
>>>
>>>
>>
>>
>>
>>
> 
> 
> 
> 



From owner-ietf-ldapbis@OpenLDAP.org  Tue Oct 28 01:31: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 BAA16171
	for <ldapbis-archive@lists.ietf.org>; Tue, 28 Oct 2003 01:31:51 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9S6TRHW041205;
	Tue, 28 Oct 2003 06:29:49 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9S6QcH3041141;
	Tue, 28 Oct 2003 06:26:38 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 28 Oct 2003 06:26:38 +0000
Received: from ausyms50.ca.com (mail30.ca.com [155.35.248.106])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9S6QXHS041121
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 28 Oct 2003 06:26:33 GMT
	(envelope-from Ron.Ramsay@ca.com)
Received: from ausyms21.ca.com ([155.35.201.5]) by ausyms50.ca.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Tue, 28 Oct 2003 17:26:11 +1100
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: New text for X.501
Date: Tue, 28 Oct 2003 17:26:11 +1100
Message-ID: <1395B4B334FCC143B36AF788E68B6381ABC4B9@ausyms21.ca.com>
Thread-Topic: New text for X.501
Thread-Index: AcOdF1Hhp8F/QF0jTSOwUcTXgxSD/QAAa4+w
From: "Ramsay, Ron" <Ron.Ramsay@ca.com>
To: "Steven Legg" <steven.legg@adacel.com.au>
Cc: "LDAP BIS" <ietf-ldapbis@OpenLDAP.org>
X-OriginalArrivalTime: 28 Oct 2003 06:26:11.0905 (UTC) FILETIME=[61A05B10:01C39D1C]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by boole.openldap.org id h9S6QYHS041132
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

OK

1) DUA --> DSA --> LDAP Server is neither fish-nor-fowl. I see how your customers may want you to do it, but I don't think it has anuthing to do with the current topic.

2) You escape the escape? Far out! How does it apply to the case in hand where clearly the escape is not escaped. That is, the value "street\$name$city" would be stored like this in LDAP and stored as 30 12 0C 0A street$name 0C 04 city in X.500.

Ron
-----Original Message-----
From: Steven Legg [mailto:steven.legg@adacel.com.au]
Sent: Tuesday, 28 October 2003 16:49
To: Ramsay, Ron
Cc: LDAP BIS
Subject: Re: New text for X.501



Ron,

Ramsay, Ron wrote:
> I must continue to object.
> 
> 1) If you use LDAP to chain then we have (for a chained update)
 > LDAP --> X.500 --> LDAP, not X.500 --> LDAP --> X.500!

A DAP modify comes in. The X.500 DSA determines the target entry is in
another DSA (LDAP-only). It chains the modify to the other DSA as an
LDAP modify (X.500 -> LDAP). The other DSA stores the new attribute
values in the LDAP-specific encoding. The user submits a DAP read of
the same target entry. The X.500 DSA chains the read as an LDAP search
to the other DSA, which responds with the attribute values in the
LDAP-specific encoding. The X.500 DSA reformats the attribute values in
BER (LDAP -> X.500) to return to the user.

Overall the values have been through X.500 -> LDAP -> X.500.

> 2) Isn't the postal address escape just '\$'? I don't see the problem with case.

The escape sequence is \24, but I got the wrong character. The backslash has
to be escaped as well. The escape sequence for *it* is either \5C or \5c.

> Dumping to LDIF and configuring using LDAP are not X.500-type operations
 > and so require no comment!

Paying customers don't care about such demarcations.

Regards,
Steven

> 
> Ron
> 
> -----Original Message-----
> From: owner-ietf-ldapbis@OpenLDAP.org
> [mailto:owner-ietf-ldapbis@OpenLDAP.org]On Behalf Of Steven Legg
> Sent: Tuesday, 28 October 2003 15:27
> To: Ramsay, Ron
> Cc: LDAP BIS
> Subject: Re: New text for X.501
> 
> 
> 
> Ron,
> 
> Ramsay, Ron wrote:
> 
>>I must protest that DirectoryString is one of the cases where the
> 
>  > abstract value can be preserved. In order to break it you have had
>  > to go X.500 -> LDAP -> X.500 and I don't see how this can be justified.
>  > LDAP is an access protocol, so we should never have the case to which
>  > you referred.
> 
> This transformation occurs if an X.500 DSA uses LDIF to dump and reload
> data. It also occurs if an X.500 DSA uses LDAP to chain to a subordinate
> (LDAP-only) DSA.
> 
> 
>>On another matter, does PostalAddress allow spaces either side of the
> 
>  > '$'? If it doesn't, then this also is a syntax for which values can be
>  > preserved.
> 
> The problem with PostalAddress is the need to escape any '$' character
> in the abstract value. The escape sequence is case insensitive and could
> be case inverted by LDAP -> BER -> LDAP.
> 
> 
>>Also, relating to the syntaxes that cannot be preserved, your previous
> 
>  > example seemed to concern configuration items like schema. While it may
>  > be appropriate to configure LDAP directories using LDAP, I don't know
>  > that this should be the case with X.500 directories.
> 
> It's a necessity. There are LDAP applications that configure the schema
> they need by using LDAP to modify the subschema subentry. Our directory
> server let's them do it.
> 
> Regards,
> Steven
> 
>  > However, this still leaves items like SearchGuide.
> 
>>Ron
>>
>>-----Original Message-----
>>From: owner-ietf-ldapbis@OpenLDAP.org
>>[mailto:owner-ietf-ldapbis@OpenLDAP.org]On Behalf Of Steven Legg
>>Sent: Tuesday, 28 October 2003 14:03
>>To: David Chadwick
>>Cc: LDAP BIS
>>Subject: Re: New text for X.501
>>
>>
>>
>>David,
>>
>>David Chadwick wrote:
>>
>>
>>>Steven
>>>
>>>We are talking about the abstract values and not the encoded values.
>>>X.500 does not mandate any particular ASN.1 encoding rules except in the
>>>case of the X.509 attributes which must be DER (and even this was later
>>>realised to be a bug, but it is too late to change it now). DSAs/LDAP
>>>servers will typically store local representations of abstract values
>>>and what these are is not stated, its implementation dependent (although
>>>in some cases such as the X.509 attributes, they will have to store the
>>>encoded values so as to preserve the signatures). Whether the transfer
>>>syntax is BER, LDAP or XER should be irrelevant to the abstract value.
>>>Does this help to clarify what the intention is
>>
>>
>>Yes, though you should be aware that there are cases where even the
>>abstract value can't be preserved. The chosen alternative in a DirectoryString
>>isn't guaranteed to be preserved in a transformation from BER to LDAP-specific
>>to BER. This affects the Directory String syntax, as well as various syntaxes
>>that have embedded DirectoryString components. The chosen alternative is
>>inconsequential for directory purposes, but changing it is, by strict definition,
>>a change to the abstract value.
>>
>>Regards,
>>Steven
>>
>>
>>
>>>regards
>>>
>>>David
>>>
>>>
>>>Steven Legg wrote:
>>>
>>>
>>>
>>>>David,
>>>>
>>>>David Chadwick wrote:
>>>>
>>>>
>>>>
>>>>>Dear LDAPers
>>>>>
>>>>>At the recent Geneva meeting of the X.500 group, Defect Report 303 was
>>>>>discussed. This concerns the fact that a user cannot be guaranteed that
>>>>>the information presented to LDAP/X.500 server in an update operation is
>>>>>subsequently returned unaltered in a Search operation. Due to this, in
>>>>>the PKIX work we are adding text to the IDs specifically to say that for
>>>>>X.509 certificates and CRLs the data must not be altered by the LDAP
>>>>>server. The X.500 group is going to go one step further than this and
>>>>>state that no attributes must be altered by the server and must be
>>>>>returned exactly as presented,
>>>>
>>>>I think this change is ill-advised, as the requirement cannot be enforced
>>>>in a mixed LDAP/X.500 distributed environment. An attribute value that is
>>>>entered in an LDAP-specific encoding has to be transformed into BER to be
>>>>carried in DSP or DISP. There is no guarantee that the exact LDAP-specific
>>>>encoding of the original attribute value will be reconstructed by the
>>>>receiving DSA. Preservation of the exact encoding of PKI attributes can
>>>>only be made to work in the general case because the LDAP encoding and the
>>>>X.500 encoding is the same - BER. For most syntaxes this is not the case.
>>>>
>>>>The XED specifications introduce a third way of encoding directory data (DXER),
>>>>which only increases the difficulty of preserving the original encoding.
>>>>
>>>>If the X.500 standards add this requirement then, as a practical necessity,
>>>>I will have to disregard it. However, I will continue to preserve the abstract
>>>>value of attribute values to the extent that it is possible to do so.
>>>>
>>>>Regards,
>>>>Steven
>>>>
>>>>
>>>>
>>>>
>>>>>although a server may store a
>>>>>canonicalised form for efficient matching if it so desires.
>>>>>
>>>>>The defect report can only address the 1997 and 2001 versions of X.500,
>>>>>since the 1993 version that LDAP is based in is no longer supported by
>>>>>ITU-T/ISO.
>>>>>
>>>>>Here is the gist of the proposed text to fix the defect report.
>>>>>
>>>>>Stored attribute values must be held as supplied. We propose to add text
>>>>>to X.501 in clause 8.5 and in 8.8.1, where we will point out that
>>>>>rationalizations to stored values for the purposes of matching do not
>>>>>effect the stored value. We will also add text to clause 6.1 of x.520
>>>>>stating that the rationalizations describe in the matching rules are
>>>>>ephemeral, for the purpose of the match only, and will not affect the
>>>>>stored value.
>>>>>
>>>>>Regards
>>>>>
>>>>>David
>>>>>
>>>
>>>
>>
>>
>>
>>
> 
> 
> 
> 





From owner-ietf-ldapbis@OpenLDAP.org  Tue Oct 28 04:26: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 EAA11568
	for <ldapbis-archive@lists.ietf.org>; Tue, 28 Oct 2003 04:26:57 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9S9NRHY047686;
	Tue, 28 Oct 2003 09:24:00 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9S9HV7J047495;
	Tue, 28 Oct 2003 09:17:31 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 28 Oct 2003 09:17:31 +0000
Received: from nb2.stroeder.com (lx.yapay.inka.de [193.197.184.188])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9S9HSHS047483
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 28 Oct 2003 09:17:29 GMT
	(envelope-from michael@stroeder.com)
Received: from localhost (localhost [127.0.0.1])
	by nb2.stroeder.com (Postfix) with ESMTP id 4BCCB7F07A
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 28 Oct 2003 08:53:03 +0100 (CET)
Received: from stroeder.com (localhost [127.0.0.1])
	by nb2.stroeder.com (Postfix) with ESMTP id E2C697F075
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 28 Oct 2003 08:52:59 +0100 (CET)
Message-ID: <3F9E205B.1060507@stroeder.com>
Date: Tue, 28 Oct 2003 08:52:59 +0100
From: =?ISO-8859-1?Q?Michael_Str=F6der?= <michael@stroeder.com>
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)
X-Accept-Language: de-de, de, en-us, en
MIME-Version: 1.0
To: ietf-ldapbis@OpenLDAP.org
Subject: Re: authmeth-07 issues
References: <HBF.20031014pk3@bombur.uio.no> <HBF.200310276iv@bombur.uio.no> <6.0.0.22.0.20031027130022.02bc7e68@127.0.0.1>
In-Reply-To: <6.0.0.22.0.20031027130022.02bc7e68@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:
> 
> I note that layer removal likely should be consistent across
> all forms of LDAP authentication.  If old SASL layers are removed
> upon subsequent SASL authentication, I think they also should
> be upon subsequent non-SASL authentication.

+1

Ciao, Michael.



From owner-ietf-ldapbis@OpenLDAP.org  Tue Oct 28 06:02: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 GAA15771
	for <ldapbis-archive@lists.ietf.org>; Tue, 28 Oct 2003 06:02:10 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9SAxSHW051392;
	Tue, 28 Oct 2003 11:00:03 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9SAt7Ud050451;
	Tue, 28 Oct 2003 10:55:07 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 28 Oct 2003 10:55:07 +0000
Received: from pat.uio.no (IDENT:7411@pat.uio.no [129.240.130.16])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9SAt1HS050418;
	Tue, 28 Oct 2003 10:55:02 GMT
	(envelope-from hbf@bombur.uio.no)
Received: from mail-mx1.uio.no ([129.240.10.29])
	by pat.uio.no with esmtp (Exim 4.20)
	id 1AERV4-0002Ss-KY; Tue, 28 Oct 2003 11:54:58 +0100
Received: from bombur.uio.no ([129.240.186.42])
	by mail-mx1.uio.no with esmtp (Exim 4.14)
	id 1AERUq-0004W0-9l; Tue, 28 Oct 2003 11:54:44 +0100
Received: from hbf by bombur.uio.no with local (Exim 2.12 #7)
	id 1AERUp-0004Qk-00; Tue, 28 Oct 2003 11:54:43 +0100
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Message-Id: <HBF.20031028unj2@bombur.uio.no>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Cc: ietf-ldapbis@OpenLDAP.org
Subject: Re: authmeth-07 issues
In-Reply-To: <6.0.0.22.0.20031027130022.02bc7e68@127.0.0.1>
References: <HBF.20031014pk3@bombur.uio.no>
	<HBF.200310276iv@bombur.uio.no>
	<6.0.0.22.0.20031027130022.02bc7e68@127.0.0.1>
X-Mailer: VM 6.37 under Emacs 19.34.1
Date: Tue, 28 Oct 2003 11:54:43 +0100
X-MailScanner-Information: This message has been scanned for viruses/spam. Contact postmaster@uio.no if you have questions about this scanning.
X-UiO-MailScanner: No virus found
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Kurt D. Zeilenga writes:
>At 11:54 AM 10/27/2003, Hallvard B Furuseth wrote:
>>
>> However, that means that after a _failed_ LDAP bind, the connection will
>> be left anonymous (because [Authmeth] and [Protocol] say so), but with
>> the old SASL layer still in effect.  That's ugly, but I don't see that
>> anything can be done about it.
> 
> Actually, I think the current SASL I-D says old layers are not
> to be left installed after a subsequent authentication.

Oh yes, subsequent non-SASL authentication... I forgot that.

> This is counter to what RFC 2829 said (it left them installed).

I can't find anything about that it RFC 2829 at all, so I guess you mean
the layers stayed installed by defaulit.

> I note that layer removal likely should be consistent across
> all forms of LDAP authentication.  If old SASL layers are removed
> upon subsequent SASL authentication, I think they also should
> be upon subsequent non-SASL authentication.

Sure, that would be nice.  However, if the layer is to be deinstalled by
another mechanism that the one specified in [SASL], we need [SASL] to
specify that the layers themselves must contain a 'deinstall layer'
command.

> Anyways, as there is a strong argument that LDAP must use SASL as
> specified in its revision, I advise those who have concerns as to
> whether the layers should be left installed or not voice those
> concerns on the SASL WG mailing list.

Sounds like you:-) I can live with keeping things the way you say they
were in rfc2829.

-- 
Hallvard


From owner-ietf-ldapbis@OpenLDAP.org  Tue Oct 28 09:16: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 JAA21651
	for <ldapbis-archive@lists.ietf.org>; Tue, 28 Oct 2003 09:16:56 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9SEBTI8072066;
	Tue, 28 Oct 2003 14:15:11 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9SEA1WB071901;
	Tue, 28 Oct 2003 14:10:01 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 28 Oct 2003 14:10:01 +0000
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9SE9wHS071888
	for <ietf-ldapbis@openldap.org>; Tue, 28 Oct 2003 14:09:58 GMT
	(envelope-from dinaras@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 JAA21019;
	Tue, 28 Oct 2003 09:09:47 -0500 (EST)
Message-Id: <200310281409.JAA21019@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-02.txt
Date: Tue, 28 Oct 2003 09:09:46 -0500
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-02.txt
	Pages		: 18
	Date		: 2003-10-27
	
The previous Lightweight Directory Access Protocol (LDAP) technical
specifications did not precisely define how character string matching
is to be performed.  This lead to a number of usability and
interoperability problems.  This document defines string preparation
algorithms for character-based matching rules defined for use in LDAP.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ldapbis-strprep-02.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-02.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-02.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-10-28092758.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ldapbis-strprep-02.txt

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

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

--OtherAccess--

--NextPart--




From owner-ietf-ldapbis@OpenLDAP.org  Tue Oct 28 09:16: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 JAA21650
	for <ldapbis-archive@lists.ietf.org>; Tue, 28 Oct 2003 09:16:56 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9SEBTI2072066;
	Tue, 28 Oct 2003 14:15:10 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9SE9nbe071841;
	Tue, 28 Oct 2003 14:09:49 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 28 Oct 2003 14:09:49 +0000
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9SE9hHS071830
	for <ietf-ldapbis@openldap.org>; Tue, 28 Oct 2003 14:09:47 GMT
	(envelope-from dinaras@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 JAA20931;
	Tue, 28 Oct 2003 09:09:26 -0500 (EST)
Message-Id: <200310281409.JAA20931@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-bcp64-01.txt
Date: Tue, 28 Oct 2003 09:09:25 -0500
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		: IANA Considerations for LDAP
	Author(s)	: K. Zeilenga
	Filename	: draft-ietf-ldapbis-bcp64-01.txt
	Pages		: 15
	Date		: 2003-10-27
	
This document provides procedures for registering extensible elements
of Lightweight Directory Access Protocol (LDAP).  The document also
provides guidelines to Internet Assigned Numbers Authority (IANA)
describing conditions under which new values can be assigned.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ldapbis-bcp64-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-ietf-ldapbis-bcp64-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-ietf-ldapbis-bcp64-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.

--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-10-28092709.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ldapbis-bcp64-01.txt

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

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

--OtherAccess--

--NextPart--




From owner-ietf-ldapbis@OpenLDAP.org  Tue Oct 28 09:16: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 JAA21668
	for <ldapbis-archive@lists.ietf.org>; Tue, 28 Oct 2003 09:16:58 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9SEBTIE072066;
	Tue, 28 Oct 2003 14:15:12 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9SEAQeG071963;
	Tue, 28 Oct 2003 14:10:26 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 28 Oct 2003 14:10:26 +0000
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9SEANHS071946
	for <ietf-ldapbis@openldap.org>; Tue, 28 Oct 2003 14:10:24 GMT
	(envelope-from dinaras@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 JAA21082;
	Tue, 28 Oct 2003 09:10:13 -0500 (EST)
Message-Id: <200310281410.JAA21082@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-protocol-18.txt
Date: Tue, 28 Oct 2003 09:10:12 -0500
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: The Protocol
	Author(s)	: J. Sermersheim
	Filename	: draft-ietf-ldapbis-protocol-18.txt
	Pages		: 63
	Date		: 2003-10-27
	
This document describes the protocol elements, along with their 
semantics and encodings, for the Lightweight Directory Access 
Protocol (LDAP). LDAP provides access to distributed directory 
services that act in accordance with X.500 data and service models. 
These protocol elements are based on those described in the X.500 
Directory Access Protocol (DAP).

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ldapbis-protocol-18.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-protocol-18.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-protocol-18.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-10-28092850.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ldapbis-protocol-18.txt

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

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

--OtherAccess--

--NextPart--




From owner-ietf-ldapbis@OpenLDAP.org  Tue Oct 28 09:17: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 JAA21667
	for <ldapbis-archive@lists.ietf.org>; Tue, 28 Oct 2003 09:16:58 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9SEBTIC072066;
	Tue, 28 Oct 2003 14:15:12 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9SE9tIa071872;
	Tue, 28 Oct 2003 14:09:55 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 28 Oct 2003 14:09:55 +0000
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9SE9kHS071831
	for <ietf-ldapbis@openldap.org>; Tue, 28 Oct 2003 14:09:50 GMT
	(envelope-from dinaras@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 JAA20966;
	Tue, 28 Oct 2003 09:09:31 -0500 (EST)
Message-Id: <200310281409.JAA20966@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-authmeth-08.txt
Date: Tue, 28 Oct 2003 09:09:31 -0500
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: Authentication Methods and Connection Level Security Mechanism
	Author(s)	: R. Harrison
	Filename	: draft-ietf-ldapbis-authmeth-08.txt
	Pages		: 53
	Date		: 2003-10-27
	
This document describes authentication methods and connection level 
   security mechanisms of the Lightweight Directory Access Protocol 
   (LDAP).  
 
   This document details the simple Bind authentication method 
   including anonymous, unauthenticated, and plain-text password 
   methods and the SASL (Simple Authentication and Security Layer) Bind 
   authentication method including the use of DIGEST-MD5 and EXTERNAL 
This document also details establishment of TLS (Transport Layer 
   Security) using the Start TLS operation. 
    
   This document describes various authentication and authorization 
   states through which a connection to an LDAP server may pass and the 
   actions that trigger these state changes. 
    
   This document also prescribes DIGEST-MD5 as LDAP's mandatory-to-
   implement strong authentication mechanism.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ldapbis-authmeth-08.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-authmeth-08.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-authmeth-08.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-10-28092725.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ldapbis-authmeth-08.txt

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

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

--OtherAccess--

--NextPart--




From owner-ietf-ldapbis@OpenLDAP.org  Tue Oct 28 09:17: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 JAA21665
	for <ldapbis-archive@lists.ietf.org>; Tue, 28 Oct 2003 09:16:58 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9SEBTI4072066;
	Tue, 28 Oct 2003 14:15:11 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9SE9uFF071881;
	Tue, 28 Oct 2003 14:09:56 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 28 Oct 2003 14:09:56 +0000
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9SE9oHS071849
	for <ietf-ldapbis@openldap.org>; Tue, 28 Oct 2003 14:09:51 GMT
	(envelope-from dinaras@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 JAA21001;
	Tue, 28 Oct 2003 09:09:39 -0500 (EST)
Message-Id: <200310281409.JAA21001@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-models-09.txt
Date: Tue, 28 Oct 2003 09:09:39 -0500
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: Directory Information Models
	Author(s)	: K. Zeilenga
	Filename	: draft-ietf-ldapbis-models-09.txt
	Pages		: 49
	Date		: 2003-10-27
	
The Lightweight Directory Access Protocol (LDAP) is an Internet
protocol for accessing distributed directory services which act in
accordance with X.500 data and service models.  This document
describes the X.500 Directory Information Models.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ldapbis-models-09.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-models-09.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-models-09.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-10-28092741.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ldapbis-models-09.txt

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

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

--OtherAccess--

--NextPart--




From owner-ietf-ldapbis@OpenLDAP.org  Tue Oct 28 09:17: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 JAA21832
	for <ldapbis-archive@lists.ietf.org>; Tue, 28 Oct 2003 09:17:37 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9SEBTI0072066;
	Tue, 28 Oct 2003 14:15:10 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9SEAXj4071981;
	Tue, 28 Oct 2003 14:10:33 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 28 Oct 2003 14:10:33 +0000
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9SEAUHS071971
	for <ietf-ldapbis@openldap.org>; Tue, 28 Oct 2003 14:10:31 GMT
	(envelope-from dinaras@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 JAA21098;
	Tue, 28 Oct 2003 09:10:19 -0500 (EST)
Message-Id: <200310281410.JAA21098@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-url-04.txt
Date: Tue, 28 Oct 2003 09:10:19 -0500
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: Uniform Resource Locator
	Author(s)	: M. Smith, T. Howes
	Filename	: draft-ietf-ldapbis-url-04.txt
	Pages		: 13
	Date		: 2003-10-27
	
This document describes a format for an LDAP Uniform Resource Locator
(URL).  An LDAP URL describes an LDAP search operation that is used
to retrieve information from an LDAP directory, or, in the context of
an LDAPv3 referral or reference, an LDAP URL describes a service
where an LDAP operation may be progressed.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ldapbis-url-04.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-url-04.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-url-04.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-10-28092903.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ldapbis-url-04.txt

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

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

--OtherAccess--

--NextPart--




From owner-ietf-ldapbis@OpenLDAP.org  Tue Oct 28 09:17: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 JAA21851
	for <ldapbis-archive@lists.ietf.org>; Tue, 28 Oct 2003 09:17:39 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9SEBTI6072066;
	Tue, 28 Oct 2003 14:15:11 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9SEA7gt071918;
	Tue, 28 Oct 2003 14:10:07 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 28 Oct 2003 14:10:07 +0000
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9SEA5HS071908
	for <ietf-ldapbis@openldap.org>; Tue, 28 Oct 2003 14:10:05 GMT
	(envelope-from dinaras@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 JAA21043;
	Tue, 28 Oct 2003 09:09:54 -0500 (EST)
Message-Id: <200310281409.JAA21043@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-filter-05.txt
Date: Tue, 28 Oct 2003 09:09:53 -0500
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 Search Filters
	Author(s)	: M. Smith, T. Howes
	Filename	: draft-ietf-ldapbis-filter-05.txt
	Pages		: 12
	Date		: 2003-10-27
	
LDAP search filters are transmitted in the LDAP protocol using a
binary representation that is appropriate for use on the network.
This document defines a human-readable string representation of LDAP
search filters that is appropriate for use in LDAP URLs and in other
applications

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ldapbis-filter-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-filter-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-filter-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-10-28092813.I-D@ietf.org>

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

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

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

--OtherAccess--

--NextPart--




From owner-ietf-ldapbis@OpenLDAP.org  Tue Oct 28 09:17:42 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21867
	for <ldapbis-archive@lists.ietf.org>; Tue, 28 Oct 2003 09:17:41 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9SEBTIA072066;
	Tue, 28 Oct 2003 14:15:12 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9SEAJpc071937;
	Tue, 28 Oct 2003 14:10:19 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 28 Oct 2003 14:10:19 +0000
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9SEAHHS071926
	for <ietf-ldapbis@openldap.org>; Tue, 28 Oct 2003 14:10:18 GMT
	(envelope-from dinaras@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 JAA21063;
	Tue, 28 Oct 2003 09:10:06 -0500 (EST)
Message-Id: <200310281410.JAA21063@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-syntaxes-07.txt
Date: Tue, 28 Oct 2003 09:10:06 -0500
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: Syntaxes and Matching Rules
	Author(s)	: K. Dally, S. Legg
	Filename	: draft-ietf-ldapbis-syntaxes-07.txt
	Pages		: 48
	Date		: 2003-10-27
	
Each attribute stored in a Lightweight Directory Access Protocol
(LDAP) directory, and whose values may be transfered in the LDAP
protocol, has a defined syntax which constrains the structure and
format of its values.  The comparison semantics for values of a
syntax are not part of the syntax definition but are instead provided
through separately defined matching rules.  Matching rules specify an
argument, an assertion value, which also has a defined syntax.  This
document defines a base set of syntaxes and matching rules for use in
defining attributes for LDAP directories.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ldapbis-syntaxes-07.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-syntaxes-07.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-syntaxes-07.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-10-28092829.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ldapbis-syntaxes-07.txt

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

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

--OtherAccess--

--NextPart--




From owner-ietf-ldapbis@OpenLDAP.org  Tue Oct 28 09:21: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 JAA22350
	for <ldapbis-archive@lists.ietf.org>; Tue, 28 Oct 2003 09:21:32 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9SEHTHW072624;
	Tue, 28 Oct 2003 14:20:01 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9SEFs5C072452;
	Tue, 28 Oct 2003 14:15:54 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 28 Oct 2003 14:15:54 +0000
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9SEFoHS072441
	for <ietf-ldapbis@openldap.org>; Tue, 28 Oct 2003 14:15:50 GMT
	(envelope-from dinaras@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 JAA21517;
	Tue, 28 Oct 2003 09:15:39 -0500 (EST)
Message-Id: <200310281415.JAA21517@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-12.txt
Date: Tue, 28 Oct 2003 09:15:38 -0500
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-12.txt
	Pages		: 14
	Date		: 2003-10-27
	
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-12.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-12.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-12.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-10-28093627.I-D@ietf.org>

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

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

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

--OtherAccess--

--NextPart--




From owner-ietf-ldapbis@OpenLDAP.org  Tue Oct 28 11:55:34 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 LAA07760
	for <ldapbis-archive@lists.ietf.org>; Tue, 28 Oct 2003 11:55:33 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9SGrYHW083504;
	Tue, 28 Oct 2003 16:53:47 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9SGpbxW083396;
	Tue, 28 Oct 2003 16:51:37 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 28 Oct 2003 16:51:37 +0000
Received: from pat.uio.no (IDENT:7411@pat.uio.no [129.240.130.16])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9SGpYHS083369
	for <ietf-ldapbis@openldap.org>; Tue, 28 Oct 2003 16:51:35 GMT
	(envelope-from hbf@bombur.uio.no)
Received: from mail-mx6.uio.no ([129.240.10.47])
	by pat.uio.no with esmtp (Exim 4.20)
	id 1AEX47-0007n2-Ap
	for ietf-ldapbis@openldap.org; Tue, 28 Oct 2003 17:51:31 +0100
Received: from bombur.uio.no ([129.240.186.42])
	by mail-mx6.uio.no with esmtp (Exim 4.14)
	id 1AEX42-0007Ru-3R
	for ietf-ldapbis@openldap.org; Tue, 28 Oct 2003 17:51:26 +0100
Received: from hbf by bombur.uio.no with local (Exim 2.12 #7)
	id 1AEX41-0005H3-00
	for ietf-ldapbis@OpenLDAP.org; Tue, 28 Oct 2003 17:51:25 +0100
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Message-Id: <HBF.20031028oouq@bombur.uio.no>
To: ietf-ldapbis@OpenLDAP.org
Subject: Authmeth: IPv6
Date: Tue, 28 Oct 2003 17:51:25 +0100
X-MailScanner-Information: This message has been scanned for viruses/spam. Contact postmaster@uio.no if you have questions about this scanning.
X-UiO-MailScanner: No virus found
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

[Authmeth]-08 section 1 says:

>   LDAP can be protected with the following security mechanisms: 
>   (...) TLS (...) SASL (...)

Also IPv6 data protection and/or authentication layers, I think.
I don't know IPv6, but I seem to remember mention of both protection
and certificates.

-- 
Hallvard


From owner-ietf-ldapbis@OpenLDAP.org  Tue Oct 28 12:44: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 MAA11773
	for <ldapbis-archive@lists.ietf.org>; Tue, 28 Oct 2003 12:44:18 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9SHfWI0088932;
	Tue, 28 Oct 2003 17:43:08 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9SHXWqw087861;
	Tue, 28 Oct 2003 17:33:32 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 28 Oct 2003 17:33:32 +0000
Received: from pat.uio.no (IDENT:7411@pat.uio.no [129.240.130.16])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9SHXTHS087835
	for <ietf-ldapbis@openldap.org>; Tue, 28 Oct 2003 17:33:30 GMT
	(envelope-from hbf@bombur.uio.no)
Received: from mail-mx3.uio.no ([129.240.10.44])
	by pat.uio.no with esmtp (Exim 4.20)
	id 1AEXig-0004OD-Jh
	for ietf-ldapbis@openldap.org; Tue, 28 Oct 2003 18:33:26 +0100
Received: from bombur.uio.no ([129.240.186.42])
	by mail-mx3.uio.no with esmtp (Exim 4.14)
	id 1AEXia-0006Hr-Q8
	for ietf-ldapbis@openldap.org; Tue, 28 Oct 2003 18:33:20 +0100
Received: from hbf by bombur.uio.no with local (Exim 2.12 #7)
	id 1AEXia-0005MQ-00
	for ietf-ldapbis@OpenLDAP.org; Tue, 28 Oct 2003 18:33:20 +0100
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Message-Id: <HBF.20031028nzmi@bombur.uio.no>
To: ietf-ldapbis@OpenLDAP.org
Subject: authmeth-08 comments
Date: Tue, 28 Oct 2003 18:33:20 +0100
X-MailScanner-Information: This message has been scanned for viruses/spam. Contact postmaster@uio.no if you have questions about this scanning.
X-UiO-MailScanner: No virus found
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

> 3. Bind Operation 
>     
>   The Bind operation defined in section 4.2 of [Protocol] allows 
>   authentication information to be exchanged between the client and 
>   server to establish a new LDAP association.
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

I would say '...to replace the old LDAP association with a new one',
otherwise it looks too much like creaing a new connection.

> 3.2. Simple Authentication  

Why was the mention of cleartext passwords removed here?  Now the only
mention of cleartext passwords is in Security Considerations, but
without mentioning that Simple Authentication uses them.

> 3.3.5. Rules for using SASL security layers 

>   If the client is configured to support multiple SASL mechanisms, it 
>   SHOULD fetch the supportedSASLmechanisms list both before and after 
>   the SASL security layer is negotiated. This allows the client to 
>   detect active attacks that remove supported SASL mechanisms from the 
>   supportedSASLMechanisms list and allows the client to ensure that it 
>   is using the best mechanism supported by both client and server. (In 
>   particular, this allows for environments where the 
>   supportedSASLMechanisms list is provided to the client through a 
>   different trusted source, e.g. as part of a digitally signed 
>   object.) 

This ()'ed text is misleading, I liked the original better.  It isn't
what the client SHOULD do which allows for what the () says, but that it
may ignore the SHOULD.  You could say something like this:

    (Though it need not re-fetch supportedSASLMechanisms in
    environments where the supportedSASLMechanisms list was provided to
    the client through a different trusted source, e.g. as part of a
    digitally signed object.)

> 3.4.1. Authorization Identity Syntax 
>   The authorization identity is a string of [UTF-8] encoded [Unicode] 
>   (...)
>   is defined as only a sequence of of [UTF-8] encoded [Unicode] 

I don't know if this will happen, but the text "UTF-8" is lost if the
RFC Editor replaces [UTF-8] with [RFCnnnn].  If so, you need to write
'UTF-8 [UTF-8]'.

The same applies to '[TLS]' and '[PLAIN]' various places in the document.

BTW, remove an "of" in "of of".

> 4.1.5. Server Identity Check 

>     - The client MUST use the server provided by the user (or other 
>       trusted entity) as the value to compare against the server name 

I'm not sure why you deleted 'hostname' after 'server' in the first line
here, but shouldn't it at least be 'server name'?


BTW, should I go through my 'authmeth-07 issues' message and list the
ones that are still outstanding?

-- 
Hallvard


From owner-ietf-ldapbis@OpenLDAP.org  Tue Oct 28 13:25: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 NAA14539
	for <ldapbis-archive@lists.ietf.org>; Tue, 28 Oct 2003 13:25:49 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9SINVHW092367;
	Tue, 28 Oct 2003 18:23:56 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9SIKMMJ092254;
	Tue, 28 Oct 2003 18:20:22 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 28 Oct 2003 18:20:22 +0000
Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9SIKJHS092244
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 28 Oct 2003 18:20:19 GMT
	(envelope-from rlmorgan@washington.edu)
Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139])
	by mxout4.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9SIKHmw009931;
	Tue, 28 Oct 2003 10:20:18 -0800
Received: from D-140-142-21-77.dhcp4.washington.edu (D-140-142-21-77.dhcp4.washington.edu [140.142.21.77])
	(authenticated bits=0)
	by smtp.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9SIKHx0025902
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT);
	Tue, 28 Oct 2003 10:20:17 -0800
Date: Tue, 28 Oct 2003 10:20:18 -0800 (PST)
From: "RL 'Bob' Morgan" <rlmorgan@washington.edu>
X-X-Sender: rlmorgan@perp.cac.washington.edu
To: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
cc: IETF ldapbis WG <ietf-ldapbis@OpenLDAP.org>
Subject: Re: Authmeth: IPv6
In-Reply-To: <HBF.20031028oouq@bombur.uio.no>
Message-ID: <Pine.LNX.4.58.0310280959190.2547@perp.cac.washington.edu>
References: <HBF.20031028oouq@bombur.uio.no>
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>


On Tue, 28 Oct 2003, Hallvard B Furuseth wrote:

> [Authmeth]-08 section 1 says:
>
> >   LDAP can be protected with the following security mechanisms:
> >   (...) TLS (...) SASL (...)
>
> Also IPv6 data protection and/or authentication layers, I think. I don't
> know IPv6, but I seem to remember mention of both protection and
> certificates.

I think the protection you're thinking about is IPsec, which applies
identically for both IPv4 and IPv6 as far as I know.  I agree that IPsec
should be listed as a possible protection mechanism in this introductory
text.  Of course, unlike SASL and TLS there are no IPsec-specific elements
in the LDAP protocol.

IPsec is referred to in the state-transition table, with associated
question marks ("?") that I guess indicate some more clarification is
needed?

 - RL "Bob"



From owner-ietf-ldapbis@OpenLDAP.org  Tue Oct 28 13:48:54 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16117
	for <ldapbis-archive@lists.ietf.org>; Tue, 28 Oct 2003 13:48:53 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9SIlVHa093627;
	Tue, 28 Oct 2003 18:47:35 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9SIguqd093494;
	Tue, 28 Oct 2003 18:42:56 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 28 Oct 2003 18:42:56 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9SIgfHS093484
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 28 Oct 2003 18:42:41 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from gypsy.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.9/8.12.9) with ESMTP id h9SIgflg079179;
	Tue, 28 Oct 2003 18:42:41 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.0.22.0.20031028104007.044d5048@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
Date: Tue, 28 Oct 2003 10:41:56 -0800
To: "RL 'Bob' Morgan" <rlmorgan@washington.edu>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: Authmeth: IPv6
Cc: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>,
        IETF ldapbis WG <ietf-ldapbis@OpenLDAP.org>
In-Reply-To: <Pine.LNX.4.58.0310280959190.2547@perp.cac.washington.edu>
References: <HBF.20031028oouq@bombur.uio.no>
 <Pine.LNX.4.58.0310280959190.2547@perp.cac.washington.edu>
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:20 AM 10/28/2003, RL 'Bob' Morgan wrote:
>I agree that IPsec
>should be listed as a possible protection mechanism in this introductory
>text. 

I'd prefer the list to be clarified to be of LDAP security
mechanisms and then add a subsequent note saying that
LDAP may also be protected by other means (IPsec, etc.).

Kurt 



From owner-ietf-ldapbis@OpenLDAP.org  Tue Oct 28 13:49: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 NAA16144
	for <ldapbis-archive@lists.ietf.org>; Tue, 28 Oct 2003 13:49:01 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9SIlVHc093627;
	Tue, 28 Oct 2003 18:47:35 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9SIkLb5093603;
	Tue, 28 Oct 2003 18:46:21 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 28 Oct 2003 18:46:21 +0000
Received: from pat.uio.no (IDENT:7411@pat.uio.no [129.240.130.16])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9SIkJHS093593
	for <ietf-ldapbis@openldap.org>; Tue, 28 Oct 2003 18:46:19 GMT
	(envelope-from hbf@bombur.uio.no)
Received: from mail-mx4.uio.no ([129.240.10.45])
	by pat.uio.no with esmtp (Exim 4.20)
	id 1AEYr9-00059K-Sj
	for ietf-ldapbis@openldap.org; Tue, 28 Oct 2003 19:46:15 +0100
Received: from bombur.uio.no ([129.240.186.42])
	by mail-mx4.uio.no with esmtp (Exim 4.14)
	id 1AEYr4-0003hj-KD
	for ietf-ldapbis@openldap.org; Tue, 28 Oct 2003 19:46:10 +0100
Received: from hbf by bombur.uio.no with local (Exim 2.12 #7)
	id 1AEYr4-0005YD-00
	for ietf-ldapbis@OpenLDAP.org; Tue, 28 Oct 2003 19:46:10 +0100
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Message-Id: <HBF.20031028mrse@bombur.uio.no>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: IETF ldapbis WG <ietf-ldapbis@OpenLDAP.org>
Subject: Re: Authmeth: IPv6
In-Reply-To: <Pine.LNX.4.58.0310280959190.2547@perp.cac.washington.edu>
References: <HBF.20031028oouq@bombur.uio.no>
	<Pine.LNX.4.58.0310280959190.2547@perp.cac.washington.edu>
X-Mailer: VM 6.37 under Emacs 19.34.1
Date: Tue, 28 Oct 2003 19:46:10 +0100
X-MailScanner-Information: This message has been scanned for viruses/spam. Contact postmaster@uio.no if you have questions about this scanning.
X-UiO-MailScanner: No virus found
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

RL 'Bob' Morgan writes:
>On Tue, 28 Oct 2003, Hallvard B Furuseth wrote:
>>[Authmeth]-08 section 1 says:
>>
>>>   LDAP can be protected with the following security mechanisms:
>>>   (...) TLS (...) SASL (...)
>>
>> Also IPv6 data protection and/or authentication layers, I think. I don't
>> know IPv6, but I seem to remember mention of both protection and
>> certificates.
> 
> I think the protection you're thinking about is IPsec, which applies
> identically for both IPv4 and IPv6 as far as I know.

Probably.  I know nothing of either.

Roger, note that I made the same mistake in my 'authmeth-07 issues'
message.

-- 
Hallvard


From owner-ietf-ldapbis@OpenLDAP.org  Tue Oct 28 14:18:42 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17702
	for <ldapbis-archive@lists.ietf.org>; Tue, 28 Oct 2003 14:18:42 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9SJC2I0094838;
	Tue, 28 Oct 2003 19:17:21 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9SJ1psr094279;
	Tue, 28 Oct 2003 19:01:51 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 28 Oct 2003 19:01:51 +0000
Received: from nb2.stroeder.com (krl9-d9bb436b.pool.mediaWays.net [217.187.67.107])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9SJ1mHS094260
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 28 Oct 2003 19:01:49 GMT
	(envelope-from michael@stroeder.com)
Received: from localhost (localhost [127.0.0.1])
	by nb2.stroeder.com (Postfix) with ESMTP id 3343A7F35A
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 28 Oct 2003 16:50:17 +0100 (CET)
Received: from stroeder.com (localhost [127.0.0.1])
	by nb2.stroeder.com (Postfix) with ESMTP id 301567F34F
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 28 Oct 2003 16:50:16 +0100 (CET)
Message-ID: <3F9E9038.5060304@stroeder.com>
Date: Tue, 28 Oct 2003 16:50:16 +0100
From: =?ISO-8859-1?Q?Michael_Str=F6der?= <michael@stroeder.com>
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)
X-Accept-Language: de-de, de, en-us, en
MIME-Version: 1.0
To: ietf-ldapbis@OpenLDAP.org
Subject: DIT Content Rules
References: <200310281409.JAA21001@ietf.org>
In-Reply-To: <200310281409.JAA21001@ietf.org>
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!

Reviewing draft-ietf-ldapbis-models-09 I wonder whether a DIT content rule 
also applies to inherited structural object classes.

Example: If I have a content rule for object class 'person' does this also 
apply to object class 'inetOrgPerson'?

The implementation I'm testing with does not seem to apply the content rule 
to inherited object classes but section 4.1.6 "DIT Content Rules" is not 
very explicit on this.

The current text is:

   For DIT entries of a particular structural object class, [..]

The word "particular" might be too weak.

Ciao, Michael.



From owner-ietf-ldapbis@OpenLDAP.org  Tue Oct 28 15:32: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 PAA23774
	for <ldapbis-archive@lists.ietf.org>; Tue, 28 Oct 2003 15:32:34 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9SKTWHW098852;
	Tue, 28 Oct 2003 20:31:14 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9SKRt02098763;
	Tue, 28 Oct 2003 20:27:55 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 28 Oct 2003 20:27:55 +0000
Received: from e3.ny.us.ibm.com (e3.ny.us.ibm.com [32.97.182.103])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9SKRpHS098730;
	Tue, 28 Oct 2003 20:27:51 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.10/8.12.2) with ESMTP id h9SKRUYJ102742;
	Tue, 28 Oct 2003 15:27:30 -0500
Received: from d27ml001.rchland.ibm.com (d01av02.pok.ibm.com [9.56.224.216])
	by northrelay04.pok.ibm.com (8.12.9/NCO/VER6.6) with ESMTP id h9SKRTQY054828;
	Tue, 28 Oct 2003 15:27:29 -0500
Subject: Re: DIT Content Rules
To: Michael =?ISO-8859-1?Q?Str=F6der?= <michael@stroeder.com>
Cc: ietf-ldapbis@OpenLDAP.org, owner-ietf-ldapbis@OpenLDAP.org
X-Mailer: Lotus Notes Release 5.0.12   February 13, 2003
Message-ID: <OF8BF50F47.D8FCF925-ON86256DCD.006F7B77-86256DCD.007060BD@us.ibm.com>
From: John McMeeking <jmcmeek@us.ibm.com>
Date: Tue, 28 Oct 2003 14:27:26 -0600
X-MIMETrack: Serialize by Router on d27ml001/27/M/IBM(Release 6.5|September 18, 2003) at
 10/28/2003 02:27:28 PM
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 h9SKRqHS098734
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 least going back to X.501(1993):

   The DIT content rules of superclasses of the structural object class for
an entry do not apply to that entry.

For your example, I interpret that as meaning that a DIT content rule for
person does not apply to inetorgperson.

It looks like that specific statement is missing from [models] though much
of the text surrounding it (in X.501) is present.

I think it would be appropriate to add this statement to [models].


John  McMeeking



                                                                                                                       
                      Michael Ströder                                                                                  
                      <michael@stroeder.co        To:       ietf-ldapbis@OpenLDAP.org                                  
                      m>                          cc:                                                                  
                      Sent by:                    Subject:  DIT Content Rules                                          
                      owner-ietf-ldapbis@O                                                                             
                      penLDAP.org                                                                                      
                                                                                                                       
                                                                                                                       
                      10/28/2003 09:50 AM                                                                              
                                                                                                                       
                                                                                                                       




HI!

Reviewing draft-ietf-ldapbis-models-09 I wonder whether a DIT content rule
also applies to inherited structural object classes.

Example: If I have a content rule for object class 'person' does this also
apply to object class 'inetOrgPerson'?

The implementation I'm testing with does not seem to apply the content rule
to inherited object classes but section 4.1.6 "DIT Content Rules" is not
very explicit on this.

The current text is:

   For DIT entries of a particular structural object class, [..]

The word "particular" might be too weak.

Ciao, Michael.






From owner-ietf-ldapbis@OpenLDAP.org  Tue Oct 28 15: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 PAA24250
	for <ldapbis-archive@lists.ietf.org>; Tue, 28 Oct 2003 15:36:51 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9SKZVHW099219;
	Tue, 28 Oct 2003 20:35:37 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9SKVt8K098950;
	Tue, 28 Oct 2003 20:31:55 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 28 Oct 2003 20:31:55 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9SKVrHS098940
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 28 Oct 2003 20:31:53 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from gypsy.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.9/8.12.9) with ESMTP id h9SKVrlg080282;
	Tue, 28 Oct 2003 20:31:53 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.0.22.0.20031028120011.02b07d78@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
Date: Tue, 28 Oct 2003 12:31:08 -0800
To: Michael =?iso-8859-1?Q?Str=F6der?= <michael@stroeder.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: DIT Content Rules
Cc: ietf-ldapbis@OpenLDAP.org
In-Reply-To: <3F9E9038.5060304@stroeder.com>
References: <200310281409.JAA21001@ietf.org>
 <3F9E9038.5060304@stroeder.com>
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 h9SKVrHS098941
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 07:50 AM 10/28/2003, Michael Ströder wrote:
>Reviewing draft-ietf-ldapbis-models-09 I wonder whether a DIT content rule also applies to inherited structural object classes.

No.  

>The word "particular" might be too weak.

The word choice is due to X.501.
  A DIT content rule is a "rule governing the content of entries of
  a particular structural object class" [X.501].

I think the text is clear here an entry is governed by the
rule for its structural object class.  As discussed in 2.4.2,
an entry is of one structural object class (but may belong
to many structural object classes).

Anyways, please feel free to offer alternative text for
consideration.

Kurt 




From owner-ietf-ldapbis@OpenLDAP.org  Tue Oct 28 15:49: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 PAA26001
	for <ldapbis-archive@lists.ietf.org>; Tue, 28 Oct 2003 15:49:06 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9SKlWHW099704;
	Tue, 28 Oct 2003 20:47:58 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9SKkt4l099677;
	Tue, 28 Oct 2003 20:46:55 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 28 Oct 2003 20:46:55 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9SKkjHS099640;
	Tue, 28 Oct 2003 20:46:49 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from gypsy.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.9/8.12.9) with ESMTP id h9SKkjlg080474;
	Tue, 28 Oct 2003 20:46:45 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.0.22.0.20031028124426.044d60d0@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
Date: Tue, 28 Oct 2003 12:46:00 -0800
To: John McMeeking <jmcmeek@us.ibm.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: DIT Content Rules
Cc: Michael =?iso-8859-1?Q?Str=F6der?= <michael@stroeder.com>,
        ietf-ldapbis@OpenLDAP.org, owner-ietf-ldapbis@OpenLDAP.org
In-Reply-To: <OF8BF50F47.D8FCF925-ON86256DCD.006F7B77-86256DCD.007060BD@
 us.ibm.com>
References: <OF8BF50F47.D8FCF925-ON86256DCD.006F7B77-86256DCD.007060BD@us.ibm.com>
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 h9SKknHS099641
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

How about if I add:
  DIT content rules for superclasses of the structural object class
  of an entry are not applicable to that entry.

at the end of the paragraph which starts with "An entry is governed
by"?

At 12:27 PM 10/28/2003, John McMeeking wrote:




>At least going back to X.501(1993):
>
>   The DIT content rules of superclasses of the structural object class for
>an entry do not apply to that entry.
>
>For your example, I interpret that as meaning that a DIT content rule for
>person does not apply to inetorgperson.
>
>It looks like that specific statement is missing from [models] though much
>of the text surrounding it (in X.501) is present.
>
>I think it would be appropriate to add this statement to [models].
>
>
>John  McMeeking
>
>
>
>                                                                                                                       
>                      Michael Ströder                                                                                  
>                      <michael@stroeder.co        To:       ietf-ldapbis@OpenLDAP.org                                  
>                      m>                          cc:                                                                  
>                      Sent by:                    Subject:  DIT Content Rules                                          
>                      owner-ietf-ldapbis@O                                                                             
>                      penLDAP.org                                                                                      
>                                                                                                                       
>                                                                                                                       
>                      10/28/2003 09:50 AM                                                                              
>                                                                                                                       
>                                                                                                                       
>
>
>
>
>HI!
>
>Reviewing draft-ietf-ldapbis-models-09 I wonder whether a DIT content rule
>also applies to inherited structural object classes.
>
>Example: If I have a content rule for object class 'person' does this also
>apply to object class 'inetOrgPerson'?
>
>The implementation I'm testing with does not seem to apply the content rule
>to inherited object classes but section 4.1.6 "DIT Content Rules" is not
>very explicit on this.
>
>The current text is:
>
>   For DIT entries of a particular structural object class, [..]
>
>The word "particular" might be too weak.
>
>Ciao, Michael.




From owner-ietf-ldapbis@OpenLDAP.org  Tue Oct 28 15:54: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 PAA26189
	for <ldapbis-archive@lists.ietf.org>; Tue, 28 Oct 2003 15:54:43 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9SKrVHW000172;
	Tue, 28 Oct 2003 20:53:39 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9SKlvkZ099731;
	Tue, 28 Oct 2003 20:47:57 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 28 Oct 2003 20:47:57 +0000
Received: from boole.openldap.org (kurt@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9SKltHS099719
	for <ietf-ldapbis@openldap.org>; Tue, 28 Oct 2003 20:47:55 GMT
	(envelope-from kurt@boole.openldap.org)
Received: (from kurt@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) id h9SKlt2s099718
	for ietf-ldapbis@openldap.org; Tue, 28 Oct 2003 12:47:55 -0800 (PST)
	(envelope-from kurt)
Received: from valiant.cnchost.com (valiant.concentric.net [207.155.252.9])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9SKeCHS099438
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 28 Oct 2003 20:40:17 GMT
	(envelope-from hyc@symas.com)
Received: from CELLO (c-24-126-120-178.we.client2.attbi.com [24.126.120.178])
	by valiant.cnchost.com
	id PAA09085; Tue, 28 Oct 2003 15:39:29 -0500 (EST)
	[ConcentricHost SMTP Relay 1.15]
From: "Howard Chu" <hyc@symas.com>
To: "'John McMeeking'" <jmcmeek@us.ibm.com>
Cc: <ietf-ldapbis@OpenLDAP.org>
Subject: RE: DIT Content Rules
Date: Tue, 28 Oct 2003 12:39:13 -0800
Message-ID: <009b01c39d93$94af36d0$8601a8c0@CELLO>
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 CWS, Build 9.0.6604 (9.0.2911.0)
In-Reply-To: <OF8BF50F47.D8FCF925-ON86256DCD.006F7B77-86256DCD.007060BD@us.ibm.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
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 John McMeeking

> At least going back to X.501(1993):
> 
>    The DIT content rules of superclasses of the structural 
> object class for
> an entry do not apply to that entry.
> 
> For your example, I interpret that as meaning that a DIT 
> content rule for
> person does not apply to inetorgperson.
> 
> It looks like that specific statement is missing from 
> [models] though much
> of the text surrounding it (in X.501) is present.
> 
> I think it would be appropriate to add this statement to [models].

Wouldn't it be more accurate to say

  The DIT content rules of superclasses of a structural objectclass
do not apply to that objectclass.

?

  -- 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  Wed Oct 29 01:26: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 BAA27291
	for <ldapbis-archive@lists.ietf.org>; Wed, 29 Oct 2003 01:26:25 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9T6NZHW024536;
	Wed, 29 Oct 2003 06:24:31 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9T6L8ub024512;
	Wed, 29 Oct 2003 06:21:08 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 29 Oct 2003 06:21:08 +0000
Received: from adacel.com (gunsmoke.adacel.com.au [210.11.130.7])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9T6L1HS024501
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 29 Oct 2003 06:21:05 GMT
	(envelope-from steven.legg@adacel.com.au)
Received: from nexus.adacel.com (Not Verified[10.32.240.1]) by adacel.com with NetIQ MailMarshal (v5.5.3.16)
	id <B000190444>; Wed, 29 Oct 2003 17:14:12 +1100
Received: (qmail 4666 invoked from network); 29 Oct 2003 06:20:38 -0000
Received: from unknown (HELO adacel.com.au) (10.32.24.165)
  by nexus.adacel.com with SMTP; 29 Oct 2003 06:20:38 -0000
Message-ID: <3F9F5C36.9070606@adacel.com.au>
Date: Wed, 29 Oct 2003 17:20:38 +1100
From: Steven Legg <steven.legg@adacel.com.au>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3.1) Gecko/20030425
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Ramsay, Ron" <Ron.Ramsay@ca.com>
CC: LDAP BIS <ietf-ldapbis@OpenLDAP.org>
Subject: Re: New text for X.501
References: <1395B4B334FCC143B36AF788E68B6381ABC4B9@ausyms21.ca.com>
In-Reply-To: <1395B4B334FCC143B36AF788E68B6381ABC4B9@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,

Ramsay, Ron wrote:
> OK
> 
> 1) DUA --> DSA --> LDAP Server is neither fish-nor-fowl. I see how your customers
 > may want you to do it, but I don't think it has anuthing to do with the current
 > topic.

I think it is relevant, but I'm not going to argue the point.

> 2) You escape the escape? Far out!

I escape a literal '\' just like RFC 2252 and draft-ietf-ldapbis-syntaxes-07.txt
say to do.

 > How does it apply to the case in hand where
 > clearly the escape is not escaped. That is, the value "street\$name$city" would
 > be stored like this in LDAP and stored as 30 12 0C 0A street$name 0C 04 city in
 > X.500.

Your LDAP value is incorrect according to RFC 2252 and the syntaxes draft,
though a liberal implementation may accept it anyway.

Regards,
Steven

> 
> Ron
> -----Original Message-----
> From: Steven Legg [mailto:steven.legg@adacel.com.au]
> Sent: Tuesday, 28 October 2003 16:49
> To: Ramsay, Ron
> Cc: LDAP BIS
> Subject: Re: New text for X.501
> 
> 
> 
> Ron,
> 
> Ramsay, Ron wrote:
> 
>>I must continue to object.
>>
>>1) If you use LDAP to chain then we have (for a chained update)
> 
>  > LDAP --> X.500 --> LDAP, not X.500 --> LDAP --> X.500!
> 
> A DAP modify comes in. The X.500 DSA determines the target entry is in
> another DSA (LDAP-only). It chains the modify to the other DSA as an
> LDAP modify (X.500 -> LDAP). The other DSA stores the new attribute
> values in the LDAP-specific encoding. The user submits a DAP read of
> the same target entry. The X.500 DSA chains the read as an LDAP search
> to the other DSA, which responds with the attribute values in the
> LDAP-specific encoding. The X.500 DSA reformats the attribute values in
> BER (LDAP -> X.500) to return to the user.
> 
> Overall the values have been through X.500 -> LDAP -> X.500.
> 
> 
>>2) Isn't the postal address escape just '\$'? I don't see the problem with case.
> 
> 
> The escape sequence is \24, but I got the wrong character. The backslash has
> to be escaped as well. The escape sequence for *it* is either \5C or \5c.
> 
> 
>>Dumping to LDIF and configuring using LDAP are not X.500-type operations
> 
>  > and so require no comment!
> 
> Paying customers don't care about such demarcations.
> 
> Regards,
> Steven
> 
> 
>>Ron
>>
>>-----Original Message-----
>>From: owner-ietf-ldapbis@OpenLDAP.org
>>[mailto:owner-ietf-ldapbis@OpenLDAP.org]On Behalf Of Steven Legg
>>Sent: Tuesday, 28 October 2003 15:27
>>To: Ramsay, Ron
>>Cc: LDAP BIS
>>Subject: Re: New text for X.501
>>
>>
>>
>>Ron,
>>
>>Ramsay, Ron wrote:
>>
>>
>>>I must protest that DirectoryString is one of the cases where the
>>
>> > abstract value can be preserved. In order to break it you have had
>> > to go X.500 -> LDAP -> X.500 and I don't see how this can be justified.
>> > LDAP is an access protocol, so we should never have the case to which
>> > you referred.
>>
>>This transformation occurs if an X.500 DSA uses LDIF to dump and reload
>>data. It also occurs if an X.500 DSA uses LDAP to chain to a subordinate
>>(LDAP-only) DSA.
>>
>>
>>
>>>On another matter, does PostalAddress allow spaces either side of the
>>
>> > '$'? If it doesn't, then this also is a syntax for which values can be
>> > preserved.
>>
>>The problem with PostalAddress is the need to escape any '$' character
>>in the abstract value. The escape sequence is case insensitive and could
>>be case inverted by LDAP -> BER -> LDAP.
>>
>>
>>
>>>Also, relating to the syntaxes that cannot be preserved, your previous
>>
>> > example seemed to concern configuration items like schema. While it may
>> > be appropriate to configure LDAP directories using LDAP, I don't know
>> > that this should be the case with X.500 directories.
>>
>>It's a necessity. There are LDAP applications that configure the schema
>>they need by using LDAP to modify the subschema subentry. Our directory
>>server let's them do it.
>>
>>Regards,
>>Steven
>>
>> > However, this still leaves items like SearchGuide.
>>
>>
>>>Ron
>>>
>>>-----Original Message-----
>>>From: owner-ietf-ldapbis@OpenLDAP.org
>>>[mailto:owner-ietf-ldapbis@OpenLDAP.org]On Behalf Of Steven Legg
>>>Sent: Tuesday, 28 October 2003 14:03
>>>To: David Chadwick
>>>Cc: LDAP BIS
>>>Subject: Re: New text for X.501
>>>
>>>
>>>
>>>David,
>>>
>>>David Chadwick wrote:
>>>
>>>
>>>
>>>>Steven
>>>>
>>>>We are talking about the abstract values and not the encoded values.
>>>>X.500 does not mandate any particular ASN.1 encoding rules except in the
>>>>case of the X.509 attributes which must be DER (and even this was later
>>>>realised to be a bug, but it is too late to change it now). DSAs/LDAP
>>>>servers will typically store local representations of abstract values
>>>>and what these are is not stated, its implementation dependent (although
>>>>in some cases such as the X.509 attributes, they will have to store the
>>>>encoded values so as to preserve the signatures). Whether the transfer
>>>>syntax is BER, LDAP or XER should be irrelevant to the abstract value.
>>>>Does this help to clarify what the intention is
>>>
>>>
>>>Yes, though you should be aware that there are cases where even the
>>>abstract value can't be preserved. The chosen alternative in a DirectoryString
>>>isn't guaranteed to be preserved in a transformation from BER to LDAP-specific
>>>to BER. This affects the Directory String syntax, as well as various syntaxes
>>>that have embedded DirectoryString components. The chosen alternative is
>>>inconsequential for directory purposes, but changing it is, by strict definition,
>>>a change to the abstract value.
>>>
>>>Regards,
>>>Steven
>>>
>>>
>>>
>>>
>>>>regards
>>>>
>>>>David
>>>>
>>>>
>>>>Steven Legg wrote:
>>>>
>>>>
>>>>
>>>>
>>>>>David,
>>>>>
>>>>>David Chadwick wrote:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>Dear LDAPers
>>>>>>
>>>>>>At the recent Geneva meeting of the X.500 group, Defect Report 303 was
>>>>>>discussed. This concerns the fact that a user cannot be guaranteed that
>>>>>>the information presented to LDAP/X.500 server in an update operation is
>>>>>>subsequently returned unaltered in a Search operation. Due to this, in
>>>>>>the PKIX work we are adding text to the IDs specifically to say that for
>>>>>>X.509 certificates and CRLs the data must not be altered by the LDAP
>>>>>>server. The X.500 group is going to go one step further than this and
>>>>>>state that no attributes must be altered by the server and must be
>>>>>>returned exactly as presented,
>>>>>
>>>>>I think this change is ill-advised, as the requirement cannot be enforced
>>>>>in a mixed LDAP/X.500 distributed environment. An attribute value that is
>>>>>entered in an LDAP-specific encoding has to be transformed into BER to be
>>>>>carried in DSP or DISP. There is no guarantee that the exact LDAP-specific
>>>>>encoding of the original attribute value will be reconstructed by the
>>>>>receiving DSA. Preservation of the exact encoding of PKI attributes can
>>>>>only be made to work in the general case because the LDAP encoding and the
>>>>>X.500 encoding is the same - BER. For most syntaxes this is not the case.
>>>>>
>>>>>The XED specifications introduce a third way of encoding directory data (DXER),
>>>>>which only increases the difficulty of preserving the original encoding.
>>>>>
>>>>>If the X.500 standards add this requirement then, as a practical necessity,
>>>>>I will have to disregard it. However, I will continue to preserve the abstract
>>>>>value of attribute values to the extent that it is possible to do so.
>>>>>
>>>>>Regards,
>>>>>Steven
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>although a server may store a
>>>>>>canonicalised form for efficient matching if it so desires.
>>>>>>
>>>>>>The defect report can only address the 1997 and 2001 versions of X.500,
>>>>>>since the 1993 version that LDAP is based in is no longer supported by
>>>>>>ITU-T/ISO.
>>>>>>
>>>>>>Here is the gist of the proposed text to fix the defect report.
>>>>>>
>>>>>>Stored attribute values must be held as supplied. We propose to add text
>>>>>>to X.501 in clause 8.5 and in 8.8.1, where we will point out that
>>>>>>rationalizations to stored values for the purposes of matching do not
>>>>>>effect the stored value. We will also add text to clause 6.1 of x.520
>>>>>>stating that the rationalizations describe in the matching rules are
>>>>>>ephemeral, for the purpose of the match only, and will not affect the
>>>>>>stored value.
>>>>>>
>>>>>>Regards
>>>>>>
>>>>>>David
>>>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>>
> 
> 
> 
> 



From owner-ietf-ldapbis@OpenLDAP.org  Wed Oct 29 04:20:15 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA29540
	for <ldapbis-archive@lists.ietf.org>; Wed, 29 Oct 2003 04:20:14 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9T9HaHW031387;
	Wed, 29 Oct 2003 09:18:11 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9T9Ei6o031320;
	Wed, 29 Oct 2003 09:14:44 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 29 Oct 2003 09:14:44 +0000
Received: from nb2.stroeder.com (lx.yapay.inka.de [193.197.184.188])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9T9EcHS031283;
	Wed, 29 Oct 2003 09:14:41 GMT
	(envelope-from michael@stroeder.com)
Received: from localhost (localhost [127.0.0.1])
	by nb2.stroeder.com (Postfix) with ESMTP
	id B7C187F423; Wed, 29 Oct 2003 08:57:18 +0100 (CET)
Received: from stroeder.com (localhost [127.0.0.1])
	by nb2.stroeder.com (Postfix) with ESMTP
	id 614DA7F41F; Wed, 29 Oct 2003 08:57:15 +0100 (CET)
Message-ID: <3F9F72DB.2090009@stroeder.com>
Date: Wed, 29 Oct 2003 08:57:15 +0100
From: =?ISO-8859-1?Q?Michael_Str=F6der?= <michael@stroeder.com>
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)
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: DIT Content Rules
References: <OF8BF50F47.D8FCF925-ON86256DCD.006F7B77-86256DCD.007060BD@us.ibm.com> <6.0.0.22.0.20031028124426.044d60d0@127.0.0.1>
In-Reply-To: <6.0.0.22.0.20031028124426.044d60d0@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:
> How about if I add:
>   DIT content rules for superclasses of the structural object class
>   of an entry are not applicable to that entry.
> 
> at the end of the paragraph which starts with "An entry is governed
> by"?

I'm fine with that.

Ciao, Michael.



From owner-ietf-ldapbis@OpenLDAP.org  Wed Oct 29 17:34: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 RAA11575
	for <ldapbis-archive@lists.ietf.org>; Wed, 29 Oct 2003 17:34:25 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9TMTeHW080601;
	Wed, 29 Oct 2003 22:33:02 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9TMQcUD080260;
	Wed, 29 Oct 2003 22:26:38 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 29 Oct 2003 22:26:37 +0000
Received: from nb2.stroeder.com (krl9-d9bb40b3.pool.mediaWays.net [217.187.64.179])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9TMQaHS080218
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 29 Oct 2003 22:26:36 GMT
	(envelope-from michael@stroeder.com)
Received: from localhost (localhost [127.0.0.1])
	by nb2.stroeder.com (Postfix) with ESMTP id EAB2F7F448
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 29 Oct 2003 18:34:13 +0100 (CET)
Received: from stroeder.com (localhost [127.0.0.1])
	by nb2.stroeder.com (Postfix) with ESMTP id DFFC97F21C
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 29 Oct 2003 18:34:10 +0100 (CET)
Message-ID: <3F9FFA12.50400@stroeder.com>
Date: Wed, 29 Oct 2003 18:34:10 +0100
From: =?ISO-8859-1?Q?Michael_Str=F6der?= <michael@stroeder.com>
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)
X-Accept-Language: de-de, de, en-us, en
MIME-Version: 1.0
To: LDAP BIS <ietf-ldapbis@OpenLDAP.org>
Subject: More on DIT content rules
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!

Still browsing through draft-ietf-ldapbis-models-09...

In section 2.4.3 there's written:

   [..] If no DIT content rule is associated with
   the structural object class of the entry, the entry cannot belong to
   any auxiliary object class.

I don't understand this statement. Shouldn't the 'cannot' be 'can'?

 From section 4.1.6.:

     MUST, MAY, and NOT specify lists of attribute types which are
         required, allowed, or precluded, respectively, from appearing in
         entries subject to this DIT content rule; and
     <extensions> describe extensions.

I'm a little bit scared of 'MUST' and 'MAY' extending the 'MUST' and 'MAY' 
of object classes. I consider this being redundant to schema design with 
object classes. Personally I'd appreciate a hint in the text stating that 
use of 'MUST' and 'MAY' in a DIT content rules is NOT RECOMMENDED since 
clients or servers might not support DIT content rules. Well, such a hint 
might be a little too much in the direction of a best practice guide.

Ciao, Michael.



From owner-ietf-ldapbis@OpenLDAP.org  Wed Oct 29 21:10: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 VAA20406
	for <ldapbis-archive@lists.ietf.org>; Wed, 29 Oct 2003 21:10:13 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9U1xgHW091352;
	Thu, 30 Oct 2003 02:00:22 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9U1sodX091274;
	Thu, 30 Oct 2003 01:54:50 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 30 Oct 2003 01:54:50 +0000
Received: from prv-mail20.provo.novell.com (prv-mail20.provo.novell.com [137.65.81.122])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9U1snHS091262
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 30 Oct 2003 01:54:49 GMT
	(envelope-from jimse@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Wed, 29 Oct 2003 18:54:29 -0700
Message-Id: <sfa00ce5.058@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.2 Beta
Date: Wed, 29 Oct 2003 18:54:19 -0700
From: "Jim Sermersheim" <jimse@novell.com>
To: <ietf-ldapbis@OpenLDAP.org>
Subject: Re: More on DIT content rules
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__PartC39D515B.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>

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.

--=__PartC39D515B.0__=
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Actually, what's being documented here has always been true. Most of the =
text is being pulled in part or whole (summarized or not) from X.501. =
Previously, one had to find these statements by reading hte ITU documents.
=20
Jim

>>> Michael Str=F6der <michael@stroeder.com> 10/29/03 10:34:10 AM >>>
HI!

Still browsing through draft-ietf-ldapbis-models-09...

In section 2.4.3 there's written:

[..] If no DIT content rule is associated with
the structural object class of the entry, the entry cannot belong to
any auxiliary object class.

I don't understand this statement. Shouldn't the 'cannot' be 'can'?

From section 4.1.6.:

MUST, MAY, and NOT specify lists of attribute types which are
required, allowed, or precluded, respectively, from appearing in
entries subject to this DIT content rule; and
<extensions> describe extensions.

I'm a little bit scared of 'MUST' and 'MAY' extending the 'MUST' and =
'MAY'=20
of object classes. I consider this being redundant to schema design =
with=20
object classes. Personally I'd appreciate a hint in the text stating =
that=20
use of 'MUST' and 'MAY' in a DIT content rules is NOT RECOMMENDED since=20
clients or servers might not support DIT content rules. Well, such a =
hint=20
might be a little too much in the direction of a best practice guide.

Ciao, Michael.




--=__PartC39D515B.0__=
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1"=
>
<META content=3D"MSHTML 5.50.4933.1800" name=3DGENERATOR></HEAD>
<BODY style=3D"MARGIN: 4px 4px 1px; FONT: 10pt Microsoft Sans Serif">
<DIV>Actually, what's being documented here has always been true. Most of =
the text is being pulled in part or whole (summarized or not) from X.501. =
Previously, one had to find these statements by reading hte ITU documents.<=
/DIV>
<DIV>&nbsp;</DIV>
<DIV>Jim<BR><BR>&gt;&gt;&gt; Michael Str=F6der &lt;michael@stroeder.com&gt;=
 10/29/03 10:34:10 AM &gt;&gt;&gt;<BR>HI!<BR><BR>Still browsing through =
draft-ietf-ldapbis-models-09...<BR><BR>In section 2.4.3 there's written:<BR=
><BR>[..] If no DIT content rule is associated with<BR>the structural =
object class of the entry, the entry cannot belong to<BR>any auxiliary =
object class.<BR><BR>I don't understand this statement. Shouldn't the =
'cannot' be 'can'?<BR><BR>From section 4.1.6.:<BR><BR>MUST, MAY, and NOT =
specify lists of attribute types which are<BR>required, allowed, or =
precluded, respectively, from appearing in<BR>entries subject to this DIT =
content rule; and<BR>&lt;extensions&gt; describe extensions.<BR><BR>I'm a =
little bit scared of 'MUST' and 'MAY' extending the 'MUST' and 'MAY' =
<BR>of object classes. I consider this being redundant to schema design =
with <BR>object classes. Personally I'd appreciate a hint in the text =
stating that <BR>use of 'MUST' and 'MAY' in a DIT content rules is NOT =
RECOMMENDED since <BR>clients or servers might not support DIT content =
rules. Well, such a hint <BR>might be a little too much in the direction =
of a best practice guide.<BR><BR>Ciao, Michael.<BR><BR></DIV></BODY></HTML>

--=__PartC39D515B.0__=--


From owner-ietf-ldapbis@OpenLDAP.org  Thu Oct 30 08:26: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 IAA21454
	for <ldapbis-archive@lists.ietf.org>; Thu, 30 Oct 2003 08:26:00 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9UDNkHW024557;
	Thu, 30 Oct 2003 13:24:34 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9UDIrCR024371;
	Thu, 30 Oct 2003 13:18:53 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 30 Oct 2003 13:18:53 +0000
Received: from e5.ny.us.ibm.com (e5.ny.us.ibm.com [32.97.182.105])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9UDImHS024341
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 30 Oct 2003 13:18:49 GMT
	(envelope-from jmcmeek@us.ibm.com)
Received: from northrelay02.pok.ibm.com (northrelay02.pok.ibm.com [9.56.224.150])
	by e5.ny.us.ibm.com (8.12.10/8.12.2) with ESMTP id h9UDI7n9276862
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 30 Oct 2003 08:18:17 -0500
Received: from d27ml001.rchland.ibm.com (d01av02.pok.ibm.com [9.56.224.216])
	by northrelay02.pok.ibm.com (8.12.9/NCO/VER6.6) with ESMTP id h9UDHtcV232246
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 30 Oct 2003 08:17:56 -0500
Subject: Re: More on DIT content rules
To: ietf-ldapbis@OpenLDAP.org
X-Mailer: Lotus Notes Release 5.0.12   February 13, 2003
Message-ID: <OF1A48C160.3CEE3D22-ON86256DCF.0047D943-86256DCF.00490D6B@us.ibm.com>
From: John McMeeking <jmcmeek@us.ibm.com>
Date: Thu, 30 Oct 2003 07:17:54 -0600
X-MIMETrack: Serialize by Router on d27ml001/27/M/IBM(Release 6.5|September 18, 2003) at
 10/30/2003 07:17:56 AM
MIME-Version: 1.0
Content-type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by boole.openldap.org id h9UDInHS024355
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 think the equivalent statements from X.501 are:

----------
If no DIT content rule is present for a structural object class, then
entries of that class shall contain only the attributes
permitted by the structural object class definition.

An entry governed by a DIT content rule may, in addition to the structural
object class of the DIT structure rule, be
associated with a subset of the auxiliary object classes identified by the
DIT content rule. This association is reflected in
the entryâ€™s objectClass attribute.
----------

That does seem to say that if there is no DIT content rule, the entry
cannot belong to any auxiliary object classes. And it does seem strange to
me.


John  McMeeking



                                                                                                                       
                      "Jim Sermersheim"                                                                                
                      <jimse@novell.com>          To:       <ietf-ldapbis@OpenLDAP.org>                                
                      Sent by:                    cc:                                                                  
                      owner-ietf-ldapbis@O        Subject:  Re: More on DIT content rules                              
                      penLDAP.org                                                                                      
                                                                                                                       
                                                                                                                       
                      10/29/2003 07:54 PM                                                                              
                                                                                                                       
                                                                                                                       





Actually, what's being documented here has always been true. Most of the
text is being pulled in part or whole (summarized or not) from X.501.
Previously, one had to find these statements by reading hte ITU documents.

Jim

>>> Michael StrĂ¶der <michael@stroeder.com> 10/29/03 10:34:10 AM >>>
HI!

Still browsing through draft-ietf-ldapbis-models-09...

In section 2.4.3 there's written:

[..] If no DIT content rule is associated with
the structural object class of the entry, the entry cannot belong to
any auxiliary object class.

I don't understand this statement. Shouldn't the 'cannot' be 'can'?

From section 4.1.6.:

MUST, MAY, and NOT specify lists of attribute types which are
required, allowed, or precluded, respectively, from appearing in
entries subject to this DIT content rule; and
<extensions> describe extensions.

I'm a little bit scared of 'MUST' and 'MAY' extending the 'MUST' and 'MAY'
of object classes. I consider this being redundant to schema design with
object classes. Personally I'd appreciate a hint in the text stating that
use of 'MUST' and 'MAY' in a DIT content rules is NOT RECOMMENDED since
clients or servers might not support DIT content rules. Well, such a hint
might be a little too much in the direction of a best practice guide.

Ciao, Michael.



From owner-ietf-ldapbis@OpenLDAP.org  Thu Oct 30 09:56: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 JAA24153
	for <ldapbis-archive@lists.ietf.org>; Thu, 30 Oct 2003 09:56:37 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9UErkHW029802;
	Thu, 30 Oct 2003 14:54:21 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9UEoMJw029612;
	Thu, 30 Oct 2003 14:50:22 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 30 Oct 2003 14:50:22 +0000
Received: from prv-mail20.provo.novell.com (prv-mail20.provo.novell.com [137.65.81.122])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9UEoJHS029592
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 30 Oct 2003 14:50:19 GMT
	(envelope-from jimse@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Thu, 30 Oct 2003 07:49:59 -0700
Message-Id: <sfa0c2a7.024@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.2 Beta
Date: Thu, 30 Oct 2003 07:49:37 -0700
From: "Jim Sermersheim" <jimse@novell.com>
To: <ietf-ldapbis@OpenLDAP.org>
Subject: Re: More on DIT content rules
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__PartC29C5111.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>

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.

--=__PartC29C5111.0__=
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Maybe I'm strange, but I like it. It allows server implementations to use =
this mechanism to control and advertise things such as which objects to =
expect what operational attributes to be available.
=20
I don't doubt that as things progress, some implementations will auto-add =
certain DIT content rules to certain types of object classes when they are =
added. As well as perhaps invent other mechanisms that make the addition =
of aux classes more seamless than it would seem on the surface.
=20
Jim

>>> John McMeeking <jmcmeek@us.ibm.com> 10/30/03 6:17:54 AM >>>




I think the equivalent statements from X.501 are:

----------
If no DIT content rule is present for a structural object class, then
entries of that class shall contain only the attributes
permitted by the structural object class definition.

An entry governed by a DIT content rule may, in addition to the structural
object class of the DIT structure rule, be
associated with a subset of the auxiliary object classes identified by the
DIT content rule. This association is reflected in
the entrys objectClass attribute.
----------

That does seem to say that if there is no DIT content rule, the entry
cannot belong to any auxiliary object classes. And it does seem strange to
me.


John McMeeking




"Jim Sermersheim"=20
< jimse@novell.com > To: < ietf-ldapbis@OpenLDAP.org >=20
Sent by: cc:=20
owner-ietf-ldapbis@O Subject: Re: More on DIT content rules=20
penLDAP.org=20


10/29/2003 07:54 PM=20







Actually, what's being documented here has always been true. Most of the
text is being pulled in part or whole (summarized or not) from X.501.
Previously, one had to find these statements by reading hte ITU documents.

Jim

>>> Michael Str=F6der < michael@stroeder.com > 10/29/03 10:34:10 AM >>>
HI!

Still browsing through draft-ietf-ldapbis-models-09...

In section 2.4.3 there's written:

[..] If no DIT content rule is associated with
the structural object class of the entry, the entry cannot belong to
any auxiliary object class.

I don't understand this statement. Shouldn't the 'cannot' be 'can'?

From section 4.1.6.:

MUST, MAY, and NOT specify lists of attribute types which are
required, allowed, or precluded, respectively, from appearing in
entries subject to this DIT content rule; and
<extensions> describe extensions.

I'm a little bit scared of 'MUST' and 'MAY' extending the 'MUST' and 'MAY'
of object classes. I consider this being redundant to schema design with
object classes. Personally I'd appreciate a hint in the text stating that
use of 'MUST' and 'MAY' in a DIT content rules is NOT RECOMMENDED since
clients or servers might not support DIT content rules. Well, such a hint
might be a little too much in the direction of a best practice guide.

Ciao, Michael.




--=__PartC29C5111.0__=
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1"=
>
<META content=3D"MSHTML 5.50.4933.1800" name=3DGENERATOR></HEAD>
<BODY style=3D"MARGIN: 4px 4px 1px; FONT: 10pt Microsoft Sans Serif">
<DIV>Maybe I'm strange, but I like it. It allows server implementations to =
use this mechanism to control and advertise things such as which objects =
to expect what operational attributes to be available.</DIV>
<DIV>&nbsp;</DIV>
<DIV>I don't doubt that as things progress, some implementations will =
auto-add certain DIT content rules to certain types of&nbsp;object classes =
when they are added. As well as perhaps invent other mechanisms that make =
the addition of aux classes more seamless than it would seem on the =
surface.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Jim<BR><BR>&gt;&gt;&gt; John McMeeking &lt;jmcmeek@us.ibm.com&gt; =
10/30/03 6:17:54 AM &gt;&gt;&gt;<BR><BR><BR><BR><BR>I think the equivalent =
statements from X.501 are:<BR><BR>----------<BR>If no DIT content rule is =
present for a structural object class, then<BR>entries of that class shall =
contain only the attributes<BR>permitted by the structural object class =
definition.<BR><BR>An entry governed by a DIT content rule may, in =
addition to the structural<BR>object class of the DIT structure rule, =
be<BR>associated with a subset of the auxiliary object classes identified =
by the<BR>DIT content rule. This association is reflected in<BR>the entrys =
objectClass attribute.<BR>----------<BR><BR>That does seem to say that if =
there is no DIT content rule, the entry<BR>cannot belong to any auxiliary =
object classes. And it does seem strange to<BR>me.<BR><BR><BR>John =
McMeeking<BR><BR><BR><BR><BR>"Jim Sermersheim" <BR>&lt;<U> <A href=3D"mailt=
o:jimse@novell.com">jimse@novell.com</A></U> &gt; To: &lt;<U> <A href=3D"ma=
ilto:ietf-ldapbis@OpenLDAP.org">ietf-ldapbis@OpenLDAP.org</A></U> &gt; =
<BR>Sent by: cc: <BR>owner-ietf-ldapbis@O Subject: Re: More on DIT content =
rules <BR>penLDAP.org <BR><BR><BR>10/29/2003 07:54 PM <BR><BR><BR><BR><BR><=
BR><BR><BR>Actually, what's being documented here has always been true. =
Most of the<BR>text is being pulled in part or whole (summarized or not) =
from X.501.<BR>Previously, one had to find these statements by reading hte =
ITU documents.<BR><BR>Jim<BR><BR>&gt;&gt;&gt; Michael Str=F6der &lt;<U> <A =
href=3D"mailto:michael@stroeder.com">michael@stroeder.com</A></U> &gt; =
10/29/03 10:34:10 AM &gt;&gt;&gt;<BR>HI!<BR><BR>Still browsing through =
draft-ietf-ldapbis-models-09...<BR><BR>In section 2.4.3 there's written:<BR=
><BR>[..] If no DIT content rule is associated with<BR>the structural =
object class of the entry, the entry cannot belong to<BR>any auxiliary =
object class.<BR><BR>I don't understand this statement. Shouldn't the =
'cannot' be 'can'?<BR><BR>From section 4.1.6.:<BR><BR>MUST, MAY, and NOT =
specify lists of attribute types which are<BR>required, allowed, or =
precluded, respectively, from appearing in<BR>entries subject to this DIT =
content rule; and<BR>&lt;extensions&gt; describe extensions.<BR><BR>I'm a =
little bit scared of 'MUST' and 'MAY' extending the 'MUST' and 'MAY'<BR>of =
object classes. I consider this being redundant to schema design with<BR>ob=
ject classes. Personally I'd appreciate a hint in the text stating =
that<BR>use of 'MUST' and 'MAY' in a DIT content rules is NOT RECOMMENDED =
since<BR>clients or servers might not support DIT content rules. Well, =
such a hint<BR>might be a little too much in the direction of a best =
practice guide.<BR><BR>Ciao, Michael.<BR><BR></DIV></BODY></HTML>

--=__PartC29C5111.0__=--


From owner-ietf-ldapbis@OpenLDAP.org  Thu Oct 30 10:21: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 KAA26493
	for <ldapbis-archive@lists.ietf.org>; Thu, 30 Oct 2003 10:21:49 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9UF5kIA030636;
	Thu, 30 Oct 2003 15:17:34 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9UF2kpt030356;
	Thu, 30 Oct 2003 15:02:46 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 30 Oct 2003 15:02:46 +0000
Received: from e5.ny.us.ibm.com (e5.ny.us.ibm.com [32.97.182.105])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9UF2hHS030273
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 30 Oct 2003 15:02:44 GMT
	(envelope-from jongchoi@us.ibm.com)
Received: from northrelay02.pok.ibm.com (northrelay02.pok.ibm.com [9.56.224.150])
	by e5.ny.us.ibm.com (8.12.10/8.12.2) with ESMTP id h9UF2Mn9513022
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 30 Oct 2003 10:02:22 -0500
Received: from d01ml604.pok.ibm.com (d01av02.pok.ibm.com [9.56.224.216])
	by northrelay02.pok.ibm.com (8.12.9/NCO/VER6.6) with ESMTP id h9UF2FcV224264
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 30 Oct 2003 10:02:15 -0500
To: John McMeeking <jmcmeek@us.ibm.com>
Cc: ietf-ldapbis@OpenLDAP.org
MIME-Version: 1.0
Subject: Re: More on DIT content rules
X-Mailer: Lotus Notes Release 5.0.11   July 24, 2002
Message-ID: <OF27793BCE.02620C42-ON85256DCF.0050438A-85256DCF.00528410@us.ibm.com>
From: Jonghyuk Choi <jongchoi@us.ibm.com>
Date: Thu, 30 Oct 2003 10:02:14 -0500
X-MIMETrack: Serialize by Router on D01ML604/01/M/IBM(Release 6.5|September 18, 2003) at
 10/30/2003 10:02:16,
	Serialize complete at 10/30/2003 10:02:16
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 h9UF2iHS030343
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 think the equivalent statements from X.501 are:
>
>----------
>If no DIT content rule is present for a structural object class, then
>entries of that class shall contain only the attributes
>permitted by the structural object class definition.
>
>An entry governed by a DIT content rule may, in addition to the 
structural
>object class of the DIT structure rule, be
>associated with a subset of the auxiliary object classes identified by 
the
>DIT content rule. This association is reflected in
>the entry's objectClass attribute.
>----------
>
>That does seem to say that if there is no DIT content rule, the entry
>cannot belong to any auxiliary object classes. And it does seem strange 
to
>me.

Yes. looks like X.501 requires a DIT content rule to be related with a 
structrual object class,
should an entry of the class be associated with any auxiliary object 
classes.
Is it the intention of the I-D to follow the X.501 model in this respect ?

------------------------
Jong Hyuk Choi
IBM Thomas J. Watson Research Center - Enterprise Linux Group
P. O. Box 218, Yorktown Heights, NY 10598
email: jongchoi@us.ibm.com
(phone) 914-945-3979    (fax) 914-945-4425   TL: 862-3979




From owner-ietf-ldapbis@OpenLDAP.org  Thu Oct 30 11:03: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 LAA28321
	for <ldapbis-archive@lists.ietf.org>; Thu, 30 Oct 2003 11:03:09 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9UFlkIG035121;
	Thu, 30 Oct 2003 15:58:19 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9UFkIaO035078;
	Thu, 30 Oct 2003 15:46:18 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 30 Oct 2003 15:46:18 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9UFkGHS035065
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 30 Oct 2003 15:46:16 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from gypsy.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.9/8.12.9) with ESMTP id h9UFkFlg004740;
	Thu, 30 Oct 2003 15:46:16 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.0.22.0.20031030073104.047790b0@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
Date: Thu, 30 Oct 2003 07:45:29 -0800
To: Jonghyuk Choi <jongchoi@us.ibm.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: More on DIT content rules
Cc: John McMeeking <jmcmeek@us.ibm.com>, ietf-ldapbis@OpenLDAP.org
In-Reply-To: <OF27793BCE.02620C42-ON85256DCF.0050438A-85256DCF.00528410@
 us.ibm.com>
References: <OF27793BCE.02620C42-ON85256DCF.0050438A-85256DCF.00528410@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 07:02 AM 10/30/2003, Jonghyuk Choi wrote:
>Is it the intention of the I-D to follow the X.501 model in this respect ?

The intention of the I-D is, in general, to follow X.500 models.
Some adaption is needed here and there, but that is kept to
a minimum.  Adaption here was not needed.  X.501 model can
be applied to LDAP without adaption and, given that LDAP
TS said that X.500 information models were to be applied, that's
what this draft does.

Kurt  



From owner-ietf-ldapbis@OpenLDAP.org  Thu Oct 30 11:58: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 LAA00554
	for <ldapbis-archive@lists.ietf.org>; Thu, 30 Oct 2003 11:58:42 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9UGrlHW038567;
	Thu, 30 Oct 2003 16:54:17 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9UGmLSE038362;
	Thu, 30 Oct 2003 16:48:21 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 30 Oct 2003 16:48:21 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9UGmIHS038352
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 30 Oct 2003 16:48:18 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from gypsy.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.9/8.12.9) with ESMTP id h9UGmDlg005215;
	Thu, 30 Oct 2003 16:48:13 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.0.22.0.20031030082914.04674e68@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
Date: Thu, 30 Oct 2003 08:47:27 -0800
To: "Jim Sermersheim" <jimse@novell.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: More on DIT content rules
Cc: <ietf-ldapbis@OpenLDAP.org>
In-Reply-To: <sfa0c2a7.024@prv-mail20.provo.novell.com>
References: <sfa0c2a7.024@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 06:49 AM 10/30/2003, Jim Sermersheim wrote:
>I don't doubt that as things progress, some implementations will auto-add certain DIT content rules to certain types of object classes when they are added.

I think some implementators take the view that their servers
have implicit DIT content rules which allow an entry to belong to any
auxiliary class but choose not to publish these rules in the subschema.
I think implementors taking this view should publish their rules
in the subschema so that clients will know which auxiliary classes
may be present in entries they update.

Kurt 



From owner-ietf-ldapbis@OpenLDAP.org  Fri Oct 31 05:28: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 FAA20315
	for <ldapbis-archive@lists.ietf.org>; Fri, 31 Oct 2003 05:28:10 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9VAQUHS095924;
	Fri, 31 Oct 2003 10:26:30 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9p2/8.12.9/Submit) with SMTP id h9VADSZI094908;
	Fri, 31 Oct 2003 10:13:28 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Fri, 31 Oct 2003 10:13:28 +0000
Received: from goliath.siemens.de (goliath.siemens.de [192.35.17.28])
	by boole.openldap.org (8.12.9p2/8.12.9) with ESMTP id h9VADPHS094892
	for <ietf-ldapbis@OpenLDAP.org>; Fri, 31 Oct 2003 10:13:25 GMT
	(envelope-from helmut.volpers@siemens.com)
Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14])
	by goliath.siemens.de (8.11.7/8.11.7) with ESMTP id h9VADNF26067;
	Fri, 31 Oct 2003 11:13:23 +0100 (MET)
Received: from pappel.asw.mchp.siemens.de ([139.25.160.30])
	by mail3.siemens.de (8.11.7/8.11.7) with ESMTP id h9VADLd07012;
	Fri, 31 Oct 2003 11:13:22 +0100 (MET)
Received: by pappel.asw.mchp.siemens.de with Internet Mail Service (5.5.2657.72)
	id <V9874FM9>; Fri, 31 Oct 2003 11:13:20 +0100
Message-ID: <D1533D42A5A9D511A8090050DA3D835784433C@pappel.asw.mchp.siemens.de>
From: "Volpers, Helmut" <helmut.volpers@siemens.com>
To: "'Jim Sermersheim'" <jimse@novell.com>, ietf-ldapbis@OpenLDAP.org
Subject: RE: More on DIT content rules
Date: Fri, 31 Oct 2003 11:13:17 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C39F97.9A9F8710"
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 is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C39F97.9A9F8710
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Jim, I agree with you that it is nice for the server to control which
objects can have which auxiliary ObjectClasses.
It is the same for DITStructureRules, it is a nice thing that the =
server
(administrator) control the tree. We have implemented=20
this since years, but there are a lot of applications which needs the
feature that I can give to a special object
a auxiliary ObjectClass and then I can give a new set of attributes to =
this
entry.
That's the way the most LDAPServers works today.
If you will be more restrictive by stronger schema checks you will =
break
some applications where we hve to
decide whether we want that.
I think we should let it optional whether a server checks against
DitContentRules and DitStructureRules.
=20
Helmut
=20
A lot of products delivers LDIF files for  the schema extensions they =
need
and the most of them only delivers
AttributeTypes and ObjectClasses and it works.

-----Original Message-----
From: Jim Sermersheim [mailto:jimse@novell.com]=20
Sent: Thursday, October 30, 2003 3:50 PM
To: ietf-ldapbis@OpenLDAP.org
Subject: Re: More on DIT content rules


Maybe I'm strange, but I like it. It allows server implementations to =
use
this mechanism to control and advertise things such as which objects to
expect what operational attributes to be available.
=20
I don't doubt that as things progress, some implementations will =
auto-add
certain DIT content rules to certain types of object classes when they =
are
added. As well as perhaps invent other mechanisms that make the =
addition of
aux classes more seamless than it would seem on the surface.
=20
Jim

>>> John McMeeking <jmcmeek@us.ibm.com> 10/30/03 6:17:54 AM >>>




I think the equivalent statements from X.501 are:

----------
If no DIT content rule is present for a structural object class, then
entries of that class shall contain only the attributes
permitted by the structural object class definition.

An entry governed by a DIT content rule may, in addition to the =
structural
object class of the DIT structure rule, be
associated with a subset of the auxiliary object classes identified by =
the
DIT content rule. This association is reflected in
the entrys objectClass attribute.
----------

That does seem to say that if there is no DIT content rule, the entry
cannot belong to any auxiliary object classes. And it does seem strange =
to
me.


John McMeeking




"Jim Sermersheim"=20
< jimse@novell.com <mailto:jimse@novell.com>  > To: <
ietf-ldapbis@OpenLDAP.org <mailto:ietf-ldapbis@OpenLDAP.org>  >=20
Sent by: cc:=20
owner-ietf-ldapbis@O Subject: Re: More on DIT content rules=20
penLDAP.org=20


10/29/2003 07:54 PM=20







Actually, what's being documented here has always been true. Most of =
the
text is being pulled in part or whole (summarized or not) from X.501.
Previously, one had to find these statements by reading hte ITU =
documents.

Jim

>>> Michael Str=F6der < michael@stroeder.com =
<mailto:michael@stroeder.com>  >
10/29/03 10:34:10 AM >>>
HI!

Still browsing through draft-ietf-ldapbis-models-09...

In section 2.4.3 there's written:

[..] If no DIT content rule is associated with
the structural object class of the entry, the entry cannot belong to
any auxiliary object class.

I don't understand this statement. Shouldn't the 'cannot' be 'can'?

From section 4.1.6.:

MUST, MAY, and NOT specify lists of attribute types which are
required, allowed, or precluded, respectively, from appearing in
entries subject to this DIT content rule; and
<extensions> describe extensions.

I'm a little bit scared of 'MUST' and 'MAY' extending the 'MUST' and =
'MAY'
of object classes. I consider this being redundant to schema design =
with
object classes. Personally I'd appreciate a hint in the text stating =
that
use of 'MUST' and 'MAY' in a DIT content rules is NOT RECOMMENDED since
clients or servers might not support DIT content rules. Well, such a =
hint
might be a little too much in the direction of a best practice guide.

Ciao, Michael.




------_=_NextPart_001_01C39F97.9A9F8710
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>Message</TITLE>

<META content="MSHTML 6.00.2800.1264" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Microsoft Sans Serif">
<DIV><SPAN class=705090210-31102003>Jim, I agree with you that it is nice for 
the server to control which objects can have which auxiliary 
ObjectClasses.</SPAN></DIV>
<DIV><SPAN class=705090210-31102003>It is the same for DITStructureRules, it is 
a nice thing that the server (administrator) control the tree. We have 
implemented </SPAN></DIV>
<DIV><SPAN class=705090210-31102003>this since years, but there are a lot of 
applications which needs the feature that I can give to a special 
object</SPAN></DIV>
<DIV><SPAN class=705090210-31102003>a auxiliary ObjectClass and then I can give 
a new set of attributes to this entry.</SPAN></DIV>
<DIV><SPAN class=705090210-31102003>That's the way the most LDAPServers works 
today.</SPAN></DIV>
<DIV><SPAN class=705090210-31102003>If you will be more restrictive by stronger 
schema checks you will break some applications where we hve to</SPAN></DIV>
<DIV><SPAN class=705090210-31102003>decide whether we want that.</SPAN></DIV>
<DIV><SPAN class=705090210-31102003>I think we should let it optional whether a 
server checks against DitContentRules and DitStructureRules.</SPAN></DIV>
<DIV><SPAN class=705090210-31102003></SPAN>&nbsp;</DIV>
<DIV><SPAN class=705090210-31102003>Helmut</SPAN></DIV>
<DIV><SPAN class=705090210-31102003></SPAN>&nbsp;</DIV>
<DIV><SPAN class=705090210-31102003>A lot of products delivers LDIF files 
for&nbsp; the schema extensions they need and the most of them only 
delivers</SPAN></DIV>
<DIV><SPAN class=705090210-31102003>AttributeTypes and ObjectClasses and it 
works.</SPAN></DIV>
<BLOCKQUOTE dir=ltr 
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV></DIV>
  <DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT 
  face=Tahoma>-----Original Message-----<BR><B>From:</B> Jim Sermersheim 
  [mailto:jimse@novell.com] <BR><B>Sent:</B> Thursday, October 30, 2003 3:50 
  PM<BR><B>To:</B> ietf-ldapbis@OpenLDAP.org<BR><B>Subject:</B> Re: More on DIT 
  content rules<BR><BR></FONT></DIV>
  <DIV>Maybe I'm strange, but I like it. It allows server implementations to use 
  this mechanism to control and advertise things such as which objects to expect 
  what operational attributes to be available.</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>I don't doubt that as things progress, some implementations will auto-add 
  certain DIT content rules to certain types of&nbsp;object classes when they 
  are added. As well as perhaps invent other mechanisms that make the addition 
  of aux classes more seamless than it would seem on the surface.</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>Jim<BR><BR>&gt;&gt;&gt; John McMeeking &lt;jmcmeek@us.ibm.com&gt; 
  10/30/03 6:17:54 AM &gt;&gt;&gt;<BR><BR><BR><BR><BR>I think the equivalent 
  statements from X.501 are:<BR><BR>----------<BR>If no DIT content rule is 
  present for a structural object class, then<BR>entries of that class shall 
  contain only the attributes<BR>permitted by the structural object class 
  definition.<BR><BR>An entry governed by a DIT content rule may, in addition to 
  the structural<BR>object class of the DIT structure rule, be<BR>associated 
  with a subset of the auxiliary object classes identified by the<BR>DIT content 
  rule. This association is reflected in<BR>the entrys objectClass 
  attribute.<BR>----------<BR><BR>That does seem to say that if there is no DIT 
  content rule, the entry<BR>cannot belong to any auxiliary object classes. And 
  it does seem strange to<BR>me.<BR><BR><BR>John 
  McMeeking<BR><BR><BR><BR><BR>"Jim Sermersheim" <BR>&lt;<U> <A 
  href="mailto:jimse@novell.com">jimse@novell.com</A></U> &gt; To: &lt;<U> <A 
  href="mailto:ietf-ldapbis@OpenLDAP.org">ietf-ldapbis@OpenLDAP.org</A></U> &gt; 
  <BR>Sent by: cc: <BR>owner-ietf-ldapbis@O Subject: Re: More on DIT content 
  rules <BR>penLDAP.org <BR><BR><BR>10/29/2003 07:54 PM 
  <BR><BR><BR><BR><BR><BR><BR><BR>Actually, what's being documented here has 
  always been true. Most of the<BR>text is being pulled in part or whole 
  (summarized or not) from X.501.<BR>Previously, one had to find these 
  statements by reading hte ITU documents.<BR><BR>Jim<BR><BR>&gt;&gt;&gt; 
  Michael Ströder &lt;<U> <A 
  href="mailto:michael@stroeder.com">michael@stroeder.com</A></U> &gt; 10/29/03 
  10:34:10 AM &gt;&gt;&gt;<BR>HI!<BR><BR>Still browsing through 
  draft-ietf-ldapbis-models-09...<BR><BR>In section 2.4.3 there's 
  written:<BR><BR>[..] If no DIT content rule is associated with<BR>the 
  structural object class of the entry, the entry cannot belong to<BR>any 
  auxiliary object class.<BR><BR>I don't understand this statement. Shouldn't 
  the 'cannot' be 'can'?<BR><BR>From section 4.1.6.:<BR><BR>MUST, MAY, and NOT 
  specify lists of attribute types which are<BR>required, allowed, or precluded, 
  respectively, from appearing in<BR>entries subject to this DIT content rule; 
  and<BR>&lt;extensions&gt; describe extensions.<BR><BR>I'm a little bit scared 
  of 'MUST' and 'MAY' extending the 'MUST' and 'MAY'<BR>of object classes. I 
  consider this being redundant to schema design with<BR>object classes. 
  Personally I'd appreciate a hint in the text stating that<BR>use of 'MUST' and 
  'MAY' in a DIT content rules is NOT RECOMMENDED since<BR>clients or servers 
  might not support DIT content rules. Well, such a hint<BR>might be a little 
  too much in the direction of a best practice guide.<BR><BR>Ciao, 
  Michael.<BR><BR></DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C39F97.9A9F8710--


