From owner-ietf-ldapbis@OpenLDAP.org  Wed Jun  2 03:20:25 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 DAA04422
	for <ldapbis-archive@lists.ietf.org>; Wed, 2 Jun 2004 03:20:24 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i527IEca049189;
	Wed, 2 Jun 2004 07:18:43 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.11/8.12.11/Submit) with SMTP id i527DhiM048937;
	Wed, 2 Jun 2004 07:13:43 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 2 Jun 2004 07:13:43 +0000
Received: from nexus.adacel.com (nexus.adacel.com.au [210.11.130.1])
	by boole.openldap.org (8.12.11/8.12.11) with SMTP id i527DbWB048923
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 2 Jun 2004 07:13:39 GMT
	(envelope-from steven.legg@adacel.com.au)
Received: (qmail 27553 invoked from network); 2 Jun 2004 07:13:15 -0000
Received: from unknown (HELO adacel.com.au) (10.32.24.165)
  by nexus.adacel.com with SMTP; 2 Jun 2004 07:13:15 -0000
Message-ID: <40BD7E0A.2060902@adacel.com.au>
Date: Wed, 02 Jun 2004 17:13:14 +1000
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: Vithalprasad Gaitonde <gvithalprasad@novell.com>
CC: ietf-ldapbis@OpenLDAP.org
Subject: Re: [Models] X- options on schema elements
References: <s0b689b1.079@lucius.provo.novell.com>
In-Reply-To: <s0b689b1.079@lucius.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


Prasad,

Vithalprasad Gaitonde wrote:
> Section 4.1 of [Models] says:
> "Implementors should note that future versions of this document may
>   expand these definitions to include additional terms.  Terms whose
>   identifier begins with "X-" are reserved for private experiments,
> and
>   are followed by <SP> and <qdstrings> tokens."
> 
> Why is there a restriction  that the X-<tag> be followed by qdstrings
> alone. Shouldnt implementations be allowed to return binary values as
> well here.

The restriction is so that implementations not recognizing the private
experiment can skip over and ignore the extension if they happen to
encounter it.

Regards,
Steven



From owner-ietf-ldapbis@OpenLDAP.org  Wed Jun  2 10:05: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 KAA22709
	for <ldapbis-archive@lists.ietf.org>; Wed, 2 Jun 2004 10:05:12 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i52E01qg070924;
	Wed, 2 Jun 2004 14:03:47 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.11/8.12.11/Submit) with SMTP id i52Dvnaj070783;
	Wed, 2 Jun 2004 13:57: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, 2 Jun 2004 13:57:49 +0000
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i52DvdvI070745
	for <ietf-ldapbis@openldap.org>; Wed, 2 Jun 2004 13:57:46 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 JAA22329;
	Wed, 2 Jun 2004 09:57:17 -0400 (EDT)
Message-Id: <200406021357.JAA22329@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
Cc: ietf-ldapbis@OpenLDAP.org
From: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-ldapbis-user-schema-07.txt
Date: Wed, 02 Jun 2004 09:57:17 -0400
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

--NextPart

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

	Title		: LDAP:  Schema for User Applications
	Author(s)	: K. Dally
	Filename	: draft-ietf-ldapbis-user-schema-07.txt
	Pages		: 26
	Date		: 2004-6-1
	
This document is a integral part of the Lightweight Directory Access 
Protocol (LDAP) technical specification [ROADMAP].  It provides a 
technical specification of attribute types and object classes 
intended for use by LDAP directory clients for many directory 
services, such as, White Pages.  These objects are widely used as a 
basis for the schema in many LDAP directories.  This document does 
not cover attributes used for the administration of directory 
servers, nor does it include directory objects defined for specific 
uses in other documents.

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

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


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

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


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

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

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

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

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

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

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

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

--OtherAccess--

--NextPart--




From owner-ietf-ldapbis@OpenLDAP.org  Wed Jun  2 11:57: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 LAA29771
	for <ldapbis-archive@lists.ietf.org>; Wed, 2 Jun 2004 11:57:20 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i52FsBMd081004;
	Wed, 2 Jun 2004 15:55:36 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.11/8.12.11/Submit) with SMTP id i52FnZgw080610;
	Wed, 2 Jun 2004 15:49: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); Wed, 2 Jun 2004 15:49:35 +0000
Received: from pat.uio.no (IDENT:7411@pat.uio.no [129.240.130.16])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i52FnRWS080576
	for <ietf-ldapbis@openldap.org>; Wed, 2 Jun 2004 15:49: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.30)
	id 1BVXzX-0000vg-Vw
	for ietf-ldapbis@openldap.org; Wed, 02 Jun 2004 17:49:23 +0200
Received: from bombur.uio.no ([129.240.186.42])
	by smtp.uio.no with esmtp (Exim 4.34)
	id 1BVXzU-0002CD-KJ; Wed, 02 Jun 2004 17:49:20 +0200
Received: from hbf by bombur.uio.no with local (Exim 2.12 #7)
	id 1BVXzU-0004Dh-00; Wed, 2 Jun 2004 17:49:20 +0200
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Message-Id: <HBF.20040602q4c4@bombur.uio.no>
To: ietf-ldapbis@OpenLDAP.org
Subject: schema-07 comments
Date: Wed, 2 Jun 2004 17:49:20 +0200
X-MailScanner-Information: This message has been scanned for viruses/spam. Contact postmaster@uio.no if you have questions about this scanning
X-UiO-MailScanner: No virus found
X-UiO-Spam-info: not spam, SpamAssassin (score=-5, required 12,
	UIO_MAIL_IS_INTERNAL -5.00)
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

Mostly an update of my message 'schema comments' of 11. Dec 2003, which
you seem to have missed.

> 2.23  postalAddress
> 2.27  registeredAddress

> "15 Main St., Ottawa, Canada"

Please use the LDAP syntax, "15 Main St.$Ottawa$Canada".

> 2.26  preferredDeliveryMethod

>   if mhs-delivery is preferred over telephone-delivery, which is 
>   preferred over all other methods, the value of the value would 
>   be {1, 9}.

That's the ASN.1 representation.  Please use the LDAP string syntax,
"mhs $ telephone".  Or spell your examples of DNs something like
{{{"c", "US"}}, {{"o", "Something, Inc."}}}:-)

> 2.43  x500UniqueIdentifier

>   In X.520 [X.520], this attribute type is called 
>   uniqueIdentifier.  This is a different attribute type from both the 
>   "uid" and "uniqueIdentifier" attribute types.
               ^^^^^^^^^^^^^^^^
If you mean an LDAP "uniqueIdentifier" attribute type, that is not
defined in this document.  Where is it defined?

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

Editorial comments:

Sections 2.21 (owner), 2.28 (roleOccupant):

<o=Widget',' Inc.> in DNs should be <o=Widget\, Inc.> or <o=Widget\2C
Inc.'>.  The -06 draft had a different error: The comma was unquoted.

roleOccupant has lost 'o=' in front of Widget.

2.30 (seeAlso), OTOH, has no comma in 'Widget Inc.'.

2.40 (uniqueMember).

I don't think DN examples should have space after the ',' between RDN
components.  IIRC, that was an LDAPv2ism.

Also, these paragraphs have some bad formatting: Text dropped to the
left with no margin, maybe after a spurious line break.  Maybe the RFC
Editor has another nroff than you.  I've seen a similar effect when a
nroff macro receives more arguments than it supported.  For some nroff
commands I believe it can be fixed by putting the .command alone on one
line, so it will take the next line as its argument.

Sections 1.4, 2.26, 2.30 and 2.40 have the same formatting problem.

Spurious blank lines:
  Section 2.4:  2 in first paragraph.
  2.9: 1 in last paragraph.
  2.28: 1 in first paragraph.
  2.42: 1 in first paragraph.
  6: 1 in third paragraph.
  7.2: 2 before the [LDAP-CRL] reference.
  Appendix A: 2 before item 2.

Section 2.35 lacks a blank line before the attribute
definition and has an extra blank line after it.

These formatting problems seem to be new since schema-06, though I've
only checked -06 for a few of them.

> 1.1  Situation

>   Section 3.4 of 
>   this document supercedes the technical specification for the 'dc' 

Section 2.4.

> 2.10  facsimileTelephoneNumber

>   numbers (and, optionally, the parameters) for facsimile terrminals.  
                                                            ^^^^^^^^^^
                                                            terminals.

> 2.28  roleOccupant

>   objects(normally people) that fulfill the responsibilities of a role 
          ^^^
      missing space

> 2.32  sn

>    The sn (surname)attribute type contains name strings for the family 
                   ^^^
              missing space

> 2.35  telephoneNumber

>   (e.g., 1 234 567 8901)  Each number is one value of this 

Suggest '+1 ...' instead of '1 ...'.

> 2.40  uniqueMember

>    Distinguished Names of the object include a value that distinguishs 
                                                            ^^^^^^^^^^^^
                                                            distinguishes

>   "ou=1st Battalion#'010101', o=Defense, c=US".  

Missing 'B' after bit string.

> 3.9  organizationalRole

>   represents a job or function or position in an organization.
                    ^^^^
                 job,   function or position

> 4.  IANA Considerations

>      Specification: RFC XXXX [editor's note:  The RFC number will be 
>            the one assigned to this document.

Missing ']'.

> 7.1  Normative

> ...[ROADMAP]  Zeilenga, K., "LDAP:  Technical Specification Road Map",

Kill the '...'.

> 7.2  Informative

>    [F.1]  Operational Provisions For The International Public Telegram
>    Service Transmission System, CCITT Recommmendation F.1, 1992

Indent 2nd line.

> Appendix A  Changes RFC 2256

s/Changes/Changes made since/.

There are more changes:

- Removed '{number}' (minimum lower bound?) after the SYNTAX oid for
  all attributes that had that.

- Added text about Unicode, SASLprep and UTF-8 for userPassword.

-- 
Hallvard


From owner-ietf-ldapbis@OpenLDAP.org  Wed Jun  2 16:44: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 QAA19001
	for <ldapbis-archive@lists.ietf.org>; Wed, 2 Jun 2004 16:44:27 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i52KgPd3000325;
	Wed, 2 Jun 2004 20:42:49 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.11/8.12.11/Submit) with SMTP id i52Kbuf3099706;
	Wed, 2 Jun 2004 20:37: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); Wed, 2 Jun 2004 20:37:56 +0000
Received: from smtp-mclean.mitre.org (smtp-mclean-x.mitre.org [192.80.55.71])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i52Kbp6j099678
	for <ietf-ldapbis@openldap.org>; Wed, 2 Jun 2004 20:37: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 i52KfwV13974
	for <ietf-ldapbis@openldap.org>; Wed, 2 Jun 2004 16:41:58 -0400
Received: from MAILHUB2 (mailhub2.mitre.org [129.83.221.18])
	by smtp-mclean.mitre.org (8.11.6/8.11.6) with ESMTP id i52KfuI13931;
	Wed, 2 Jun 2004 16:41:56 -0400
Received: from mm108631-pc.mitre.org (128.29.3.71) by mailhub2.mitre.org with SMTP
        id 3036408; Wed, 02 Jun 2004 16:37:39 -0400
From: "Kathy Dally" <kdally@mitre.org>
To: "'Hallvard B Furuseth'" <h.b.furuseth@usit.uio.no>,
        <ietf-ldapbis@OpenLDAP.org>
Subject: RE: schema-07 comments
Date: Wed, 2 Jun 2004 16:37:42 -0400
Organization: The MITRE Corporation
Message-ID: <001601c448e1$74a8d680$47031d80@MITRE.ORG>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.5709
In-reply-to: <HBF.20040602q4c4@bombur.uio.no>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Importance: Normal
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by boole.openldap.org id i52Kbs6j099689
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.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!

Thanks for your input.  My responses (kld:) are
in-line below.  One general remark.  The line
wrapping problems were not in my original.  I'll
take this up with the RFC Editor.

Regards,
Kathy Dally


-----Original Message-----
From: owner-ietf-ldapbis@OpenLDAP.org
[mailto:owner-ietf-ldapbis@OpenLDAP.org] On Behalf
Of Hallvard B Furuseth
Sent: Wednesday, June 02, 2004 11:49 AM
To: ietf-ldapbis@OpenLDAP.org
Subject: schema-07 comments


Mostly an update of my message 'schema comments'
of 11. Dec 2003, which
you seem to have missed.

> 2.23  postalAddress
> 2.27  registeredAddress

> "15 Main St., Ottawa, Canada"

Please use the LDAP syntax, "15 Main
St.$Ottawa$Canada".
kld:  No.  The example is a single address.
Escaping the ","s is fixed.

> 2.26  preferredDeliveryMethod

>   if mhs-delivery is preferred over
telephone-delivery, which is 
>   preferred over all other methods, the value of
the value would 
>   be {1, 9}.

That's the ASN.1 representation.  Please use the
LDAP string syntax,
"mhs $ telephone".  Or spell your examples of DNs
something like
{{{"c", "US"}}, {{"o", "Something, Inc."}}}:-)
kld:  fixed

> 2.43  x500UniqueIdentifier

>   In X.520 [X.520], this attribute type is
called 
>   uniqueIdentifier.  This is a different
attribute type from both the 
>   "uid" and "uniqueIdentifier" attribute types.
               ^^^^^^^^^^^^^^^^
If you mean an LDAP "uniqueIdentifier" attribute
type, that is not
defined in this document.  Where is it defined?
kld:  It is in RFC 1274.  However, we are trying
to avoid references to that 
      RFC.  If "(uniqueIdentifier is specified in
RFC 1274.)", was added 
      to the paragraph would that be ok?  Would
RFC 1274 have to be included
      as an Informative Reference?  Also, see 2.39
in the I-D.
--------------------------------------------------
----------------------

Editorial comments:

Sections 2.21 (owner), 2.28 (roleOccupant):

<o=Widget',' Inc.> in DNs should be <o=Widget\,
Inc.> or <o=Widget\2C
Inc.'>.  The -06 draft had a different error: The
comma was unquoted.
kld:  fixed

roleOccupant has lost 'o=' in front of Widget.
kld:  fixed

2.30 (seeAlso), OTOH, has no comma in 'Widget
Inc.'.

2.40 (uniqueMember).

I don't think DN examples should have space after
the ',' between RDN
components.  IIRC, that was an LDAPv2ism.
kld:  fixed;  Also, the bit string was moved to
the end of the distinguished name.

Also, these paragraphs have some bad formatting:
Text dropped to the
left with no margin, maybe after a spurious line
break.  Maybe the RFC
Editor has another nroff than you.  I've seen a
similar effect when a
nroff macro receives more arguments than it
supported.  For some nroff
commands I believe it can be fixed by putting the
.command alone on one
line, so it will take the next line as its
argument.

Sections 1.4, 2.26, 2.30 and 2.40 have the same
formatting problem.

Spurious blank lines:
  Section 2.4:  2 in first paragraph.
  2.9: 1 in last paragraph.
  2.28: 1 in first paragraph.
  2.42: 1 in first paragraph.
  6: 1 in third paragraph.
  7.2: 2 before the [LDAP-CRL] reference.
  Appendix A: 2 before item 2.
kld:  fixed

Section 2.35 lacks a blank line before the
attribute
definition and has an extra blank line after it.
kld:  fixed

These formatting problems seem to be new since
schema-06, though I've
only checked -06 for a few of them.

> 1.1  Situation

>   Section 3.4 of 
>   this document supercedes the technical
specification for the 'dc' 
kld:  not in my original

Section 2.4.

> 2.10  facsimileTelephoneNumber

>   numbers (and, optionally, the parameters) for
facsimile terrminals.  
 
^^^^^^^^^^
 
terminals.
kld:  fixed

> 2.28  roleOccupant

>   objects(normally people) that fulfill the
responsibilities of a role 
          ^^^
      missing space
kld:  fixed

> 2.32  sn

>    The sn (surname)attribute type contains name
strings for the family 
                   ^^^
              missing space
kld:  fixed

> 2.35  telephoneNumber

>   (e.g., 1 234 567 8901)  Each number is one
value of this 

Suggest '+1 ...' instead of '1 ...'.
kld:  ok


> 2.40  uniqueMember

>    Distinguished Names of the object include a
value that distinguishs 
 
^^^^^^^^^^^^
 
distinguishes
kld:  fixed

>   "ou=1st Battalion#'010101', o=Defense, c=US".


Missing 'B' after bit string.
kld:  fixed

> 3.9  organizationalRole

>   represents a job or function or position in an
organization.
                    ^^^^
                 job,   function or position
kld:  fixed

> 4.  IANA Considerations

>      Specification: RFC XXXX [editor's note:
The RFC number will be 
>            the one assigned to this document.

Missing ']'.
kld:  fixed

> 7.1  Normative

> ...[ROADMAP]  Zeilenga, K., "LDAP:  Technical
Specification Road Map",

Kill the '...'.
kld:  I don't understand what's wrong.

> 7.2  Informative

>    [F.1]  Operational Provisions For The
International Public Telegram
>    Service Transmission System, CCITT
Recommmendation F.1, 1992

Indent 2nd line.
kld:  fixed

> Appendix A  Changes RFC 2256

s/Changes/Changes made since/.

There are more changes:

- Removed '{number}' (minimum lower bound?) after
the SYNTAX oid for
  all attributes that had that.

- Added text about Unicode, SASLprep and UTF-8 for
userPassword.
kld:  ok

-- 
Hallvard





From owner-ietf-ldapbis@OpenLDAP.org  Wed Jun  2 17:31:17 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 RAA22820
	for <ldapbis-archive@lists.ietf.org>; Wed, 2 Jun 2004 17:31:17 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i52LU5cn003888;
	Wed, 2 Jun 2004 21:30:09 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.11/8.12.11/Submit) with SMTP id i52LQXqO003459;
	Wed, 2 Jun 2004 21:26: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, 2 Jun 2004 21:26:33 +0000
Received: from pat.uio.no (IDENT:7411@pat.uio.no [129.240.130.16])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i52LQTwJ003419
	for <ietf-ldapbis@openldap.org>; Wed, 2 Jun 2004 21:26:32 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.30)
	id 1BVdFh-0005qY-U3; Wed, 02 Jun 2004 23:26:25 +0200
Received: from bombur.uio.no ([129.240.186.42])
	by smtp.uio.no with esmtp (Exim 4.34)
	id 1BVdFf-0006sB-J9; Wed, 02 Jun 2004 23:26:23 +0200
Received: from hbf by bombur.uio.no with local (Exim 2.12 #7)
	id 1BVdFf-00051r-00; Wed, 2 Jun 2004 23:26:23 +0200
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Message-Id: <HBF.20040602v097@bombur.uio.no>
To: "Kathy Dally" <kdally@mitre.org>
Cc: ietf-ldapbis@OpenLDAP.org
Subject: RE: schema-07 comments
In-Reply-To: <001601c448e1$74a8d680$47031d80@MITRE.ORG>
References: <HBF.20040602q4c4@bombur.uio.no>
	<001601c448e1$74a8d680$47031d80@MITRE.ORG>
X-Mailer: VM 6.37 under Emacs 19.34.1
Date: Wed, 2 Jun 2004 23:26:23 +0200
X-MailScanner-Information: This message has been scanned for viruses/spam. Contact postmaster@uio.no if you have questions about this scanning
X-UiO-MailScanner: No virus found
X-UiO-Spam-info: not spam, SpamAssassin (score=-5, required 12,
	UIO_MAIL_IS_INTERNAL -5.00)
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

Kathy Dally writes:
>Hallvard B Furuseth:

>> 2.23  postalAddress
>> 2.27  registeredAddress
> 
>> "15 Main St., Ottawa, Canada"
> 
> Please use the LDAP syntax, "15 Main
> St.$Ottawa$Canada".
> kld:  No.  The example is a single address.

Eh?  "$" doesn't separate different addresses, it is a separator
between lines of one address.  Look at the Postal Address examples
in [Syntaxes].

> Escaping the ","s is fixed.

What escaping?

>> 2.43  x500UniqueIdentifier
> 
>>   In X.520 [X.520], this attribute type is called 
>>   uniqueIdentifier.  This is a different attribute type from both the 
>>   "uid" and "uniqueIdentifier" attribute types.
>                ^^^^^^^^^^^^^^^^
> If you mean an LDAP "uniqueIdentifier" attribute type, that is not
> defined in this document.  Where is it defined?
>
> kld: It is in RFC 1274.  However, we are trying to avoid references to
> that RFC.  If "(uniqueIdentifier is specified in RFC 1274.)", was
> added to the paragraph would that be ok?  Would RFC 1274 have to be
> included as an Informative Reference?

I have no idea.  How about:

  This is a different attribute type from both the "uid" and
  the obsolete "uniqueIdentifier" LDAP attribute types.
      ^^^^^^^^                    ^^^^

> Also, see 2.39 in the I-D.

OK:

>   The uid attribute type contains computer system login names
>   associated with the object.  (Source: RFC 1274,
>   RFC 2798).  Each name is one value of this multi-valued attribute.

Hm.  I wouldn't call RFC 2798 (inetOrgPerson) a source for uid, since
it's years newer than the use of uid in RFC 2253.  If you count RFCs
newer than uid as sources, isn't [Schema] itself just as good a source?

As far as I can tell, the source for uid is buried in RFC 2253 which
says that LDAP 'uid' = X.500 'userid', combined with RFC 1274 for
'userid'.

>> 1.1  Situation
>
>>   Section 3.4 of 
>>   this document supercedes the technical specification for the 'dc' 
> kld:  not in my original

Fixed after submission, then.  I've just verified that this sentence is
in the official -07 draft.

>> 7.1  Normative
> 
>> ...[ROADMAP]  Zeilenga, K., "LDAP:  Technical
>                Specification Road Map",
> 
> Kill the '...'.
> kld:  I don't understand what's wrong.

The '...' in front of '[ROADMAP]' should be '   ', unless '...' has some
special meaning I don't know about.

>> Appendix A  Changes RFC 2256
> 
> s/Changes/Changes made since/.
> 
> There are more changes:
> 
> - Removed '{number}' (minimum lower bound?) after the SYNTAX oid for
>   all attributes that had that.

Whoops, I think I should have said 'minimum _upper_ bound'.

-- 
Hallvard


From owner-ietf-ldapbis@OpenLDAP.org  Wed Jun  2 17:31: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 RAA22822
	for <ldapbis-archive@lists.ietf.org>; Wed, 2 Jun 2004 17:31:17 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i52LU5cp003888;
	Wed, 2 Jun 2004 21:30:09 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.11/8.12.11/Submit) with SMTP id i52LQWH9003445;
	Wed, 2 Jun 2004 21:26: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); Wed, 2 Jun 2004 21:26:32 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i52LQOLJ003418
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 2 Jun 2004 21:26: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.11) with ESMTP id i52LQMqf028394;
	Wed, 2 Jun 2004 21:26:22 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.1.1.0.20040602140940.0497ef68@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Wed, 02 Jun 2004 14:26:21 -0700
To: "Kathy Dally" <kdally@mitre.org>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: RE: schema-07 comments
Cc: <ietf-ldapbis@OpenLDAP.org>
In-Reply-To: <001601c448e1$74a8d680$47031d80@MITRE.ORG>
References: <HBF.20040602q4c4@bombur.uio.no>
 <001601c448e1$74a8d680$47031d80@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:37 PM 6/2/2004, Kathy Dally wrote:
>Thanks for your input.  My responses (kld:) are
>in-line below.  One general remark.  The line
>wrapping problems were not in my original.  I'll
>take this up with the RFC Editor.

I note that the RFC Editor is not involved in I-D
publication process.   I-D publication is handled
by the Secretariat.

It's my general experience that such problems
are more commonly a problem with the submission
than any action taken by the Secretariat.  In most
cases, the I-D is published as submitted.  Hence,
I suggest you double check what you submitted
using known good text readers.  Here, text
readers (such as web browsers) are better than
text editors.

This I-D uses old templates.  Please update to latest
Status of Memo text, latest IPR text, and latest
Copyright text.  I note that a new ID checklist has
been published (replacing the old ID nits).  Please
check these off:
  http://www.ietf.org/ID-Checklist.html

The last item likely applies to most all LDAPBIS I-Ds.
I ask all Editors to address these new publication
requirements in the next I-D revisions.  (I will
provide examples in the form of updates to I-Ds
I'm editing shortly.)

Kurt


>Regards,
>Kathy Dally
>
>
>-----Original Message-----
>From: owner-ietf-ldapbis@OpenLDAP.org
>[mailto:owner-ietf-ldapbis@OpenLDAP.org] On Behalf
>Of Hallvard B Furuseth
>Sent: Wednesday, June 02, 2004 11:49 AM
>To: ietf-ldapbis@OpenLDAP.org
>Subject: schema-07 comments
>
>
>Mostly an update of my message 'schema comments'
>of 11. Dec 2003, which
>you seem to have missed.
>
>> 2.23  postalAddress
>> 2.27  registeredAddress
>
>> "15 Main St., Ottawa, Canada"
>
>Please use the LDAP syntax, "15 Main
>St.$Ottawa$Canada".
>kld:  No.  The example is a single address.
>Escaping the ","s is fixed.
>
>> 2.26  preferredDeliveryMethod
>
>>   if mhs-delivery is preferred over
>telephone-delivery, which is 
>>   preferred over all other methods, the value of
>the value would 
>>   be {1, 9}.
>
>That's the ASN.1 representation.  Please use the
>LDAP string syntax,
>"mhs $ telephone".  Or spell your examples of DNs
>something like
>{{{"c", "US"}}, {{"o", "Something, Inc."}}}:-)
>kld:  fixed
>
>> 2.43  x500UniqueIdentifier
>
>>   In X.520 [X.520], this attribute type is
>called 
>>   uniqueIdentifier.  This is a different
>attribute type from both the 
>>   "uid" and "uniqueIdentifier" attribute types.
>               ^^^^^^^^^^^^^^^^
>If you mean an LDAP "uniqueIdentifier" attribute
>type, that is not
>defined in this document.  Where is it defined?
>kld:  It is in RFC 1274.  However, we are trying
>to avoid references to that 
>      RFC.  If "(uniqueIdentifier is specified in
>RFC 1274.)", was added 
>      to the paragraph would that be ok?  Would
>RFC 1274 have to be included
>      as an Informative Reference?  Also, see 2.39
>in the I-D.
>--------------------------------------------------
>----------------------
>
>Editorial comments:
>
>Sections 2.21 (owner), 2.28 (roleOccupant):
>
><o=Widget',' Inc.> in DNs should be <o=Widget\,
>Inc.> or <o=Widget\2C
>Inc.'>.  The -06 draft had a different error: The
>comma was unquoted.
>kld:  fixed
>
>roleOccupant has lost 'o=' in front of Widget.
>kld:  fixed
>
>2.30 (seeAlso), OTOH, has no comma in 'Widget
>Inc.'.
>
>2.40 (uniqueMember).
>
>I don't think DN examples should have space after
>the ',' between RDN
>components.  IIRC, that was an LDAPv2ism.
>kld:  fixed;  Also, the bit string was moved to
>the end of the distinguished name.
>
>Also, these paragraphs have some bad formatting:
>Text dropped to the
>left with no margin, maybe after a spurious line
>break.  Maybe the RFC
>Editor has another nroff than you.  I've seen a
>similar effect when a
>nroff macro receives more arguments than it
>supported.  For some nroff
>commands I believe it can be fixed by putting the
>.command alone on one
>line, so it will take the next line as its
>argument.
>
>Sections 1.4, 2.26, 2.30 and 2.40 have the same
>formatting problem.
>
>Spurious blank lines:
>  Section 2.4:  2 in first paragraph.
>  2.9: 1 in last paragraph.
>  2.28: 1 in first paragraph.
>  2.42: 1 in first paragraph.
>  6: 1 in third paragraph.
>  7.2: 2 before the [LDAP-CRL] reference.
>  Appendix A: 2 before item 2.
>kld:  fixed
>
>Section 2.35 lacks a blank line before the
>attribute
>definition and has an extra blank line after it.
>kld:  fixed
>
>These formatting problems seem to be new since
>schema-06, though I've
>only checked -06 for a few of them.
>
>> 1.1  Situation
>
>>   Section 3.4 of 
>>   this document supercedes the technical
>specification for the 'dc' 
>kld:  not in my original
>
>Section 2.4.
>
>> 2.10  facsimileTelephoneNumber
>
>>   numbers (and, optionally, the parameters) for
>facsimile terrminals.  
> 
>^^^^^^^^^^
> 
>terminals.
>kld:  fixed
>
>> 2.28  roleOccupant
>
>>   objects(normally people) that fulfill the
>responsibilities of a role 
>          ^^^
>      missing space
>kld:  fixed
>
>> 2.32  sn
>
>>    The sn (surname)attribute type contains name
>strings for the family 
>                   ^^^
>              missing space
>kld:  fixed
>
>> 2.35  telephoneNumber
>
>>   (e.g., 1 234 567 8901)  Each number is one
>value of this 
>
>Suggest '+1 ...' instead of '1 ...'.
>kld:  ok
>
>
>> 2.40  uniqueMember
>
>>    Distinguished Names of the object include a
>value that distinguishs 
> 
>^^^^^^^^^^^^
> 
>distinguishes
>kld:  fixed
>
>>   "ou=1st Battalion#'010101', o=Defense, c=US".
>
>
>Missing 'B' after bit string.
>kld:  fixed
>
>> 3.9  organizationalRole
>
>>   represents a job or function or position in an
>organization.
>                    ^^^^
>                 job,   function or position
>kld:  fixed
>
>> 4.  IANA Considerations
>
>>      Specification: RFC XXXX [editor's note:
>The RFC number will be 
>>            the one assigned to this document.
>
>Missing ']'.
>kld:  fixed
>
>> 7.1  Normative
>
>> ...[ROADMAP]  Zeilenga, K., "LDAP:  Technical
>Specification Road Map",
>
>Kill the '...'.
>kld:  I don't understand what's wrong.
>
>> 7.2  Informative
>
>>    [F.1]  Operational Provisions For The
>International Public Telegram
>>    Service Transmission System, CCITT
>Recommmendation F.1, 1992
>
>Indent 2nd line.
>kld:  fixed
>
>> Appendix A  Changes RFC 2256
>
>s/Changes/Changes made since/.
>
>There are more changes:
>
>- Removed '{number}' (minimum lower bound?) after
>the SYNTAX oid for
>  all attributes that had that.
>
>- Added text about Unicode, SASLprep and UTF-8 for
>userPassword.
>kld:  ok
>
>-- 
>Hallvard



From owner-ietf-ldapbis@OpenLDAP.org  Wed Jun  2 19:02: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 TAA00647
	for <ldapbis-archive@lists.ietf.org>; Wed, 2 Jun 2004 19:02:08 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i52N0Hhw008132;
	Wed, 2 Jun 2004 23:00:30 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.11/8.12.11/Submit) with SMTP id i52MsLS0007954;
	Wed, 2 Jun 2004 22:54: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); Wed, 2 Jun 2004 22:54:21 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i52Mrm37007914
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 2 Jun 2004 22:54:20 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.11) with ESMTP id i52Mrkqf030246;
	Wed, 2 Jun 2004 22:53:46 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.1.1.0.20040602153922.02c875a8@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Wed, 02 Jun 2004 15:53:45 -0700
To: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: RE: schema-07 comments
Cc: "Kathy Dally" <kdally@mitre.org>, ietf-ldapbis@OpenLDAP.org
In-Reply-To: <HBF.20040602v097@bombur.uio.no>
References: <HBF.20040602q4c4@bombur.uio.no>
 <001601c448e1$74a8d680$47031d80@MITRE.ORG>
 <HBF.20040602v097@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>

I have a few comments to inject here...

At 02:26 PM 6/2/2004, Hallvard B Furuseth wrote:
>>> 2.43  x500UniqueIdentifier
>> 
>>>   In X.520 [X.520], this attribute type is called 
>>>   uniqueIdentifier.  This is a different attribute type from both the 
>>>   "uid" and "uniqueIdentifier" attribute types.
>>                ^^^^^^^^^^^^^^^^
>> If you mean an LDAP "uniqueIdentifier" attribute type, that is not
>> defined in this document.  Where is it defined?
>>
>> kld: It is in RFC 1274.  However, we are trying to avoid references to
>> that RFC.

s/references/normative references/

An informative reference would be okay.

>If "(uniqueIdentifier is specified in RFC 1274.)", was
>> added to the paragraph would that be ok?  Would RFC 1274 have to be
>> included as an Informative Reference?
>
>I have no idea.  How about:
>
>  This is a different attribute type from both the "uid" and
>  the obsolete "uniqueIdentifier" LDAP attribute types.
>      ^^^^^^^^                    ^^^^

uniqueIdentifier is not obsolete. RFC 1274 is still a proposed standard.

I suggest adding a statement to the existing text:
        The uniqueIdentifier attribute type is defined in [RFC1274].
and an informative reference.

>>   The uid attribute type contains computer system login names
>>   associated with the object.  (Source: RFC 1274,
>>   RFC 2798).  Each name is one value of this multi-valued attribute.
>
>Hm.  I wouldn't call RFC 2798 (inetOrgPerson) a source for uid, since
>it's years newer than the use of uid in RFC 2253.

RFC 2798 provided an (informative) LDAP description for the uid attribute
type, whereas RFC 1274 provided an X.500 description of the attribute type.
This document supercedes both.

>If you count RFCs newer than uid as sources, isn't [Schema] itself just as good a source?
>As far as I can tell, the source for uid is buried in RFC 2253 which
>says that LDAP 'uid' = X.500 'userid', combined with RFC 1274 for
>'userid'.

RFC 2798 specifically provided a previously missing LDAP
description.  RFC 2798 can be viewed as updating RFC 1274.



From owner-ietf-ldapbis@OpenLDAP.org  Wed Jun  2 19:13: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 TAA01386
	for <ldapbis-archive@lists.ietf.org>; Wed, 2 Jun 2004 19:13:29 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i52NC44A008590;
	Wed, 2 Jun 2004 23:12:05 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.11/8.12.11/Submit) with SMTP id i52N7dZV008462;
	Wed, 2 Jun 2004 23:07:39 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 2 Jun 2004 23:07:39 +0000
Received: from smtp-mclean.mitre.org (smtp-mclean-x.mitre.org [192.80.55.71])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i52N7S9n008450
	for <ietf-ldapbis@openldap.org>; Wed, 2 Jun 2004 23:07:36 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 i52NBbV32691
	for <ietf-ldapbis@openldap.org>; Wed, 2 Jun 2004 19:11:37 -0400
Received: from MAILHUB2 (mailhub2.mitre.org [129.83.221.18])
	by smtp-mclean.mitre.org (8.11.6/8.11.6) with ESMTP id i52NBbI32683;
	Wed, 2 Jun 2004 19:11:37 -0400
Received: from mm108631-pc.mitre.org (128.29.3.71) by mailhub2.mitre.org with SMTP
        id 3038124; Wed, 02 Jun 2004 19:07:23 -0400
From: "Kathy Dally" <kdally@mitre.org>
To: "'Hallvard B Furuseth'" <h.b.furuseth@usit.uio.no>
Cc: <ietf-ldapbis@OpenLDAP.org>
Subject: RE: schema-07 comments
Date: Wed, 2 Jun 2004 19:07:27 -0400
Organization: The MITRE Corporation
Message-ID: <003001c448f6$5f5c0f80$47031d80@MITRE.ORG>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.5709
In-reply-to: <HBF.20040602v097@bombur.uio.no>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Importance: Normal
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by boole.openldap.org id i52N7a9n008453
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.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!

As before, see "KLD2:".

Thanks,
Kathy Dally

-----Original Message-----
From: Hallvard B Furuseth
[mailto:h.b.furuseth@usit.uio.no] 
Sent: Wednesday, June 02, 2004 5:26 PM
To: Kathy Dally
Cc: ietf-ldapbis@OpenLDAP.org
Subject: RE: schema-07 comments


Kathy Dally writes:
>Hallvard B Furuseth:

>> 2.23  postalAddress
>> 2.27  registeredAddress
> 
>> "15 Main St., Ottawa, Canada"
> 
> Please use the LDAP syntax, "15 Main
> St.$Ottawa$Canada".
> kld:  No.  The example is a single address.

Eh?  "$" doesn't separate different addresses, it
is a separator
between lines of one address.  Look at the Postal
Address examples
in [Syntaxes].

> Escaping the ","s is fixed.

What escaping?
KLD2:  Oops!  I wonder what I was looking at?
Fixed.

>> 2.43  x500UniqueIdentifier
> 
>>   In X.520 [X.520], this attribute type is
called 
>>   uniqueIdentifier.  This is a different
attribute type from both the 
>>   "uid" and "uniqueIdentifier" attribute types.
>                ^^^^^^^^^^^^^^^^
> If you mean an LDAP "uniqueIdentifier" attribute
type, that is not
> defined in this document.  Where is it defined?
>
> kld: It is in RFC 1274.  However, we are trying
to avoid references to
> that RFC.  If "(uniqueIdentifier is specified in
RFC 1274.)", was
> added to the paragraph would that be ok?  Would
RFC 1274 have to be
> included as an Informative Reference?

I have no idea.  How about:

  This is a different attribute type from both the
"uid" and
  the obsolete "uniqueIdentifier" LDAP attribute
types.
      ^^^^^^^^                    ^^^^

> Also, see 2.39 in the I-D.

OK:

>   The uid attribute type contains computer
system login names
>   associated with the object.  (Source: RFC
1274,
>   RFC 2798).  Each name is one value of this
multi-valued attribute.

Hm.  I wouldn't call RFC 2798 (inetOrgPerson) a
source for uid, since
it's years newer than the use of uid in RFC 2253.
If you count RFCs
newer than uid as sources, isn't [Schema] itself
just as good a source?
KLD2:  Yes, in a sense.  That's why uid is
included in [Schema].

As far as I can tell, the source for uid is buried
in RFC 2253 which
says that LDAP 'uid' = X.500 'userid', combined
with RFC 1274 for
'userid'.

KLD2:  The name 'uid' is introduced in RFC 2253
(and its successor -DN-xx), but it does not
specify the attribute type.  The 'userId'
attribute type is in RFC 1274 and does not exist
in X.500.  A definition of 'uid' in a more recent
specification style is given in RFC 2798.
[Schema]
replaces the informative definition of RFC 2798,
as stated in section 1.1.


>> 1.1  Situation
>
>>   Section 3.4 of 
>>   this document supercedes the technical
specification for the 'dc' 
> kld:  not in my original

Fixed after submission, then.  I've just verified
that this sentence is
in the official -07 draft.
KLD2:  Huh?  I thought you were referring to a
formatting problem.  I see that the section should
be "2.4".  Is there anything else?


>> 7.1  Normative
> 
>> ...[ROADMAP]  Zeilenga, K., "LDAP:  Technical
>                Specification Road Map",
> 
> Kill the '...'.
> kld:  I don't understand what's wrong.

The '...' in front of '[ROADMAP]' should be '   ',
unless '...' has some
special meaning I don't know about.
KLD2:  Ahh!  I'm still learning the difference
between space and period!  Fixed.

>> Appendix A  Changes RFC 2256
> 
> s/Changes/Changes made since/.
> 
> There are more changes:
> 
> - Removed '{number}' (minimum lower bound?)
after the SYNTAX oid for
>   all attributes that had that.

Whoops, I think I should have said 'minimum
_upper_ bound'.
KLD2:  Yes, caught it.

-- 
Hallvard





From owner-ietf-ldapbis@OpenLDAP.org  Wed Jun  2 19:19: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 TAA01987
	for <ldapbis-archive@lists.ietf.org>; Wed, 2 Jun 2004 19:19:29 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i52NI49g008855;
	Wed, 2 Jun 2004 23:18:05 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.11/8.12.11/Submit) with SMTP id i52NCCv0008629;
	Wed, 2 Jun 2004 23:12:12 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 2 Jun 2004 23:12:12 +0000
Received: from smtp-mclean.mitre.org (smtp-mclean-x.mitre.org [192.80.55.71])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i52NC2nx008582;
	Wed, 2 Jun 2004 23:12:09 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 i52NGBV03840;
	Wed, 2 Jun 2004 19:16:11 -0400
Received: from MAILHUB2 (mailhub2.mitre.org [129.83.221.18])
	by smtp-mclean.mitre.org (8.11.6/8.11.6) with ESMTP id i52NGAI03813;
	Wed, 2 Jun 2004 19:16:10 -0400
Received: from mm108631-pc.mitre.org (128.29.3.71) by mailhub2.mitre.org with SMTP
        id 3038140; Wed, 02 Jun 2004 19:11:51 -0400
From: "Kathy Dally" <kdally@mitre.org>
To: "'Kurt D. Zeilenga'" <Kurt@OpenLDAP.org>,
        "'Hallvard B Furuseth'" <h.b.furuseth@usit.uio.no>
Cc: <ietf-ldapbis@OpenLDAP.org>
Subject: RE: schema-07 comments
Date: Wed, 2 Jun 2004 19:11:55 -0400
Organization: The MITRE Corporation
Message-ID: <003101c448f6$ff23afa0$47031d80@MITRE.ORG>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.5709
In-reply-to: <6.0.1.1.0.20040602153922.02c875a8@127.0.0.1>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Importance: Normal
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by boole.openldap.org id i52NC9nx008599
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 8bit

Hi Kurt!

I agree with your wording and will include RFC
1274 as an Informative Reference.

Thanks,
Kathy


-----Original Message-----
From: Kurt D. Zeilenga [mailto:Kurt@OpenLDAP.org] 
Sent: Wednesday, June 02, 2004 6:54 PM
To: Hallvard B Furuseth
Cc: Kathy Dally; ietf-ldapbis@OpenLDAP.org
Subject: RE: schema-07 comments


I have a few comments to inject here...

At 02:26 PM 6/2/2004, Hallvard B Furuseth wrote:
>>> 2.43  x500UniqueIdentifier
>> 
>>>   In X.520 [X.520], this attribute type is
called 
>>>   uniqueIdentifier.  This is a different
attribute type from both the 
>>>   "uid" and "uniqueIdentifier" attribute
types.
>>                ^^^^^^^^^^^^^^^^
>> If you mean an LDAP "uniqueIdentifier"
attribute type, that is not
>> defined in this document.  Where is it defined?
>>
>> kld: It is in RFC 1274.  However, we are trying
to avoid references to
>> that RFC.

s/references/normative references/

An informative reference would be okay.

>If "(uniqueIdentifier is specified in RFC
1274.)", was
>> added to the paragraph would that be ok?  Would
RFC 1274 have to be
>> included as an Informative Reference?
>
>I have no idea.  How about:
>
>  This is a different attribute type from both
the "uid" and
>  the obsolete "uniqueIdentifier" LDAP attribute
types.
>      ^^^^^^^^                    ^^^^

uniqueIdentifier is not obsolete. RFC 1274 is
still a proposed standard.

I suggest adding a statement to the existing text:
        The uniqueIdentifier attribute type is
defined in [RFC1274].
and an informative reference.

>>   The uid attribute type contains computer
system login names
>>   associated with the object.  (Source: RFC
1274,
>>   RFC 2798).  Each name is one value of this
multi-valued attribute.
>
>Hm.  I wouldn't call RFC 2798 (inetOrgPerson) a
source for uid, since
>it's years newer than the use of uid in RFC 2253.

RFC 2798 provided an (informative) LDAP
description for the uid attribute
type, whereas RFC 1274 provided an X.500
description of the attribute type.
This document supercedes both.

>If you count RFCs newer than uid as sources,
isn't [Schema] itself just as good a source?
>As far as I can tell, the source for uid is
buried in RFC 2253 which
>says that LDAP 'uid' = X.500 'userid', combined
with RFC 1274 for
>'userid'.

RFC 2798 specifically provided a previously
missing LDAP
description.  RFC 2798 can be viewed as updating
RFC 1274.






From owner-ietf-ldapbis@OpenLDAP.org  Thu Jun  3 02:22: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 CAA11936
	for <ldapbis-archive@lists.ietf.org>; Thu, 3 Jun 2004 02:22:21 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i536IJi9028006;
	Thu, 3 Jun 2004 06:18:30 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.11/8.12.11/Submit) with SMTP id i536Dtds027905;
	Thu, 3 Jun 2004 06:13:55 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 3 Jun 2004 06:13:55 +0000
Received: from pat.uio.no (IDENT:7411@pat.uio.no [129.240.130.16])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i536DUOw027893
	for <ietf-ldapbis@openldap.org>; Thu, 3 Jun 2004 06:13:51 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.30)
	id 1BVlTj-0005pB-3K; Thu, 03 Jun 2004 08:13:27 +0200
Received: from bombur.uio.no ([129.240.186.42])
	by smtp.uio.no with esmtp (Exim 4.34)
	id 1BVlTg-0002y0-HB; Thu, 03 Jun 2004 08:13:24 +0200
Received: from hbf by bombur.uio.no with local (Exim 2.12 #7)
	id 1BVlTf-0006Sb-00; Thu, 3 Jun 2004 08:13:23 +0200
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Message-Id: <HBF.20040603m72u@bombur.uio.no>
To: Kathy Dally <kdally@mitre.org>
Cc: ietf-ldapbis@OpenLDAP.org
Subject: RE: schema-07 comments
In-Reply-To: <003001c448f6$5f5c0f80$47031d80@MITRE.ORG>
References: <HBF.20040602v097@bombur.uio.no>
	<003001c448f6$5f5c0f80$47031d80@MITRE.ORG>
X-Mailer: VM 6.37 under Emacs 19.34.1
Date: Thu, 3 Jun 2004 08:13:23 +0200
X-MailScanner-Information: This message has been scanned for viruses/spam. Contact postmaster@uio.no if you have questions about this scanning
X-UiO-MailScanner: No virus found
X-UiO-Spam-info: not spam, SpamAssassin (score=-5, required 12,
	UIO_MAIL_IS_INTERNAL -5.00)
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

Kathy Dally writes:
>From: Hallvard B Furuseth

>>> 1.1  Situation
>>
>>>   Section 3.4 of 
>>>   this document supercedes the technical specification for the 'dc' 
>> kld:  not in my original
> 
> Fixed after submission, then.  I've just verified that this sentence is
> in the official -07 draft.
> KLD2:  Huh?  I thought you were referring to a formatting problem.

Ah.  When I said "These formatting problems..." I meant "The above
formatting problems...".

> I see that the section should
> be "2.4".  Is there anything else?

No.

-- 
Hallvard


From owner-ietf-ldapbis@OpenLDAP.org  Thu Jun  3 04:13: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 EAA18431
	for <ldapbis-archive@lists.ietf.org>; Thu, 3 Jun 2004 04:13:55 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i538CWos033545;
	Thu, 3 Jun 2004 08:12:42 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.11/8.12.11/Submit) with SMTP id i538C1TG033523;
	Thu, 3 Jun 2004 08:12:01 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 3 Jun 2004 08:12:01 +0000
Received: from pat.uio.no (IDENT:7411@pat.uio.no [129.240.130.16])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i538BcXW033492
	for <ietf-ldapbis@openldap.org>; Thu, 3 Jun 2004 08:11:40 GMT
	(envelope-from hbf@bombur.uio.no)
Received: from mail-mx2.uio.no ([129.240.10.30])
	by pat.uio.no with esmtp (Exim 4.30)
	id 1BVnK3-0000QO-8f
	for ietf-ldapbis@openldap.org; Thu, 03 Jun 2004 10:11:35 +0200
Received: from bombur.uio.no ([129.240.186.42])
	by smtp.uio.no with esmtp (Exim 4.34)
	id 1BVnJu-0000o3-61; Thu, 03 Jun 2004 10:11:26 +0200
Received: from hbf by bombur.uio.no with local (Exim 2.12 #7)
	id 1BVnJq-0006ji-00; Thu, 3 Jun 2004 10:11:22 +0200
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Message-Id: <HBF.20040603k82g@bombur.uio.no>
To: ietf-ldapbis@OpenLDAP.org
Subject: More schema-07 nits
Date: Thu, 3 Jun 2004 10:11:22 +0200
X-MailScanner-Information: This message has been scanned for viruses/spam. Contact postmaster@uio.no if you have questions about this scanning
X-UiO-MailScanner: No virus found
X-UiO-Spam-info: not spam, SpamAssassin (score=-5, required 12,
	UIO_MAIL_IS_INTERNAL -5.00)
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

[2798] should be [RFC2798], which is missing from References.
[LDAP-PKI] seems to be called [LDAP-CERT] in References.
{} should be [] in {LDAP-CERT] and [RFC1034}.
Reference [X.509] is not used.

A few more old schema comment of mine which seems to have been lost:

I think Section 2.4 (dc) needs '(Source: RFC 2247)', since one needs to
read that RFC to find an object class to put "dc" in.  The RFC is
mentioned elsewhere, but section 2.4 and 3.* is where readers who need
such an object class will be looking.

BTW, shouldn't Acknowledgements mention the X.500 series?

-- 
Hallvard


From owner-ietf-ldapbis@OpenLDAP.org  Thu Jun  3 05:26: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 FAA22911
	for <ldapbis-archive@lists.ietf.org>; Thu, 3 Jun 2004 05:26:16 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i539ON3i037390;
	Thu, 3 Jun 2004 09:24:43 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.11/8.12.11/Submit) with SMTP id i539LS7k037259;
	Thu, 3 Jun 2004 09:21: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); Thu, 3 Jun 2004 09:21:28 +0000
Received: from pat.uio.no (IDENT:7411@pat.uio.no [129.240.130.16])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i539LN0B037235
	for <ietf-ldapbis@openldap.org>; Thu, 3 Jun 2004 09:21:25 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.30)
	id 1BVoPN-0006YK-Gs
	for ietf-ldapbis@openldap.org; Thu, 03 Jun 2004 11:21:09 +0200
Received: from bombur.uio.no ([129.240.186.42])
	by smtp.uio.no with esmtp (Exim 4.34)
	id 1BVoKF-0005IA-PN; Thu, 03 Jun 2004 11:15:51 +0200
Received: from hbf by bombur.uio.no with local (Exim 2.12 #7)
	id 1BVoKE-0006sg-00; Thu, 3 Jun 2004 11:15:50 +0200
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Message-Id: <HBF.20040603j59l@bombur.uio.no>
To: ietf-ldapbis@OpenLDAP.org
Subject: I-D templates (was: schema-07 comments)
In-Reply-To: <6.0.1.1.0.20040602140940.0497ef68@127.0.0.1>
References: <HBF.20040602q4c4@bombur.uio.no>
	<001601c448e1$74a8d680$47031d80@MITRE.ORG>
	<6.0.1.1.0.20040602140940.0497ef68@127.0.0.1>
X-Mailer: VM 6.37 under Emacs 19.34.1
Date: Thu, 3 Jun 2004 11:15:50 +0200
X-MailScanner-Information: This message has been scanned for viruses/spam. Contact postmaster@uio.no if you have questions about this scanning
X-UiO-MailScanner: No virus found
X-UiO-Spam-info: not spam, SpamAssassin (score=-5, required 12,
	UIO_MAIL_IS_INTERNAL -5.00)
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.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:
> This I-D uses old templates.  Please update to latest
> Status of Memo text, latest IPR text, and latest
> Copyright text.  I note that a new ID checklist has
> been published (replacing the old ID nits).  Please
> check these off:
>   http://www.ietf.org/ID-Checklist.html

1id-guidelines.txt still requires

         This document is an Internet-Draft and is subject to
         all provisions of Section 10 of RFC2026.

but the idnits-v1.31 program complains that this text should not be used
with the new templates.  It also refers to rfc2223bis-07, which has a
reference which looks buggy to RFC3667 section 5.2.  I've written to the
authors of the documents since I'm writing an I-D too, and will forward
the responses.

-- 
Hallvard


From owner-ietf-ldapbis@OpenLDAP.org  Thu Jun  3 10:34: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 KAA16109
	for <ldapbis-archive@lists.ietf.org>; Thu, 3 Jun 2004 10:34:18 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i53EUGLj055264;
	Thu, 3 Jun 2004 14:32:53 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.11/8.12.11/Submit) with SMTP id i53EOq9Z054201;
	Thu, 3 Jun 2004 14:24:52 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, 3 Jun 2004 14:24:52 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i53EOe8n054164
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 3 Jun 2004 14:24:51 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.11) with ESMTP id i53EOeqf035829;
	Thu, 3 Jun 2004 14:24:40 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.1.1.0.20040603071526.04b5ed08@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Thu, 03 Jun 2004 07:24:37 -0700
To: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: I-D templates (was: schema-07 comments)
Cc: ietf-ldapbis@OpenLDAP.org
In-Reply-To: <HBF.20040603j59l@bombur.uio.no>
References: <HBF.20040602q4c4@bombur.uio.no>
 <001601c448e1$74a8d680$47031d80@MITRE.ORG>
 <6.0.1.1.0.20040602140940.0497ef68@127.0.0.1>
 <HBF.20040603j59l@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>

Hopefully this will be updated soon.  Talk is require
new text soon (e.g., refuse submissions which don't use
new text) .  So, please ignore this 1id-guidelines
statement regarding Section 10 of RFC 2026.  This section
is replaced by RFC 3667/3668.  See Section 5 and 6 of
RFC 3667 for notices for I-D.

At 02:15 AM 6/3/2004, Hallvard B Furuseth wrote:
>Kurt D. Zeilenga writes:
>> This I-D uses old templates.  Please update to latest
>> Status of Memo text, latest IPR text, and latest
>> Copyright text.  I note that a new ID checklist has
>> been published (replacing the old ID nits).  Please
>> check these off:
>>   http://www.ietf.org/ID-Checklist.html
>
>1id-guidelines.txt still requires
>
>         This document is an Internet-Draft and is subject to
>         all provisions of Section 10 of RFC2026.
>
>but the idnits-v1.31 program complains that this text should not be used
>with the new templates.  It also refers to rfc2223bis-07, which has a
>reference which looks buggy to RFC3667 section 5.2.  I've written to the
>authors of the documents since I'm writing an I-D too, and will forward
>the responses.
>
>-- 
>Hallvard



From owner-ietf-ldapbis@OpenLDAP.org  Tue Jun  8 16:21: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 QAA21637
	for <ldapbis-archive@lists.ietf.org>; Tue, 8 Jun 2004 16:21:17 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i58KDNJF089368;
	Tue, 8 Jun 2004 20:19:59 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.11/8.12.11/Submit) with SMTP id i58KBtkF089162;
	Tue, 8 Jun 2004 20:11: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, 8 Jun 2004 20:11:55 +0000
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i58KBqW9089152
	for <ietf-ldapbis@openldap.org>; Tue, 8 Jun 2004 20:11:53 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 QAA21180;
	Tue, 8 Jun 2004 16:11:49 -0400 (EDT)
Message-Id: <200406082011.QAA21180@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
Cc: ietf-ldapbis@OpenLDAP.org
From: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-ldapbis-roadmap-05.txt
Date: Tue, 08 Jun 2004 16:11:49 -0400
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

--NextPart

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

	Title		: Lightweight Directory Access Protocol (LDAP): 
			  Technical Specification Road Map
	Author(s)	: K. Zeilenga
	Filename	: draft-ietf-ldapbis-roadmap-05.txt
	Pages		: 7
	Date		: 2004-6-8
	
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-05.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


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-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-roadmap-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-6-8163458.I-D@ietf.org>

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

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

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

--OtherAccess--

--NextPart--




From owner-ietf-ldapbis@OpenLDAP.org  Tue Jun  8 16:21: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 QAA21695
	for <ldapbis-archive@lists.ietf.org>; Tue, 8 Jun 2004 16:21:35 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i58KDNJD089368;
	Tue, 8 Jun 2004 20:19:58 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.11/8.12.11/Submit) with SMTP id i58KBAub089089;
	Tue, 8 Jun 2004 20:11:10 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 8 Jun 2004 20:11:10 +0000
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i58KB4bc089079
	for <ietf-ldapbis@openldap.org>; Tue, 8 Jun 2004 20:11: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 QAA21149;
	Tue, 8 Jun 2004 16:11:01 -0400 (EDT)
Message-Id: <200406082011.QAA21149@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
Cc: ietf-ldapbis@OpenLDAP.org
From: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-ldapbis-models-11.txt
Date: Tue, 08 Jun 2004 16:11:01 -0400
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

--NextPart

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

	Title		: LDAP: Directory Information Models
	Author(s)	: K. Zeilenga
	Filename	: draft-ietf-ldapbis-models-11.txt
	Pages		: 50
	Date		: 2004-6-8
	
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, as used in LDAP.

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

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


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-11.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-11.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-6-8163435.I-D@ietf.org>

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

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

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

--OtherAccess--

--NextPart--




From owner-ietf-ldapbis@OpenLDAP.org  Tue Jun  8 16:32: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 QAA22177
	for <ldapbis-archive@lists.ietf.org>; Tue, 8 Jun 2004 16:32:21 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i58KV0tb091046;
	Tue, 8 Jun 2004 20:31:02 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.11/8.12.11/Submit) with SMTP id i58KUdDE091031;
	Tue, 8 Jun 2004 20:30:39 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 8 Jun 2004 20:30:39 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i58KUZZZ091020
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 8 Jun 2004 20:30:36 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.11) with ESMTP id i58KUZqf076809
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 8 Jun 2004 20:30:35 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.1.1.0.20040608132731.0485a478@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Tue, 08 Jun 2004 13:30:50 -0700
To: ietf-ldapbis@OpenLDAP.org
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: I-D ACTION:draft-ietf-ldapbis-bcp64-03.txt
In-Reply-To: <200406082010.QAA21127@ietf.org>
References: <200406082010.QAA21127@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

In this revision, the following substantive change(s) were made:

- Section 3.1: clarified that Directory Numbers may be used
  not only by the IETF, but by others.

Kurt



From owner-ietf-ldapbis@OpenLDAP.org  Tue Jun  8 16:44: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 QAA22648
	for <ldapbis-archive@lists.ietf.org>; Tue, 8 Jun 2004 16:44:01 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i58Kh2Au091464;
	Tue, 8 Jun 2004 20:43:05 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.11/8.12.11/Submit) with SMTP id i58KfxS2091415;
	Tue, 8 Jun 2004 20:41: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, 8 Jun 2004 20:41:59 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i58KfrZ8091405
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 8 Jun 2004 20:41:58 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.11) with ESMTP id i58Kfqqf076874
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 8 Jun 2004 20:41:52 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.1.1.0.20040608133155.04974058@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Tue, 08 Jun 2004 13:42:07 -0700
To: ietf-ldapbis@OpenLDAP.org
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: I-D ACTION:draft-ietf-ldapbis-roadmap-05.txt
In-Reply-To: <200406082011.QAA21180@ietf.org>
References: <200406082011.QAA21180@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

In this revision, the following substantive changes were
made:

- Added: Extensions are expected to be truly optional.
- Added: Prior LDAP TS includes RFC 3771
  (this text is not well formed, will correct in next revision)
- Added: Added [Protocol] includes RFC 3771 portion of prior LDAP TS.
- Added: Other documents may be updated/replaced by portions of
  LDAP TS as noted in documents detailing these portions.
  (this text will be improved in next revision as well)

At 01:11 PM 6/8/2004, Internet-Drafts@ietf.org wrote:
>A New Internet-Draft is available from the on-line Internet-Drafts directories.
>This draft is a work item of the LDAP (v3) Revision Working Group of the IETF.
>
>        Title           : Lightweight Directory Access Protocol (LDAP): 
>                          Technical Specification Road Map
>        Author(s)       : K. Zeilenga
>        Filename        : draft-ietf-ldapbis-roadmap-05.txt
>        Pages           : 7
>        Date            : 2004-6-8
>        
>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-05.txt
>
>To remove yourself from the I-D Announcement list, send a message to 
>i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
>You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
>to change your subscription settings.
>
>
>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-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-roadmap-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.
>Content-Type: text/plain
>Content-ID:     <2004-6-8163458.I-D@ietf.org>
>
>ENCODING mime
>FILE /internet-drafts/draft-ietf-ldapbis-roadmap-05.txt
>
><ftp://ftp.ietf.org/internet-drafts/draft-ietf-ldapbis-roadmap-05.txt>



From owner-ietf-ldapbis@OpenLDAP.org  Tue Jun  8 16:50:19 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 QAA23242
	for <ldapbis-archive@lists.ietf.org>; Tue, 8 Jun 2004 16:50:18 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i58Kmt6L091897;
	Tue, 8 Jun 2004 20:48:56 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.11/8.12.11/Submit) with SMTP id i58Kh9ch091479;
	Tue, 8 Jun 2004 20:43:09 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 8 Jun 2004 20:43:09 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i58Kh3Z2091468
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 8 Jun 2004 20:43: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.11) with ESMTP id i58Kh3qf076886
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 8 Jun 2004 20:43:03 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.1.1.0.20040608134248.02c82a90@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Tue, 08 Jun 2004 13:43:18 -0700
To: ietf-ldapbis@OpenLDAP.org
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: I-D ACTION:draft-ietf-ldapbis-dn-14.txt
In-Reply-To: <200406082011.QAA21166@ietf.org>
References: <200406082011.QAA21166@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

No substantive changes were made in this revision.


At 01:11 PM 6/8/2004, Internet-Drafts@ietf.org wrote:
>A New Internet-Draft is available from the on-line Internet-Drafts directories.
>This draft is a work item of the LDAP (v3) Revision Working Group of the IETF.
>
>        Title           : LDAP:String Representation of Distinguished Names
>        Author(s)       : K. Zeilenga
>        Filename        : draft-ietf-ldapbis-dn-14.txt
>        Pages           : 14
>        Date            : 2004-6-8
>        
>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-14.txt
>
>To remove yourself from the I-D Announcement list, send a message to 
>i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
>You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
>to change your subscription settings.
>
>
>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-14.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-14.txt".
>        
>NOTE:   The mail server at ietf.org can return the document in
>        MIME-encoded form by using the "mpack" utility.  To use this
>        feature, insert the command "ENCODING mime" before the "FILE"
>        command.  To decode the response(s), you will need "munpack" or
>        a MIME-compliant mail reader.  Different MIME-compliant mail readers
>        exhibit different behavior, especially when dealing with
>        "multipart" MIME messages (i.e. documents which have been split
>        up into multiple messages), so check your local documentation on
>        how to manipulate these messages.
>                
>                
>Below is the data which will enable a MIME compliant mail reader
>implementation to automatically retrieve the ASCII version of the
>Internet-Draft.
>Content-Type: text/plain
>Content-ID:     <2004-6-8163451.I-D@ietf.org>
>
>ENCODING mime
>FILE /internet-drafts/draft-ietf-ldapbis-dn-14.txt
>
><ftp://ftp.ietf.org/internet-drafts/draft-ietf-ldapbis-dn-14.txt>



From owner-ietf-ldapbis@OpenLDAP.org  Tue Jun  8 17:04: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 RAA23878
	for <ldapbis-archive@lists.ietf.org>; Tue, 8 Jun 2004 17:04:00 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i58L1AnM092765;
	Tue, 8 Jun 2004 21:02:50 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.11/8.12.11/Submit) with SMTP id i58Krdgc092211;
	Tue, 8 Jun 2004 20:53:39 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 8 Jun 2004 20:53:39 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i58KrbvB092198
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 8 Jun 2004 20:53:38 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.11) with ESMTP id i58Kraqf076976
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 8 Jun 2004 20:53:36 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.1.1.0.20040608134402.04855fe0@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Tue, 08 Jun 2004 13:53:51 -0700
To: ietf-ldapbis@OpenLDAP.org
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: I-D ACTION:draft-ietf-ldapbis-strprep-04.txt
In-Reply-To: <200406082011.QAA21159@ietf.org>
References: <200406082011.QAA21159@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

In this revision, the following substantive changes were made.

The term "combining mark" was more clearly defined.

A definitive lists of "all other control code points (e.g., Cc)
or code points with a control function (e.g., Cf)" and
"All other code points with Separator (space, line, or paragraph)
property" are now provided.

The Appendix B table, and mention of it, was removed as redundant.

Lists provided in the Prohibit step were replaced with
references to equivalent tables in [Stringprep].

The above changes clarify, but do not alter, the LDAPprep
algorithms.  Please verify correctness of all lists and
tables used.

Kurt

At 01:11 PM 6/8/2004, Internet-Drafts@ietf.org wrote:
>A New Internet-Draft is available from the on-line Internet-Drafts directories.
>This draft is a work item of the LDAP (v3) Revision Working Group of the IETF.
>
>        Title           : LDAP: Internationalized String Preparation
>        Author(s)       : K. Zeilenga
>        Filename        : draft-ietf-ldapbis-strprep-04.txt
>        Pages           : 19
>        Date            : 2004-6-8
>        
>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-04.txt
>
>To remove yourself from the I-D Announcement list, send a message to 
>i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
>You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
>to change your subscription settings.
>
>
>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-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-strprep-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.
>Content-Type: text/plain
>Content-ID:     <2004-6-8163443.I-D@ietf.org>
>
>ENCODING mime
>FILE /internet-drafts/draft-ietf-ldapbis-strprep-04.txt
>
><ftp://ftp.ietf.org/internet-drafts/draft-ietf-ldapbis-strprep-04.txt>



From owner-ietf-ldapbis@OpenLDAP.org  Tue Jun  8 17:10: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 QAA21638
	for <ldapbis-archive@lists.ietf.org>; Tue, 8 Jun 2004 16:21:17 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i58KDNJB089368;
	Tue, 8 Jun 2004 20:19:58 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.11/8.12.11/Submit) with SMTP id i58KAqRu089069;
	Tue, 8 Jun 2004 20:10:52 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, 8 Jun 2004 20:10:52 +0000
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i58KAmrs089059
	for <ietf-ldapbis@openldap.org>; Tue, 8 Jun 2004 20:10:50 GMT
	(envelope-from dinaras@cnri.reston.va.us)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21127;
	Tue, 8 Jun 2004 16:10:46 -0400 (EDT)
Message-Id: <200406082010.QAA21127@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
Cc: ietf-ldapbis@OpenLDAP.org
From: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-ldapbis-bcp64-03.txt
Date: Tue, 08 Jun 2004 16:10:46 -0400
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

--NextPart

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

	Title		: IANA Considerations for LDAP
	Author(s)	: K. Zeilenga
	Filename	: draft-ietf-ldapbis-bcp64-03.txt
	Pages		: 16
	Date		: 2004-6-8
	
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-03.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


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-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-bcp64-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-6-8163427.I-D@ietf.org>

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

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

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

--OtherAccess--

--NextPart--




From owner-ietf-ldapbis@OpenLDAP.org  Tue Jun  8 17:10: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 QAA21635
	for <ldapbis-archive@lists.ietf.org>; Tue, 8 Jun 2004 16:21:17 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i58KDNJH089368;
	Tue, 8 Jun 2004 20:19:59 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.11/8.12.11/Submit) with SMTP id i58KBKlI089107;
	Tue, 8 Jun 2004 20:11: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); Tue, 8 Jun 2004 20:11:20 +0000
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i58KBGD7089095
	for <ietf-ldapbis@openldap.org>; Tue, 8 Jun 2004 20:11:18 GMT
	(envelope-from dinaras@cnri.reston.va.us)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21159;
	Tue, 8 Jun 2004 16:11:14 -0400 (EDT)
Message-Id: <200406082011.QAA21159@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
Cc: ietf-ldapbis@OpenLDAP.org
From: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-ldapbis-strprep-04.txt
Date: Tue, 08 Jun 2004 16:11:14 -0400
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

--NextPart

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

	Title		: LDAP: Internationalized String Preparation
	Author(s)	: K. Zeilenga
	Filename	: draft-ietf-ldapbis-strprep-04.txt
	Pages		: 19
	Date		: 2004-6-8
	
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-04.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


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-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-strprep-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-6-8163443.I-D@ietf.org>

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

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

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

--OtherAccess--

--NextPart--




From owner-ietf-ldapbis@OpenLDAP.org  Tue Jun  8 17:10: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 QAA21636
	for <ldapbis-archive@lists.ietf.org>; Tue, 8 Jun 2004 16:21:17 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i58KDNJJ089368;
	Tue, 8 Jun 2004 20:19:59 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.11/8.12.11/Submit) with SMTP id i58KBV6W089125;
	Tue, 8 Jun 2004 20:11:31 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 8 Jun 2004 20:11:31 +0000
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i58KBPjI089112
	for <ietf-ldapbis@openldap.org>; Tue, 8 Jun 2004 20:11:30 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 QAA21166;
	Tue, 8 Jun 2004 16:11:23 -0400 (EDT)
Message-Id: <200406082011.QAA21166@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
Cc: ietf-ldapbis@OpenLDAP.org
From: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-ldapbis-dn-14.txt
Date: Tue, 08 Jun 2004 16:11:23 -0400
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

--NextPart

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

	Title		: LDAP:String Representation of Distinguished Names
	Author(s)	: K. Zeilenga
	Filename	: draft-ietf-ldapbis-dn-14.txt
	Pages		: 14
	Date		: 2004-6-8
	
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-14.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


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-14.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-14.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-6-8163451.I-D@ietf.org>

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

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

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

--OtherAccess--

--NextPart--




From owner-ietf-ldapbis@OpenLDAP.org  Tue Jun  8 17:18: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 RAA24577
	for <ldapbis-archive@lists.ietf.org>; Tue, 8 Jun 2004 17:18:27 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i58LCxUG093727;
	Tue, 8 Jun 2004 21:17:14 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.11/8.12.11/Submit) with SMTP id i58L8WGh093456;
	Tue, 8 Jun 2004 21:08:32 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 8 Jun 2004 21:08:32 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i58L8TjB093393
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 8 Jun 2004 21:08:30 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.11) with ESMTP id i58L8Sqf077124
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 8 Jun 2004 21:08:28 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.1.1.0.20040608135436.0497de50@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Tue, 08 Jun 2004 14:08:43 -0700
To: ietf-ldapbis@OpenLDAP.org
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: I-D ACTION:draft-ietf-ldapbis-models-11.txt
In-Reply-To: <200406082011.QAA21149@ietf.org>
References: <200406082011.QAA21149@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

In this revision, the following substantive changes were made:

- flipped sections 2.2/2.3

- reworked attribute value specification, incorporating
  2.5.4 into other sections (namely new 2.2).

- affect of no equality matching rule for an attribute type
  was clarified.

- xstring corrected to use ALPHA not UALPHA

- described SINGLE-VALUE

- Updated "changes since" to note that
  "Subtyping and AttributeDescriptions with options" have
  been clarified.

At 01:11 PM 6/8/2004, Internet-Drafts@ietf.org wrote:
>A New Internet-Draft is available from the on-line Internet-Drafts directories.
>This draft is a work item of the LDAP (v3) Revision Working Group of the IETF.
>
>        Title           : LDAP: Directory Information Models
>        Author(s)       : K. Zeilenga
>        Filename        : draft-ietf-ldapbis-models-11.txt
>        Pages           : 50
>        Date            : 2004-6-8
>        
>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, as used in LDAP.
>
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-ietf-ldapbis-models-11.txt
>
>To remove yourself from the I-D Announcement list, send a message to 
>i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
>You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
>to change your subscription settings.
>
>
>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-11.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-11.txt".
>        
>NOTE:   The mail server at ietf.org can return the document in
>        MIME-encoded form by using the "mpack" utility.  To use this
>        feature, insert the command "ENCODING mime" before the "FILE"
>        command.  To decode the response(s), you will need "munpack" or
>        a MIME-compliant mail reader.  Different MIME-compliant mail readers
>        exhibit different behavior, especially when dealing with
>        "multipart" MIME messages (i.e. documents which have been split
>        up into multiple messages), so check your local documentation on
>        how to manipulate these messages.
>                
>                
>Below is the data which will enable a MIME compliant mail reader
>implementation to automatically retrieve the ASCII version of the
>Internet-Draft.
>Content-Type: text/plain
>Content-ID:     <2004-6-8163435.I-D@ietf.org>
>
>ENCODING mime
>FILE /internet-drafts/draft-ietf-ldapbis-models-11.txt
>
><ftp://ftp.ietf.org/internet-drafts/draft-ietf-ldapbis-models-11.txt>



From owner-ietf-ldapbis@OpenLDAP.org  Tue Jun  8 19:47:25 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 TAA10117
	for <ldapbis-archive@lists.ietf.org>; Tue, 8 Jun 2004 19:47:25 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i58NkG10002538;
	Tue, 8 Jun 2004 23:46:26 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.11/8.12.11/Submit) with SMTP id i58NWVL0001462;
	Tue, 8 Jun 2004 23: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); Tue, 8 Jun 2004 23:32:31 +0000
Received: from smtp.unc.edu (smtpsrv11.isis.unc.edu [152.2.1.242])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i58NWRQU001446
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 8 Jun 2004 23:32:29 GMT
	(envelope-from ses@unc.edu)
Received: from [152.2.246.2] (eritrea.oit.unc.edu [152.2.246.2])
	(authenticated bits=0)
	by smtp.unc.edu (8.12.9/8.12.9) with ESMTP id i58NVYMY005781;
	Tue, 8 Jun 2004 19:31:35 -0400 (EDT)
Message-ID: <40C64C57.5040701@unc.edu>
Date: Tue, 08 Jun 2004 19:31:35 -0400
From: Simon Spero <ses@unc.edu>
User-Agent: Mozilla Thunderbird 0.6 (Macintosh/20040502)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Steven Legg <steven.legg@adacel.com.au>
CC: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>, ietf-ldapbis@OpenLDAP.org
Subject: Extension markers in ldap (was Re: I-D ACTION:draft-ietf-ldapbis-protocol-24.txt
 )
References: <s0a9473a.050@sinclair.provo.novell.com>	<40A9A2DB.1080606@adacel.com.au> <HBF.20040519erb1@bombur.uio.no> <40ABF873.60804@adacel.com.au>
In-Reply-To: <40ABF873.60804@adacel.com.au>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Steven Legg wrote:

> After intermediateResponse. The ellipsis is placed at the end of the 
> alternatives
> in the original base definition (which I would take to be the one in 
> RFC 2251).
> Each extension thereafter is appended to the end.

There's a problem with adding extension markers to the CHOICE, but we 
can get around it with the power of imagination.

RFC2251 doesn't have implicit extensibility on CHOICE - just SEQUENCE .
Making a CHOICE extensible changes the encoded form under the PER.
Even if the protocol version number were to be changed, it would be 
inside the bindRequest, which is  inside a protocolOp.

The easy way around this problem is to just  pretend that 
intermediateResponse and the extension marker were  in RFC2251 all the 
time; nobody noticed because the module was declared with IMPLICIT FNORDS.

Simon






From owner-ietf-ldapbis@OpenLDAP.org  Wed Jun  9 20:27:00 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 UAA05689
	for <ldapbis-archive@lists.ietf.org>; Wed, 9 Jun 2004 20:26:59 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5A0PFfm076010;
	Thu, 10 Jun 2004 00:25:36 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.11/8.12.11/Submit) with SMTP id i5A0MXUj075938;
	Thu, 10 Jun 2004 00:22:33 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 10 Jun 2004 00:22:33 +0000
Received: from adacel.com (gunsmoke.adacel.com.au [210.11.130.7])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5A0LSAg075914
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 10 Jun 2004 00:22:32 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.6.7)
	id <B00027092d>; Thu, 10 Jun 2004 10:19:25 +1000
Received: (qmail 6352 invoked from network); 10 Jun 2004 00:13:11 -0000
Received: from unknown (HELO adacel.com.au) (10.32.24.165)
  by nexus.adacel.com with SMTP; 10 Jun 2004 00:13:11 -0000
Message-ID: <40C7A796.1000609@adacel.com.au>
Date: Thu, 10 Jun 2004 10:13:10 +1000
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: Simon Spero <ses@unc.edu>
CC: ietf-ldapbis@OpenLDAP.org
Subject: Re: Extension markers in ldap (was Re: I-D ACTION:draft-ietf-ldapbis-protocol-24.txt
 )
References: <s0a9473a.050@sinclair.provo.novell.com>	<40A9A2DB.1080606@adacel.com.au> <HBF.20040519erb1@bombur.uio.no> <40ABF873.60804@adacel.com.au> <40C64C57.5040701@unc.edu>
In-Reply-To: <40C64C57.5040701@unc.edu>
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


Simon,

Simon Spero wrote:
> Steven Legg wrote:
> 
>> After intermediateResponse. The ellipsis is placed at the end of the 
>> alternatives
>> in the original base definition (which I would take to be the one in 
>> RFC 2251).
>> Each extension thereafter is appended to the end.
> 
> 
> There's a problem with adding extension markers to the CHOICE, but we 
> can get around it with the power of imagination.
> 
> RFC2251 doesn't have implicit extensibility on CHOICE - just SEQUENCE .
> Making a CHOICE extensible changes the encoded form under the PER.

Yes, though if the supposed implementation of LDAP in PER had assumed
implied extensibility everywhere (the case in X.500) then putting the
intermediateResponse after the extension marker would be backward
compatible for PER, while putting them the other way around would not be.

Putting the intermediateResponse after the extension marker is the
lesser of two evils. If nothing else, it alerts future extenders of the
protocol that the extension marker doesn't just go at the end, and that
its placement could have important consequences.

Regards,
Steven

> Even if the protocol version number were to be changed, it would be 
> inside the bindRequest, which is  inside a protocolOp.
> 
> The easy way around this problem is to just  pretend that 
> intermediateResponse and the extension marker were  in RFC2251 all the 
> time; nobody noticed because the module was declared with IMPLICIT FNORDS.
> 
> Simon
> 
> 
> 
> 
> 
> 



From owner-ietf-ldapbis@OpenLDAP.org  Thu Jun 10 17:45: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 RAA01551
	for <ldapbis-archive@lists.ietf.org>; Thu, 10 Jun 2004 17:45:16 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5ALbeR8034451;
	Thu, 10 Jun 2004 21:44:11 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.11/8.12.11/Submit) with SMTP id i5ALZa8q034302;
	Thu, 10 Jun 2004 21:35: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); Thu, 10 Jun 2004 21:35:36 +0000
Received: from sinclair.provo.novell.com (sinclair.provo.novell.com [137.65.81.169])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5ALYo4f034186;
	Thu, 10 Jun 2004 21:35:29 GMT
	(envelope-from RHARRISON@novell.com)
Received: from INET-PRV-MTA by sinclair.provo.novell.com
	with Novell_GroupWise; Thu, 10 Jun 2004 15:34:30 -0600
Message-Id: <s0c87f86.083@sinclair.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.2 Beta
Date: Thu, 10 Jun 2004 15:34:06 -0600
From: "Roger Harrison" <RHARRISON@novell.com>
To: <Kurt@OpenLDAP.org>, <h.b.furuseth@usit.uio.no>
Cc: <ietf-ldapbis@OpenLDAP.org>
Subject: Re: Applicability (Was: authmeth review notes [long])
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__PartEDCC68DE.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.

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

I've reviewed your fairly lengthy debate on this subject and have made
the following adjustments to the next draft of authmeth:
 
1. I have decided to explicitly call out mechanism names. Although they
are a bit long, the names I've decided on (for consistency with the
protocol definition) are: Anonymous Authentication Mechanism of the
Simple Bind Choice, Unauthenticated Authentication Mechanism of the
Simple Bind Choice, and Simple Authentication Mechanism of the Simple
Bind Choice.  Each has its own section with parallel language regarding
the way the mechanism is used.
 
2. I will use parallel terminology for SASL mechanisms.
 
3. I have clarified that implementations supporting the Simple
Authentication Mechanism of the Simple Bind Choice MUST be *capable* of
protecting it via TLS or other suitable data confidentiality and data
integrity services (e.g. IPSec).
 
4. Other minor modifications needed to support the main issues above.
 
I'm probably still a day or two away from submitting the next draft of
authmeth, so if you have violent disagreements to any of this stuff, you
can probably catch me in time to make changes prior to publication if
you don't delay.
 
Thanks,
 
Roger

>>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 3/9/2004 6:03:27 PM >>>
At 04:31 PM 3/9/2004, Hallvard B Furuseth wrote:
>Kurt D. Zeilenga writes:
>>At 01:23 PM 3/9/2004, Hallvard B Furuseth wrote:
>
>>>>> BTW, MUST they support unauthenticated binds?
>>>>
>>>> I believe consensus is that the unauthenticated mechanism of the
simple
>>>> method is elective, (...)
>>>
>>>Then this is wrong:
>>>
>>> LDAP server implementations MUST support the anonymous mechanism
of
>>> the simple Bind method.
>> 
>> No, that's talking about the anonymous mechanism, not the
>> unauthenticated mechanism.
>> 
>> Simple bind support three mechanisms: anonymous, unauthenticated,
>> and authenticated. While the first two both result in an anonymous
>> associations, they are different mechanisms.
>
>Oh. The problem is, the 'anonymous mechanism' of Simple Bind isn't
>defined anywhere,

It should be. We need to be distinguish this mechanism from
other simple mechanisms and well as other mechanisms whose
purpose is to establish an anonymous association.

>so it can be read eather as your definition or as
>anonymous binds. I see no reason to define it either, just to be able
>to use it here. So I suggest again:

We need to precise in this area as we have different requirements
for different mechanisms.

>>> It should be 'support anonymous binds with...' (according to
section 6),
>>> or 'anonymous authentication via the simple Bind method with no
name or
>>> password'.
>
>Also, this text from your suggestion must be fixed in the same way:
>
> LDAP implementations which support any authentication mechanism
> (other than anonymous mechanism of the simple Bind method) MUST
> support the DIGEST-MD5 (...)

I think it better to precisely define the "anonymous mechanism of
the simple Bind method".

>> I think we just need to be more precise when it comes to
>> distinguishing mechanisms from outcomes. One could say
>> that the use of SASL/ANONYMOUS mechanism is an "anonymous
>> bind". But it is a different mechanism from the simple
>> method's anonymous mechanism.
>
>My suggested texts do refer to anonymous simple bind, so they exclude
>SASL/ANONYMOUS.

Yes, but my point "anonymous simple bind" as you just used it
is ambiguous. It could mean binding with the anonymous
mechanism of the simple method or binding with the unauthenticated
mechanism of the simple method. I think the term "anonymous
simple bind" should be avoid. We should, depending on the
circumstances, either talk in terms of what kinds of associations
will/have been established, or in terms the particular
mechanisms to used in establishing the association.


>>>>>> 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.
>>>>>
>>>>> I think this paragraph can be dropped.
>>>>
>>>> I think it is important to say that other mechanisms are
elective.
>>>
>>>If you mean _all_ other mechanisms, the paragraph doesn't say that.
>>>It just says there are elective mechanisms. But I agree such a
statement
>>>would be nice. As well as a similar statement for basic TLS
features.
>> 
>> I rather not say _all_ other mechanisms, as some mechanisms have
>> very limited applicability (and some other mechanisms may actually
>> be deprecated (for very good reasons)). So, I guess, it may be best
>> not to actually say other mechanisms are elective.
>
>This should cover both needs: 'Of the mechanisms defined in this
>document, only the above mechanisms are mandatory'.

I don't believe all the mechanisms "above" are mandatory.

>> Maybe we should just s/MAY/may/ (or s/MAY/can/) here.
>
>Also an improvement over your original text.

Okay.


>> It might be appropriate
>> to note that implementors considering supporting additional
mechanisms
>> should carefully consider their applicability to LDAP and directory
>> applications they intend to support.
>
>I don't understand. Are you talking about a security consideration,
or
>something else? Why and how would they consider it?

Applicability of a mechanism certain encompasses security
considerations, but can also encompass other factors.
Note that I use the term applicability in the RFC 2026 sense.

>>>These seem inconsistent to me:
>>>
>>>>>> 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).
>>>>>
>>>>> I preferred the authmeth-10 text which only required this of
servers,
>>>>> not "implementations". It should be OK to write thin clients.
>>>>
>>>> I believe similar concerns were previously discussed. I believe
>>>> consensus supports the requirement as applying to both clients
and
>>>> servers.
>>>
>>>Above, clients that do not use DIGEST-MD5 must support it anyway.
>>>Below, clients that do not use simple/anon need not support it.
>> 
>> Because the requirements address different concerns.
>> 
>> The former requirement is to ensure that all implementations
>> share a strong authentication mechanism.
>
>If this is to satisfy some formal IETF requirement that they must
share
>such a mechanism, I'm with you.

There is a requirement for all IETF protocols to have a reasonable
strong authentication mechanism. (I forget where it is formalized.)

> Otherwise I still don't see the
>difference between clients that don't need DIGEST-MD5 and clients
that
>don't need discovery (below).

Maybe someone else can take a stab at explaining the difference
better than I.

>Also, that all implementations 'share'
>DIGEST-MD5 doesn't mean that one can bind with DIGEST-MD5 to all
servers
>supporting it, for the reasons I meantioned before about DIGEST-MD5.

Assuming you are referring to interoperability issues
(as opposed to local policy/configuration issues), please
drop me a note with a quick summary of the reasons and
pointers to past discussions.

(I have some interoperability concerns with DIGEST-MD5,
especially with layers. I intend to do a quick interop
study in this area in the next few weeks to ensure we
have (or likely will have) multiple independently developed
implementations of DIGEST-MD5 (including layers).)


>> The latter requirement is to ensure that all servers provide
>> adequate support for discovery. Clients are not generally
>> required to use discovery (or use simple/anon with discovery),
>> but servers are generally required to support discovery (if
>> so configured).
>> 
>>>>>> LDAP server implementations MUST support the anonymous mechanism
of
>>>>>> the simple Bind method.
>>>>>
>>>>> You changed this from "implementations" to "server
implementations".
>>>>> I guess I agree with that.
>>>>
>>>> This is because servers need to support various initial operation
>>>> sequences discussed in [Protocol]. However, clients need not
support
>>>> all of these. For instance, a client is free to initially request
>>>> DIGEST-MD5 authentication. Such a client need not support the
>>>> anonymous mechanism. (...)
>
>-- 
>Hallvard



--=__PartEDCC68DE.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've reviewed your fairly lengthy debate on this subject and have =
made the following adjustments to the next draft of authmeth:</DIV>
<DIV>&nbsp;</DIV>
<DIV>1. I have decided to explicitly call out mechanism names. Although =
they are a bit long, the names I've decided on (for consistency with the =
protocol definition) are: Anonymous Authentication Mechanism of the Simple =
Bind Choice, Unauthenticated Authentication Mechanism of the Simple Bind =
Choice, and Simple Authentication Mechanism of the Simple Bind Choice.&nbsp=
; Each has its own section with parallel language regarding the way the =
mechanism is used.</DIV>
<DIV>&nbsp;</DIV>
<DIV>2. I will use parallel terminology for SASL mechanisms.</DIV>
<DIV>&nbsp;</DIV>
<DIV>3. I have clarified that implementations supporting the Simple =
Authentication Mechanism of the Simple Bind Choice MUST be *capable* of =
protecting it via TLS or other suitable data confidentiality and data =
integrity services (e.g. IPSec).</DIV>
<DIV>&nbsp;</DIV>
<DIV>4. Other minor modifications needed to support the main issues =
above.</DIV>
<DIV>&nbsp;</DIV>
<DIV>I'm probably still a day or two away from submitting the next draft =
of authmeth, so if you have violent disagreements to any of this stuff, =
you can probably catch me in time to make changes prior to publication if =
you don't delay.</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;=
 3/9/2004 6:03:27 PM &gt;&gt;&gt;<BR>At 04:31 PM 3/9/2004, Hallvard B =
Furuseth wrote:<BR>&gt;Kurt D. Zeilenga writes:<BR>&gt;&gt;At 01:23 PM =
3/9/2004, Hallvard B Furuseth wrote:<BR>&gt;<BR>&gt;&gt;&gt;&gt;&gt; BTW, =
MUST they support unauthenticated binds?<BR>&gt;&gt;&gt;&gt;<BR>&gt;&gt;&gt=
;&gt; I believe consensus is that the unauthenticated mechanism of the =
simple<BR>&gt;&gt;&gt;&gt; method is elective, (...)<BR>&gt;&gt;&gt;<BR>&gt=
;&gt;&gt;Then this is wrong:<BR>&gt;&gt;&gt;<BR>&gt;&gt;&gt; LDAP server =
implementations MUST support the anonymous mechanism of<BR>&gt;&gt;&gt; =
the simple Bind method.<BR>&gt;&gt; <BR>&gt;&gt; No, that's talking about =
the anonymous mechanism, not the<BR>&gt;&gt; unauthenticated mechanism.<BR>=
&gt;&gt; <BR>&gt;&gt; Simple bind support three mechanisms: anonymous, =
unauthenticated,<BR>&gt;&gt; and authenticated. While the first two both =
result in an anonymous<BR>&gt;&gt; associations, they are different =
mechanisms.<BR>&gt;<BR>&gt;Oh. The problem is, the 'anonymous mechanism' =
of Simple Bind isn't<BR>&gt;defined anywhere,<BR><BR>It should be. We need =
to be distinguish this mechanism from<BR>other simple mechanisms and well =
as other mechanisms whose<BR>purpose is to establish an anonymous =
association.<BR><BR>&gt;so it can be read eather as your definition or =
as<BR>&gt;anonymous binds. I see no reason to define it either, just to be =
able<BR>&gt;to use it here. So I suggest again:<BR><BR>We need to precise =
in this area as we have different requirements<BR>for different mechanisms.=
<BR><BR>&gt;&gt;&gt; It should be 'support anonymous binds with...' =
(according to section 6),<BR>&gt;&gt;&gt; or 'anonymous authentication via =
the simple Bind method with no name or<BR>&gt;&gt;&gt; password'.<BR>&gt;<B=
R>&gt;Also, this text from your suggestion must be fixed in the same =
way:<BR>&gt;<BR>&gt; LDAP implementations which support any authentication =
mechanism<BR>&gt; (other than anonymous mechanism of the simple Bind =
method) MUST<BR>&gt; support the DIGEST-MD5 (...)<BR><BR>I think it better =
to precisely define the "anonymous mechanism of<BR>the simple Bind =
method".<BR><BR>&gt;&gt; I think we just need to be more precise when it =
comes to<BR>&gt;&gt; distinguishing mechanisms from outcomes. One could =
say<BR>&gt;&gt; that the use of SASL/ANONYMOUS mechanism is an "anonymous<B=
R>&gt;&gt; bind". But it is a different mechanism from the simple<BR>&gt;&g=
t; method's anonymous mechanism.<BR>&gt;<BR>&gt;My suggested texts do =
refer to anonymous simple bind, so they exclude<BR>&gt;SASL/ANONYMOUS.<BR><=
BR>Yes, but my point "anonymous simple bind" as you just used it<BR>is =
ambiguous. It could mean binding with the anonymous<BR>mechanism of the =
simple method or binding with the unauthenticated<BR>mechanism of the =
simple method. I think the term "anonymous<BR>simple bind" should be =
avoid. We should, depending on the<BR>circumstances, either talk in terms =
of what kinds of associations<BR>will/have been established, or in terms =
the particular<BR>mechanisms to used in establishing the association.<BR><B=
R><BR>&gt;&gt;&gt;&gt;&gt;&gt; Implementations MAY support additional =
authentication mechanisms of<BR>&gt;&gt;&gt;&gt;&gt;&gt; the simple and =
SASL bind methods, and/or mechanisms of other bind<BR>&gt;&gt;&gt;&gt;&gt;&=
gt; methods. Some of these mechanisms are discussed below.<BR>&gt;&gt;&gt;&=
gt;&gt;<BR>&gt;&gt;&gt;&gt;&gt; I think this paragraph can be dropped.<BR>&=
gt;&gt;&gt;&gt;<BR>&gt;&gt;&gt;&gt; I think it is important to say that =
other mechanisms are elective.<BR>&gt;&gt;&gt;<BR>&gt;&gt;&gt;If you mean =
_all_ other mechanisms, the paragraph doesn't say that.<BR>&gt;&gt;&gt;It =
just says there are elective mechanisms. But I agree such a statement<BR>&g=
t;&gt;&gt;would be nice. As well as a similar statement for basic TLS =
features.<BR>&gt;&gt; <BR>&gt;&gt; I rather not say _all_ other mechanisms,=
 as some mechanisms have<BR>&gt;&gt; very limited applicability (and some =
other mechanisms may actually<BR>&gt;&gt; be deprecated (for very good =
reasons)). So, I guess, it may be best<BR>&gt;&gt; not to actually say =
other mechanisms are elective.<BR>&gt;<BR>&gt;This should cover both =
needs: 'Of the mechanisms defined in this<BR>&gt;document, only the above =
mechanisms are mandatory'.<BR><BR>I don't believe all the mechanisms =
"above" are mandatory.<BR><BR>&gt;&gt; Maybe we should just s/MAY/may/ (or =
s/MAY/can/) here.<BR>&gt;<BR>&gt;Also an improvement over your original =
text.<BR><BR>Okay.<BR><BR><BR>&gt;&gt; It might be appropriate<BR>&gt;&gt; =
to note that implementors considering supporting additional mechanisms<BR>&=
gt;&gt; should carefully consider their applicability to LDAP and =
directory<BR>&gt;&gt; applications they intend to support.<BR>&gt;<BR>&gt;I=
 don't understand. Are you talking about a security consideration, =
or<BR>&gt;something else? Why and how would they consider it?<BR><BR>Applic=
ability of a mechanism certain encompasses security<BR>considerations, but =
can also encompass other factors.<BR>Note that I use the term applicability=
 in the RFC 2026 sense.<BR><BR>&gt;&gt;&gt;These seem inconsistent to =
me:<BR>&gt;&gt;&gt;<BR>&gt;&gt;&gt;&gt;&gt;&gt; LDAP implementations which =
support any authentication mechanism<BR>&gt;&gt;&gt;&gt;&gt;&gt; (other =
than anonymous mechanism of the simple Bind method) MUST<BR>&gt;&gt;&gt;&gt=
;&gt;&gt; support the DIGEST-MD5 [RFC2831bis] mechanism of the SASL =
Bind<BR>&gt;&gt;&gt;&gt;&gt;&gt; method (as detailed in Section X).<BR>&gt;=
&gt;&gt;&gt;&gt;<BR>&gt;&gt;&gt;&gt;&gt; I preferred the authmeth-10 text =
which only required this of servers,<BR>&gt;&gt;&gt;&gt;&gt; not "implement=
ations". It should be OK to write thin clients.<BR>&gt;&gt;&gt;&gt;<BR>&gt;=
&gt;&gt;&gt; I believe similar concerns were previously discussed. I =
believe<BR>&gt;&gt;&gt;&gt; consensus supports the requirement as applying =
to both clients and<BR>&gt;&gt;&gt;&gt; servers.<BR>&gt;&gt;&gt;<BR>&gt;&gt=
;&gt;Above, clients that do not use DIGEST-MD5 must support it anyway.<BR>&=
gt;&gt;&gt;Below, clients that do not use simple/anon need not support =
it.<BR>&gt;&gt; <BR>&gt;&gt; Because the requirements address different =
concerns.<BR>&gt;&gt; <BR>&gt;&gt; The former requirement is to ensure =
that all implementations<BR>&gt;&gt; share a strong authentication =
mechanism.<BR>&gt;<BR>&gt;If this is to satisfy some formal IETF requiremen=
t that they must share<BR>&gt;such a mechanism, I'm with you.<BR><BR>There =
is a requirement for all IETF protocols to have a reasonable<BR>strong =
authentication mechanism. (I forget where it is formalized.)<BR><BR>&gt; =
Otherwise I still don't see the<BR>&gt;difference between clients that =
don't need DIGEST-MD5 and clients that<BR>&gt;don't need discovery =
(below).<BR><BR>Maybe someone else can take a stab at explaining the =
difference<BR>better than I.<BR><BR>&gt;Also, that all implementations =
'share'<BR>&gt;DIGEST-MD5 doesn't mean that one can bind with DIGEST-MD5 =
to all servers<BR>&gt;supporting it, for the reasons I meantioned before =
about DIGEST-MD5.<BR><BR>Assuming you are referring to interoperability =
issues<BR>(as opposed to local policy/configuration issues), please<BR>drop=
 me a note with a quick summary of the reasons and<BR>pointers to past =
discussions.<BR><BR>(I have some interoperability concerns with DIGEST-MD5,=
<BR>especially with layers. I intend to do a quick interop<BR>study in =
this area in the next few weeks to ensure we<BR>have (or likely will have) =
multiple independently developed<BR>implementations of DIGEST-MD5 =
(including layers).)<BR><BR><BR>&gt;&gt; The latter requirement is to =
ensure that all servers provide<BR>&gt;&gt; adequate support for discovery.=
 Clients are not generally<BR>&gt;&gt; required to use discovery (or use =
simple/anon with discovery),<BR>&gt;&gt; but servers are generally =
required to support discovery (if<BR>&gt;&gt; so configured).<BR>&gt;&gt; =
<BR>&gt;&gt;&gt;&gt;&gt;&gt; LDAP server implementations MUST support the =
anonymous mechanism of<BR>&gt;&gt;&gt;&gt;&gt;&gt; the simple Bind =
method.<BR>&gt;&gt;&gt;&gt;&gt;<BR>&gt;&gt;&gt;&gt;&gt; You changed this =
from "implementations" to "server implementations".<BR>&gt;&gt;&gt;&gt;&gt;=
 I guess I agree with that.<BR>&gt;&gt;&gt;&gt;<BR>&gt;&gt;&gt;&gt; This =
is because servers need to support various initial operation<BR>&gt;&gt;&gt=
;&gt; sequences discussed in [Protocol]. However, clients need not =
support<BR>&gt;&gt;&gt;&gt; all of these. For instance, a client is free =
to initially request<BR>&gt;&gt;&gt;&gt; DIGEST-MD5 authentication. Such a =
client need not support the<BR>&gt;&gt;&gt;&gt; anonymous mechanism. =
(...)<BR>&gt;<BR>&gt;-- <BR>&gt;Hallvard<BR><BR></DIV></BODY></HTML>

--=__PartEDCC68DE.0__=--


From owner-ietf-ldapbis@OpenLDAP.org  Thu Jun 10 17:50: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 RAA01732
	for <ldapbis-archive@lists.ietf.org>; Thu, 10 Jun 2004 17:50:36 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5ALhFTI034752;
	Thu, 10 Jun 2004 21:49:59 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.11/8.12.11/Submit) with SMTP id i5ALcA5m034499;
	Thu, 10 Jun 2004 21:38:10 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 10 Jun 2004 21:38:10 +0000
Received: from sinclair.provo.novell.com (sinclair.provo.novell.com [137.65.81.169])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5ALc5s0034457;
	Thu, 10 Jun 2004 21:38:06 GMT
	(envelope-from RHARRISON@novell.com)
Received: from INET-PRV-MTA by sinclair.provo.novell.com
	with Novell_GroupWise; Thu, 10 Jun 2004 15:37:45 -0600
Message-Id: <s0c88049.019@sinclair.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.2 Beta
Date: Thu, 10 Jun 2004 15:37:15 -0600
From: "Roger Harrison" <RHARRISON@novell.com>
To: <Kurt@OpenLDAP.org>, <h.b.furuseth@usit.uio.no>
Cc: <ietf-ldapbis@OpenLDAP.org>
Subject: Re: active attacks (Was: Applicability (Was: authmeth
	reviewnotes [long]))
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__PartAF8E2A9B.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.

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

I've added a security consideration that states:
 
"Implementers should be aware of and understand TLS security
considerations as discussed in the TLS specification [TLS]."
 
I believe this should resolve this issue.
 
Roger

>>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 3/10/2004 4:00:40 PM >>>
At 01:55 PM 3/10/2004, Hallvard B Furuseth wrote:
>Kurt D. Zeilenga writes:
>>At 01:42 PM 3/9/2004, Hallvard B Furuseth wrote:
>>>I wrote:
>>>
>>>> DIGEST-MD5...
>>> ... is also vulnerable to active intermediary attacks ([Authmeth]
>>> section 10).
>> 
>> So is TLS (version downgrade attack), see RFC 2246.
>
>I couldn't find that, but I found 'version rollback attack'.

That's it.

>Then [Authmeth] should mention that TLS is vulnerable too.

Or simply say that implementors should be aware of and understand
TLS security considerations as discussed in RFC 2246. It does
not make much sense trying to reiterate this material, it can
be incorporated by reference. However, [Authmeth] should discuss
any LDAP-specific attacks or any LDAP-specific defenses against
these attacks.

>However, an
>unqualified statement that it is vulnerable seems wrong.

My point exactly, as applied to both TLS or DIGEST-MD5.

>As far as I can tell from RFC 2246, TLS is 'reasonably secure'
>if one uses version 3.0+ and addresses the attack properly.

Same can be said for DIGEST-MD5 and it's technical specification.

>Should be added to Section
>3.1.4 (Discovery of Resultant Security Level), which will then need
to
>
>> DIGEST-MD5 addresses the known active intermediate vulnerability
>> (the layer downgrade attack) of the authentication exchange by
>> stating that both peers must ensure that adequate protections have
>> been established before transferring any application-protocol data.
>> Likewise, [Authmeth] must say this for its use of SASL as LDAP's
>> SASL mechanism discovery facility is also subject to downgrade
>> attacks (unless protected by other means).
>
>Um... that "also" confuses me. Are you talking about two different
>attacks on DIGEST-MD5, or is it one attack and DIGEST-MD5 is secure
>(as far as we know) if one addresses this attack?

There is an attack on SASL mechanism discovery (mechanism downgrade)
and an attack on DIGEST-MD5 mechanism (layer downgrade) and, these
attacks can be used together in some interesting ways. Both
attacks (and combined attacks) are addressed by having each peer
ensure the resultant security level meets their minimum
requirements before continuing. (It is also wise to avoid
entering into an exchange which cannot possible result in
acceptable security level.)

I believe all known attacks upon DIGEST-MD5 are discussed in
draft-ietf-sasl-rfc2831bis. If not, please holler on the SASL
WG list.

Kurt 



--=__PartAF8E2A9B.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've added a security consideration that states:</DIV>
<DIV>&nbsp;</DIV>
<DIV>"Implementers should be aware of and understand TLS security =
considerations as discussed in the TLS specification [TLS]."</DIV>
<DIV>&nbsp;</DIV>
<DIV>I believe this should resolve this issue.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Roger<BR><BR>&gt;&gt;&gt; "Kurt D. Zeilenga" &lt;Kurt@OpenLDAP.org&gt;=
 3/10/2004 4:00:40 PM &gt;&gt;&gt;<BR>At 01:55 PM 3/10/2004, Hallvard B =
Furuseth wrote:<BR>&gt;Kurt D. Zeilenga writes:<BR>&gt;&gt;At 01:42 PM =
3/9/2004, Hallvard B Furuseth wrote:<BR>&gt;&gt;&gt;I wrote:<BR>&gt;&gt;&gt=
;<BR>&gt;&gt;&gt;&gt; DIGEST-MD5...<BR>&gt;&gt;&gt; ... is also vulnerable =
to active intermediary attacks ([Authmeth]<BR>&gt;&gt;&gt; section =
10).<BR>&gt;&gt; <BR>&gt;&gt; So is TLS (version downgrade attack), see =
RFC 2246.<BR>&gt;<BR>&gt;I couldn't find that, but I found 'version =
rollback attack'.<BR><BR>That's it.<BR><BR>&gt;Then [Authmeth] should =
mention that TLS is vulnerable too.<BR><BR>Or simply say that implementors =
should be aware of and understand<BR>TLS security considerations as =
discussed in RFC 2246. It does<BR>not make much sense trying to reiterate =
this material, it can<BR>be incorporated by reference. However, [Authmeth] =
should discuss<BR>any LDAP-specific attacks or any LDAP-specific defenses =
against<BR>these attacks.<BR><BR>&gt;However, an<BR>&gt;unqualified =
statement that it is vulnerable seems wrong.<BR><BR>My point exactly, as =
applied to both TLS or DIGEST-MD5.<BR><BR>&gt;As far as I can tell from =
RFC 2246, TLS is 'reasonably secure'<BR>&gt;if one uses version 3.0+ and =
addresses the attack properly.<BR><BR>Same can be said for DIGEST-MD5 and =
it's technical specification.<BR><BR>&gt;Should be added to Section<BR>&gt;=
3.1.4 (Discovery of Resultant Security Level), which will then need =
to<BR>&gt;<BR>&gt;&gt; DIGEST-MD5 addresses the known active intermediate =
vulnerability<BR>&gt;&gt; (the layer downgrade attack) of the authenticatio=
n exchange by<BR>&gt;&gt; stating that both peers must ensure that =
adequate protections have<BR>&gt;&gt; been established before transferring =
any application-protocol data.<BR>&gt;&gt; Likewise, [Authmeth] must say =
this for its use of SASL as LDAP's<BR>&gt;&gt; SASL mechanism discovery =
facility is also subject to downgrade<BR>&gt;&gt; attacks (unless =
protected by other means).<BR>&gt;<BR>&gt;Um... that "also" confuses me. =
Are you talking about two different<BR>&gt;attacks on DIGEST-MD5, or is it =
one attack and DIGEST-MD5 is secure<BR>&gt;(as far as we know) if one =
addresses this attack?<BR><BR>There is an attack on SASL mechanism =
discovery (mechanism downgrade)<BR>and an attack on DIGEST-MD5 mechanism =
(layer downgrade) and, these<BR>attacks can be used together in some =
interesting ways. Both<BR>attacks (and combined attacks) are addressed by =
having each peer<BR>ensure the resultant security level meets their =
minimum<BR>requirements before continuing. (It is also wise to avoid<BR>ent=
ering into an exchange which cannot possible result in<BR>acceptable =
security level.)<BR><BR>I believe all known attacks upon DIGEST-MD5 are =
discussed in<BR>draft-ietf-sasl-rfc2831bis. If not, please holler on the =
SASL<BR>WG list.<BR><BR>Kurt <BR><BR></DIV></BODY></HTML>

--=__PartAF8E2A9B.0__=--


From owner-ietf-ldapbis@OpenLDAP.org  Fri Jun 11 00:04: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 AAA15088
	for <ldapbis-archive@lists.ietf.org>; Fri, 11 Jun 2004 00:04:12 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5B41eDV049429;
	Fri, 11 Jun 2004 04:01:59 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.11/8.12.11/Submit) with SMTP id i5B3ukAK049259;
	Fri, 11 Jun 2004 03:56: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); Fri, 11 Jun 2004 03:56:46 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5B3ufh8049249
	for <ietf-ldapbis@OpenLDAP.org>; Fri, 11 Jun 2004 03:56:42 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.11) with ESMTP id i5B3ufMC096239
	for <ietf-ldapbis@OpenLDAP.org>; Fri, 11 Jun 2004 03:56:41 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.1.1.0.20040610203514.048ea2a0@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Thu, 10 Jun 2004 20:56:54 -0700
To: ietf-ldapbis@OpenLDAP.org
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: userPassword
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>

[Schema] describes userPassword:
   The userPassword attribute type contains character strings that are
   known only to the user and the system to which the user has access.  
   Each string is one value of this multi-valued attribute. 

As previously discussed, userPassword is not necessarily character
data, s/character/octet/ to fix.

I also note that "attribute type" should be replaced with
"attribute" as your describing attribute values.



From owner-ietf-ldapbis@OpenLDAP.org  Fri Jun 11 05:09: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 FAA08252
	for <ldapbis-archive@lists.ietf.org>; Fri, 11 Jun 2004 05:09:29 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5B97UIF066361;
	Fri, 11 Jun 2004 09:07:53 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.11/8.12.11/Submit) with SMTP id i5B96FKL066339;
	Fri, 11 Jun 2004 09:06: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); Fri, 11 Jun 2004 09:06:15 +0000
Received: from pat.uio.no (IDENT:7411@pat.uio.no [129.240.130.16])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5B96AmB066305;
	Fri, 11 Jun 2004 09:06:12 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.30)
	id 1BYhzD-0000Dq-LB; Fri, 11 Jun 2004 11:06:07 +0200
Received: from bombur.uio.no ([129.240.186.42])
	by smtp.uio.no with esmtp (Exim 4.34)
	id 1BYhz7-0007ci-9k; Fri, 11 Jun 2004 11:06:01 +0200
Received: from hbf by bombur.uio.no with local (Exim 2.12 #7)
	id 1BYhz6-0003rp-00; Fri, 11 Jun 2004 11:06:00 +0200
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Message-Id: <HBF.20040611boi@bombur.uio.no>
To: Roger Harrison <RHARRISON@novell.com>
Cc: Kurt@OpenLDAP.org, ietf-ldapbis@OpenLDAP.org
Subject: Re: Applicability (Was: authmeth review notes [long])
In-Reply-To: <s0c87f86.083@sinclair.provo.novell.com>
References: <s0c87f86.083@sinclair.provo.novell.com>
X-Mailer: VM 6.37 under Emacs 19.34.1
Date: Fri, 11 Jun 2004 11:06:00 +0200
X-MailScanner-Information: This message has been scanned for viruses/spam. Contact postmaster@uio.no if you have questions about this scanning
X-UiO-MailScanner: No virus found
X-UiO-Spam-info: not spam, SpamAssassin (score=-5, required 12,
	UIO_MAIL_IS_INTERNAL -5.00)
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.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 Harrison writes:
> I've reviewed your fairly lengthy debate on this subject and have made
> the following adjustments to the next draft of authmeth:
>
> 1. I have decided to explicitly call out mechanism names. Although they
> are a bit long, the names I've decided on (for consistency with the
> protocol definition) are: Anonymous Authentication Mechanism of the
> Simple Bind Choice, Unauthenticated Authentication Mechanism of the
> Simple Bind Choice, and Simple Authentication Mechanism of the Simple
> Bind Choice.  Each has its own section with parallel language regarding
> the way the mechanism is used.

Whoops, I'd forgotten that debate.  Decided to sleep on some attempted
improvements which I wasn't satisfied with, and 'slept' too long.

I'm undecided about whether expanding the Bind terms is better than
defining shorter terms.  Fewer definitions to keep track of make it
easier to read the standard, but OTOH the above terms are too long for
everyday use, so people are going to abbreviate them anyway.  With
expanded names as above, preferably the mechanism names should at least
lend themselves to abbreviations that remain reasonably unambiguous.  If
I could just come up with an alternative for 'anonymous' bind which
can't be misunderstood to include 'unauthenticated':-( 'Unnamed' or
'nameless' are my best so far, but sound a bit strange to me.

Could the above terms at least be shortened a little, like
'xxx Authentication Mechanism of the Simple Bind Choice'
-> 'xxx mechanism of Simple Bind'?


Anyway: I dislike the 'anonymous' vs. 'unauthenticated' terminology,
with or without the above verbosity.  The two words keep getting
confused.  With good reason:

The 'unauthenticated' mechanism, spelled out or not, produces an
'anonymous' association.  OTOH, an LDAP 'anonymous' (neither DN nor
password) bind or 'anonymous' association can in non-LDAP terms be said
to be 'unauthenticated'.

Indeed, when I googled for 'unauthenticated bind', I found just as many
texts which meant one of the variants of 'anonymous'.  And a lot of
texts where I couldn't tell if they got it right or not.
And of course, some 'anonymous' binds out there mean both variants,
while others mean neither DN nor password.


It would be preferable if the binds that produce 'anonymous'
associations were the same binds that are called something with
'anonymous'.  However, that fits neither 'unauthenticated' simple binds
nor the SASL/ANONYMOUS mechanism.  So I think 'anonymous associations'
should be renamed, but I can't come up with a suggestion.  Still, it's a
new term, and thus should be easier to kill off than the established
Bind terms.

'Unauthenticated' binds could be renamed to e.g. 'informative' or
'informational' simple bind (possible expanded as Roger does above),
with a note that it was previously called 'unauthenticated' and this
caused confusion.

-- 
Hallvard


From owner-ietf-ldapbis@OpenLDAP.org  Fri Jun 11 10:42:34 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 KAA05375
	for <ldapbis-archive@lists.ietf.org>; Fri, 11 Jun 2004 10:42:34 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5BEbJSM084279;
	Fri, 11 Jun 2004 14:41:30 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.11/8.12.11/Submit) with SMTP id i5BEYOgf083558;
	Fri, 11 Jun 2004 14:34: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); Fri, 11 Jun 2004 14:34:24 +0000
Received: from pat.uio.no (IDENT:7411@pat.uio.no [129.240.130.16])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5BEYLac083539
	for <ietf-ldapbis@openldap.org>; Fri, 11 Jun 2004 14:34:23 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.30)
	id 1BYn6o-00025s-9D
	for ietf-ldapbis@openldap.org; Fri, 11 Jun 2004 16:34:18 +0200
Received: from bombur.uio.no ([129.240.186.42])
	by smtp.uio.no with esmtp (Exim 4.34)
	id 1BYn6m-0001Rr-69; Fri, 11 Jun 2004 16:34:16 +0200
Received: from hbf by bombur.uio.no with local (Exim 2.12 #7)
	id 1BYn6l-0004hj-00; Fri, 11 Jun 2004 16:34:15 +0200
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Message-Id: <HBF.20040611tu4g@bombur.uio.no>
To: ietf-ldapbis@OpenLDAP.org
Subject: Re: protocol: "outstanding" operations
In-Reply-To: <6.0.1.1.0.20040519071448.02ca8108@127.0.0.1>
References: <HBF.20040507tkuc@bombur.uio.no>
	<HBF.20040519d2zz@bombur.uio.no>
	<6.0.1.1.0.20040519071448.02ca8108@127.0.0.1>
X-Mailer: VM 6.37 under Emacs 19.34.1
Date: Fri, 11 Jun 2004 16:34:15 +0200
X-MailScanner-Information: This message has been scanned for viruses/spam. Contact postmaster@uio.no if you have questions about this scanning
X-UiO-MailScanner: No virus found
X-UiO-Spam-info: not spam, SpamAssassin (score=-5, required 12,
	UIO_MAIL_IS_INTERNAL -5.00)
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

Well, Jim is back, I believe.  I'll begin small:-)

Roger, note that Authmeth has two 'outstanding's too.


Looking a bit closer at the texts, I think only the 'outstanding' in
[Protocol] 4.1.1.1 (Message ID) is not self-explanatory.
Here is a possible replacement text:

   A client MUST NOT reuse a previous request's message ID in the
   same LDAP exchange until it knows that the server has completed
   or successfully abandoned the operation.

Or maybe s/successfully abandoned/discarded/.


If anyone feels like replacing the others, here are some suggestions.
And two non-suggestions for Abandon; I like 'outstanding' better than
the replacement texts I could think of:

4.2.1 (Processing of the Bind Request):

s/outstanding/previous/.

4.3 (Unbind Operation):

s/outstanding/remaining previous/.

4.4.1 (Notice of Disconnection):

s/outstanding/remaining/.

4.11 (Abandon Operation):

Not s/outstanding/previous/ (server side), that implies operations that
have responded too.  Not 'uncompleted previous', that looks a bit like
the server must at least have started to process the operation.

4.14.3 (Removal of the TLS Layer):

s/outstanding/remaining previous/?

5.1 (Operation and LDAP exchange Relationship):

s/outstanding/remaining/ (server side and client side).

A.2 (Result Codes#operationsError):

s/while there are other operations outstanding/
  before all previous operations have completed/ ?


[Authmeth] 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 previous requests remain for the server to process on
         the same LDAP exchange.

>   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 

s/outstanding LDAP operations/remaining previous requests/.

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


Kurt D. Zeilenga writes:
>At 04:13 AM 5/19/2004, Hallvard B Furuseth wrote:
>>I wrote:
>>> A recent poster to the OpenLDAP-software list had not understood what an
>>> outstanding operation is.  Maybe [protocol] should define it at the time
>>> of first use.  Something like this:
>>>   
>>>   at the server: a request which is being or waiting to be processed.
>>>   at the client: as above,
>>
>>including requests sent by the client which the server has not yet
>>received,
>>
>>>   , or an operation for which the server has
>>>   sent a response which the client has not yet received.
>>
>>It gets a bit cumbersome, I'm afraid.
> 
> That's my fear.  Are such clarifications going cause more
> confusion? 
> 
>>Improvements are welcome:-)
> 
> My suggestion would be avoiding the need to define the
> term.  Instead, I would try to reword any sentence which
> used the phrase "outstanding operation" (or "outstanding
> request") to be reasonable clear without having to
> rely on separately stated terminology definitions.

-- 
Hallvard


From owner-ietf-ldapbis@OpenLDAP.org  Fri Jun 11 11:08: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 LAA09913
	for <ldapbis-archive@lists.ietf.org>; Fri, 11 Jun 2004 11:08:24 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5BF7Ojt088018;
	Fri, 11 Jun 2004 15:07:27 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.11/8.12.11/Submit) with SMTP id i5BF61x6087955;
	Fri, 11 Jun 2004 15:06:01 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Fri, 11 Jun 2004 15:06:01 +0000
Received: from smtp-mclean.mitre.org (smtp-mclean-x.mitre.org [192.80.55.71])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5BF5vOP087891;
	Fri, 11 Jun 2004 15:05:58 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 i5BFCGc21562;
	Fri, 11 Jun 2004 11:12:16 -0400
Received: from MAILHUB2 (mailhub2.mitre.org [129.83.221.18])
	by smtp-mclean.mitre.org (8.11.6/8.11.6) with ESMTP id i5BFCFH21523;
	Fri, 11 Jun 2004 11:12:15 -0400
Received: from mm108631-pc.mitre.org (128.29.3.71) by mailhub2.mitre.org with SMTP
        id 3179075; Fri, 11 Jun 2004 11:05:36 -0400
From: "Kathy Dally" <kdally@mitre.org>
To: "'Kurt D. Zeilenga'" <Kurt@OpenLDAP.org>, <ietf-ldapbis@OpenLDAP.org>
Subject: RE: userPassword
Date: Fri, 11 Jun 2004 11:05:43 -0400
Organization: The MITRE Corporation
Message-ID: <000001c44fc5$914f9540$47031d80@MITRE.ORG>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.5709
In-reply-to: <6.0.1.1.0.20040610203514.048ea2a0@127.0.0.1>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by boole.openldap.org id i5BF5xOP087898
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.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

Done!

Kathy

-----Original Message-----
From: owner-ietf-ldapbis@OpenLDAP.org
[mailto:owner-ietf-ldapbis@OpenLDAP.org] On Behalf
Of Kurt D. Zeilenga
Sent: Thursday, June 10, 2004 11:57 PM
To: ietf-ldapbis@OpenLDAP.org
Subject: userPassword


[Schema] describes userPassword:
   The userPassword attribute type contains
character strings that are
   known only to the user and the system to which
the user has access.  
   Each string is one value of this multi-valued
attribute. 

As previously discussed, userPassword is not
necessarily character
data, s/character/octet/ to fix.

I also note that "attribute type" should be
replaced with
"attribute" as your describing attribute values.






From owner-ietf-ldapbis@OpenLDAP.org  Fri Jun 11 11:08:25 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 LAA09914
	for <ldapbis-archive@lists.ietf.org>; Fri, 11 Jun 2004 11:08:24 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5BF7Ojv088018;
	Fri, 11 Jun 2004 15:07:27 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.11/8.12.11/Submit) with SMTP id i5BF5uH1087886;
	Fri, 11 Jun 2004 15:05: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, 11 Jun 2004 15:05:56 +0000
Received: from sinclair.provo.novell.com (sinclair.provo.novell.com [137.65.81.169])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5BF5oBF087813
	for <ietf-ldapbis@OpenLDAP.org>; Fri, 11 Jun 2004 15:05:54 GMT
	(envelope-from RHARRISON@novell.com)
Received: from INET-PRV-MTA by sinclair.provo.novell.com
	with Novell_GroupWise; Fri, 11 Jun 2004 09:05:30 -0600
Message-Id: <s0c975da.030@sinclair.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.2 Beta
Date: Fri, 11 Jun 2004 09:05:12 -0600
From: "Roger Harrison" <RHARRISON@novell.com>
To: <ietf-ldapbis@OpenLDAP.org>, <h.b.furuseth@usit.uio.no>
Subject: Re: protocol: "outstanding" operations
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__Part13329738.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.

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

Apparently, I had already fixed one of the uses of "outstanding" in
[Authmeth] because I can find only one in my current draft. I've now
resolved it.
 
Roger

>>> Hallvard B Furuseth <h.b.furuseth@usit.uio.no> 6/11/2004 8:34:15 AM
>>>
Well, Jim is back, I believe. I'll begin small:-)

Roger, note that Authmeth has two 'outstanding's too.


Looking a bit closer at the texts, I think only the 'outstanding' in
[Protocol] 4.1.1.1 (Message ID) is not self-explanatory.
Here is a possible replacement text:

A client MUST NOT reuse a previous request's message ID in the
same LDAP exchange until it knows that the server has completed
or successfully abandoned the operation.

Or maybe s/successfully abandoned/discarded/.


If anyone feels like replacing the others, here are some suggestions.
And two non-suggestions for Abandon; I like 'outstanding' better than
the replacement texts I could think of:

4.2.1 (Processing of the Bind Request):

s/outstanding/previous/.

4.3 (Unbind Operation):

s/outstanding/remaining previous/.

4.4.1 (Notice of Disconnection):

s/outstanding/remaining/.

4.11 (Abandon Operation):

Not s/outstanding/previous/ (server side), that implies operations
that
have responded too. Not 'uncompleted previous', that looks a bit like
the server must at least have started to process the operation.

4.14.3 (Removal of the TLS Layer):

s/outstanding/remaining previous/?

5.1 (Operation and LDAP exchange Relationship):

s/outstanding/remaining/ (server side and client side).

A.2 (Result Codes#operationsError):

s/while there are other operations outstanding/
before all previous operations have completed/ ?


[Authmeth] 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 previous requests remain for the server to process on
the same LDAP exchange.

> 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 

s/outstanding LDAP operations/remaining previous requests/.

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


Kurt D. Zeilenga writes:
>At 04:13 AM 5/19/2004, Hallvard B Furuseth wrote:
>>I wrote:
>>> A recent poster to the OpenLDAP-software list had not understood
what an
>>> outstanding operation is. Maybe [protocol] should define it at the
time
>>> of first use. Something like this:
>>> 
>>> at the server: a request which is being or waiting to be
processed.
>>> at the client: as above,
>>
>>including requests sent by the client which the server has not yet
>>received,
>>
>>> , or an operation for which the server has
>>> sent a response which the client has not yet received.
>>
>>It gets a bit cumbersome, I'm afraid.
> 
> That's my fear. Are such clarifications going cause more
> confusion? 
> 
>>Improvements are welcome:-)
> 
> My suggestion would be avoiding the need to define the
> term. Instead, I would try to reword any sentence which
> used the phrase "outstanding operation" (or "outstanding
> request") to be reasonable clear without having to
> rely on separately stated terminology definitions.

-- 
Hallvard


--=__Part13329738.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>Apparently, I had already fixed one of the uses of "outstanding" in =
[Authmeth] because I can find only one in my current draft. I've now =
resolved it.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Roger<BR><BR>&gt;&gt;&gt; Hallvard B Furuseth &lt;h.b.furuseth@usit.ui=
o.no&gt; 6/11/2004 8:34:15 AM &gt;&gt;&gt;<BR>Well, Jim is back, I =
believe. I'll begin small:-)<BR><BR>Roger, note that Authmeth has two =
'outstanding's too.<BR><BR><BR>Looking a bit closer at the texts, I think =
only the 'outstanding' in<BR>[Protocol] 4.1.1.1 (Message ID) is not =
self-explanatory.<BR>Here is a possible replacement text:<BR><BR>A client =
MUST NOT reuse a previous request's message ID in the<BR>same LDAP =
exchange until it knows that the server has completed<BR>or successfully =
abandoned the operation.<BR><BR>Or maybe s/successfully abandoned/discarded=
/.<BR><BR><BR>If anyone feels like replacing the others, here are some =
suggestions.<BR>And two non-suggestions for Abandon; I like 'outstanding' =
better than<BR>the replacement texts I could think of:<BR><BR>4.2.1 =
(Processing of the Bind Request):<BR><BR>s/outstanding/previous/.<BR><BR>4.=
3 (Unbind Operation):<BR><BR>s/outstanding/remaining previous/.<BR><BR>4.4.=
1 (Notice of Disconnection):<BR><BR>s/outstanding/remaining/.<BR><BR>4.11 =
(Abandon Operation):<BR><BR>Not s/outstanding/previous/ (server side), =
that implies operations that<BR>have responded too. Not 'uncompleted =
previous', that looks a bit like<BR>the server must at least have started =
to process the operation.<BR><BR>4.14.3 (Removal of the TLS Layer):<BR><BR>=
s/outstanding/remaining previous/?<BR><BR>5.1 (Operation and LDAP exchange =
Relationship):<BR><BR>s/outstanding/remaining/ (server side and client =
side).<BR><BR>A.2 (Result Codes#operationsError):<BR><BR>s/while there are =
other operations outstanding/<BR>before all previous operations have =
completed/ ?<BR><BR><BR>[Authmeth] 3.1.1 (Start TLS Request):<BR><BR>&gt; =
A client may send the Start TLS extended request at any time after =
<BR>&gt; establishing an LDAP connection, except: <BR>&gt; (...)<BR><BR>- =
when previous requests remain for the server to process on<BR>the same =
LDAP exchange.<BR><BR>&gt; The result of violating any of these requirement=
s is a resultCode of<BR>&gt; operationsError, as described in [Protocol] =
section 4.13.2.2. Client<BR>&gt; implementers should note that it is =
possible to receive a resultCode<BR>&gt; of success for a Start TLS =
operation that is sent on a connection<BR>&gt; with outstanding LDAP =
operations if the server has sufficient time <BR><BR>s/outstanding LDAP =
operations/remaining previous requests/.<BR><BR>&gt; to process them prior =
to its receiving the Start TLS request. <BR>&gt; Implementors of clients =
should ensure that they do not inadvertently <BR>&gt; depend upon this =
race condition. <BR><BR><BR>Kurt D. Zeilenga writes:<BR>&gt;At 04:13 AM =
5/19/2004, Hallvard B Furuseth wrote:<BR>&gt;&gt;I wrote:<BR>&gt;&gt;&gt; =
A recent poster to the OpenLDAP-software list had not understood what =
an<BR>&gt;&gt;&gt; outstanding operation is. Maybe [protocol] should =
define it at the time<BR>&gt;&gt;&gt; of first use. Something like =
this:<BR>&gt;&gt;&gt; <BR>&gt;&gt;&gt; at the server: a request which is =
being or waiting to be processed.<BR>&gt;&gt;&gt; at the client: as =
above,<BR>&gt;&gt;<BR>&gt;&gt;including requests sent by the client which =
the server has not yet<BR>&gt;&gt;received,<BR>&gt;&gt;<BR>&gt;&gt;&gt; , =
or an operation for which the server has<BR>&gt;&gt;&gt; sent a response =
which the client has not yet received.<BR>&gt;&gt;<BR>&gt;&gt;It gets a =
bit cumbersome, I'm afraid.<BR>&gt; <BR>&gt; That's my fear. Are such =
clarifications going cause more<BR>&gt; confusion? <BR>&gt; <BR>&gt;&gt;Imp=
rovements are welcome:-)<BR>&gt; <BR>&gt; My suggestion would be avoiding =
the need to define the<BR>&gt; term. Instead, I would try to reword any =
sentence which<BR>&gt; used the phrase "outstanding operation" (or =
"outstanding<BR>&gt; request") to be reasonable clear without having =
to<BR>&gt; rely on separately stated terminology definitions.<BR><BR>-- =
<BR>Hallvard<BR></DIV></BODY></HTML>

--=__Part13329738.0__=--


From owner-ietf-ldapbis@OpenLDAP.org  Fri Jun 11 11:39: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 LAA11917
	for <ldapbis-archive@lists.ietf.org>; Fri, 11 Jun 2004 11:39:19 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5BFWFFq089344;
	Fri, 11 Jun 2004 15:38:10 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.11/8.12.11/Submit) with SMTP id i5BFQbo7088964;
	Fri, 11 Jun 2004 15:26: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); Fri, 11 Jun 2004 15:26:37 +0000
Received: from sinclair.provo.novell.com (sinclair.provo.novell.com [137.65.81.169])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5BFQYmb088927
	for <ietf-ldapbis@OpenLDAP.org>; Fri, 11 Jun 2004 15:26:35 GMT
	(envelope-from jimse@novell.com)
Received: from INET-PRV-MTA by sinclair.provo.novell.com
	with Novell_GroupWise; Fri, 11 Jun 2004 09:26:14 -0600
Message-Id: <s0c97ab6.095@sinclair.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.2 Beta
Date: Fri, 11 Jun 2004 09:25:51 -0600
From: "Jim Sermersheim" <jimse@novell.com>
To: <ietf-ldapbis@OpenLDAP.org>, <h.b.furuseth@usit.uio.no>
Subject: Re: protocol: "outstanding" operations
Mime-Version: 1.0
Content-Type: text/plain; charset=Windows-1256
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by boole.openldap.org id i5BFQZmb088953
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 8bit

I think I prefer uncompleted or unfinished over remaining previous.

outstanding catch by the way * har har. 

>>> Hallvard B Furuseth <h.b.furuseth@usit.uio.no> 6/11/04 8:34:15 AM >>>
Well, Jim is back, I believe.  I'll begin small:-)

Roger, note that Authmeth has two 'outstanding's too.


Looking a bit closer at the texts, I think only the 'outstanding' in
[Protocol] 4.1.1.1 (Message ID) is not self-explanatory.
Here is a possible replacement text:

   A client MUST NOT reuse a previous request's message ID in the
   same LDAP exchange until it knows that the server has completed
   or successfully abandoned the operation.

Or maybe s/successfully abandoned/discarded/.


If anyone feels like replacing the others, here are some suggestions.
And two non-suggestions for Abandon; I like 'outstanding' better than
the replacement texts I could think of:

4.2.1 (Processing of the Bind Request):

s/outstanding/previous/.

4.3 (Unbind Operation):

s/outstanding/remaining previous/.

4.4.1 (Notice of Disconnection):

s/outstanding/remaining/.

4.11 (Abandon Operation):

Not s/outstanding/previous/ (server side), that implies operations that
have responded too.  Not 'uncompleted previous', that looks a bit like
the server must at least have started to process the operation.

4.14.3 (Removal of the TLS Layer):

s/outstanding/remaining previous/?

5.1 (Operation and LDAP exchange Relationship):

s/outstanding/remaining/ (server side and client side).

A.2 (Result Codes#operationsError):

s/while there are other operations outstanding/
  before all previous operations have completed/ ?


[Authmeth] 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 previous requests remain for the server to process on
         the same LDAP exchange.

>   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 

s/outstanding LDAP operations/remaining previous requests/.

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


Kurt D. Zeilenga writes:
>At 04:13 AM 5/19/2004, Hallvard B Furuseth wrote:
>>I wrote:
>>> A recent poster to the OpenLDAP-software list had not understood what an
>>> outstanding operation is.  Maybe [protocol] should define it at the time
>>> of first use.  Something like this:
>>>   
>>>   at the server: a request which is being or waiting to be processed.
>>>   at the client: as above,
>>
>>including requests sent by the client which the server has not yet
>>received,
>>
>>>   , or an operation for which the server has
>>>   sent a response which the client has not yet received.
>>
>>It gets a bit cumbersome, I'm afraid.
> 
> That's my fear.  Are such clarifications going cause more
> confusion? 
> 
>>Improvements are welcome:-)
> 
> My suggestion would be avoiding the need to define the
> term.  Instead, I would try to reword any sentence which
> used the phrase "outstanding operation" (or "outstanding
> request") to be reasonable clear without having to
> rely on separately stated terminology definitions.

-- 
Hallvard




From owner-ietf-ldapbis@OpenLDAP.org  Sat Jun 19 21:35: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 VAA18350
	for <ldapbis-archive@lists.ietf.org>; Sat, 19 Jun 2004 21:35:21 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5K1WZ3e005706;
	Sun, 20 Jun 2004 01:33:31 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.11/8.12.11/Submit) with SMTP id i5K1UjY1005662;
	Sun, 20 Jun 2004 01:30: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); Sun, 20 Jun 2004 01:30:45 +0000
Received: from ghidora.unity.ncsu.edu (ghidora.unity.ncsu.edu [152.1.4.40])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5K1TfIj005618
	for <ietf-ldapbis@openldap.org>; Sun, 20 Jun 2004 01:30:44 GMT
	(envelope-from daniel@unity.ncsu.edu)
Received: (from daniel@localhost)
	by ghidora.unity.ncsu.edu (8.11.7p1+Sun/8.10.2) id i5K1Td412456;
	Sat, 19 Jun 2004 21:29:39 -0400 (EDT)
Date: Sat, 19 Jun 2004 21:29:39 -0400 (EDT)
From: Daniel Henninger <daniel@unity.ncsu.edu>
Reply-To: daniel@ncsu.edu
To: ietf-ldapbis@OpenLDAP.org
Subject: ListMatch Clarification
Message-ID: <Pine.GSO.4.58.0406192125120.12430@ghidora.unity.ncsu.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-ID: ietf-ldapbis mailing list <ietf-ldapbis@OpenLDAP.org>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

Folk,

I'm looking into implementing the ListMatch style matches and submitting a
patch.  I am having some trouble understanding part of the specification.
I understand that $ is effectively a newline.  The draft seems to indicate
that you ignore $ (ie, pull it out) and escape (\).  That said, the part
I'm not clear on is the actual search string.  Does the $ get handled in
the search string as well?  For example, lets say I want to find someone
on Foo Street, in Raleigh, NC.  Would I do a search along the lines of:
postalAddress=*Foo Street $ Raleigh, NC*
or
postalAddress=*Foo Street * Raleigh, NC*
or both?

Also is there supposed to be a space on both sides of the $, similar to
how $'s are used in schema, or would there be no spaces?

Daniel

-- 
/\\\----------------------------------------------------------------------///\
\ \\\      Daniel Henninger           http://www.vorpalcloud.org/        /// /
 \_\\\      North Carolina State University - Systems Programmer        ///_/
    \\\                   Information Technology <IT>                  ///
     """--------------------------------------------------------------"""


From owner-ietf-ldapbis@OpenLDAP.org  Sun Jun 20 22:11: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 WAA15131
	for <ldapbis-archive@lists.ietf.org>; Sun, 20 Jun 2004 22:11:48 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5L28cI1055309;
	Mon, 21 Jun 2004 02:09:39 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.11/8.12.11/Submit) with SMTP id i5L2385d055260;
	Mon, 21 Jun 2004 02:03:08 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 21 Jun 2004 02:03:08 +0000
Received: from adacel.com (gunsmoke.adacel.com.au [210.11.130.7])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5L231e9055246
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 21 Jun 2004 02:03:03 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.6.7)
	id <B00027d802>; Mon, 21 Jun 2004 12:01:03 +1000
Received: (qmail 22586 invoked from network); 21 Jun 2004 02:02:33 -0000
Received: from unknown (HELO adacel.com.au) (10.32.24.165)
  by nexus.adacel.com with SMTP; 21 Jun 2004 02:02:33 -0000
Message-ID: <40D641B7.7020108@adacel.com.au>
Date: Mon, 21 Jun 2004 12:02:31 +1000
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: daniel@ncsu.edu
CC: ietf-ldapbis@OpenLDAP.org
Subject: Re: ListMatch Clarification
References: <Pine.GSO.4.58.0406192125120.12430@ghidora.unity.ncsu.edu>
In-Reply-To: <Pine.GSO.4.58.0406192125120.12430@ghidora.unity.ncsu.edu>
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-ID: ietf-ldapbis mailing list <ietf-ldapbis@OpenLDAP.org>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


Daniel,

Daniel Henninger wrote:
> Folk,
> 
> I'm looking into implementing the ListMatch style matches and submitting a
> patch.  I am having some trouble understanding part of the specification.
> I understand that $ is effectively a newline.  The draft seems to indicate
> that you ignore $ (ie, pull it out) and escape (\).  That said, the part
> I'm not clear on is the actual search string.  Does the $ get handled in
> the search string as well?  For example, lets say I want to find someone
> on Foo Street, in Raleigh, NC.  Would I do a search along the lines of:
> postalAddress=*Foo Street $ Raleigh, NC*
> or
> postalAddress=*Foo Street * Raleigh, NC*
> or both?

The second assertion value is the one that applies. The assertion syntax for
caseIgnoreListSubstringsMatch is Substring Assertion, for which $ is an
ordinary character (only * and \ are special). The first assertion value
would only match if there were an escaped $ (i.e. not a line separator)
in a line of the address (where only $ and \ are special).

The unescaped $ line separators in a Postal Address value are an artefact
of the LDAP-specific encoding and are not matchable character data.

> 
> Also is there supposed to be a space on both sides of the $, similar to
> how $'s are used in schema, or would there be no spaces?

There is no requirement either way, and for caseIgnoreListMatch it makes no
difference since each line of the address is matched according to
caseIgnoreMatch which ignores leading and trailing space on each line.
It makes no difference for caseIgnoreListSubstringsMatch as well
because of the interaction of stringprep and the requirement that
a substring in an assertion value for caseIgnoreListSubstringsMatch
does not match characters across multiple lines.

Regards,
Steven

> 
> Daniel
> 



From owner-ietf-ldapbis@OpenLDAP.org  Mon Jun 21 07: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 HAA04400
	for <ldapbis-archive@lists.ietf.org>; Mon, 21 Jun 2004 07:59:15 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5LBugfM075710;
	Mon, 21 Jun 2004 11:57:29 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.11/8.12.11/Submit) with SMTP id i5LBubY6075702;
	Mon, 21 Jun 2004 11:56: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, 21 Jun 2004 11:56:36 +0000
Received: from ghidora.unity.ncsu.edu (ghidora.unity.ncsu.edu [152.1.4.40])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5LBuWvq075691
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 21 Jun 2004 11:56:33 GMT
	(envelope-from daniel@unity.ncsu.edu)
Received: (from daniel@localhost)
	by ghidora.unity.ncsu.edu (8.11.7p1+Sun/8.10.2) id i5LBuU803104;
	Mon, 21 Jun 2004 07:56:30 -0400 (EDT)
Date: Mon, 21 Jun 2004 07:55:08 -0400 (EDT)
From: daniel@unity.ncsu.edu
Reply-To: daniel@ncsu.edu
To: Steven Legg <steven.legg@adacel.com.au>
cc: ietf-ldapbis@OpenLDAP.org
Subject: Re: ListMatch Clarification
In-Reply-To: <40D641B7.7020108@adacel.com.au>
Message-ID: <Pine.OSX.4.58.0406210747160.1719@katana.vorpalcloud.org>
References: <Pine.GSO.4.58.0406192125120.12430@ghidora.unity.ncsu.edu>
 <40D641B7.7020108@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-ID: ietf-ldapbis mailing list <ietf-ldapbis@OpenLDAP.org>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

> > I'm looking into implementing the ListMatch style matches and submitting a
> > patch.  I am having some trouble understanding part of the specification.
> > I understand that $ is effectively a newline.  The draft seems to indicate
> > that you ignore $ (ie, pull it out) and escape (\).  That said, the part
> > I'm not clear on is the actual search string.  Does the $ get handled in
> > the search string as well?  For example, lets say I want to find someone
> > on Foo Street, in Raleigh, NC.  Would I do a search along the lines of:
> > postalAddress=*Foo Street $ Raleigh, NC*
> > or
> > postalAddress=*Foo Street * Raleigh, NC*
> > or both?
>
> The second assertion value is the one that applies. The assertion syntax for
> caseIgnoreListSubstringsMatch is Substring Assertion, for which $ is an
> ordinary character (only * and \ are special). The first assertion value
> would only match if there were an escaped $ (i.e. not a line separator)
> in a line of the address (where only $ and \ are special).
>
> The unescaped $ line separators in a Postal Address value are an artefact
> of the LDAP-specific encoding and are not matchable character data.

Hrm.  Ok, let me see if I understand this correctly.  The address query is
matched on lines, not the string as a whole?  Given address:
123 Foo Street
Raleigh, NC 12345
aka: 123 Foo Street $ Raleigh, NC 12345

If I did a query of *Raleigh*, I would expect it to:
123 Foo Street		no match
Raleigh, NC 12345	match
	address matches

If I did a query of *Foo*, I would expect it to:
123 Foo Street		match
Raleigh, NC 12345	no match
	address matches

But what if I did *Foo Street*Raleigh*, I would expect it to:
123 Foo Street		no match
Raleigh, NC 12345	no match
	address doesn't match

Is this a correct interpretation of how it should work?  If you wanted to
make sure it was Foo Street in Raleigh, NC, how would you go about doing
that?  (&(postalAddress=*Foo Street*)(postalAddress=*Raleigh*)) ?

Thanks!

Daniel

>
> >
> > Also is there supposed to be a space on both sides of the $, similar to
> > how $'s are used in schema, or would there be no spaces?
>
> There is no requirement either way, and for caseIgnoreListMatch it makes no
> difference since each line of the address is matched according to
> caseIgnoreMatch which ignores leading and trailing space on each line.
> It makes no difference for caseIgnoreListSubstringsMatch as well
> because of the interaction of stringprep and the requirement that
> a substring in an assertion value for caseIgnoreListSubstringsMatch
> does not match characters across multiple lines.
>
> Regards,
> Steven
>
> >
> > Daniel
> >
>
>

-- 
/\\\----------------------------------------------------------------------///\
\ \\\      Daniel Henninger           http://www.vorpalcloud.org/        /// /
 \_\\\      North Carolina State University - Systems Programmer        ///_/
    \\\                   Information Technology <IT>                  ///
     """--------------------------------------------------------------"""


From owner-ietf-ldapbis@OpenLDAP.org  Mon Jun 21 09:31: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 JAA12831
	for <ldapbis-archive@lists.ietf.org>; Mon, 21 Jun 2004 09:31:43 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5LDKgO3079611;
	Mon, 21 Jun 2004 13:21:57 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.11/8.12.11/Submit) with SMTP id i5LDIdaK079558;
	Mon, 21 Jun 2004 13:18:39 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 21 Jun 2004 13:18:39 +0000
Received: from e4.ny.us.ibm.com (e4.ny.us.ibm.com [32.97.182.104])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5LDIZCw079546
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 21 Jun 2004 13:18:37 GMT
	(envelope-from jmcmeek@us.ibm.com)
Received: from northrelay04.pok.ibm.com (northrelay04.pok.ibm.com [9.56.224.206])
	by e4.ny.us.ibm.com (8.12.10/8.12.2) with ESMTP id i5LDI9rn672326;
	Mon, 21 Jun 2004 09:18:13 -0400
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 i5LDIuru102642;
	Mon, 21 Jun 2004 09:18:56 -0400
In-Reply-To: <Pine.OSX.4.58.0406210747160.1719@katana.vorpalcloud.org>
Subject: Re: ListMatch Clarification
To: daniel@ncsu.edu, ietf-ldapbis@OpenLDAP.org
X-Mailer: Lotus Notes Release 6.0.2CF1 June 9, 2003
Message-ID: <OF1A8ED09F.D3A8643D-ON86256EBA.0045DDBA-86256EBA.00490F5E@us.ibm.com>
From: John McMeeking <jmcmeek@us.ibm.com>
Date: Mon, 21 Jun 2004 08:18:06 -0500
X-MIMETrack: Serialize by Router on d27ml001/27/M/IBM(Release 6.5.2|June 01, 2004) at 06/21/2004
 08:18:08 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-ID: ietf-ldapbis mailing list <ietf-ldapbis@OpenLDAP.org>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>





I'm responding to test my understanding.

As I understand it, matching applies to the entire address as a
concatinated string, excluding the $ separators, except that * --
<initial>, <any>, or <final> -- does not span lines in an attribute value.
That is, * matches a substring of a line or the entire line, but not parts
of two lines.

Applying this to your later examples:

> Hrm.  Ok, let me see if I understand this correctly.  The address query
is
> matched on lines, not the string as a whole?  Given address:
> 123 Foo Street
> Raleigh, NC 12345
> aka: 123 Foo Street $ Raleigh, NC 12345

Matching will be applied to the concatinated string "123 Foo Street
Raleigh, NC 12345" with a hidden separator replacing the $.

>
> If I did a query of *Raleigh*, I would expect it to:
> 123 Foo Street      no match
> Raleigh, NC 12345   match
>    address matches

Matches:
Initial * matches "123 Foo Street", "Raleigh" matches Raleigh, final *
matches ", NC 12345"

>
> If I did a query of *Foo*, I would expect it to:
> 123 Foo Street      match
> Raleigh, NC 12345   no match
>    address matches

No match:
Initial * matches either a) the entire first line or b) "123"
a) "Foo *" does not match second line
b) "Foo *" matches "Foo Street" but does not include the next line of the
address.

>
> But what if I did *Foo Street*Raleigh*, I would expect it to:
> 123 Foo Street      no match
> Raleigh, NC 12345   no match
>    address doesn't match

Matches:
Initial "*Foo Street" matches 1st line, 2nd "*" matches empty string,
"Raleigh*" matches 2nd line.

Personal observations:
- Since the middle * is matching an empty string, "*Foo Street Raleigh*"
should also match.
- "*Foo Street*Raleigh*" could also match addresses like:
   123 Foo Street NW
   Raleigh, NC 12345
or
   123 Foo Street
   North Raleigh, NC 12345

>
> Is this a correct interpretation of how it should work?  If you wanted to
> make sure it was Foo Street in Raleigh, NC, how would you go about doing
> that?  (&(postalAddress=*Foo Street*)(postalAddress=*Raleigh*)) ?

Is my interpretation any better?

John  McMeeking


owner-ietf-ldapbis@OpenLDAP.org wrote on 06/21/2004 06:55:08 AM:

> > > I'm looking into implementing the ListMatch style matches and
submitting a
> > > patch.  I am having some trouble understanding part of the
specification.
> > > I understand that $ is effectively a newline.  The draft seems to
indicate
> > > that you ignore $ (ie, pull it out) and escape (\).  That said, the
part
> > > I'm not clear on is the actual search string.  Does the $ get handled
in
> > > the search string as well?  For example, lets say I want to find
someone
> > > on Foo Street, in Raleigh, NC.  Would I do a search along the lines
of:
> > > postalAddress=*Foo Street $ Raleigh, NC*
> > > or
> > > postalAddress=*Foo Street * Raleigh, NC*
> > > or both?
> >
> > The second assertion value is the one that applies. The assertion
syntax for
> > caseIgnoreListSubstringsMatch is Substring Assertion, for which $ is an
> > ordinary character (only * and \ are special). The first assertion
value
> > would only match if there were an escaped $ (i.e. not a line separator)
> > in a line of the address (where only $ and \ are special).
> >
> > The unescaped $ line separators in a Postal Address value are an
artefact
> > of the LDAP-specific encoding and are not matchable character data.
>
> Hrm.  Ok, let me see if I understand this correctly.  The address query
is
> matched on lines, not the string as a whole?  Given address:
> 123 Foo Street
> Raleigh, NC 12345
> aka: 123 Foo Street $ Raleigh, NC 12345
>
> If I did a query of *Raleigh*, I would expect it to:
> 123 Foo Street      no match
> Raleigh, NC 12345   match
>    address matches
>
> If I did a query of *Foo*, I would expect it to:
> 123 Foo Street      match
> Raleigh, NC 12345   no match
>    address matches
>
> But what if I did *Foo Street*Raleigh*, I would expect it to:
> 123 Foo Street      no match
> Raleigh, NC 12345   no match
>    address doesn't match
>
> Is this a correct interpretation of how it should work?  If you wanted to
> make sure it was Foo Street in Raleigh, NC, how would you go about doing
> that?  (&(postalAddress=*Foo Street*)(postalAddress=*Raleigh*)) ?
>
> Thanks!
>
> Daniel
>
> >
> > >
> > > Also is there supposed to be a space on both sides of the $, similar
to
> > > how $'s are used in schema, or would there be no spaces?
> >
> > There is no requirement either way, and for caseIgnoreListMatch it
makes no
> > difference since each line of the address is matched according to
> > caseIgnoreMatch which ignores leading and trailing space on each line.
> > It makes no difference for caseIgnoreListSubstringsMatch as well
> > because of the interaction of stringprep and the requirement that
> > a substring in an assertion value for caseIgnoreListSubstringsMatch
> > does not match characters across multiple lines.
> >
> > Regards,
> > Steven
> >
> > >
> > > Daniel
> > >
> >
> >
>
> --
>
/\\\----------------------------------------------------------------------///\

> \ \\\      Daniel Henninger           http://www.vorpalcloud.org/
/// /
>  \_\\\      North Carolina State University - Systems Programmer
///_/
>     \\\                   Information Technology <IT>
///
>      """--------------------------------------------------------------"""



From owner-ietf-ldapbis@OpenLDAP.org  Mon Jun 21 11:17: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 LAA19774
	for <ldapbis-archive@lists.ietf.org>; Mon, 21 Jun 2004 11:17:49 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5LFEh4V087367;
	Mon, 21 Jun 2004 15:16:35 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.11/8.12.11/Submit) with SMTP id i5LFCOOF087152;
	Mon, 21 Jun 2004 15:12: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); Mon, 21 Jun 2004 15:12:24 +0000
Received: from ghidora.unity.ncsu.edu (ghidora.unity.ncsu.edu [152.1.4.40])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5LFCLTF087141
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 21 Jun 2004 15:12:22 GMT
	(envelope-from daniel@unity.ncsu.edu)
Received: (from daniel@localhost)
	by ghidora.unity.ncsu.edu (8.11.7p1+Sun/8.10.2) id i5LFC0N07824;
	Mon, 21 Jun 2004 11:12:00 -0400 (EDT)
Date: Mon, 21 Jun 2004 11:12:00 -0400 (EDT)
From: Daniel Henninger <daniel@unity.ncsu.edu>
Reply-To: daniel@ncsu.edu
To: John McMeeking <jmcmeek@us.ibm.com>
cc: ietf-ldapbis@OpenLDAP.org
Subject: Re: ListMatch Clarification
In-Reply-To: <OF1A8ED09F.D3A8643D-ON86256EBA.0045DDBA-86256EBA.00490F5E@us.ibm.com>
Message-ID: <Pine.GSO.4.58.0406211059580.17557@ghidora.unity.ncsu.edu>
References: <OF1A8ED09F.D3A8643D-ON86256EBA.0045DDBA-86256EBA.00490F5E@us.ibm.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-ID: ietf-ldapbis mailing list <ietf-ldapbis@OpenLDAP.org>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

> As I understand it, matching applies to the entire address as a
> concatinated string, excluding the $ separators, except that * --
> <initial>, <any>, or <final> -- does not span lines in an attribute value.
> That is, * matches a substring of a line or the entire line, but not parts
> of two lines.

So if I'm understanding that correctly, one would have to do:
*Foo**NC* to match my example below?  I'll get to that.

> Applying this to your later examples:
>
> > Hrm.  Ok, let me see if I understand this correctly.  The address query
> is
> > matched on lines, not the string as a whole?  Given address:
> > 123 Foo Street
> > Raleigh, NC 12345
> > aka: 123 Foo Street $ Raleigh, NC 12345
>
> Matching will be applied to the concatinated string "123 Foo Street
> Raleigh, NC 12345" with a hidden separator replacing the $.

but the hidden seperator "stops dead" the *?  is that correct?

> > If I did a query of *Raleigh*, I would expect it to:
> > 123 Foo Street      no match
> > Raleigh, NC 12345   match
> >    address matches
>
> Matches:
> Initial * matches "123 Foo Street", "Raleigh" matches Raleigh, final *
> matches ", NC 12345"

And it only matches Raleigh because Raleigh is right at the beginning of
the line.  Correct?  If it were *NC*, it would -not- match?

> > If I did a query of *Foo*, I would expect it to:
> > 123 Foo Street      match
> > Raleigh, NC 12345   no match
> >    address matches
>
> No match:
> Initial * matches either a) the entire first line or b) "123"
> a) "Foo *" does not match second line
> b) "Foo *" matches "Foo Street" but does not include the next line of the
> address.

Ok, that makes sense based off my understanding from above.  =)

> > But what if I did *Foo Street*Raleigh*, I would expect it to:
> > 123 Foo Street      no match
> > Raleigh, NC 12345   no match
> >    address doesn't match
>
> Matches:
> Initial "*Foo Street" matches 1st line, 2nd "*" matches empty string,
> "Raleigh*" matches 2nd line.
>
> Personal observations:
> - Since the middle * is matching an empty string, "*Foo Street Raleigh*"
> should also match.
> - "*Foo Street*Raleigh*" could also match addresses like:
>    123 Foo Street NW
>    Raleigh, NC 12345

Because the first line would match *Foo Street* and the second line
would match the Raleigh* portion.


> or
>    123 Foo Street
>    North Raleigh, NC 12345

And because the first line would match *Foo Street and the second line
would match *Raleigh*.

> Is my interpretation any better?

Yes, that makes sense.  Makes it a lot harder to parse, but hey.  =)
Thanks!

Daniel

>
> John  McMeeking
>
>
> owner-ietf-ldapbis@OpenLDAP.org wrote on 06/21/2004 06:55:08 AM:
>
> > > > I'm looking into implementing the ListMatch style matches and
> submitting a
> > > > patch.  I am having some trouble understanding part of the
> specification.
> > > > I understand that $ is effectively a newline.  The draft seems to
> indicate
> > > > that you ignore $ (ie, pull it out) and escape (\).  That said, the
> part
> > > > I'm not clear on is the actual search string.  Does the $ get handled
> in
> > > > the search string as well?  For example, lets say I want to find
> someone
> > > > on Foo Street, in Raleigh, NC.  Would I do a search along the lines
> of:
> > > > postalAddress=*Foo Street $ Raleigh, NC*
> > > > or
> > > > postalAddress=*Foo Street * Raleigh, NC*
> > > > or both?
> > >
> > > The second assertion value is the one that applies. The assertion
> syntax for
> > > caseIgnoreListSubstringsMatch is Substring Assertion, for which $ is an
> > > ordinary character (only * and \ are special). The first assertion
> value
> > > would only match if there were an escaped $ (i.e. not a line separator)
> > > in a line of the address (where only $ and \ are special).
> > >
> > > The unescaped $ line separators in a Postal Address value are an
> artefact
> > > of the LDAP-specific encoding and are not matchable character data.
> >
> > Hrm.  Ok, let me see if I understand this correctly.  The address query
> is
> > matched on lines, not the string as a whole?  Given address:
> > 123 Foo Street
> > Raleigh, NC 12345
> > aka: 123 Foo Street $ Raleigh, NC 12345
> >
> > If I did a query of *Raleigh*, I would expect it to:
> > 123 Foo Street      no match
> > Raleigh, NC 12345   match
> >    address matches
> >
> > If I did a query of *Foo*, I would expect it to:
> > 123 Foo Street      match
> > Raleigh, NC 12345   no match
> >    address matches
> >
> > But what if I did *Foo Street*Raleigh*, I would expect it to:
> > 123 Foo Street      no match
> > Raleigh, NC 12345   no match
> >    address doesn't match
> >
> > Is this a correct interpretation of how it should work?  If you wanted to
> > make sure it was Foo Street in Raleigh, NC, how would you go about doing
> > that?  (&(postalAddress=*Foo Street*)(postalAddress=*Raleigh*)) ?
> >
> > Thanks!
> >
> > Daniel
> >
> > >
> > > >
> > > > Also is there supposed to be a space on both sides of the $, similar
> to
> > > > how $'s are used in schema, or would there be no spaces?
> > >
> > > There is no requirement either way, and for caseIgnoreListMatch it
> makes no
> > > difference since each line of the address is matched according to
> > > caseIgnoreMatch which ignores leading and trailing space on each line.
> > > It makes no difference for caseIgnoreListSubstringsMatch as well
> > > because of the interaction of stringprep and the requirement that
> > > a substring in an assertion value for caseIgnoreListSubstringsMatch
> > > does not match characters across multiple lines.
> > >
> > > Regards,
> > > Steven
> > >
> > > >
> > > > Daniel
> > > >
> > >
> > >
> >
> > --
> >
> /\\\----------------------------------------------------------------------///\
>
> > \ \\\      Daniel Henninger           http://www.vorpalcloud.org/
> /// /
> >  \_\\\      North Carolina State University - Systems Programmer
> ///_/
> >     \\\                   Information Technology <IT>
> ///
> >      """--------------------------------------------------------------"""
>
>

-- 
/\\\----------------------------------------------------------------------///\
\ \\\      Daniel Henninger           http://www.vorpalcloud.org/        /// /
 \_\\\      North Carolina State University - Systems Programmer        ///_/
    \\\                   Information Technology <IT>                  ///
     """--------------------------------------------------------------"""


From owner-ietf-ldapbis@OpenLDAP.org  Mon Jun 21 12:03:34 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 MAA26226
	for <ldapbis-archive@lists.ietf.org>; Mon, 21 Jun 2004 12:03:33 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5LFuhZA090435;
	Mon, 21 Jun 2004 16:01:57 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.11/8.12.11/Submit) with SMTP id i5LFsdj6090195;
	Mon, 21 Jun 2004 15:54:39 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 21 Jun 2004 15:54:39 +0000
Received: from e3.ny.us.ibm.com (e3.ny.us.ibm.com [32.97.182.103])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5LFsaLi090140
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 21 Jun 2004 15:54:37 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 i5LFsEc6776072;
	Mon, 21 Jun 2004 11:54:14 -0400
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 i5LFtMeP073826;
	Mon, 21 Jun 2004 11:55:22 -0400
In-Reply-To: <Pine.GSO.4.58.0406211059580.17557@ghidora.unity.ncsu.edu>
Subject: Re: ListMatch Clarification
To: daniel@ncsu.edu
Cc: ietf-ldapbis@OpenLDAP.org
X-Mailer: Lotus Notes Release 6.0.2CF1 June 9, 2003
Message-ID: <OF25CB7E54.644BA491-ON86256EBA.00560427-86256EBA.005759A9@us.ibm.com>
From: John McMeeking <jmcmeek@us.ibm.com>
Date: Mon, 21 Jun 2004 10:54:11 -0500
X-MIMETrack: Serialize by Router on d27ml001/27/M/IBM(Release 6.5.2|June 01, 2004) at 06/21/2004
 10:54:13 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-ID: ietf-ldapbis mailing list <ietf-ldapbis@OpenLDAP.org>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>





I think you've got it right, assuming someone else doesn't correct me.

Would it help to have some examples in the ldapbis syntaxes draft
illustrating some of these cases?

John  McMeeking


Daniel Henninger <daniel@unity.ncsu.edu> wrote on 06/21/2004 10:12:00 AM:

> > As I understand it, matching applies to the entire address as a
> > concatinated string, excluding the $ separators, except that * --
> > <initial>, <any>, or <final> -- does not span lines in an attribute
value.
> > That is, * matches a substring of a line or the entire line, but not
parts
> > of two lines.
>
> So if I'm understanding that correctly, one would have to do:
> *Foo**NC* to match my example below?  I'll get to that.

That's how I understand it.

>
> > Applying this to your later examples:
> >
> > > Hrm.  Ok, let me see if I understand this correctly.  The address
query
> > is
> > > matched on lines, not the string as a whole?  Given address:
> > > 123 Foo Street
> > > Raleigh, NC 12345
> > > aka: 123 Foo Street $ Raleigh, NC 12345
> >
> > Matching will be applied to the concatinated string "123 Foo Street
> > Raleigh, NC 12345" with a hidden separator replacing the $.
>
> but the hidden seperator "stops dead" the *?  is that correct?

I believe so.  Both X.520 and ldapbis [SYNTAXES] say:

   ... none of the <initial>, <any>, or <final> substrings of the
   assertion value are considered to match a substring of the
   concatenated string which spans more than one of the original strings
   of the attribute value.

>
> > > If I did a query of *Raleigh*, I would expect it to:
> > > 123 Foo Street      no match
> > > Raleigh, NC 12345   match
> > >    address matches
> >
> > Matches:
> > Initial * matches "123 Foo Street", "Raleigh" matches Raleigh, final *
> > matches ", NC 12345"
>
> And it only matches Raleigh because Raleigh is right at the beginning of
> the line.  Correct?  If it were *NC*, it would -not- match?

Correct, (postaladdress=*NC*) would not match this address.

>
> > > If I did a query of *Foo*, I would expect it to:
> > > 123 Foo Street      match
> > > Raleigh, NC 12345   no match
> > >    address matches
> >
> > No match:
> > Initial * matches either a) the entire first line or b) "123"
> > a) "Foo *" does not match second line
> > b) "Foo *" matches "Foo Street" but does not include the next line of
the
> > address.
>
> Ok, that makes sense based off my understanding from above.  =)
>
> > > But what if I did *Foo Street*Raleigh*, I would expect it to:
> > > 123 Foo Street      no match
> > > Raleigh, NC 12345   no match
> > >    address doesn't match
> >
> > Matches:
> > Initial "*Foo Street" matches 1st line, 2nd "*" matches empty string,
> > "Raleigh*" matches 2nd line.
> >
> > Personal observations:
> > - Since the middle * is matching an empty string, "*Foo Street
Raleigh*"
> > should also match.
> > - "*Foo Street*Raleigh*" could also match addresses like:
> >    123 Foo Street NW
> >    Raleigh, NC 12345
>
> Because the first line would match *Foo Street* and the second line
> would match the Raleigh* portion.
>
>
> > or
> >    123 Foo Street
> >    North Raleigh, NC 12345
>
> And because the first line would match *Foo Street and the second line
> would match *Raleigh*.
>
> > Is my interpretation any better?
>
> Yes, that makes sense.  Makes it a lot harder to parse, but hey.  =)
> Thanks!
>
> Daniel
>
> >
> > John  McMeeking
> >
> >
> > owner-ietf-ldapbis@OpenLDAP.org wrote on 06/21/2004 06:55:08 AM:
> >
> > > > > I'm looking into implementing the ListMatch style matches and
> > submitting a
> > > > > patch.  I am having some trouble understanding part of the
> > specification.
> > > > > I understand that $ is effectively a newline.  The draft seems to
> > indicate
> > > > > that you ignore $ (ie, pull it out) and escape (\).  That said,
the
> > part
> > > > > I'm not clear on is the actual search string.  Does the $ get
handled
> > in
> > > > > the search string as well?  For example, lets say I want to find
> > someone
> > > > > on Foo Street, in Raleigh, NC.  Would I do a search along the
lines
> > of:
> > > > > postalAddress=*Foo Street $ Raleigh, NC*
> > > > > or
> > > > > postalAddress=*Foo Street * Raleigh, NC*
> > > > > or both?
> > > >
> > > > The second assertion value is the one that applies. The assertion
> > syntax for
> > > > caseIgnoreListSubstringsMatch is Substring Assertion, for which $
is an
> > > > ordinary character (only * and \ are special). The first assertion
> > value
> > > > would only match if there were an escaped $ (i.e. not a line
separator)
> > > > in a line of the address (where only $ and \ are special).
> > > >
> > > > The unescaped $ line separators in a Postal Address value are an
> > artefact
> > > > of the LDAP-specific encoding and are not matchable character data.
> > >
> > > Hrm.  Ok, let me see if I understand this correctly.  The address
query
> > is
> > > matched on lines, not the string as a whole?  Given address:
> > > 123 Foo Street
> > > Raleigh, NC 12345
> > > aka: 123 Foo Street $ Raleigh, NC 12345
> > >
> > > If I did a query of *Raleigh*, I would expect it to:
> > > 123 Foo Street      no match
> > > Raleigh, NC 12345   match
> > >    address matches
> > >
> > > If I did a query of *Foo*, I would expect it to:
> > > 123 Foo Street      match
> > > Raleigh, NC 12345   no match
> > >    address matches
> > >
> > > But what if I did *Foo Street*Raleigh*, I would expect it to:
> > > 123 Foo Street      no match
> > > Raleigh, NC 12345   no match
> > >    address doesn't match
> > >
> > > Is this a correct interpretation of how it should work?  If you
wanted to
> > > make sure it was Foo Street in Raleigh, NC, how would you go about
doing
> > > that?  (&(postalAddress=*Foo Street*)(postalAddress=*Raleigh*)) ?
> > >
> > > Thanks!
> > >
> > > Daniel
> > >
> > > >
> > > > >
> > > > > Also is there supposed to be a space on both sides of the $,
similar
> > to
> > > > > how $'s are used in schema, or would there be no spaces?
> > > >
> > > > There is no requirement either way, and for caseIgnoreListMatch it
> > makes no
> > > > difference since each line of the address is matched according to
> > > > caseIgnoreMatch which ignores leading and trailing space on each
line.
> > > > It makes no difference for caseIgnoreListSubstringsMatch as well
> > > > because of the interaction of stringprep and the requirement that
> > > > a substring in an assertion value for caseIgnoreListSubstringsMatch
> > > > does not match characters across multiple lines.
> > > >
> > > > Regards,
> > > > Steven
> > > >
> > > > >
> > > > > Daniel
> > > > >
> > > >
> > > >
> > >
> > > --
> > >
> >
>
/\\\----------------------------------------------------------------------///\

> >
> > > \ \\\      Daniel Henninger           http://www.vorpalcloud.org/
> > /// /
> > >  \_\\\      North Carolina State University - Systems Programmer
> > ///_/
> > >     \\\                   Information Technology <IT>
> > ///
> > >
"""--------------------------------------------------------------"""
> >
> >
>
> --
>
/\\\----------------------------------------------------------------------///\

> \ \\\      Daniel Henninger           http://www.vorpalcloud.org/
/// /
>  \_\\\      North Carolina State University - Systems Programmer
///_/
>     \\\                   Information Technology <IT>
///
>      """--------------------------------------------------------------"""



From owner-ietf-ldapbis@OpenLDAP.org  Mon Jun 21 13:05: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 NAA05004
	for <ldapbis-archive@lists.ietf.org>; Mon, 21 Jun 2004 13:05:04 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5LH2iCU093557;
	Mon, 21 Jun 2004 17:03:21 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.11/8.12.11/Submit) with SMTP id i5LH0jfg093325;
	Mon, 21 Jun 2004 17:00:45 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 21 Jun 2004 17:00:45 +0000
Received: from ghidora.unity.ncsu.edu (ghidora.unity.ncsu.edu [152.1.4.40])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5LH0cO2093311
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 21 Jun 2004 17:00:40 GMT
	(envelope-from daniel@unity.ncsu.edu)
Received: (from daniel@localhost)
	by ghidora.unity.ncsu.edu (8.11.7p1+Sun/8.10.2) id i5LGxsx01915;
	Mon, 21 Jun 2004 12:59:54 -0400 (EDT)
Date: Mon, 21 Jun 2004 12:59:54 -0400 (EDT)
From: Daniel Henninger <daniel@unity.ncsu.edu>
Reply-To: daniel@ncsu.edu
To: John McMeeking <jmcmeek@us.ibm.com>
cc: ietf-ldapbis@OpenLDAP.org
Subject: Re: ListMatch Clarification
In-Reply-To: <OF25CB7E54.644BA491-ON86256EBA.00560427-86256EBA.005759A9@us.ibm.com>
Message-ID: <Pine.GSO.4.58.0406211259350.1914@ghidora.unity.ncsu.edu>
References: <OF25CB7E54.644BA491-ON86256EBA.00560427-86256EBA.005759A9@us.ibm.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-ID: ietf-ldapbis mailing list <ietf-ldapbis@OpenLDAP.org>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

> I think you've got it right, assuming someone else doesn't correct me.
>
> Would it help to have some examples in the ldapbis syntaxes draft
> illustrating some of these cases?

=)  I always think examples are a good thing!

Daniel

>
>
> Daniel Henninger <daniel@unity.ncsu.edu> wrote on 06/21/2004 10:12:00 AM:
>
> > > As I understand it, matching applies to the entire address as a
> > > concatinated string, excluding the $ separators, except that * --
> > > <initial>, <any>, or <final> -- does not span lines in an attribute
> value.
> > > That is, * matches a substring of a line or the entire line, but not
> parts
> > > of two lines.
> >
> > So if I'm understanding that correctly, one would have to do:
> > *Foo**NC* to match my example below?  I'll get to that.
>
> That's how I understand it.
>
> >
> > > Applying this to your later examples:
> > >
> > > > Hrm.  Ok, let me see if I understand this correctly.  The address
> query
> > > is
> > > > matched on lines, not the string as a whole?  Given address:
> > > > 123 Foo Street
> > > > Raleigh, NC 12345
> > > > aka: 123 Foo Street $ Raleigh, NC 12345
> > >
> > > Matching will be applied to the concatinated string "123 Foo Street
> > > Raleigh, NC 12345" with a hidden separator replacing the $.
> >
> > but the hidden seperator "stops dead" the *?  is that correct?
>
> I believe so.  Both X.520 and ldapbis [SYNTAXES] say:
>
>    ... none of the <initial>, <any>, or <final> substrings of the
>    assertion value are considered to match a substring of the
>    concatenated string which spans more than one of the original strings
>    of the attribute value.
>
> >
> > > > If I did a query of *Raleigh*, I would expect it to:
> > > > 123 Foo Street      no match
> > > > Raleigh, NC 12345   match
> > > >    address matches
> > >
> > > Matches:
> > > Initial * matches "123 Foo Street", "Raleigh" matches Raleigh, final *
> > > matches ", NC 12345"
> >
> > And it only matches Raleigh because Raleigh is right at the beginning of
> > the line.  Correct?  If it were *NC*, it would -not- match?
>
> Correct, (postaladdress=*NC*) would not match this address.
>
> >
> > > > If I did a query of *Foo*, I would expect it to:
> > > > 123 Foo Street      match
> > > > Raleigh, NC 12345   no match
> > > >    address matches
> > >
> > > No match:
> > > Initial * matches either a) the entire first line or b) "123"
> > > a) "Foo *" does not match second line
> > > b) "Foo *" matches "Foo Street" but does not include the next line of
> the
> > > address.
> >
> > Ok, that makes sense based off my understanding from above.  =)
> >
> > > > But what if I did *Foo Street*Raleigh*, I would expect it to:
> > > > 123 Foo Street      no match
> > > > Raleigh, NC 12345   no match
> > > >    address doesn't match
> > >
> > > Matches:
> > > Initial "*Foo Street" matches 1st line, 2nd "*" matches empty string,
> > > "Raleigh*" matches 2nd line.
> > >
> > > Personal observations:
> > > - Since the middle * is matching an empty string, "*Foo Street
> Raleigh*"
> > > should also match.
> > > - "*Foo Street*Raleigh*" could also match addresses like:
> > >    123 Foo Street NW
> > >    Raleigh, NC 12345
> >
> > Because the first line would match *Foo Street* and the second line
> > would match the Raleigh* portion.
> >
> >
> > > or
> > >    123 Foo Street
> > >    North Raleigh, NC 12345
> >
> > And because the first line would match *Foo Street and the second line
> > would match *Raleigh*.
> >
> > > Is my interpretation any better?
> >
> > Yes, that makes sense.  Makes it a lot harder to parse, but hey.  =)
> > Thanks!
> >
> > Daniel
> >
> > >
> > > John  McMeeking
> > >
> > >
> > > owner-ietf-ldapbis@OpenLDAP.org wrote on 06/21/2004 06:55:08 AM:
> > >
> > > > > > I'm looking into implementing the ListMatch style matches and
> > > submitting a
> > > > > > patch.  I am having some trouble understanding part of the
> > > specification.
> > > > > > I understand that $ is effectively a newline.  The draft seems to
> > > indicate
> > > > > > that you ignore $ (ie, pull it out) and escape (\).  That said,
> the
> > > part
> > > > > > I'm not clear on is the actual search string.  Does the $ get
> handled
> > > in
> > > > > > the search string as well?  For example, lets say I want to find
> > > someone
> > > > > > on Foo Street, in Raleigh, NC.  Would I do a search along the
> lines
> > > of:
> > > > > > postalAddress=*Foo Street $ Raleigh, NC*
> > > > > > or
> > > > > > postalAddress=*Foo Street * Raleigh, NC*
> > > > > > or both?
> > > > >
> > > > > The second assertion value is the one that applies. The assertion
> > > syntax for
> > > > > caseIgnoreListSubstringsMatch is Substring Assertion, for which $
> is an
> > > > > ordinary character (only * and \ are special). The first assertion
> > > value
> > > > > would only match if there were an escaped $ (i.e. not a line
> separator)
> > > > > in a line of the address (where only $ and \ are special).
> > > > >
> > > > > The unescaped $ line separators in a Postal Address value are an
> > > artefact
> > > > > of the LDAP-specific encoding and are not matchable character data.
> > > >
> > > > Hrm.  Ok, let me see if I understand this correctly.  The address
> query
> > > is
> > > > matched on lines, not the string as a whole?  Given address:
> > > > 123 Foo Street
> > > > Raleigh, NC 12345
> > > > aka: 123 Foo Street $ Raleigh, NC 12345
> > > >
> > > > If I did a query of *Raleigh*, I would expect it to:
> > > > 123 Foo Street      no match
> > > > Raleigh, NC 12345   match
> > > >    address matches
> > > >
> > > > If I did a query of *Foo*, I would expect it to:
> > > > 123 Foo Street      match
> > > > Raleigh, NC 12345   no match
> > > >    address matches
> > > >
> > > > But what if I did *Foo Street*Raleigh*, I would expect it to:
> > > > 123 Foo Street      no match
> > > > Raleigh, NC 12345   no match
> > > >    address doesn't match
> > > >
> > > > Is this a correct interpretation of how it should work?  If you
> wanted to
> > > > make sure it was Foo Street in Raleigh, NC, how would you go about
> doing
> > > > that?  (&(postalAddress=*Foo Street*)(postalAddress=*Raleigh*)) ?
> > > >
> > > > Thanks!
> > > >
> > > > Daniel
> > > >
> > > > >
> > > > > >
> > > > > > Also is there supposed to be a space on both sides of the $,
> similar
> > > to
> > > > > > how $'s are used in schema, or would there be no spaces?
> > > > >
> > > > > There is no requirement either way, and for caseIgnoreListMatch it
> > > makes no
> > > > > difference since each line of the address is matched according to
> > > > > caseIgnoreMatch which ignores leading and trailing space on each
> line.
> > > > > It makes no difference for caseIgnoreListSubstringsMatch as well
> > > > > because of the interaction of stringprep and the requirement that
> > > > > a substring in an assertion value for caseIgnoreListSubstringsMatch
> > > > > does not match characters across multiple lines.
> > > > >
> > > > > Regards,
> > > > > Steven
> > > > >
> > > > > >
> > > > > > Daniel
> > > > > >
> > > > >
> > > > >
> > > >
> > > > --
> > > >
> > >
> >
> /\\\----------------------------------------------------------------------///\
>
> > >
> > > > \ \\\      Daniel Henninger           http://www.vorpalcloud.org/
> > > /// /
> > > >  \_\\\      North Carolina State University - Systems Programmer
> > > ///_/
> > > >     \\\                   Information Technology <IT>
> > > ///
> > > >
> """--------------------------------------------------------------"""
> > >
> > >
> >
> > --
> >
> /\\\----------------------------------------------------------------------///\
>
> > \ \\\      Daniel Henninger           http://www.vorpalcloud.org/
> /// /
> >  \_\\\      North Carolina State University - Systems Programmer
> ///_/
> >     \\\                   Information Technology <IT>
> ///
> >      """--------------------------------------------------------------"""
>
>

-- 
/\\\----------------------------------------------------------------------///\
\ \\\      Daniel Henninger           http://www.vorpalcloud.org/        /// /
 \_\\\      North Carolina State University - Systems Programmer        ///_/
    \\\                   Information Technology <IT>                  ///
     """--------------------------------------------------------------"""


From owner-ietf-ldapbis@OpenLDAP.org  Mon Jun 21 17:37: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 RAA03263
	for <ldapbis-archive@lists.ietf.org>; Mon, 21 Jun 2004 17:37:45 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5LLQj9G013616;
	Mon, 21 Jun 2004 21:36:47 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.11/8.12.11/Submit) with SMTP id i5LLMA2Z013459;
	Mon, 21 Jun 2004 21:22:10 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 21 Jun 2004 21:22:10 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5LLM46A013448
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 21 Jun 2004 21:22:05 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.11) with ESMTP id i5LLM1MC082328;
	Mon, 21 Jun 2004 21:22:02 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.1.1.0.20040621140555.04897a90@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Mon, 21 Jun 2004 14:22:11 -0700
To: daniel@ncsu.edu
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: ListMatch Clarification
Cc: John McMeeking <jmcmeek@us.ibm.com>, ietf-ldapbis@OpenLDAP.org
In-Reply-To: <Pine.GSO.4.58.0406211059580.17557@ghidora.unity.ncsu.edu>
References: <OF1A8ED09F.D3A8643D-ON86256EBA.0045DDBA-86256EBA.00490F5E@us.ibm.com>
 <Pine.GSO.4.58.0406211059580.17557@ghidora.unity.ncsu.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-ID: ietf-ldapbis mailing list <ietf-ldapbis@OpenLDAP.org>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

I think the syntax I-D note regarding LDAP-string encoding
handling is causing some confusion here.  I would instead
say that caseIgnoreSubstringsListMatch(substrings,list) is,
in terms of the LDAP-specific encodings, acts like
caseIgnoreMatch(escape(substrings),list) where escape()
escapes "\" and "$" appearing in substrings so that they
will properly match like characters appearing in list
strings (but not list separators).

At 08:12 AM 6/21/2004, Daniel Henninger wrote:
>> As I understand it, matching applies to the entire address as a
>> concatinated string, excluding the $ separators, except that * --
>> <initial>, <any>, or <final> -- does not span lines in an attribute value.
>> That is, * matches a substring of a line or the entire line, but not parts
>> of two lines.

I think it a bit dangerous to think of * as wildcard.
But if one has foo*bar*foo than each * can certain "match"
portions of multiple lines.  However, each substring
(foo, bar, foo) must appear wholly within one line.
That is, *foobar* does not match foo$bar.

>So if I'm understanding that correctly, one would have to do:
>*Foo**NC* to match my example below?  I'll get to that.

This assertion is invalid.  All substrings must have
non-zero length.

>> Applying this to your later examples:

I think the rest of this stuff is confused.

Do not think of '*' as a wildcard.  Think in terms
of the <initial>, <any>, and <final> substrings being
asserted and the list of strings they are matched
against. 



From owner-ietf-ldapbis@OpenLDAP.org  Mon Jun 21 20:59: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 UAA22572
	for <ldapbis-archive@lists.ietf.org>; Mon, 21 Jun 2004 20:59:11 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5M0uk7v022952;
	Tue, 22 Jun 2004 00:57:13 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.11/8.12.11/Submit) with SMTP id i5M0ujR8022944;
	Tue, 22 Jun 2004 00:56: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, 22 Jun 2004 00:56:45 +0000
Received: from adacel.com (gunsmoke.adacel.com.au [210.11.130.7])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5M0ubKe022930
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 22 Jun 2004 00:56:39 GMT
	(envelope-from steven.legg@adacel.com.au)
Received: from nexus.adacel.com (Not Verified[10.32.240.1]) by adacel.com with NetIQ MailMarshal (v5.5.6.7)
	id <B00027e7ac>; Tue, 22 Jun 2004 10:54:38 +1000
Received: (qmail 31724 invoked from network); 22 Jun 2004 00:56:15 -0000
Received: from unknown (HELO adacel.com.au) (10.32.24.165)
  by nexus.adacel.com with SMTP; 22 Jun 2004 00:56:15 -0000
Message-ID: <40D783AE.1060102@adacel.com.au>
Date: Tue, 22 Jun 2004 10:56:14 +1000
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: daniel@ncsu.edu
CC: John McMeeking <jmcmeek@us.ibm.com>, ietf-ldapbis@OpenLDAP.org
Subject: Re: ListMatch Clarification
References: <OF1A8ED09F.D3A8643D-ON86256EBA.0045DDBA-86256EBA.00490F5E@us.ibm.com> <Pine.GSO.4.58.0406211059580.17557@ghidora.unity.ncsu.edu>
In-Reply-To: <Pine.GSO.4.58.0406211059580.17557@ghidora.unity.ncsu.edu>
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-ID: ietf-ldapbis mailing list <ietf-ldapbis@OpenLDAP.org>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


Daniel,

Daniel Henninger wrote:
 > John McMeeking wrote:
>>As I understand it, matching applies to the entire address as a
>>concatinated string, excluding the $ separators, except that * --
>><initial>, <any>, or <final> -- does not span lines in an attribute value.
>>That is, * matches a substring of a line or the entire line, but not parts
>>of two lines.

It is not the intention that the * separators in a Substring Assertion value
are part of the substrings that are matched, and which are required to match
entirely within a line. As Kurt points out, it isn't appropriate to think
of the *'s as wildcards either. I will try to rewrite the text about substring
matching to make this clearer in the next revision.

> 
> 
> So if I'm understanding that correctly, one would have to do:
> *Foo**NC* to match my example below?  I'll get to that.

The substrings to be matched are "Foo" and "NC", so the correct assertion
is "*Foo*NC*". The position of the *'s tells us that "Foo" and "NC" are
both any substrings (as opposed to initial or final substrings).

> 
> 
>>Applying this to your later examples:
>>
>>
>>>Hrm.  Ok, let me see if I understand this correctly.  The address query
>>
>>is
>>
>>>matched on lines, not the string as a whole?  Given address:
>>>123 Foo Street
>>>Raleigh, NC 12345
>>>aka: 123 Foo Street $ Raleigh, NC 12345
>>
>>Matching will be applied to the concatinated string "123 Foo Street
>>Raleigh, NC 12345" with a hidden separator replacing the $.
> 
> 
> but the hidden seperator "stops dead" the *?  is that correct?

No, because the * isn't part of a substring to be matched.

> 
> 
>>>If I did a query of *Raleigh*, I would expect it to:
>>>123 Foo Street      no match
>>>Raleigh, NC 12345   match
>>>   address matches
>>
>>Matches:
>>Initial * matches "123 Foo Street", "Raleigh" matches Raleigh, final *
>>matches ", NC 12345"
> 
> 
> And it only matches Raleigh because Raleigh is right at the beginning of
> the line.  Correct?  If it were *NC*, it would -not- match?

"*NC*" would match because the any substring "NC" completely matches a string
of characters wholly contained within a line of the address (the second line).

> 
> 
>>>If I did a query of *Foo*, I would expect it to:
>>>123 Foo Street      match
>>>Raleigh, NC 12345   no match
>>>   address matches
>>
>>No match:
>>Initial * matches either a) the entire first line or b) "123"
>>a) "Foo *" does not match second line
>>b) "Foo *" matches "Foo Street" but does not include the next line of the
>>address.

"*Foo*" would match because the any substring "Foo" completely matches a string
of characters wholly contained within a line of the address (the first line).

> 
> 
> Ok, that makes sense based off my understanding from above.  =)
> 
> 
>>>But what if I did *Foo Street*Raleigh*, I would expect it to:
>>>123 Foo Street      no match
>>>Raleigh, NC 12345   no match
>>>   address doesn't match
>>
>>Matches:
>>Initial "*Foo Street" matches 1st line, 2nd "*" matches empty string,
>>"Raleigh*" matches 2nd line.

The address matches. The any substring "Foo Street" completely matches a
string of characters wholly contained within a line of the address (the
first line) and the any substring "Raleigh" completely matches a subsequent
string of characters wholly contained within a line of the address (the
the second line).

>>
>>Personal observations:
>>- Since the middle * is matching an empty string, "*Foo Street Raleigh*"
>>should also match.

"*Foo Street Raleigh*" won't match because the any substring "Foo Street Raleigh"
does not match any string of characters which is wholly contained within any
one line of the address.

>>- "*Foo Street*Raleigh*" could also match addresses like:
>>   123 Foo Street NW
>>   Raleigh, NC 12345
> 
> 
> Because the first line would match *Foo Street* and the second line
> would match the Raleigh* portion.

It's the right answer, but the reasoning is that the any substring "Foo Street"
completely matches a string of characters wholly contained within a line of the
address (the first line) and the any substring "Raleigh" completely matches a
subsequent string of characters wholly contained within a line of the address
(the second line).

The examples have substrings matching strings of characters on separate lines
but there is nothing to stop the substrings matching disjoint strings of
characters on the same line.

Regards,
Steven

> 
> 
> 
>>or
>>   123 Foo Street
>>   North Raleigh, NC 12345
> 
> 
> And because the first line would match *Foo Street and the second line
> would match *Raleigh*.
> 
> 
>>Is my interpretation any better?
> 
> 
> Yes, that makes sense.  Makes it a lot harder to parse, but hey.  =)
> Thanks!
> 
> Daniel
> 
> 
>>John  McMeeking
>>
>>
>>owner-ietf-ldapbis@OpenLDAP.org wrote on 06/21/2004 06:55:08 AM:
>>
>>
>>>>>I'm looking into implementing the ListMatch style matches and
>>
>>submitting a
>>
>>>>>patch.  I am having some trouble understanding part of the
>>
>>specification.
>>
>>>>>I understand that $ is effectively a newline.  The draft seems to
>>
>>indicate
>>
>>>>>that you ignore $ (ie, pull it out) and escape (\).  That said, the
>>
>>part
>>
>>>>>I'm not clear on is the actual search string.  Does the $ get handled
>>
>>in
>>
>>>>>the search string as well?  For example, lets say I want to find
>>
>>someone
>>
>>>>>on Foo Street, in Raleigh, NC.  Would I do a search along the lines
>>
>>of:
>>
>>>>>postalAddress=*Foo Street $ Raleigh, NC*
>>>>>or
>>>>>postalAddress=*Foo Street * Raleigh, NC*
>>>>>or both?
>>>>
>>>>The second assertion value is the one that applies. The assertion
>>
>>syntax for
>>
>>>>caseIgnoreListSubstringsMatch is Substring Assertion, for which $ is an
>>>>ordinary character (only * and \ are special). The first assertion
>>
>>value
>>
>>>>would only match if there were an escaped $ (i.e. not a line separator)
>>>>in a line of the address (where only $ and \ are special).
>>>>
>>>>The unescaped $ line separators in a Postal Address value are an
>>
>>artefact
>>
>>>>of the LDAP-specific encoding and are not matchable character data.
>>>
>>>Hrm.  Ok, let me see if I understand this correctly.  The address query
>>
>>is
>>
>>>matched on lines, not the string as a whole?  Given address:
>>>123 Foo Street
>>>Raleigh, NC 12345
>>>aka: 123 Foo Street $ Raleigh, NC 12345
>>>
>>>If I did a query of *Raleigh*, I would expect it to:
>>>123 Foo Street      no match
>>>Raleigh, NC 12345   match
>>>   address matches
>>>
>>>If I did a query of *Foo*, I would expect it to:
>>>123 Foo Street      match
>>>Raleigh, NC 12345   no match
>>>   address matches
>>>
>>>But what if I did *Foo Street*Raleigh*, I would expect it to:
>>>123 Foo Street      no match
>>>Raleigh, NC 12345   no match
>>>   address doesn't match
>>>
>>>Is this a correct interpretation of how it should work?  If you wanted to
>>>make sure it was Foo Street in Raleigh, NC, how would you go about doing
>>>that?  (&(postalAddress=*Foo Street*)(postalAddress=*Raleigh*)) ?
>>>
>>>Thanks!
>>>
>>>Daniel
>>>
>>>
>>>>>Also is there supposed to be a space on both sides of the $, similar
>>
>>to
>>
>>>>>how $'s are used in schema, or would there be no spaces?
>>>>
>>>>There is no requirement either way, and for caseIgnoreListMatch it
>>
>>makes no
>>
>>>>difference since each line of the address is matched according to
>>>>caseIgnoreMatch which ignores leading and trailing space on each line.
>>>>It makes no difference for caseIgnoreListSubstringsMatch as well
>>>>because of the interaction of stringprep and the requirement that
>>>>a substring in an assertion value for caseIgnoreListSubstringsMatch
>>>>does not match characters across multiple lines.
>>>>
>>>>Regards,
>>>>Steven
>>>>
>>>>
>>>>>Daniel
>>>>>
>>>>
>>>>
>>>--
>>>
>>
>>/\\\----------------------------------------------------------------------///\
>>
>>
>>>\ \\\      Daniel Henninger           http://www.vorpalcloud.org/
>>
>>/// /
>>
>>> \_\\\      North Carolina State University - Systems Programmer
>>
>>///_/
>>
>>>    \\\                   Information Technology <IT>
>>
>>///
>>
>>>     """--------------------------------------------------------------"""
>>
>>
> 



From owner-ietf-ldapbis@OpenLDAP.org  Mon Jun 21 21:04: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 VAA22643
	for <ldapbis-archive@lists.ietf.org>; Mon, 21 Jun 2004 21:04:28 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5M12k6U023184;
	Tue, 22 Jun 2004 01:02:52 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.11/8.12.11/Submit) with SMTP id i5M0wn0w023019;
	Tue, 22 Jun 2004 00:58: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, 22 Jun 2004 00:58:49 +0000
Received: from adacel.com (gunsmoke.adacel.com.au [210.11.130.7])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5M0wjSE022972
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 22 Jun 2004 00:58:46 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.6.7)
	id <B00027e7b5>; Tue, 22 Jun 2004 10:56:47 +1000
Received: (qmail 32138 invoked from network); 22 Jun 2004 00:58:24 -0000
Received: from unknown (HELO adacel.com.au) (10.32.24.165)
  by nexus.adacel.com with SMTP; 22 Jun 2004 00:58:24 -0000
Message-ID: <40D78430.7000405@adacel.com.au>
Date: Tue, 22 Jun 2004 10:58:24 +1000
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: daniel@ncsu.edu
CC: John McMeeking <jmcmeek@us.ibm.com>, ietf-ldapbis@OpenLDAP.org
Subject: Re: ListMatch Clarification
References: <OF25CB7E54.644BA491-ON86256EBA.00560427-86256EBA.005759A9@us.ibm.com> <Pine.GSO.4.58.0406211259350.1914@ghidora.unity.ncsu.edu>
In-Reply-To: <Pine.GSO.4.58.0406211259350.1914@ghidora.unity.ncsu.edu>
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-ID: ietf-ldapbis mailing list <ietf-ldapbis@OpenLDAP.org>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


I'll look at adding some examples in the next revision.

Regards,
Steven

Daniel Henninger wrote:
>>I think you've got it right, assuming someone else doesn't correct me.
>>
>>Would it help to have some examples in the ldapbis syntaxes draft
>>illustrating some of these cases?
> 
> 
> =)  I always think examples are a good thing!
> 
> Daniel
> 
> 
>>
>>Daniel Henninger <daniel@unity.ncsu.edu> wrote on 06/21/2004 10:12:00 AM:
>>
>>
>>>>As I understand it, matching applies to the entire address as a
>>>>concatinated string, excluding the $ separators, except that * --
>>>><initial>, <any>, or <final> -- does not span lines in an attribute
>>
>>value.
>>
>>>>That is, * matches a substring of a line or the entire line, but not
>>
>>parts
>>
>>>>of two lines.
>>>
>>>So if I'm understanding that correctly, one would have to do:
>>>*Foo**NC* to match my example below?  I'll get to that.
>>
>>That's how I understand it.
>>
>>
>>>>Applying this to your later examples:
>>>>
>>>>
>>>>>Hrm.  Ok, let me see if I understand this correctly.  The address
>>
>>query
>>
>>>>is
>>>>
>>>>>matched on lines, not the string as a whole?  Given address:
>>>>>123 Foo Street
>>>>>Raleigh, NC 12345
>>>>>aka: 123 Foo Street $ Raleigh, NC 12345
>>>>
>>>>Matching will be applied to the concatinated string "123 Foo Street
>>>>Raleigh, NC 12345" with a hidden separator replacing the $.
>>>
>>>but the hidden seperator "stops dead" the *?  is that correct?
>>
>>I believe so.  Both X.520 and ldapbis [SYNTAXES] say:
>>
>>   ... none of the <initial>, <any>, or <final> substrings of the
>>   assertion value are considered to match a substring of the
>>   concatenated string which spans more than one of the original strings
>>   of the attribute value.
>>
>>
>>>>>If I did a query of *Raleigh*, I would expect it to:
>>>>>123 Foo Street      no match
>>>>>Raleigh, NC 12345   match
>>>>>   address matches
>>>>
>>>>Matches:
>>>>Initial * matches "123 Foo Street", "Raleigh" matches Raleigh, final *
>>>>matches ", NC 12345"
>>>
>>>And it only matches Raleigh because Raleigh is right at the beginning of
>>>the line.  Correct?  If it were *NC*, it would -not- match?
>>
>>Correct, (postaladdress=*NC*) would not match this address.
>>
>>
>>>>>If I did a query of *Foo*, I would expect it to:
>>>>>123 Foo Street      match
>>>>>Raleigh, NC 12345   no match
>>>>>   address matches
>>>>
>>>>No match:
>>>>Initial * matches either a) the entire first line or b) "123"
>>>>a) "Foo *" does not match second line
>>>>b) "Foo *" matches "Foo Street" but does not include the next line of
>>
>>the
>>
>>>>address.
>>>
>>>Ok, that makes sense based off my understanding from above.  =)
>>>
>>>
>>>>>But what if I did *Foo Street*Raleigh*, I would expect it to:
>>>>>123 Foo Street      no match
>>>>>Raleigh, NC 12345   no match
>>>>>   address doesn't match
>>>>
>>>>Matches:
>>>>Initial "*Foo Street" matches 1st line, 2nd "*" matches empty string,
>>>>"Raleigh*" matches 2nd line.
>>>>
>>>>Personal observations:
>>>>- Since the middle * is matching an empty string, "*Foo Street
>>
>>Raleigh*"
>>
>>>>should also match.
>>>>- "*Foo Street*Raleigh*" could also match addresses like:
>>>>   123 Foo Street NW
>>>>   Raleigh, NC 12345
>>>
>>>Because the first line would match *Foo Street* and the second line
>>>would match the Raleigh* portion.
>>>
>>>
>>>
>>>>or
>>>>   123 Foo Street
>>>>   North Raleigh, NC 12345
>>>
>>>And because the first line would match *Foo Street and the second line
>>>would match *Raleigh*.
>>>
>>>
>>>>Is my interpretation any better?
>>>
>>>Yes, that makes sense.  Makes it a lot harder to parse, but hey.  =)
>>>Thanks!
>>>
>>>Daniel
>>>
>>>
>>>>John  McMeeking
>>>>
>>>>
>>>>owner-ietf-ldapbis@OpenLDAP.org wrote on 06/21/2004 06:55:08 AM:
>>>>
>>>>
>>>>>>>I'm looking into implementing the ListMatch style matches and
>>>>
>>>>submitting a
>>>>
>>>>>>>patch.  I am having some trouble understanding part of the
>>>>
>>>>specification.
>>>>
>>>>>>>I understand that $ is effectively a newline.  The draft seems to
>>>>
>>>>indicate
>>>>
>>>>>>>that you ignore $ (ie, pull it out) and escape (\).  That said,
>>
>>the
>>
>>>>part
>>>>
>>>>>>>I'm not clear on is the actual search string.  Does the $ get
>>
>>handled
>>
>>>>in
>>>>
>>>>>>>the search string as well?  For example, lets say I want to find
>>>>
>>>>someone
>>>>
>>>>>>>on Foo Street, in Raleigh, NC.  Would I do a search along the
>>
>>lines
>>
>>>>of:
>>>>
>>>>>>>postalAddress=*Foo Street $ Raleigh, NC*
>>>>>>>or
>>>>>>>postalAddress=*Foo Street * Raleigh, NC*
>>>>>>>or both?
>>>>>>
>>>>>>The second assertion value is the one that applies. The assertion
>>>>
>>>>syntax for
>>>>
>>>>>>caseIgnoreListSubstringsMatch is Substring Assertion, for which $
>>
>>is an
>>
>>>>>>ordinary character (only * and \ are special). The first assertion
>>>>
>>>>value
>>>>
>>>>>>would only match if there were an escaped $ (i.e. not a line
>>
>>separator)
>>
>>>>>>in a line of the address (where only $ and \ are special).
>>>>>>
>>>>>>The unescaped $ line separators in a Postal Address value are an
>>>>
>>>>artefact
>>>>
>>>>>>of the LDAP-specific encoding and are not matchable character data.
>>>>>
>>>>>Hrm.  Ok, let me see if I understand this correctly.  The address
>>
>>query
>>
>>>>is
>>>>
>>>>>matched on lines, not the string as a whole?  Given address:
>>>>>123 Foo Street
>>>>>Raleigh, NC 12345
>>>>>aka: 123 Foo Street $ Raleigh, NC 12345
>>>>>
>>>>>If I did a query of *Raleigh*, I would expect it to:
>>>>>123 Foo Street      no match
>>>>>Raleigh, NC 12345   match
>>>>>   address matches
>>>>>
>>>>>If I did a query of *Foo*, I would expect it to:
>>>>>123 Foo Street      match
>>>>>Raleigh, NC 12345   no match
>>>>>   address matches
>>>>>
>>>>>But what if I did *Foo Street*Raleigh*, I would expect it to:
>>>>>123 Foo Street      no match
>>>>>Raleigh, NC 12345   no match
>>>>>   address doesn't match
>>>>>
>>>>>Is this a correct interpretation of how it should work?  If you
>>
>>wanted to
>>
>>>>>make sure it was Foo Street in Raleigh, NC, how would you go about
>>
>>doing
>>
>>>>>that?  (&(postalAddress=*Foo Street*)(postalAddress=*Raleigh*)) ?
>>>>>
>>>>>Thanks!
>>>>>
>>>>>Daniel
>>>>>
>>>>>
>>>>>>>Also is there supposed to be a space on both sides of the $,
>>
>>similar
>>
>>>>to
>>>>
>>>>>>>how $'s are used in schema, or would there be no spaces?
>>>>>>
>>>>>>There is no requirement either way, and for caseIgnoreListMatch it
>>>>
>>>>makes no
>>>>
>>>>>>difference since each line of the address is matched according to
>>>>>>caseIgnoreMatch which ignores leading and trailing space on each
>>
>>line.
>>
>>>>>>It makes no difference for caseIgnoreListSubstringsMatch as well
>>>>>>because of the interaction of stringprep and the requirement that
>>>>>>a substring in an assertion value for caseIgnoreListSubstringsMatch
>>>>>>does not match characters across multiple lines.
>>>>>>
>>>>>>Regards,
>>>>>>Steven
>>>>>>
>>>>>>
>>>>>>>Daniel
>>>>>>>
>>>>>>
>>>>>>
>>>>>--
>>>>>
>>>>
>>/\\\----------------------------------------------------------------------///\
>>
>>
>>>>>\ \\\      Daniel Henninger           http://www.vorpalcloud.org/
>>>>
>>>>/// /
>>>>
>>>>> \_\\\      North Carolina State University - Systems Programmer
>>>>
>>>>///_/
>>>>
>>>>>    \\\                   Information Technology <IT>
>>>>
>>>>///
>>>>
>>"""--------------------------------------------------------------"""
>>
>>>>
>>>--
>>>
>>
>>/\\\----------------------------------------------------------------------///\
>>
>>
>>>\ \\\      Daniel Henninger           http://www.vorpalcloud.org/
>>
>>/// /
>>
>>> \_\\\      North Carolina State University - Systems Programmer
>>
>>///_/
>>
>>>    \\\                   Information Technology <IT>
>>
>>///
>>
>>>     """--------------------------------------------------------------"""
>>
>>
> 



From owner-ietf-ldapbis@OpenLDAP.org  Mon Jun 21 23:16: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 XAA28317
	for <ldapbis-archive@lists.ietf.org>; Mon, 21 Jun 2004 23:16:22 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5M2uqu1025969;
	Tue, 22 Jun 2004 02:58:07 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.11/8.12.11/Submit) with SMTP id i5M2qc99025831;
	Tue, 22 Jun 2004 02:52:38 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 22 Jun 2004 02:52:38 +0000
Received: from adacel.com (gunsmoke.adacel.com.au [210.11.130.7])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5M2pWUX025799
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 22 Jun 2004 02:52:37 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.6.7)
	id <B00027e955>; Tue, 22 Jun 2004 12:49:31 +1000
Received: (qmail 26163 invoked from network); 22 Jun 2004 02:51:09 -0000
Received: from unknown (HELO adacel.com.au) (10.32.24.165)
  by nexus.adacel.com with SMTP; 22 Jun 2004 02:51:09 -0000
Message-ID: <40D79E9D.6030600@adacel.com.au>
Date: Tue, 22 Jun 2004 12:51:09 +1000
From: Steven Legg <steven.legg@adacel.com.au>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3.1) Gecko/20030425
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
CC: ietf-ldapbis@OpenLDAP.org
Subject: Re: ListMatch Clarification
References: <OF1A8ED09F.D3A8643D-ON86256EBA.0045DDBA-86256EBA.00490F5E@us.ibm.com> <Pine.GSO.4.58.0406211059580.17557@ghidora.unity.ncsu.edu> <6.0.1.1.0.20040621140555.04897a90@127.0.0.1>
In-Reply-To: <6.0.1.1.0.20040621140555.04897a90@127.0.0.1>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-ID: ietf-ldapbis mailing list <ietf-ldapbis@OpenLDAP.org>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


Kurt,

Kurt D. Zeilenga wrote:
> I think the syntax I-D note regarding LDAP-string encoding
> handling is causing some confusion here.  I would instead
> say that caseIgnoreSubstringsListMatch(substrings,list) is,

caseIgnoreListSubstringsMatch

The function notation you are using hasn't been defined anywhere.

> in terms of the LDAP-specific encodings, acts like
> caseIgnoreMatch(escape(substrings),list) where escape()

caseIgnoreSubstringsMatch

> escapes "\" and "$" appearing in substrings so that they
> will properly match like characters appearing in list
> strings (but not list separators).

I prefer to be replacing escapes in the concatenated string rather
than adding escapes to the substrings of the substring assertion because
the latter is heading down the direction of comparing LDAP-specific
encodings rather than comparing abstract values.

The syntax definition for SubstringAssertion currently only allows
escapes for "\" and "*". It would need to be extended to allow for "$"
as well.

There is also the problem that the concatenated string, which is notionally
of the Directory String syntax, or similar, would contain escaped "$" but
the Directory String syntax does not have a defined escaping mechanism in
either RFC 2252 or the syntaxes draft. If we regard "\24" as literal text
then we have a weird situation where caseIgnoreSubstringsMatch matches "\24"
with "\24" but not "$", while "\2A" matches "*" but not "\2A". Yikes!

Regards,
Steven



From owner-ietf-ldapbis@OpenLDAP.org  Mon Jun 21 23:26: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 XAA28780
	for <ldapbis-archive@lists.ietf.org>; Mon, 21 Jun 2004 23:26:16 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5M3ElVP026859;
	Tue, 22 Jun 2004 03:15:33 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.11/8.12.11/Submit) with SMTP id i5M3DXwC026830;
	Tue, 22 Jun 2004 03:13:33 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 22 Jun 2004 03:13:33 +0000
Received: from cantor.openldap.org (root@cantor.openldap.org [204.152.186.52])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5M3CSHI026814
	for <ietf-ldapbis@mail.OpenLDAP.org>; Tue, 22 Jun 2004 03:13:31 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from pretender.boolean.net (root@foobarlabs-pt.tunnel.tserv1.fmt.ipv6.he.net [IPv6:2001:470:1f00:ffff::797] (may be forged))
	by cantor.openldap.org (8.12.11/8.12.11) with ESMTP id i5M3CRrU081299
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 22 Jun 2004 03:12: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.11) with ESMTP id i5M3BNMC084805;
	Tue, 22 Jun 2004 03:11:23 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.1.1.0.20040621195648.048563c0@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Mon, 21 Jun 2004 20:11:32 -0700
To: Steven Legg <steven.legg@adacel.com.au>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: ListMatch Clarification
Cc: ietf-ldapbis@OpenLDAP.org
In-Reply-To: <40D79E9D.6030600@adacel.com.au>
References: <OF1A8ED09F.D3A8643D-ON86256EBA.0045DDBA-86256EBA.00490F5E@us.ibm.com>
 <Pine.GSO.4.58.0406211059580.17557@ghidora.unity.ncsu.edu>
 <6.0.1.1.0.20040621140555.04897a90@127.0.0.1>
 <40D79E9D.6030600@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-ID: ietf-ldapbis mailing list <ietf-ldapbis@OpenLDAP.org>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

At 07:51 PM 6/21/2004, Steven Legg wrote:
>I prefer to be replacing escapes in the concatenated string rather
>than adding escapes to the substrings of the substring assertion because
>the latter is heading down the direction of comparing LDAP-specific
>encodings rather than comparing abstract values. 

I actually dislike, to a lessor degree, the current note for
the same reason (but not enough to call for the note to be
removed).



Kurt 



From owner-ietf-ldapbis@OpenLDAP.org  Wed Jun 23 08:11:25 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 IAA22999
	for <ldapbis-archive@lists.ietf.org>; Wed, 23 Jun 2004 08:11:25 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5NC8xAC080420;
	Wed, 23 Jun 2004 12:09:53 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.11/8.12.11/Submit) with SMTP id i5NC6RgP080326;
	Wed, 23 Jun 2004 12:06:27 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 23 Jun 2004 12:06:27 +0000
Received: from ghidora.unity.ncsu.edu (ghidora.unity.ncsu.edu [152.1.4.40])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5NC6JET080316
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 23 Jun 2004 12:06:21 GMT
	(envelope-from daniel@unity.ncsu.edu)
Received: (from daniel@localhost)
	by ghidora.unity.ncsu.edu (8.11.7p1+Sun/8.10.2) id i5NC6Dp09003;
	Wed, 23 Jun 2004 08:06:13 -0400 (EDT)
Date: Wed, 23 Jun 2004 08:06:13 -0400 (EDT)
From: Daniel Henninger <daniel@unity.ncsu.edu>
Reply-To: daniel@ncsu.edu
To: Steven Legg <steven.legg@adacel.com.au>
cc: ietf-ldapbis@OpenLDAP.org
Subject: Re: ListMatch Clarification
In-Reply-To: <40D783AE.1060102@adacel.com.au>
Message-ID: <Pine.GSO.4.58.0406230757250.8985@ghidora.unity.ncsu.edu>
References: <OF1A8ED09F.D3A8643D-ON86256EBA.0045DDBA-86256EBA.00490F5E@us.ibm.com>
 <Pine.GSO.4.58.0406211059580.17557@ghidora.unity.ncsu.edu>
 <40D783AE.1060102@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-ID: ietf-ldapbis mailing list <ietf-ldapbis@OpenLDAP.org>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

=)  Ok, I hushed up briefly to let all the responses come in and level
off.  So one important thing I am to understand is that * is not
'wildcard', instead it means:

Foo*      Foo is at the beginning of the line
*Foo      Foo is at the end of the line
*Foo*     Foo is somewhere in the line

Is this correct?  So they are not necessarily treated as wild cards
(though they behave similarly)?

I am still not clear on *Foo*Raleigh*.  Is that equal to:
*Foo*
 and
*Raleigh*

or is it 'split up' and equal more to:
*Foo*
Raleigh*
 or
*Foo
*Raleigh*

if the latter is the case, which one wins?

If the former is the case, if I wanted to search for Foo anywhere in a
line plus Raleigh at the beginning of a line, would I need to do:
*Foo* Raleigh*
(ie, have a space separator?)


Anyway, for the List match aspect, do you just try to match each piece and
if all of the pieces match, then you have a list match?  Like you would go
through looking for a match for *Foo*.  When you found it, move in to
the Raleigh part and continue on looking for it.  If you find the Raleigh
part, great, you have a match.  Otherwise, nope?

Daniel

-- 
/\\\----------------------------------------------------------------------///\
\ \\\      Daniel Henninger           http://www.vorpalcloud.org/        /// /
 \_\\\      North Carolina State University - Systems Programmer        ///_/
    \\\                   Information Technology <IT>                  ///
     """--------------------------------------------------------------"""


From owner-ietf-ldapbis@OpenLDAP.org  Wed Jun 23 14:47: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 OAA03255
	for <ldapbis-archive@lists.ietf.org>; Wed, 23 Jun 2004 14:47:36 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5NIj1CG017850;
	Wed, 23 Jun 2004 18:45:38 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.11/8.12.11/Submit) with SMTP id i5NIfEv4017774;
	Wed, 23 Jun 2004 18:41:14 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 23 Jun 2004 18:41:14 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5NIeuQb017760
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 23 Jun 2004 18:40:57 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.11) with ESMTP id i5NIepMC002945;
	Wed, 23 Jun 2004 18:40:51 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.1.1.0.20040623111917.04970cd8@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Wed, 23 Jun 2004 11:40:57 -0700
To: daniel@ncsu.edu
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: ListMatch Clarification
Cc: Steven Legg <steven.legg@adacel.com.au>, ietf-ldapbis@OpenLDAP.org
In-Reply-To: <Pine.GSO.4.58.0406230757250.8985@ghidora.unity.ncsu.edu>
References: <OF1A8ED09F.D3A8643D-ON86256EBA.0045DDBA-86256EBA.00490F5E@us.ibm.com>
 <Pine.GSO.4.58.0406211059580.17557@ghidora.unity.ncsu.edu>
 <40D783AE.1060102@adacel.com.au>
 <Pine.GSO.4.58.0406230757250.8985@ghidora.unity.ncsu.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-ID: ietf-ldapbis mailing list <ietf-ldapbis@OpenLDAP.org>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

At 05:06 AM 6/23/2004, Daniel Henninger wrote:
>=)  Ok, I hushed up briefly to let all the responses come in and level
>off.  So one important thing I am to understand is that * is not
>'wildcard', instead it means:
>
>Foo*      Foo is at the beginning of the line

Foo is to be matched with initial portion of the value,
in this case, the beginning of the first line of the list.

>*Foo      Foo is at the end of the line

Foo is to be matched with final portion of the value,
in this case, the end of the last line of the list.

>*Foo*     Foo is somewhere in the line

Foo is to be matched with a portion of the value,
in this case, any part of any line of the list.

>I am still not clear on *Foo*Raleigh*.  Is that equal to:
>*Foo*
> and
>*Raleigh*

No, the substrings assertion *Foo*Raleigh* is not
equivalent to the AND of substrings assertions *Foo*
and *Raleigh*.

In evaluation of *Foo*Raleigh*, Foo is to matched with any
part of any line of the list and Raleigh is to be matched
with any part of any line of the list subsequent to the
part which *Foo* matched.  That is, *Foo*Raleigh* would
match Foo$Raleigh or Foo_Raleigh but not Raleigh$Foo nor
Raleigh_Foo.

>if I wanted to search for Foo anywhere in a
>line plus Raleigh at the beginning of a line, would I need to do:
>*Foo* Raleigh*
>(ie, have a space separator?)

The substrings matching rule doesn't support such assertions.
As a substrings assertions, *Foo* Raleigh* and *Foo*Raleigh*
will match the same entries as the extra leading space in
the second any string (in the first assertion) is simply
ignored.

>Anyway, for the List match aspect, do you just try to match each piece and
>if all of the pieces match, then you have a list match?  Like you would go
>through looking for a match for *Foo*.  When you found it, move in to
>the Raleigh part and continue on looking for it.  If you find the Raleigh
>part, great, you have a match.  Otherwise, nope?

It's unclear to me that your description is correct.

caseIgnoreListSubstringsMatch has the same basic substrings
semantics as caseIgnoreSubstringsMatch.  Instead of matching
against a single directory string, the former matches against
a list of directory strings (lines).  The initial substring, if
asserted, must match the beginning of the first line.  The
final substring, if asserted, must match the end of the last
line.  Each any substrings match in between.  The matched
portions must not overlap each other, must not span lines,
and must appear in the same order as the substrings.  Multiple
matched portions, however, may be in the same line... and
some lines may have no matched portions.

Kurt 



From owner-ietf-ldapbis@OpenLDAP.org  Wed Jun 23 16:17:34 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 QAA13178
	for <ldapbis-archive@lists.ietf.org>; Wed, 23 Jun 2004 16:17:34 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5NKF2aj021106;
	Wed, 23 Jun 2004 20:15:21 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.11/8.12.11/Submit) with SMTP id i5NKArEM020902;
	Wed, 23 Jun 2004 20:10: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); Wed, 23 Jun 2004 20:10:53 +0000
Received: from cantor.openldap.org (root@cantor.openldap.org [204.152.186.52])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5NKA756020838;
	Wed, 23 Jun 2004 20:10:08 GMT
	(envelope-from daniel@unity.ncsu.edu)
Received: from ghidora.unity.ncsu.edu (ghidora.unity.ncsu.edu [152.1.4.40])
	by cantor.openldap.org (8.12.11/8.12.11) with ESMTP id i5NIsXpF021427;
	Wed, 23 Jun 2004 18:54:34 GMT
	(envelope-from daniel@unity.ncsu.edu)
Received: (from daniel@localhost)
	by ghidora.unity.ncsu.edu (8.11.7p1+Sun/8.10.2) id i5NInLs12139;
	Wed, 23 Jun 2004 14:49:21 -0400 (EDT)
Date: Wed, 23 Jun 2004 14:49:21 -0400 (EDT)
From: Daniel Henninger <daniel@unity.ncsu.edu>
Reply-To: daniel@ncsu.edu
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
cc: Steven Legg <steven.legg@adacel.com.au>, ietf-ldapbis@OpenLDAP.org
Subject: Re: ListMatch Clarification
In-Reply-To: <6.0.1.1.0.20040623111917.04970cd8@127.0.0.1>
Message-ID: <Pine.GSO.4.58.0406231446590.12138@ghidora.unity.ncsu.edu>
References: <OF1A8ED09F.D3A8643D-ON86256EBA.0045DDBA-86256EBA.00490F5E@us.ibm.com>
 <Pine.GSO.4.58.0406211059580.17557@ghidora.unity.ncsu.edu>
 <40D783AE.1060102@adacel.com.au> <Pine.GSO.4.58.0406230757250.8985@ghidora.unity.ncsu.edu>
 <6.0.1.1.0.20040623111917.04970cd8@127.0.0.1>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-ID: ietf-ldapbis mailing list <ietf-ldapbis@OpenLDAP.org>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

> caseIgnoreListSubstringsMatch has the same basic substrings
> semantics as caseIgnoreSubstringsMatch.  Instead of matching
> against a single directory string, the former matches against
> a list of directory strings (lines).  The initial substring, if
> asserted, must match the beginning of the first line.  The
> final substring, if asserted, must match the end of the last
> line.  Each any substrings match in between.  The matched
> portions must not overlap each other, must not span lines,
> and must appear in the same order as the substrings.  Multiple
> matched portions, however, may be in the same line... and
> some lines may have no matched portions.


Ok so, caseIgnoreListSubstringsMatch is no different than
caseIgnoreSubstringsMatch -except- for:

A. the list is effectively concatenated into one line
B. there are "markers" where there were line breaks that no single pattern
   can cross
C. \'s and $'s are handled so that they can be escaped out

Does that sound right?

Daniel

-- 
/\\\----------------------------------------------------------------------///\
\ \\\      Daniel Henninger           http://www.vorpalcloud.org/        /// /
 \_\\\      North Carolina State University - Systems Programmer        ///_/
    \\\                   Information Technology <IT>                  ///
     """--------------------------------------------------------------"""


From owner-ietf-ldapbis@OpenLDAP.org  Wed Jun 23 16:22: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 QAA13539
	for <ldapbis-archive@lists.ietf.org>; Wed, 23 Jun 2004 16:22:09 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5NKL2vN021386;
	Wed, 23 Jun 2004 20:21:04 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.11/8.12.11/Submit) with SMTP id i5NKFewC021136;
	Wed, 23 Jun 2004 20:15:40 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 23 Jun 2004 20:15:40 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5NKFObg021119
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 23 Jun 2004 20:15:25 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.11) with ESMTP id i5NKFAMC003385;
	Wed, 23 Jun 2004 20:15:10 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.1.1.0.20040623131434.02c8c7b0@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Wed, 23 Jun 2004 13:15:16 -0700
To: daniel@ncsu.edu
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: ListMatch Clarification
Cc: Steven Legg <steven.legg@adacel.com.au>, ietf-ldapbis@OpenLDAP.org
In-Reply-To: <Pine.GSO.4.58.0406231446590.12138@ghidora.unity.ncsu.edu>
References: <OF1A8ED09F.D3A8643D-ON86256EBA.0045DDBA-86256EBA.00490F5E@us.ibm.com>
 <Pine.GSO.4.58.0406211059580.17557@ghidora.unity.ncsu.edu>
 <40D783AE.1060102@adacel.com.au>
 <Pine.GSO.4.58.0406230757250.8985@ghidora.unity.ncsu.edu>
 <6.0.1.1.0.20040623111917.04970cd8@127.0.0.1>
 <Pine.GSO.4.58.0406231446590.12138@ghidora.unity.ncsu.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-ID: ietf-ldapbis mailing list <ietf-ldapbis@OpenLDAP.org>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

At 11:49 AM 6/23/2004, Daniel Henninger wrote:
>> caseIgnoreListSubstringsMatch has the same basic substrings
>> semantics as caseIgnoreSubstringsMatch.  Instead of matching
>> against a single directory string, the former matches against
>> a list of directory strings (lines).  The initial substring, if
>> asserted, must match the beginning of the first line.  The
>> final substring, if asserted, must match the end of the last
>> line.  Each any substrings match in between.  The matched
>> portions must not overlap each other, must not span lines,
>> and must appear in the same order as the substrings.  Multiple
>> matched portions, however, may be in the same line... and
>> some lines may have no matched portions.
>
>
>Ok so, caseIgnoreListSubstringsMatch is no different than
>caseIgnoreSubstringsMatch -except- for:
>
>A. the list is effectively concatenated into one line
>B. there are "markers" where there were line breaks that no single pattern
>   can cross
>C. \'s and $'s are handled so that they can be escaped out
>
>Does that sound right?

Yes. 



From owner-ietf-ldapbis@OpenLDAP.org  Mon Jun 28 14:07: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 OAA20061
	for <ldapbis-archive@lists.ietf.org>; Mon, 28 Jun 2004 14:07:37 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5SI3nom059209;
	Mon, 28 Jun 2004 18:05:50 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.11/8.12.11/Submit) with SMTP id i5SHwmlQ059015;
	Mon, 28 Jun 2004 17:58: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, 28 Jun 2004 17:58:48 +0000
Received: from ghidora.unity.ncsu.edu (ghidora.unity.ncsu.edu [152.1.4.40])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5SHuvs6058923;
	Mon, 28 Jun 2004 17:58:01 GMT
	(envelope-from daniel@unity.ncsu.edu)
Received: (from daniel@localhost)
	by ghidora.unity.ncsu.edu (8.11.7p1+Sun/8.10.2) id i5SHuue10867;
	Mon, 28 Jun 2004 13:56:56 -0400 (EDT)
Date: Mon, 28 Jun 2004 13:56:56 -0400 (EDT)
From: Daniel Henninger <daniel@unity.ncsu.edu>
Reply-To: daniel@ncsu.edu
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
cc: Steven Legg <steven.legg@adacel.com.au>, ietf-ldapbis@OpenLDAP.org
Subject: Re: ListMatch Clarification
In-Reply-To: <6.0.1.1.0.20040623131434.02c8c7b0@127.0.0.1>
Message-ID: <Pine.GSO.4.58.0406281349420.10854@ghidora.unity.ncsu.edu>
References: <OF1A8ED09F.D3A8643D-ON86256EBA.0045DDBA-86256EBA.00490F5E@us.ibm.com>
 <Pine.GSO.4.58.0406211059580.17557@ghidora.unity.ncsu.edu>
 <40D783AE.1060102@adacel.com.au> <Pine.GSO.4.58.0406230757250.8985@ghidora.unity.ncsu.edu>
 <6.0.1.1.0.20040623111917.04970cd8@127.0.0.1>
 <Pine.GSO.4.58.0406231446590.12138@ghidora.unity.ncsu.edu>
 <6.0.1.1.0.20040623131434.02c8c7b0@127.0.0.1>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-ID: ietf-ldapbis mailing list <ietf-ldapbis@OpenLDAP.org>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

> >> caseIgnoreListSubstringsMatch has the same basic substrings
> >> semantics as caseIgnoreSubstringsMatch.  Instead of matching
> >> against a single directory string, the former matches against
> >> a list of directory strings (lines).  The initial substring, if
> >> asserted, must match the beginning of the first line.  The
> >> final substring, if asserted, must match the end of the last
> >> line.  Each any substrings match in between.  The matched
> >> portions must not overlap each other, must not span lines,
> >> and must appear in the same order as the substrings.  Multiple
> >> matched portions, however, may be in the same line... and
> >> some lines may have no matched portions.
> >
> >
> >Ok so, caseIgnoreListSubstringsMatch is no different than
> >caseIgnoreSubstringsMatch -except- for:
> >
> >A. the list is effectively concatenated into one line
> >B. there are "markers" where there were line breaks that no single pattern
> >   can cross
> >C. \'s and $'s are handled so that they can be escaped out
> >
> >Does that sound right?
>
> Yes.

Excellent.  So I've been looking at what it would take to implement this,
and here is how I "think I should implement it".  I'd definitely like
feedback before going through with this.  I also have a side question, but
I'll get to this.  First of all, here's how I propose that I would
implement this:

given: A. is the query string
       B. is the entity within the ldap db I am comparing against

1. convert A to "escaped" format by running that escape command on it
   (assuming that is a real command  haven't looked at that)  escape
   out $ and \

2. convert B by turning the line separator $ into a ^M (ctrl-M)  (or a \n
   not sure which would be better there)

3. turn the converted A and B over to caseIgnoreSubstringsMatch for
   comparison

This does mean that an added side effect is that you could actually
-match- those newlines using ^M or \n, depending on which were used.
Personally, I don't think anything is wrong with that.  ;)

If I can do that, then my second question is moot.  If I can not allow the
newline to be matchable at all, then how is it possible to do a
non-substrings match?

Daniel

-- 
/\\\----------------------------------------------------------------------///\
\ \\\      Daniel Henninger           http://www.vorpalcloud.org/        /// /
 \_\\\      North Carolina State University - Systems Programmer        ///_/
    \\\                   Information Technology <IT>                  ///
     """--------------------------------------------------------------"""


From owner-ietf-ldapbis@OpenLDAP.org  Mon Jun 28 21:12: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 VAA28647
	for <ldapbis-archive@lists.ietf.org>; Mon, 28 Jun 2004 21:12:06 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5T1A23C072965;
	Tue, 29 Jun 2004 01:10:32 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.11/8.12.11/Submit) with SMTP id i5T17du3072928;
	Tue, 29 Jun 2004 01:07:39 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
X-Authentication-Warning: boole.openldap.org: majordomo owned process doing -bs
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 29 Jun 2004 01:07:39 +0000
Received: from adacel.com (gunsmoke.adacel.com.au [210.11.130.7])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5T16GsK072871
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 29 Jun 2004 01:07:29 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.6.7)
	id <B0002853b5>; Tue, 29 Jun 2004 11:04:27 +1000
Received: (qmail 23436 invoked from network); 29 Jun 2004 01:05:55 -0000
Received: from unknown (HELO adacel.com.au) (10.32.24.165)
  by nexus.adacel.com with SMTP; 29 Jun 2004 01:05:55 -0000
Message-ID: <40E0C072.5060701@adacel.com.au>
Date: Tue, 29 Jun 2004 11:05:54 +1000
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: daniel@ncsu.edu
CC: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>, ietf-ldapbis@OpenLDAP.org
Subject: Re: ListMatch Clarification
References: <OF1A8ED09F.D3A8643D-ON86256EBA.0045DDBA-86256EBA.00490F5E@us.ibm.com> <Pine.GSO.4.58.0406211059580.17557@ghidora.unity.ncsu.edu> <40D783AE.1060102@adacel.com.au> <Pine.GSO.4.58.0406230757250.8985@ghidora.unity.ncsu.edu> <6.0.1.1.0.20040623111917.04970cd8@127.0.0.1> <Pine.GSO.4.58.0406231446590.12138@ghidora.unity.ncsu.edu> <6.0.1.1.0.20040623131434.02c8c7b0@127.0.0.1> <Pine.GSO.4.58.0406281349420.10854@ghidora.unity.ncsu.edu>
In-Reply-To: <Pine.GSO.4.58.0406281349420.10854@ghidora.unity.ncsu.edu>
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-ID: ietf-ldapbis mailing list <ietf-ldapbis@OpenLDAP.org>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


Daniel,

Daniel Henninger wrote:
>>>>caseIgnoreListSubstringsMatch has the same basic substrings
>>>>semantics as caseIgnoreSubstringsMatch.  Instead of matching
>>>>against a single directory string, the former matches against
>>>>a list of directory strings (lines).  The initial substring, if
>>>>asserted, must match the beginning of the first line.  The
>>>>final substring, if asserted, must match the end of the last
>>>>line.  Each any substrings match in between.  The matched
>>>>portions must not overlap each other, must not span lines,
>>>>and must appear in the same order as the substrings.  Multiple
>>>>matched portions, however, may be in the same line... and
>>>>some lines may have no matched portions.
>>>
>>>
>>>Ok so, caseIgnoreListSubstringsMatch is no different than
>>>caseIgnoreSubstringsMatch -except- for:
>>>
>>>A. the list is effectively concatenated into one line
>>>B. there are "markers" where there were line breaks that no single pattern
>>>  can cross
>>>C. \'s and $'s are handled so that they can be escaped out
>>>
>>>Does that sound right?
>>
>>Yes.
> 
> 
> Excellent.  So I've been looking at what it would take to implement this,
> and here is how I "think I should implement it".  I'd definitely like
> feedback before going through with this.  I also have a side question, but
> I'll get to this.  First of all, here's how I propose that I would
> implement this:
> 
> given: A. is the query string
>        B. is the entity within the ldap db I am comparing against
> 
> 1. convert A to "escaped" format by running that escape command on it
>    (assuming that is a real command  haven't looked at that)  escape
>    out $ and \

Our implementation unescapes B and stores it as a list of lines. This is
closer to the spirit of X.500. Escaping A should have the same effect as far
as I can see, but there are nuances to deal with.

> 
> 2. convert B by turning the line separator $ into a ^M (ctrl-M)  (or a \n
>    not sure which would be better there)

Why change the $ separator ? If you have escaped $ in the assertion substrings
then none of the substrings can match a literal $ in B. What you will need to
do though is escape any *'s in B because they are already escaped in A. All this
assumes that the routine for matching substrings is doing a literal character
comparison and is ignorant of character escapes.

> 
> 3. turn the converted A and B over to caseIgnoreSubstringsMatch for
>    comparison
> 
> This does mean that an added side effect is that you could actually
> -match- those newlines using ^M or \n, depending on which were used.
> Personally, I don't think anything is wrong with that.  ;)

It would not be conformant with the specification of caseIgnoreListSubstringsMatch.

> 
> If I can do that, then my second question is moot.  If I can not allow the
> newline to be matchable at all, then how is it possible to do a
> non-substrings match?

1) Don't map the $'s in B to anything else. Do escape the *'s in B.

OR

2) The description of caseIgnoreListSubstringsMatch depends on the description
of caseIgnoreSubstringsMatch but that doesn't mean it must necessarily be
implemented that way. Our implementation uses a separate function for
caseIgnoreListSubstringsMatch. It attempts to match as many of the assertion
substrings as it can in the first line (where an initial substring must match
the beginning of the first line). If there are any left over it attempts
to match the remainder on the second line. If there are still some left over it
attempts to match the new remainder on the third line, and so on. If all the substrings
get matched, and any final substring matches the end of the last line, then success!

Since we store B as a list of separately terminated lines (and do much the same for A)
there is no need to worry about separators or escaping (except to undo it on input).

Regards,
Steven

> 
> Daniel
> 



From owner-ietf-ldapbis@OpenLDAP.org  Mon Jun 28 21:23: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 VAA29061
	for <ldapbis-archive@lists.ietf.org>; Mon, 28 Jun 2004 21:23:29 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5T1LmJo073334;
	Tue, 29 Jun 2004 01:21:49 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.11/8.12.11/Submit) with SMTP id i5T1Gr3V073256;
	Tue, 29 Jun 2004 01:16: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); Tue, 29 Jun 2004 01:16:53 +0000
Received: from ghidora.unity.ncsu.edu (ghidora.unity.ncsu.edu [152.1.4.40])
	by boole.openldap.org (8.12.11/8.12.11) with ESMTP id i5T1Fd0F073146
	for <ietf-ldapbis@openldap.org>; Tue, 29 Jun 2004 01:16:43 GMT
	(envelope-from daniel@unity.ncsu.edu)
Received: (from daniel@localhost)
	by ghidora.unity.ncsu.edu (8.11.7p1+Sun/8.10.2) id i5T1FcT11414;
	Mon, 28 Jun 2004 21:15:38 -0400 (EDT)
Date: Mon, 28 Jun 2004 21:13:54 -0400 (EDT)
From: daniel@unity.ncsu.edu
Reply-To: daniel@ncsu.edu
To: Steven Legg <steven.legg@adacel.com.au>
cc: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>, ietf-ldapbis@OpenLDAP.org
Subject: Re: ListMatch Clarification
In-Reply-To: <40E0C072.5060701@adacel.com.au>
Message-ID: <Pine.OSX.4.58.0406282110490.3547@katana.vorpalcloud.org>
References: <OF1A8ED09F.D3A8643D-ON86256EBA.0045DDBA-86256EBA.00490F5E@us.ibm.com>
 <Pine.GSO.4.58.0406211059580.17557@ghidora.unity.ncsu.edu>
 <40D783AE.1060102@adacel.com.au> <Pine.GSO.4.58.0406230757250.8985@ghidora.unity.ncsu.edu>
 <6.0.1.1.0.20040623111917.04970cd8@127.0.0.1>
 <Pine.GSO.4.58.0406231446590.12138@ghidora.unity.ncsu.edu>
 <6.0.1.1.0.20040623131434.02c8c7b0@127.0.0.1>
 <Pine.GSO.4.58.0406281349420.10854@ghidora.unity.ncsu.edu>
 <40E0C072.5060701@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-ID: ietf-ldapbis mailing list <ietf-ldapbis@OpenLDAP.org>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

Aiyee!  Ok, folk, I'm sorry.  I'm apparantly just not getting what the
goal is with these list matches.  I keep hearing what sound like, to me,
conflicting definitions of how it should work.  I am going to humbly back
off and continue to use openldap as is until someone else who is more
familiar with the standard and the code has some time to implement
listmatches.  Sorry folk.  Thanks much for all the help and
explanations regardless!

Daniel


> Daniel,
>
> Daniel Henninger wrote:
> >>>>caseIgnoreListSubstringsMatch has the same basic substrings
> >>>>semantics as caseIgnoreSubstringsMatch.  Instead of matching
> >>>>against a single directory string, the former matches against
> >>>>a list of directory strings (lines).  The initial substring, if
> >>>>asserted, must match the beginning of the first line.  The
> >>>>final substring, if asserted, must match the end of the last
> >>>>line.  Each any substrings match in between.  The matched
> >>>>portions must not overlap each other, must not span lines,
> >>>>and must appear in the same order as the substrings.  Multiple
> >>>>matched portions, however, may be in the same line... and
> >>>>some lines may have no matched portions.
> >>>
> >>>
> >>>Ok so, caseIgnoreListSubstringsMatch is no different than
> >>>caseIgnoreSubstringsMatch -except- for:
> >>>
> >>>A. the list is effectively concatenated into one line
> >>>B. there are "markers" where there were line breaks that no single pattern
> >>>  can cross
> >>>C. \'s and $'s are handled so that they can be escaped out
> >>>
> >>>Does that sound right?
> >>
> >>Yes.
> >
> >
> > Excellent.  So I've been looking at what it would take to implement this,
> > and here is how I "think I should implement it".  I'd definitely like
> > feedback before going through with this.  I also have a side question, but
> > I'll get to this.  First of all, here's how I propose that I would
> > implement this:
> >
> > given: A. is the query string
> >        B. is the entity within the ldap db I am comparing against
> >
> > 1. convert A to "escaped" format by running that escape command on it
> >    (assuming that is a real command  haven't looked at that)  escape
> >    out $ and \
>
> Our implementation unescapes B and stores it as a list of lines. This is
> closer to the spirit of X.500. Escaping A should have the same effect as far
> as I can see, but there are nuances to deal with.
>
> >
> > 2. convert B by turning the line separator $ into a ^M (ctrl-M)  (or a \n
> >    not sure which would be better there)
>
> Why change the $ separator ? If you have escaped $ in the assertion substrings
> then none of the substrings can match a literal $ in B. What you will need to
> do though is escape any *'s in B because they are already escaped in A. All this
> assumes that the routine for matching substrings is doing a literal character
> comparison and is ignorant of character escapes.
>
> >
> > 3. turn the converted A and B over to caseIgnoreSubstringsMatch for
> >    comparison
> >
> > This does mean that an added side effect is that you could actually
> > -match- those newlines using ^M or \n, depending on which were used.
> > Personally, I don't think anything is wrong with that.  ;)
>
> It would not be conformant with the specification of caseIgnoreListSubstringsMatch.
>
> >
> > If I can do that, then my second question is moot.  If I can not allow the
> > newline to be matchable at all, then how is it possible to do a
> > non-substrings match?
>
> 1) Don't map the $'s in B to anything else. Do escape the *'s in B.
>
> OR
>
> 2) The description of caseIgnoreListSubstringsMatch depends on the description
> of caseIgnoreSubstringsMatch but that doesn't mean it must necessarily be
> implemented that way. Our implementation uses a separate function for
> caseIgnoreListSubstringsMatch. It attempts to match as many of the assertion
> substrings as it can in the first line (where an initial substring must match
> the beginning of the first line). If there are any left over it attempts
> to match the remainder on the second line. If there are still some left over it
> attempts to match the new remainder on the third line, and so on. If all the substrings
> get matched, and any final substring matches the end of the last line, then success!
>
> Since we store B as a list of separately terminated lines (and do much the same for A)
> there is no need to worry about separators or escaping (except to undo it on input).
>
> Regards,
> Steven
>
> >
> > Daniel
> >
>
>

-- 
/\\\----------------------------------------------------------------------///\
\ \\\      Daniel Henninger           http://www.vorpalcloud.org/        /// /
 \_\\\      North Carolina State University - Systems Programmer        ///_/
    \\\                   Information Technology <IT>                  ///
     """--------------------------------------------------------------"""


