From owner-ietf-ldapbis@OpenLDAP.org  Mon Feb  2 14:46:12 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04818
	for <ldapbis-archive@lists.ietf.org>; Mon, 2 Feb 2004 14:46:11 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i12JhK5t096184;
	Mon, 2 Feb 2004 19:44:15 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i12JbRnh096010;
	Mon, 2 Feb 2004 19:37: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); Mon, 2 Feb 2004 19:37:27 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i12JbQ5r096000
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 2 Feb 2004 19:37:26 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from gypsy.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.10/8.12.10) with ESMTP id i12JbQ7s037168
	for <ietf-ldapbis@openldap.org>; Mon, 2 Feb 2004 19:37:26 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.1.1.0.20040202112737.02ba0a78@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Mon, 02 Feb 2004 11:37:14 -0800
To: ietf-ldapbis@OpenLDAP.org
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: LDAPBIS @ IETF#59
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 we had hoped we would wrap up the revised LDAP
TS by now, we obviously have a bit more work to do.
As such, I have requested a 1-hr slot for IETF#59 to
discuss the remaining outstanding issues and next steps.

Regards, Kurt



From owner-ietf-ldapbis@OpenLDAP.org  Mon Feb  9 15:50:36 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10712
	for <ldapbis-archive@lists.ietf.org>; Mon, 9 Feb 2004 15:50:35 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i19Kic5t037074;
	Mon, 9 Feb 2004 20:49:18 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i19KhkkU037027;
	Mon, 9 Feb 2004 20:43: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); Mon, 9 Feb 2004 20:43:46 +0000
Received: from pat.uio.no (IDENT:7411@pat.uio.no [129.240.130.16])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i19Khh5r036992;
	Mon, 9 Feb 2004 20:43:43 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 1AqIFl-0005ND-IB; Mon, 09 Feb 2004 21:43:37 +0100
Received: from bombur.uio.no ([129.240.186.42])
	by mail-mx3.uio.no with esmtp (Exim 4.14)
	id 1AqIFh-00082f-95; Mon, 09 Feb 2004 21:43:33 +0100
Received: from hbf by bombur.uio.no with local (Exim 2.12 #7)
	id 1AqIFg-0004uB-00; Mon, 9 Feb 2004 21:43:32 +0100
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Message-Id: <HBF.20040209qjvn@bombur.uio.no>
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>, steven.legg@adacel.com.au
Cc: ietf-ldapbis@OpenLDAP.org
Subject: Re: strange uniqueMemberMatch
In-Reply-To: <5.2.0.9.0.20030108110558.02312c88@127.0.0.1>
References: <HBF.20030104hp76@bombur.uio.no>
	<00ee01c2b53d$20d2beb0$a518200a@osmium.mtwav.adacel.com.au>
	<5.2.0.9.0.20030108110558.02312c88@127.0.0.1>
Date: Mon, 9 Feb 2004 21:43:32 +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
X-UiO-Spam-info: not spam, SpamAssassin (score=0, required 12)
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

Any progress with this?  It's been a year now.  I asked before, but
I don't think anyone answered.

http://www.OpenLDAP.org/lists/ietf-ldapbis/200301/msg00027.html
http://www.OpenLDAP.org/lists/ietf-ldapbis/200301/msg00029.html

At 08 Jan 2003, Kurt D. Zeilenga wrote:
>At 08:36 PM 1/5/2003, Steven Legg wrote:
>> The uniqueMemberMatch rule is an equality matching rule that is not
>> commutative, which causes problems in deciding whether attribute values
>> are equal or not when adding or deleting values. I've raised this with
>> the X.500 working group and I'm waiting to see how they resolve it.
>
> We likely should nudge them on this.  The current
> definition is, I think, problematic because uniqueMember
> is not single-valued.

-- 
Hallvard


From owner-ietf-ldapbis@OpenLDAP.org  Mon Feb  9 15:55:21 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10937
	for <ldapbis-archive@lists.ietf.org>; Mon, 9 Feb 2004 15:55:20 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i19Ko85t037498;
	Mon, 9 Feb 2004 20:53:54 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i19KjI8I037148;
	Mon, 9 Feb 2004 20:45: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); Mon, 9 Feb 2004 20:45:18 +0000
Received: from pat.uio.no (IDENT:7411@pat.uio.no [129.240.130.16])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i19KjH5r037129
	for <ietf-ldapbis@openldap.org>; Mon, 9 Feb 2004 20:45:17 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 1AqIHJ-0005eq-Ia
	for ietf-ldapbis@openldap.org; Mon, 09 Feb 2004 21:45:13 +0100
Received: from bombur.uio.no ([129.240.186.42])
	by mail-mx6.uio.no with esmtp (Exim 4.14)
	id 1AqIHH-0002Ge-Vp; Mon, 09 Feb 2004 21:45:11 +0100
Received: from hbf by bombur.uio.no with local (Exim 2.12 #7)
	id 1AqIHH-0004uq-00; Mon, 9 Feb 2004 21:45:11 +0100
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Message-Id: <HBF.20040209qivi@bombur.uio.no>
To: ietf-ldapbis@OpenLDAP.org
Subject: DN draft and X.500
Date: Mon, 9 Feb 2004 21:45:11 +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
X-UiO-Spam-info: not spam, SpamAssassin (score=0, required 12)
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

draft-ietf-ldapbis-dn-12.txt says:

> 1.  Background and Intended Usage

>   The structure of a DN [X.501] is described in terms of ASN.1 [X.680].

Only X.500 DNs.  LDAP DNs are not, and that's the important ones in
an LDAP draft.

>   This specification assumes familiarity with X.500 [X.500], and the
>   concept of Distinguished Name [X.501][Models].

No, familiarity with Sections 1-2 of [Models] is sufficient - at least
for a reader who just implements LDAP.  If he implements a gateway
to/from X.500, he'll need to know the ASN.1 of various syntaxes too, but
he needs the references in [Syntaxes] for that, not the rest of
[Models].
We do need to know the ASN.1 of DNs and RDNs from X.500, but the ASN.1
in section 2 of this draft seems to be enough for that.

-- 
Hallvard


From owner-ietf-ldapbis@OpenLDAP.org  Mon Feb  9 16:24:13 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14230
	for <ldapbis-archive@lists.ietf.org>; Mon, 9 Feb 2004 16:24:12 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i19LK95t039693;
	Mon, 9 Feb 2004 21:22:22 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i19LEfA7039099;
	Mon, 9 Feb 2004 21:14: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); Mon, 9 Feb 2004 21:14:41 +0000
Received: from pat.uio.no (IDENT:7411@pat.uio.no [129.240.130.16])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i19LEe5r039077
	for <ietf-ldapbis@openldap.org>; Mon, 9 Feb 2004 21:14:40 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 1AqIjj-0001zJ-HX
	for ietf-ldapbis@openldap.org; Mon, 09 Feb 2004 22:14:35 +0100
Received: from bombur.uio.no ([129.240.186.42])
	by mail-mx1.uio.no with esmtp (Exim 4.14)
	id 1AqIjg-0008Or-7D; Mon, 09 Feb 2004 22:14:32 +0100
Received: from hbf by bombur.uio.no with local (Exim 2.12 #7)
	id 1AqIjf-0004zK-00; Mon, 9 Feb 2004 22:14:31 +0100
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Message-Id: <HBF.20040209q17w@bombur.uio.no>
To: ietf-ldapbis@OpenLDAP.org
Subject: protocol: data hiding
Date: Mon, 9 Feb 2004 22:14:31 +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
X-UiO-Spam-info: not spam, SpamAssassin (score=0, required 12)
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

A Security Consideration like this might be a good idea:

   The matchedDN and diagnosticMessage fields and some result
   codes (such as insufficientAccessRights, attributeOrValueExists
   and entryAlreadyExists) may reveal the presence of specific
   data in the directory.  If access controls prohibit this, the
   server must take care to instead act as if the data are not
   present, or when that is not possible, to return a less
   informative result code.

-- 
Hallvard


From owner-ietf-ldapbis@OpenLDAP.org  Mon Feb  9 17:21:29 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22438
	for <ldapbis-archive@lists.ietf.org>; Mon, 9 Feb 2004 17:21:29 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i19MKJ5t043294;
	Mon, 9 Feb 2004 22:20:27 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i19MF3bQ043060;
	Mon, 9 Feb 2004 22:15:03 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, 9 Feb 2004 22:15:03 +0000
Received: from prv-mail20.provo.novell.com (prv-mail20.provo.novell.com [137.65.81.122])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i19MF25r043031
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 9 Feb 2004 22:15:02 GMT
	(envelope-from jimse@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Mon, 09 Feb 2004 15:14:41 -0700
Message-Id: <s027a3e1.047@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.2 Beta
Date: Mon, 09 Feb 2004 15:14:27 -0700
From: "Jim Sermersheim" <jimse@novell.com>
To: <ietf-ldapbis@OpenLDAP.org>, <h.b.furuseth@usit.uio.no>
Subject: Re: protocol: data hiding
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__Part55743053.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.

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

I like the notion of bringing this to the reader's attention, but I
dislike prescribing specific actions. How about something more like:
 
The matchedDN and diagnosticMessage fields and some result codes (such
as insufficientAccessRights, attributeOrValueExists and
entryAlreadyExists) may disclose the presence of specific data in the
directory. Access controls coupled with restrictive policies can be used
to protect against such disclosure.
 
Jim

>>> Hallvard B Furuseth <h.b.furuseth@usit.uio.no> 2/9/04 2:14:31 PM
>>>
A Security Consideration like this might be a good idea:

The matchedDN and diagnosticMessage fields and some result
codes (such as insufficientAccessRights, attributeOrValueExists
and entryAlreadyExists) may reveal the presence of specific
data in the directory. If access controls prohibit this, the
server must take care to instead act as if the data are not
present, or when that is not possible, to return a less
informative result code.

-- 
Hallvard


--=__Part55743053.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 6.00.2800.1400" name=3DGENERATOR></HEAD>
<BODY style=3D"MARGIN: 4px 4px 1px; FONT: 10pt Microsoft Sans Serif">
<DIV>I like the notion of bringing this to the reader's attention, but I =
dislike prescribing specific actions. How about something more like:</DIV>
<DIV>&nbsp;</DIV>
<DIV>The matchedDN and diagnosticMessage fields and some result codes =
(such as insufficientAccessRights, attributeOrValueExists and entryAlreadyE=
xists) may disclose the presence of specific data in the directory. Access =
controls coupled with restrictive policies can be used to protect against =
such disclosure.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Jim<BR><BR>&gt;&gt;&gt; Hallvard B Furuseth &lt;h.b.furuseth@usit.uio.=
no&gt; 2/9/04 2:14:31 PM &gt;&gt;&gt;<BR>A Security Consideration like =
this might be a good idea:<BR><BR>The matchedDN and diagnosticMessage =
fields and some result<BR>codes (such as insufficientAccessRights, =
attributeOrValueExists<BR>and entryAlreadyExists) may reveal the presence =
of specific<BR>data in the directory. If access controls prohibit this, =
the<BR>server must take care to instead act as if the data are not<BR>prese=
nt, or when that is not possible, to return a less<BR>informative result =
code.<BR><BR>-- <BR>Hallvard<BR></DIV></BODY></HTML>

--=__Part55743053.0__=--


From owner-ietf-ldapbis@OpenLDAP.org  Mon Feb  9 17:57:06 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26262
	for <ldapbis-archive@lists.ietf.org>; Mon, 9 Feb 2004 17:57:06 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i19MuB5t045567;
	Mon, 9 Feb 2004 22:56:18 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i19Mrk2C045422;
	Mon, 9 Feb 2004 22:53: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); Mon, 9 Feb 2004 22:53:46 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i19Mrj5r045412
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 9 Feb 2004 22:53:45 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from gypsy.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.10/8.12.10) with ESMTP id i19Mql7s066752;
	Mon, 9 Feb 2004 22:52:47 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.1.1.0.20040209144227.04cfb570@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Mon, 09 Feb 2004 14:52:31 -0800
To: "Jim Sermersheim" <jimse@novell.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: protocol: data hiding
Cc: <ietf-ldapbis@OpenLDAP.org>, <h.b.furuseth@usit.uio.no>
In-Reply-To: <s027a3e1.047@prv-mail20.provo.novell.com>
References: <s027a3e1.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 02:14 PM 2/9/2004, Jim Sermersheim wrote:
>I like the notion of bringing this to the reader's attention, but I dislike prescribing specific actions. How about something more like:
> 
>The matchedDN and diagnosticMessage fields and some result codes (such as insufficientAccessRights, attributeOrValueExists and entryAlreadyExists) may disclose the presence of specific data in the directory. Access controls coupled with restrictive policies can be used to protect against such disclosure.

I rather word the consideration to the implementor not the
user.
        The matchedDN and diagnosticMessage fields, as well as some
        resultCode values (e.g., attributeOrValueExists and
        entryAlreadyExists), could disclose the presence the
        specific data in the directory where not subjected to
        access and other administrative controls.  Server
        implementators should provide access control mechanisms
        which not only restrict access to information under both
        normal but also under error conditions.


Kurt


> 
>Jim
>
>>>> Hallvard B Furuseth <h.b.furuseth@usit.uio.no> 2/9/04 2:14:31 PM >>>
>A Security Consideration like this might be a good idea:
>
>The matchedDN and diagnosticMessage fields and some result
>codes (such as insufficientAccessRights, attributeOrValueExists
>and entryAlreadyExists) may reveal the presence of specific
>data in the directory. If access controls prohibit this, the
>server must take care to instead act as if the data are not
>present, or when that is not possible, to return a less
>informative result code.
>
>-- 
>Hallvard



From owner-ietf-ldapbis@OpenLDAP.org  Tue Feb 10 18:45:58 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00455
	for <ldapbis-archive@lists.ietf.org>; Tue, 10 Feb 2004 18:45:58 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1ANiU5t042953;
	Tue, 10 Feb 2004 23:45:00 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1ANftGp042837;
	Tue, 10 Feb 2004 23:41: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, 10 Feb 2004 23:41:55 +0000
Received: from smtp-mclean.mitre.org (smtp-mclean-x.mitre.org [192.80.55.71])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1ANfr5r042806;
	Tue, 10 Feb 2004 23:41:53 GMT
	(envelope-from kdally@mitre.org)
Received: from smtp-mclean.mitre.org (localhost.localdomain [127.0.0.1])
	by smtp-mclean.mitre.org (8.11.6/8.11.6) with ESMTP id i1ANfqb04442;
	Tue, 10 Feb 2004 18:41:52 -0500
Received: from MAILHUB1 (mailhub1.mitre.org [129.83.20.31])
	by smtp-mclean.mitre.org (8.11.6/8.11.6) with ESMTP id i1ANfqD04424;
	Tue, 10 Feb 2004 18:41:52 -0500
Received: from mm108631-pc.mitre.org (128.29.3.34) by mailhub1.mitre.org with SMTP
        id 6069519; Tue, 10 Feb 2004 18:41:49 -0500
Message-ID: <40296C3C.C1D602A2@mitre.org>
Date: Tue, 10 Feb 2004 18:41:48 -0500
From: Kathleen Dally <kdally@mitre.org>
Organization: The MITRE Corporation
X-Mailer: Mozilla 4.79 [en]C-20020130M  (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Kurt@OpenLDAP.org, IETF-LDAPbis@OpenLDAP.org
Subject: SUBCLASSING, again
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hi All!

Here is an example of a structural object class that subclasses both one
structural object class and one auxiliary object class.  I believe this
is an important capability, so that a new structural object class can be
defined by augmenting another.  Using a content rule to add the
auxiliary to the original class is not always possible because of
needing two distinct types of entries.  In the example, there may be
entries with applicationEntity as the structural class and other entries
with mLAgent as the structural class.

    ( 2.16.840.1.101.2.2.3.64 NAME 'mLAgent'
          SUP ( 2.5.6.12 $
                    2.5.6.21  )
      MAY 2.5.4.52 )
            ; 2.5.6.12 = applicationEntity
            ; 2.5.6.21 = pkiUser, an auxiliary object class
            ; 2.5.4.52 = supportedAlgorithms

My problem is that this important case appears to be precluded by the
statement in Models-09, 2.4.2:
        "Structural object classes cannot subclass auxiliary object
classes."
What am I missing?

Thanks,
Kathy Dally




From owner-ietf-ldapbis@OpenLDAP.org  Wed Feb 11 11:39:51 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08649
	for <ldapbis-archive@lists.ietf.org>; Wed, 11 Feb 2004 11:39:49 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1BGcN5v009447;
	Wed, 11 Feb 2004 16:38:52 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1BGaHXn009314;
	Wed, 11 Feb 2004 16:36: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, 11 Feb 2004 16:36:17 +0000
Received: from e3.ny.us.ibm.com (e3.ny.us.ibm.com [32.97.182.103])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1BGaC5r009248
	for <IETF-LDAPbis@OpenLDAP.org>; Wed, 11 Feb 2004 16:36:16 GMT
	(envelope-from jmcmeek@us.ibm.com)
Received: from northrelay02.pok.ibm.com (northrelay02.pok.ibm.com [9.56.224.150])
	by e3.ny.us.ibm.com (8.12.10/8.12.2) with ESMTP id i1BGZptB463938
	for <IETF-LDAPbis@OpenLDAP.org>; Wed, 11 Feb 2004 11:35:51 -0500
Received: from d27ml001.rchland.ibm.com (d01av02.pok.ibm.com [9.56.224.216])
	by northrelay02.pok.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id i1BGZo2R115362
	for <IETF-LDAPbis@OpenLDAP.org>; Wed, 11 Feb 2004 11:35:51 -0500
In-Reply-To: <40296C3C.C1D602A2@mitre.org>
Subject: Re: SUBCLASSING, again
To: IETF-LDAPbis@OpenLDAP.org
X-Mailer: Lotus Notes Release 6.0.2CF1 June 9, 2003
Message-ID: <OF884CF79D.C61640E0-ON86256E37.00585FD0-86256E37.005B2BC2@us.ibm.com>
From: John McMeeking <jmcmeek@us.ibm.com>
Date: Wed, 11 Feb 2004 10:35:48 -0600
X-MIMETrack: Serialize by Router on d27ml001/27/M/IBM(Release 6.5|September 18, 2003) at
 02/11/2004 10:35:50 AM
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 don't know where this restriction came from.  I haven't found it (yet?)
in the original V3 RFCs.

X.501 has one restriction on subclassing: only an abstract class can be a
superclass of another abstract class.  An auxiliary class subclassing a
structural class could introduce problems -- entries would likely have more
than one most subordinate structural class.  But structural classes
subclassing auxiliary classes seems like it should be okay.  If someone
were to try to remove the auxiliary class from an entry, the server would
have to verify that the auxiliary class wasn't subclassed by any of the
remaining objectclasses.  That doesn't seem too hard.


John  McMeeking


owner-ietf-ldapbis@OpenLDAP.org wrote on 02/10/2004 05:41:48 PM:

> Hi All!
>
> Here is an example of a structural object class that subclasses both one
> structural object class and one auxiliary object class.  I believe this
> is an important capability, so that a new structural object class can be
> defined by augmenting another.  Using a content rule to add the
> auxiliary to the original class is not always possible because of
> needing two distinct types of entries.  In the example, there may be
> entries with applicationEntity as the structural class and other entries
> with mLAgent as the structural class.
>
>     ( 2.16.840.1.101.2.2.3.64 NAME 'mLAgent'
>           SUP ( 2.5.6.12 $
>                     2.5.6.21  )
>       MAY 2.5.4.52 )
>             ; 2.5.6.12 = applicationEntity
>             ; 2.5.6.21 = pkiUser, an auxiliary object class
>             ; 2.5.4.52 = supportedAlgorithms
>
> My problem is that this important case appears to be precluded by the
> statement in Models-09, 2.4.2:
>         "Structural object classes cannot subclass auxiliary object
> classes."
> What am I missing?
>
> Thanks,
> Kathy Dally
>
>



From owner-ietf-ldapbis@OpenLDAP.org  Wed Feb 11 13:39:30 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12998
	for <ldapbis-archive@lists.ietf.org>; Wed, 11 Feb 2004 13:39:30 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1BIcN5v019161;
	Wed, 11 Feb 2004 18:38:34 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1BIZxDj018975;
	Wed, 11 Feb 2004 18:35: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, 11 Feb 2004 18:35:59 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1BIZx5r018965
	for <IETF-LDAPbis@OpenLDAP.org>; Wed, 11 Feb 2004 18:35:59 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from gypsy.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.10/8.12.10) with ESMTP id i1BIZu7s002630;
	Wed, 11 Feb 2004 18:35:56 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.1.1.0.20040210160558.0498e488@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Tue, 10 Feb 2004 20:41:13 -0800
To: Kathleen Dally <kdally@mitre.org>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: SUBCLASSING, again
Cc: IETF-LDAPbis@OpenLDAP.org
In-Reply-To: <40296C3C.C1D602A2@mitre.org>
References: <40296C3C.C1D602A2@mitre.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>

I note that this topic was discussed early last year in this
thread:
  http://www.openldap.org/lists/ietf-ldapbis/200301/msg00057.html

which was summarized (post WG Last Call) in item 5 of this post:
  http://www.openldap.org/lists/ietf-ldapbis/200302/msg00017.html

as follows:
  It was noted that Section 2.4.2 and 2.4.3 includes restrictions
  up subclassing not explicitly stated in X.501.  The author
  considers the lack of such statements in X.501 as a technical
  omission as such subclassing makes little sense.  No action.

It's my opinion (as Editor, not chair) that, in absence of a new
significant issue, we should consider this item closed.

However, to try to answer your "What am I missing?" question,
here is a little more detail.

While X.501 did not explicitly stated these restrictions, it
did imply them.  For instance, by the text:
  An object class (a subclass) may be derived from an object
  class (its direct superclass) which is itself derived from
  an even more generic object class.

(consider what "more generic" implies here).  However,
more directly implied because, without them, the specification
object class model and DIT content rules would make little sense.

For instance, it is quite clear in X.501 that which auxiliary
classes an entry can belongs to is controlled solely by the
DIT Content Rule.  However, the entry's structural object
class has a auxiliary super class, then the entry belong to
that auxiliary class even when the DIT content rule disallows
it from belong to that auxiliary class.

Kurt



From owner-ietf-ldapbis@OpenLDAP.org  Wed Feb 11 14:16:39 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15371
	for <ldapbis-archive@lists.ietf.org>; Wed, 11 Feb 2004 14:16:38 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1BJ2O6d020988;
	Wed, 11 Feb 2004 19:15:47 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1BIsDUw020354;
	Wed, 11 Feb 2004 18:54: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); Wed, 11 Feb 2004 18:54:13 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1BIsC5r020342
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 11 Feb 2004 18:54:12 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from gypsy.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.10/8.12.10) with ESMTP id i1BIsB7s002881;
	Wed, 11 Feb 2004 18:54:12 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.1.1.0.20040211104611.04903810@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Wed, 11 Feb 2004 10:53:52 -0800
To: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: DN draft and X.500
Cc: ietf-ldapbis@OpenLDAP.org
In-Reply-To: <HBF.20040209qivi@bombur.uio.no>
References: <HBF.20040209qivi@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 12:45 PM 2/9/2004, Hallvard B Furuseth wrote:
>draft-ietf-ldapbis-dn-12.txt says:
>
>> 1.  Background and Intended Usage
>>   The structure of a DN [X.501] is described in terms of ASN.1 [X.680].
>
>Only X.500 DNs.  LDAP DNs are not, and that's the important ones in
>an LDAP draft.

This document does not define the structure of a X.500/LDAP DN,
X.501 does.  (LDAP is defined in terms of X.500 as an X.500 access
mechanism.)  This sentence is correct.

>>   This specification assumes familiarity with X.500 [X.500], and the
>>   concept of Distinguished Name [X.501][Models].
>
>No,

Disagree.  This specification, in fact the whole LDAP TS, assumes
familiarity with X.500.  (LDAP is defined in terms of X.500 as an
X.500 access mechanism.)

>familiarity with Sections 1-2 of [Models] is sufficient - at least
>for a reader who just implements LDAP.

[Models] provides an overview of the data model defined in X.501.
It is quite appropriate to reference both here.

>If he implements a gateway
>to/from X.500, he'll need to know the ASN.1 of various syntaxes too, but
>he needs the references in [Syntaxes] for that, not the rest of
>[Models].
>We do need to know the ASN.1 of DNs and RDNs from X.500, but the ASN.1
>in section 2 of this draft seems to be enough for that.

The section 2 provides a variant ASN.1 for discussion purposes.
To fully understand some aspects of DNs, reading of X.501 may
be necessary, including understanding the definitive DN ASN.1
it provides.

Kurt 



From owner-ietf-ldapbis@OpenLDAP.org  Wed Feb 11 17:30:50 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04270
	for <ldapbis-archive@lists.ietf.org>; Wed, 11 Feb 2004 17:30:49 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1BMIP6L040600;
	Wed, 11 Feb 2004 22:30:01 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1BLsKxe038096;
	Wed, 11 Feb 2004 21:54: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, 11 Feb 2004 21:54:20 +0000
Received: from pat.uio.no (IDENT:7411@pat.uio.no [129.240.130.16])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1BLsH5r038037;
	Wed, 11 Feb 2004 21:54:18 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 1Ar2JB-0005Vo-Uw; Wed, 11 Feb 2004 22:54:13 +0100
Received: from bombur.uio.no ([129.240.186.42])
	by mail-mx1.uio.no with esmtp (Exim 4.14)
	id 1Ar2J8-0006Sz-0q; Wed, 11 Feb 2004 22:54:10 +0100
Received: from hbf by bombur.uio.no with local (Exim 2.12 #7)
	id 1Ar2J7-0004Ov-00; Wed, 11 Feb 2004 22:54:09 +0100
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Message-Id: <HBF.20040211o9k9@bombur.uio.no>
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Cc: Kathleen Dally <kdally@mitre.org>, IETF-LDAPbis@OpenLDAP.org
Subject: Re: SUBCLASSING, again
In-Reply-To: <6.0.1.1.0.20040210160558.0498e488@127.0.0.1>
References: <40296C3C.C1D602A2@mitre.org>
	<6.0.1.1.0.20040210160558.0498e488@127.0.0.1>
X-Mailer: VM 6.37 under Emacs 19.34.1
Date: Wed, 11 Feb 2004 22:54:09 +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
X-UiO-Spam-info: not spam, SpamAssassin (score=0, required 12)
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.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:
> For instance, it is quite clear in X.501 that which auxiliary
> classes an entry can belongs to is controlled solely by the
> DIT Content Rule.  However, the entry's structural object
> class has a auxiliary super class, then the entry belong to
> that auxiliary class even when the DIT content rule disallows
> it from belong to that auxiliary class.

I guess that would mean that an entry of that structural object class
cannot be created unless a DIT content rule allows the auxiliary class.

-- 
Hallvard


From owner-ietf-ldapbis@OpenLDAP.org  Wed Feb 11 18:18:15 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04271
	for <ldapbis-archive@lists.ietf.org>; Wed, 11 Feb 2004 17:30:49 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1BMTt6n042144;
	Wed, 11 Feb 2004 22:30:09 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1BM5YPO039474;
	Wed, 11 Feb 2004 22:05:34 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, 11 Feb 2004 22:05:34 +0000
Received: from pat.uio.no (IDENT:7411@pat.uio.no [129.240.130.16])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1BM5W5r039442;
	Wed, 11 Feb 2004 22:05:32 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 1Ar2U5-0006rV-20; Wed, 11 Feb 2004 23:05:29 +0100
Received: from bombur.uio.no ([129.240.186.42])
	by mail-mx1.uio.no with esmtp (Exim 4.14)
	id 1Ar2U2-0000nS-RZ; Wed, 11 Feb 2004 23:05:26 +0100
Received: from hbf by bombur.uio.no with local (Exim 2.12 #7)
	id 1Ar2U2-0004QL-00; Wed, 11 Feb 2004 23:05:26 +0100
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Message-Id: <HBF.20040211o2rr@bombur.uio.no>
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>, Jim Sermersheim <jimse@novell.com>
Cc: ietf-ldapbis@OpenLDAP.org
Subject: Re: protocol: data hiding
In-Reply-To: <6.0.1.1.0.20040209144227.04cfb570@127.0.0.1>
References: <s027a3e1.047@prv-mail20.provo.novell.com>
	<6.0.1.1.0.20040209144227.04cfb570@127.0.0.1>
X-Mailer: VM 6.37 under Emacs 19.34.1
Date: Wed, 11 Feb 2004 23:05:26 +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
X-UiO-Spam-info: not spam, SpamAssassin (score=0, required 12)
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

Jim Sermersheim wrote:

> I like the notion of bringing this to the reader's attention, but I
> dislike prescribing specific actions. How about something more like:

For diagnosticMessage, I agree.

Not sure about matchedDN.  The options I can think of are to act as if
the entry is not there, or to not return a matchedDN at all.  However,
with the latter behaviour, a user who knows the server well can
sometimes deduce that an expected but missing matchedDN indicates a
hidden entry.  So I think the text should at least mention that data
is best hidden by pretending it is not there.

As for the result code, I would like the text to at least suggest that
one may return a less informative result code.  Otherwise it may not be
clear to an implementor what he can do when some revealing result code
should normally be returned.  Since I can't think of any other option, I
don't really care is that is stated as a suggestion or a mandate.

Also,

Kurt D. Zeilenga wrote:

>         The matchedDN and diagnosticMessage fields, as well as some
>         resultCode values (e.g., attributeOrValueExists and
>         entryAlreadyExists), could disclose the presence the
>         specific data in the directory where not subjected to
>         access and other administrative controls.  Server
>         implementators should provide access control mechanisms
>         which not only restrict access to information under both
>         normal but also under error conditions.

s/both//.
s/presence the/presence of/.

-- 
Hallvard


From owner-ietf-ldapbis@OpenLDAP.org  Wed Feb 11 18:51:09 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11555
	for <ldapbis-archive@lists.ietf.org>; Wed, 11 Feb 2004 18:51:08 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1BNoA5r049470;
	Wed, 11 Feb 2004 23:50:10 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1BNbTZd048491;
	Wed, 11 Feb 2004 23:37: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); Wed, 11 Feb 2004 23:37:29 +0000
Received: from smtp-mclean.mitre.org (smtp-mclean-x.mitre.org [192.80.55.71])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1BNbQ5r048457;
	Wed, 11 Feb 2004 23:37:26 GMT
	(envelope-from kdally@mitre.org)
Received: from smtp-mclean.mitre.org (localhost.localdomain [127.0.0.1])
	by smtp-mclean.mitre.org (8.11.6/8.11.6) with ESMTP id i1BNbPb03857;
	Wed, 11 Feb 2004 18:37:25 -0500
Received: from MAILHUB2 (mailhub2.mitre.org [129.83.221.18])
	by smtp-mclean.mitre.org (8.11.6/8.11.6) with ESMTP id i1BNbOD03834;
	Wed, 11 Feb 2004 18:37:25 -0500
Received: from mm108631-pc.mitre.org (128.29.3.34) by mailhub2.mitre.org with SMTP
        id 1455527; Wed, 11 Feb 2004 18:37:20 -0500
Message-ID: <402ABCB1.CF3C93DF@mitre.org>
Date: Wed, 11 Feb 2004 18:37:21 -0500
From: Kathleen Dally <kdally@mitre.org>
Organization: The MITRE Corporation
X-Mailer: Mozilla 4.79 [en]C-20020130M  (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
CC: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>, IETF-LDAPbis@OpenLDAP.org
Subject: Re: SUBCLASSING, again
References: <40296C3C.C1D602A2@mitre.org>
		<6.0.1.1.0.20040210160558.0498e488@127.0.0.1> <HBF.20040211o9k9@bombur.uio.no>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hi All!

I think Entries and Object Classes are being confused in this discussion.
Nowhere does X.501 say that the superclasses of a Structural Object Class
cannot be Auxiliary.  In fact, there is no explicit statement that any of
the superclasses must be Structural.

For ENTRIES however, it is clear that there is exactly one Structural
Object Class.  Any additions or deletions of attributes or additions of
(Auxiliary) Object Classes to an ENTRY must be handled by a Content Rule.
There is nothing in the specification of a Content Rule that prohibits the
use of an Auxiliary Object Class.

For many years, I have been told by implementors that the products do not
support Content Rules!  Given this fact, if Auxiliary Object Classes could
not be superclasses, no Auxiliary Object Classes could never be used.
X.509 clearly intends that Auxiliary Object Classes be used, as it defines
several.

I think this sentence in the Models draft must be removed from section
2.4.2:
      "Structural object classes cannot subclass auxiliary object classes."

I think section 2.4.2 should be clarified to indicate that multiple
inheritance is possible, as is clearly stated in X.501, clause 8.3:
        "An object class may be derived from two or more direct
superclasses (superclasses not part of the same
         superclass chain). This feature of subclassing is termed multiple
inheritance."

 Perhaps this paragraph could be added to the end of section 2.4.2:
        "A Structural Object Class that is formed by multiple inheritance
has one direct superclass which is a
         structural object class and other direct superclasses which are
abstract or auxiliary object classes."

Regards,
Kathy Dally



Hallvard B Furuseth wrote:

> Kurt D. Zeilenga writes:
> > For instance, it is quite clear in X.501 that which auxiliary
> > classes an entry can belongs to is controlled solely by the
> > DIT Content Rule.  However, the entry's structural object
> > class has a auxiliary super class, then the entry belong to
> > that auxiliary class even when the DIT content rule disallows
> > it from belong to that auxiliary class.
>
> I guess that would mean that an entry of that structural object class
> cannot be created unless a DIT content rule allows the auxiliary class.
>
> --
> Hallvard




From owner-ietf-ldapbis@OpenLDAP.org  Wed Feb 11 19:43:24 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA14955
	for <ldapbis-archive@lists.ietf.org>; Wed, 11 Feb 2004 19:43:24 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1C0cP5v052137;
	Thu, 12 Feb 2004 00:42:37 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1C0bhwS052122;
	Thu, 12 Feb 2004 00:37: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, 12 Feb 2004 00:37:43 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1C0bf5r052112
	for <IETF-LDAPbis@OpenLDAP.org>; Thu, 12 Feb 2004 00:37:41 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from gypsy.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.10/8.12.10) with ESMTP id i1C0bc7s008297;
	Thu, 12 Feb 2004 00:37:38 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.1.1.0.20040211135958.049f2b20@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Wed, 11 Feb 2004 16:37:19 -0800
To: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: SUBCLASSING, again
Cc: Kathleen Dally <kdally@mitre.org>, IETF-LDAPbis@OpenLDAP.org
In-Reply-To: <HBF.20040211o9k9@bombur.uio.no>
References: <40296C3C.C1D602A2@mitre.org>
 <6.0.1.1.0.20040210160558.0498e488@127.0.0.1>
 <HBF.20040211o9k9@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 01:54 PM 2/11/2004, Hallvard B Furuseth wrote:
>Kurt D. Zeilenga writes:
>> For instance, it is quite clear in X.501 that which auxiliary
>> classes an entry can belongs to is controlled solely by the
>> DIT Content Rule.  However, the entry's structural object
>> class has a auxiliary super class, then the entry belong to
>> that auxiliary class even when the DIT content rule disallows
>> it from belong to that auxiliary class.
>
>I guess that would mean that an entry of that structural object class
>cannot be created unless a DIT content rule allows the auxiliary class.

Or one could argue that's not necessary because its controlled
through the structural object class of the entry.  That is,
it can be argued that a DIT content rules only controls the
optional set of auxiliary classes an entry may belong to.
As any entry of this structural class must belong to this
auxiliary class, it not subject to the DIT content rule.

My point here is that someone would need to engineer how such
subclassing should work.  That's a tall order when you
consider that not only did X.501 not explicitly disallow
Structurals from subclassing Auxiliaries, it did not
explicitly disallow Auxiliaries from subclassing Structurals.
Even if we were to only allow the former category, sections
8, 12, and 14 of X.501 would need to be significantly revised.

That is, the alternative to stating these restrictions is
not simple removal of the restrictions.  The alternative
is to revise the technical specification such that the model
make sense in the face of such subclassing and that it is
clear how implementations are to behave.

The WG considered this alternative during the WG Last Call
and rejected it.

Hence, at this point, if there are those who believe strongly
that this alternative should have been taken, that they
(on an individual basis) write an I-D making sense of such
subclassing.  That is, I don't think the WG should revisit
this issue in absence of a specific alternative text.  That
text should attempt to address the underlying problems with
X.501 which caused the restrictions to be added in the first
place.

Kurt



From owner-ietf-ldapbis@OpenLDAP.org  Wed Feb 11 19:51:18 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15280
	for <ldapbis-archive@lists.ietf.org>; Wed, 11 Feb 2004 19:51:17 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1C0oP5v052492;
	Thu, 12 Feb 2004 00:50:36 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1C0irsh052343;
	Thu, 12 Feb 2004 00:44: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, 12 Feb 2004 00:44:53 +0000
Received: from prv-mail20.provo.novell.com (prv-mail20.provo.novell.com [137.65.81.122])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1C0ip5r052301
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 12 Feb 2004 00:44:52 GMT
	(envelope-from jimse@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Wed, 11 Feb 2004 17:44:31 -0700
Message-Id: <s02a69ff.089@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.2 Beta
Date: Wed, 11 Feb 2004 17:44:07 -0700
From: "Jim Sermersheim" <jimse@novell.com>
To: <ietf-ldapbis@OpenLDAP.org>
Cc: "Steve McLain" <SMCLAIN@novell.com>
Subject: Models: Attribute subtype overrides
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__Part89A8EE47.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.

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

Models is not clear on which aspects of an attribute may and may not be
overridden in a subtype of that attribute.
 
In Section 2.5.1, it says "An attribute type cannot be a subtype of an 
attribute of different usage.". So we have direction on one of the
fields (USAGE), but we don't know whether other fields can be
overridden. Specifically:
- matching rules
- syntax (if so, does the overriding syntax have to be a subsyntax of
the supertype's syntax? probably, see countryString)
- single value (probably, see countryString)
- collective
- no user modification
- obsolete and description
 
Jim

--=__Part89A8EE47.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 6.00.2800.1400" name=3DGENERATOR></HEAD>
<BODY style=3D"MARGIN: 4px 4px 1px; FONT: 10pt Microsoft Sans Serif">
<DIV>Models is not clear on which aspects of an attribute may and may not =
be overridden in a subtype of that attribute.</DIV>
<DIV>&nbsp;</DIV>
<DIV>In Section 2.5.1, it says "An attribute type cannot be a subtype of =
an&nbsp; attribute of different usage.". So we have direction on one of =
the fields (USAGE), but we don't know whether other fields can be =
overridden. Specifically:</DIV>
<DIV>- matching rules</DIV>
<DIV>- syntax (if so, does the overriding syntax have to be a subsyntax of =
the supertype's syntax? probably, see countryString)</DIV>
<DIV>- single value (probably, see countryString)</DIV>
<DIV>- collective</DIV>
<DIV>- no user modification</DIV>
<DIV>- obsolete and description</DIV>
<DIV>&nbsp;</DIV>
<DIV>Jim</DIV></BODY></HTML>

--=__Part89A8EE47.0__=--


From owner-ietf-ldapbis@OpenLDAP.org  Wed Feb 11 19:57:15 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15577
	for <ldapbis-archive@lists.ietf.org>; Wed, 11 Feb 2004 19:57:14 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1C0uP5v052782;
	Thu, 12 Feb 2004 00:56:27 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1C0sDAU052709;
	Thu, 12 Feb 2004 00:54: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); Thu, 12 Feb 2004 00:54:13 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1C0sC5r052697
	for <IETF-LDAPbis@OpenLDAP.org>; Thu, 12 Feb 2004 00:54:13 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from gypsy.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.10/8.12.10) with ESMTP id i1C0sA7s008560;
	Thu, 12 Feb 2004 00:54:10 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.1.1.0.20040211163920.049f4d78@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Wed, 11 Feb 2004 16:53:51 -0800
To: Kathleen Dally <kdally@mitre.org>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: SUBCLASSING, again
Cc: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>, IETF-LDAPbis@OpenLDAP.org
In-Reply-To: <402ABCB1.CF3C93DF@mitre.org>
References: <40296C3C.C1D602A2@mitre.org>
 <6.0.1.1.0.20040210160558.0498e488@127.0.0.1>
 <HBF.20040211o9k9@bombur.uio.no>
 <402ABCB1.CF3C93DF@mitre.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>

X.501 doesn't explicitly say that auxiliary classes cannot
not subclass structural classes.  By your argument, these
must be allowed as well.  Why aren't you making this argument?

Kurt



From owner-ietf-ldapbis@OpenLDAP.org  Wed Feb 11 20:51:52 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA17787
	for <ldapbis-archive@lists.ietf.org>; Wed, 11 Feb 2004 20:51:51 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1C1oQ5v054767;
	Thu, 12 Feb 2004 01:50:59 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1C1jon3054645;
	Thu, 12 Feb 2004 01:45: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, 12 Feb 2004 01:45:50 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1C1jn5r054635
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 12 Feb 2004 01:45:49 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from gypsy.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.10/8.12.10) with ESMTP id i1C1je7s009380;
	Thu, 12 Feb 2004 01:45:40 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.1.1.0.20040211172457.049f6c38@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Wed, 11 Feb 2004 17:45:21 -0800
To: "Jim Sermersheim" <jimse@novell.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: Models: Attribute subtype overrides
Cc: <ietf-ldapbis@OpenLDAP.org>, "Steve McLain" <SMCLAIN@novell.com>
In-Reply-To: <s02a69ff.089@prv-mail20.provo.novell.com>
References: <s02a69ff.089@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 04:44 PM 2/11/2004, Jim Sermersheim wrote:
>Models is not clear on which aspects of an attribute may and may not be overridden in a subtype of that attribute.

There are two questions.

1) When one specifies a subtype without detailing all aspects of the
subtype, which aspects take there DEFAULT value and which take
their value from the supertype?

2) How may aspects of the subtype may differ from aspects of the
supertype?

The answer to 1) is, I believe:
  The only aspects which, if not provided, are taken from the
  supertype are the matching rule(s) and syntax.  All other
  aspects take there defaults.

The answer to 2) is a bit more involved.  The general rule is
that the supertype must be a more generic than its subtype.

For syntax, this implies that not only the abstract type
which the supertype can take be more generic, but the string
representation of the subtype should be refinement of the
string representation of the supertype.  And matching rules
for the supertype should be compatible with syntax of the
subtype.

I think the single valueness of the subtype should be the
same its supertype.

Collective requirements are detailed in [RFC3671].

I don't see much of a problem with no-user-modification
taking on a different value from super to sub type.
Off hand, same for obsolete.

And value of DESC takes doesn't matter, it's simply
a comment.

Looks like the TS needs some additional clarification here.
(Hallvard sent me a suggestion which partially addresses
issue 1, but I think more is needed.)  I'll offer new
text in a bit.

Kurt

> 
>In Section 2.5.1, it says "An attribute type cannot be a subtype of an  attribute of different usage.". So we have direction on one of the fields (USAGE), but we don't know whether other fields can be overridden. Specifically:
>- matching rules
>- syntax (if so, does the overriding syntax have to be a subsyntax of the supertype's syntax? probably, see countryString)
>- single value (probably, see countryString)
>- collective
>- no user modification
>- obsolete and description
> 
>Jim



From owner-ietf-ldapbis@OpenLDAP.org  Wed Feb 11 21:09:27 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA18182
	for <ldapbis-archive@lists.ietf.org>; Wed, 11 Feb 2004 21:09:27 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1C28Q5v055367;
	Thu, 12 Feb 2004 02:08:29 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1C267ek055278;
	Thu, 12 Feb 2004 02:06: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); Thu, 12 Feb 2004 02:06:07 +0000
Received: from prv-mail20.provo.novell.com (prv-mail20.provo.novell.com [137.65.81.122])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1C2645r055219;
	Thu, 12 Feb 2004 02:06:04 GMT
	(envelope-from jimse@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Wed, 11 Feb 2004 19:05:42 -0700
Message-Id: <s02a7d06.088@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.2 Beta
Date: Wed, 11 Feb 2004 19:03:29 -0700
From: "Jim Sermersheim" <jimse@novell.com>
To: <Kurt@OpenLDAP.org>
Cc: "Steve McLain" <SMCLAIN@novell.com>, <ietf-ldapbis@OpenLDAP.org>
Subject: Re: Models: Attribute subtype overrides
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__Part3D1C5AE1.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.

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

Note that countryString in X.500 and RFC 2252 change the
single-valueness while subtyping.
 
Good point on there being two different questions.
 
Also, if we want to get picky, we could state that a MUST attribute in
an object classes superclass is not made optional by placing it in the
MAY list of the object class.
 
Jim

>>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 2/11/04 6:45:21 PM >>>
At 04:44 PM 2/11/2004, Jim Sermersheim wrote:
>Models is not clear on which aspects of an attribute may and may not
be overridden in a subtype of that attribute.

There are two questions.

1) When one specifies a subtype without detailing all aspects of the
subtype, which aspects take there DEFAULT value and which take
their value from the supertype?

2) How may aspects of the subtype may differ from aspects of the
supertype?

The answer to 1) is, I believe:
The only aspects which, if not provided, are taken from the
supertype are the matching rule(s) and syntax. All other
aspects take there defaults.

The answer to 2) is a bit more involved. The general rule is
that the supertype must be a more generic than its subtype.

For syntax, this implies that not only the abstract type
which the supertype can take be more generic, but the string
representation of the subtype should be refinement of the
string representation of the supertype. And matching rules
for the supertype should be compatible with syntax of the
subtype.

I think the single valueness of the subtype should be the
same its supertype.

Collective requirements are detailed in [RFC3671].

I don't see much of a problem with no-user-modification
taking on a different value from super to sub type.
Off hand, same for obsolete.

And value of DESC takes doesn't matter, it's simply
a comment.

Looks like the TS needs some additional clarification here.
(Hallvard sent me a suggestion which partially addresses
issue 1, but I think more is needed.) I'll offer new
text in a bit.

Kurt

> 
>In Section 2.5.1, it says "An attribute type cannot be a subtype of an
attribute of different usage.". So we have direction on one of the
fields (USAGE), but we don't know whether other fields can be
overridden. Specifically:
>- matching rules
>- syntax (if so, does the overriding syntax have to be a subsyntax of
the supertype's syntax? probably, see countryString)
>- single value (probably, see countryString)
>- collective
>- no user modification
>- obsolete and description
> 
>Jim



--=__Part3D1C5AE1.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 6.00.2800.1400" name=3DGENERATOR></HEAD>
<BODY style=3D"MARGIN: 4px 4px 1px; FONT: 10pt Microsoft Sans Serif">
<DIV>Note that countryString in X.500 and RFC 2252 change the single-valuen=
ess while subtyping.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Good point on there being&nbsp;two different questions.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Also, if we want to get picky, we could state that a MUST attribute =
in an object classes&nbsp;superclass is not made optional by placing it in =
the MAY list of the object class.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Jim<BR><BR>&gt;&gt;&gt; "Kurt D. Zeilenga" &lt;Kurt@OpenLDAP.org&gt; =
2/11/04 6:45:21 PM &gt;&gt;&gt;<BR>At 04:44 PM 2/11/2004, Jim Sermersheim =
wrote:<BR>&gt;Models is not clear on which aspects of an attribute may and =
may not be overridden in a subtype of that attribute.<BR><BR>There are two =
questions.<BR><BR>1) When one specifies a subtype without detailing all =
aspects of the<BR>subtype, which aspects take there DEFAULT value and =
which take<BR>their value from the supertype?<BR><BR>2) How may aspects of =
the subtype may differ from aspects of the<BR>supertype?<BR><BR>The answer =
to 1) is, I believe:<BR>The only aspects which, if not provided, are taken =
from the<BR>supertype are the matching rule(s) and syntax. All other<BR>asp=
ects take there defaults.<BR><BR>The answer to 2) is a bit more involved. =
The general rule is<BR>that the supertype must be a more generic than its =
subtype.<BR><BR>For syntax, this implies that not only the abstract =
type<BR>which the supertype can take be more generic, but the string<BR>rep=
resentation of the subtype should be refinement of the<BR>string representa=
tion of the supertype. And matching rules<BR>for the supertype should be =
compatible with syntax of the<BR>subtype.<BR><BR>I think the single =
valueness of the subtype should be the<BR>same its supertype.<BR><BR>Collec=
tive requirements are detailed in [RFC3671].<BR><BR>I don't see much of a =
problem with no-user-modification<BR>taking on a different value from =
super to sub type.<BR>Off hand, same for obsolete.<BR><BR>And value of =
DESC takes doesn't matter, it's simply<BR>a comment.<BR><BR>Looks like the =
TS needs some additional clarification here.<BR>(Hallvard sent me a =
suggestion which partially addresses<BR>issue 1, but I think more is =
needed.) I'll offer new<BR>text in a bit.<BR><BR>Kurt<BR><BR>&gt; =
<BR>&gt;In Section 2.5.1, it says "An attribute type cannot be a subtype =
of an attribute of different usage.". So we have direction on one of the =
fields (USAGE), but we don't know whether other fields can be overridden. =
Specifically:<BR>&gt;- matching rules<BR>&gt;- syntax (if so, does the =
overriding syntax have to be a subsyntax of the supertype's syntax? =
probably, see countryString)<BR>&gt;- single value (probably, see =
countryString)<BR>&gt;- collective<BR>&gt;- no user modification<BR>&gt;- =
obsolete and description<BR>&gt; <BR>&gt;Jim<BR><BR></DIV></BODY></HTML>

--=__Part3D1C5AE1.0__=--


From owner-ietf-ldapbis@OpenLDAP.org  Wed Feb 11 21:15:21 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19049
	for <ldapbis-archive@lists.ietf.org>; Wed, 11 Feb 2004 21:15:21 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1C2EQ5v055627;
	Thu, 12 Feb 2004 02:14:28 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1C2CWKb055592;
	Thu, 12 Feb 2004 02:12: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); Thu, 12 Feb 2004 02:12:32 +0000
Received: from prv-mail20.provo.novell.com (prv-mail20.provo.novell.com [137.65.81.122])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1C2CT5r055551;
	Thu, 12 Feb 2004 02:12:29 GMT
	(envelope-from jimse@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Wed, 11 Feb 2004 19:12:09 -0700
Message-Id: <s02a7e89.036@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.2 Beta
Date: Wed, 11 Feb 2004 19:11:35 -0700
From: "Jim Sermersheim" <jimse@novell.com>
To: <Kurt@OpenLDAP.org>, <h.b.furuseth@usit.uio.no>
Cc: <kdally@mitre.org>, <IETF-LDAPbis@OpenLDAP.org>
Subject: Re: SUBCLASSING, again
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__Part250442C7.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.

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

Well, as long as we're on the topic...
 
Models doesn't give state whether a DIT content rule applies only to
the structural object class it names, or if it is inherited to
subclasses of that object class (there may be some inferences, but
nothing obvious). From memory, I think X.500 says DIT content rules only
apply to the structural object class named in the DIT content rule (no
inheritance). Whatever the case may be, It should probably be called out
in Models to avoid confusion.
 
Jim

>>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 2/11/04 5:37:19 PM >>>
At 01:54 PM 2/11/2004, Hallvard B Furuseth wrote:
>Kurt D. Zeilenga writes:
>> For instance, it is quite clear in X.501 that which auxiliary
>> classes an entry can belongs to is controlled solely by the
>> DIT Content Rule. However, the entry's structural object
>> class has a auxiliary super class, then the entry belong to
>> that auxiliary class even when the DIT content rule disallows
>> it from belong to that auxiliary class.
>
>I guess that would mean that an entry of that structural object class
>cannot be created unless a DIT content rule allows the auxiliary
class.

Or one could argue that's not necessary because its controlled
through the structural object class of the entry. That is,
it can be argued that a DIT content rules only controls the
optional set of auxiliary classes an entry may belong to.
As any entry of this structural class must belong to this
auxiliary class, it not subject to the DIT content rule.

My point here is that someone would need to engineer how such
subclassing should work. That's a tall order when you
consider that not only did X.501 not explicitly disallow
Structurals from subclassing Auxiliaries, it did not
explicitly disallow Auxiliaries from subclassing Structurals.
Even if we were to only allow the former category, sections
8, 12, and 14 of X.501 would need to be significantly revised.

That is, the alternative to stating these restrictions is
not simple removal of the restrictions. The alternative
is to revise the technical specification such that the model
make sense in the face of such subclassing and that it is
clear how implementations are to behave.

The WG considered this alternative during the WG Last Call
and rejected it.

Hence, at this point, if there are those who believe strongly
that this alternative should have been taken, that they
(on an individual basis) write an I-D making sense of such
subclassing. That is, I don't think the WG should revisit
this issue in absence of a specific alternative text. That
text should attempt to address the underlying problems with
X.501 which caused the restrictions to be added in the first
place.

Kurt



--=__Part250442C7.1__=
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 6.00.2800.1400" name=3DGENERATOR></HEAD>
<BODY style=3D"MARGIN: 4px 4px 1px; FONT: 10pt Microsoft Sans Serif">
<DIV>Well, as long as we're on the topic...</DIV>
<DIV>&nbsp;</DIV>
<DIV>Models doesn't give state whether a DIT content rule applies only to =
the structural object class it names, or if it is inherited to subclasses =
of that object class (there may be some inferences, but nothing obvious). =
From memory, I think X.500 says DIT content rules only apply to the =
structural object class named in the DIT content rule (no inheritance). =
Whatever the case may be, It should probably be called out in Models to =
avoid confusion.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Jim<BR><BR>&gt;&gt;&gt; "Kurt D. Zeilenga" &lt;Kurt@OpenLDAP.org&gt; =
2/11/04 5:37:19 PM &gt;&gt;&gt;<BR>At 01:54 PM 2/11/2004, Hallvard B =
Furuseth wrote:<BR>&gt;Kurt D. Zeilenga writes:<BR>&gt;&gt; For instance, =
it is quite clear in X.501 that which auxiliary<BR>&gt;&gt; classes an =
entry can belongs to is controlled solely by the<BR>&gt;&gt; DIT Content =
Rule. However, the entry's structural object<BR>&gt;&gt; class has a =
auxiliary super class, then the entry belong to<BR>&gt;&gt; that auxiliary =
class even when the DIT content rule disallows<BR>&gt;&gt; it from belong =
to that auxiliary class.<BR>&gt;<BR>&gt;I guess that would mean that an =
entry of that structural object class<BR>&gt;cannot be created unless a =
DIT content rule allows the auxiliary class.<BR><BR>Or one could argue =
that's not necessary because its controlled<BR>through the structural =
object class of the entry. That is,<BR>it can be argued that a DIT content =
rules only controls the<BR>optional set of auxiliary classes an entry may =
belong to.<BR>As any entry of this structural class must belong to =
this<BR>auxiliary class, it not subject to the DIT content rule.<BR><BR>My =
point here is that someone would need to engineer how such<BR>subclassing =
should work. That's a tall order when you<BR>consider that not only did =
X.501 not explicitly disallow<BR>Structurals from subclassing Auxiliaries, =
it did not<BR>explicitly disallow Auxiliaries from subclassing Structurals.=
<BR>Even if we were to only allow the former category, sections<BR>8, 12, =
and 14 of X.501 would need to be significantly revised.<BR><BR>That is, =
the alternative to stating these restrictions is<BR>not simple removal of =
the restrictions. The alternative<BR>is to revise the technical specificati=
on such that the model<BR>make sense in the face of such subclassing and =
that it is<BR>clear how implementations are to behave.<BR><BR>The WG =
considered this alternative during the WG Last Call<BR>and rejected =
it.<BR><BR>Hence, at this point, if there are those who believe strongly<BR=
>that this alternative should have been taken, that they<BR>(on an =
individual basis) write an I-D making sense of such<BR>subclassing. That =
is, I don't think the WG should revisit<BR>this issue in absence of a =
specific alternative text. That<BR>text should attempt to address the =
underlying problems with<BR>X.501 which caused the restrictions to be =
added in the first<BR>place.<BR><BR>Kurt<BR><BR></DIV></BODY></HTML>

--=__Part250442C7.1__=--


From owner-ietf-ldapbis@OpenLDAP.org  Wed Feb 11 21:21:11 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19404
	for <ldapbis-archive@lists.ietf.org>; Wed, 11 Feb 2004 21:21:10 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1C2KQ5v055852;
	Thu, 12 Feb 2004 02:20:28 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1C2FEXe055670;
	Thu, 12 Feb 2004 02:15: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); Thu, 12 Feb 2004 02:15:13 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1C2FC5r055659
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 12 Feb 2004 02:15:12 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from gypsy.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.10/8.12.10) with ESMTP id i1C2FA7s009726;
	Thu, 12 Feb 2004 02:15:11 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.1.1.0.20040211174658.04a12260@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Wed, 11 Feb 2004 18:14:52 -0800
To: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: protocol: data hiding
Cc: Jim Sermersheim <jimse@novell.com>, ietf-ldapbis@OpenLDAP.org
In-Reply-To: <HBF.20040211o2rr@bombur.uio.no>
References: <s027a3e1.047@prv-mail20.provo.novell.com>
 <6.0.1.1.0.20040209144227.04cfb570@127.0.0.1>
 <HBF.20040211o2rr@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 02:05 PM 2/11/2004, Hallvard B Furuseth wrote:
>Jim Sermersheim wrote:
>
>> I like the notion of bringing this to the reader's attention, but I
>> dislike prescribing specific actions. How about something more like:
>
>For diagnosticMessage, I agree.
>
>Not sure about matchedDN.  The options I can think of are to act as if
>the entry is not there, or to not return a matchedDN at all.  However,
>with the latter behaviour, a user who knows the server well can
>sometimes deduce that an expected but missing matchedDN indicates a
>hidden entry.  So I think the text should at least mention that data
>is best hidden by pretending it is not there.

Note that matchedDN, like diagnosticMessage, are not OPTIONAL
fields.  They must always be present in the response.  However,
there value can be the empty string.

Beyond this, I agree with your sediment that you need to
careful in what you return in matchedDN.  If the value of
matchedDN is conditional in the implementation (that is,
the server does not always return the root DN), a client
may be able to deduce information from values provided.
And if additional information is available, such as the
naming context(s), it becomes even easier to deduce
information from the values provided.


>As for the result code, I would like the text to at least suggest that
>one may return a less informative result code.  Otherwise it may not be
>clear to an implementor what he can do when some revealing result code
>should normally be returned.

Note that more general is not necessarily less informative
to the attacker.


> Since I can't think of any other option, I
>don't really care is that is stated as a suggestion or a mandate.

I think it comes down to the server being free to return what
it considers to be the most appropriate code.  The most
appropriate code may not be the most specific.

Kurt


>Also,
>
>Kurt D. Zeilenga wrote:
>
>>         The matchedDN and diagnosticMessage fields, as well as some
>>         resultCode values (e.g., attributeOrValueExists and
>>         entryAlreadyExists), could disclose the presence the
>>         specific data in the directory where not subjected to
>>         access and other administrative controls.  Server
>>         implementators should provide access control mechanisms
>>         which not only restrict access to information under both
>>         normal but also under error conditions.
>
>s/both//.
>s/presence the/presence of/.
>
>-- 
>Hallvard



From owner-ietf-ldapbis@OpenLDAP.org  Wed Feb 11 21:57:48 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA20289
	for <ldapbis-archive@lists.ietf.org>; Wed, 11 Feb 2004 21:57:48 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1C2uQ5v057106;
	Thu, 12 Feb 2004 02:56:57 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1C2ofKd056917;
	Thu, 12 Feb 2004 02:50: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, 12 Feb 2004 02:50:41 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1C2oa5r056906
	for <IETF-LDAPbis@OpenLDAP.org>; Thu, 12 Feb 2004 02:50:40 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from gypsy.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.10/8.12.10) with ESMTP id i1C2oa7s010251;
	Thu, 12 Feb 2004 02:50:36 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.1.1.0.20040211184333.049e7ac0@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Wed, 11 Feb 2004 18:50:17 -0800
To: "Jim Sermersheim" <jimse@novell.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: dit content rules (Was: SUBCLASSING, again)
Cc: <IETF-LDAPbis@OpenLDAP.org>
In-Reply-To: <s02a7e89.036@prv-mail20.provo.novell.com>
References: <s02a7e89.036@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:11 PM 2/11/2004, Jim Sermersheim wrote:
>Well, as long as we're on the topic...
> 
>Models doesn't give state whether a DIT content rule applies only to the structural object class it names, or if it is inherited to subclasses of that object class (there may be some inferences, but nothing obvious).

My working copy includes a clarification for this:
  An entry is governed by (if present and active in the subschema)
  the DIT content rule which applies to the structural object class
  of the entry (see Section 2.4.2).  If no active rule is present for
  the entry's structural object class, the entry's content is governed
  by the structural object class (and possibly other aspects of user
  and system schema).  DIT content rules for superclasses of the
  structural object class of an entry are not applicable to that
  entry.

>>From memory, I think X.500 says DIT content rules only apply to the structural object class named in the DIT content rule (no inheritance). Whatever the case may be, It should probably be called out in Models to avoid confusion.
> 
>Jim
>
>>>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 2/11/04 5:37:19 PM >>>
>At 01:54 PM 2/11/2004, Hallvard B Furuseth wrote:
>>Kurt D. Zeilenga writes:
>>> For instance, it is quite clear in X.501 that which auxiliary
>>> classes an entry can belongs to is controlled solely by the
>>> DIT Content Rule. However, the entry's structural object
>>> class has a auxiliary super class, then the entry belong to
>>> that auxiliary class even when the DIT content rule disallows
>>> it from belong to that auxiliary class.
>>
>>I guess that would mean that an entry of that structural object class
>>cannot be created unless a DIT content rule allows the auxiliary class.
>
>Or one could argue that's not necessary because its controlled
>through the structural object class of the entry. That is,
>it can be argued that a DIT content rules only controls the
>optional set of auxiliary classes an entry may belong to.
>As any entry of this structural class must belong to this
>auxiliary class, it not subject to the DIT content rule.
>
>My point here is that someone would need to engineer how such
>subclassing should work. That's a tall order when you
>consider that not only did X.501 not explicitly disallow
>Structurals from subclassing Auxiliaries, it did not
>explicitly disallow Auxiliaries from subclassing Structurals.
>Even if we were to only allow the former category, sections
>8, 12, and 14 of X.501 would need to be significantly revised.
>
>That is, the alternative to stating these restrictions is
>not simple removal of the restrictions. The alternative
>is to revise the technical specification such that the model
>make sense in the face of such subclassing and that it is
>clear how implementations are to behave.
>
>The WG considered this alternative during the WG Last Call
>and rejected it.
>
>Hence, at this point, if there are those who believe strongly
>that this alternative should have been taken, that they
>(on an individual basis) write an I-D making sense of such
>subclassing. That is, I don't think the WG should revisit
>this issue in absence of a specific alternative text. That
>text should attempt to address the underlying problems with
>X.501 which caused the restrictions to be added in the first
>place.
>
>Kurt



From owner-ietf-ldapbis@OpenLDAP.org  Wed Feb 11 22:01:46 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA20370
	for <ldapbis-archive@lists.ietf.org>; Wed, 11 Feb 2004 22:01:45 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1C3155v057639;
	Thu, 12 Feb 2004 03:01:10 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1C2ueHR057164;
	Thu, 12 Feb 2004 02:56: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); Thu, 12 Feb 2004 02:56:40 +0000
Received: from smtp-mclean.mitre.org (smtp-mclean-x.mitre.org [192.80.55.71])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1C2uc5r057116;
	Thu, 12 Feb 2004 02:56:38 GMT
	(envelope-from kdally@mitre.org)
Received: from smtp-mclean.mitre.org (localhost.localdomain [127.0.0.1])
	by smtp-mclean.mitre.org (8.11.6/8.11.6) with ESMTP id i1C2ubb00746;
	Wed, 11 Feb 2004 21:56:37 -0500
Received: from MAILHUB1 (mailhub1.mitre.org [129.83.20.31])
	by smtp-mclean.mitre.org (8.11.6/8.11.6) with ESMTP id i1C2ubD00736;
	Wed, 11 Feb 2004 21:56:37 -0500
Received: from mm108631-pc.mitre.org (128.29.3.34) by mailhub1.mitre.org with SMTP
        id 6097780; Wed, 11 Feb 2004 21:56:32 -0500
Message-ID: <402AEB5F.9DACCE1E@mitre.org>
Date: Wed, 11 Feb 2004 21:56:31 -0500
From: Kathleen Dally <kdally@mitre.org>
Organization: The MITRE Corporation
X-Mailer: Mozilla 4.79 [en]C-20020130M  (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
CC: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>, IETF-LDAPbis@OpenLDAP.org
Subject: Re: SUBCLASSING, again
References: <40296C3C.C1D602A2@mitre.org>
	 <6.0.1.1.0.20040210160558.0498e488@127.0.0.1>
	 <HBF.20040211o9k9@bombur.uio.no>
	 <402ABCB1.CF3C93DF@mitre.org> <6.0.1.1.0.20040211163920.049f4d78@127.0.0.1>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hi Kurt!

I would have no trouble deleting the sentence from Models, section
2.4.3:
        " Auxiliary object classes cannot subclass structural object
classes."

However, I do not believe that the intent to permit Auxiliary object
classes to subclass Structural object classes is as clear in X.501.

To fix the original problem, Models, section 2.4.3, third paragraph,
second sentence needs to be deleted, too.  It begins:
        "If no DIT content rule ..."

Regards,
Kathy


"Kurt D. Zeilenga" wrote:

> X.501 doesn't explicitly say that auxiliary classes cannot
> not subclass structural classes.  By your argument, these
> must be allowed as well.  Why aren't you making this argument?
>
> Kurt




From owner-ietf-ldapbis@OpenLDAP.org  Wed Feb 11 22:09:28 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA20534
	for <ldapbis-archive@lists.ietf.org>; Wed, 11 Feb 2004 22:09:27 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1C38Q5v058126;
	Thu, 12 Feb 2004 03:08:31 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1C34W7C057897;
	Thu, 12 Feb 2004 03:04: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); Thu, 12 Feb 2004 03:04:32 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1C34R5r057884
	for <IETF-LDAPbis@OpenLDAP.org>; Thu, 12 Feb 2004 03:04:31 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from gypsy.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.10/8.12.10) with ESMTP id i1C34P7s010600;
	Thu, 12 Feb 2004 03:04:25 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.1.1.0.20040211185718.049eb830@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Wed, 11 Feb 2004 19:04:06 -0800
To: Kathleen Dally <kdally@mitre.org>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: SUBCLASSING, again
Cc: IETF-LDAPbis@OpenLDAP.org
In-Reply-To: <402AEB5F.9DACCE1E@mitre.org>
References: <40296C3C.C1D602A2@mitre.org>
 <6.0.1.1.0.20040210160558.0498e488@127.0.0.1>
 <HBF.20040211o9k9@bombur.uio.no>
 <402ABCB1.CF3C93DF@mitre.org>
 <6.0.1.1.0.20040211163920.049f4d78@127.0.0.1>
 <402AEB5F.9DACCE1E@mitre.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

At 06:56 PM 2/11/2004, Kathleen Dally wrote:
>I would have no trouble deleting the sentence from Models, section
>2.4.3:
>        " Auxiliary object classes cannot subclass structural object
>classes."

Even though the model makes no sense in face of such
constructions?

>However, I do not believe that the intent to permit Auxiliary object
>classes to subclass Structural object classes is as clear in X.501.

Why?  Since X.501 didn't explicitly disallow this, why do
you think it clear that the intent was to disallow this?

Kurt 



From owner-ietf-ldapbis@OpenLDAP.org  Wed Feb 11 22:27:15 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA21021
	for <ldapbis-archive@lists.ietf.org>; Wed, 11 Feb 2004 22:27:14 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1C3QQ5v058795;
	Thu, 12 Feb 2004 03:26:29 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1C3Njwg058672;
	Thu, 12 Feb 2004 03:23: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); Thu, 12 Feb 2004 03:23:45 +0000
Received: from smtp-mclean.mitre.org (smtp-mclean-x.mitre.org [192.80.55.71])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1C3Ng5r058631;
	Thu, 12 Feb 2004 03:23:43 GMT
	(envelope-from kdally@mitre.org)
Received: from smtp-mclean.mitre.org (localhost.localdomain [127.0.0.1])
	by smtp-mclean.mitre.org (8.11.6/8.11.6) with ESMTP id i1C3Ngb15184;
	Wed, 11 Feb 2004 22:23:42 -0500
Received: from MAILHUB1 (mailhub1.mitre.org [129.83.20.31])
	by smtp-mclean.mitre.org (8.11.6/8.11.6) with ESMTP id i1C3NgD15175;
	Wed, 11 Feb 2004 22:23:42 -0500
Received: from mm108631-pc.mitre.org (128.29.3.34) by mailhub1.mitre.org with SMTP
        id 6097888; Wed, 11 Feb 2004 22:23:40 -0500
Message-ID: <402AF1BA.CF3ECA14@mitre.org>
Date: Wed, 11 Feb 2004 22:23:38 -0500
From: Kathleen Dally <kdally@mitre.org>
Organization: The MITRE Corporation
X-Mailer: Mozilla 4.79 [en]C-20020130M  (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Jim Sermersheim <jimse@novell.com>
CC: Kurt@OpenLDAP.org, h.b.furuseth@usit.uio.no, IETF-LDAPbis@OpenLDAP.org
Subject: Re: SUBCLASSING, again
References: <s02a7e89.035@prv-mail20.provo.novell.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hi Jim!

The statement in X.501, which you are looking for, is in clause 12.7.1:
        "The DIT content rules of superclasses of the structural object
class for an entry do not apply to that entry."

Regards,
Kathy


Jim Sermersheim wrote:

>  Well, as long as we're on the topic... Models doesn't give state
> whether a DIT content rule applies only to the structural object class
> it names, or if it is inherited to subclasses of that object class
> (there may be some inferences, but nothing obvious). From memory, I
> think X.500 says DIT content rules only apply to the structural object
> class named in the DIT content rule (no inheritance). Whatever the
> case may be, It should probably be called out in Models to avoid
> confusion. Jim
>
> >>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 2/11/04 5:37:19 PM >>>
> At 01:54 PM 2/11/2004, Hallvard B Furuseth wrote:
> >Kurt D. Zeilenga writes:
> >> For instance, it is quite clear in X.501 that which auxiliary
> >> classes an entry can belongs to is controlled solely by the
> >> DIT Content Rule. However, the entry's structural object
> >> class has a auxiliary super class, then the entry belong to
> >> that auxiliary class even when the DIT content rule disallows
> >> it from belong to that auxiliary class.
> >
> >I guess that would mean that an entry of that structural object class
>
> >cannot be created unless a DIT content rule allows the auxiliary
> class.
>
> Or one could argue that's not necessary because its controlled
> through the structural object class of the entry. That is,
> it can be argued that a DIT content rules only controls the
> optional set of auxiliary classes an entry may belong to.
> As any entry of this structural class must belong to this
> auxiliary class, it not subject to the DIT content rule.
>
> My point here is that someone would need to engineer how such
> subclassing should work. That's a tall order when you
> consider that not only did X.501 not explicitly disallow
> Structurals from subclassing Auxiliaries, it did not
> explicitly disallow Auxiliaries from subclassing Structurals.
> Even if we were to only allow the former category, sections
> 8, 12, and 14 of X.501 would need to be significantly revised.
>
> That is, the alternative to stating these restrictions is
> not simple removal of the restrictions. The alternative
> is to revise the technical specification such that the model
> make sense in the face of such subclassing and that it is
> clear how implementations are to behave.
>
> The WG considered this alternative during the WG Last Call
> and rejected it.
>
> Hence, at this point, if there are those who believe strongly
> that this alternative should have been taken, that they
> (on an individual basis) write an I-D making sense of such
> subclassing. That is, I don't think the WG should revisit
> this issue in absence of a specific alternative text. That
> text should attempt to address the underlying problems with
> X.501 which caused the restrictions to be added in the first
> place.
>
> Kurt
>




From owner-ietf-ldapbis@OpenLDAP.org  Wed Feb 11 22:33:12 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA21340
	for <ldapbis-archive@lists.ietf.org>; Wed, 11 Feb 2004 22:33:11 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1C3WQ5v059115;
	Thu, 12 Feb 2004 03:32:33 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1C3Us50059055;
	Thu, 12 Feb 2004 03:30: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); Thu, 12 Feb 2004 03:30:54 +0000
Received: from smtp-mclean.mitre.org (smtp-mclean-x.mitre.org [192.80.55.71])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1C3Up5r059025;
	Thu, 12 Feb 2004 03:30:51 GMT
	(envelope-from kdally@mitre.org)
Received: from smtp-mclean.mitre.org (localhost.localdomain [127.0.0.1])
	by smtp-mclean.mitre.org (8.11.6/8.11.6) with ESMTP id i1C3Upb18828;
	Wed, 11 Feb 2004 22:30:51 -0500
Received: from MAILHUB1 (mailhub1.mitre.org [129.83.20.31])
	by smtp-mclean.mitre.org (8.11.6/8.11.6) with ESMTP id i1C3UpD18823;
	Wed, 11 Feb 2004 22:30:51 -0500
Received: from mm108631-pc.mitre.org (128.29.3.34) by mailhub1.mitre.org with SMTP
        id 6097922; Wed, 11 Feb 2004 22:30:49 -0500
Message-ID: <402AF367.DF52B561@mitre.org>
Date: Wed, 11 Feb 2004 22:30:47 -0500
From: Kathleen Dally <kdally@mitre.org>
Organization: The MITRE Corporation
X-Mailer: Mozilla 4.79 [en]C-20020130M  (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
CC: IETF-LDAPbis@OpenLDAP.org
Subject: Re: SUBCLASSING, again
References: <40296C3C.C1D602A2@mitre.org>
	 <6.0.1.1.0.20040210160558.0498e488@127.0.0.1>
	 <HBF.20040211o9k9@bombur.uio.no>
	 <402ABCB1.CF3C93DF@mitre.org>
	 <6.0.1.1.0.20040211163920.049f4d78@127.0.0.1>
	 <402AEB5F.9DACCE1E@mitre.org> <6.0.1.1.0.20040211185718.049eb830@127.0.0.1>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hi Kurt!

Responses in-line.

Thanks,
Kathy


"Kurt D. Zeilenga" wrote:

> At 06:56 PM 2/11/2004, Kathleen Dally wrote:
> >I would have no trouble deleting the sentence from Models, section
> >2.4.3:
> >        " Auxiliary object classes cannot subclass structural object
> >classes."
>
> Even though the model makes no sense in face of such
> constructions?

kd:  I agree that this seems nonsensical.  I haven't seen any use made of
such a subclassing.

>

>
>
> >However, I do not believe that the intent to permit Auxiliary object
> >classes to subclass Structural object classes is as clear in X.501.
>
> Why?  Since X.501 didn't explicitly disallow this, why do
> you think it clear that the intent was to disallow this?

kd:  The intent that I am speaking about is the nature of Auxiliary
Object Classes being a means of augmenting other classes and entries with
groups of attributes.

>
>
> Kurt




From owner-ietf-ldapbis@OpenLDAP.org  Thu Feb 12 02:15:59 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA10998
	for <ldapbis-archive@lists.ietf.org>; Thu, 12 Feb 2004 02:15:58 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1C7El5r067339;
	Thu, 12 Feb 2004 07:14:47 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1C76V9Z066941;
	Thu, 12 Feb 2004 07: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); Thu, 12 Feb 2004 07:06:31 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1C76T5r066931
	for <IETF-LDAPbis@OpenLDAP.org>; Thu, 12 Feb 2004 07: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.10/8.12.10) with ESMTP id i1C76Q7s013919;
	Thu, 12 Feb 2004 07:06:26 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.1.1.0.20040211202558.049f4d58@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Wed, 11 Feb 2004 23:06:07 -0800
To: Kathleen Dally <kdally@mitre.org>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: SUBCLASSING, again
Cc: IETF-LDAPbis@OpenLDAP.org
In-Reply-To: <402AF367.DF52B561@mitre.org>
References: <40296C3C.C1D602A2@mitre.org>
 <6.0.1.1.0.20040210160558.0498e488@127.0.0.1>
 <HBF.20040211o9k9@bombur.uio.no>
 <402ABCB1.CF3C93DF@mitre.org>
 <6.0.1.1.0.20040211163920.049f4d78@127.0.0.1>
 <402AEB5F.9DACCE1E@mitre.org>
 <6.0.1.1.0.20040211185718.049eb830@127.0.0.1>
 <402AF367.DF52B561@mitre.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

At 07:30 PM 2/11/2004, Kathleen Dally wrote:
>"Kurt D. Zeilenga" wrote:
>
>> At 06:56 PM 2/11/2004, Kathleen Dally wrote:
>> >I would have no trouble deleting the sentence from Models, section
>> >2.4.3:
>> >        " Auxiliary object classes cannot subclass structural object
>> >classes."
>>
>> Even though the model makes no sense in face of such
>> constructions?
>
>kd:  I agree that this seems nonsensical.  I haven't seen any use made of
>such a subclassing.

So, it's okay to disallow this, even though X.501 didn't
explicitly do so, because they are nonsensical.

One can, and the WG did, apply the same argument to Structural
Classes which subclass Auxiliaries.  That is, that this is
nonsensical and hence should be disallowed, as implied by the
"more generic" statement as well as other aspects of the
specification.

As I noted then (and recently), the alternative is to try to
make sense of it.  However, that's a tall order (see below).

>> >However, I do not believe that the intent to permit Auxiliary object
>> >classes to subclass Structural object classes is as clear in X.501.
>>
>> Why?  Since X.501 didn't explicitly disallow this, why do
>> you think it clear that the intent was to disallow this?
>
>kd:  The intent that I am speaking about is the nature of Auxiliary
>Object Classes being a means of augmenting other classes and entries with
>groups of attributes.

Where in X.501 does it describe Auxiliary object classes as a
mechanism for extending other classes, in particular, any
structural class?  In reading 8.3.3, it seems clear the nature
of Auxiliary object classes is to allow optional augmentation
of entries.

Do you see any language anywhere which specifically mentions
that those constructs are allowed, and, more importantly, any
text which addresses the special cases which would naturally
arise from allowance of such constructs?

My concern is that there are many statements which, when taken
together, make little sense if structural classes are allowed
to subclass auxiliary classes.  Below I elaborate on a few
instances.

8.3.3 says:
  Therefore, besides being a member of the structural object class,
  an entry may be optionally a member of one or more auxiliary object
  classes.
This would have to reworded:
  Therefore, besides being a member of the structural object class
  and any auxiliary classes which are superclasses of this
  structural object class, an entry may be optionally a member of
  one or more auxiliary object classes.
to clarify that membership in structural class's superclass
auxiliary class is not always optional as implied by current text.

8.3.3 continues:
  An entry’s auxiliary object classes may change over time.
This would have to reworded:
  An entry's auxiliary object classes, except those which are
  superclasses of the entry's structural object class, may
  change over time.
as not all the entry's object classes may change over time as
implied by the current text.

Before I go on, I note that it's starting to sounding like an
auxiliary class which is a superclass of the structural object
class of an entry is to be treated as if it were structural
in this situation.  But, I note that is counter to 8.3:
  Each object class is of precisely one of these kinds,
  and remains of this kind in whatever situation it is
  encountered within the Directory.
This section, I think, was intended that special cases were
not intended.  But we'd have to treat auxiliary classes in this
situation quite differently from those not in this situation.

12.3 says,
   There shall be one value of the objectClass attribute for
   the entry’s structural object class and a value for each
   of its superclasses.
So, in this situation, the auxiliary superclasses of the
structural class of the entry are required to be listed as
objectClass values. 12.3 then says:
      Where auxiliary object classes are used, an entry may
   contain values of the objectClass attribute for the
   auxiliary object classes and their superclasses allowed
   by a DIT content rule.
which means that in this situation, these auxiliary
superclasses of the structural class of the entry must in
listed in the controlling DIT content rule.  And, unsaid,
this requires there to be a controlling DIT content rule
in this situation.

12.7 says:
  A DIT content rule specifies the permissible content of
  entries of a particular structural object class via the
  identification of an optional set of auxiliary object
  classes, mandatory, optional and precluded attributes.
That is, only those auxiliary classes in this optional set are
permissible.  12.7 continues:
  A DIT content rule definition includes:
      optionally, an indication of the auxiliary object
      classes allowed for entries governed by the rule
That is, if they are listed, the class is "allowed", not
"required". But from 12.3 we get that auxiliary superclasses
of the structural class of the entry are actually required
to be listed and this set is not optional in this situation.

12.7 says:
  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.
If we consider a DIT content rule which lists as allowed
only the auxiliary superclasses of the structural class of
the entry, then the only subset which an entry can be
associated with is the complete set, not any subset.

There are likely other areas where that would need to
be revised if such constructs were to be allowed.

In response to your comment:

>For many years, I have been told by implementors that
>the products do not support Content Rules!

Some do, some don't.  In LDAP, it's viewed as optional.

>Given this fact, if Auxiliary Object Classes could not be
>superclasses, no Auxiliary Object Classes could never
>be used.

In absence of some extension, as previously discussed
during WG Last Call, yes.

Many LDAP implementations have extensions in this area.
However, I'm now aware of any formal specification which
details how the set of permissible auxiliary classes is
controlled in absence of DIT content rules.  However, I
am aware of implementations which, while supporting
such extensions, do not allow such subclassing constructs.
This because the constructs are nonsensical even when
one uses other mechanisms to control which auxiliaries
may be present (for instance, section 8 concerns above).

The question for us is whether implementations which
claim to support DIT content rules in a manner consistent
with the existing specification and, if so, how to address
interoperability and other known technical issues.  It is
clear that that there are multiple independently developed
implementations of DIT content rules as described in this
X.500 and that the clarifications in [Models] go a long way
towards addressing the known technical issues.

Kurt 



From owner-ietf-ldapbis@OpenLDAP.org  Thu Feb 12 05:11:40 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA17354
	for <ldapbis-archive@lists.ietf.org>; Thu, 12 Feb 2004 05:11:40 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1CAAG5r088052;
	Thu, 12 Feb 2004 10:10:16 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1CA1Eb9087391;
	Thu, 12 Feb 2004 10:01: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); Thu, 12 Feb 2004 10:01:14 +0000
Received: from nb2.stroeder.com ([62.80.59.140])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1CA1A5r087332;
	Thu, 12 Feb 2004 10:01:11 GMT
	(envelope-from michael@stroeder.com)
Received: from stroeder.com (localhost [127.0.0.1])
	by nb2.stroeder.com (Postfix) with ESMTP
	id D6535112C9; Thu, 12 Feb 2004 10:50:30 +0100 (CET)
Message-ID: <402B4C66.4030202@stroeder.com>
Date: Thu, 12 Feb 2004 10:50:30 +0100
From: =?ISO-8859-1?Q?Michael_Str=F6der?= <michael@stroeder.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: de-de, de, en-us, en
MIME-Version: 1.0
To: Jim Sermersheim <jimse@novell.com>
Cc: Kurt@OpenLDAP.org, Steve McLain <SMCLAIN@novell.com>,
        ietf-ldapbis@OpenLDAP.org
Subject: Re: Models: Attribute subtype overrides
References: <s02a7d06.088@prv-mail20.provo.novell.com>
In-Reply-To: <s02a7d06.088@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 Sermersheim wrote:
> 
> Also, if we want to get picky, we could state that a MUST attribute in 
> an object classes superclass is not made optional by placing it in the 
> MAY list of the object class.

My code assumes that this is the case. An attribute is MUST if it's MUST in 
at least one superclass.

Ciao, Michael.


From owner-ietf-ldapbis@OpenLDAP.org  Thu Feb 12 11:04:24 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29892
	for <ldapbis-archive@lists.ietf.org>; Thu, 12 Feb 2004 11:04:23 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1CG2V5v011351;
	Thu, 12 Feb 2004 16:03:09 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1CFwkao011248;
	Thu, 12 Feb 2004 15:58: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, 12 Feb 2004 15:58:46 +0000
Received: from cosium01.intelliden.net (cosium01.intelliden.net [12.41.186.248])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1CFwd5r011215;
	Thu, 12 Feb 2004 15:58:43 GMT
	(envelope-from John.Strassner@intelliden.com)
Received: by cosium01.intelliden.net with Internet Mail Service (5.5.2653.19)
	id <D386KWSW>; Thu, 12 Feb 2004 08:58:28 -0700
Message-ID: <AE723009E85E224CB00132C7FF0B34E1B6F311@cosium02.intelliden.net>
From: John Strassner <John.Strassner@intelliden.com>
To: "'Kurt D. Zeilenga'" <Kurt@OpenLDAP.org>,
        "'Kathleen Dally'"
	 <kdally@mitre.org>
Cc: "'IETF-LDAPbis@OpenLDAP.org'" <IETF-LDAPbis@OpenLDAP.org>
Subject: RE: SUBCLASSING, again
Date: Thu, 12 Feb 2004 08:58:27 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C3F181.0D708920"
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.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_01C3F181.0D708920
Content-Type: text/plain

How can you make an abstract subclass from something that was concrete?
Subclassing means refinement or specialization.

This defies Logic, Object-Oriented Programming, and Common Sense.


regards,
John

John C. Strassner
Chief Strategy Officer
Intelliden Inc.
90 South Cascade Avenue
Colorado Springs, CO  80906  USA
phone:  +1.719.785.0648
  fax:     +1.719.785.0644
email:    john.strassner@intelliden.com



> -----Original Message-----
> From: Kurt D. Zeilenga [mailto:Kurt@OpenLDAP.org] 
> Sent: Wednesday, February 11, 2004 8:04 PM
> To: Kathleen Dally
> Cc: IETF-LDAPbis@OpenLDAP.org
> Subject: Re: SUBCLASSING, again
> 
> 
> At 06:56 PM 2/11/2004, Kathleen Dally wrote:
> >I would have no trouble deleting the sentence from Models, section
> >2.4.3:
> >        " Auxiliary object classes cannot subclass structural object 
> >classes."
> 
> Even though the model makes no sense in face of such constructions?
> 
> >However, I do not believe that the intent to permit Auxiliary object 
> >classes to subclass Structural object classes is as clear in X.501.
> 
> Why?  Since X.501 didn't explicitly disallow this, why do
> you think it clear that the intent was to disallow this?
> 
> Kurt 
> 

------_=_NextPart_001_01C3F181.0D708920
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>RE: SUBCLASSING, again</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>How can you make an abstract subclass from something =
that was concrete? Subclassing means refinement or =
specialization.</FONT>
</P>

<P><FONT SIZE=3D2>This defies Logic, Object-Oriented Programming, and =
Common Sense.</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>regards,</FONT>
<BR><FONT SIZE=3D2>John</FONT>
</P>

<P><FONT SIZE=3D2>John C. Strassner</FONT>
<BR><FONT SIZE=3D2>Chief Strategy Officer</FONT>
<BR><FONT SIZE=3D2>Intelliden Inc.</FONT>
<BR><FONT SIZE=3D2>90 South Cascade Avenue</FONT>
<BR><FONT SIZE=3D2>Colorado Springs, CO&nbsp; 80906&nbsp; USA</FONT>
<BR><FONT SIZE=3D2>phone:&nbsp; +1.719.785.0648</FONT>
<BR><FONT SIZE=3D2>&nbsp; fax:&nbsp;&nbsp;&nbsp;&nbsp; =
+1.719.785.0644</FONT>
<BR><FONT SIZE=3D2>email:&nbsp;&nbsp;&nbsp; =
john.strassner@intelliden.com</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Kurt D. Zeilenga [<A =
HREF=3D"mailto:Kurt@OpenLDAP.org">mailto:Kurt@OpenLDAP.org</A>] </FONT>
<BR><FONT SIZE=3D2>&gt; Sent: Wednesday, February 11, 2004 8:04 =
PM</FONT>
<BR><FONT SIZE=3D2>&gt; To: Kathleen Dally</FONT>
<BR><FONT SIZE=3D2>&gt; Cc: IETF-LDAPbis@OpenLDAP.org</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: Re: SUBCLASSING, again</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; At 06:56 PM 2/11/2004, Kathleen Dally =
wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;I would have no trouble deleting the =
sentence from Models, section</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;2.4.3:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&quot; Auxiliary object classes cannot subclass structural object =
</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;classes.&quot;</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Even though the model makes no sense in face of =
such constructions?</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;However, I do not believe that the intent =
to permit Auxiliary object </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;classes to subclass Structural object =
classes is as clear in X.501.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Why?&nbsp; Since X.501 didn't explicitly =
disallow this, why do</FONT>
<BR><FONT SIZE=3D2>&gt; you think it clear that the intent was to =
disallow this?</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Kurt </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C3F181.0D708920--


From owner-ietf-ldapbis@OpenLDAP.org  Thu Feb 12 16:29:56 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA17077
	for <ldapbis-archive@lists.ietf.org>; Thu, 12 Feb 2004 16:29:55 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1CL8X6R029830;
	Thu, 12 Feb 2004 21:27:58 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1CL4IJB029527;
	Thu, 12 Feb 2004 21:04: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, 12 Feb 2004 21:04:18 +0000
Received: from smtp-bedford.mitre.org (smtp-bedford-x.mitre.org [192.160.51.76])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1CL4D5r029497;
	Thu, 12 Feb 2004 21:04:13 GMT
	(envelope-from kdally@mitre.org)
Received: from smtp-bedford.mitre.org (localhost.localdomain [127.0.0.1])
	by smtp-bedford.mitre.org (8.11.6/8.11.6) with ESMTP id i1CL4CO27662;
	Thu, 12 Feb 2004 16:04:12 -0500
Received: from MAILHUB1 (mailhub1.mitre.org [129.83.20.31])
	by smtp-bedford.mitre.org (8.11.6/8.11.6) with ESMTP id i1CL4CZ27646;
	Thu, 12 Feb 2004 16:04:12 -0500
Received: from mm108631-pc.mitre.org (128.29.3.34) by mailhub1.mitre.org with SMTP
        id 6113930; Thu, 12 Feb 2004 16:04:08 -0500
Message-ID: <402BEA45.D6762FC4@mitre.org>
Date: Thu, 12 Feb 2004 16:04:06 -0500
From: Kathleen Dally <kdally@mitre.org>
Organization: The MITRE Corporation
X-Mailer: Mozilla 4.79 [en]C-20020130M  (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
CC: IETF-LDAPbis@OpenLDAP.org
Subject: Re: SUBCLASSING, again
References: <40296C3C.C1D602A2@mitre.org>
	 <6.0.1.1.0.20040210160558.0498e488@127.0.0.1>
	 <HBF.20040211o9k9@bombur.uio.no>
	 <402ABCB1.CF3C93DF@mitre.org>
	 <6.0.1.1.0.20040211163920.049f4d78@127.0.0.1>
	 <402AEB5F.9DACCE1E@mitre.org>
	 <6.0.1.1.0.20040211185718.049eb830@127.0.0.1>
	 <402AF367.DF52B561@mitre.org> <6.0.1.1.0.20040211202558.049f4d58@127.0.0.1>
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 i1CL4D5r029498
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 8bit

Hi Kurt!

Responses in-line.

Regards,
Kathy


"Kurt D. Zeilenga" wrote:

> At 07:30 PM 2/11/2004, Kathleen Dally wrote:
> >"Kurt D. Zeilenga" wrote:
> >
> >> At 06:56 PM 2/11/2004, Kathleen Dally wrote:
> >> >I would have no trouble deleting the sentence from Models, section
> >> >2.4.3:
> >> >        " Auxiliary object classes cannot subclass structural object
> >> >classes."
> >>
> >> Even though the model makes no sense in face of such
> >> constructions?
> >
> >kd:  I agree that this seems nonsensical.  I haven't seen any use made of
> >such a subclassing.
>
> So, it's okay to disallow this, even though X.501 didn't
> explicitly do so, because they are nonsensical.
>
> One can, and the WG did, apply the same argument to Structural
> Classes which subclass Auxiliaries.  That is, that this is
> nonsensical and hence should be disallowed, as implied by the
> "more generic" statement as well as other aspects of the
> specification.
>

> kd:  By definition of multiple inheritance, a (new) object class can have
> more than one direct superclass.  Nothing is said in the multiple
> inheritance definition about the type of  the superclasses.  In the
> definition of structural, it indicates that only one of the superclasses is
> a structural object class.  Therefore, the other direct superclasses must be
> auxiliary or abstract.  An ENTRY has exactly one structural object class,
> which is in the case of the new object class derived from one structural
> object class and, possibly, auxiliary object classes.

>
> As I noted then (and recently), the alternative is to try to
> make sense of it.  However, that's a tall order (see below).
>
> >> >However, I do not believe that the intent to permit Auxiliary object
> >> >classes to subclass Structural object classes is as clear in X.501.
> >>
> >> Why?  Since X.501 didn't explicitly disallow this, why do
> >> you think it clear that the intent was to disallow this?
> >
> >kd:  The intent that I am speaking about is the nature of Auxiliary
> >Object Classes being a means of augmenting other classes and entries with
> >groups of attributes.
>
> Where in X.501 does it describe Auxiliary object classes as a
> mechanism for extending other classes, in particular, any
> structural class?  In reading 8.3.3, it seems clear the nature
> of Auxiliary object classes is to allow optional augmentation
> of entries.

> Do you see any language anywhere which specifically mentions
> that those constructs are allowed, and, more importantly, any
> text which addresses the special cases which would naturally
> arise from allowance of such constructs?
>

kd:  Could you please give an example of one of the special cases?

> My concern is that there are many statements which, when taken
> together, make little sense if structural classes are allowed
> to subclass auxiliary classes.  Below I elaborate on a few
> instances.
>
> 8.3.3 says:
>   Therefore, besides being a member of the structural object class,
>   an entry may be optionally a member of one or more auxiliary object
>   classes.
> This would have to reworded:
>   Therefore, besides being a member of the structural object class
>   and any auxiliary classes which are superclasses of this
>   structural object class, an entry may be optionally a member of
>   one or more auxiliary object classes.
> to clarify that membership in structural class's superclass
> auxiliary class is not always optional as implied by current text.

kd:  No, the rewording would have to be:
        "Therefore, besides being a member of the structural object class and
any structural, auxiliary, and abstract
         classes which are superclasses of this structural object class, and
entry maybe optional a member of one or
         more auxiliary object classes."
I don't think we need to elaborate the definition of subclassing here.

>
> 8.3.3 continues:
>   An entry’s auxiliary object classes may change over time.
> This would have to reworded:
>   An entry's auxiliary object classes, except those which are
>   superclasses of the entry's structural object class, may
>   change over time.
> as not all the entry's object classes may change over time as
> implied by the current text.

kd:  No, because the statement is about the nature of ENTRIES, not OBJECT
CLASSES.

>
> Before I go on, I note that it's starting to sounding like an
> auxiliary class which is a superclass of the structural object
> class of an entry is to be treated as if it were structural
> in this situation.  But, I note that is counter to 8.3:
>   Each object class is of precisely one of these kinds,
>   and remains of this kind in whatever situation it is
>   encountered within the Directory.
> This section, I think, was intended that special cases were
> not intended.  But we'd have to treat auxiliary classes in this
> situation quite differently from those not in this situation.
>

kd:  No, the nature of the auxiliary class is not changed by being a
superclass.  However, the attributes included in the auxiliary class are
inherited in the new class in the same way as those from any other
superclasses.  (For example, top does not become structural.)

>
> 12.3 says,
>    There shall be one value of the objectClass attribute for
>    the entry’s structural object class and a value for each
>    of its superclasses.
> So, in this situation, the auxiliary superclasses of the
> structural class of the entry are required to be listed as
> objectClass values.

kd:  Yes.

> 12.3 then says:
>       Where auxiliary object classes are used, an entry may
>    contain values of the objectClass attribute for the
>    auxiliary object classes and their superclasses allowed
>    by a DIT content rule.
> which means that in this situation, these auxiliary
> superclasses of the structural class of the entry must in
> listed in the controlling DIT content rule.  And, unsaid,
> this requires there to be a controlling DIT content rule
> in this situation.

kd:  No.  The statement is about ENTRY.  Any auxiliary superclasses of the
structural object classes are not required to be cited in a Content Rule,
because they are already part of the entry under the definition of the
structural object class.

>
>
> 12.7 says:
>   A DIT content rule specifies the permissible content of
>   entries of a particular structural object class via the
>   identification of an optional set of auxiliary object
>   classes, mandatory, optional and precluded attributes.
> That is, only those auxiliary classes in this optional set are
> permissible.

kd:  No.  This statement is discussing the significance of the Content Rule,
which controls auxiliary object classes and attributes beyond the
specification of the structural object class.

>

> 12.7 continues:
>   A DIT content rule definition includes:
>       optionally, an indication of the auxiliary object
>       classes allowed for entries governed by the rule
> That is, if they are listed, the class is "allowed", not
> "required". But from 12.3 we get that auxiliary superclasses
> of the structural class of the entry are actually required
> to be listed and this set is not optional in this situation.
>

kd:  This is a discussion of the Content Rule, not the requirements on the
entry specified by the structural object class.

>
> 12.7 says:
>   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.
> If we consider a DIT content rule which lists as allowed
> only the auxiliary superclasses of the structural class of
> the entry, then the only subset which an entry can be
> associated with is the complete set, not any subset.
>

kd:  Same as above.

>
> There are likely other areas where that would need to
> be revised if such constructs were to be allowed.
>
> In response to your comment:
>
> >For many years, I have been told by implementors that
> >the products do not support Content Rules!
>
> Some do, some don't.  In LDAP, it's viewed as optional.
>
> >Given this fact, if Auxiliary Object Classes could not be
> >superclasses, no Auxiliary Object Classes could never
> >be used.
> kd:  But, the use of auxiliary object classes as superclasses is not
> precluded in X.500.  LDAP is being overly restrictive.

>
> In absence of some extension, as previously discussed
> during WG Last Call, yes.
>
> Many LDAP implementations have extensions in this area.
> However, I'm now aware of any formal specification which
> details how the set of permissible auxiliary classes is
> controlled in absence of DIT content rules.  However, I
> am aware of implementations which, while supporting
> such extensions, do not allow such subclassing constructs.
> This because the constructs are nonsensical even when
> one uses other mechanisms to control which auxiliaries
> may be present (for instance, section 8 concerns above).
>

kd:  I disagree that structural object classes derived from another structural
class and one or more auxiliary or abstract classes is nonsense.  A perfectly
good, useful, structural object class is one, such as, "namedPerson" which
would be defined as:

( x.x.x.x NAME 'namedPerson'
   SUP person, individualName)

( x.x.x.x NAME 'individualName'
   SUP top
   AUXILIARY
   MUST ( givenName $ initials $ generationQualifier ) )

The advantage of using the auxiliary object class in namedPerson (instead of a
MUST list of attributes), is that the individualName object class can be
searched for in the objectClass attribute.

> The question for us is whether implementations which
> claim to support DIT content rules in a manner consistent
> with the existing specification and, if so, how to address
> interoperability and other known technical issues.  It is
> clear that that there are multiple independently developed
> implementations of DIT content rules as described in this
> X.500 and that the clarifications in [Models] go a long way
> towards addressing the known technical issues.
>

kd:  I am NOT disagreeing with the definition of CONTENT RULES or ENTRIES,
only the Models restriction on OBJECT CLASSES.



>
> Kurt





From owner-ietf-ldapbis@OpenLDAP.org  Fri Feb 13 12:54:13 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22787
	for <ldapbis-archive@lists.ietf.org>; Fri, 13 Feb 2004 12:54:12 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1DHie6B092081;
	Fri, 13 Feb 2004 17:53:13 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1DHferF091678;
	Fri, 13 Feb 2004 17:41: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); Fri, 13 Feb 2004 17:41:40 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1DHfd5r091668
	for <IETF-LDAPbis@OpenLDAP.org>; Fri, 13 Feb 2004 17:41:39 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from gypsy.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.10/8.12.10) with ESMTP id i1DHfa7s038796;
	Fri, 13 Feb 2004 17:41:37 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.1.1.0.20040212132508.04962e78@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Fri, 13 Feb 2004 09:41:15 -0800
To: Kathleen Dally <kdally@mitre.org>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: SUBCLASSING, again
Cc: IETF-LDAPbis@OpenLDAP.org
In-Reply-To: <402BEA45.D6762FC4@mitre.org>
References: <40296C3C.C1D602A2@mitre.org>
 <6.0.1.1.0.20040210160558.0498e488@127.0.0.1>
 <HBF.20040211o9k9@bombur.uio.no>
 <402ABCB1.CF3C93DF@mitre.org>
 <6.0.1.1.0.20040211163920.049f4d78@127.0.0.1>
 <402AEB5F.9DACCE1E@mitre.org>
 <6.0.1.1.0.20040211185718.049eb830@127.0.0.1>
 <402AF367.DF52B561@mitre.org>
 <6.0.1.1.0.20040211202558.049f4d58@127.0.0.1>
 <402BEA45.D6762FC4@mitre.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

At 01:04 PM 2/12/2004, Kathleen Dally wrote:
>kd:  Could you please give an example of one of the special cases?

An auxiliary class which would be mandatory for the entry to belong
to (because it was a supertype of the entry's structural class) is
a special case.  Section 8 describes auxiliary classes as supporting
optional augmentation of a entry, and section 12 is relies heavily
upon this.

To make clear in the specification that some auxiliary classes in
some situations are mandatory would require significant rewriting of
these, and possible other (14?), sections.  That was the alternative
I offered to the WG during WG Last Call.  That alternative was rejected.

Kurt




From owner-ietf-ldapbis@OpenLDAP.org  Sun Feb 15 23:42:01 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA13110
	for <ldapbis-archive@lists.ietf.org>; Sun, 15 Feb 2004 23:42:00 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1G4d15v074061;
	Mon, 16 Feb 2004 04:40:29 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1G4Zplc073980;
	Mon, 16 Feb 2004 04:35: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); Mon, 16 Feb 2004 04:35:51 +0000
Received: from prv-mail20.provo.novell.com (prv-mail20.provo.novell.com [137.65.81.122])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1G4Zo5r073965
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 16 Feb 2004 04:35:50 GMT
	(envelope-from jimse@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Sun, 15 Feb 2004 21:35:29 -0700
Message-Id: <s02fe621.079@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.2 Beta
Date: Sun, 15 Feb 2004 21:35:06 -0700
From: "Jim Sermersheim" <jimse@novell.com>
To: <ietf-ldapbis@OpenLDAP.org>
Subject: Re: Outstanding protocol issues
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__Part3A1B476A.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.

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

The last issue I'm tracking is this from a private message from
Hallvard:
 
>> 4.7. Add Operation
>
>>    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.
>
>This is wrong when adding the root entry of the naming context.

 
I believe that the act of adding a context prefix is still under
specified in LDAP (as is the entire distributed data model). But my read
of X.511 says that the ManageDsaIT control is used to add this and other
entries that make up the information tree.
 
I think that when the IETF defines the distributed data model, and the
management of that model, this statement will still be fine (it's just a
SHOULD).
 
Maybe what I'll do is change it to say:
 
In the absence of distributed data management directives, 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.
 
Jim



--=__Part3A1B476A.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 6.00.2800.1400" name=3DGENERATOR></HEAD>
<BODY style=3D"MARGIN: 4px 4px 1px; FONT: 10pt Microsoft Sans Serif">
<DIV style=3D"FONT: 10pt Microsoft Sans Serif; COLOR: #000000">
<DIV>The last issue I'm tracking is this from a private message from =
Hallvard:</DIV>
<DIV>&nbsp;</DIV>
<DIV>&gt;&gt; 4.7. Add Operation</DIV>
<DIV>&gt;</DIV>
<DIV>&gt;&gt;&nbsp;&nbsp;&nbsp; If the parent entry exists<BR>&gt;&gt;&nbsp=
;&nbsp;&nbsp; but is not in a naming context held by the server, the =
server SHOULD<BR>&gt;&gt;&nbsp;&nbsp;&nbsp; return a referral to the =
server holding the parent entry.</DIV>
<DIV>&gt;</DIV>
<DIV>&gt;This is wrong when adding the root entry of the naming context.<BR=
></DIV>
<DIV>&nbsp;</DIV>
<DIV>I believe that the act of adding a context prefix is still under =
specified in LDAP (as is the entire distributed data model). But&nbsp;my =
read of X.511 says that the ManageDsaIT control is used to add this and =
other entries that make up the information tree.</DIV>
<DIV>&nbsp;</DIV>
<DIV>I think that when the IETF defines the distributed data model, and =
the management of that model, this statement will still be fine (it's just =
a SHOULD).</DIV>
<DIV>&nbsp;</DIV>
<DIV>Maybe what I'll do is change it to say:</DIV>
<DIV>
<DIV>&nbsp;</DIV>
<DIV>In the absence of distributed data management directives, 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.</DI=
V>
<DIV>&nbsp;</DIV>
<DIV>Jim</DIV></DIV></DIV></BODY></HTML>

--=__Part3A1B476A.0__=--


From owner-ietf-ldapbis@OpenLDAP.org  Mon Feb 16 00:09:52 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA13754
	for <ldapbis-archive@lists.ietf.org>; Mon, 16 Feb 2004 00:09:52 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1G5915v074633;
	Mon, 16 Feb 2004 05:09:04 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1G550iS074551;
	Mon, 16 Feb 2004 05:05:00 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, 16 Feb 2004 05:05:00 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1G54x5r074541
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 16 Feb 2004 05:04:59 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from gypsy.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.10/8.12.10) with ESMTP id i1G54w7s078969;
	Mon, 16 Feb 2004 05:04:58 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.1.1.0.20040215205257.04b59788@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Sun, 15 Feb 2004 21:04:50 -0800
To: "Jim Sermersheim" <jimse@novell.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: Outstanding protocol issues
Cc: <ietf-ldapbis@OpenLDAP.org>
In-Reply-To: <s02fe621.079@prv-mail20.provo.novell.com>
References: <s02fe621.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 think it could be argued that adding of the context prefix
to DSA is an implementation-specific issue and, hence, beyond
the scope of the specification.

I think the sentence in question was meant to not that where
the entry to add is not within any context this server masters,
and the server has superior knowledge, the server may return
a referral.

I think the sentence should be replaced with something that
captures this.   Additionally, it might be appropriate to say
that establishment of a naming context and addition of an entry
at the context prefix (as well as knowledge information in
the superior context) is not standardized.

Kurt

At 08:35 PM 2/15/2004, Jim Sermersheim wrote:
>The last issue I'm tracking is this from a private message from Hallvard:
> 
>>> 4.7. Add Operation
>>
>>>    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.
>>
>>This is wrong when adding the root entry of the naming context.
> 
>I believe that the act of adding a context prefix is still under specified in LDAP (as is the entire distributed data model). But my read of X.511 says that the ManageDsaIT control is used to add this and other entries that make up the information tree.
> 
>I think that when the IETF defines the distributed data model, and the management of that model, this statement will still be fine (it's just a SHOULD).
> 
>Maybe what I'll do is change it to say:
> 
>In the absence of distributed data management directives, 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.
> 
>Jim



From owner-ietf-ldapbis@OpenLDAP.org  Mon Feb 16 00:39:53 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA14666
	for <ldapbis-archive@lists.ietf.org>; Mon, 16 Feb 2004 00:39:52 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1G5d15v075210;
	Mon, 16 Feb 2004 05:39:09 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1G5YQaG075140;
	Mon, 16 Feb 2004 05:34: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); Mon, 16 Feb 2004 05:34:26 +0000
Received: from prv-mail20.provo.novell.com (prv-mail20.provo.novell.com [137.65.81.122])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1G5Y75r075110;
	Mon, 16 Feb 2004 05:34:07 GMT
	(envelope-from jimse@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Sun, 15 Feb 2004 22:33:47 -0700
Message-Id: <s02ff3cb.097@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.2 Beta
Date: Sun, 15 Feb 2004 22:33:23 -0700
From: "Jim Sermersheim" <jimse@novell.com>
To: <Kurt@OpenLDAP.org>
Cc: <ietf-ldapbis@OpenLDAP.org>
Subject: Re: Outstanding protocol issues
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__Part7D5C0033.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.

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

>>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 2/15/04 10:04:50 PM >>>
>I think it could be argued that adding of the context prefix
>to DSA is an implementation-specific issue and, hence, beyond
>the scope of the specification.
>
>I think the sentence in question was meant to not that where
>the entry to add is not within any context this server masters,
>and the server has superior knowledge, the server may return
>a referral.

or any knowledge (it could be subordinate, or cross as well). Anyway, I
agree. 

>I think the sentence should be replaced with something that
>captures this. 
 
I'll opt for that, rather than the more specific language previously
suggested.
 
>Additionally, it might be appropriate to say
>that establishment of a naming context and addition of an entry
>at the context prefix (as well as knowledge information in
>the superior context) is not standardized.

If we want to go this far, there are other types of IT data that should
be called out (glue, references, etc.). I would rather that [Models]
make a generic statement regarding the non-specification of the
distributed information tree.
 
Jim

>Kurt

>At 08:35 PM 2/15/2004, Jim Sermersheim wrote:
>The last issue I'm tracking is this from a private message from
Hallvard:
> 
>>> 4.7. Add Operation
>>
>>> 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.
>>
>>This is wrong when adding the root entry of the naming context.
> 
>I believe that the act of adding a context prefix is still under
specified in LDAP (as is the entire distributed data model). But my read
of X.511 says that the ManageDsaIT control is used to add this and other
entries that make up the information tree.
> 
>I think that when the IETF defines the distributed data model, and the
management of that model, this statement will still be fine (it's just a
SHOULD).
> 
>Maybe what I'll do is change it to say:
> 
>In the absence of distributed data management directives, 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.
> 
>Jim



--=__Part7D5C0033.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 6.00.2800.1400" name=3DGENERATOR></HEAD>
<BODY style=3D"MARGIN: 4px 4px 1px; FONT: 10pt Microsoft Sans Serif">
<DIV>&gt;&gt;&gt; "Kurt D. Zeilenga" &lt;Kurt@OpenLDAP.org&gt; 2/15/04 =
10:04:50 PM &gt;&gt;&gt;<BR>&gt;I think it could be argued that adding of =
the context prefix<BR>&gt;to DSA is an implementation-specific issue and, =
hence, beyond<BR>&gt;the scope of the specification.<BR>&gt;<BR>&gt;I =
think the sentence in question was meant to not that where<BR>&gt;the =
entry to add is not within any context this server masters,<BR>&gt;and the =
server has superior knowledge, the server may return<BR>&gt;a referral.<BR>=
</DIV>
<DIV>or any knowledge (it could be subordinate, or cross as well). Anyway, =
I agree. </DIV>
<DIV><BR>&gt;I think the sentence should be replaced with something =
that<BR>&gt;captures this. </DIV>
<DIV>&nbsp;</DIV>
<DIV>I'll opt for that, rather than the more specific language previously =
suggested.</DIV>
<DIV>&nbsp;</DIV>
<DIV>&gt;Additionally, it might be appropriate to say<BR>&gt;that =
establishment of a naming context and addition of an entry<BR>&gt;at the =
context prefix (as well as knowledge information in<BR>&gt;the superior =
context) is not standardized.<BR></DIV>
<DIV>If we want to go this far, there are other types of IT data that =
should be called out (glue, references, etc.). I would rather that =
[Models] make a generic statement regarding the non-specification of the =
distributed information tree.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Jim</DIV>
<DIV><BR>&gt;Kurt<BR><BR>&gt;At 08:35 PM 2/15/2004, Jim Sermersheim =
wrote:<BR>&gt;The last issue I'm tracking is this from a private message =
from Hallvard:<BR>&gt; <BR>&gt;&gt;&gt; 4.7. Add Operation<BR>&gt;&gt;<BR>&=
gt;&gt;&gt; If the parent entry exists<BR>&gt;&gt;&gt; but is not in a =
naming context held by the server, the server SHOULD<BR>&gt;&gt;&gt; =
return a referral to the server holding the parent entry.<BR>&gt;&gt;<BR>&g=
t;&gt;This is wrong when adding the root entry of the naming context.<BR>&g=
t; <BR>&gt;I believe that the act of adding a context prefix is still =
under specified in LDAP (as is the entire distributed data model). But my =
read of X.511 says that the ManageDsaIT control is used to add this and =
other entries that make up the information tree.<BR>&gt; <BR>&gt;I think =
that when the IETF defines the distributed data model, and the management =
of that model, this statement will still be fine (it's just a SHOULD).<BR>&=
gt; <BR>&gt;Maybe what I'll do is change it to say:<BR>&gt; <BR>&gt;In the =
absence of distributed data management directives, 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.<BR>&gt; =
<BR>&gt;Jim<BR><BR></DIV></BODY></HTML>

--=__Part7D5C0033.0__=--


From owner-ietf-ldapbis@OpenLDAP.org  Mon Feb 16 02:16:44 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA29604
	for <ldapbis-archive@lists.ietf.org>; Mon, 16 Feb 2004 02:16:43 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1G7F25v078002;
	Mon, 16 Feb 2004 07:15:22 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1G79kUC077868;
	Mon, 16 Feb 2004 07:09: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); Mon, 16 Feb 2004 07:09:46 +0000
Received: from prv-mail20.provo.novell.com (prv-mail20.provo.novell.com [137.65.81.122])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1G79g5r077820;
	Mon, 16 Feb 2004 07:09:42 GMT
	(envelope-from RHARRISON@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Mon, 16 Feb 2004 00:09:22 -0700
Message-Id: <s0300a32.092@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.2 Beta
Date: Mon, 16 Feb 2004 00:08:57 -0700
From: "Roger Harrison" <RHARRISON@novell.com>
To: <Kurt@OpenLDAP.org>, <h.b.furuseth@usit.uio.no>
Cc: <ietf-ldapbis@OpenLDAP.org>
Subject: Re: Revisited: effect of Start TLS on authentication state
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__PartEDCC9099.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.

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

I believe I have represented the discussion consensus on this issue for
the -10 draft of authmeth.
 
For TLS Connection Establishment Effects:
 
"The decision to keep or invalidate the established authentication and
authorization identities in place after TLS is negotiated is a matter of
local server policy."
 
For TLS Connection Closure Effects
 
"The decision to keep or invalidate the established authentication and
authorization identities in place after TLS closure is a matter of local
server policy."
 
And I've added this new section:
 
"Invalidated Associations
 
"The server may, at any time, invalidate the association, e.g. if the
established security association between the client and server has
unexpectedly failed or been compromised.  The association remains
invalidated until the next successful bind request.  While the
association is invalidated, the server may reject any operation request
other than Bind, Unbind, and Start TLS by responding with a resultCode
of strongAuthRequired to indicate that the client needs to bind to
reestablish its authentication state before performing the requested
operation."
 
Roger


>>> Hallvard B Furuseth <h.b.furuseth@usit.uio.no> 12/10/2003 2:47:44
AM >>>
Kurt D. Zeilenga writes:
> I don't see any reason to keep a MUST which few if anyone has ever
> implemented

No, if it's largely unimplemented I have no objection to the change.
I do agree the new TLS Closure behavior is better.

That leaves one concern of mine: SHOULD invalidate association after
StartTLS unless other security layers are in place, or unless the TLS
cipersuite is weak (null?). Should we add that, or not, or just
suggest
it in Security Considerations? I'm not quite sure if you were talking
about that or about TLS closure in some parts of your reply:-)


About invalidated associations:

At 02:31 AM 12/9/2003, Hallvard B Furuseth wrote:

>> When the association is invalidated, the server it MUST reject
>> subsequent operation requests other than Bind, Unbind and Start
TLS,
>> and respond with a resultCode of strongAuthRequired to indicate
that
>> the client needs to bind to reestablish its authentication.
> 
> I'm a little concerned that of the overload here. strongAuthRequired
> means, generally, that stronger authentication is required. Now,
> that could be due to the invalidation of the association, but it
could
> be due to any number of other reasons. Additionally, the server
could
> be willing, after invalidating the association, to continue to allow
> the client to attempt operations which don't require that
association.

All true, but maybe this is the best LDAPv3 can do. What we need is a
new error code, or at least to rename strongAuthRequired, but I take
it
that's out of scope for ldapbis. A new code certainly is.

> The MUST here is actually extraneous.

As I said in the previous message, I agree. The MUST is OK if we
change
[Protocol] to match. Otherwise I suggest to delete it (not just
lowercase it) and add a sentence about servers being allowed to return
strongAuthRequired in other circumstances too. See my previous
message.

-- 
Hallvard


--=__PartEDCC9099.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 6.00.2800.1400" name=3DGENERATOR></HEAD>
<BODY style=3D"MARGIN: 4px 4px 1px; FONT: 10pt Tahoma">
<DIV>I believe I have represented the discussion consensus on this issue =
for the -10 draft of authmeth.</DIV>
<DIV>&nbsp;</DIV>
<DIV>For TLS Connection Establishment Effects:</DIV>
<DIV>&nbsp;</DIV>
<DIV>"The decision to keep or invalidate the established authentication =
and authorization identities in place after TLS is negotiated is a matter =
of local server policy."</DIV>
<DIV>&nbsp;</DIV>
<DIV>For TLS Connection Closure Effects</DIV>
<DIV>&nbsp;</DIV>
<DIV>"The decision to keep or invalidate the established authentication =
and authorization identities in place after TLS closure is a matter of =
local server policy."</DIV>
<DIV>&nbsp;</DIV>
<DIV>And I've added this new section:</DIV>
<DIV>&nbsp;</DIV>
<DIV>"Invalidated Associations</DIV>
<DIV>&nbsp;</DIV>
<DIV>"The server may, at any time, invalidate the association, e.g. if the =
established security association between the client and server has =
unexpectedly failed or been compromised.&nbsp; The association remains =
invalidated until the next successful bind request.&nbsp; While the =
association is invalidated, the server may reject any operation request =
other than Bind, Unbind, and Start TLS by responding with a resultCode of =
strongAuthRequired to indicate that the client needs to bind to reestablish=
 its authentication state before performing the requested operation."</DIV>=

<DIV>&nbsp;</DIV>
<DIV>Roger<BR><BR><BR>&gt;&gt;&gt; Hallvard B Furuseth &lt;h.b.furuseth@usi=
t.uio.no&gt; 12/10/2003 2:47:44 AM &gt;&gt;&gt;<BR>Kurt D. Zeilenga =
writes:<BR>&gt; I don't see any reason to keep a MUST which few if anyone =
has ever<BR>&gt; implemented<BR><BR>No, if it's largely unimplemented I =
have no objection to the change.<BR>I do agree the new TLS Closure =
behavior is better.<BR><BR>That leaves one concern of mine: SHOULD =
invalidate association after<BR>StartTLS unless other security layers are =
in place, or unless the TLS<BR>cipersuite is weak (null?). Should we add =
that, or not, or just suggest<BR>it in Security Considerations? I'm not =
quite sure if you were talking<BR>about that or about TLS closure in some =
parts of your reply:-)<BR><BR><BR>About invalidated associations:<BR><BR>At=
 02:31 AM 12/9/2003, Hallvard B Furuseth wrote:<BR><BR>&gt;&gt; When the =
association is invalidated, the server it MUST reject<BR>&gt;&gt; =
subsequent operation requests other than Bind, Unbind and Start TLS,<BR>&gt=
;&gt; and respond with a resultCode of strongAuthRequired to indicate =
that<BR>&gt;&gt; the client needs to bind to reestablish its authentication=
.<BR>&gt; <BR>&gt; I'm a little concerned that of the overload here. =
strongAuthRequired<BR>&gt; means, generally, that stronger authentication =
is required. Now,<BR>&gt; that could be due to the invalidation of the =
association, but it could<BR>&gt; be due to any number of other reasons. =
Additionally, the server could<BR>&gt; be willing, after invalidating the =
association, to continue to allow<BR>&gt; the client to attempt operations =
which don't require that association.<BR><BR>All true, but maybe this is =
the best LDAPv3 can do. What we need is a<BR>new error code, or at least =
to rename strongAuthRequired, but I take it<BR>that's out of scope for =
ldapbis. A new code certainly is.<BR><BR>&gt; The MUST here is actually =
extraneous.<BR><BR>As I said in the previous message, I agree. The MUST is =
OK if we change<BR>[Protocol] to match. Otherwise I suggest to delete it =
(not just<BR>lowercase it) and add a sentence about servers being allowed =
to return<BR>strongAuthRequired in other circumstances too. See my =
previous message.<BR><BR>-- <BR>Hallvard<BR></DIV></BODY></HTML>

--=__PartEDCC9099.0__=--


From owner-ietf-ldapbis@OpenLDAP.org  Mon Feb 16 02:33:48 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA01851
	for <ldapbis-archive@lists.ietf.org>; Mon, 16 Feb 2004 02:33:48 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1G7X25v079097;
	Mon, 16 Feb 2004 07:33:05 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1G7WV3q079085;
	Mon, 16 Feb 2004 07:32: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); Mon, 16 Feb 2004 07:32:31 +0000
Received: from prv-mail20.provo.novell.com (prv-mail20.provo.novell.com [137.65.81.122])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1G7WU5r079075
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 16 Feb 2004 07:32:30 GMT
	(envelope-from RHARRISON@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Mon, 16 Feb 2004 00:32:09 -0700
Message-Id: <s0300f89.025@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.2 Beta
Date: Mon, 16 Feb 2004 00:31:47 -0700
From: "Roger Harrison" <RHARRISON@novell.com>
To: <ietf-ldapbis@OpenLDAP.org>, <h.b.furuseth@usit.uio.no>
Subject: Re: authmeth-07 issues
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__Part9ABBE7F3.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.

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


With the fairly extensive reworking of the effect of Start TLS and TLS
closure on the LDAP association state, I'm wondering how WG members view
the need for these security considerations proposed by Hallvard.  Your
comments are greatly appreciated.
 
Roger

>>> Hallvard B Furuseth <h.b.furuseth@usit.uio.no> 10/14/2003 8:11:28
AM >>>
> 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.




--=__Part9ABBE7F3.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 6.00.2800.1400" name=3DGENERATOR></HEAD>
<BODY style=3D"MARGIN: 4px 4px 1px; FONT: 10pt Tahoma"><BR>
<DIV>With the fairly extensive reworking of the effect of Start TLS and =
TLS closure on the LDAP association state, I'm wondering how WG members =
view the need for these security considerations proposed by Hallvard.&nbsp;=
 Your comments are greatly appreciated.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Roger<BR></DIV>
<DIV>&gt;&gt;&gt; Hallvard B Furuseth &lt;h.b.furuseth@usit.uio.no&gt; =
10/14/2003 8:11:28 AM &gt;&gt;&gt;<BR>&gt; 10. Security Considerations<BR><=
BR>I think you should say that if the connection is already bound =
when<BR>startTLS is performed, servers SHOULD reject operations that =
follow<BR>StartTLS other than bind, unbind and abandon (with strongAuthRequ=
ired?).<BR><BR>bind before startTLS is an insecure combination, and that =
an attacker<BR>also may insert a bind before a startTLS when the client =
expects to do<BR>anonymous operations with TLS.<BR><BR>Or SHOULD the =
server reject these operations even if the connection is<BR>anonymous? The =
attacker could have inserted an anonymous bind, though<BR>that doesn't =
seem like much of a problem.<BR><BR></DIV><BR></BODY></HTML>

--=__Part9ABBE7F3.0__=--


From owner-ietf-ldapbis@OpenLDAP.org  Mon Feb 16 03:06:08 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA03900
	for <ldapbis-archive@lists.ietf.org>; Mon, 16 Feb 2004 03:06:07 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1G8325v080727;
	Mon, 16 Feb 2004 08:03:28 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1G80aJ7080704;
	Mon, 16 Feb 2004 08:00: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, 16 Feb 2004 08:00:36 +0000
Received: from prv-mail20.provo.novell.com (prv-mail20.provo.novell.com [137.65.81.122])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1G80U5r080657;
	Mon, 16 Feb 2004 08:00:30 GMT
	(envelope-from RHARRISON@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Mon, 16 Feb 2004 01:00:09 -0700
Message-Id: <s0301619.077@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.2 Beta
Date: Mon, 16 Feb 2004 00:59:14 -0700
From: "Roger Harrison" <RHARRISON@novell.com>
To: <Kurt@OpenLDAP.org>, <h.b.furuseth@usit.uio.no>
Cc: <ietf-ldapbis@OpenLDAP.org>
Subject: Re: names of RFC references (was: models-09 comments)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__Part22035F42.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.

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

I haven't seen any further comments on this subject, so I'll jump in.
I've attempted to at least make AuthMeth consistent with itself and with
Protocol in the -10 draft by using descriptive names for all
references.
 
I had assumed that since we are using descriptive names for the LDAP TS
that it would make sense to use them everywhere. I realize that the RFC
editor could replace descriptive names of LDAP TS  docs with their RFCs
as the RFC numbers are assigned, but I'd prefer leaving descriptive
names throughout.
 
Roger

>>> Hallvard B Furuseth <h.b.furuseth@usit.uio.no> 1/8/2004 1:46:32 PM
>>>
Kurt D. Zeilenga writes:
>At 09:39 AM 1/7/2004, Hallvard B Furuseth wrote:
>
>> It would be nice if the LDAPbis documents had more or less
>> the same reference names for the same documents, at least
>> for references to LDAPbis documents.
>
> Yes. I hope we can leave it to the Editors to determine
> exactly what LDAPBIS style is.

Yes, I'd have posted this to the ietf-ldapbis-editors mailinglist if
it
existed:-)

>> I'll post a list of differences between reference names is
>> anyone is interested.
>
> Pointing out differences in style (where it matters) is
> useful.

I don't know what of this matters, but:

Reference name styles:

[BCP64bis], [LDAPDN], [LDAPURL], [Models], [Roadmap], [Schema],
[Strprep] use document numbers: [RFC2234], [X.690].

[Protocol] uses descriptive names: [ABNF], [BER].

[AuthMeth] prefers document numbers, but also has [ABNF] and [UTF-8].

[Filters] uses document numbers for RFCs, but also has [ASN.1].

[Syntaxes] uses descriptive names, except it also needs names like
[BCP64], [RFC2256] for older documents.

Nobody call [X.500], [T.50] & co anything interesting:-)

[Syntaxes] and partly [Schema] use uppercased descriptive names
for internet-drafts and RFCs. The other documents do not.

Name conflict:

[Filters] calls X.690 '[ASN.1]', while [Protocol] and [Syntaxes] call
X.680 '[ASN.1]'. That is confusing. I suggest [Filters] calls X.690
[BER], as [Protocol] and [Syntaxes] do.

URL styles:

[LDAPDN] uses the approximate URL < http://www.iana.org/ ...>.
[BCP64bis] only refers to the web site < http://www.iana.org/ > for
the
registry (outside a reference). URLs in other places, including IANA
URLs, are complete.

Other details:

The [UTF-8] or [UTF8] reference is outdated in many drafts.
It is now an RFC, not an internet-draft:
Yergeau, F., "UTF-8, a transformation format of ISO 10646",
STD 63 and RFC 3629, November 2003.

Reference descriptions in [LDAPURL], [Filters] and partly [AuthMeth]
are not indented out from the reference names, which makes searching
for a reference slower.

Some reference names are also descriptive words in the text, which
will be lost if the reference is renamed. E.g. the phrases '[UTF-8]
encoded' in [AuthMeth] and '[TLS]-protected' in [Protocol]. I'll
scan for more if you are interested.

The reference name [BCP64bis] will have to be renamed, since the
name implies an unfinished document. Hopefully it will be finished
someday:-)

-- 
Hallvard


--=__Part22035F42.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 6.00.2800.1400" name=3DGENERATOR></HEAD>
<BODY style=3D"MARGIN: 4px 4px 1px; FONT: 10pt Tahoma">
<DIV>I haven't seen any further comments on this subject, so I'll jump in. =
I've attempted to at least make AuthMeth consistent with itself and with =
Protocol in the -10 draft by using descriptive names for all references.</D=
IV>
<DIV>&nbsp;</DIV>
<DIV>I had assumed that since we are using descriptive names for the LDAP =
TS that it would make sense to use them everywhere. I realize that the RFC =
editor could replace descriptive names of LDAP TS&nbsp; docs with their =
RFCs as the RFC numbers are assigned, but I'd prefer leaving descriptive =
names throughout.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Roger<BR><BR>&gt;&gt;&gt; Hallvard B Furuseth &lt;h.b.furuseth@usit.ui=
o.no&gt; 1/8/2004 1:46:32 PM &gt;&gt;&gt;<BR>Kurt D. Zeilenga writes:<BR>&g=
t;At 09:39 AM 1/7/2004, Hallvard B Furuseth wrote:<BR>&gt;<BR>&gt;&gt; It =
would be nice if the LDAPbis documents had more or less<BR>&gt;&gt; the =
same reference names for the same documents, at least<BR>&gt;&gt; for =
references to LDAPbis documents.<BR>&gt;<BR>&gt; Yes. I hope we can leave =
it to the Editors to determine<BR>&gt; exactly what LDAPBIS style =
is.<BR><BR>Yes, I'd have posted this to the ietf-ldapbis-editors mailinglis=
t if it<BR>existed:-)<BR><BR>&gt;&gt; I'll post a list of differences =
between reference names is<BR>&gt;&gt; anyone is interested.<BR>&gt;<BR>&gt=
; Pointing out differences in style (where it matters) is<BR>&gt; =
useful.<BR><BR>I don't know what of this matters, but:<BR><BR>Reference =
name styles:<BR><BR>[BCP64bis], [LDAPDN], [LDAPURL], [Models], [Roadmap], =
[Schema],<BR>[Strprep] use document numbers: [RFC2234], [X.690].<BR><BR>[Pr=
otocol] uses descriptive names: [ABNF], [BER].<BR><BR>[AuthMeth] prefers =
document numbers, but also has [ABNF] and [UTF-8].<BR><BR>[Filters] uses =
document numbers for RFCs, but also has [ASN.1].<BR><BR>[Syntaxes] uses =
descriptive names, except it also needs names like<BR>[BCP64], [RFC2256] =
for older documents.<BR><BR>Nobody call [X.500], [T.50] &amp; co anything =
interesting:-)<BR><BR>[Syntaxes] and partly [Schema] use uppercased =
descriptive names<BR>for internet-drafts and RFCs. The other documents do =
not.<BR><BR>Name conflict:<BR><BR>[Filters] calls X.690 '[ASN.1]', while =
[Protocol] and [Syntaxes] call<BR>X.680 '[ASN.1]'. That is confusing. I =
suggest [Filters] calls X.690<BR>[BER], as [Protocol] and [Syntaxes] =
do.<BR><BR>URL styles:<BR><BR>[LDAPDN] uses the approximate URL &lt;<U> <A =
href=3D"http://www.iana.org/">http://www.iana.org/</A></U> ...&gt;.<BR>[BCP=
64bis] only refers to the web site &lt;<U> <A href=3D"http://www.iana.org/"=
>http://www.iana.org/</A></U> &gt; for the<BR>registry (outside a =
reference). URLs in other places, including IANA<BR>URLs, are complete.<BR>=
<BR>Other details:<BR><BR>The [UTF-8] or [UTF8] reference is outdated in =
many drafts.<BR>It is now an RFC, not an internet-draft:<BR>Yergeau, F., =
"UTF-8, a transformation format of ISO 10646",<BR>STD 63 and RFC 3629, =
November 2003.<BR><BR>Reference descriptions in [LDAPURL], [Filters] and =
partly [AuthMeth]<BR>are not indented out from the reference names, which =
makes searching<BR>for a reference slower.<BR><BR>Some reference names are =
also descriptive words in the text, which<BR>will be lost if the reference =
is renamed. E.g. the phrases '[UTF-8]<BR>encoded' in [AuthMeth] and =
'[TLS]-protected' in [Protocol]. I'll<BR>scan for more if you are =
interested.<BR><BR>The reference name [BCP64bis] will have to be renamed, =
since the<BR>name implies an unfinished document. Hopefully it will be =
finished<BR>someday:-)<BR><BR>-- <BR>Hallvard<BR></DIV></BODY></HTML>

--=__Part22035F42.0__=--


From owner-ietf-ldapbis@OpenLDAP.org  Mon Feb 16 03:16:04 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA04253
	for <ldapbis-archive@lists.ietf.org>; Mon, 16 Feb 2004 03:16:03 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1G8F261081393;
	Mon, 16 Feb 2004 08:15:06 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1G8EJJd081373;
	Mon, 16 Feb 2004 08:14: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); Mon, 16 Feb 2004 08:14:18 +0000
Received: from prv-mail20.provo.novell.com (prv-mail20.provo.novell.com [137.65.81.122])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1G8EG5r081299;
	Mon, 16 Feb 2004 08:14:16 GMT
	(envelope-from RHARRISON@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Mon, 16 Feb 2004 01:13:56 -0700
Message-Id: <s0301954.005@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.2 Beta
Date: Mon, 16 Feb 2004 01:13:30 -0700
From: "Roger Harrison" <RHARRISON@novell.com>
To: <Kurt@OpenLDAP.org>, <h.b.furuseth@usit.uio.no>
Cc: <ietf-ldapbis@OpenLDAP.org>
Subject: Re: authmeth-09 comments
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__PartD9F8A4BA.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.

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

Kurt,
 
Is your concern regarding the lack of attention to the tables directed
to WG members in general or from me? I reworked the tables completely
for the -09 draft and feel quite confident that they are much better
than they have ever been before. I would appreciate some more eyes on
them at this point, but I reviewed every production in the tables for
the -09 draft.
 
Roger

>>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 1/8/2004 5:45:45 PM >>>

I believe some find the table useful. Personally, I worry that the
table might not accurately reflect the prose. (As co-chair, I'm
concerned by the lack of attention the tables are getting.)

Kurt



--=__PartD9F8A4BA.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 6.00.2800.1400" name=3DGENERATOR></HEAD>
<BODY style=3D"MARGIN: 4px 4px 1px; FONT: 10pt Tahoma">
<DIV>Kurt,</DIV>
<DIV>&nbsp;</DIV>
<DIV>Is your concern regarding the lack of attention to the tables =
directed to WG members in general or from me? I reworked the tables =
completely for the -09 draft and feel quite confident that they are much =
better than they have ever been before. I would appreciate some more eyes =
on them at this point, but I reviewed every production in the tables for =
the -09 draft.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Roger<BR><BR>&gt;&gt;&gt; "Kurt D. Zeilenga" &lt;Kurt@OpenLDAP.org&gt;=
 1/8/2004 5:45:45 PM &gt;&gt;&gt;<BR><BR>I believe some find the table =
useful. Personally, I worry that the<BR>table might not accurately reflect =
the prose. (As co-chair, I'm<BR>concerned by the lack of attention the =
tables are getting.)<BR><BR>Kurt<BR><BR></DIV></BODY></HTML>

--=__PartD9F8A4BA.0__=--


From owner-ietf-ldapbis@OpenLDAP.org  Mon Feb 16 03:16:06 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA04271
	for <ldapbis-archive@lists.ietf.org>; Mon, 16 Feb 2004 03:16:06 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1G8F263081393;
	Mon, 16 Feb 2004 08:15:06 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1G895iP081086;
	Mon, 16 Feb 2004 08:09: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); Mon, 16 Feb 2004 08:09:05 +0000
Received: from prv-mail20.provo.novell.com (prv-mail20.provo.novell.com [137.65.81.122])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1G8925r080972;
	Mon, 16 Feb 2004 08:09:02 GMT
	(envelope-from RHARRISON@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Mon, 16 Feb 2004 01:08:42 -0700
Message-Id: <s030181a.093@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.2 Beta
Date: Mon, 16 Feb 2004 01:08:17 -0700
From: "Roger Harrison" <RHARRISON@novell.com>
To: <Kurt@OpenLDAP.org>, <h.b.furuseth@usit.uio.no>
Cc: <ietf-ldapbis@OpenLDAP.org>
Subject: Re: authmeth-09 comments
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__Part03227E61.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.

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

The state tables were originally created in response to general demand
for them by WG members. I had assumed that while not normative, they
could be used by implementers to verify the basic state transitions
followed by their servers. At this point, I've moved them to an appendix
and added wording to indicate that they are informative. If WG consensus
is that they have no significant future value, I'm glad to pull them
out. This is one case, however, where I would like to base the decision
on explicit discussion rather than silence due to their origins stemming
from WG feedback.
 
Roger

>>> Hallvard B Furuseth h.b.furuseth@usit.uio.no> 1/8/2004 3:34:05 PM
>>
>>> 8. LDAP Association State Transition Tables
>>
>>The more I look at this section, the less I like it... How about
>>moving it to a non-normative appendix? I *really* hope this section
>>doesn't contain any information which must be read and can't be seen
>>elsewhere in the draft.
> 
> I concur that these tables should be moved to an Informative
> appendix (or section). Implementators should not need to grok
> these tables to properly implement the protocol. The tables
> should be informative, provided to help the implementor to
> understand the prose.

So far, I find the prose far easier to track than the table, so my
_real_ preference is for the table to be deleted. Roger didn't
dignify that suggestion with a reply when he replied to the message
suggesting that, though... OTOH, nobody spoke up and said 'yes, I
find the table useful':-)

-- 
Hallvard


--=__Part03227E61.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 6.00.2800.1400" name=3DGENERATOR></HEAD>
<BODY style=3D"MARGIN: 4px 4px 1px; FONT: 10pt Tahoma">
<DIV>The state tables were originally created in response to general =
demand for them by WG members. I had assumed that while not normative, =
they could be used by implementers to verify the basic state transitions =
followed by their servers. At this point, I've moved them to an appendix =
and added wording to indicate that they are informative. If WG consensus =
is that they have no significant future value, I'm glad to pull them out. =
This is one case, however, where I would like to base the decision on =
explicit discussion rather than silence due to their origins stemming from =
WG feedback.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Roger</DIV>
<DIV><BR>&gt;&gt;&gt; Hallvard B Furuseth <A href=3D"mailto:h.b.furuseth@us=
it.uio.no> 1/8/2004 3:34:05 PM >>">h.b.furuseth@usit.uio.no&gt; 1/8/2004 =
3:34:05 PM &gt;&gt;</A><BR>&gt;&gt;&gt; 8. LDAP Association State =
Transition Tables<BR>&gt;&gt;<BR>&gt;&gt;The more I look at this section, =
the less I like it... How about<BR>&gt;&gt;moving it to a non-normative =
appendix? I *really* hope this section<BR>&gt;&gt;doesn't contain any =
information which must be read and can't be seen<BR>&gt;&gt;elsewhere in =
the draft.<BR>&gt; <BR>&gt; I concur that these tables should be moved to =
an Informative<BR>&gt; appendix (or section). Implementators should not =
need to grok<BR>&gt; these tables to properly implement the protocol. The =
tables<BR>&gt; should be informative, provided to help the implementor =
to<BR>&gt; understand the prose.<BR><BR>So far, I find the prose far =
easier to track than the table, so my<BR>_real_ preference is for the =
table to be deleted. Roger didn't<BR>dignify that suggestion with a reply =
when he replied to the message<BR>suggesting that, though... OTOH, nobody =
spoke up and said 'yes, I<BR>find the table useful':-)<BR><BR>-- <BR>Hallva=
rd<BR></DIV></BODY></HTML>

--=__Part03227E61.0__=--


From owner-ietf-ldapbis@OpenLDAP.org  Mon Feb 16 03:21:57 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA04502
	for <ldapbis-archive@lists.ietf.org>; Mon, 16 Feb 2004 03:21:57 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1G8L25v081785;
	Mon, 16 Feb 2004 08:21:05 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1G8HhgA081534;
	Mon, 16 Feb 2004 08:17: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, 16 Feb 2004 08:17:43 +0000
Received: from prv-mail20.provo.novell.com (prv-mail20.provo.novell.com [137.65.81.122])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1G8He5r081496;
	Mon, 16 Feb 2004 08:17:40 GMT
	(envelope-from RHARRISON@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Mon, 16 Feb 2004 01:17:20 -0700
Message-Id: <s0301a20.015@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.2 Beta
Date: Mon, 16 Feb 2004 01:16:56 -0700
From: "Roger Harrison" <RHARRISON@novell.com>
To: <Kurt@OpenLDAP.org>, <h.b.furuseth@usit.uio.no>
Cc: <ietf-ldapbis@OpenLDAP.org>
Subject: Re: authmeth-09 comments
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__Part0C2D7168.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.

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

Kurt,
 
Could you provide some details about what you mean by this phrase?  I
added the idea to the -10 draft several weeks ago, but I'm still not
sure I know what these words mean to you.
 
Thanks,
 
Roger

>>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 1/6/2004 1:55:45 PM >>>
(8) Hijacking of protocol sessions.




--=__Part0C2D7168.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 6.00.2800.1400" name=3DGENERATOR></HEAD>
<BODY style=3D"MARGIN: 4px 4px 1px; FONT: 10pt Tahoma">
<DIV>Kurt,</DIV>
<DIV>&nbsp;</DIV>
<DIV>Could you provide some details about what you mean by this phrase?&nbs=
p; I added the idea to the -10 draft several weeks ago, but I'm still not =
sure I know what these words mean to you.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Thanks,</DIV>
<DIV>&nbsp;</DIV>
<DIV>Roger<BR><BR>&gt;&gt;&gt; "Kurt D. Zeilenga" &lt;Kurt@OpenLDAP.org&gt;=
 1/6/2004 1:55:45 PM &gt;&gt;&gt;<BR>(8) Hijacking of protocol sessions.<BR=
><BR><BR></DIV></BODY></HTML>

--=__Part0C2D7168.0__=--


From owner-ietf-ldapbis@OpenLDAP.org  Mon Feb 16 04:10:05 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07080
	for <ldapbis-archive@lists.ietf.org>; Mon, 16 Feb 2004 04:10:04 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1G99261083186;
	Mon, 16 Feb 2004 09:09:16 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1G98X1a083160;
	Mon, 16 Feb 2004 09:08: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, 16 Feb 2004 09:08:33 +0000
Received: from prv-mail20.provo.novell.com (prv-mail20.provo.novell.com [137.65.81.122])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1G98V5r083142
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 16 Feb 2004 09:08:31 GMT
	(envelope-from RHARRISON@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Mon, 16 Feb 2004 02:08:22 -0700
Message-Id: <s0302616.063@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.2 Beta
Date: Mon, 16 Feb 2004 02:08:03 -0700
From: "Roger Harrison" <RHARRISON@novell.com>
To: <ietf-ldapbis@OpenLDAP.org>, <h.b.furuseth@usit.uio.no>
Subject: Re: authmeth: unsupported <TLS+anonymous bind>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__PartF3D28E63.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.

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

For authmeth -10, the single, consolidated section on anonymous
authentication now states that LDAP implementations MUST support
anonymous authentication with no other qualifications. The fact that
Start TLS is a required-to-implement operation implies that
implementations MUST support anonymous authentication when TLS is
established.
 
Roger

>>> Hallvard B Furuseth <h.b.furuseth@usit.uio.no> 1/3/2004 7:34:17 AM
>>>
authmeth-09 says:

> 5. Anonymous Authentication

> LDAP implementations MUST support anonymous authentication, as
> defined in section 5.1.
>
> LDAP implementations MAY support anonymous authentication with TLS,
> as defined in section 5.2.

Huh? Why allow implementations to not support anonymous
authentication on secure connections, but support it on insecure
ones? I could understand it if it was the other way around - along
with not implementing Simple Bind at all without TLS.

-- 
Hallvard


--=__PartF3D28E63.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 6.00.2800.1400" name=3DGENERATOR></HEAD>
<BODY style=3D"MARGIN: 4px 4px 1px; FONT: 10pt Tahoma">
<DIV>For authmeth -10, the single, consolidated section on anonymous =
authentication now states that LDAP implementations MUST support anonymous =
authentication with no other qualifications. The fact that Start TLS is a =
required-to-implement operation implies that implementations MUST support =
anonymous authentication when TLS is established.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Roger<BR><BR>&gt;&gt;&gt; Hallvard B Furuseth &lt;h.b.furuseth@usit.ui=
o.no&gt; 1/3/2004 7:34:17 AM &gt;&gt;&gt;<BR>authmeth-09 says:<BR><BR>&gt; =
5. Anonymous Authentication<BR><BR>&gt; LDAP implementations MUST support =
anonymous authentication, as<BR>&gt; defined in section 5.1.<BR>&gt;<BR>&gt=
; LDAP implementations MAY support anonymous authentication with TLS,<BR>&g=
t; as defined in section 5.2.<BR><BR>Huh? Why allow implementations to not =
support anonymous<BR>authentication on secure connections, but support it =
on insecure<BR>ones? I could understand it if it was the other way around =
- along<BR>with not implementing Simple Bind at all without TLS.<BR><BR>-- =
<BR>Hallvard<BR></DIV></BODY></HTML>

--=__PartF3D28E63.0__=--


From owner-ietf-ldapbis@OpenLDAP.org  Mon Feb 16 04:10:07 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07103
	for <ldapbis-archive@lists.ietf.org>; Mon, 16 Feb 2004 04:10:07 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1G99263083186;
	Mon, 16 Feb 2004 09:09:17 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1G94Za3083011;
	Mon, 16 Feb 2004 09:04: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, 16 Feb 2004 09:04:35 +0000
Received: from prv-mail20.provo.novell.com (prv-mail20.provo.novell.com [137.65.81.122])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1G94X5r082998
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 16 Feb 2004 09:04:34 GMT
	(envelope-from RHARRISON@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Mon, 16 Feb 2004 02:04:13 -0700
Message-Id: <s030251d.050@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.2 Beta
Date: Mon, 16 Feb 2004 02:03:56 -0700
From: "Roger Harrison" <RHARRISON@novell.com>
To: <ietf-ldapbis@OpenLDAP.org>, <h.b.furuseth@usit.uio.no>
Subject: Re: authmeth: missing protection
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__PartF3D28E6C.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.

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


> >>> Hallvard B Furuseth <h.b.furuseth@usit.uio.no> 1/3/2004 7:34:57
AM >>>
> authmeth-09 says:
> 
> > 6.2. Digest Authentication
> >
> > (...) [DIGEST-MD5]. This provides client
> > authentication with protection against passive eavesdropping
> > attacks, but does not provide protection against active
intermediary
> > attacks.
> 
> What does this mean? That DIGEST-MD5 is vulnerable to
> man-in-the-middle attacks? I didn't think it was.
 
I don't have enough experience with Digest Authentication to speak to
this. Can someone else in the WG please comment?

> 
> BTW, maybe 'simple anonymous bind' should be 'simple anonymous or
> unauthenticated bind'.
> 
> It goes on to say:
> 
> > 10.1. Start TLS Security Considerations
> 
> > 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.
> 
> I don't understand. I thought confidentiality was exactly one of
> the things TLS was for.
 
I think the point is that TLS protects the data in transit between
client and server, but it can't do anything to protect the data at the
point it is housed. E.g. if the data is all just in text files on the
LDAP server's file system with world-readable permissions, anyone with
access to the server's file system can see the data.

> 
> -- 
> Hallvard

Roger

--=__PartF3D28E6C.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 6.00.2800.1400" name=3DGENERATOR></HEAD>
<BODY style=3D"MARGIN: 4px 4px 1px; FONT: 10pt Tahoma">
<DIV><BR>&gt; &gt;&gt;&gt; Hallvard B Furuseth &lt;h.b.furuseth@usit.uio.no=
&gt; 1/3/2004 7:34:57 AM &gt;&gt;&gt;<BR>&gt; authmeth-09 says:<BR>&gt; =
<BR>&gt; &gt; 6.2. Digest Authentication<BR>&gt; &gt;<BR>&gt; &gt; (...) =
[DIGEST-MD5]. This provides client<BR>&gt; &gt; authentication with =
protection against passive eavesdropping<BR>&gt; &gt; attacks, but does =
not provide protection against active intermediary<BR>&gt; &gt; attacks.<BR=
>&gt; <BR>&gt; What does this mean? That DIGEST-MD5 is vulnerable =
to<BR>&gt; man-in-the-middle attacks? I didn't think it was.</DIV>
<DIV>&nbsp;</DIV>
<DIV>I don't have enough experience with Digest Authentication to speak to =
this. Can someone else in the WG please comment?</DIV>
<DIV><BR>&gt; <BR>&gt; BTW, maybe 'simple anonymous bind' should be =
'simple anonymous or<BR>&gt; unauthenticated bind'.<BR>&gt; <BR>&gt; It =
goes on to say:<BR>&gt; <BR>&gt; &gt; 10.1. Start TLS Security Consideratio=
ns<BR>&gt; <BR>&gt; &gt; The use of TLS does not provide or<BR>&gt; &gt; =
ensure for confidentiality and/or non-repudiation of the data housed<BR>&gt=
; &gt; by an LDAP-based directory server.<BR>&gt; <BR>&gt; I don't =
understand. I thought confidentiality was exactly one of<BR>&gt; the =
things TLS was for.</DIV>
<DIV>&nbsp;</DIV>
<DIV>I think the point is that TLS protects the data in transit between =
client and server, but it can't do anything to protect the data at the =
point it is housed. E.g. if the data is all just in text files on the LDAP =
server's file system with world-readable permissions, anyone with access =
to the server's file system can see the data.</DIV>
<DIV><BR>&gt; <BR>&gt; -- <BR>&gt; Hallvard<BR></DIV>
<DIV>Roger</DIV></BODY></HTML>

--=__PartF3D28E6C.0__=--


From owner-ietf-ldapbis@OpenLDAP.org  Mon Feb 16 04:15:43 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07358
	for <ldapbis-archive@lists.ietf.org>; Mon, 16 Feb 2004 04:15:43 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1G9F25v083580;
	Mon, 16 Feb 2004 09:15:04 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1G9BJl1083304;
	Mon, 16 Feb 2004 09:11: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); Mon, 16 Feb 2004 09:11:19 +0000
Received: from prv-mail20.provo.novell.com (prv-mail20.provo.novell.com [137.65.81.122])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1G9BI5r083266
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 16 Feb 2004 09:11:18 GMT
	(envelope-from RHARRISON@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Mon, 16 Feb 2004 02:10:58 -0700
Message-Id: <s03026b2.083@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.2 Beta
Date: Mon, 16 Feb 2004 02:10:43 -0700
From: "Roger Harrison" <RHARRISON@novell.com>
To: <ietf-ldapbis@OpenLDAP.org>, <h.b.furuseth@usit.uio.no>
Subject: Fwd: Re: authmeth: unsupported <TLS+anonymous bind>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__Part92B3EF03.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.

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

In thinking about this, perhaps I've over-stepped my authority as an ID
editor on this one. The original way implied that it was optional to
support anonymous authentication when TLS was established, but now this
isn't the case. I'd appreciate some advice here.
 
Thanks,
 
Roger

>>> Roger Harrison 2/16/2004 2:08:03 AM >>>

For authmeth -10, the single, consolidated section on anonymous
authentication now states that LDAP implementations MUST support
anonymous authentication with no other qualifications. The fact that
Start TLS is a required-to-implement operation implies that
implementations MUST support anonymous authentication when TLS is
established.
 
Roger

>>> Hallvard B Furuseth <h.b.furuseth@usit.uio.no> 1/3/2004 7:34:17 AM
>>>
authmeth-09 says:

> 5. Anonymous Authentication

> LDAP implementations MUST support anonymous authentication, as
> defined in section 5.1.
>
> LDAP implementations MAY support anonymous authentication with TLS,
> as defined in section 5.2.

Huh? Why allow implementations to not support anonymous
authentication on secure connections, but support it on insecure
ones? I could understand it if it was the other way around - along
with not implementing Simple Bind at all without TLS.

-- 
Hallvard



--=__Part92B3EF03.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 6.00.2800.1400" name=3DGENERATOR></HEAD>
<BODY style=3D"MARGIN: 4px 4px 1px; FONT: 10pt Tahoma">
<DIV>In thinking about this, perhaps I've over-stepped my authority as an =
ID editor on this one. The original way implied that it was optional to =
support anonymous authentication when TLS was established, but now this =
isn't the case. I'd appreciate some advice here.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Thanks,</DIV>
<DIV>&nbsp;</DIV>
<DIV>Roger<BR><BR>&gt;&gt;&gt; Roger Harrison 2/16/2004 2:08:03 AM =
&gt;&gt;&gt;<BR></DIV>
<DIV style=3D"FONT: 10pt Tahoma; COLOR: #000000">
<DIV>For authmeth -10, the single, consolidated section on anonymous =
authentication now states that LDAP implementations MUST support anonymous =
authentication with no other qualifications. The fact that Start TLS is a =
required-to-implement operation implies that implementations MUST support =
anonymous authentication when TLS is established.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Roger<BR><BR>&gt;&gt;&gt; Hallvard B Furuseth &lt;h.b.furuseth@usit.ui=
o.no&gt; 1/3/2004 7:34:17 AM &gt;&gt;&gt;<BR>authmeth-09 says:<BR><BR>&gt; =
5. Anonymous Authentication<BR><BR>&gt; LDAP implementations MUST support =
anonymous authentication, as<BR>&gt; defined in section 5.1.<BR>&gt;<BR>&gt=
; LDAP implementations MAY support anonymous authentication with TLS,<BR>&g=
t; as defined in section 5.2.<BR><BR>Huh? Why allow implementations to not =
support anonymous<BR>authentication on secure connections, but support it =
on insecure<BR>ones? I could understand it if it was the other way around =
- along<BR>with not implementing Simple Bind at all without TLS.<BR><BR>-- =
<BR>Hallvard<BR></DIV></DIV></BODY></HTML>

--=__Part92B3EF03.0__=--


From owner-ietf-ldapbis@OpenLDAP.org  Mon Feb 16 09:58:38 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21058
	for <ldapbis-archive@lists.ietf.org>; Mon, 16 Feb 2004 09:58:38 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1GEj47F097692;
	Mon, 16 Feb 2004 14:57:48 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1GEhpSV097650;
	Mon, 16 Feb 2004 14:43: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); Mon, 16 Feb 2004 14:43:51 +0000
Received: from e5.ny.us.ibm.com (e5.ny.us.ibm.com [32.97.182.105])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1GEhn5r097577
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 16 Feb 2004 14:43:50 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 i1GEhTFP695954
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 16 Feb 2004 09:43:29 -0500
Received: from d27ml001.rchland.ibm.com (d01av04.pok.ibm.com [9.56.224.64])
	by northrelay02.pok.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id i1GEhSSp133890
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 16 Feb 2004 09:43:28 -0500
In-Reply-To: <s0300f89.025@prv-mail20.provo.novell.com>
Subject: Re: authmeth-07 issues
To: ietf-ldapbis@OpenLDAP.org
X-Mailer: Lotus Notes Release 6.0.2CF1 June 9, 2003
Message-ID: <OF6A0836FB.9A523361-ON86256E3C.0050A1FD-86256E3C.0050E10C@us.ibm.com>
From: John McMeeking <jmcmeek@us.ibm.com>
Date: Mon, 16 Feb 2004 08:43:24 -0600
X-MIMETrack: Serialize by Router on d27ml001/27/M/IBM(Release 6.5.1|January 21, 2004) at
 02/16/2004 08:43:27 AM
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 don't think there is any need to add material to the Security
Considerations section if the proposed changes to authmethod are made (your
previous note on StartTLS and StopTLS).


John  McMeeking


"Roger Harrison" <RHARRISON@novell.com> wrote on 02/16/2004 01:31:47 AM:

> With the fairly extensive reworking of the effect of Start TLS and
> TLS closure on the LDAP association state, I'm wondering how WG
> members view the need for these security considerations proposed by
> Hallvard.  Your comments are greatly appreciated.
>
> Roger
> >>> Hallvard B Furuseth <h.b.furuseth@usit.uio.no> 10/14/2003 8:11:28 AM
>>>
> > 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.



From owner-ietf-ldapbis@OpenLDAP.org  Mon Feb 16 09:59:33 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21176
	for <ldapbis-archive@lists.ietf.org>; Mon, 16 Feb 2004 09:59:33 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1GEv463098884;
	Mon, 16 Feb 2004 14:58:56 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1GEqs3i098420;
	Mon, 16 Feb 2004 14:52: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); Mon, 16 Feb 2004 14:52:54 +0000
Received: from e5.ny.us.ibm.com (e5.ny.us.ibm.com [32.97.182.105])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1GEqr5r098355
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 16 Feb 2004 14:52:53 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 i1GEqWFP321088
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 16 Feb 2004 09:52:32 -0500
Received: from d27ml001.rchland.ibm.com (d01av04.pok.ibm.com [9.56.224.64])
	by northrelay02.pok.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id i1GEqWSp136690
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 16 Feb 2004 09:52:32 -0500
In-Reply-To: <s0302616.063@prv-mail20.provo.novell.com>
Subject: Re: authmeth: unsupported <TLS+anonymous bind>
To: ietf-ldapbis@OpenLDAP.org
X-Mailer: Lotus Notes Release 6.0.2CF1 June 9, 2003
Message-ID: <OFA394B30A.E7B6A7F4-ON86256E3C.005192FF-86256E3C.0051B63B@us.ibm.com>
From: John McMeeking <jmcmeek@us.ibm.com>
Date: Mon, 16 Feb 2004 08:52:29 -0600
X-MIMETrack: Serialize by Router on d27ml001/27/M/IBM(Release 6.5.1|January 21, 2004) at
 02/16/2004 08:52:31 AM
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>





That sounds fine.

John  McMeeking


"Roger Harrison" <RHARRISON@novell.com> wrote on 02/16/2004 03:08:03 AM:

> For authmeth -10, the single, consolidated section on anonymous
> authentication now states that LDAP implementations MUST support
> anonymous authentication with no other qualifications. The fact that
> Start TLS is a required-to-implement operation implies that
> implementations MUST support anonymous authentication when TLS is
established.
>
> Roger
>
> >>> Hallvard B Furuseth <h.b.furuseth@usit.uio.no> 1/3/2004 7:34:17 AM
>>>
> authmeth-09 says:
>
> > 5. Anonymous Authentication
>
> > LDAP implementations MUST support anonymous authentication, as
> > defined in section 5.1.
> >
> > LDAP implementations MAY support anonymous authentication with TLS,
> > as defined in section 5.2.
>
> Huh? Why allow implementations to not support anonymous
> authentication on secure connections, but support it on insecure
> ones? I could understand it if it was the other way around - along
> with not implementing Simple Bind at all without TLS.
>
> --
> Hallvard



From owner-ietf-ldapbis@OpenLDAP.org  Mon Feb 16 10:09:53 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22162
	for <ldapbis-archive@lists.ietf.org>; Mon, 16 Feb 2004 10:09:52 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1GF346j099746;
	Mon, 16 Feb 2004 15:08:06 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1GExRcj099328;
	Mon, 16 Feb 2004 14:59: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); Mon, 16 Feb 2004 14:59:27 +0000
Received: from e1.ny.us.ibm.com (e1.ny.us.ibm.com [32.97.182.101])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1GExP5r099259
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 16 Feb 2004 14:59:25 GMT
	(envelope-from jmcmeek@us.ibm.com)
Received: from northrelay04.pok.ibm.com (northrelay04.pok.ibm.com [9.56.224.206])
	by e1.ny.us.ibm.com (8.12.10/NS PXFA) with ESMTP id i1GEx5dw457176
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 16 Feb 2004 09:59:05 -0500
Received: from d27ml001.rchland.ibm.com (d01av04.pok.ibm.com [9.56.224.64])
	by northrelay04.pok.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id i1GEx7pw102626
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 16 Feb 2004 09:59:08 -0500
In-Reply-To: <s030251d.050@prv-mail20.provo.novell.com>
Subject: Re: authmeth: missing protection
To: ietf-ldapbis@OpenLDAP.org
X-Mailer: Lotus Notes Release 6.0.2CF1 June 9, 2003
Message-ID: <OFA0B8BAF4.4822F271-ON86256E3C.0051D039-86256E3C.00524EE0@us.ibm.com>
From: John McMeeking <jmcmeek@us.ibm.com>
Date: Mon, 16 Feb 2004 08:59:00 -0600
X-MIMETrack: Serialize by Router on d27ml001/27/M/IBM(Release 6.5.1|January 21, 2004) at
 02/16/2004 08:59:02 AM
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 can't speak to this issue specifically, but it raises a minor question:
Is there any reason to say anyhting about this in authmeth?  Weaknesses of
DIGEST-MD5 apply to any protocol that supports it, not just LDAP.  The same
thing applies to discussion of TLS ciphers that are recommended or not.  Is
it common practice to list such issues in standards for other protocols
that support such technologies?  It seems like the kind of thing that
should be said in one place, and applies to all applications of that
particular technology.


John  McMeeking



"Roger Harrison" <RHARRISON@novell.com> wrote on 02/16/2004 03:03:56 AM:

>
> > >>> Hallvard B Furuseth <h.b.furuseth@usit.uio.no> 1/3/2004 7:34:57 AM
>>>
> > authmeth-09 says:
> >
> > > 6.2. Digest Authentication
> > >
> > > (...) [DIGEST-MD5]. This provides client
> > > authentication with protection against passive eavesdropping
> > > attacks, but does not provide protection against active intermediary
> > > attacks.
> >
> > What does this mean? That DIGEST-MD5 is vulnerable to
> > man-in-the-middle attacks? I didn't think it was.
>
> I don't have enough experience with Digest Authentication to speak
> to this. Can someone else in the WG please comment?
>
> >
> > BTW, maybe 'simple anonymous bind' should be 'simple anonymous or
> > unauthenticated bind'.
> >
> > It goes on to say:
> >
> > > 10.1. Start TLS Security Considerations
> >
> > > 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.
> >
> > I don't understand. I thought confidentiality was exactly one of
> > the things TLS was for.
>
> I think the point is that TLS protects the data in transit between
> client and server, but it can't do anything to protect the data at
> the point it is housed. E.g. if the data is all just in text files
> on the LDAP server's file system with world-readable permissions,
> anyone with access to the server's file system can see the data.
>
> >
> > --
> > Hallvard
> Roger



From owner-ietf-ldapbis@OpenLDAP.org  Mon Feb 16 12:19:20 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06587
	for <ldapbis-archive@lists.ietf.org>; Mon, 16 Feb 2004 12:19:19 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1GHF55v010240;
	Mon, 16 Feb 2004 17:18:30 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1GHBHJ1010044;
	Mon, 16 Feb 2004 17:11: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); Mon, 16 Feb 2004 17:11:17 +0000
Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1GHBB5r010007;
	Mon, 16 Feb 2004 17:11:15 GMT
	(envelope-from mcs@pearlcrescent.com)
Received: from pearlcrescent.com (pcp05006455pcs.sanarb01.mi.comcast.net[68.40.228.200])
          by comcast.net (rwcrmhc13) with SMTP
          id <2004021617105101500ij7v9e>
          (Authid: mcs);
          Mon, 16 Feb 2004 17:10:51 +0000
Message-ID: <4030F992.5080609@pearlcrescent.com>
Date: Mon, 16 Feb 2004 12:10:42 -0500
From: Mark Smith <mcs@pearlcrescent.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: Kurt@OpenLDAP.org, h.b.furuseth@usit.uio.no, ietf-ldapbis@OpenLDAP.org
Subject: Re: names of RFC references (was: models-09 comments)
References: <s0301619.077@prv-mail20.provo.novell.com>
In-Reply-To: <s0301619.077@prv-mail20.provo.novell.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Roger Harrison wrote:
> I haven't seen any further comments on this subject, so I'll jump in. 
> I've attempted to at least make AuthMeth consistent with itself and with 
> Protocol in the -10 draft by using descriptive names for all references.
>  
> I had assumed that since we are using descriptive names for the LDAP TS 
> that it would make sense to use them everywhere. I realize that the RFC 
> editor could replace descriptive names of LDAP TS  docs with their RFCs 
> as the RFC numbers are assigned, but I'd prefer leaving descriptive 
> names throughout.

I like descriptive names.  On the other hand, [RFC####] names are very 
precise.  I think everyone agress that we should be consistent across 
all of the LDAPBIS documents.  Someone should just decide which approach 
we will use ;-)

-Mark




From owner-ietf-ldapbis@OpenLDAP.org  Mon Feb 16 15:50:10 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21679
	for <ldapbis-archive@lists.ietf.org>; Mon, 16 Feb 2004 15:50:09 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1GKj761023667;
	Mon, 16 Feb 2004 20:48:42 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1GKg3ks023468;
	Mon, 16 Feb 2004 20:42:03 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, 16 Feb 2004 20:42:03 +0000
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1GKg25r023458
	for <ietf-ldapbis@openldap.org>; Mon, 16 Feb 2004 20:42:02 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 PAA20317;
	Mon, 16 Feb 2004 15:42:00 -0500 (EST)
Message-Id: <200402162042.PAA20317@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-05.txt
Date: Mon, 16 Feb 2004 15:41:59 -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-05.txt
	Pages		: 14
	Date		: 2004-2-16
	
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-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-url-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-url-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:	<2004-2-16124220.I-D@ietf.org>

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

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

Content-Type: text/plain
Content-ID:	<2004-2-16124220.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-ietf-ldapbis@OpenLDAP.org  Mon Feb 16 16:39:41 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21678
	for <ldapbis-archive@lists.ietf.org>; Mon, 16 Feb 2004 15:50:09 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1GKj763023667;
	Mon, 16 Feb 2004 20:48:42 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1GKdmck023353;
	Mon, 16 Feb 2004 20:39: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, 16 Feb 2004 20:39:48 +0000
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1GKdk5r023342
	for <ietf-ldapbis@openldap.org>; Mon, 16 Feb 2004 20:39: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 PAA19848;
	Mon, 16 Feb 2004 15:39:44 -0500 (EST)
Message-Id: <200402162039.PAA19848@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-06.txt
Date: Mon, 16 Feb 2004 15:39:43 -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-06.txt
	Pages		: 12
	Date		: 2004-2-16
	
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-06.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-06.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-06.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:	<2004-2-16122943.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ldapbis-filter-06.txt

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

Content-Type: text/plain
Content-ID:	<2004-2-16122943.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-ietf-ldapbis@OpenLDAP.org  Mon Feb 16 17:13:44 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01647
	for <ldapbis-archive@lists.ietf.org>; Mon, 16 Feb 2004 17:13:44 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1GM976L030496;
	Mon, 16 Feb 2004 22:12:38 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1GM5Snr030154;
	Mon, 16 Feb 2004 22:05: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); Mon, 16 Feb 2004 22:05:28 +0000
Received: from adacel.com (gunsmoke.adacel.com.au [210.11.130.7])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1GM5K5r030121
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 16 Feb 2004 22:05:26 GMT
	(envelope-from andrew.sciberras@adacel.com)
Received: from nexus.adacel.com (Not Verified[10.32.240.1]) by adacel.com with NetIQ MailMarshal (v5.5.5.9)
	id <B000213ddb>; Tue, 17 Feb 2004 08:55:37 +1100
Received: (qmail 26147 invoked from network); 16 Feb 2004 22:04:58 -0000
Received: from unknown (HELO shylock) (10.32.24.166)
  by nexus.adacel.com with SMTP; 16 Feb 2004 22:04:58 -0000
Reply-To: <andrew.sciberras@adacel.com>
From: "Andrew Sciberras" <andrew.sciberras@adacel.com>
To: "'Mark Smith'" <mcs@pearlcrescent.com>, <howes@opsware.com>
Cc: <ietf-ldapbis@OpenLDAP.org>
Subject: RE: I-D ACTION:draft-ietf-ldapbis-url-05.txt
Date: Tue, 17 Feb 2004 09:04:57 +1100
Message-ID: <013e01c3f4d8$eaf899e0$a618200a@mtwav.adacel.com.au>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0
In-Reply-To: <200402162042.PAA20317@ietf.org>
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

G'day,

Just some comments:


Section 4. Introduction.
Include "MUST NOT" and "SHOULD NOT" in the final paragraph.


Section 5. URL Definition

>SLASH = %x5C; forward slash ("/")
%x5C is the backslash, use %x2F instead.

>The "ldap" prefix indicates an entry or entries residing in the LDAP
>server running on the given hostname at the given portnumber.
Does this imply that it would be wrong to chain the request, if the server
is able to do so?

>An extension prefixed with a '!'character (ASCII 33)
>is critical.
Wouldn't it be better to maintain consistency and use hex (0x21) instead of
decimal (33)?

>If an LDAP URL extension is recognised by an implementation, the
>implementation MUST make use of it.
What if you recognise it, but don't implement it?
If it is not critical then I see no reason why the operation should not
proceed.


Regards,

Andrew Sciberras
Software Engineer
Adacel Technologies Ltd



From owner-ietf-ldapbis@OpenLDAP.org  Mon Feb 16 18:10:16 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07939
	for <ldapbis-archive@lists.ietf.org>; Mon, 16 Feb 2004 18:10:14 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1GN975v033212;
	Mon, 16 Feb 2004 23:09:29 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1GN5snt033087;
	Mon, 16 Feb 2004 23:05: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); Mon, 16 Feb 2004 23:05:54 +0000
Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1GN5q5r033075
	for <ietf-ldapbis@openldap.org>; Mon, 16 Feb 2004 23:05:53 GMT
	(envelope-from mcs@pearlcrescent.com)
Received: from pearlcrescent.com (pcp05006455pcs.sanarb01.mi.comcast.net[68.40.228.200])
          by comcast.net (rwcrmhc13) with SMTP
          id <2004021623053201500gkdl9e>
          (Authid: mcs);
          Mon, 16 Feb 2004 23:05:32 +0000
Message-ID: <40314CB3.8020702@pearlcrescent.com>
Date: Mon, 16 Feb 2004 18:05:23 -0500
From: Mark Smith <mcs@pearlcrescent.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: andrew.sciberras@adacel.com
CC: howes@opsware.com, ietf-ldapbis@OpenLDAP.org
Subject: Re: I-D ACTION:draft-ietf-ldapbis-url-05.txt
References: <013e01c3f4d8$eaf899e0$a618200a@mtwav.adacel.com.au>
In-Reply-To: <013e01c3f4d8$eaf899e0$a618200a@mtwav.adacel.com.au>
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

Andrew Sciberras wrote:

> G'day,
> 
> Just some comments:
> 
> 
> Section 4. Introduction.
> Include "MUST NOT" and "SHOULD NOT" in the final paragraph.

Good catch.  I will add those.


> Section 5. URL Definition
> 
> 
>>SLASH = %x5C; forward slash ("/")
> 
> %x5C is the backslash, use %x2F instead.

Oops.  Thanks; I will fix it.


>>The "ldap" prefix indicates an entry or entries residing in the LDAP
>>server running on the given hostname at the given portnumber.
> 
> Does this imply that it would be wrong to chain the request, if the server
> is able to do so?

No, I do not think so.  The phrase "residing in" is probably too 
restrictive.  Perhaps replace with "accessible from" so it reads:

   The "ldap" prefix indicates an entry or entries accessible from
   the LDAP server running on the given hostname at the given portnumber.

?


>>An extension prefixed with a '!'character (ASCII 33)
>>is critical.
> 
> Wouldn't it be better to maintain consistency and use hex (0x21) instead of
> decimal (33)?

OK; good suggestion.


>>If an LDAP URL extension is recognised by an implementation, the
>>implementation MUST make use of it.
> 
> What if you recognise it, but don't implement it?
> If it is not critical then I see no reason why the operation should not
> proceed.

Kurt can probably explain this better than I can... but the goal is to 
be consistent the philopsophy used for LDAP controls in the Protocol 
document.  I think "recognized" implies "ability to use" an extension; 
that is, if an implementation recognizes an extension it is able to use it.

-Mark




From owner-ietf-ldapbis@OpenLDAP.org  Mon Feb 16 19:20:50 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15598
	for <ldapbis-archive@lists.ietf.org>; Mon, 16 Feb 2004 19:20:50 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1H0F85x035391;
	Tue, 17 Feb 2004 00:19:31 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1H0AjR7035062;
	Tue, 17 Feb 2004 00:10: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); Tue, 17 Feb 2004 00:10:45 +0000
Received: from usilms55.ca.com (mail13.ca.com [141.202.248.42])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1H0Ai5r035052
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 17 Feb 2004 00:10:44 GMT
	(envelope-from Ron.Ramsay@ca.com)
Received: from usilms81.ca.com ([141.202.201.51]) by usilms55.ca.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Mon, 16 Feb 2004 19:10:43 -0500
Received: from ausyms80.ca.com ([155.35.201.10]) by usilms81.ca.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Mon, 16 Feb 2004 19:10:42 -0500
Received: from ausyms21.ca.com ([155.35.201.5]) by ausyms80.ca.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Tue, 17 Feb 2004 11:10:39 +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: authmeth: missing protection
Date: Tue, 17 Feb 2004 11:10:39 +1100
Message-ID: <1395B4B334FCC143B36AF788E68B6381010D07D1@ausyms21.ca.com>
Thread-Topic: authmeth: missing protection
Thread-Index: AcP0nr+6kO4IaYT9TCm3p5+XvqijAwAS3OIQ
From: "Ramsay, Ron" <Ron.Ramsay@ca.com>
To: "John McMeeking" <jmcmeek@us.ibm.com>, <ietf-ldapbis@OpenLDAP.org>
X-OriginalArrivalTime: 17 Feb 2004 00:10:39.0595 (UTC) FILETIME=[7996B3B0:01C3F4EA]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by boole.openldap.org id i1H0Ai5r035053
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.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

As the mechanism is recommended by LDAP, and not the free choice of the implementer, there is a responsibility to provide some context for its use.

Ron

-----Original Message-----
From: owner-ietf-ldapbis@OpenLDAP.org
[mailto:owner-ietf-ldapbis@OpenLDAP.org]On Behalf Of John McMeeking
Sent: Tuesday, 17 February 2004 01:59
To: ietf-ldapbis@OpenLDAP.org
Subject: Re: authmeth: missing protection






I can't speak to this issue specifically, but it raises a minor question:
Is there any reason to say anyhting about this in authmeth?  Weaknesses of
DIGEST-MD5 apply to any protocol that supports it, not just LDAP.  The same
thing applies to discussion of TLS ciphers that are recommended or not.  Is
it common practice to list such issues in standards for other protocols
that support such technologies?  It seems like the kind of thing that
should be said in one place, and applies to all applications of that
particular technology.


John  McMeeking



"Roger Harrison" <RHARRISON@novell.com> wrote on 02/16/2004 03:03:56 AM:

>
> > >>> Hallvard B Furuseth <h.b.furuseth@usit.uio.no> 1/3/2004 7:34:57 AM
>>>
> > authmeth-09 says:
> >
> > > 6.2. Digest Authentication
> > >
> > > (...) [DIGEST-MD5]. This provides client
> > > authentication with protection against passive eavesdropping
> > > attacks, but does not provide protection against active intermediary
> > > attacks.
> >
> > What does this mean? That DIGEST-MD5 is vulnerable to
> > man-in-the-middle attacks? I didn't think it was.
>
> I don't have enough experience with Digest Authentication to speak
> to this. Can someone else in the WG please comment?
>
> >
> > BTW, maybe 'simple anonymous bind' should be 'simple anonymous or
> > unauthenticated bind'.
> >
> > It goes on to say:
> >
> > > 10.1. Start TLS Security Considerations
> >
> > > 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.
> >
> > I don't understand. I thought confidentiality was exactly one of
> > the things TLS was for.
>
> I think the point is that TLS protects the data in transit between
> client and server, but it can't do anything to protect the data at
> the point it is housed. E.g. if the data is all just in text files
> on the LDAP server's file system with world-readable permissions,
> anyone with access to the server's file system can see the data.
>
> >
> > --
> > Hallvard
> Roger





From owner-ietf-ldapbis@OpenLDAP.org  Mon Feb 16 19:33:53 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16086
	for <ldapbis-archive@lists.ietf.org>; Mon, 16 Feb 2004 19:33:53 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1H0R963036371;
	Tue, 17 Feb 2004 00:33:07 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1H0FLGU035419;
	Tue, 17 Feb 2004 00:15: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, 17 Feb 2004 00:15:21 +0000
Received: from uslims57.ca.com (mail15.ca.com [208.232.182.11])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1H0FK5r035348
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 17 Feb 2004 00:15:20 GMT
	(envelope-from Ron.Ramsay@ca.com)
Received: from usilms81.ca.com ([141.202.201.51]) by uslims57.ca.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Mon, 16 Feb 2004 18:14:59 -0600
Received: from ausyms80.ca.com ([155.35.201.10]) by usilms81.ca.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Mon, 16 Feb 2004 19:14:59 -0500
Received: from ausyms21.ca.com ([155.35.201.5]) by ausyms80.ca.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Tue, 17 Feb 2004 11:14:55 +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: I-D ACTION:draft-ietf-ldapbis-url-05.txt
Date: Tue, 17 Feb 2004 11:14:55 +1100
Message-ID: <1395B4B334FCC143B36AF788E68B6381010D07DD@ausyms21.ca.com>
Thread-Topic: I-D ACTION:draft-ietf-ldapbis-url-05.txt
Thread-Index: AcP04fNlfeJpzz0RQT+qbpnO09m4pAACJYhw
From: "Ramsay, Ron" <Ron.Ramsay@ca.com>
To: "Mark Smith" <mcs@pearlcrescent.com>, <andrew.sciberras@adacel.com>
Cc: <howes@opsware.com>, <ietf-ldapbis@OpenLDAP.org>
X-OriginalArrivalTime: 17 Feb 2004 00:14:55.0968 (UTC) FILETIME=[12661E00:01C3F4EB]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by boole.openldap.org id i1H0FK5r035410
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.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

Why are they called extensions and not controls? It looks a bit misleading to me. (LDAP can be extended in a number of ways.)

As regards the action to be taken when a control is present, can't you simply refer to the protocol spec?

Ron

-----Original Message-----
From: owner-ietf-ldapbis@OpenLDAP.org
[mailto:owner-ietf-ldapbis@OpenLDAP.org]On Behalf Of Mark Smith
Sent: Tuesday, 17 February 2004 10:05
To: andrew.sciberras@adacel.com
Cc: howes@opsware.com; ietf-ldapbis@OpenLDAP.org
Subject: Re: I-D ACTION:draft-ietf-ldapbis-url-05.txt


Andrew Sciberras wrote:

> G'day,
> 
> Just some comments:
> 
> 
> Section 4. Introduction.
> Include "MUST NOT" and "SHOULD NOT" in the final paragraph.

Good catch.  I will add those.


> Section 5. URL Definition
> 
> 
>>SLASH = %x5C; forward slash ("/")
> 
> %x5C is the backslash, use %x2F instead.

Oops.  Thanks; I will fix it.


>>The "ldap" prefix indicates an entry or entries residing in the LDAP
>>server running on the given hostname at the given portnumber.
> 
> Does this imply that it would be wrong to chain the request, if the server
> is able to do so?

No, I do not think so.  The phrase "residing in" is probably too 
restrictive.  Perhaps replace with "accessible from" so it reads:

   The "ldap" prefix indicates an entry or entries accessible from
   the LDAP server running on the given hostname at the given portnumber.

?


>>An extension prefixed with a '!'character (ASCII 33)
>>is critical.
> 
> Wouldn't it be better to maintain consistency and use hex (0x21) instead of
> decimal (33)?

OK; good suggestion.


>>If an LDAP URL extension is recognised by an implementation, the
>>implementation MUST make use of it.
> 
> What if you recognise it, but don't implement it?
> If it is not critical then I see no reason why the operation should not
> proceed.

Kurt can probably explain this better than I can... but the goal is to 
be consistent the philopsophy used for LDAP controls in the Protocol 
document.  I think "recognized" implies "ability to use" an extension; 
that is, if an implementation recognizes an extension it is able to use it.

-Mark






From owner-ietf-ldapbis@OpenLDAP.org  Tue Feb 17 01:14:20 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA28878
	for <ldapbis-archive@lists.ietf.org>; Tue, 17 Feb 2004 01:14:19 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1H69A5v051211;
	Tue, 17 Feb 2004 06:13:13 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1H65GUW050967;
	Tue, 17 Feb 2004 06:05:16 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, 17 Feb 2004 06:05:16 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1H65F5r050957
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 17 Feb 2004 06:05:15 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from gypsy.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.10/8.12.10) with ESMTP id i1H65D7s098305;
	Tue, 17 Feb 2004 06:05:13 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.1.1.0.20040216220232.04bab8e8@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Mon, 16 Feb 2004 22:05:04 -0800
To: "Roger Harrison" <RHARRISON@novell.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: hijack attack (Was: authmeth-09 comments)
Cc: <ietf-ldapbis@OpenLDAP.org>
In-Reply-To: <s0301a20.015@prv-mail20.provo.novell.com>
References: <s0301a20.015@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>

RFC 2828:
   $ hijack attack
      (I) A form of active wiretapping in which the attacker seizes     
      control of a previously established communication association.
      (See: man-in-the-middle attack, pagejacking, piggyback attack.)

That is, if an LDAP client authenticates using DIGEST-MD5 but fails
to establish integrity protections, then a MITM attacker can take
over (or "hijack") the LDAP association.

Kurt

At 12:16 AM 2/16/2004, Roger Harrison wrote:
>Kurt,
> 
>Could you provide some details about what you mean by this phrase?  I added the idea to the -10 draft several weeks ago, but I'm still not sure I know what these words mean to you.
> 
>Thanks,
> 
>Roger
>
>>>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 1/6/2004 1:55:45 PM >>>
>(8) Hijacking of protocol sessions.
>



From owner-ietf-ldapbis@OpenLDAP.org  Tue Feb 17 01:42:28 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA29408
	for <ldapbis-archive@lists.ietf.org>; Tue, 17 Feb 2004 01:42:27 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1H6dn65052358;
	Tue, 17 Feb 2004 06:41:23 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1H6Nffw051649;
	Tue, 17 Feb 2004 06:23: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); Tue, 17 Feb 2004 06:23:41 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1H6Ne5r051639
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 17 Feb 2004 06:23:40 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from gypsy.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.10/8.12.10) with ESMTP id i1H6Na7s098485;
	Tue, 17 Feb 2004 06:23:36 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.1.1.0.20040216220704.04c80eb0@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Mon, 16 Feb 2004 22:23:27 -0800
To: Mark Smith <mcs@pearlcrescent.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: I-D ACTION:draft-ietf-ldapbis-url-05.txt
Cc: andrew.sciberras@adacel.com, howes@opsware.com, ietf-ldapbis@OpenLDAP.org
In-Reply-To: <40314CB3.8020702@pearlcrescent.com>
References: <013e01c3f4d8$eaf899e0$a618200a@mtwav.adacel.com.au>
 <40314CB3.8020702@pearlcrescent.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 03:05 PM 2/16/2004, Mark Smith wrote:
>>>If an LDAP URL extension is recognised by an implementation, the
>>>implementation MUST make use of it.
>>What if you recognise it, but don't implement it?
>>If it is not critical then I see no reason why the operation should not
>>proceed.
>
>Kurt can probably explain this better than I can... but the goal is to be consistent the philopsophy used for LDAP controls in the Protocol document. 
>I think "recognized" implies "ability to use" an extension; that is, if an implementation recognizes an extension it is able to use it.

I prefer "implement" here over "recognize".  Like a number of
other protocol tokens, it is possible to "recognize" an
token without actually implementing the syntax and semantics
associated with that token.   For instance, a implementation
could recognize the bindname extension but not implement it
(maybe the implementation only supports the mandatory-to-implement
authentication mechanism (e.g., DIGEST-MD5)).

Ron asked:
>Why are they called extensions and not controls?  It looks a bit misleading to me. (LDAP can be extended in a number of ways.)

I think it would be misleading to call them LDAP URL Controls
as they would confused with LDAP Controls.  LDAP URL Extensions
are not necessarily LDAP Controls.

Kurt




From owner-ietf-ldapbis@OpenLDAP.org  Tue Feb 17 01:57:05 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA29612
	for <ldapbis-archive@lists.ietf.org>; Tue, 17 Feb 2004 01:57:05 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1H6pA5x053052;
	Tue, 17 Feb 2004 06:56:22 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1H6jmeH052867;
	Tue, 17 Feb 2004 06:45: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); Tue, 17 Feb 2004 06:45:48 +0000
Received: from uslims56.ca.com (mail14.ca.com [208.232.182.10])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1H6jj5r052810;
	Tue, 17 Feb 2004 06:45:46 GMT
	(envelope-from Ron.Ramsay@ca.com)
Received: from usilms80.ca.com ([141.202.201.17]) by uslims56.ca.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Tue, 17 Feb 2004 00:45:25 -0600
Received: from ausyms80.ca.com ([155.35.201.10]) by usilms80.ca.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Tue, 17 Feb 2004 01:45:24 -0500
Received: from ausyms21.ca.com ([155.35.201.5]) by ausyms80.ca.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Tue, 17 Feb 2004 17:45:21 +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: I-D ACTION:draft-ietf-ldapbis-url-05.txt
Date: Tue, 17 Feb 2004 17:45:21 +1100
Message-ID: <1395B4B334FCC143B36AF788E68B6381010D0DAE@ausyms21.ca.com>
Thread-Topic: I-D ACTION:draft-ietf-ldapbis-url-05.txt
Thread-Index: AcP1IR9PWlw5R2dIR4qHgw9LqUr6PQAAEdug
From: "Ramsay, Ron" <Ron.Ramsay@ca.com>
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Cc: <andrew.sciberras@adacel.com>, <howes@opsware.com>,
        <ietf-ldapbis@OpenLDAP.org>
X-OriginalArrivalTime: 17 Feb 2004 06:45:21.0459 (UTC) FILETIME=[9D146030:01C3F521]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by boole.openldap.org id i1H6jk5r052838
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.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 doubt they are LDAP URL Extensions as they are part of the base definition! I believe the only things you can put a '!' in front of are LDAP controls, so I stick with what I said.

-----Original Message-----
From: owner-ietf-ldapbis@OpenLDAP.org
[mailto:owner-ietf-ldapbis@OpenLDAP.org]On Behalf Of Kurt D. Zeilenga
Sent: Tuesday, 17 February 2004 17:23
To: Mark Smith
Cc: andrew.sciberras@adacel.com; howes@opsware.com;
ietf-ldapbis@OpenLDAP.org
Subject: Re: I-D ACTION:draft-ietf-ldapbis-url-05.txt


At 03:05 PM 2/16/2004, Mark Smith wrote:
>>>If an LDAP URL extension is recognised by an implementation, the
>>>implementation MUST make use of it.
>>What if you recognise it, but don't implement it?
>>If it is not critical then I see no reason why the operation should not
>>proceed.
>
>Kurt can probably explain this better than I can... but the goal is to be consistent the philopsophy used for LDAP controls in the Protocol document. 
>I think "recognized" implies "ability to use" an extension; that is, if an implementation recognizes an extension it is able to use it.

I prefer "implement" here over "recognize".  Like a number of
other protocol tokens, it is possible to "recognize" an
token without actually implementing the syntax and semantics
associated with that token.   For instance, a implementation
could recognize the bindname extension but not implement it
(maybe the implementation only supports the mandatory-to-implement
authentication mechanism (e.g., DIGEST-MD5)).

Ron asked:
>Why are they called extensions and not controls?  It looks a bit misleading to me. (LDAP can be extended in a number of ways.)

I think it would be misleading to call them LDAP URL Controls
as they would confused with LDAP Controls.  LDAP URL Extensions
are not necessarily LDAP Controls.

Kurt






From owner-ietf-ldapbis@OpenLDAP.org  Tue Feb 17 07:49:22 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA25703
	for <ldapbis-archive@lists.ietf.org>; Tue, 17 Feb 2004 07:49:22 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1HCjC5v084450;
	Tue, 17 Feb 2004 12:48:25 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1HChn4U084328;
	Tue, 17 Feb 2004 12:43: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, 17 Feb 2004 12:43:49 +0000
Received: from e3.ny.us.ibm.com (e3.ny.us.ibm.com [32.97.182.103])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1HChl5r084299
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 17 Feb 2004 12:43:47 GMT
	(envelope-from jmcmeek@us.ibm.com)
Received: from northrelay02.pok.ibm.com (northrelay02.pok.ibm.com [9.56.224.150])
	by e3.ny.us.ibm.com (8.12.10/8.12.2) with ESMTP id i1HCh7nD765364;
	Tue, 17 Feb 2004 07:43:07 -0500
Received: from d27ml001.rchland.ibm.com (d01av02.pok.ibm.com [9.56.224.216])
	by northrelay02.pok.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id i1HCh60U115144;
	Tue, 17 Feb 2004 07:43:07 -0500
In-Reply-To: <1395B4B334FCC143B36AF788E68B6381010D0DAE@ausyms21.ca.com>
Subject: RE: I-D ACTION:draft-ietf-ldapbis-url-05.txt
To: "Ramsay, Ron" <Ron.Ramsay@ca.com>, ietf-ldapbis@OpenLDAP.org
X-Mailer: Lotus Notes Release 6.0.2CF1 June 9, 2003
Message-ID: <OFDF42A063.4AB333BC-ON86256E3D.00458391-86256E3D.0045DD2D@us.ibm.com>
From: John McMeeking <jmcmeek@us.ibm.com>
Date: Tue, 17 Feb 2004 06:43:05 -0600
X-MIMETrack: Serialize by Router on d27ml001/27/M/IBM(Release 6.5.1|January 21, 2004) at
 02/17/2004 06:43:06 AM
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 2255 defines a bindname extension; when using the URL, the client was
to authenticate to the server as the specified DN.  This is an example of
an URL extension that is not a LDAP control or extended request.


John  McMeeking


owner-ietf-ldapbis@OpenLDAP.org wrote on 02/17/2004 12:45:21 AM:

> I doubt they are LDAP URL Extensions as they are part of the base
> definition! I believe the only things you can put a '!' in front of
> are LDAP controls, so I stick with what I said.
>
> -----Original Message-----
> From: owner-ietf-ldapbis@OpenLDAP.org
> [mailto:owner-ietf-ldapbis@OpenLDAP.org]On Behalf Of Kurt D. Zeilenga
> Sent: Tuesday, 17 February 2004 17:23
> To: Mark Smith
> Cc: andrew.sciberras@adacel.com; howes@opsware.com;
> ietf-ldapbis@OpenLDAP.org
> Subject: Re: I-D ACTION:draft-ietf-ldapbis-url-05.txt
>
>
> At 03:05 PM 2/16/2004, Mark Smith wrote:
> >>>If an LDAP URL extension is recognised by an implementation, the
> >>>implementation MUST make use of it.
> >>What if you recognise it, but don't implement it?
> >>If it is not critical then I see no reason why the operation should not
> >>proceed.
> >
> >Kurt can probably explain this better than I can... but the goal is
> to be consistent the philopsophy used for LDAP controls in the
> Protocol document.
> >I think "recognized" implies "ability to use" an extension; that
> is, if an implementation recognizes an extension it is able to use it.
>
> I prefer "implement" here over "recognize".  Like a number of
> other protocol tokens, it is possible to "recognize" an
> token without actually implementing the syntax and semantics
> associated with that token.   For instance, a implementation
> could recognize the bindname extension but not implement it
> (maybe the implementation only supports the mandatory-to-implement
> authentication mechanism (e.g., DIGEST-MD5)).
>
> Ron asked:
> >Why are they called extensions and not controls?  It looks a bit
> misleading to me. (LDAP can be extended in a number of ways.)
>
> I think it would be misleading to call them LDAP URL Controls
> as they would confused with LDAP Controls.  LDAP URL Extensions
> are not necessarily LDAP Controls.
>
> Kurt
>
>
>
>



From owner-ietf-ldapbis@OpenLDAP.org  Tue Feb 17 10:43:42 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06763
	for <ldapbis-archive@lists.ietf.org>; Tue, 17 Feb 2004 10:43:41 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1HFdD6x002147;
	Tue, 17 Feb 2004 15:42:40 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1HFYsCa001446;
	Tue, 17 Feb 2004 15:34: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, 17 Feb 2004 15:34:54 +0000
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1HFYq5r001422
	for <ietf-ldapbis@openldap.org>; Tue, 17 Feb 2004 15:34:52 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 KAA05367;
	Tue, 17 Feb 2004 10:34:50 -0500 (EST)
Message-Id: <200402171534.KAA05367@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-10.txt
Date: Tue, 17 Feb 2004 10:34:49 -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-10.txt
	Pages		: 50
	Date		: 2004-2-17
	
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-10.txt

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

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

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


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

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

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

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

Content-Type: text/plain
Content-ID:	<2004-2-17103911.I-D@ietf.org>

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

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

Content-Type: text/plain
Content-ID:	<2004-2-17103911.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-ietf-ldapbis@OpenLDAP.org  Tue Feb 17 10:43:42 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06764
	for <ldapbis-archive@lists.ietf.org>; Tue, 17 Feb 2004 10:43:41 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1HFdD79002147;
	Tue, 17 Feb 2004 15:42:42 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1HFXsVB001253;
	Tue, 17 Feb 2004 15:33: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, 17 Feb 2004 15:33:54 +0000
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1HFXq5r001243
	for <ietf-ldapbis@openldap.org>; Tue, 17 Feb 2004 15:33:52 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 KAA05155;
	Tue, 17 Feb 2004 10:33:50 -0500 (EST)
Message-Id: <200402171533.KAA05155@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-03.txt
Date: Tue, 17 Feb 2004 10:33:50 -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-03.txt
	Pages		: 19
	Date		: 2004-2-17
	
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-03.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-03.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-03.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:	<2004-2-17103602.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ldapbis-strprep-03.txt

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

Content-Type: text/plain
Content-ID:	<2004-2-17103602.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-ietf-ldapbis@OpenLDAP.org  Tue Feb 17 10:43:44 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06768
	for <ldapbis-archive@lists.ietf.org>; Tue, 17 Feb 2004 10:43:42 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1HFdD6v002147;
	Tue, 17 Feb 2004 15:42:40 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1HFXfQi001202;
	Tue, 17 Feb 2004 15:33: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); Tue, 17 Feb 2004 15:33:41 +0000
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1HFXd5r001192
	for <ietf-ldapbis@openldap.org>; Tue, 17 Feb 2004 15:33:40 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 KAA05123;
	Tue, 17 Feb 2004 10:33:37 -0500 (EST)
Message-Id: <200402171533.KAA05123@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-10.txt
Date: Tue, 17 Feb 2004 10:33:37 -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-10.txt
	Pages		: 50
	Date		: 2004-2-17
	
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-10.txt

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

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

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


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

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

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

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

Content-Type: text/plain
Content-ID:	<2004-2-17103553.I-D@ietf.org>

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

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

Content-Type: text/plain
Content-ID:	<2004-2-17103553.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-ietf-ldapbis@OpenLDAP.org  Tue Feb 17 10:44:26 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06970
	for <ldapbis-archive@lists.ietf.org>; Tue, 17 Feb 2004 10:44:25 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1HFdD7D002147;
	Tue, 17 Feb 2004 15:42:43 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1HFZBQf001517;
	Tue, 17 Feb 2004 15:35: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, 17 Feb 2004 15:35:11 +0000
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1HFZ95r001507
	for <ietf-ldapbis@openldap.org>; Tue, 17 Feb 2004 15:35:10 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 KAA05423;
	Tue, 17 Feb 2004 10:35:07 -0500 (EST)
Message-Id: <200402171535.KAA05423@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-22.txt
Date: Tue, 17 Feb 2004 10:35:07 -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-22.txt
	Pages		: 59
	Date		: 2004-2-17
	
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-22.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-22.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-22.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:	<2004-2-17103935.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ldapbis-protocol-22.txt

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

Content-Type: text/plain
Content-ID:	<2004-2-17103935.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-ietf-ldapbis@OpenLDAP.org  Tue Feb 17 10:44:46 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07029
	for <ldapbis-archive@lists.ietf.org>; Tue, 17 Feb 2004 10:44:45 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1HFdD71002147;
	Tue, 17 Feb 2004 15:42:40 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1HFXbH1001185;
	Tue, 17 Feb 2004 15:33: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, 17 Feb 2004 15:33:37 +0000
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1HFXY5r001175
	for <ietf-ldapbis@openldap.org>; Tue, 17 Feb 2004 15:33:35 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 KAA05109;
	Tue, 17 Feb 2004 10:33:32 -0500 (EST)
Message-Id: <200402171533.KAA05109@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-02.txt
Date: Tue, 17 Feb 2004 10:33:32 -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-02.txt
	Pages		: 15
	Date		: 2004-2-17
	
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-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-bcp64-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-bcp64-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:	<2004-2-17103544.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ldapbis-bcp64-02.txt

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

Content-Type: text/plain
Content-ID:	<2004-2-17103544.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-ietf-ldapbis@OpenLDAP.org  Tue Feb 17 10:44:46 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07028
	for <ldapbis-archive@lists.ietf.org>; Tue, 17 Feb 2004 10:44:45 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1HFdD7J002147;
	Tue, 17 Feb 2004 15:42:44 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1HFZHu2001535;
	Tue, 17 Feb 2004 15:35: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); Tue, 17 Feb 2004 15:35:17 +0000
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1HFZG5r001525
	for <ietf-ldapbis@openldap.org>; Tue, 17 Feb 2004 15:35:16 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 KAA05467;
	Tue, 17 Feb 2004 10:35:13 -0500 (EST)
Message-Id: <200402171535.KAA05467@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-13.txt
Date: Tue, 17 Feb 2004 10:35:13 -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-13.txt
	Pages		: 14
	Date		: 2004-2-17
	
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-13.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-13.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-13.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:	<2004-2-17103946.I-D@ietf.org>

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

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

Content-Type: text/plain
Content-ID:	<2004-2-17103946.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-ietf-ldapbis@OpenLDAP.org  Tue Feb 17 10:44:50 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07071
	for <ldapbis-archive@lists.ietf.org>; Tue, 17 Feb 2004 10:44:49 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1HFdD7H002147;
	Tue, 17 Feb 2004 15:42:43 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1HFYBj8001331;
	Tue, 17 Feb 2004 15:34: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, 17 Feb 2004 15:34:11 +0000
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1HFY95r001320
	for <ietf-ldapbis@openldap.org>; Tue, 17 Feb 2004 15:34:09 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 KAA05203;
	Tue, 17 Feb 2004 10:34:06 -0500 (EST)
Message-Id: <200402171534.KAA05203@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-13.txt
Date: Tue, 17 Feb 2004 10:34:05 -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-13.txt
	Pages		: 14
	Date		: 2004-2-17
	
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-13.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-13.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-13.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:	<2004-2-17103630.I-D@ietf.org>

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

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

Content-Type: text/plain
Content-ID:	<2004-2-17103630.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-ietf-ldapbis@OpenLDAP.org  Tue Feb 17 10:44:50 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07072
	for <ldapbis-archive@lists.ietf.org>; Tue, 17 Feb 2004 10:44:49 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1HFdD7F002147;
	Tue, 17 Feb 2004 15:42:43 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1HFY4bv001300;
	Tue, 17 Feb 2004 15:34: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); Tue, 17 Feb 2004 15:34:04 +0000
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1HFY35r001286
	for <ietf-ldapbis@openldap.org>; Tue, 17 Feb 2004 15:34:03 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 KAA05181;
	Tue, 17 Feb 2004 10:34:00 -0500 (EST)
Message-Id: <200402171534.KAA05181@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-22.txt
Date: Tue, 17 Feb 2004 10:34:00 -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-22.txt
	Pages		: 59
	Date		: 2004-2-17
	
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-22.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-22.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-22.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:	<2004-2-17103620.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ldapbis-protocol-22.txt

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

Content-Type: text/plain
Content-ID:	<2004-2-17103620.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-ietf-ldapbis@OpenLDAP.org  Tue Feb 17 10:44:51 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07075
	for <ldapbis-archive@lists.ietf.org>; Tue, 17 Feb 2004 10:44:50 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1HFdD7B002147;
	Tue, 17 Feb 2004 15:42:42 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1HFZ0Ci001475;
	Tue, 17 Feb 2004 15:35:00 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, 17 Feb 2004 15:35:00 +0000
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1HFYw5r001464
	for <ietf-ldapbis@openldap.org>; Tue, 17 Feb 2004 15:34: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 KAA05380;
	Tue, 17 Feb 2004 10:34:56 -0500 (EST)
Message-Id: <200402171534.KAA05380@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-03.txt
Date: Tue, 17 Feb 2004 10:34:56 -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-03.txt
	Pages		: 19
	Date		: 2004-2-17
	
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-03.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-03.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-03.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:	<2004-2-17103919.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ldapbis-strprep-03.txt

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

Content-Type: text/plain
Content-ID:	<2004-2-17103919.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-ietf-ldapbis@OpenLDAP.org  Tue Feb 17 10:44:55 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07127
	for <ldapbis-archive@lists.ietf.org>; Tue, 17 Feb 2004 10:44:54 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1HFdD73002147;
	Tue, 17 Feb 2004 15:42:41 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1HFYmSG001399;
	Tue, 17 Feb 2004 15:34: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); Tue, 17 Feb 2004 15:34:48 +0000
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1HFYk5r001389
	for <ietf-ldapbis@openldap.org>; Tue, 17 Feb 2004 15:34: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 KAA05349;
	Tue, 17 Feb 2004 10:34:44 -0500 (EST)
Message-Id: <200402171534.KAA05349@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-02.txt
Date: Tue, 17 Feb 2004 10:34:44 -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-02.txt
	Pages		: 15
	Date		: 2004-2-17
	
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-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-bcp64-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-bcp64-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:	<2004-2-17103904.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ldapbis-bcp64-02.txt

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

Content-Type: text/plain
Content-ID:	<2004-2-17103904.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-ietf-ldapbis@OpenLDAP.org  Tue Feb 17 11:34:04 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06762
	for <ldapbis-archive@lists.ietf.org>; Tue, 17 Feb 2004 10:43:41 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1HFdD75002147;
	Tue, 17 Feb 2004 15:42:41 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1HFZ6br001500;
	Tue, 17 Feb 2004 15:35: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); Tue, 17 Feb 2004 15:35:06 +0000
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1HFZ45r001490
	for <ietf-ldapbis@openldap.org>; Tue, 17 Feb 2004 15:35: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 KAA05400;
	Tue, 17 Feb 2004 10:35:02 -0500 (EST)
Message-Id: <200402171535.KAA05400@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-roadmap-04.txt
Date: Tue, 17 Feb 2004 10:35:01 -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: Technical Specification Road Map
	Author(s)	: K. Zeilenga
	Filename	: draft-ietf-ldapbis-roadmap-04.txt
	Pages		: 6
	Date		: 2004-2-17
	
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 provides
a roadmap of the LDAP Technical Specification.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ldapbis-roadmap-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-roadmap-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-roadmap-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:	<2004-2-17103926.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ldapbis-roadmap-04.txt

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

Content-Type: text/plain
Content-ID:	<2004-2-17103926.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-ietf-ldapbis@OpenLDAP.org  Tue Feb 17 11:34:05 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06772
	for <ldapbis-archive@lists.ietf.org>; Tue, 17 Feb 2004 10:43:43 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1HFdD77002147;
	Tue, 17 Feb 2004 15:42:41 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1HFXxiI001275;
	Tue, 17 Feb 2004 15:33: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); Tue, 17 Feb 2004 15:33:59 +0000
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1HFXv5r001262
	for <ietf-ldapbis@openldap.org>; Tue, 17 Feb 2004 15:33:57 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 KAA05168;
	Tue, 17 Feb 2004 10:33:55 -0500 (EST)
Message-Id: <200402171533.KAA05168@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-roadmap-04.txt
Date: Tue, 17 Feb 2004 10:33:54 -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: Technical Specification Road Map
	Author(s)	: K. Zeilenga
	Filename	: draft-ietf-ldapbis-roadmap-04.txt
	Pages		: 6
	Date		: 2004-2-17
	
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 provides
a roadmap of the LDAP Technical Specification.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ldapbis-roadmap-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-roadmap-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-roadmap-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:	<2004-2-17103611.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ldapbis-roadmap-04.txt

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

Content-Type: text/plain
Content-ID:	<2004-2-17103611.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-ietf-ldapbis@OpenLDAP.org  Tue Feb 17 19:23:02 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA18802
	for <ldapbis-archive@lists.ietf.org>; Tue, 17 Feb 2004 19:23:01 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1I0LH5v071124;
	Wed, 18 Feb 2004 00:21:54 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1I0GosT070958;
	Wed, 18 Feb 2004 00:16: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); Wed, 18 Feb 2004 00:16:50 +0000
Received: from usilms54.ca.com (mail12.ca.com [141.202.248.38])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1I0Gm5r070948
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 18 Feb 2004 00:16:48 GMT
	(envelope-from Ron.Ramsay@ca.com)
Received: from usilms81.ca.com ([141.202.201.51]) by usilms54.ca.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Tue, 17 Feb 2004 19:16:47 -0500
Received: from ausyms81.ca.com ([155.35.201.11]) by usilms81.ca.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Tue, 17 Feb 2004 19:16:47 -0500
Received: from ausyms21.ca.com ([155.35.201.5]) by ausyms81.ca.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Wed, 18 Feb 2004 11:16:44 +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: I-D ACTION:draft-ietf-ldapbis-url-05.txt
Date: Wed, 18 Feb 2004 11:16:44 +1100
Message-ID: <1395B4B334FCC143B36AF788E68B6381010D12CE@ausyms21.ca.com>
Thread-Topic: I-D ACTION:draft-ietf-ldapbis-url-05.txt
Thread-Index: AcP1U6hcOycNdM7iRtKiqhkooDR5AAAYLtsw
From: "Ramsay, Ron" <Ron.Ramsay@ca.com>
To: "John McMeeking" <jmcmeek@us.ibm.com>, <ietf-ldapbis@OpenLDAP.org>
X-OriginalArrivalTime: 18 Feb 2004 00:16:44.0345 (UTC) FILETIME=[7D68E290:01C3F5B4]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by boole.openldap.org id i1I0Gn5r070949
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.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

And it can be marked critical using '!'?

-----Original Message-----
From: John McMeeking [mailto:jmcmeek@us.ibm.com]
Sent: Tuesday, 17 February 2004 23:43
To: Ramsay, Ron; ietf-ldapbis@OpenLDAP.org
Subject: RE: I-D ACTION:draft-ietf-ldapbis-url-05.txt






RFC 2255 defines a bindname extension; when using the URL, the client was
to authenticate to the server as the specified DN.  This is an example of
an URL extension that is not a LDAP control or extended request.


John  McMeeking


owner-ietf-ldapbis@OpenLDAP.org wrote on 02/17/2004 12:45:21 AM:

> I doubt they are LDAP URL Extensions as they are part of the base
> definition! I believe the only things you can put a '!' in front of
> are LDAP controls, so I stick with what I said.
>
> -----Original Message-----
> From: owner-ietf-ldapbis@OpenLDAP.org
> [mailto:owner-ietf-ldapbis@OpenLDAP.org]On Behalf Of Kurt D. Zeilenga
> Sent: Tuesday, 17 February 2004 17:23
> To: Mark Smith
> Cc: andrew.sciberras@adacel.com; howes@opsware.com;
> ietf-ldapbis@OpenLDAP.org
> Subject: Re: I-D ACTION:draft-ietf-ldapbis-url-05.txt
>
>
> At 03:05 PM 2/16/2004, Mark Smith wrote:
> >>>If an LDAP URL extension is recognised by an implementation, the
> >>>implementation MUST make use of it.
> >>What if you recognise it, but don't implement it?
> >>If it is not critical then I see no reason why the operation should not
> >>proceed.
> >
> >Kurt can probably explain this better than I can... but the goal is
> to be consistent the philopsophy used for LDAP controls in the
> Protocol document.
> >I think "recognized" implies "ability to use" an extension; that
> is, if an implementation recognizes an extension it is able to use it.
>
> I prefer "implement" here over "recognize".  Like a number of
> other protocol tokens, it is possible to "recognize" an
> token without actually implementing the syntax and semantics
> associated with that token.   For instance, a implementation
> could recognize the bindname extension but not implement it
> (maybe the implementation only supports the mandatory-to-implement
> authentication mechanism (e.g., DIGEST-MD5)).
>
> Ron asked:
> >Why are they called extensions and not controls?  It looks a bit
> misleading to me. (LDAP can be extended in a number of ways.)
>
> I think it would be misleading to call them LDAP URL Controls
> as they would confused with LDAP Controls.  LDAP URL Extensions
> are not necessarily LDAP Controls.
>
> Kurt
>
>
>
>





From owner-ietf-ldapbis@OpenLDAP.org  Tue Feb 17 19:40:22 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA19339
	for <ldapbis-archive@lists.ietf.org>; Tue, 17 Feb 2004 19:40:21 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1I0dG5x071886;
	Wed, 18 Feb 2004 00:39:20 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1I0bOSN071766;
	Wed, 18 Feb 2004 00:37: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, 18 Feb 2004 00:37:24 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1I0bN5r071756
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 18 Feb 2004 00:37:23 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from gypsy.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.10/8.12.10) with ESMTP id i1I0bM7s014072
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 18 Feb 2004 00:37:23 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.1.1.0.20040217163222.04c1b148@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Tue, 17 Feb 2004 16:37:12 -0800
To: <ietf-ldapbis@OpenLDAP.org>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Please review: draft-ietf-ldapbis-authmeth
In-Reply-To: <s0300a32.092@prv-mail20.provo.novell.com>
References: <s0300a32.092@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 11:08 PM 2/15/2004, Roger Harrison wrote:
>I believe I have represented the discussion consensus on this issue for the -10 draft of authmeth.

Thanks.  I ask the WG to carefully review this revision of authmeth I-D and
comment to the list regarding any and all technical issues which concern you.
Editorial comments should be sent directly to the editor.  If after you review
this revision you have no comments, please let me know by private email.

I ask that you review and comment so within the next couple of weeks so that
issues which need face-to-face time to resolve can be discussed at IETF#59.
We'll consider next steps (e.g., when issue the WG Last Call) at IETF#59.

Kurt (LDAPBIS co-chair)



From owner-ietf-ldapbis@OpenLDAP.org  Tue Feb 17 20:04:14 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20889
	for <ldapbis-archive@lists.ietf.org>; Tue, 17 Feb 2004 20:04:14 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1I13H5v072568;
	Wed, 18 Feb 2004 01:03:26 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1I1191A072542;
	Wed, 18 Feb 2004 01:01: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, 18 Feb 2004 01:01:09 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1I1185r072532
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 18 Feb 2004 01:01:08 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from gypsy.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.10/8.12.10) with ESMTP id i1I10x7s014376;
	Wed, 18 Feb 2004 01:00:59 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.1.1.0.20040217164946.04ceec20@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Tue, 17 Feb 2004 17:00:49 -0800
To: "Roger Harrison" <RHARRISON@novell.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: authmeth-09 comments
Cc: <ietf-ldapbis@OpenLDAP.org>
In-Reply-To: <s0301954.005@prv-mail20.provo.novell.com>
References: <s0301954.005@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 12:13 AM 2/16/2004, Roger Harrison wrote:
>Is your concern regarding the lack of attention to the tables directed to WG members in general or from me?

I am particularly concerned that the tables are not getting adequate
review by WG members.  I ask that reviewers pay particular attention
to these tables and specifically comment on their soundness.  (Please
comment as I previously requested.)

>I reworked the tables completely for the -09 draft and feel quite confident that they are much better than they have ever been before. I would appreciate some more eyes on them at this point, but I reviewed every production in the tables for the -09 draft.
> 
>Roger
>
>>>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 1/8/2004 5:45:45 PM >>>
>
>I believe some find the table useful. Personally, I worry that the
>table might not accurately reflect the prose. (As co-chair, I'm
>concerned by the lack of attention the tables are getting.)
>
>Kurt



From owner-ietf-ldapbis@OpenLDAP.org  Tue Feb 17 20:40:38 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA22356
	for <ldapbis-archive@lists.ietf.org>; Tue, 17 Feb 2004 20:40:38 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1I1dH5v073811;
	Wed, 18 Feb 2004 01:39:35 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1I1aa8R073711;
	Wed, 18 Feb 2004 01:36: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); Wed, 18 Feb 2004 01:36:36 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1I1aZ5r073701
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 18 Feb 2004 01:36:35 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from gypsy.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.10/8.12.10) with ESMTP id i1I1aU7s014868;
	Wed, 18 Feb 2004 01:36:30 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.1.1.0.20040217170657.04c0f080@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Tue, 17 Feb 2004 17:36:20 -0800
To: "Roger Harrison" <RHARRISON@novell.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: authmeth: unsupported <TLS+anonymous bind>
Cc: <ietf-ldapbis@OpenLDAP.org>
In-Reply-To: <s0302616.063@prv-mail20.provo.novell.com>
References: <s0302616.063@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>

Roger,

I think we more clear as to what is required to implement, versus
what, if implemented, must be implemented in a particular way.
There may also be cases where implementation of an elective
feature may require implementation of some other feature, which
by itself, is elective.

RFC 2829 was a bit unclear to precise what was required to
implement (because of use of conditional phrasing).  Per prior WG
discussions, I think should simply state:

All implementations which implement any authentication mechanism
(other than simple anonymous) MUST implement the SASL DIGEST-MD5
mechanism.  All server MUST implement anonymous authentication.

For historical reasons, simple DN/password Bind should be RECOMMENDED.
However, where simple DN/password Bind is implemented, Start TLS
MUST be implemented.  And, as recently discussed, servers SHOULD
(by default) disallow use of simple DN/password when adequate
security protections (e.g., TLS) have not been established.

As we have a mandatory-to-implement "strong" mechanism, including
support for both integrity and data confidential protections, there
is (IMO) insufficient (rfc2026/rfc2119) reason to mandate or
recommend implementation of TLS (Start TLS).  Where TLS is implemented,
I also believe there is insufficient reason to mandate or recommend
support for simple anonymous, simple DN+password, and/or EXTERNAL.
These should all be optional.

Kurt

At 01:08 AM 2/16/2004, Roger Harrison wrote:
>For authmeth -10, the single, consolidated section on anonymous authentication now states that LDAP implementations MUST support anonymous authentication with no other qualifications. The fact that Start TLS is a required-to-implement operation implies that implementations MUST support anonymous authentication when TLS is established.
> 
>Roger
>
>>>> Hallvard B Furuseth <h.b.furuseth@usit.uio.no> 1/3/2004 7:34:17 AM >>>
>authmeth-09 says:
>
>> 5. Anonymous Authentication
>
>> LDAP implementations MUST support anonymous authentication, as
>> defined in section 5.1.
>>
>> LDAP implementations MAY support anonymous authentication with TLS,
>> as defined in section 5.2.
>
>Huh? Why allow implementations to not support anonymous
>authentication on secure connections, but support it on insecure
>ones? I could understand it if it was the other way around - along
>with not implementing Simple Bind at all without TLS.
>
>-- 
>Hallvard



From owner-ietf-ldapbis@OpenLDAP.org  Tue Feb 17 21:04:06 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA22901
	for <ldapbis-archive@lists.ietf.org>; Tue, 17 Feb 2004 21:04:06 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1I23H5v074420;
	Wed, 18 Feb 2004 02:03:20 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1I20eqA074367;
	Wed, 18 Feb 2004 02:00: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); Wed, 18 Feb 2004 02:00:40 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1I20d5r074357
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 18 Feb 2004 02:00:39 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from gypsy.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.10/8.12.10) with ESMTP id i1I20c7s015207;
	Wed, 18 Feb 2004 02:00:38 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.1.1.0.20040217173841.04c10c30@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Tue, 17 Feb 2004 18:00:27 -0800
To: "Roger Harrison" <RHARRISON@novell.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: authmeth: missing protection
Cc: <ietf-ldapbis@OpenLDAP.org>, <h.b.furuseth@usit.uio.no>
In-Reply-To: <s030251d.050@prv-mail20.provo.novell.com>
References: <s030251d.050@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 01:03 AM 2/16/2004, Roger Harrison wrote:
>> >>> Hallvard B Furuseth <h.b.furuseth@usit.uio.no> 1/3/2004 7:34:57 AM >>>
>> authmeth-09 says:
>> > 6.2. Digest Authentication
>> > (...) [DIGEST-MD5]. This provides client
>> > authentication with protection against passive eavesdropping
>> > attacks, but does not provide protection against active intermediary
>> > attacks.
>> What does this mean? That DIGEST-MD5 is vulnerable to
>> man-in-the-middle attacks? I didn't think it was.
>I don't have enough experience with Digest Authentication to speak to this. Can someone else in the WG please comment?

DIGEST-MD5 is prone to at least one active attack, qop substitution,
as discussed in 6.2 of RFC 2831.  The qop substitution attack can
be mitigated (as discussed in 6.2 of RFC 2831).

John asks:
>I can't speak to this issue specifically, but it raises a minor question:
>Is there any reason to say anyhting about this in authmeth?  Weaknesses of
>DIGEST-MD5 apply to any protocol that supports it, not just LDAP.

Given that DIGEST-MD5 is LDAP's "strong" authentication
mechanism, I believe it is appropriate for this I-D to state
that DIGEST-MD5 is prone to at least one active attack and
then refer readers to the DIGEST-MD5 specification for further
details.

>The same
>thing applies to discussion of TLS ciphers that are recommended or not.  Is
>it common practice to list such issues in standards for other protocols
>that support such technologies?

Yes, because the applicability of ciphers differ from protocol to
protocol.  We need to detail which are applicable to LDAP.

>It seems like the kind of thing that
>should be said in one place, and applies to all applications of that
>particular technology.

But it doesn't necessarily apply to all applications.

Kurt 



From owner-ietf-ldapbis@OpenLDAP.org  Wed Feb 18 10:17:40 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19046
	for <ldapbis-archive@lists.ietf.org>; Wed, 18 Feb 2004 10:17:39 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1IF9O67011591;
	Wed, 18 Feb 2004 15:16:25 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1IExEjh010951;
	Wed, 18 Feb 2004 14:59: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); Wed, 18 Feb 2004 14:59:14 +0000
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1IEx55r010934
	for <ietf-ldapbis@openldap.org>; Wed, 18 Feb 2004 14:59:06 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 JAA15601;
	Wed, 18 Feb 2004 09:59:01 -0500 (EST)
Message-Id: <200402181459.JAA15601@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-10.txt
Date: Wed, 18 Feb 2004 09:59:01 -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-10.txt
	Pages		: 55
	Date		: 2004-2-18
	
This document describes authentication methods and connection level 
security mechanisms of the Lightweight Directory Access Protocol 
(LDAP).

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

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

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

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


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

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

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

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

Content-Type: text/plain
Content-ID:	<2004-2-18101212.I-D@ietf.org>

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

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

Content-Type: text/plain
Content-ID:	<2004-2-18101212.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-ietf-ldapbis@OpenLDAP.org  Wed Feb 18 13:35:35 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07440
	for <ldapbis-archive@lists.ietf.org>; Wed, 18 Feb 2004 13:35:35 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1IIYb5r031916;
	Wed, 18 Feb 2004 18:34:37 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1IILY7F031072;
	Wed, 18 Feb 2004 18:21:34 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, 18 Feb 2004 18:21:34 +0000
Received: from nb2.stroeder.com (krl9-d9bb43e9.pool.mediaWays.net [217.187.67.233])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1IILW5r031061
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 18 Feb 2004 18:21:33 GMT
	(envelope-from michael@stroeder.com)
Received: from stroeder.com (localhost [127.0.0.1])
	by nb2.stroeder.com (Postfix) with ESMTP
	id 757D91E371; Wed, 18 Feb 2004 18:16:10 +0100 (CET)
Message-ID: <40339DD9.7080302@stroeder.com>
Date: Wed, 18 Feb 2004 18:16:09 +0100
From: =?ISO-8859-1?Q?Michael_Str=F6der?= <michael@stroeder.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: de-de, de, en-us, en
MIME-Version: 1.0
To: "Ramsay, Ron" <Ron.Ramsay@ca.com>
Cc: ietf-ldapbis@OpenLDAP.org
Subject: Re: I-D ACTION:draft-ietf-ldapbis-url-05.txt
References: <1395B4B334FCC143B36AF788E68B6381010D12CE@ausyms21.ca.com>
In-Reply-To: <1395B4B334FCC143B36AF788E68B6381010D12CE@ausyms21.ca.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Ramsay, Ron wrote:
> And it can be marked critical using '!'?

Yes, why not?

It's up to the LDAP application whether it is able to apply any reasonable 
semantics to !bindname=<Bind-DN>.

Personally I'd prefer draft-ietf-ldapbis-url not as being strictly tied or 
limited to draft-ietf-ldapbis-protocol.

Ciao, Michael.


From owner-ietf-ldapbis@OpenLDAP.org  Sun Feb 22 22:36:37 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA21599
	for <ldapbis-archive@lists.ietf.org>; Sun, 22 Feb 2004 22:36:36 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1N3Y05v032670;
	Mon, 23 Feb 2004 03:35:14 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1N3ShM1032577;
	Mon, 23 Feb 2004 03:28: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, 23 Feb 2004 03:28:43 +0000
Received: from prv-mail20.provo.novell.com (prv-mail20.provo.novell.com [137.65.81.122])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1N3Sg5r032565
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 23 Feb 2004 03:28:42 GMT
	(envelope-from smclain@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Sun, 22 Feb 2004 20:28:21 -0700
Message-Id: <s03910e5.009@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.2 Beta
Date: Sun, 22 Feb 2004 20:28:10 -0700
From: "Steve McLain" <smclain@novell.com>
To: <ietf-ldapbis@OpenLDAP.org>
Subject: dITStructureRules
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__Part38194C5A.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.

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

What is the desired/proper behavior if when adding a new entry, there
are two or more possible dITStructureRules that could equally be the
governingStructureRule?  
 
For exampe:
NameForm1   mandatory cn, optional ou, namedObjectClass orgPerson 
NameForm2   mandatory cn, optional sn, namedObjectClass orgPerson
 
StructureRule5
     NameForm     nameForm1
     SuperiorRule   StructureRule4
 
StructureRule6
      NameForm     nameForm2
      SuperiorRule   StructureRule4
 
StructureRule7
       NameForm    nameform2
       SuperiorRule  Structurerule6
 
Attempting to add a orgPerson object with the rdn of "cn=ldapuser" to a
parent object that has a governingStructureRule
of StructureRule4.
 
What dITStructureRule is set for the governingStructureRule or should
this error?
I have looked through X.500 and the current model draft, I have not
found the answer yet.
 
Steve McLain

--=__Part38194C5A.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 6.00.2800.1400" name=3DGENERATOR></HEAD>
<BODY style=3D"MARGIN: 4px 4px 1px; FONT: 10pt Tahoma">
<DIV>What is the desired/proper behavior if when adding a new entry, there =
are two or more&nbsp;possible dITStructureRules that could equally be the =
governingStructureRule?&nbsp; </DIV>
<DIV>&nbsp;</DIV>
<DIV>For exampe:</DIV>
<DIV>NameForm1&nbsp;&nbsp; mandatory&nbsp;cn,&nbsp;optional ou,&nbsp;namedO=
bjectClass orgPerson&nbsp;</DIV>
<DIV>NameForm2&nbsp;&nbsp; mandatory cn, optional sn, namedObjectClass =
orgPerson</DIV>
<DIV>&nbsp;</DIV>
<DIV>StructureRule5</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp; NameForm&nbsp;&nbsp;&nbsp;&nbsp; nameForm1</D=
IV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp; SuperiorRule&nbsp;&nbsp; StructureRule4</DIV>=

<DIV>&nbsp;</DIV>
<DIV>StructureRule6</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NameForm&nbsp;&nbsp;&nbsp;&nbsp; =
nameForm2</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SuperiorRule&nbsp;&nbsp; StructureRule4=
</DIV>
<DIV>&nbsp;</DIV>
<DIV>StructureRule7</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NameForm&nbsp;&nbsp;&nbsp; =
nameform2</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SuperiorRule&nbsp; Structurerule6=
</DIV>
<DIV>&nbsp;</DIV>
<DIV>Attempting to add a orgPerson object with the rdn of "cn=3Dldapuser" =
to a parent object that has a governingStructureRule</DIV>
<DIV>of StructureRule4.</DIV>
<DIV>&nbsp;</DIV>
<DIV>What dITStructureRule is set for the governingStructureRule or should =
this error?</DIV>
<DIV>I have looked through X.500 and the current model draft, I have not =
found the answer yet.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Steve McLain</DIV></BODY></HTML>

--=__Part38194C5A.0__=--


From owner-ietf-ldapbis@OpenLDAP.org  Tue Feb 24 12:06:51 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29665
	for <ldapbis-archive@lists.ietf.org>; Tue, 24 Feb 2004 12:06:50 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1OH4I5v046716;
	Tue, 24 Feb 2004 17:05:20 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1OH0Qct046532;
	Tue, 24 Feb 2004 17:00: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, 24 Feb 2004 17:00:26 +0000
Received: from prv-mail20.provo.novell.com (prv-mail20.provo.novell.com [137.65.81.122])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1OH0O5r046505
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 24 Feb 2004 17:00:25 GMT
	(envelope-from jimse@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Tue, 24 Feb 2004 10:00:04 -0700
Message-Id: <s03b20a4.032@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.2 Beta
Date: Tue, 24 Feb 2004 09:59:39 -0700
From: "Jim Sermersheim" <jimse@novell.com>
To: <ietf-ldapbis@OpenLDAP.org>
Subject: Re: dITStructureRules
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__Part7A5B0CEB.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.

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

It would be interesting to know what some X.500 vendors currently do.
This seems to beg for some kind of 'ambiguousStructuralRule' error.
 
Jim

>>> "Steve McLain" <smclain@novell.com> 2/22/04 8:28:10 PM >>>

What is the desired/proper behavior if when adding a new entry, there
are two or more possible dITStructureRules that could equally be the
governingStructureRule?  
 
For exampe:
NameForm1   mandatory cn, optional ou, namedObjectClass orgPerson 
NameForm2   mandatory cn, optional sn, namedObjectClass orgPerson
 
StructureRule5
     NameForm     nameForm1
     SuperiorRule   StructureRule4
 
StructureRule6
      NameForm     nameForm2
      SuperiorRule   StructureRule4
 
StructureRule7
       NameForm    nameform2
       SuperiorRule  Structurerule6
 
Attempting to add a orgPerson object with the rdn of "cn=ldapuser" to a
parent object that has a governingStructureRule
of StructureRule4.
 
What dITStructureRule is set for the governingStructureRule or should
this error?
I have looked through X.500 and the current model draft, I have not
found the answer yet.
 
Steve McLain


--=__Part7A5B0CEB.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 6.00.2800.1400" name=3DGENERATOR></HEAD>
<BODY style=3D"MARGIN: 4px 4px 1px; FONT: 10pt Microsoft Sans Serif">
<DIV>It would be interesting to know what some X.500 vendors currently do. =
This seems to beg for some kind of 'ambiguousStructuralRule' error.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Jim<BR><BR>&gt;&gt;&gt; "Steve McLain" &lt;smclain@novell.com&gt; =
2/22/04 8:28:10 PM &gt;&gt;&gt;<BR></DIV>
<DIV style=3D"FONT: 10pt Tahoma; COLOR: #000000">
<DIV>What is the desired/proper behavior if when adding a new entry, there =
are two or more&nbsp;possible dITStructureRules that could equally be the =
governingStructureRule?&nbsp; </DIV>
<DIV>&nbsp;</DIV>
<DIV>For exampe:</DIV>
<DIV>NameForm1&nbsp;&nbsp; mandatory&nbsp;cn,&nbsp;optional ou,&nbsp;namedO=
bjectClass orgPerson&nbsp;</DIV>
<DIV>NameForm2&nbsp;&nbsp; mandatory cn, optional sn, namedObjectClass =
orgPerson</DIV>
<DIV>&nbsp;</DIV>
<DIV>StructureRule5</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp; NameForm&nbsp;&nbsp;&nbsp;&nbsp; nameForm1</D=
IV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp; SuperiorRule&nbsp;&nbsp; StructureRule4</DIV>=

<DIV>&nbsp;</DIV>
<DIV>StructureRule6</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NameForm&nbsp;&nbsp;&nbsp;&nbsp; =
nameForm2</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SuperiorRule&nbsp;&nbsp; StructureRule4=
</DIV>
<DIV>&nbsp;</DIV>
<DIV>StructureRule7</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NameForm&nbsp;&nbsp;&nbsp; =
nameform2</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SuperiorRule&nbsp; Structurerule6=
</DIV>
<DIV>&nbsp;</DIV>
<DIV>Attempting to add a orgPerson object with the rdn of "cn=3Dldapuser" =
to a parent object that has a governingStructureRule</DIV>
<DIV>of StructureRule4.</DIV>
<DIV>&nbsp;</DIV>
<DIV>What dITStructureRule is set for the governingStructureRule or should =
this error?</DIV>
<DIV>I have looked through X.500 and the current model draft, I have not =
found the answer yet.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Steve McLain</DIV></DIV></BODY></HTML>

--=__Part7A5B0CEB.0__=--


From owner-ietf-ldapbis@OpenLDAP.org  Tue Feb 24 18:08:55 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15780
	for <ldapbis-archive@lists.ietf.org>; Tue, 24 Feb 2004 18:08:55 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1ON7Z61068861;
	Tue, 24 Feb 2004 23:08:03 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1OMfBRv066393;
	Tue, 24 Feb 2004 22:41: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, 24 Feb 2004 22:41:11 +0000
Received: from adacel.com (gunsmoke.adacel.com.au [210.11.130.7])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1OMf85r066308
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 24 Feb 2004 22:41:10 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.5.9)
	id <B000219071>; Wed, 25 Feb 2004 09:31:41 +1100
Received: (qmail 25800 invoked from network); 24 Feb 2004 22:40:47 -0000
Received: from unknown (HELO adacel.com.au) (10.32.24.165)
  by nexus.adacel.com with SMTP; 24 Feb 2004 22:40:47 -0000
Message-ID: <403BD2EE.8030209@adacel.com.au>
Date: Wed, 25 Feb 2004 09:40:46 +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: ietf-ldapbis@OpenLDAP.org
Subject: Re: dITStructureRules
References: <s03b20a4.032@prv-mail20.provo.novell.com>
In-Reply-To: <s03b20a4.032@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


In the Adacel directory server we disallow ambiguous name forms in the
schema. An update that attempts to add an ambiguous name form to a
subschema subentry fails with a constraintViolation error.

To the best of my knowledge, X.500 doesn't say what to do with ambiguous
name forms. We chose to disallow them.

Regards,
Steven

Jim Sermersheim wrote:
> It would be interesting to know what some X.500 vendors currently do. 
> This seems to beg for some kind of 'ambiguousStructuralRule' error.
>  
> Jim
> 
>  >>> "Steve McLain" <smclain@novell.com> 2/22/04 8:28:10 PM >>>
> What is the desired/proper behavior if when adding a new entry, there 
> are two or more possible dITStructureRules that could equally be the 
> governingStructureRule? 
>  
> For exampe:
> NameForm1   mandatory cn, optional ou, namedObjectClass orgPerson 
> NameForm2   mandatory cn, optional sn, namedObjectClass orgPerson
>  
> StructureRule5
>      NameForm     nameForm1
>      SuperiorRule   StructureRule4
>  
> StructureRule6
>       NameForm     nameForm2
>       SuperiorRule   StructureRule4
>  
> StructureRule7
>        NameForm    nameform2
>        SuperiorRule  Structurerule6
>  
> Attempting to add a orgPerson object with the rdn of "cn=ldapuser" to a 
> parent object that has a governingStructureRule
> of StructureRule4.
>  
> What dITStructureRule is set for the governingStructureRule or should 
> this error?
> I have looked through X.500 and the current model draft, I have not 
> found the answer yet.
>  
> Steve McLain



From owner-ietf-ldapbis@OpenLDAP.org  Tue Feb 24 18:35:26 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17130
	for <ldapbis-archive@lists.ietf.org>; Tue, 24 Feb 2004 18:35:25 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1ONYY5r070696;
	Tue, 24 Feb 2004 23:34:34 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1ONLTc1069967;
	Tue, 24 Feb 2004 23:21: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, 24 Feb 2004 23:21:29 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1ONLS5r069957
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 24 Feb 2004 23:21:28 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from gypsy.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.10/8.12.10) with ESMTP id i1ONLLMs035022;
	Tue, 24 Feb 2004 23:21:21 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.1.1.0.20040224151851.04b5aa28@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Tue, 24 Feb 2004 15:21:16 -0800
To: Steven Legg <steven.legg@adacel.com.au>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: dITStructureRules
Cc: ietf-ldapbis@OpenLDAP.org
In-Reply-To: <403BD2EE.8030209@adacel.com.au>
References: <s03b20a4.032@prv-mail20.provo.novell.com>
 <403BD2EE.8030209@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 02:40 PM 2/24/2004, Steven Legg wrote:
>In the Adacel directory server we disallow ambiguous name forms in the
>schema. An update that attempts to add an ambiguous name form to a
>subschema subentry fails with a constraintViolation error.
>
>To the best of my knowledge, X.500 doesn't say what to do with ambiguous
>name forms. We chose to disallow them.

I don't recall any specific statement, but doesn't X.501
contain a general statement that implies DSA are to ensure
that the subschema is, at least, self consistent.  Anyways,
folks who think some sort of specific statement is needed in
[Models] should offer text for the WG to consider.

Regards, Kurt


>Regards,
>Steven
>
>Jim Sermersheim wrote:
>>It would be interesting to know what some X.500 vendors currently do. This seems to beg for some kind of 'ambiguousStructuralRule' error.
>> 
>>Jim
>> >>> "Steve McLain" <smclain@novell.com> 2/22/04 8:28:10 PM >>>
>>What is the desired/proper behavior if when adding a new entry, there are two or more possible dITStructureRules that could equally be the governingStructureRule?  For exampe:
>>NameForm1   mandatory cn, optional ou, namedObjectClass orgPerson NameForm2   mandatory cn, optional sn, namedObjectClass orgPerson
>> 
>>StructureRule5
>>     NameForm     nameForm1
>>     SuperiorRule   StructureRule4
>> 
>>StructureRule6
>>      NameForm     nameForm2
>>      SuperiorRule   StructureRule4
>> 
>>StructureRule7
>>       NameForm    nameform2
>>       SuperiorRule  Structurerule6
>> 
>>Attempting to add a orgPerson object with the rdn of "cn=ldapuser" to a parent object that has a governingStructureRule
>>of StructureRule4.
>> 
>>What dITStructureRule is set for the governingStructureRule or should this error?
>>I have looked through X.500 and the current model draft, I have not found the answer yet.
>> 
>>Steve McLain



From owner-ietf-ldapbis@OpenLDAP.org  Wed Feb 25 16:53:38 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA17265
	for <ldapbis-archive@lists.ietf.org>; Wed, 25 Feb 2004 16:53:37 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1PLiC6B030465;
	Wed, 25 Feb 2004 21:52:42 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1PLSXXG028697;
	Wed, 25 Feb 2004 21:28: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, 25 Feb 2004 21:28:33 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1PLSW5r028684
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 25 Feb 2004 21:28:32 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from gypsy.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.10/8.12.10) with ESMTP id i1PLSVMs050551
	for <ietf-ldapbis@openldap.org>; Wed, 25 Feb 2004 21:28:31 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.1.1.0.20040225132748.02c374c8@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Wed, 25 Feb 2004 13:28:25 -0800
To: ietf-ldapbis@OpenLDAP.org
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: LDAPBIS agenda
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>

Here's the agenda for next week's meeting...


LDAP Revision WG (LDAPBIS)

TUESDAY, March 2 at 1545-1645
=============================

CHAIRS:
	RL "Bob" Morgan <rlmorgan@washington.edu>
	Kurt Zeilenga <kurt@openLDAP.org> 

AGENDA:

0) Preliminaries (Blue Sheets, Scribes) - Chairs - 1m
1) WG Status Summary - Chairs - 5m
2) draft-ietf-ldapbis-protocol - 15m - Jim
3) draft-ietf-ldapbis-authmeth - 15m - Jim
4) other outstanding issues - 10m - Editors
   draft-ietf-ldapbis-*
4) Milestone review - Chairs - 5m
5) Open mic - Floor - remaining time




From owner-ietf-ldapbis@OpenLDAP.org  Fri Feb 27 02:12:13 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA16422
	for <ldapbis-archive@lists.ietf.org>; Fri, 27 Feb 2004 02:12:12 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1R6uMZR088031;
	Fri, 27 Feb 2004 07:11:09 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1R6rV1T087749;
	Fri, 27 Feb 2004 06:53: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); Fri, 27 Feb 2004 06:53:31 +0000
Received: from pat.uio.no (IDENT:7411@pat.uio.no [129.240.130.16])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1R6rTYT087735
	for <ietf-ldapbis@openldap.org>; Fri, 27 Feb 2004 06:53: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 1AwbsD-0007I0-Hb
	for ietf-ldapbis@openldap.org; Fri, 27 Feb 2004 07:53:25 +0100
Received: from bombur.uio.no ([129.240.186.42])
	by mail-mx3.uio.no with esmtp (Exim 4.14)
	id 1AwbsA-0001s9-Jk; Fri, 27 Feb 2004 07:53:22 +0100
Received: from hbf by bombur.uio.no with local (Exim 2.12 #7)
	id 1AwbsA-00066y-00; Fri, 27 Feb 2004 07:53:22 +0100
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Message-Id: <HBF.20040227jcov@bombur.uio.no>
To: ietf-ldapbis@OpenLDAP.org
Subject: authmeth: passwords in the clear
Date: Fri, 27 Feb 2004 07:53:22 +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
X-UiO-Spam-info: not spam, SpamAssassin (score=0, required 12)
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.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-10 says:

> 11. General Requirements for Password-based Authentication
> (...)
>   To mitigate the security risks associated with the use of passwords, 
>   a server implementation MUST implement a configuration that at the 
>   time of authentication or password modification, requires: 
>
>      1) A Start TLS encryption layer has been successfully negotiated. 
>
>       OR 
>
>      2) Some other confidentiality mechanism that protects the password 
>         value from snooping has been provided. 
>
>       OR 

This should only apply to cleartext passwords, not e.g. modifications of
attributes that contain encrypted passwords.  I suppose that can be
considered a 'confidentiality mechanism' as in (2) so this case is
covered, but confidentiality mechanisms elsewhere in the draft do not
refer to that, only to things like TLS or SASL layers.

It's not just modifications.  It's any operation which involves
passwords, e.g. compare.

Finally, as I said in the thread about this, we cannot mandate this for
other operations than bind, because a gateway server may not know which
attributes contain passwords (other than userPassword).  You could use
"MUST" protect cleartext bind passwords, and "SHOULD" protect other
cleartext passwords.

-- 
Hallvard


From owner-ietf-ldapbis@OpenLDAP.org  Fri Feb 27 02:31:56 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA18414
	for <ldapbis-archive@lists.ietf.org>; Fri, 27 Feb 2004 02:31:55 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1R7VEYT092587;
	Fri, 27 Feb 2004 07:31:14 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1R7Jnjx091699;
	Fri, 27 Feb 2004 07:19: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); Fri, 27 Feb 2004 07:19:49 +0000
Received: from pat.uio.no (IDENT:7411@pat.uio.no [129.240.130.16])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1R7JlYT091689
	for <ietf-ldapbis@openldap.org>; Fri, 27 Feb 2004 07:19:48 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 1AwcHg-0002ot-Dc
	for ietf-ldapbis@openldap.org; Fri, 27 Feb 2004 08:19:44 +0100
Received: from bombur.uio.no ([129.240.186.42])
	by mail-mx4.uio.no with esmtp (Exim 4.14)
	id 1AwcHd-0001DS-EV; Fri, 27 Feb 2004 08:19:41 +0100
Received: from hbf by bombur.uio.no with local (Exim 2.12 #7)
	id 1AwcHd-0006AA-00; Fri, 27 Feb 2004 08:19:41 +0100
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Message-Id: <HBF.20040227iwun@bombur.uio.no>
To: ietf-ldapbis@OpenLDAP.org
Subject: Attributes with no equality matching rule
Date: Fri, 27 Feb 2004 08:19:41 +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
X-UiO-Spam-info: not spam, SpamAssassin (score=0, required 12)
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.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've just gotten a major surprise from looking at X.500(1993):

Attributes with no equality matching rule are rather special in
X.500, but not very in old LDAPv3 and even less so in LDAPbis' LDAP.
(Partly because of my suggestions, I'm afraid...)

Should the drafts conform to X.500 in this, or should they stay the
way they are?

Or - maybe implementations SHOULD behave as stated today, but MAY behave
like X.500?  Otherwise I think LDAP-X.500 gateways are in trouble.

Anyway, here are the specifics.  X.501(1993) says:

   12.4.4   Attribute syntax

   If an equality matching rule is specified for the attribute type,
   the Directory shall ensure that the correct attributesyntax is
   used for every value of this attribute type.

   12.4.5   Matching rules
   (...)
   If no equality matching rule is indicated, the Directory:
   a) treats values of this attribute as having type ANY, i.e. the
      Directory may not check that those values conform with the
      data type or any other rule indicated for the attribute;
   b) does not permit the attribute to be used for naming;
   c) does not allow individual values of multi-valued attributes to
      be added or removed;
   d) does not perform comparisons of values of the attribute;
   e) will not attempt to evaluate AVAs using values of such an
      attribute type.

12.4.4 and 12.4.5a really surprised me.  Are they really saying that
the server must allow the user to store a DN in the telexNumber
attribute, since telexNumber has no equality matching rule?

I believe LDAP, for attributes without EQUALITY matching rule:

   a) checks attribute syntaxes, unlike X.500.

   b) partly mimics X.500:

      As far as I can tell, there is no statement forbidding RDN
      components without equality matching rules.
.
      OTOH, DNs are _matched_ according to the RDN components' equality
      matching rules ([Syntaxes] 4.2.10. distinguishedNameMatch), so if
      a DN contains an attribute without an equality matching rule,
      presumably one cannot retrieve that entry by its name.  One can
      retrieve it by searching for it, though.

   c) does allow us to add/remove individual values, unlike X.500.

   d) mimics X.500:
      does not perform comparisons of values of the attribute.

I'm not sure what (e) implies, so I'll let others comment on that.

X.500(1993) can be read at <http://archive.dante.net/np/ds/osi.html>.

(Sorry, I won't see answers until after IETF#59; I'm about to go on
vacation.)

-- 
Hallvard


From owner-ietf-ldapbis@OpenLDAP.org  Fri Feb 27 02:59:03 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA19484
	for <ldapbis-archive@lists.ietf.org>; Fri, 27 Feb 2004 02:59:02 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1R7uMYl093564;
	Fri, 27 Feb 2004 07:58:15 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1R7tuSH093555;
	Fri, 27 Feb 2004 07:55: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); Fri, 27 Feb 2004 07:55:56 +0000
Received: from pat.uio.no (IDENT:7411@pat.uio.no [129.240.130.16])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1R7tsYT093544
	for <ietf-ldapbis@openldap.org>; Fri, 27 Feb 2004 07:55:55 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 1Awcqc-0007FF-8W
	for ietf-ldapbis@openldap.org; Fri, 27 Feb 2004 08:55:50 +0100
Received: from bombur.uio.no ([129.240.186.42])
	by mail-mx2.uio.no with esmtp (Exim 4.14)
	id 1Awcqa-0006RO-Jl; Fri, 27 Feb 2004 08:55:48 +0100
Received: from hbf by bombur.uio.no with local (Exim 2.12 #7)
	id 1Awcqa-0006Fb-00; Fri, 27 Feb 2004 08:55:48 +0100
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Message-Id: <HBF.20040227ib43@bombur.uio.no>
To: ietf-ldapbis@OpenLDAP.org
Subject: authmeth: bind and authorization/authentication IDs
Date: Fri, 27 Feb 2004 08:55:48 +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
X-UiO-Spam-info: not spam, SpamAssassin (score=0, required 12)
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.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 description of the Bind operation does not say which ID
(authorization or authentication) is transmitted.  It can be deduced
from the definitions in Appendix C, but I think that's a bit weak.  So I
suggest something like this is added:

In section 4 (Bind Operation):

   The Bind operation sets the association's authentication and
   authorization identities.

   The Bind request typically specifies the desired authentication
   identity.

   If the authorization identity is not specified, the server derives it
   from the authentication identity in an implementation-specific
   manner.

...Then move (and edit a bit) this from Section 9.2 (Explicit
Assertion), since it is applies to more than just EXTERNAL bind:

   If the bind mechanism allows the authorization identity to be
   supplied, and the client does supply it, the server MUST verify that
   the authentication identity 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.


Also, in section 9 (SASL EXTERNAL Mechanism), specify that the
authentication ID which is (derived from?) the security credentials (in
an implementation-specific manner?).

Section 9 says LDAP 'makes use of' the security credentials.  I'm not
sure if that means the authentication ID must be what is contained in
the security credentials, or if the credentials can be transformed in
some way - e.g. via a private lookup table.

-- 
Hallvard


From owner-ietf-ldapbis@OpenLDAP.org  Fri Feb 27 10:25:38 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08086
	for <ldapbis-archive@lists.ietf.org>; Fri, 27 Feb 2004 10:25:36 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1RFOQYT021532;
	Fri, 27 Feb 2004 15:24:26 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1RFBxZU019889;
	Fri, 27 Feb 2004 15:11: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); Fri, 27 Feb 2004 15:11:59 +0000
Received: from boole.openldap.org (kurt@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1RFBtYT019878
	for <ietf-ldapbis@openldap.org>; Fri, 27 Feb 2004 15:11:55 GMT
	(envelope-from kurt@boole.openldap.org)
Received: (from kurt@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) id i1RFBtgg019877
	for ietf-ldapbis@openldap.org; Fri, 27 Feb 2004 07:11:55 -0800 (PST)
	(envelope-from kurt)
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1RFAVYT019643
	for <ietf-ldapbis@OpenLDAP.org>; Fri, 27 Feb 2004 15:10:31 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from gypsy.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.10/8.12.10) with ESMTP id i1RFAUMs083625
	for <ietf-ldapbis@openldap.org>; Fri, 27 Feb 2004 15:10:30 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.1.1.0.20040227070642.04cd3330@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Fri, 27 Feb 2004 07:10:21 -0800
To: ietf-ldapbis@OpenLDAP.org
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: authmeth review notes [long]
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>

Here are my notes from my in-progress review.  I hope
to wrap up my review on the airplane, but thought I'd
share this with you all now (to stir up discussion before
our session).  Later....

Kurt


>INTERNET-DRAFT                                      Editor: R. Harrison 
>draft-ietf-ldapbis-authmeth-10.txt                         Novell, Inc. 
>Obsoletes: 2829, 2830                                  10 February 2003 
>Intended Category: Draft Standard                                       
> 
> 
>                     LDAP: Authentication Methods 
>                                  and  
>                 Connection Level Security Mechanisms 
> 
>Status of this Memo 
> 
>   This document is an Internet-Draft and is in full conformance with 
>   all provisions of Section 10 of RFC2026. 
>    
>   This document is intended to be, after appropriate review and 
>   revision, submitted to the RFC Editor as a Standard Track document. 
>   Distribution of this memo is unlimited.  Technical discussion of 
>   this document will take place on the IETF LDAP Revision Working 
>   Group mailing list <ietf-ldapbis@OpenLDAP.org>.  Please send 
>   editorial comments directly to the author 
>   <roger_harrison@novell.com>. 
>    
>   Internet-Drafts are working documents of the Internet Engineering 
>   Task Force (IETF), its areas, and its working groups.  Note that 
>   other groups may also distribute working documents as Internet-
>   Drafts. Internet-Drafts are draft documents valid for a maximum of 
>   six months and may be updated, replaced, or obsoleted by other 
>   documents at any time.  It is inappropriate to use Internet-Drafts 
>   as reference material or to cite them other than as "work in 
>   progress." 
>    
>   The list of current Internet-Drafts can be accessed at 
>   http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-
>   Draft Shadow Directories can be accessed at 
>   http://www.ietf.org/shadow.html. 
>    
>Copyright Notice 
>    
>   Copyright (C) The Internet Society (2003).  All Rights Reserved. 

Update year.

>    
>Abstract 
>    
>   This document describes authentication methods and connection level 
>   security mechanisms of the Lightweight Directory Access Protocol 
>   (LDAP).  
> 
>   This document also details establishment of TLS (Transport Layer 
>   Security) using the Start TLS operation. 

  s/also//

>   This document also details the simple Bind authentication method 

  s/also//

>   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 describes various authentication and authorization 
>   states through which a connection to an LDAP server may pass and the 
>   actions that trigger these state changes. 

  s/describes/discusses/

>Table of Contents 
>    
>   1. Introduction................................................3 
>   1.1. Relationship to Other Documents...........................5 
>   2. Conventions Used in this Document...........................5 
>   2.1. Glossary of Terms.........................................5 
>   2.2. Security Terms and Concepts...............................5 
>   2.3. Keywords..................................................6 
>   3. Start TLS Operation.........................................6 
>   3.1. Sequencing of the Start TLS Operation ....................6 
>   3.1.1. Start TLS Request.......................................6 
>   3.1.2. Start TLS Response......................................7 
>   3.1.3. TLS Version Negotiation.................................7 
>   3.1.4. Discovery of Resultant Security Level...................7 
>   3.1.5. Server Identity Check...................................7 
>   3.1.6. Refresh of Server Capabilities Information..............8 
>   3.2. Effects of TLS on a Client's Authorization Identity.......8 
>   3.2.1. TLS Connection Establishment Effects....................9 
>   3.2.2. Client Assertion of Authorization Identity..............9 
>   3.2.3. TLS Connection Closure Effects..........................9 
>   4. Bind Operation..............................................9 
>   4.1. Simple Authentication.....................................9 
>   4.2. SASL Authentication.......................................9 
>   5. Anonymous LDAP Association on Unbound Connections......... 10 
>   6. Anonymous Authentication ................................. 10 
>   7. Simple Authentication..................................... 10 
>   8. SASL Authentication Profile............................... 11 
>   8.1. SASL Service Name for LDAP.............................. 11 
>   8.2. SASL Authentication Initiation and Protocol Exchange.... 11 
>   8.3. Octet Where Negotiated Security Mechanisms Take Effect.. 12 
>   8.4. Determination of Supported SASL Mechanisms.............. 12 
>   8.5. Rules for Using SASL Security Layers.................... 13 
>   9. SASL EXTERNAL Mechanism................................... 13 
>   9.1. Implicit Assertion...................................... 13 
>   9.2. Explicit Assertion...................................... 14 
>   9.3. SASL Authorization Identity............................. 14 
>   9.4 Authorization Identity Syntax............................ 14 
>   10. SASL DIGEST-MD5 Mechanism................................ 15 
>   11. General Requirements for Password-based Authentication .. 15 
>   12. Invalidated Associations................................. 16 
>   13. TLS Ciphersuites......................................... 16 
>   13.1. TLS Ciphersuites Recommendations....................... 17 
>   14. Security Considerations ................................. 18 
>   14.1. Start TLS Security Considerations...................... 18 
>   15. IANA Considerations...................................... 19 
>   Acknowledgements............................................. 19 
>   Normative References......................................... 19 
>   Informative References....................................... 21 
>   Author's Address............................................. 21 
>   Appendix A. LDAP Association State Transition Tables......... 21 
>   A.1. LDAP Association States................................. 21 
>   A.2. Actions that Affect LDAP Association State.............. 22 
>   A.3. Decisions Used in Making LDAP Association State Changes. 22 
>   A.4. LDAP Association State Transition Table................. 22 
>   Appendix B. Example Deployment Scenarios..................... 23 
>   Appendix C. Authentication and Authorization Concepts........ 24 
>   C.1. Access Control Policy................................... 24 
>   C.2. Access Control Factors ................................. 24 
>   C.3. Authentication, Credentials, Identity .................. 25 
>   C.4. Authorization Identity ................................. 25 
>   Appendix D. RFC 2829 Change History ......................... 25 
>   Appendix E. RFC 2830 Change History ......................... 29 
>   Appendix F. RFC 2251 Change History ......................... 30 
>   Appendix G. Change History to Combined Document.............. 30 
>   Appendix H. Issues to be Resolved............................ 41 
>    
>    
>1. Introduction 
>    
>   The Lightweight Directory Access Protocol (LDAP) [Protocol] is a 
>   powerful access protocol for directories.

  s/[Protocol]/[Roadmap]/

Suggest
  s/access protocol for directories/protocol for accessing 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 LDAP conformance. 
> 
>   Basic threats to an LDAP directory service include: 
> 
>   (1) Unauthorized access to directory data via data-retrieval 
>       operations, 
> 
>   (2) Unauthorized access to directory data by monitoring others' 
>       access, 
>    
>   (3) Unauthorized access to reusable client authentication 
>       information by monitoring others' access, 
>    
>   (4) Unauthorized modification of directory data, 
> 
>   (5) Unauthorized modification of configuration information, 
>
>   (6) Denial of Service: Use of resources (commonly in excess) in a 
>       manner intended to deny service to others. and 

s/. and/,/

> 
>   (7) Spoofing: Tricking a user or 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. Tricking a user or client into sending privileged 
>       information to a hostile entity that appears to be the directory 
>       server but is not. Tricking a directory server into believing 
>       that information came from a particular client when in fact it 
>       came from a hostile entity. 

s/./, and/

>   (8) Hijacking of prototocol sessions. 
 
  s/prototocol/protocol/

>   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, e.g. IP 
>   spoofing. 

Add (8) to the latter list.

>   LDAP offers the following security mechanisms: 
> 
>   (1) Authentication by means of the Bind operation.  The Bind 
>       operation provides a simple method which supports anonymous, 
>       unauthenticated, and authenticated with password mechanisms, and 
>       the Secure Authentication and Security Layer (SASL) method which 
>       supports a wide variety of authentication mechanisms and which 
>       may be extended to support additional methods of authentication. 

s/./,/
s/and which...//  (no need to discuss extensibility here)

>   (2) Client authorization by means of access control based on the 
>       requestor's authenticated identity, 

Given that LDAP doesn't offer an authorization (access control)
model, this seems dubious (even with the note below).  However, I
don't have a suggestion (at the moment) on how to better address
this.

>   (3) Data integrity protection by means of TLS or SASL mechanisms 
>       with security layers that provide data integrity services, 

s/protection/service/ (use RFC2828 term)
 
>   (4) Data confidentiality protection against snooping by means of the 
>       TLS protocol or SASL mechanisms that provide data 
>       confidentiality services, 

s/protection/service/ (use RFC2828 term)
s/against snooping// (implicit in term, hence redundant)

>   (5) Server resource usage limitation by means of administrative 
>       service limits configured on the server, and 

s/service//

Note: the term "administrative limits" comes from X.511 and is
specifically associated with the adminLimitExceeded result code.
Insertion of the word "service" confuses this association.

>   (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 LDAP. 
> 
>   It seems clear that allowing any implementation, faced with the 

s/any/an/ or s/any implemention/implementations/

>   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 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.

s/see/use/
s/take the form of an LDAP distinguished name/
s/are represented as distinguished names [X.501][Models] in string
form [LDAPDN]/.

>               This means that this data must be updated outside the 
>   protocol or only updated in sessions well protected against 
>   snooping.

s/snooping/eavesdropping/ (use RFC2828 term)

>               It is also desirable to allow authentication methods to 
>   carry identities not represented as LDAP DNs that are familiar to 
>   the user or that are used in other systems. 

suggest:
	It is also desirable to allow authentication methods to 
	carry identities (other than DNs) that are familiar to the
	user or that are used in other systems. 

>   The set of security mechanisms provided in LDAP 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 LDAP implementations and deployments. 
>   Appendix B contains example deployment scenarios that list the 
>   mechanisms that might be used to achieve a reasonable level of 
>   security in various circumstances. 
>    
>1.1. Relationship to Other Documents 
> 
>   This document is an integral part of the LDAP Technical 
>   Specification [Roadmap].  
>    
>   This document obsoletes RFC 2829. 
>    
>   Sections 2 and 4 of RFC 2830 are obsoleted by [Protocol].  The 
>   remainder of RFC 2830 is obsoleted by this document.  
>    
>2. Conventions Used in this Document 

Suggest you make this Section 1.2.

>2.1. Glossary of Terms 

and this 1.2.1.
    
>   The following terms are used in this document. To aid the reader, 
>   these terms are defined here. 
>    
>     - "user" represents any 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 [TLS] 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 

and this 1.2.2.

>    
> 
>Harrison                  Expires July 2004                  [Page 5] 
>
>Internet-Draft       LDAP Authentication Methods      5 December 2003 
> 
>   In general, security terms in this document are used consistently 
>   with the definitions provided in [Glossary]. In addition, several 
>   terms and concepts relating to security, authentication, and 
>   authorization are presented in Appendix C 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 C before reading the remainder of this document. 

>2.3. Keywords 

and this 1.2.3.

>    
>   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 [Keyword]. 

I would like to add a new section (or possible placed subsequent
to the technical specification of these features) which gathers the
high level implementation requirements.  Gathering the statements
are requirement level for each feature (as oppose to detailing how
that feature, if implemented, is to be implemented).

2.  Implementation Requirements

 LDAP implementations which support any authentication mechanism
 (other than anonymous mechanism of the simple Bind method) MUST
 support the DIGEST-MD5 [RFC2831bis] mechanism of the SASL Bind
 method (as detailed in Section X).  That is, excepting those
 implementations which only support anonymous connections, all
 implementations MUST support DIGEST-MD5.  DIGEST-MD5 is reasonably
 strong authentication mechanism which provides (mandatory-to-implement)
 data security (data integrity and data confidentity) services.

 LDAP implementations SHOULD support the simple DN/password mechanism
 of the simple Bind method (as detailed in Section X).  Implementations
 which support this mechanism MUST be capable of protecting it by
 establishment (as discussed in Section 3) of TLS. 

 LDAP server implementations MUST support the anonymous mechanism of
 the simple Bind method.

 Implementations MAY support additional authentication mechanisms of
 the simple and SASL bind methods, and/or mechanisms of other bind
 methods.  Some of these mechanisms are discussed below.


>3. Start TLS Operation 
>    
>   The Start Transport Layer Security (Start TLS) operation defined in 
>   section 4.13 of [Protocol] provides the ability to establish [TLS] 
>   on an LDAP connection. 
>    
>3.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 connection are described in detail in 
>   section 3.2. 
> 
>3.1.1. Start TLS Request  
> 
>   A client may send the Start TLS extended request at any time after 
>   establishing an 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 outstanding LDAP operations on the connection. 

s/LDAP operations/responses for previously issued operations/

This makes, I think, it clear that clients are to wait.  Hence,
the following paragraph can be replaced with:

	As described in [Protocol, Section 4.13.2.2], a (detected)
	violation of any of these requirements results in return of
	the operationsError resultCode.

>   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 receive a resultCode 
>   of success for a Start TLS operation that is sent on a connection 
>   with outstanding LDAP operations if the server has sufficient time 
>   to process them prior to its receiving the Start TLS request. 
>   Implementors of clients should ensure that they do not inadvertently 
>   depend upon this race condition. 
    
(Even with all of the qualifications, the above wording sounds
like it condoning not waiting for outstanding responses.)

>   There is no requirement that the client have or have not already 
>   performed a Bind operation (section 4) before sending a Start TLS 
>   operation request. 

s/no/no general/ (there may be requirements in specific cases)

>   If the client did not establish a TLS connection before sending some 
>   other request, and the server requires the client to establish a TLS 
>   connection before performing that request, the server MUST reject 
>   that request by sending a resultCode of confidentialityRequired or 
>   strongAuthRequired. 

The following paragraph seems misplaced as it relates to events
which take place after success completion of the operation.  Suggest
you insert a subsection "Client Certificate" after 3.1.3.  (This
section could meantion that the client certificate may be used
in support of the EXTERNAL mechanism.)

>   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. 

There are too many conditionals in the above sentence.

	could it end with "not present an suitable certificate"?


>3.1.2. Start TLS Response 
> 
>   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 resultCode values (documented in [Protocol] section 4.13.2.2) 
>   if it is unwilling or unable to do so. 

s/other resultCode values/a resultCode other than success/

>   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. 
> 
>3.1.3. TLS Version Negotiation 
> 
>   Negotiating the version of TLS to be used is a part of the TLS 
>   Handshake Protocol [TLS]. Please refer to that document for details. 
> 
>3.1.4. Discovery of Resultant Security Level 
> 
>   After a TLS connection is established on an LDAP connection, both 
>   parties must individually decide whether or not to continue based on 
>   the security level achieved. Ascertaining the TLS connection's 
>   security level is implementation dependent and accomplished by 
>   communicating with one's respective local TLS implementation. 
> 
>   If the client or server decides that the level of authentication or 
>   security 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 3.2.3 below). 
>   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. 
> 
>3.1.5. 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 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). 
>    
>     - 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. 
>   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 in making 
>   this determination. 
> 
>3.1.6. Refresh of Server Capabilities Information 
> 
>   Upon TLS session establishment, the client SHOULD discard or refresh 
>   all information about the server it obtained prior to the initiation 
>   of the TLS negotiation and not obtained through secure mechanisms. 
>   This protects against active-intermediary attacks that may have 
>   altered any server capabilities information retrieved prior to TLS 
>   establishment.  
>    
>   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). 
>    
>3.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 connection. 
>   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 C. 
> 
>3.2.1. TLS Connection Establishment Effects 
>    
>   The decision to keep or invalidate the established authentication 
>   and authorization identities in place after TLS closure is a matter 
>   of local server policy.  
> 
>3.2.2. Client Assertion of Authorization Identity 
>    
>   After successfully establishing a TLS session, a client may request 
>   that its credentials exchanged during the TLS establishment be 
>   utilized to authenticate the LDAP association and thus determine the 
>   client's authorization status. The client accomplishes this via an 
>   LDAP Bind request specifying a SASL mechanism of EXTERNAL [SASL] 
>   (section 9). LDAP server implementations SHOULD support this 
>   authentication method. 
>    
>3.2.3. TLS Connection Closure Effects 
>    
>   The decision to keep or invalidate the established authentication 
>   and authorization identities in place after TLS closure is a matter 
>   of local server policy. 

I think we should insert here a section about LDAP associations,
including what the default association is, how new associations
are established, and how associations are invalidated.  If done
well, sections 4, 5, 12 could be merged into this new section.

>4. 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.  
>    
>   Upon receipt of a Bind request, the LDAP association is moved to an 
>   anonymous state and only upon successful completion of the 
>   authentication exchange (and the Bind operation) is the association 
>   moved to an authenticated state. 
>    
>4.1. Simple Authentication  
>    
>   The simple authentication choice of the Bind Operation provides 
>   minimal facilities for establishing an anonymous association 
>   (section 6) or for establishing an LDAP association based upon 
>   credentials consisting of a name (in the form of an LDAP 
>   distinguished name [LDAPDN]) and a password (section 7). 
>    
>4.2. SASL Authentication  
>    
>   The sasl authentication choice of the Bind Operation provides 
>   facilities for authenticating via SASL mechanisms (sections 8-10). 
>
>5. Anonymous LDAP Association on Unbound Connections 
>    
>   Prior to the successful completion of a Bind operation and during 
>   any subsequent authentication exchange, the session has an anonymous 
>   LDAP association. Among other things this implies that 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. This authentication state on an LDAP association is 
>   sometimes referred to as an implied anonymous bind. 
> 
>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. 

I hope this is not typical.  I think this paragraph should simply
be deleted.

>   An LDAP client may explicitly establish an anonymous association by 
>   sending a Bind Request with the simple authentication choice 
>   containing a value--construed as the password--of zero length. A 
>   bind request where both the name and password are of zero length is 
>   said to be an anonymous bind. A bind request where the name, a DN, 
>   is of non-zero length, and the password is of zero length is said to 
>   be an unauthenticated bind. Both variations produce an anonymous 
>   association. 
>    
>   Unauthenticated binds can have significant security issues (see 
>   section 14). Servers SHOULD by default reject unauthenticated bind 
>   requests with a resultCode of invalidCredentials, and clients may 
>   need to actively detect situations where they would make an 
>   unauthenticated bind request. 
>    
>   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. 
>    
>   LDAP implementations MUST support anonymous authentication. 
> 
>7. Simple Authentication 
> 
>   An LDAP client may establish an LDAP association by sending a Bind 
>   Request with a name value consisting of an LDAP distinguished name 
>   [LDAPDN] and specifying the simple authentication choice with a 
>   password value.  

s/an LDAP distinguished name/a distinguished name in LDAP string
form [LDAPDN]/

s/password value/password value, an OCTET STRING.
    
>   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.

s/DSAs/Servers/
s/more passwords/more passwords, each an OCTET STRING,/
s/compare/compare octet wise/

>            If the presented password matches any member of that set,
>   then the server will respond with a success resultCode, otherwise
>   the server will respond with an invalidCredentials resultCode.

This wording doesn't account for other possible failures.  Instead,
I suggest:
	         The presented password is considered valid if it
    matches any member of this set.

	If the DN is not valid, or the password is not valid for
	the DN, or the server otherwise considers the credentials
	to be invalid, the server is to return the invalidCredentials
	result code.  The server is only to return success result
	code when the credentials are valid and the server is willing
	to provide service to the entity these credentials identify.

>   The 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. 
> 
>8. 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 LDAP. 
>    
>8.1. SASL Service Name for LDAP 
> 
>   The SASL service name for LDAP is "ldap", which has been registered 
>   with the IANA as a GSSAPI service name. 
>    
>8.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 the SaslCredentials 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 5.1). 
>    
>   In general, a SASL authentication protocol exchange consists of a 
>   series of server challenges and client responses, the contents of 
>   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 
>   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 
>   authMethodNotSupported 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. 
>    
>   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. 
> 
>8.3. Octet Where Negotiated Security Mechanisms Take Effect 
> 
>   SASL security layers take effect following the transmission by the 
>   server and reception by the client of the final successful 
>   BindResponse in the exchange. 
> 
>   Once a SASL security layer providing integrity or confidentiality 
>   services takes effect, the layer remains in effect until a new layer 
>   is installed (i.e. at the first octet following the final 
>   BindResponse of the bind operation that caused the new layer to take 
>   effect). 
>         
>8.4. Determination of Supported SASL Mechanisms 
>    
>   Clients may determine the SASL mechanisms a server supports by  
>   reading the 'supportedSASLMechanisms ' attribute from the root DSE 
>   (DSA-Specific Entry) ([Models] section 5.1).  The values of this 
>   attribute, if any, list the mechanisms the server supports in the 
>   current LDAP session state. 
> 
>   LDAP servers SHOULD allow an anonymously-bound client to retrieve 
>   the supportedSASLMechanisms attribute of the root DSE. 
> 
>8.5. Rules for Using SASL Security Layers 
>    
>   If a SASL security layer is negotiated, the client SHOULD discard 
>   information about the server it obtained prior to the initiation of 
>   the SASL negotiation and not obtained through secure mechanisms.  
>    
>   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. In all other 
>   respects, SASL security services and other security layers act 
>   independently, e.g. if both TLS and SASL security service are in 
>   effect removing the SASL security service does not affect the 
>   continuing service of TLS and vice versa. 
>    
>   Because SASL mechanisms provide critical security functions, clients 
>   and servers should allow the user to specify what mechanisms are 
>   acceptable and allow only those mechanisms to be used. 
> 
>9. SASL EXTERNAL Mechanism 

I think this section needs a major rewrite.  I'll offer
replacement text in a bit.

>    
>   A client can use the EXTERNAL SASL [SASL] mechanism to request the 
>   LDAP server to make use of security credentials exchanged by a lower 
>   security layer (such as by TLS authentication or IP-level security 
>   [SecArch]).  

"lower level security layer" is too restrictive.  RFC 2222 actually
says
   The server uses information, external to SASL, to determine
   whether the client is authorized to authenticate as the
   authorization identity. 

This section needs to reworded using terms consisent with RFC 2222
section 7.4.  Also, introduction of "implicit assertion" and
"explicit assertion" terminology seems unnecessary (and certainly
isn't specific to this mechanism).  General handling of authorization
identities needs to be discussed in section 8.  This section needs
only to provide an LDAP profile of the EXTERNAL mechanism, and
possibly an example or two.

>   If the client's authentication credentials have not been established 
>   at a lower security layer, the SASL EXTERNAL bind MUST fail with a 
>   resultCode of inappropriateAuthentication.

It may be difficult for some LDAP implementations, such as those
which use protocol-neutral SASL implementations, to map a
mechanism-specific failure to a protocol-specific code.  For
ease of implementation, we should avoid mandating mechanism-specific
failure handling.  This MUST should minimally be replaced with a
SHOULD, if not removed outright... (or replaced with mechanism
neutral text placed elsewhere).

>                                                 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). In such a situation, the 
>   state of any established security layer is unaffected. 

This seems to just be restating was is true for all Bind
failures.  I see little point in repeating it.

> 
>   A client may either implicitly request that its LDAP authorization 
>   identity be derived from a lower layer 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. 
>    
>9.1. Implicit Assertion 
>    
>   An implicit authorization identity assertion is performed by 
>   invoking a Bind request of the SASL form using the EXTERNAL 
>   mechanism name that does not include the optional credentials octet 
>   string (found within the SaslCredentials sequence in the Bind 
>   Request). The server will derive the client's authorization identity 
>   from the authentication identity supplied by the security layer 
>   (e.g., a public key certificate used during TLS establishment) 
>   according to local policy. The underlying mechanics of how this is 
>   accomplished are implementation specific. 
> 
>9.2. Explicit Assertion 
>    
>   An explicit authorization identity assertion is performed by 
>   invoking a Bind request of the SASL form using the EXTERNAL 
>   mechanism name that includes 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. 
> 
>9.3. SASL Authorization Identity 
> 
>   When the EXTERNAL SASL mechanism is being negotiated, if the 
>   SaslCredentials credentials field is present, it contains an 
>   authorization identity. Other mechanisms define the location of the 
>   authorization identity in the credentials field. In either case, the 
>   authorization identity is represented in the authzId form described 
>   below. 

I think we need cover mechanism indepenent handling of authzids
in section 8 and only detail in section 9 how authzids are
transferred (or not) when using EXTERNAL.

>9.4 Authorization Identity Syntax 

This section needs to be in section 8 as the LDAP's SASL profile
must include the specification the authorization identity form.

>    
>   The authorization identity is a string of [UTF-8] encoded [Unicode] 
>   characters corresponding to the following [ABNF] grammar: 
> 
>   authzId = dnAuthzId / uAuthzId 
> 
>   DNCOLON  = %x64 %x6e %x3a ; "dn:" 
>   UCOLON = %x75 %x3a ; "u:" 

These are not equivalent to the RFC 2829 ABNF!  Instead:

   DNCOLON  = ( %x44 / %x64 ) ( %4E / %x6E ) %x3A ; "dn:" 
   UCOLON = ( %x55 / %x75 ) %x3A ; "u:" 


>   ; distinguished-name-based authz id. 
>   dnAuthzId = DNCOLON distinguishedName 
> 
>   ; unspecified authorization id, UTF-8 encoded. 
>   uAuthzId = UCOLON userid 
>   userid = *UTF8    ; syntax unspecified 
>    
>   where the <distinguishedName> production is defined in section 3 of 
>   [LDAPDN] and <UTF8> production is defined in section 1.3 of 
>   [Models]. 
> 
>   In order to support additional specific authorization identity 
>   forms, future updates to this specification may add new choices 
>   supporting other forms may be added to the authzId production.  
>    
>   The dnAuthzId choice allows clients to assert authorization 
>   identities in the form of a distinguished name to be matched in 
>   accordance with the distinguishedNameMatch 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. 

I also suggest a slight rewriting:
	As the decision to allow or disallow the client to assume
	the requested authorization identity is a matter of local
	policy (see section 4.2 of [SASL]), there is no requirement
	that the asserted DN be that of an entry in the directory.

>   The uAuthzId choice allows for compatibility with clients that wish 
>   to assert an authorization identity to a local directory but do not 
>   have that identity in distinguished name form. The value contained 
>   within a uAuthzId MUST be prepared using [SASLPrep] before being 
>   compared octet-wise. The format of userid is defined as only a 
>   sequence of [UTF-8] encoded [Unicode] characters, and further 
>   interpretation is subject to prior agreement between the client and 
>   server. 
> 
>   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.

s/the local-part of//

This offers an example which, unlike the others, obviously
includes punctuation characters.

>   A uAuthzId SHOULD NOT be assumed to be globally unique. 
> 
>10. SASL DIGEST-MD5 Mechanism 
>    
>   LDAP servers that implement any authentication method or mechanism 
>   other than simple anonymous bind MUST implement the SASL 
>   DIGEST-MD5 mechanism [DIGEST-MD5].  This provides client 
>   authentication with protection against passive eavesdropping attacks 
>   but does not provide protection against active intermediary attacks.  
>   DIGEST-MD5 also provides data integrity and data confidentiality 
>   capabilities. 
>    
>   Support for subsequent authentication ([DIGEST-MD5] section 2.2) is 
>   OPTIONAL in clients and servers. 
>    
>   Implementers 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 ([DIGEST-MD5] section 2.1) which are 
>   syntactically simple strings and semantically 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, 
>   dc=example,dc=com>, are syntactically allowed, however DIGEST-MD5 
>   treats them as simple strings for comparison purposes. To illustrate 
>   further, the two DNs <cn=Bob,dc=example,dc=com> (upper case "B") and 
>   <cn=bob,dc=example,dc=com> (lower case "b") are equivalent when 
>   being compared semantically as LDAP DNs because the cn attribute is 
>   defined to be case insensitive, however the two values are not 
>   equivalent if they represent username values in DIGEST-MD5 because 
>   [SASLPrep] semantics are used by DIGEST-MD5.  
> 
>11. General Requirements for Password-based Authentication 
>    
>   The transmission of passwords in the clear--typically for 
>   authentication or modification--poses a significant security risk. 
>   This risk can be avoided by using SASL authentication [SASL] 
>   mechanisms that do not transmit passwords in the clear or by 
>   negotiating transport or session layer confidentiality services 
>   before transmitting password values. 
>    
>   To mitigate the security risks associated with the use of passwords, 
>   a server implementation MUST implement a configuration that at the 
>   time of authentication or password modification, requires: 
>    
>     1) A Start TLS encryption layer has been successfully negotiated. 
>      
>      OR 
>      
>     2) Some other confidentiality mechanism that protects the password 
>        value from snooping has been provided. 
>      
>      OR 
>      
>     3) The server returns a resultCode of confidentialityRequired for 
>        the operation (i.e. simple bind with password value, SASL bind 
>        transmitting a password value in the clear, add or modify 
>        including a userPassword value, etc.), even if the password 
>        value is correct. 
> 
>12. Invalidated Associations 
> 
>   The server may, at any time, invalidate the association, e.g. if the 
>   established security association between the client and server has 
>   unexpectedly failed or been compromised.  The association remains 
>   invalidated until the next successful bind request.  While the 
>   association is invalidated, the server may reject any operation 
>   request other than Bind, Unbind, and Start TLS by responding with a 
>   resultCode of strongAuthRequired to indicate that the client needs 
>   to bind to reestablish its authentication state before performing 
>   the requested operation. 
> 
>13. TLS Ciphersuites 

This section should be incorporated in section 3 (as the last
subsection).
 
>        A client or server that supports TLS MUST support 
>        TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA. Servers SHOULD NOT support 
>        weaker ciphersuites unless other data integrity and 
>        confidentiality protection (such as a SASL security layer) is 
>        in place 

This is unnecessarily intended.
    
>   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. 
> 
>13.1. TLS Ciphersuites Recommendations 

This section needs to be updated.

>   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 [TLS] 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 [TLS] 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 
> 
> 
>14. Security Considerations 

I'd like to see this section split into a couple of additional
subsections.
	14.1 General considerations
	14.2 Start TLS considerations
	14.3 Simple Bind considerations
	14.4 SASL Bind considerations

And then flush these sections out.
    
>   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 can minimize denial of service attacks by timing out idle 
>   connections, and returning the unwillingToPerform resultCode rather 
>   than performing computationally expensive operations requested by 
>   unauthorized clients. 
>    
>   The use of cleartext passwords and other unprotected authentication 
>   credentials is strongly discouraged over open networks when the 
>   underlying transport service cannot guarantee confidentiality. 
>    
>   Operational experience shows that clients can (and frequently do) 
>   misuse unauthenticated bind (see section 5.1).  For example, a 
>   client program might make a decision to grant access to non-
>   directory information on the basis of completing a successful bind 
>   operation. Some LDAP server implementations will return a success 
>   response to an unauthenticated bind thus leaving the client with the 
>   impression that the server has successfully authenticated the 
>   identity represented by the user name, when in effect, an anonymous 
>   LDAP association has been created. Clients that use the results from 
>   a simple bind operation to make authorization decisions should 
>   actively detect unauthenticated bind requests (via the empty 
>   password value) and react appropriately. 
>    
>   Access control SHOULD always be applied when reading sensitive 
>   information or updating directory information. 
> 
>   A connection on which the client has not established connection  
>   integrity and privacy services (e.g via Start TLS, IPSec or a 
>   suitable SASL mechanism) is subject to man-in-the-middle attacks to 
>   view and modify information in transit. 
>    
>14.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. 
>    
>   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 
>   connection--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 supported 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 data 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 [TLS]. 
>    
>15. IANA Considerations 
>    
>   The following IANA considerations apply to this document: 
>    
>   Please update the GSSAPI service name registry to point to [Roadmap] 
>   and this document. 
>    
>   [To be completed] 
>    
>Acknowledgements 
>    
>   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. 
> 
>   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 
> 
>   [ABNF]       Crocker, D., Ed. and P. Overell, "Augmented BNF for 
>                Syntax Specifications: ABNF", RFC 2234, November 1997. 
>    
>   [DIGEST-MD5] Leach, P. C. Newman, and A. Melnikov, "Using Digest 
>                Authentication as a SASL Mechanism", draft-ietf-sasl-
>                rfc2831bis-xx.txt, a work in progress.  
>    
>   [Keyword]    Bradner, S., "Key Words for use in RFCs to Indicate 
>                Requirement Levels", BCP 14, RFC 2119, March 1997. 
>    
>   [LDAPDN]     Zeilenga, Kurt D. (editor), "LDAP: String 
>                Representation of Distinguished Names", draft-ietf-
>                ldapbis-dn-xx.txt, a work in progress. 
>    
>   [Models]     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. 
>    
>   [SASLPrep]   Zeilenga, K., "Stringprep profile for user names and 
>                passwords", draft-ietf-sasl-saslprep-xx.txt, (a work in 
>                progress). 
>    
>   [StringPrep] Hoffman P. and M. Blanchet, "Preparation of 
>                Internationalized Strings ('stringprep')", draft-
>                hoffman-rfc3454bis-xx.txt, a work in progress.  
>    
>   [Syntaxes]   Legg, S. (editor), "LDAP: Syntaxes and Matching Rules", 
>                draft-ietf-ldapbis-syntaxes-xx.txt, a work in progress. 
>    
>   [TLS]        Dierks, T. and C. Allen. "The TLS Protocol Version 
>                1.1", draft-ietf-tls-rfc2246-bis-xx.txt, a work in 
>                progress. 
>    
>   [UTF-8]      Yergeau, F., "UTF-8, a transformation format of ISO 
>                10646", RFC 3629, STD 63, November 2003. 
>    
>   [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/). 
> 
>Informative References 
> 
>   [ANONYMOUS]  Zeilenga, K.,"Anonymous SASL Mechanism", draft-
>                zeilenga-sasl-anon-xx.txt, a work in progress. 
>    
>   [Glossary]   Shirey, R., "Internet Security Glossary", RFC 2828, May 
>                2000. 
>    
>   [PLAIN]      Zeilenga, K.,"Plain SASL Mechanism", draft-zeilenga-
>                sasl-plain-xx.txt, a work in progress. 
>    
>   [SecArch]    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 
>   USA 
>   +1 801 861 2642 
>   roger_harrison@novell.com 
> 
>Appendix A. LDAP Association State Transition Tables 
>    
>   This section provides a state transition table to represent a state 
>   diagram for the various authentication and TLS states through which 
>   an LDAP association may pass during the course of its existence and 
>   the actions that cause these changes in state.   
>    
>   This section is based entirely on information found in this document 
>   and other documents that are part of the LDAP Technical 
>   Specification [Roadmap]. As such, it is strictly informational in 
>   nature. 
>    
>A.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 A.4. 
>    
>   ID State Description 
>   -- -------------------------------------------------------------- 
>   S1 Anonymous 
>          no Authentication ID is associated with the LDAP connection 
>          no Authorization ID is in force 
>   S2 Authenticated 
>          Authentication ID = I 
>          Authorization ID = X 
>   S3 Authenticated SASL EXTERNAL, implicit authorization ID 
>          Authentication ID = J 
>          Authorization ID = Y 
>   S4 Authenticated SASL EXTERNAL, explicit authorization ID  
>          Authentication ID = J 
>          Authorization ID = Z 
> 
>A.2. Actions that Affect LDAP Association State 
>    
>   The following table lists the actions that can affect the 
>   authentication and authorization state of an LDAP association. The 
>   ID for each action is used in the state transition table in section 
>   A.4. 
>    
>   ID  Action 
>   --  -------------------------------------------------------------- 
>   A1  Client bind request fails 
>   A2  Client successfully performs anonymous simple bind 
>   A3  Client successfully performs unauthenticated simple bind 
>   A4  Client successfully performs simple bind with name and 
>        password OR SASL bind with any mechanism except EXTERNAL using 
>        an authentication ID = I that maps to authorization ID X 
>   A5  Client Binds SASL EXTERNAL with implicit assertion of 
>        authorization ID (section 3.3.6.1)]. The current 
>        authentication ID maps to authorization ID = Y. 
>   A6  Client Binds SASL EXTERNAL with explicit assertion of 
>        authorization ID = Z (section 3.3.6.2)] 
>   A7  Client abandons a bind operation, and server processes the 
>        abandon 
>   A8  Client abandons a bind operation, and server does not process 
>        the abandon 
>   A9  Client Start TLS request fails 
>   A10 Client Start TLS request succeeds 
>   A11 Client or Server: graceful TLS closure ([Protocol] section 
>        4.13.3.1.) 
>                                                  
>A.3. Decisions Used in Making LDAP Association State Changes 
>    
>   Certain changes in the authentication and authorization 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 transition in the state 
>   transition table in section A.4.  
>    
>   ID Decision Question 
>   -- -------------------------------------------------------------- 
>   D1 Are lower-layer credentials available? 
>   D2 Can lower-layer credentials for Auth ID "K" be mapped to 
>       asserted AuthZID "L"? 
>    
>A.4. LDAP Association State Transition Table 
>    
>   The LDAP Association table below lists the valid authentication and 
>   authorization 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. 
>    
>   S1, the initial state for the state machine described in this table, 
>   is the authentication state when an LDAP connection is initially 
>   established. 
>    
>   Current            Next    
>    State  Action    State  Comment 
>   ------- -------   -----  --------------------------------------- 
>     Any   A1          S1    [Protocol] section 4.2.1 
>     Any   A2          S1    Section 6 
>     Any   A3          S1    Section 6 
>     Any   A4          S2    Sections 6.1, 6.2 
>     Any   A5,         S1    Failed bind, section 3.3.6 
>            D1=no 
>     Any   A5,         S3     
>            D1=yes 
>     Any   A6,         S1    failed bind, section 3.3.6 
>            D1=no 
>     Any   A6,         S1    failed bind, section 3.3.6.2 
>            D1=yes,  
>            D2=no 
>     Any   A6,         S4     
>            D1=yes, 
>            D2=yes 
>     Any   A7          S1    [Protocol] section 4.2.1. Clients 
>                               cannot detect this state. 
>     Any   A8          no    [Protocol] section 4.2.1. Clients 
>                      change  cannot detect this state.  
>     Any   A9          no    [Protocol] section 4.13.2.2 
>                      change 
>     Any   A10         no    Section 4.2.1 
>                      change 
>     Any   A11         S1    Section 4.2.3 
> 
>Appendix B. 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 C. Authentication and Authorization 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. 
> 
>C.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. Security objects and 
>   mechanisms, such as those described here, enable the expression of 
>   access control policies and their enforcement.        
> 
>C.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. 
> 
>C.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. 
> 
>C.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. 
> 
>Appendix D. RFC 2829 Change History 

Insert here a summary of substantive changes (in total) since RFC
2829.

Then either add:
	[[Note to RFC Editor: the remaining portion of this appendix
	should be deleted prior to publication.]]
or remove the following text and subsections.

>   This appendix lists the changes made to the text of RFC 2829 in 
>   preparing this document. 
>    
[trimmed]
>    
>Appendix E. RFC 2830 Change History 
    
Insert here a summary of substantive changes (in total) since RFC
2830.

Then either add:
	[[Note to RFC Editor: the remaining portion of this appendix
	should be deleted prior to publication.]]
or remove the following text and subsections.

>   This appendix lists the changes made to the text of RFC 2830 in 
>   preparing this document. 
    
[trimmed]

>Appendix F. RFC 2251 Change History 

Insert here a summary of substantive changes (in total) since RFC
2251.

Then either add:
	[[Note to RFC Editor: the remaining portion of this appendix
	should be deleted prior to publication.]]
or remove the following text and subsections.


>Appendix G. Change History to Combined Document 

Either add:
	[[Note to RFC Editor: this appendix should be deleted prior
	to publication.]]
or remove it.

[trimmed]

> 
>Appendix H. Issues to be Resolved 
>    
Either add:
	[[Note to RFC Editor: this appendix should be deleted prior
	to publication.]]
or remove it.

>   This appendix lists open questions and issues that need to be 
>   resolved before work on this document is deemed complete. 
 
[trimmed]


From owner-ietf-ldapbis@OpenLDAP.org  Sat Feb 28 03:10:41 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA06957
	for <ldapbis-archive@lists.ietf.org>; Sat, 28 Feb 2004 03:10:41 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1S88VYX073538;
	Sat, 28 Feb 2004 08:09:33 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1S83Eps073465;
	Sat, 28 Feb 2004 08:03: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); Sat, 28 Feb 2004 08:03:14 +0000
Received: from boole.openldap.org (kurt@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1S830YT073449
	for <ietf-ldapbis@openldap.org>; Sat, 28 Feb 2004 08:03:00 GMT
	(envelope-from kurt@boole.openldap.org)
Received: (from kurt@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) id i1S830Ts073448
	for ietf-ldapbis@openldap.org; Sat, 28 Feb 2004 00:03:00 -0800 (PST)
	(envelope-from kurt)
Received: from pat.uio.no (IDENT:7411@pat.uio.no [129.240.130.16])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1R8jsYT096120;
	Fri, 27 Feb 2004 08:45:55 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 1Awdd0-0007PO-RK; Fri, 27 Feb 2004 09:45:50 +0100
Received: from bombur.uio.no ([129.240.186.42])
	by mail-mx6.uio.no with esmtp (Exim 4.14)
	id 1Awdcz-0003Di-PZ; Fri, 27 Feb 2004 09:45:49 +0100
Received: from hbf by bombur.uio.no with local (Exim 2.12 #7)
	id 1Awdcz-0006NI-00; Fri, 27 Feb 2004 09:45:49 +0100
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Message-Id: <HBF.20040227hh0d@bombur.uio.no>
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Cc: ietf-ldapbis@OpenLDAP.org
Subject: Re: Protocol: control specifications.
In-Reply-To: <6.0.0.22.0.20040113074035.042a6130@127.0.0.1>
References: <6.0.0.22.0.20040109200051.042f0f18@127.0.0.1>
	<OF10861124.92F9A595-ON86256E19.004E6B22-86256E1A.00547166@us.ibm.com>
	<OF10861124.92F9A595-ON86256E19.004E6B22-86256E1A.00547166@
 us.ibm.com>
	<6.0.0.22.0.20040113074035.042a6130@127.0.0.1>
X-Mailer: VM 6.37 under Emacs 19.34.1
Date: Fri, 27 Feb 2004 09:45:49 +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
X-UiO-Spam-info: not spam, SpamAssassin (score=0, required 12)
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.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 should have replied to this before, but I got so frustrated that just
had to quit the discussion for a while.  I'll rush off a reply now
before going on holiday, just so it comes before the next IETF.  Sorry
about the bad timing, and about setting this up so I can't reply in
time.

Kurt, I think we have said to each other what there is to say about my
proposal: that servers SHOULD reject incorrect criticality on known
controls.  However, you have not replied several of the my points about
your proposal.  An argument against my suggested change is _not_ an
argument for the opposite change.

- You say the intent of the original text was to encourage extension
  authors to discuss the circumstances of when particular criticality
  values are appropriate.  I wonder how you know that, since it is
  very different from what rfc2251 says.

- X.500 does mostly mandate criticality TRUE when criticality is
  mentioned, not merely recommend it.  Though there is one place
  where it only recommends.  I don't know if a wrong criticality in
  X.500 is an error which MUST be reported, or MAY be reported, or what.

- I can't see that the current text allows the control spec to mandate a
  particular criticality, it only says the spec can give 'direction' for
  the value.  You said somewhere that 'direction' might be a mandate.
  If so, the text in [Protocol] should mention that explicitly.
  Also, it should make clear if it is talking about mandating the
  criticality protocol field, or the criticality value as used by
  the server (maybe ignoring the protocol field), or either.

- The original text could be read as allowing the server to return an
  error if the wrong criticality is supplied.  I can't see the new text
  saying that.  I don't remember at the moment what who ended up meaning
  about that, except it took some rounds of clarifications because you
  misunderstood why I read the text that way.

The current draft is even worse than your proposal, though:

   - Regardless of the value of the criticality field, if the server 
     recognizes the control type and it is appropriate for the 
     operation, the server is to make use of the control when 
     performing the operation. 

Now it _really_ isn't possible to treat wrong criticality as an error.
With this wording it doesn't make sense here to claim that "when
performing the operation" only applies if the operation is performed at
all, and that one can still return an error instead.

Kurt D. Zeilenga writes:
> John, Hallvard,
> 
> Are you aware of any server implementation which behaves consistently
> with the interpretation that you and Hallvard favor?

I really don't know many clients at all.

> I think the suggested new text is pretty clear that if a control
> specification really needs to alter the semantics of the server's
> general criticality processing, the control specification needs
> to state an imperative separately from the guidance it gives to
> client.

If you mean stating that the criticality is mandated, then as I've said,
I don't think your text says that at all.  I'd prefer

   - direction as to what value the sender should provide for the 
     criticality field

in the current draft to be changed to 'direction or requirements as
to...'.

-- 
Hallvard


From owner-ietf-ldapbis@OpenLDAP.org  Sun Feb 29 06:59:15 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA17867
	for <ldapbis-archive@lists.ietf.org>; Sun, 29 Feb 2004 06:59:15 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1TBueYd024449;
	Sun, 29 Feb 2004 11:57:59 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1TBtbN0024431;
	Sun, 29 Feb 2004 11:55: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); Sun, 29 Feb 2004 11:55:37 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1TBtTYT024421
	for <ietf-ldapbis@OpenLDAP.org>; Sun, 29 Feb 2004 11:55:29 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from gypsy.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.10/8.12.10) with ESMTP id i1TBtFN0016776;
	Sun, 29 Feb 2004 11:55:28 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.1.1.0.20040229145453.02c78ab8@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Sun, 29 Feb 2004 15:06:49 +0900
To: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: authmeth: passwords in the clear
Cc: ietf-ldapbis@OpenLDAP.org
In-Reply-To: <HBF.20040227jcov@bombur.uio.no>
References: <HBF.20040227jcov@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 08:53 AM 2/28/2004, Hallvard B Furuseth wrote:
>authmeth-10 says:
>
>> 11. General Requirements for Password-based Authentication
>> (...)
>>   To mitigate the security risks associated with the use of passwords, 
>>   a server implementation MUST implement a configuration that at the 
>>   time of authentication or password modification, requires: 
>>
>>      1) A Start TLS encryption layer has been successfully negotiated. 
>>
>>       OR 
>>
>>      2) Some other confidentiality mechanism that protects the password 
>>         value from snooping has been provided. 
>>
>>       OR 
>
>This should only apply to cleartext passwords, not e.g. modifications of
>attributes that contain encrypted passwords.

I concur that this particular section should be limited to
cleartext passwords used in authentication.  

>Finally, as I said in the thread about this, we cannot mandate this for
>other operations than bind, because a gateway server may not know which
>attributes contain passwords (other than userPassword).  You could use
>"MUST" protect cleartext bind passwords, and "SHOULD" protect other
>cleartext passwords.

I think other "uses" of cleartext passwords (such as modification)
should be address in documents detail specific mechanisms (e.g.,
LDAP Password Modify Operation) and/or password schema.  (And,
aside from some very general guidance, issues associated with
gateways, caching proxies, chaining servers, and/or replicas
should be addressed in documents discussing such these things.)

Kurt 



From owner-ietf-ldapbis@OpenLDAP.org  Sun Feb 29 07:46:50 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA17868
	for <ldapbis-archive@lists.ietf.org>; Sun, 29 Feb 2004 06:59:15 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1TBueYb024449;
	Sun, 29 Feb 2004 11:57:59 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i1TBtPDm024414;
	Sun, 29 Feb 2004 11:55: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); Sun, 29 Feb 2004 11:55:25 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i1TBtIYT024404
	for <ietf-ldapbis@OpenLDAP.org>; Sun, 29 Feb 2004 11:55:18 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from gypsy.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.10/8.12.10) with ESMTP id i1TBtFMs016776;
	Sun, 29 Feb 2004 11:55:17 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.1.1.0.20040228163825.04913020@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Sun, 29 Feb 2004 16:15:11 +0900
To: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: Attributes with no equality matching rule
Cc: ietf-ldapbis@OpenLDAP.org
In-Reply-To: <HBF.20040227iwun@bombur.uio.no>
References: <HBF.20040227iwun@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>

Hmmm....  I'm not sure if we just missed 12.4.5, or what, but I do
think we likely do need to (re)consider whether the language in
[Models] is appropriate in face of this.

At 11:19 PM 2/26/2004, Hallvard B Furuseth wrote:
>Should the drafts conform to X.500 in this, or should they stay the
>way they are?

Well, given the RFC 2251's "MUST act in accordance with X.500"
language as well as the likely hood that multiple implementations
are acting in accordance with 12.4.5, I'm cannot see good reason
to adopt text (such as that in the current I-D) which is counter
12.4.5.

>Or - maybe implementations SHOULD behave as stated today, but MAY behave
>like X.500?  Otherwise I think LDAP-X.500 gateways are in trouble.

I think it needs to be one way or the other. Otherwise clients
designed for one way won't interoperate properly with servers
designed for the other way.

Off hand, I think we need to revert to X.500 semantics unless
there is a very good reason to not to.  I don't see one.

Kurt  



From owner-ietf-ldapbis@OpenLDAP.org  Sun Feb 29 23:34:50 2004
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA01096
	for <ldapbis-archive@lists.ietf.org>; Sun, 29 Feb 2004 23:34:49 -0500 (EST)
Received: from boole.openldap.org (smmsp@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i214WkYX055808;
	Mon, 1 Mar 2004 04:33:26 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) with SMTP id i214SZJ3055621;
	Mon, 1 Mar 2004 04:28: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, 1 Mar 2004 04:28:35 +0000
Received: from boole.openldap.org (kurt@localhost [127.0.0.1])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i214SYYT055610
	for <ietf-ldapbis@openldap.org>; Mon, 1 Mar 2004 04:28:34 GMT
	(envelope-from kurt@boole.openldap.org)
Received: (from kurt@localhost)
	by boole.openldap.org (8.12.10/8.12.10/Submit) id i214SY7T055609
	for ietf-ldapbis@openldap.org; Sun, 29 Feb 2004 20:28:34 -0800 (PST)
	(envelope-from kurt)
Received: from ausyms50.ca.com ([155.35.248.106])
	by boole.openldap.org (8.12.10/8.12.10) with ESMTP id i214R3YT055524
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 1 Mar 2004 04:27:04 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, 1 Mar 2004 15:26:42 +1100
x-mimeole: Produced By Microsoft Exchange V6.0.6547.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: Protocol: control specifications.
Date: Mon, 1 Mar 2004 15:26:42 +1100
Message-ID: <1395B4B334FCC143B36AF788E68B63810119A756@ausyms21.ca.com>
Thread-Topic: Protocol: control specifications.
Thread-Index: AcP90jzA6MBy3bF8SU2rmcKItyUR0gBcWMyQ
From: "Ramsay, Ron" <Ron.Ramsay@ca.com>
To: "Hallvard B Furuseth" <h.b.furuseth@usit.uio.no>
Cc: <ietf-ldapbis@OpenLDAP.org>
X-OriginalArrivalTime: 01 Mar 2004 04:26:42.0729 (UTC) FILETIME=[6619A990:01C3FF45]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by boole.openldap.org id i214R5YT055526
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.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 Hallvard,

I can't help feeling that you have answered your own question. Let's look at the cases:

1A: Server implements control and criticality incorrectly marked TRUE
1B: Server implements control and criticality incorrectly marked FALSE
2A: Server does not implement control and criticality incorrectly marked TRUE
2B: Server does not implement control and criticality incorrectly marked FALSE.

The server response is

1A: Server must use the information in the control to perform the operation. The result returned is the result of performing the operation; the server cannot advise the client on the use of controls
1B: This is the same as 1A: if a server CAN perform a control, it MUST perform it. Servers have no discretion when it comes to controls
2A: Server returns unavailable critical extension
2B: Server ignores the control.

That is, a server cannot make a comment about whether the criticality of the control is correct. This is because a server MUST take the control into account if it understands (implenments) it. If the server implements the control, it doesn't matter if the criticality is TRUE or FALSE.

Therefore, advice on the criticality of the control can only apply to clients. And servers cannot educate clients in this regard. As the discretion is with the clients, control designers should direct there remarks concerning criticality to the client writers.

Of course, there is the issue of response controls, but it seems that the criticality of these controls should always be FALSE.

Ron


-----Original Message-----
From: owner-ietf-ldapbis@OpenLDAP.org
[mailto:owner-ietf-ldapbis@OpenLDAP.org]On Behalf Of Hallvard B Furuseth
Sent: Friday, 27 February 2004 19:46
To: Kurt D. Zeilenga
Cc: ietf-ldapbis@OpenLDAP.org
Subject: Re: Protocol: control specifications.


I should have replied to this before, but I got so frustrated that just
had to quit the discussion for a while.  I'll rush off a reply now
before going on holiday, just so it comes before the next IETF.  Sorry
about the bad timing, and about setting this up so I can't reply in
time.

Kurt, I think we have said to each other what there is to say about my
proposal: that servers SHOULD reject incorrect criticality on known
controls.  However, you have not replied several of the my points about
your proposal.  An argument against my suggested change is _not_ an
argument for the opposite change.

- You say the intent of the original text was to encourage extension
  authors to discuss the circumstances of when particular criticality
  values are appropriate.  I wonder how you know that, since it is
  very different from what rfc2251 says.

- X.500 does mostly mandate criticality TRUE when criticality is
  mentioned, not merely recommend it.  Though there is one place
  where it only recommends.  I don't know if a wrong criticality in
  X.500 is an error which MUST be reported, or MAY be reported, or what.

- I can't see that the current text allows the control spec to mandate a
  particular criticality, it only says the spec can give 'direction' for
  the value.  You said somewhere that 'direction' might be a mandate.
  If so, the text in [Protocol] should mention that explicitly.
  Also, it should make clear if it is talking about mandating the
  criticality protocol field, or the criticality value as used by
  the server (maybe ignoring the protocol field), or either.

- The original text could be read as allowing the server to return an
  error if the wrong criticality is supplied.  I can't see the new text
  saying that.  I don't remember at the moment what who ended up meaning
  about that, except it took some rounds of clarifications because you
  misunderstood why I read the text that way.

The current draft is even worse than your proposal, though:

   - Regardless of the value of the criticality field, if the server 
     recognizes the control type and it is appropriate for the 
     operation, the server is to make use of the control when 
     performing the operation. 

Now it _really_ isn't possible to treat wrong criticality as an error.
With this wording it doesn't make sense here to claim that "when
performing the operation" only applies if the operation is performed at
all, and that one can still return an error instead.

Kurt D. Zeilenga writes:
> John, Hallvard,
> 
> Are you aware of any server implementation which behaves consistently
> with the interpretation that you and Hallvard favor?

I really don't know many clients at all.

> I think the suggested new text is pretty clear that if a control
> specification really needs to alter the semantics of the server's
> general criticality processing, the control specification needs
> to state an imperative separately from the guidance it gives to
> client.

If you mean stating that the criticality is mandated, then as I've said,
I don't think your text says that at all.  I'd prefer

   - direction as to what value the sender should provide for the 
     criticality field

in the current draft to be changed to 'direction or requirements as
to...'.

-- 
Hallvard


