From owner-ietf-ldapbis@OpenLDAP.org  Tue Jul  1 07:31:45 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA08048
	for <ldapbis-archive@lists.ietf.org>; Tue, 1 Jul 2003 07:31:45 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h61BQdkf026649;
	Tue, 1 Jul 2003 11:29:54 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h61BNIFf026533;
	Tue, 1 Jul 2003 11:23:18 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 1 Jul 2003 11:23:18 +0000
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h61BNGkb026522
	for <ietf-ldapbis@openldap.org>; Tue, 1 Jul 2003 11:23:16 GMT
	(envelope-from nsyracus@cnri.reston.va.us)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA07174;
	Tue, 1 Jul 2003 07:23:08 -0400 (EDT)
Message-Id: <200307011123.HAA07174@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: ietf-ldapbis@OpenLDAP.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-ldapbis-protocol-15.txt
Date: Tue, 01 Jul 2003 07:23:04 -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: The Protocol
	Author(s)	: J. Sermersheim
	Filename	: draft-ietf-ldapbis-protocol-15.txt
	Pages		: 63
	Date		: 2003-6-30
	
This document describes the protocol elements, along with their 
semantics and encodings, for the Lightweight Directory Access 
Protocol (LDAP). LDAP provides access to distributed directory 
services that act in accordance with X.500 data and service models. 
These protocol elements are based on those described in the X.500 
Directory Access Protocol (DAP).

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

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

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

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


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

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

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

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

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

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

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

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

--OtherAccess--

--NextPart--




From owner-ietf-ldapbis@OpenLDAP.org  Tue Jul  1 14:18:42 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09824
	for <ldapbis-archive@lists.ietf.org>; Tue, 1 Jul 2003 14:18:31 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h61I8flJ062685;
	Tue, 1 Jul 2003 18:17:02 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h61I7Wvi062634;
	Tue, 1 Jul 2003 18:07:32 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 1 Jul 2003 18:07:32 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h61I7Ukb062624
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 1 Jul 2003 18:07:30 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from nomad.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.8/8.12.8) with ESMTP id h61I7Uc6058234
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 1 Jul 2003 18:07:30 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030701104945.01d18f80@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Tue, 01 Jul 2003 11:04:26 -0700
To: ietf-ldapbis@OpenLDAP.org
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: Updating our milestones
In-Reply-To: <5.2.0.9.0.20030618135340.01ad52d8@127.0.0.1>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

After consider input (mostly off-list discussions with
the editors) and our current status, the chairs will
re-negotiate our milestones based upon proposal below
with minor changes  While we expect the WG to complete
required WG Last Calls by the end of August as discussed,
additional time is needed to turn the documents around.
Hence, September deliver dates will be requested for the
first two milestones.

Kurt, LDAPBIS co-chair


At 02:14 PM 6/18/2003, Kurt D. Zeilenga wrote:
>Our milestones need to be renegotiated.  In has been proposed
>that our current uncompleted milestones be replaced with:
>
>        Aug 03 Deliver revised LDAP "core" TS to the IESG for
>              consideration as a Proposed Standard
>        Aug 03 Deliver revised BCP 64 I-D to IESG for
>              consideration to the IESG as a BCP
>        Oct 03 Submit Interoperability Report I-D
>        Apr 04 Deliver Interoperability Report to IESG with
>              recommendation that revised LDAP "core" TS be
>              promoted to Draft Standard. 
>
>The chairs plan to make a decision in the next few weeks
>on this proposal and solicits your comments on it.
>Please send any comments to this list (or, if
>necessary, directly to the chairs) by 30 June 2003.
>
>Kurt, LDAPBIS co-chair  



From owner-ietf-ldapbis@OpenLDAP.org  Tue Jul  1 15:21:04 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13366
	for <ldapbis-archive@lists.ietf.org>; Tue, 1 Jul 2003 15:21:04 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h61JEfkt067807;
	Tue, 1 Jul 2003 19:19:22 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h61J99O2067621;
	Tue, 1 Jul 2003 19:09:09 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 1 Jul 2003 19:09:09 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h61J8ukb067610
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 1 Jul 2003 19:08:56 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from nomad.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.8/8.12.8) with ESMTP id h61J8rc6058806;
	Tue, 1 Jul 2003 19:08:54 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030701113558.01d59e48@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Tue, 01 Jul 2003 12:05:49 -0700
To: "Jim Sermersheim" <jimse@novell.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: WG consensus Re: Extensibility of SearchRequest.attributes
Cc: <ietf-ldapbis@OpenLDAP.org>
In-Reply-To: <5.2.0.9.0.20030403205848.02251550@127.0.0.1>
References: <se8b02a5.011@prv-mail20.provo.novell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

As co-chair, I have reviewed this thread:
  http://www.openldap.org/lists/ietf-ldapbis/200304/msg00002.html

and draw two conclusions.

1) Concern was raised that the specification makes conflicting
statements regarding AttributeDescriptionList contents.  Consensus
supports clarifying the ASN.1 and related ABNF that an
AttributeDescriptionList is a SEQUENCE of LDAPString where the
LDAPString is either "*" or an <AttributeDescription>.  The editor
should make appropriate changes to address this issue.  Once
made, the WG will be asked to review the changes to ensure they
adequately address this issue.

2) Concern was raised regarding the extensibility of
AttributeDescriptionList to support additional "specials".
Consensus does not support adding text to the LDAP "core" TS
as to how to extend the set of allowed specials.  It should be
noted that the lack of a statement allowing extensions does not
preclude future (or existing) specifications from detailing
such extensions.  It is assume that appropriate care will be
taken in engineering such extensions when and where they are
desirable.  This issue is now considered resolved.

Kurt, LDAPBIS co-chair



From owner-ietf-ldapbis@OpenLDAP.org  Tue Jul  1 20:06:10 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA21765
	for <ldapbis-archive@lists.ietf.org>; Tue, 1 Jul 2003 20:06:09 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6202hkf088664;
	Wed, 2 Jul 2003 00:04:43 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h6202Ucl088656;
	Wed, 2 Jul 2003 00:02:30 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 2 Jul 2003 00:02:30 +0000
Received: from prv-mail20.provo.novell.com (prv-mail20.provo.novell.com [137.65.81.122])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6202Tkb088646
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 2 Jul 2003 00:02:29 GMT
	(envelope-from RHARRISON@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Tue, 01 Jul 2003 18:02:08 -0600
Message-Id: <sf01cca0.066@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.1 
Date: Tue, 01 Jul 2003 17:18:05 -0600
From: "Roger Harrison" <RHARRISON@novell.com>
To: <ietf-ldapbis@OpenLDAP.org>
Subject: [authmeth] effect of StartTLS on authentication state
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__PartFEA0CEBD.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.

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

A WG member has asked whether the server should drop all knowledge of
the connection, i.e. return to anonymous state, if it gets a StartTLS
request on a connection that has successfully bound using the simple
method. I believe that the intent of section 5 the authmeth draft is
clear on this point: if the association is in state S4 (authenticated
but no TLS) and the client performs action A3 (sends a Start TLS
request), then the next association state is S5 (authenticated with
TLS).
 
My understanding of existing implementations leads me to believe that
this is the generally accepted understanding of the way this should
work.  I can't see any serious security issues with maintaining this
behavior. Therefore, I propose that we do not change this requirement. 
I will consider adding wording to clarify this point if WG members
request it.
 
Please respond with your opinions.
 
Thanks,
 
Roger

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

<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1169" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Tahoma">
<DIV>A WG member has asked whether the server should drop all knowledge of the connection, i.e. return to anonymous state, if it gets a StartTLS request on a connection that has successfully bound using the simple method. I believe that the intent of section 5 the authmeth draft is clear on this point: if the association is in state S4 (authenticated but no TLS) and the client performs action A3 (sends a Start TLS request), then the next association state is S5 (authenticated with TLS).</DIV>
<DIV>&nbsp;</DIV>
<DIV>My understanding of existing implementations leads me to believe that this is the generally accepted understanding of the way this should work.&nbsp; I can't see any serious security issues with maintaining this behavior. Therefore, I propose that we do not change this requirement.&nbsp; I will consider adding wording to clarify this point if WG members request it.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Please respond with your opinions.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Thanks,</DIV>
<DIV>&nbsp;</DIV>
<DIV>Roger</DIV></BODY></HTML>
--=__PartFEA0CEBD.0__=--


From owner-ietf-ldapbis@OpenLDAP.org  Tue Jul  1 22:16:33 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA24996
	for <ldapbis-archive@lists.ietf.org>; Tue, 1 Jul 2003 22:16:32 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6228hkr091901;
	Wed, 2 Jul 2003 02:15:03 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h6223N0m091773;
	Wed, 2 Jul 2003 02:03:23 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 2 Jul 2003 02:03:23 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6223Ikb091748
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 2 Jul 2003 02:03:18 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from nomad.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.8/8.12.8) with ESMTP id h6223Gc6061841;
	Wed, 2 Jul 2003 02:03:16 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030701171553.01da9e50@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Tue, 01 Jul 2003 19:00:12 -0700
To: "Roger Harrison" <RHARRISON@novell.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: [authmeth] effect of StartTLS on authentication state
Cc: <ietf-ldapbis@OpenLDAP.org>
In-Reply-To: <sf01cca0.066@prv-mail20.provo.novell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

The obvious security consideration is that a client which does:
        StartTLS+simple
and a client which does
        simple+StartTLS

would (assuming both provided the same credentials and the negotiated
the same security layers, association state diagram were followed)
achieve the same apparent authorization state and protection levels when,
in fact, the latter approach is prone to a number of obvious attacks.

For the life of me, I cannot imagine why a client would do
    simple+StartTLS+modify
or even
    simple+StartTLS+search-for-user-application-objects

If the exchanged information is sensitive enough to warrant starting TLS,
then it follows that password which provides access to that information is
equally sensitive and should be protected by TLS.

It's my opinion that the RFC 2830, section 5.1.1 absolute
imperative is inappropriate and actually in conflict with section 3.1.
Authorization state diagram aside (its not normative), if a client does
simple+StartTLS+X, the server is free, per section 3.1, to return
strongAuthRequired for X.  And if 3.1 isn't enough, please consider
access and administrative control models behavior is a local matter and
servers are free to return security codes as necessary to implement
the model they support.  Also, nothing in the LDAP TS should be viewed
as precluding from lowering the effective access rights or otherwise
placing restrictions upon clients for this or any other reason.

It is not only reasonable that servers treat StartTLS+simple differently
than simple+StartTLS, it makes good sense from a security perspective.  I
believe that the OpenLDAP behavior (which is policy driven) of forcing the
session to anonymous upon StartTLS has significantly improved the security
of the Internet.  There are a lot less clients doing simple+StartTLS now
and that is, IMO, a good thing.

Kurt


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



From owner-ietf-ldapbis@OpenLDAP.org  Tue Jul  1 22:43:24 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA25423
	for <ldapbis-archive@lists.ietf.org>; Tue, 1 Jul 2003 22:43:24 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h622chkf093263;
	Wed, 2 Jul 2003 02:42:33 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h622b3KU093129;
	Wed, 2 Jul 2003 02:37:03 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 2 Jul 2003 02:37:03 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h622aqkb093119
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 2 Jul 2003 02:36:52 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from nomad.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.8/8.12.8) with ESMTP id h622apc6062065;
	Wed, 2 Jul 2003 02:36:51 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030701192833.01da9220@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Tue, 01 Jul 2003 19:33:47 -0700
To: "Roger Harrison" <RHARRISON@novell.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: [authmeth] effect of StartTLS on authentication state
Cc: <ietf-ldapbis@OpenLDAP.org>
In-Reply-To: <5.2.0.9.0.20030701171553.01da9e50@127.0.0.1>
References: <sf01cca0.066@prv-mail20.provo.novell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

At 07:00 PM 7/1/2003, Kurt D. Zeilenga wrote:
>It's my opinion that the RFC 2830, section 5.1.1 absolute
>imperative is inappropriate and actually in conflict with section 3.1.

I misread section 3.1.  It doesn't cover this case (as StartTLS
as been initiated) so is not in conflict with 5.1.1.  Regardless,
I still believe the server is free to return strongAuthRequired
at any time it considers the in force association to be inappropriate
for the requested operation.   Hence, the server may, in effect,
move the association to anonymous after StartTLS.

Kurt 



From owner-ietf-ldapbis@OpenLDAP.org  Wed Jul  2 07:05:47 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA04198
	for <ldapbis-archive@lists.ietf.org>; Wed, 2 Jul 2003 07:05:47 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h62B4Nkd014021;
	Wed, 2 Jul 2003 11:04:38 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h62AtZLU013303;
	Wed, 2 Jul 2003 10:55:35 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 2 Jul 2003 10:55:35 +0000
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h62AtWkb013293
	for <ietf-ldapbis@openldap.org>; Wed, 2 Jul 2003 10:55:33 GMT
	(envelope-from nsyracus@cnri.reston.va.us)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02664;
	Wed, 2 Jul 2003 06:55:31 -0400 (EDT)
Message-Id: <200307021055.GAA02664@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: ietf-ldapbis@OpenLDAP.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-ldapbis-roadmap-03.txt
Date: Wed, 02 Jul 2003 06:55:31 -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: Technical Specification Road Map
	Author(s)	: K. Zeilenga
	Filename	: draft-ietf-ldapbis-roadmap-03.txt
	Pages		: 6
	Date		: 2003-7-1
	
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-03.txt

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

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-ldapbis-roadmap-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-roadmap-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:	<2003-7-1134554.I-D@ietf.org>

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

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

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

--OtherAccess--

--NextPart--




From owner-ietf-ldapbis@OpenLDAP.org  Wed Jul  2 07:06:15 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA04232
	for <ldapbis-archive@lists.ietf.org>; Wed, 2 Jul 2003 07:06:14 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h62Aukl5013333;
	Wed, 2 Jul 2003 11:05:12 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h62AtTgi013286;
	Wed, 2 Jul 2003 10:55:29 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 2 Jul 2003 10:55:29 +0000
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h62AtRkb013276
	for <ietf-ldapbis@openldap.org>; Wed, 2 Jul 2003 10:55:27 GMT
	(envelope-from nsyracus@cnri.reston.va.us)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02629;
	Wed, 2 Jul 2003 06:55:25 -0400 (EDT)
Message-Id: <200307021055.GAA02629@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: ietf-ldapbis@OpenLDAP.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-ldapbis-strprep-01.txt
Date: Wed, 02 Jul 2003 06:55:25 -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-01.txt
	Pages		: 18
	Date		: 2003-7-1
	
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-01.txt

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

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

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


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

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

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

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

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

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

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

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

--OtherAccess--

--NextPart--




From owner-ietf-ldapbis@OpenLDAP.org  Wed Jul  2 07:54:40 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA04199
	for <ldapbis-archive@lists.ietf.org>; Wed, 2 Jul 2003 07:05:47 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h62B4Nkb014021;
	Wed, 2 Jul 2003 11:04:23 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h62Ate89013320;
	Wed, 2 Jul 2003 10:55:40 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 2 Jul 2003 10:55:40 +0000
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h62Atckb013310
	for <ietf-ldapbis@openldap.org>; Wed, 2 Jul 2003 10:55:38 GMT
	(envelope-from nsyracus@cnri.reston.va.us)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02683;
	Wed, 2 Jul 2003 06:55:37 -0400 (EDT)
Message-Id: <200307021055.GAA02683@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: ietf-ldapbis@OpenLDAP.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-ldapbis-dn-11.txt
Date: Wed, 02 Jul 2003 06:55:36 -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-11.txt
	Pages		: 14
	Date		: 2003-7-1
	
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-11.txt

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

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-ldapbis-dn-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-dn-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:	<2003-7-1134609.I-D@ietf.org>

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

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

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

--OtherAccess--

--NextPart--




From owner-ietf-ldapbis@OpenLDAP.org  Wed Jul  2 13:29:50 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03373
	for <ldapbis-archive@lists.ietf.org>; Wed, 2 Jul 2003 13:29:47 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h62HQmkf047391;
	Wed, 2 Jul 2003 17:28:53 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h62HOS4H047284;
	Wed, 2 Jul 2003 17:24:28 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 2 Jul 2003 17:24:28 +0000
Received: from goose.ehsco.com (goose.ehsco.com [207.65.203.98])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h62HOOkb047273
	for <ietf-ldapbis@openldap.org>; Wed, 2 Jul 2003 17:24:25 GMT
	(envelope-from ehall@ehsco.com)
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.0.6)
  with ESMTP-TLS id 260374; Wed, 02 Jul 2003 12:24:04 -0500
Message-ID: <3F031543.60901@ehsco.com>
Date: Wed, 02 Jul 2003 12:24:19 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: Jim Sermersheim <jimse@novell.com>
CC: mcs@netscape.com, Steve McLain <SMCLAIN@novell.com>,
        Tom Doman <TDoman.PRV-1.PROVO@novell.com>, ietf-ldapbis@OpenLDAP.org
Subject: Re: Specifying non-tcp transports referrals
References: <sefae9e6.075@prv-mail20.provo.novell.com>
In-Reply-To: <sefae9e6.075@prv-mail20.provo.novell.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


on 6/26/2003 1:39 PM Jim Sermersheim wrote:

>>The only well defined transport for LDAP is TCP. So I just assume that
>>LDAP URLs must use TCP as a transport too. Are you saying that is too
>>limiting?
> 
> I'm just saying that it's under specified or ambiguous (I actually
> don't know if LDAP URLs can be used to specify transports other than
> TCP--I'd like it to be able to).

I've changed my mind on this and agree with Jim. I think that the proper
way to specify transports is to extend the hostport syntax to allow for
transport.port or transport/port whatever is necessary, with [tcp] being
the default when a transport is not explicitly declared.

This approach would allow a single URL to specify multiple transports, and
would preserve the transport/protocol mapping. It also preserves the
authority that "valid" transports are defined by the LDAP service and not
by URLs.

This can be synchronized with SRV with the right text. eg, ~"use the
scheme name and the transport to determine the SRV labels".

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/



From owner-ietf-ldapbis@OpenLDAP.org  Wed Jul  2 16:53:29 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16493
	for <ldapbis-archive@lists.ietf.org>; Wed, 2 Jul 2003 16:53:29 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h62Kj2kp061831;
	Wed, 2 Jul 2003 20:52:16 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h62KXXai060836;
	Wed, 2 Jul 2003 20:33:33 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 2 Jul 2003 20:33:33 +0000
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h62KXOkb060806
	for <ietf-ldapbis@openldap.org>; Wed, 2 Jul 2003 20:33:25 GMT
	(envelope-from nsyracus@cnri.reston.va.us)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12680;
	Wed, 2 Jul 2003 16:32:22 -0400 (EDT)
Message-Id: <200307022032.QAA12680@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: ietf-ldapbis@OpenLDAP.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-ldapbis-protocol-16.txt
Date: Wed, 02 Jul 2003 16:32:22 -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: The Protocol
	Author(s)	: J. Sermersheim
	Filename	: draft-ietf-ldapbis-protocol-16.txt
	Pages		: 63
	Date		: 2003-7-2
	
This document describes the protocol elements, along with their 
semantics and encodings, for the Lightweight Directory Access 
Protocol (LDAP). LDAP provides access to distributed directory 
services that act in accordance with X.500 data and service models. 
These protocol elements are based on those described in the X.500 
Directory Access Protocol (DAP).

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

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

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

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


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

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

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

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

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

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

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

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

--OtherAccess--

--NextPart--




From owner-ietf-ldapbis@OpenLDAP.org  Wed Jul  2 16:53:30 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16494
	for <ldapbis-archive@lists.ietf.org>; Wed, 2 Jul 2003 16:53:29 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h62Kcol9061427;
	Wed, 2 Jul 2003 20:52:24 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h62KXVxp060827;
	Wed, 2 Jul 2003 20:33:31 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 2 Jul 2003 20:33:31 +0000
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h62KXQkb060807
	for <ietf-ldapbis@openldap.org>; Wed, 2 Jul 2003 20:33:26 GMT
	(envelope-from nsyracus@cnri.reston.va.us)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12664;
	Wed, 2 Jul 2003 16:32:17 -0400 (EDT)
Message-Id: <200307022032.QAA12664@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: ietf-ldapbis@OpenLDAP.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-ldapbis-models-08.txt
Date: Wed, 02 Jul 2003 16:32: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: Directory Information Models
	Author(s)	: K. Zeilenga
	Filename	: draft-ietf-ldapbis-models-08.txt
	Pages		: 49
	Date		: 2003-7-2
	
The Lightweight Directory Access Protocol (LDAP) is an Internet
protocol for accessing distributed directory services which act in
accordance with X.500 data and service models.  This document
describes the X.500 Directory Information Models.

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

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

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

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


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

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

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

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

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

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

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

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

--OtherAccess--

--NextPart--




From owner-ietf-ldapbis@OpenLDAP.org  Thu Jul  3 10:15:45 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12693
	for <ldapbis-archive@lists.ietf.org>; Thu, 3 Jul 2003 10:15:41 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h63DotlJ002115;
	Thu, 3 Jul 2003 14:13:59 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h63Dm5ga001891;
	Thu, 3 Jul 2003 13:48:05 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 3 Jul 2003 13:48:05 +0000
Received: from pat.uio.no (IDENT:7411@pat.uio.no [129.240.130.16])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h63Dm1kb001831;
	Thu, 3 Jul 2003 13:48:02 GMT
	(envelope-from hbf@bombur.uio.no)
Received: from mail-mx1.uio.no ([129.240.10.29])
	by pat.uio.no with esmtp (Exim 2.12 #7)
	id 19Y4RK-0004Zg-00; Thu, 3 Jul 2003 15:47:58 +0200
Received: from [129.240.130.19] (helo=miss.uio.no)
	by mail-mx1.uio.no with esmtp (Exim 4.14)
	id 19Y4RF-0006OK-55; Thu, 03 Jul 2003 15:47:53 +0200
Received: from bombur.uio.no ([129.240.186.42])
	by miss.uio.no with esmtp (Exim 2.12 #7)
	id 19Y4RF-0004Fh-00; Thu, 3 Jul 2003 15:47:53 +0200
Received: from hbf by bombur.uio.no with local (Exim 2.12 #7)
	id 19Y4RF-0000Yu-00; Thu, 3 Jul 2003 15:47:53 +0200
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Message-Id: <HBF.20030703wadg@bombur.uio.no>
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Cc: "Roger Harrison" <RHARRISON@novell.com>, ietf-ldapbis@OpenLDAP.org
Subject: Re: [authmeth] effect of StartTLS on authentication state
In-Reply-To: <5.2.0.9.0.20030701192833.01da9220@127.0.0.1>
References: <sf01cca0.066@prv-mail20.provo.novell.com>
	<5.2.0.9.0.20030701171553.01da9e50@127.0.0.1>
	<5.2.0.9.0.20030701192833.01da9220@127.0.0.1>
X-Mailer: VM 6.37 under Emacs 19.34.1
Date: Thu, 3 Jul 2003 15:47:53 +0200
X-MailScanner-Information: This message has been scanned for viruses/spam. Contact postmaster@uio.no if you have questions about this scanning.
X-UiO-MailScanner: No virus found
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

Kurt D. Zeilenga writes:

> I still believe the server is free to return strongAuthRequired at any
> time it considers the in force association to be inappropriate for the
> requested operation.

I don't think so.  5.2.1 says:
    
   Upon establishment of the TLS session onto the LDAP association, any 
   previously established authentication and authorization identities 
   MUST remain in force

> Hence, the server may, in effect, move the association to anonymous
> after StartTLS.

I think it _should_ be allowed to, yes.

-- 
Hallvard


From owner-ietf-ldapbis@OpenLDAP.org  Thu Jul  3 10:44:34 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13884
	for <ldapbis-archive@lists.ietf.org>; Thu, 3 Jul 2003 10:44:32 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h63DWtlN000460;
	Thu, 3 Jul 2003 13:56:57 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h63DTESl000302;
	Thu, 3 Jul 2003 13:29:14 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 3 Jul 2003 13:29:14 +0000
Received: from pat.uio.no (IDENT:7411@pat.uio.no [129.240.130.16])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h63DTAkb000261;
	Thu, 3 Jul 2003 13:29:11 GMT
	(envelope-from hbf@bombur.uio.no)
Received: from mail-mx2.uio.no ([129.240.10.30])
	by pat.uio.no with esmtp (Exim 2.12 #7)
	id 19Y495-0002hf-00; Thu, 3 Jul 2003 15:29:07 +0200
Received: from [129.240.130.19] (helo=miss.uio.no)
	by mail-mx2.uio.no with esmtp (Exim 4.14)
	id 19Y491-0004Wf-Pd; Thu, 03 Jul 2003 15:29:03 +0200
Received: from bombur.uio.no ([129.240.186.42])
	by miss.uio.no with esmtp (Exim 2.12 #7)
	id 19Y491-00027f-00; Thu, 3 Jul 2003 15:29:03 +0200
Received: from hbf by bombur.uio.no with local (Exim 2.12 #7)
	id 19Y491-0000VI-00; Thu, 3 Jul 2003 15:29:03 +0200
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Message-Id: <HBF.20030703wlpw@bombur.uio.no>
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Cc: "Roger Harrison" <RHARRISON@novell.com>, ietf-ldapbis@OpenLDAP.org
Subject: Re: [authmeth] effect of StartTLS on authentication state
In-Reply-To: <5.2.0.9.0.20030701171553.01da9e50@127.0.0.1>
References: <sf01cca0.066@prv-mail20.provo.novell.com>
	<5.2.0.9.0.20030701171553.01da9e50@127.0.0.1>
X-Mailer: VM 6.37 under Emacs 19.34.1
Date: Thu, 3 Jul 2003 15:29:03 +0200
X-MailScanner-Information: This message has been scanned for viruses/spam. Contact postmaster@uio.no if you have questions about this scanning.
X-UiO-MailScanner: No virus found
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

Kurt D. Zeilenga writes:
> For the life of me, I cannot imagine why a client would do
>     simple+StartTLS+modify
> or even
>     simple+StartTLS+search-for-user-application-objects

However, an attacker could insert a bind before the StartTLS in a client
which expects to run with anonymous auth and which grants access to
something depending on what is returned from the search.  I can vaguely
imagine that this could be a problem in rare cases.

And of course, the attacker could insert another bind after the client's
bind if the client does simple+StartTLS+modify.

-- 
Hallvard


From owner-ietf-ldapbis@OpenLDAP.org  Thu Jul  3 11:26:20 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15352
	for <ldapbis-archive@lists.ietf.org>; Thu, 3 Jul 2003 11:26:19 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h63EuulL009595;
	Thu, 3 Jul 2003 15:21:40 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h63Euftg009551;
	Thu, 3 Jul 2003 14:56:41 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 3 Jul 2003 14:56:41 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h63Euekb009541
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 3 Jul 2003 14:56:40 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from nomad.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.8/8.12.8) with ESMTP id h63Euec6077107;
	Thu, 3 Jul 2003 14:56:40 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030703072240.01d8bf70@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Thu, 03 Jul 2003 07:53:34 -0700
To: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: [authmeth] effect of StartTLS on authentication state
Cc: ietf-ldapbis@OpenLDAP.org
In-Reply-To: <HBF.20030703wadg@bombur.uio.no>
References: <5.2.0.9.0.20030701192833.01da9220@127.0.0.1>
 <sf01cca0.066@prv-mail20.provo.novell.com>
 <5.2.0.9.0.20030701171553.01da9e50@127.0.0.1>
 <5.2.0.9.0.20030701192833.01da9220@127.0.0.1>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

At 06:47 AM 7/3/2003, Hallvard B Furuseth wrote:
>Kurt D. Zeilenga writes:
>> I still believe the server is free to return strongAuthRequired at any
>> time it considers the in force association to be inappropriate for the
>> requested operation.
>
>I don't think so.  5.2.1 says:
>    
>   Upon establishment of the TLS session onto the LDAP association, any 
>   previously established authentication and authorization identities 
>   MUST remain in force

This only says the server must keep identities in force.  It
does not mean that the server cannot consider the client not
to have obtained a strong enough security association to
request the subsequent operation.  The server is always free
to return stongAuthRequired when the in force association is
not strong enough.

>> Hence, the server may, in effect, move the association to anonymous
>> after StartTLS.
>
>I think it _should_ be allowed to, yes.

While obviously I agree,  I argue that they can, in all effect, as
nothing in the LDAP TS says what authorization an in force identity
has.  It may have none, it may have same authorization as an anonymous
user, it may have some other level of authorization.  The authorization
of a client may depend on any number of factors, including the ordering
of operations presented to it.

Kurt 



From owner-ietf-ldapbis@OpenLDAP.org  Thu Jul  3 11:37:21 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17660
	for <ldapbis-archive@lists.ietf.org>; Thu, 3 Jul 2003 11:37:20 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h63FWukl012832;
	Thu, 3 Jul 2003 15:36:17 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h63FVdUB012711;
	Thu, 3 Jul 2003 15:31:39 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 3 Jul 2003 15:31:39 +0000
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h63FVYkb012697
	for <ietf-ldapbis@openldap.org>; Thu, 3 Jul 2003 15:31:34 GMT
	(envelope-from nsyracus@cnri.reston.va.us)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16461;
	Thu, 3 Jul 2003 11:31:23 -0400 (EDT)
Message-Id: <200307031531.LAA16461@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: ietf-ldapbis@OpenLDAP.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-ldapbis-authmeth-06.txt
Date: Thu, 03 Jul 2003 11:31:22 -0400
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

--NextPart

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

	Title		: LDAP: Authentication Methods and Connection Level 
                          Security Mechanism
	Author(s)	: R. Harrison
	Filename	: draft-ietf-ldapbis-authmeth-06.txt
	Pages		: 45
	Date		: 2003-7-3
	
This document describes LDAPv3 (Lightweight Directory Access 
Protocol v3) authentication methods and connection level security 
mechanisms that are required of all conforming LDAPv3 server 
implementations and makes recommendations for combinations of these 
mechanisms to be used in various deployment circumstances.  
Among the mechanisms described are 
- various forms of authentication including anonymous 
authentication, password-based authentication, and certificate 
based authentication 
- the use of SASL mechanisms with LDAPv3 
- the use of TLS (Transport Layer Security) with LDAPv3 
- the various authentication and authorization states through 
which a connection to an LDAP server may pass and the actions 
that trigger these state changes.

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

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

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

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


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

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

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

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

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

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

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

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

--OtherAccess--

--NextPart--




From owner-ietf-ldapbis@OpenLDAP.org  Thu Jul  3 11:37:26 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17676
	for <ldapbis-archive@lists.ietf.org>; Thu, 3 Jul 2003 11:37:25 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h63FWukn012832;
	Thu, 3 Jul 2003 15:36:17 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h63FVSYi012689;
	Thu, 3 Jul 2003 15:31:28 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 3 Jul 2003 15:31:28 +0000
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h63FVLkb012676
	for <ietf-ldapbis@openldap.org>; Thu, 3 Jul 2003 15:31:24 GMT
	(envelope-from nsyracus@cnri.reston.va.us)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16442;
	Thu, 3 Jul 2003 11:31:18 -0400 (EDT)
Message-Id: <200307031531.LAA16442@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: ietf-ldapbis@OpenLDAP.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-ldapbis-user-schema-06.txt
Date: Thu, 03 Jul 2003 11:31:18 -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-06.txt
	Pages		: 27
	Date		: 2003-7-3
	
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-06.txt

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

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

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


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

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

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

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

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

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

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

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

--OtherAccess--

--NextPart--




From owner-ietf-ldapbis@OpenLDAP.org  Fri Jul  4 11:47:13 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00074
	for <ldapbis-archive@lists.ietf.org>; Fri, 4 Jul 2003 11:47:10 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h64Fjjkb072822;
	Fri, 4 Jul 2003 15:45:45 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h64FRPHc071804;
	Fri, 4 Jul 2003 15:27:25 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Fri, 4 Jul 2003 15:27:25 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h64FRNkb071793
	for <ietf-ldapbis@OpenLDAP.org>; Fri, 4 Jul 2003 15:27:24 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from nomad.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.8/8.12.8) with ESMTP id h64FRJc6086157;
	Fri, 4 Jul 2003 15:27:20 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030704081521.01c87010@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Fri, 04 Jul 2003 08:24:14 -0700
To: steven Legg <steven.legg@adacel.com.au>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: PrintableString in [SYNTAXES]
Cc: ietf-ldapbis@OpenLDAP.org
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

Unlike DirectoryString and IA5String, PrintableString specification
does how detail, in prose, how many characters can appear in a
value conforming to the syntax.  The specification should say
"string of one or more ... characters".

Kurt



From owner-ietf-ldapbis@OpenLDAP.org  Mon Jul  7 12:33:57 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02317
	for <ldapbis-archive@lists.ietf.org>; Mon, 7 Jul 2003 12:33:56 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h67GLSlJ065633;
	Mon, 7 Jul 2003 16:32:47 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h67GL3h1065554;
	Mon, 7 Jul 2003 16:21:03 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 7 Jul 2003 16:21:03 +0000
Received: from prv-mail20.provo.novell.com (prv-mail20.provo.novell.com [137.65.81.122])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h67GL0kb065459
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 7 Jul 2003 16:21:00 GMT
	(envelope-from jimse@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Mon, 07 Jul 2003 10:20:36 -0600
Message-Id: <sf094974.027@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.1 
Date: Mon, 07 Jul 2003 10:18:52 -0600
From: "Jim Sermersheim" <jimse@novell.com>
To: <Olivier.Dubuisson@francetelecom.com>, <ietf-ldapbis@OpenLDAP.org>
Subject: Re: draft-ietf-ldapbis-protocol-16.txt
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

>>> Olivier Dubuisson <Olivier.Dubuisson@francetelecom.com> 7/3/03
12:52:50 AM >>>
>Dear Jim,
>
>regarding Section 9 of 
><http://www.ietf.org/internet-drafts/draft-ietf-ldapbis-protocol-16.txt>
>please update the dates of X.680 and X.690 to 2002, for it is the only

>version in force for the ASN.1 standard.

I note also that [Syntaxes] points to the 1997 version of X.690, and
[Models] points to the 1997 version of X.680 (though [Syntaxes] points
to the 2002 version). I don't remember what we decided to do with the
dates of the ITU-T documents, but likely we should apply the changes to
all the documents.

>Would it be acceptable to you if the ASN.1 module defined in your I-D
is 
>checked and pretty-printed by the ITU-T, and published as part of the

>module database on their website at 
><http://www.itu.int/itu-t/asn1/database>?

My read of the copyright statement on the last page permits you to
copy, prepare, and publish a derivative work (so yes)

Jim

>-- 
>Olivier DUBUISSON (leader of the ITU-T ASN.1 Project)
>france telecom R&D
>
>DTL/TAL - 22307 Lannion Cedex - France
>t: +33 2 96 05 38 50 - f: +33 2 96 05 39 45 -
http://asn1.elibel.tm.fr/ 



From owner-ietf-ldapbis@OpenLDAP.org  Mon Jul  7 13:12:13 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04057
	for <ldapbis-archive@lists.ietf.org>; Mon, 7 Jul 2003 13:12:12 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h67H3TlJ069590;
	Mon, 7 Jul 2003 17:10:57 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h67H35cR069575;
	Mon, 7 Jul 2003 17:03:05 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 7 Jul 2003 17:03:05 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h67H33kb069564
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 7 Jul 2003 17:03:04 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from nomad.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.8/8.12.8) with ESMTP id h67H2lc6013802;
	Mon, 7 Jul 2003 17:02:47 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030707093912.01be2760@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Mon, 07 Jul 2003 09:59:39 -0700
To: "Jim Sermersheim" <jimse@novell.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: draft-ietf-ldapbis-protocol-16.txt
Cc: <ietf-ldapbis@OpenLDAP.org>, Olivier.Dubuisson@francetelecom.com
In-Reply-To: <sf094974.027@prv-mail20.provo.novell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

At 09:18 AM 7/7/2003, Jim Sermersheim wrote:
>>>> Olivier Dubuisson <Olivier.Dubuisson@francetelecom.com> 7/3/03
>12:52:50 AM >>>
>>Dear Jim,
>>
>>regarding Section 9 of 
>><http://www.ietf.org/internet-drafts/draft-ietf-ldapbis-protocol-16.txt>
>>please update the dates of X.680 and X.690 to 2002, for it is the only
>
>>version in force for the ASN.1 standard.
>
>I note also that [Syntaxes] points to the 1997 version of X.690, and
>[Models] points to the 1997 version of X.680 (though [Syntaxes] points
>to the 2002 version). I don't remember what we decided to do with the
>dates of the ITU-T documents, but likely we should apply the changes to
>all the documents.

For X.680/X.690, referencing the latest versions is not problematic.
For other ITU-T documents, in particular X.500 series documents, we
need to stick with 2nd edition revisions (e.g, circa 1993).

>>Would it be acceptable to you if the ASN.1 module defined in your I-D
>is 
>>checked and pretty-printed by the ITU-T, and published as part of the
>
>>module database on their website at 
>><http://www.itu.int/itu-t/asn1/database>?

Verification of the ASN.1 using available checkers would
be appreciated.

>My read of the copyright statement on the last page permits you to
>copy, prepare, and publish a derivative work (so yes)

I note that as the ASN.1 is often used and distributed
separately from the RFC, we likely should apply the MIB
copyright guidelines:
   http://www.ietf.org/IESG/STATEMENTS/MIB-COPYRIGHT.txt
so that the ISOC copyright appears in the ASN.1.

Kurt 



From owner-ietf-ldapbis@OpenLDAP.org  Mon Jul  7 20:31:04 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA22818
	for <ldapbis-archive@lists.ietf.org>; Mon, 7 Jul 2003 20:31:01 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h680RVkf085199;
	Tue, 8 Jul 2003 00:29:22 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h680OJvx085156;
	Tue, 8 Jul 2003 00:24:19 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 8 Jul 2003 00:24:19 +0000
Received: from adacel.com (gunsmoke.adacel.com.au [210.11.130.7])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h680OGkb085106
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 8 Jul 2003 00:24:17 GMT
	(envelope-from steven.legg@adacel.com.au)
Received: from nexus.adacel.com (Not Verified[10.32.240.1]) by adacel.com with NetIQ MailMarshal (v5.5.3.16)
	id <B0000fe63a>; Tue, 08 Jul 2003 10:19:49 +1000
Received: (qmail 5673 invoked from network); 8 Jul 2003 00:21:59 -0000
Received: from unknown (HELO osmium) (10.32.24.165)
  by nexus.adacel.com with SMTP; 8 Jul 2003 00:21:59 -0000
Reply-To: <steven.legg@adacel.com.au>
From: "Steven Legg" <steven.legg@adacel.com.au>
To: "'Kurt D. Zeilenga'" <Kurt@OpenLDAP.org>,
        "'Jim Sermersheim'" <jimse@novell.com>
Cc: <ietf-ldapbis@OpenLDAP.org>, <Olivier.Dubuisson@francetelecom.com>
Subject: RE: draft-ietf-ldapbis-protocol-16.txt
Date: Tue, 8 Jul 2003 10:23:54 +1000
Message-ID: <000801c344e7$37502800$a518200a@osmium.mtwav.adacel.com.au>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0
In-Reply-To: <5.2.0.9.0.20030707093912.01be2760@127.0.0.1>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2120.0
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


Kurt,

Kurt D. Zeilenga wrote:
> > At 09:18 AM 7/7/2003, Jim Sermersheim wrote:
> >My read of the copyright statement on the last page permits you to
> >copy, prepare, and publish a derivative work (so yes)
> 
> I note that as the ASN.1 is often used and distributed
> separately from the RFC, we likely should apply the MIB
> copyright guidelines:
>    http://www.ietf.org/IESG/STATEMENTS/MIB-COPYRIGHT.txt
> so that the ISOC copyright appears in the ASN.1.

I agree. We just need to change "this MIB module" to "this ASN.1 module".
I suggest we place the copyright notice as an ASN.1 comment after
the ModuleIdentifier but before the DEFINITIONS keyword, e.g.

Foo { 1 2 3 }

-- Copyright (C) The Internet Society (year). This version of
--  this ASN.1 module is part of RFC xxxx; see the RFC itself
--  for full legal notices.

DEFINITIONS
...


Regards,
Steven



From owner-ietf-ldapbis@OpenLDAP.org  Tue Jul  8 01:12:36 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA27209
	for <ldapbis-archive@lists.ietf.org>; Tue, 8 Jul 2003 01:12:35 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6859Xkf091869;
	Tue, 8 Jul 2003 05:11:18 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h6854mYZ091777;
	Tue, 8 Jul 2003 05:04:48 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 8 Jul 2003 05:04:48 +0000
Received: from ausyms50.ca.com ([155.35.248.106])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6854kkb091767
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 8 Jul 2003 05:04:47 GMT
	(envelope-from Ron.Ramsay@ca.com)
Received: from ausyms21.ca.com ([155.35.201.5]) by ausyms50.ca.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 8 Jul 2003 15:04:23 +1000
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C3450E.65AFA758"
Subject: Substrings any match on an empty string
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
Date: Tue, 8 Jul 2003 15:04:23 +1000
Message-ID: <1395B4B334FCC143B36AF788E68B6381465C11@ausyms21.ca.com>
Thread-Topic: Substrings any match on an empty string
Thread-Index: AcNFDmTN13k9IMBdT16oRsybYG6j4g==
From: "Ramsay, Ron" <Ron.Ramsay@ca.com>
To: <ietf-ldapbis@OpenLDAP.org>
X-OriginalArrivalTime: 08 Jul 2003 05:04:23.0450 (UTC) FILETIME=[65B18FA0:01C3450E]
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C3450E.65AFA758
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi all,

Does anyone have an answer to this question:

If I specify a filter of type 'substrings' where the substrings contain =
only an 'any' with a zero-length value, should I return all entries =
containing the attribute?

It seems to me that the empty string is a substring of all strings.

I've looked in RFC 2251, X.511 and X.520 but have not seen a statement =
which I could interpret as answering this question.

Thanks for your help,

Ron

------_=_NextPart_001_01C3450E.65AFA758
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.6389.0">
<TITLE>Substrings any match on an empty string</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT SIZE=3D2 FACE=3D"Arial">Hi all,</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Does anyone have an answer to this =
question:</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">If I specify a filter of type =
'substrings' where the substrings contain only an 'any' with a =
zero-length value, should I return all entries containing the =
attribute?</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">It seems to me that the empty string is =
a substring of all strings.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">I've looked in RFC 2251, X.511 and =
X.520 but have not seen a statement which I could interpret as answering =
this question.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Thanks for your help,</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Ron</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C3450E.65AFA758--


From owner-ietf-ldapbis@OpenLDAP.org  Tue Jul  8 01:30:35 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA27485
	for <ldapbis-archive@lists.ietf.org>; Tue, 8 Jul 2003 01:30:34 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h685RXkf092329;
	Tue, 8 Jul 2003 05:27:39 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h685Nsw9092254;
	Tue, 8 Jul 2003 05:23:54 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 8 Jul 2003 05:23:54 +0000
Received: from prv-mail25.provo.novell.com (prv-mail25.provo.novell.com [137.65.81.121])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h685Nrkb092243
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 8 Jul 2003 05:23:53 GMT
	(envelope-from gvithalprasad@novell.com)
Received: from INET-PRV1-MTA by prv-mail25.provo.novell.com
	with Novell_GroupWise; Mon, 07 Jul 2003 23:23:32 -0600
Message-Id: <sf0a00f4.068@prv-mail25.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.1 
Date: Mon, 07 Jul 2003 23:23:11 -0600
From: "Vithalprasad Gaitonde" <gvithalprasad@novell.com>
To: <ietf-ldapbis@OpenLDAP.org>
Subject: Re: Substrings any match on an empty string
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Wouldn't this just be equivalent to a presence filter on that
attribute.
We should have a statement in the LDAP protocols draft saying that the
filter that you describe is equivalent to a presence match.
Prasad

>>> "Ramsay, Ron" <Ron.Ramsay@ca.com> 7/8/2003 10:34:23 AM >>>
Hi all,

Does anyone have an answer to this question:

If I specify a filter of type 'substrings' where the substrings contain
only an 'any' with a zero-length value, should I return all entries
containing the attribute?

It seems to me that the empty string is a substring of all strings.

I've looked in RFC 2251, X.511 and X.520 but have not seen a statement
which I could interpret as answering this question.

Thanks for your help,

Ron


From owner-ietf-ldapbis@OpenLDAP.org  Tue Jul  8 02:35:19 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA11513
	for <ldapbis-archive@lists.ietf.org>; Tue, 8 Jul 2003 02:35:18 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h686XXkf094469;
	Tue, 8 Jul 2003 06:33:47 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h686WJfl094399;
	Tue, 8 Jul 2003 06:32:19 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 8 Jul 2003 06:32:19 +0000
Received: from prv-mail20.provo.novell.com (prv-mail20.provo.novell.com [137.65.81.122])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h686WIkb094369
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 8 Jul 2003 06:32:18 GMT
	(envelope-from jimse@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Tue, 08 Jul 2003 00:31:58 -0600
Message-Id: <sf0a10fe.078@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.1 
Date: Tue, 08 Jul 2003 00:30:17 -0600
From: "Jim Sermersheim" <jimse@novell.com>
To: <ietf-ldapbis@OpenLDAP.org>
Subject: Re: Substrings any match on an empty string
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

It depends on the Assertion Value for the matching rule being used.

Which brings up an issue:
In Section 5.1 of [Syntaxes], there is a statement 
   "Note that the AssertionValue in a SubstringFilter
   [PROT] MUST conform to the assertion syntax of the equality
matching
   rule for the attribute type rather than the assertion syntax of the
   substrings matching rule for the attribute type.  "

This does not align with [Protocol]. Steven, is this a historical
artifact, or did I screw the protocol up?

Jim

>>> "Ramsay, Ron" <Ron.Ramsay@ca.com> 7/7/03 11:04:23 PM >>>
Hi all,

Does anyone have an answer to this question:

If I specify a filter of type 'substrings' where the substrings contain
only an 'any' with a zero-length value, should I return all entries
containing the attribute?

It seems to me that the empty string is a substring of all strings.

I've looked in RFC 2251, X.511 and X.520 but have not seen a statement
which I could interpret as answering this question.

Thanks for your help,

Ron


From owner-ietf-ldapbis@OpenLDAP.org  Tue Jul  8 02:41:01 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA11749
	for <ldapbis-archive@lists.ietf.org>; Tue, 8 Jul 2003 02:41:01 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h686dXkf094745;
	Tue, 8 Jul 2003 06:39:36 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h686aeOF094610;
	Tue, 8 Jul 2003 06:36:40 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 8 Jul 2003 06:36:40 +0000
Received: from prv-mail20.provo.novell.com (prv-mail20.provo.novell.com [137.65.81.122])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h686ackb094595
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 8 Jul 2003 06:36:39 GMT
	(envelope-from jimse@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Tue, 08 Jul 2003 00:36:18 -0600
Message-Id: <sf0a1202.067@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.1 
Date: Tue, 08 Jul 2003 00:34:36 -0600
From: "Jim Sermersheim" <jimse@novell.com>
To: <ietf-ldapbis@OpenLDAP.org>
Subject: Re: Substrings any match on an empty string
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

What if the assertion syntax requires >0 octets? And/or what if the
substring matching rule has a special provision for the empty value?

Jim

>>> "Vithalprasad Gaitonde" <gvithalprasad@novell.com> 7/7/03 11:23:11
PM >>>
Wouldn't this just be equivalent to a presence filter on that
attribute.
We should have a statement in the LDAP protocols draft saying that the
filter that you describe is equivalent to a presence match.
Prasad

>>> "Ramsay, Ron" <Ron.Ramsay@ca.com> 7/8/2003 10:34:23 AM >>>
Hi all,

Does anyone have an answer to this question:

If I specify a filter of type 'substrings' where the substrings
contain
only an 'any' with a zero-length value, should I return all entries
containing the attribute?

It seems to me that the empty string is a substring of all strings.

I've looked in RFC 2251, X.511 and X.520 but have not seen a statement
which I could interpret as answering this question.

Thanks for your help,

Ron


From owner-ietf-ldapbis@OpenLDAP.org  Tue Jul  8 03:39:11 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA13004
	for <ldapbis-archive@lists.ietf.org>; Tue, 8 Jul 2003 03:39:11 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h687XYkn097322;
	Tue, 8 Jul 2003 07:38:06 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h687U6sl097166;
	Tue, 8 Jul 2003 07:30:06 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 8 Jul 2003 07:30:06 +0000
Received: from adacel.com (gunsmoke.adacel.com.au [210.11.130.7])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h687U4kb097122
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 8 Jul 2003 07:30:05 GMT
	(envelope-from steven.legg@adacel.com.au)
Received: from nexus.adacel.com (Not Verified[10.32.240.1]) by adacel.com with NetIQ MailMarshal (v5.5.3.16)
	id <B0000fef27>; Tue, 08 Jul 2003 17:25:35 +1000
Received: (qmail 18714 invoked from network); 8 Jul 2003 07:27:46 -0000
Received: from unknown (HELO osmium) (10.32.24.165)
  by nexus.adacel.com with SMTP; 8 Jul 2003 07:27:46 -0000
Reply-To: <steven.legg@adacel.com.au>
From: "Steven Legg" <steven.legg@adacel.com.au>
To: "'Jim Sermersheim'" <jimse@novell.com>, <ietf-ldapbis@OpenLDAP.org>
Subject: RE: Substrings any match on an empty string
Date: Tue, 8 Jul 2003 17:29:42 +1000
Message-ID: <001001c34522$b328b560$a518200a@osmium.mtwav.adacel.com.au>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0
In-Reply-To: <sf0a10fe.078@prv-mail20.provo.novell.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2120.0
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


Jim,

Jim Sermersheim wrote:
> It depends on the Assertion Value for the matching rule being used.
> 
> Which brings up an issue:
> In Section 5.1 of [Syntaxes], there is a statement 
>    "Note that the AssertionValue in a SubstringFilter
>    [PROT] MUST conform to the assertion syntax of the equality
> matching
>    rule for the attribute type rather than the assertion syntax of the
>    substrings matching rule for the attribute type.  "
> 
> This does not align with [Protocol]. Steven, is this a historical
> artifact, or did I screw the protocol up?

Well it's historical in the sense that it is analogous to
what X.500 defines, but it remains appropriate. If an AssertionValue
in a SubstringFilter were of the Substring Assertion syntax then we
would have something which contains initial, any and final substrings
embedded in something (the SubstringFilter) which also has initial,
any and final parts. That would be silly. For example, what would be
the point of the Substring Assertion syntax value "*foo" in the initial
AssertionValue ?

Given that the AssertionValue conforms to the assertion syntax of
the equality matching rule then for most attributes an "any" with
a zero-length string would be an invalid syntax. For those where
it is valid the result depends on the way string prep deals with empty
strings (each substring is prepared in isolation by the substring
matching rules).

Regards,
Steven
 
> 
> Jim
> 
> >>> "Ramsay, Ron" <Ron.Ramsay@ca.com> 7/7/03 11:04:23 PM >>>
> Hi all,
> 
> Does anyone have an answer to this question:
> 
> If I specify a filter of type 'substrings' where the 
> substrings contain
> only an 'any' with a zero-length value, should I return all entries
> containing the attribute?
> 
> It seems to me that the empty string is a substring of all strings.
> 
> I've looked in RFC 2251, X.511 and X.520 but have not seen a statement
> which I could interpret as answering this question.
> 
> Thanks for your help,
> 
> Ron
> 


From owner-ietf-ldapbis@OpenLDAP.org  Tue Jul  8 04:18:26 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA13613
	for <ldapbis-archive@lists.ietf.org>; Tue, 8 Jul 2003 04:18:25 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h688FYkf099815;
	Tue, 8 Jul 2003 08:17:17 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h688CMYv099682;
	Tue, 8 Jul 2003 08:12:22 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 8 Jul 2003 08:12:22 +0000
Received: from prv-mail20.provo.novell.com (prv-mail20.provo.novell.com [137.65.81.122])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h688CJkb099638
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 8 Jul 2003 08:12:19 GMT
	(envelope-from jimse@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Tue, 08 Jul 2003 02:11:59 -0600
Message-Id: <sf0a286e.034@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.1 
Date: Tue, 08 Jul 2003 02:10:17 -0600
From: "Jim Sermersheim" <jimse@novell.com>
To: <ietf-ldapbis@OpenLDAP.org>
Subject: RE: Substrings any match on an empty string
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Ok, after re-reading the [Protocol] statement, it only says:
     The matching rule for AssertionValues in a substrings filter item

     is defined by the SUBSTR matching rule for the attribute type. 
(nothing about the syntax of those AssertionValues)

And after reading Section 5.1 of [Syntaxes] further, I see:
   The entire
   SubstringFilter is converted into an assertion value of the
   substrings matching rule prior to applying the rule.

So, I see a few issues:

1) [Protocol] should likely specify the bit about which syntax is to be
used in SubstringFilter AssertionValues.
2) [Protocol] should likely talk about the conversion into the
substrings matching rule syntax (as [Syntaxes] does).
3) The answer to Ron's original question is that it's *always* invalid
to have an empty _any_ part--correct? This is because even though an
equality assertion syntax might allow zero octets, the Substring
Assertion syntax (which we need to convert to) never allows a
zero-length substring.

Jim


>>> "Steven Legg" <steven.legg@adacel.com.au> 7/8/03 1:29:42 AM >>>

Jim,

Jim Sermersheim wrote:
> It depends on the Assertion Value for the matching rule being used.
> 
> Which brings up an issue:
> In Section 5.1 of [Syntaxes], there is a statement 
>    "Note that the AssertionValue in a SubstringFilter
>    [PROT] MUST conform to the assertion syntax of the equality
> matching
>    rule for the attribute type rather than the assertion syntax of
the
>    substrings matching rule for the attribute type.  "
> 
> This does not align with [Protocol]. Steven, is this a historical
> artifact, or did I screw the protocol up?

Well it's historical in the sense that it is analogous to
what X.500 defines, but it remains appropriate. If an AssertionValue
in a SubstringFilter were of the Substring Assertion syntax then we
would have something which contains initial, any and final substrings
embedded in something (the SubstringFilter) which also has initial,
any and final parts. That would be silly. For example, what would be
the point of the Substring Assertion syntax value "*foo" in the
initial
AssertionValue ?

Given that the AssertionValue conforms to the assertion syntax of
the equality matching rule then for most attributes an "any" with
a zero-length string would be an invalid syntax. For those where
it is valid the result depends on the way string prep deals with empty
strings (each substring is prepared in isolation by the substring
matching rules).

Regards,
Steven
 
> 
> Jim
> 
> >>> "Ramsay, Ron" <Ron.Ramsay@ca.com> 7/7/03 11:04:23 PM >>>
> Hi all,
> 
> Does anyone have an answer to this question:
> 
> If I specify a filter of type 'substrings' where the 
> substrings contain
> only an 'any' with a zero-length value, should I return all entries
> containing the attribute?
> 
> It seems to me that the empty string is a substring of all strings.
> 
> I've looked in RFC 2251, X.511 and X.520 but have not seen a
statement
> which I could interpret as answering this question.
> 
> Thanks for your help,
> 
> Ron
> 


From owner-ietf-ldapbis@OpenLDAP.org  Tue Jul  8 09:25:11 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20944
	for <ldapbis-archive@lists.ietf.org>; Tue, 8 Jul 2003 09:25:10 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h68DLZkj013902;
	Tue, 8 Jul 2003 13:23:27 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h68DKDfw013854;
	Tue, 8 Jul 2003 13:20:13 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 8 Jul 2003 13:20:13 +0000
Received: from boole.openldap.org (kurt@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h68DJukb013839
	for <ietf-ldapbis@openldap.org>; Tue, 8 Jul 2003 13:19:56 GMT
	(envelope-from kurt@boole.openldap.org)
Received: (from kurt@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) id h68DJub3013838
	for ietf-ldapbis@openldap.org; Tue, 8 Jul 2003 13:19:56 GMT
	(envelope-from kurt)
Received: from p-mail2 (p-mail2.rd.francetelecom.com [195.101.245.16])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6874Rkb095685;
	Tue, 8 Jul 2003 07:04:31 GMT
	(envelope-from olivier.dubuisson@rd.francetelecom.com)
Received: from parmhs4.rd.francetelecom.fr ([10.193.117.63]) by parsmtp2.rd.francetelecom.com with Microsoft SMTPSVC(5.0.2195.5329);
	Tue, 8 Jul 2003 09:03:45 +0200
Received: from francetelecom.com ([10.193.13.28]) by parmhs4.rd.francetelecom.fr with Microsoft SMTPSVC(5.0.2195.5329);
	Tue, 8 Jul 2003 09:03:44 +0200
Message-ID: <3F0A6CCB.4040900@francetelecom.com>
Date: Tue, 08 Jul 2003 09:03:39 +0200
From: Olivier Dubuisson <Olivier.Dubuisson@francetelecom.com>
Organization: France Telecom R&D
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
CC: Jim Sermersheim <jimse@novell.com>, ietf-ldapbis@OpenLDAP.org,
        "sebastien.castano@itu.int" <sebastien.castano@itu.int>
Subject: Re: draft-ietf-ldapbis-protocol-16.txt
References: <5.2.0.9.0.20030707093912.01be2760@127.0.0.1>
In-Reply-To: <5.2.0.9.0.20030707093912.01be2760@127.0.0.1>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 08 Jul 2003 07:03:44.0267 (UTC) FILETIME=[11DF85B0:01C3451F]
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Kurt D. Zeilenga wrote:
> At 09:18 AM 7/7/2003, Jim Sermersheim wrote:
>  >>>> Olivier Dubuisson <Olivier.Dubuisson@francetelecom.com> 7/3/03
>  >12:52:50 AM >>>
>  >>Dear Jim,
>  >>
>  >>regarding Section 9 of
>  >><http://www.ietf.org/internet-drafts/draft-ietf-ldapbis-protocol-16.txt>
>  >>please update the dates of X.680 and X.690 to 2002, for it is the only
>  >
>  >>version in force for the ASN.1 standard.
>  >
>  >I note also that [Syntaxes] points to the 1997 version of X.690, and
>  >[Models] points to the 1997 version of X.680 (though [Syntaxes] points
>  >to the 2002 version). I don't remember what we decided to do with the
>  >dates of the ITU-T documents, but likely we should apply the changes to
>  >all the documents.
> 
> For X.680/X.690, referencing the latest versions is not problematic.

They are freely available from
http://www.itu.int/ITU-T/studygroups/com17/languages/

> For other ITU-T documents, in particular X.500 series documents, we
> need to stick with 2nd edition revisions (e.g, circa 1993).
> 
>  >>Would it be acceptable to you if the ASN.1 module defined in your I-D
>  >is
>  >>checked and pretty-printed by the ITU-T, and published as part of the
>  >
>  >>module database on their website at
>  >><http://www.itu.int/itu-t/asn1/database>?
> 
> Verification of the ASN.1 using available checkers would
> be appreciated.

Sebastien Castano from the ITU TSB will keep you informed as soon as the 
work is done and published on the ITU website so that you can hyperlink 
to the module database.

>  >My read of the copyright statement on the last page permits you to
>  >copy, prepare, and publish a derivative work (so yes)
> 
> I note that as the ASN.1 is often used and distributed
> separately from the RFC, we likely should apply the MIB
> copyright guidelines:
>    http://www.ietf.org/IESG/STATEMENTS/MIB-COPYRIGHT.txt
> so that the ISOC copyright appears in the ASN.1.

Good idea. We will add this copyright statement at the end of the ASN.1 
modules defined in RFCs before they are pretty-printed. But what kind of 
copyright statement would you like to see for Jim's I-D?
-- 
Olivier DUBUISSON (leader of the ITU-T ASN.1 Project)
france telecom R&D

DTL/TAL - 22307 Lannion Cedex - France
t: +33 2 96 05 38 50 - f: +33 2 96 05 39 45 - http://asn1.elibel.tm.fr/


From owner-ietf-ldapbis@OpenLDAP.org  Tue Jul  8 09:25:11 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20945
	for <ldapbis-archive@lists.ietf.org>; Tue, 8 Jul 2003 09:25:10 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h68DLZkl013902;
	Tue, 8 Jul 2003 13:23:43 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h68DKuTV013877;
	Tue, 8 Jul 2003 13:20:56 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 8 Jul 2003 13:20:56 +0000
Received: from boole.openldap.org (kurt@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h68DKskb013866
	for <ietf-ldapbis@openldap.org>; Tue, 8 Jul 2003 13:20:54 GMT
	(envelope-from kurt@boole.openldap.org)
Received: (from kurt@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) id h68DKsOs013865
	for ietf-ldapbis@openldap.org; Tue, 8 Jul 2003 13:20:54 GMT
	(envelope-from kurt)
Received: from p-mail2.rd.francetelecom.com (p-mail2.rd.francetelecom.com [195.101.245.16])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h688gWkb000602;
	Tue, 8 Jul 2003 08:42:32 GMT
	(envelope-from olivier.dubuisson@rd.francetelecom.com)
Received: from parmhs4.rd.francetelecom.fr ([10.193.117.63]) by parsmtp1.rd.francetelecom.com with Microsoft SMTPSVC(5.0.2195.5329);
	Tue, 8 Jul 2003 10:41:48 +0200
Received: from francetelecom.com ([10.193.13.28]) by parmhs4.rd.francetelecom.fr with Microsoft SMTPSVC(5.0.2195.5329);
	Tue, 8 Jul 2003 10:41:47 +0200
Message-ID: <3F0A83CA.4050003@francetelecom.com>
Date: Tue, 08 Jul 2003 10:41:46 +0200
From: Olivier Dubuisson <Olivier.Dubuisson@francetelecom.com>
Organization: France Telecom R&D
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: steven.legg@adacel.com.au
CC: "'Kurt D. Zeilenga'" <Kurt@OpenLDAP.org>,
        "'Jim Sermersheim'" <jimse@novell.com>, ietf-ldapbis@OpenLDAP.org,
        "sebastien.castano@itu.int" <sebastien.castano@itu.int>
Subject: Re: draft-ietf-ldapbis-protocol-16.txt
References: <000801c344e7$37502800$a518200a@osmium.mtwav.adacel.com.au>
In-Reply-To: <000801c344e7$37502800$a518200a@osmium.mtwav.adacel.com.au>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 08 Jul 2003 08:41:47.0715 (UTC) FILETIME=[C4AE7130:01C3452C]
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.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:
> Kurt,
> 
> Kurt D. Zeilenga wrote:
> 
>>>At 09:18 AM 7/7/2003, Jim Sermersheim wrote:
>>>My read of the copyright statement on the last page permits you to
>>>copy, prepare, and publish a derivative work (so yes)
>>
>>I note that as the ASN.1 is often used and distributed
>>separately from the RFC, we likely should apply the MIB
>>copyright guidelines:
>>   http://www.ietf.org/IESG/STATEMENTS/MIB-COPYRIGHT.txt
>>so that the ISOC copyright appears in the ASN.1.
> 
> I agree. We just need to change "this MIB module" to "this ASN.1 module".
> I suggest we place the copyright notice as an ASN.1 comment after
> the ModuleIdentifier but before the DEFINITIONS keyword, e.g.
> 
> Foo { 1 2 3 }
> 
> -- Copyright (C) The Internet Society (year). This version of
> --  this ASN.1 module is part of RFC xxxx; see the RFC itself
> --  for full legal notices.
> 
> DEFINITIONS
> ...

Sebastien, please handle this with the small change that it is not an 
RFC but an I-D (OK Steven?).
-- 
Olivier DUBUISSON
france telecom R&D

DTL/TAL - 22307 Lannion Cedex - France
t: +33 2 96 05 38 50 - f: +33 2 96 05 39 45 - http://asn1.elibel.tm.fr/


From owner-ietf-ldapbis@OpenLDAP.org  Tue Jul  8 10:22:58 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24201
	for <ldapbis-archive@lists.ietf.org>; Tue, 8 Jul 2003 10:22:56 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h68ELakf015795;
	Tue, 8 Jul 2003 14:21:49 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h68EKEbX015778;
	Tue, 8 Jul 2003 14:20:14 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 8 Jul 2003 14:20:14 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h68EKBkb015768
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 8 Jul 2003 14:20:11 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from nomad.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.8/8.12.8) with ESMTP id h68EK3c6022365;
	Tue, 8 Jul 2003 14:20:04 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030708070442.01bb5a60@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Tue, 08 Jul 2003 07:16:54 -0700
To: ietf-ldapbis@OpenLDAP.org
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Agenda for LDAPBIS @ IETF#57
Cc: agenda@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>

LDAP (v3) Revision (LDAPBIS) WG 

TUESDAY, July 15, 2003
1415-1515 Afternoon Sessions II
Hall LM

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

1) Preliminaries - 5m - chairs
2) draft-ietf-ldapbis-protocol - 20m - editor*
3) draft-ietf-ldapbis-authmeth - 20m - editor*
4) Other issues / Open mic - as time permits - WG

* other WG members will fill in where the editor is unavailable 



From owner-ietf-ldapbis@OpenLDAP.org  Tue Jul  8 20:16:18 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA16592
	for <ldapbis-archive@lists.ietf.org>; Tue, 8 Jul 2003 20:16:17 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6909ekf052487;
	Wed, 9 Jul 2003 00:14:55 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h6905mTu052359;
	Wed, 9 Jul 2003 00:05:48 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 9 Jul 2003 00:05:48 +0000
Received: from adacel.com (gunsmoke.adacel.com.au [210.11.130.7])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6905jkb052301
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 9 Jul 2003 00:05: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.3.16)
	id <B000100816>; Wed, 09 Jul 2003 10:01:11 +1000
Received: (qmail 21095 invoked from network); 9 Jul 2003 00:03:22 -0000
Received: from unknown (HELO osmium) (10.32.24.165)
  by nexus.adacel.com with SMTP; 9 Jul 2003 00:03:22 -0000
Reply-To: <steven.legg@adacel.com.au>
From: "Steven Legg" <steven.legg@adacel.com.au>
To: "'Olivier Dubuisson'" <Olivier.Dubuisson@francetelecom.com>
Cc: <ietf-ldapbis@OpenLDAP.org>, <sebastien.castano@itu.int>
Subject: RE: draft-ietf-ldapbis-protocol-16.txt
Date: Wed, 9 Jul 2003 10:05:22 +1000
Message-ID: <001301c345ad$cb0a8970$a518200a@osmium.mtwav.adacel.com.au>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0
In-Reply-To: <3F0A6CCB.4040900@francetelecom.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2120.0
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


Olivier,

Olivier Dubuisson wrote:
> Kurt D. Zeilenga wrote:
> > At 09:18 AM 7/7/2003, Jim Sermersheim wrote:
> >  >>>> Olivier Dubuisson <Olivier.Dubuisson@francetelecom.com> 7/3/03
> >  >12:52:50 AM >>>
> >  >>Dear Jim,
> >  >>
> >  >>regarding Section 9 of
> >  
> >><http://www.ietf.org/internet-drafts/draft-ietf-ldapbis-prot
> ocol-16.txt>
> >  >>please update the dates of X.680 and X.690 to 2002, for 
> it is the only
> >  >
> >  >>version in force for the ASN.1 standard.
> >  >
> >  >I note also that [Syntaxes] points to the 1997 version of 
> X.690, and
> >  >[Models] points to the 1997 version of X.680 (though 
> [Syntaxes] points
> >  >to the 2002 version). I don't remember what we decided to 
> do with the
> >  >dates of the ITU-T documents, but likely we should apply 
> the changes to
> >  >all the documents.
> > 
> > For X.680/X.690, referencing the latest versions is not problematic.
> 
> They are freely available from
> http://www.itu.int/ITU-T/studygroups/com17/languages/
> 
> > For other ITU-T documents, in particular X.500 series documents, we
> > need to stick with 2nd edition revisions (e.g, circa 1993).
> > 
> >  >>Would it be acceptable to you if the ASN.1 module 
> defined in your I-D
> >  >is
> >  >>checked and pretty-printed by the ITU-T, and published 
> as part of the
> >  >
> >  >>module database on their website at
> >  >><http://www.itu.int/itu-t/asn1/database>?
> > 
> > Verification of the ASN.1 using available checkers would
> > be appreciated.
> 
> Sebastien Castano from the ITU TSB will keep you informed as 
> soon as the 
> work is done and published on the ITU website so that you can 
> hyperlink 
> to the module database.

Are you sure you want to publish ASN.1 from an Internet draft ?
It's a good idea to run it through a syntax checker as soon as
possible after any changes, but I would wait on publishing it
until after the draft becomes an RFC. Also, by that time we should
have added the necessary copyright statements.

Regards,
Steven

> 
> >  >My read of the copyright statement on the last page permits you to
> >  >copy, prepare, and publish a derivative work (so yes)
> > 
> > I note that as the ASN.1 is often used and distributed
> > separately from the RFC, we likely should apply the MIB
> > copyright guidelines:
> >    http://www.ietf.org/IESG/STATEMENTS/MIB-COPYRIGHT.txt
> > so that the ISOC copyright appears in the ASN.1.
> 
> Good idea. We will add this copyright statement at the end of 
> the ASN.1 
> modules defined in RFCs before they are pretty-printed. But 
> what kind of 
> copyright statement would you like to see for Jim's I-D?
> -- 
> Olivier DUBUISSON (leader of the ITU-T ASN.1 Project)
> france telecom R&D
> 
> DTL/TAL - 22307 Lannion Cedex - France
> t: +33 2 96 05 38 50 - f: +33 2 96 05 39 45 - 
> http://asn1.elibel.tm.fr/
> 


From owner-ietf-ldapbis@OpenLDAP.org  Wed Jul  9 03:13:41 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA21292
	for <ldapbis-archive@lists.ietf.org>; Wed, 9 Jul 2003 03:13:26 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6979gkf069749;
	Wed, 9 Jul 2003 07:11:35 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h6973kK7069532;
	Wed, 9 Jul 2003 07:03:46 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 9 Jul 2003 07:03:46 +0000
Received: from p-mail1.rd.francetelecom.com (p-mail1.rd.francetelecom.com [195.101.245.15])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6973gkb069517
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 9 Jul 2003 07:03:43 GMT
	(envelope-from olivier.dubuisson@rd.francetelecom.com)
Received: from parmhs4.rd.francetelecom.fr ([10.193.117.63]) by parsmtp1.rd.francetelecom.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 9 Jul 2003 09:03:10 +0200
Received: from francetelecom.com ([10.193.13.28]) by parmhs4.rd.francetelecom.fr with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 9 Jul 2003 09:03:08 +0200
Message-ID: <3F0BBE28.5000806@francetelecom.com>
Date: Wed, 09 Jul 2003 09:03:04 +0200
From: Olivier Dubuisson <Olivier.Dubuisson@francetelecom.com>
Organization: France Telecom R&D
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: steven.legg@adacel.com.au
CC: ietf-ldapbis@OpenLDAP.org, sebastien.castano@itu.int
Subject: Re: draft-ietf-ldapbis-protocol-16.txt
References: <001301c345ad$cb0a8970$a518200a@osmium.mtwav.adacel.com.au>
In-Reply-To: <001301c345ad$cb0a8970$a518200a@osmium.mtwav.adacel.com.au>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 09 Jul 2003 07:03:08.0767 (UTC) FILETIME=[272066F0:01C345E8]
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.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:
> 
> Are you sure you want to publish ASN.1 from an Internet draft ?
> It's a good idea to run it through a syntax checker as soon as
> possible after any changes, but I would wait on publishing it
> until after the draft becomes an RFC. Also, by that time we should
> have added the necessary copyright statements.

No problem. We'll wait.
-- 
Olivier DUBUISSON
france telecom R&D

DTL/TAL - 22307 Lannion Cedex - France
t: +33 2 96 05 38 50 - f: +33 2 96 05 39 45 - http://asn1.elibel.tm.fr/



From owner-ietf-ldapbis@OpenLDAP.org  Wed Jul  9 19:00:45 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27993
	for <ldapbis-archive@lists.ietf.org>; Wed, 9 Jul 2003 19:00:42 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h69Mplkf002427;
	Wed, 9 Jul 2003 22:53:50 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h69MlcoZ002366;
	Wed, 9 Jul 2003 22:47:38 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 9 Jul 2003 22:47:38 +0000
Received: from prv-mail20.provo.novell.com (prv-mail20.provo.novell.com [137.65.81.122])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h69Mlakb002334
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 9 Jul 2003 22:47:37 GMT
	(envelope-from jimse@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Wed, 09 Jul 2003 16:47:16 -0600
Message-Id: <sf0c4714.048@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.1 
Date: Wed, 09 Jul 2003 16:45:34 -0600
From: "Jim Sermersheim" <jimse@novell.com>
To: <ietf-ldapbis@OpenLDAP.org>
Cc: "Duane Buss" <DBuss@novell.com>, "Steve McLain" <SMCLAIN@novell.com>,
        "Tom Doman" <TDoman@novell.com>
Subject: ABNF of numericoid
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

All,

In [Models], we define:
numericoid = number *( DOT number )

This allows an invalid oid like 23.666.<whatever>

Are there usages of numericoid that need to allow these non-valid oids?
If not, I think it'd be better to show the proper restrictions on the
first two numbers.

Jim


From owner-ietf-ldapbis@OpenLDAP.org  Thu Jul 10 08:04:16 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA28245
	for <ldapbis-archive@lists.ietf.org>; Thu, 10 Jul 2003 08:04:11 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6ABvpkf026916;
	Thu, 10 Jul 2003 12:02:35 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h6ABvI0E026905;
	Thu, 10 Jul 2003 11:57:18 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 10 Jul 2003 11:57:18 +0000
Received: from pat.uio.no (IDENT:7411@pat.uio.no [129.240.130.16])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6ABvGkb026895
	for <ietf-ldapbis@openldap.org>; Thu, 10 Jul 2003 11:57:16 GMT
	(envelope-from hbf@bombur.uio.no)
Received: from mail-mx2.uio.no ([129.240.10.30])
	by pat.uio.no with esmtp (Exim 2.12 #7)
	id 19aa2v-0000HR-00; Thu, 10 Jul 2003 13:57:09 +0200
Received: from [129.240.201.2] (helo=goggins.uio.no)
	by mail-mx2.uio.no with esmtp (Exim 4.14)
	id 19aa2q-0005wh-O8; Thu, 10 Jul 2003 13:57:04 +0200
Received: from bombur.uio.no ([129.240.186.42])
	by goggins.uio.no with esmtp (Exim 2.12 #7)
	id 19aa2q-0004bs-00; Thu, 10 Jul 2003 13:57:04 +0200
Received: from hbf by bombur.uio.no with local (Exim 2.12 #7)
	id 19aa2m-00014k-00; Thu, 10 Jul 2003 13:57:00 +0200
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Message-Id: <HBF.20030710bpi5@bombur.uio.no>
To: Jim Sermersheim <jimse@novell.com>
Cc: ietf-ldapbis@OpenLDAP.org, Duane Buss <DBuss@novell.com>,
        Steve McLain <SMCLAIN@novell.com>, Tom Doman <TDoman@novell.com>
Subject: Re: ABNF of numericoid
In-Reply-To: <sf0c4714.048@prv-mail20.provo.novell.com>
References: <sf0c4714.048@prv-mail20.provo.novell.com>
X-Mailer: VM 6.37 under Emacs 19.34.1
Date: Thu, 10 Jul 2003 13:57: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
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

Jim Sermersheim writes:
> In [Models], we define:
> numericoid = number *( DOT number )
> 
> This allows an invalid oid like 23.666.<whatever>
> 
> Are there usages of numericoid that need to allow these non-valid oids?
> If not, I think it'd be better to show the proper restrictions on the
> first two numbers.

Including the restriction that there should be at least two numbers,
IIRC.

-- 
Hallvard


From owner-ietf-ldapbis@OpenLDAP.org  Thu Jul 10 09:17:26 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00651
	for <ldapbis-archive@lists.ietf.org>; Thu, 10 Jul 2003 09:17:25 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6ADFqkf031024;
	Thu, 10 Jul 2003 13:16:13 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h6ADC2As030907;
	Thu, 10 Jul 2003 13:12:02 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 10 Jul 2003 13:12:02 +0000
Received: from smtp.unc.edu (smtpsrv10.isis.unc.edu [152.2.1.241])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6ADBvkb030853;
	Thu, 10 Jul 2003 13:11:58 GMT
	(envelope-from ses@unc.edu)
Received: from [192.168.1.101] (rdu57-255-231.nc.rr.com [66.57.255.231])
	(authenticated bits=0)
	by smtp.unc.edu (8.12.9/8.12.9) with ESMTP id h6ADB4WX029364
	(version=TLSv1/SSLv3 cipher=IDEA-CBC-SHA bits=128 verify=NOT);
	Thu, 10 Jul 2003 09:11:05 -0400 (EDT)
Date: Thu, 10 Jul 2003 09:10:59 -0400
From: Simon Spero <ses@unc.edu>
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>, ietf-ldapbis@OpenLDAP.org
cc: agenda@ietf.org
Subject: Re: Agenda for LDAPBIS @ IETF#57
Message-ID: <96624968.1057828259@[192.168.1.101]>
In-Reply-To: <5.2.0.9.0.20030708070442.01bb5a60@127.0.0.1>
References: <5.2.0.9.0.20030708070442.01bb5a60@127.0.0.1>
X-Mailer: Mulberry/3.0.2 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

--On Tuesday, July 08, 2003 7:16 AM -0700 "Kurt D. Zeilenga" 
<Kurt@OpenLDAP.org> wrote:

> LDAP (v3) Revision (LDAPBIS) WG

> TUESDAY, July 15, 2003
> 1415-1515 Afternoon Sessions II

Is this going to multicast? I'm assuming all times are Z+2?


From owner-ietf-ldapbis@OpenLDAP.org  Thu Jul 10 18:01:21 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23798
	for <ldapbis-archive@lists.ietf.org>; Thu, 10 Jul 2003 18:01:19 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6ALvtkf057700;
	Thu, 10 Jul 2003 22:00:14 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h6ALufRs057636;
	Thu, 10 Jul 2003 21:56:41 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 10 Jul 2003 21:56:41 +0000
Received: from rembrandt.esys.ca (rembrandt.esys.ca [198.161.92.131])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6ALuckb057606;
	Thu, 10 Jul 2003 21:56:38 GMT
	(envelope-from Alexey.Melnikov@isode.com)
Received: from isode.com (1Cust29.tnt101.lnd4.gbr.da.uu.net [213.116.50.29])
	(authenticated)
	by rembrandt.esys.ca (8.11.6/8.11.0.Beta0) with ESMTP id h6AM0EV19005;
	Thu, 10 Jul 2003 16:00:16 -0600
Message-ID: <3F0DDFF6.20AE6525@isode.com>
Date: Thu, 10 Jul 2003 15:51:50 -0600
From: Alexey Melnikov <Alexey.Melnikov@isode.com>
Organization: Isode Limited
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
CC: ietf-ldapbis@OpenLDAP.org
Subject: Re: Agenda for LDAPBIS @ IETF#57
References: <5.2.0.9.0.20030708070442.01bb5a60@127.0.0.1> <96624968.1057828259@[192.168.1.101]>
Content-Type: text/plain; charset=koi8-r
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 Spero wrote:

> --On Tuesday, July 08, 2003 7:16 AM -0700 "Kurt D. Zeilenga"
> <Kurt@OpenLDAP.org> wrote:
>
> > LDAP (v3) Revision (LDAPBIS) WG
>
> > TUESDAY, July 15, 2003
> > 1415-1515 Afternoon Sessions II
>
> Is this going to multicast? I'm assuming all times are Z+2?

Can somebody at least take Jabber notes?

Alexey
__________________________________________
Home Page: http://orthanc.ab.ca/mel
IETF standard
related pages: http://orthanc.ab.ca/mel/devel/Links.html
__________________________________________





From owner-ietf-ldapbis@OpenLDAP.org  Fri Jul 11 16:57:12 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16528
	for <ldapbis-archive@lists.ietf.org>; Fri, 11 Jul 2003 16:57:11 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6BKk2lN008541;
	Fri, 11 Jul 2003 20:55:45 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h6BKicP9008376;
	Fri, 11 Jul 2003 20:44:38 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Fri, 11 Jul 2003 20:44:38 +0000
Received: from boole.openldap.org (kurt@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6BKibkb008365
	for <ietf-ldapbis@openldap.org>; Fri, 11 Jul 2003 20:44:37 GMT
	(envelope-from kurt@boole.openldap.org)
Received: (from kurt@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) id h6BKibwq008364
	for ietf-ldapbis@openldap.org; Fri, 11 Jul 2003 20:44:37 GMT
	(envelope-from kurt)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6ADMDkb031375;
	Thu, 10 Jul 2003 13:22:14 GMT
	(envelope-from dinaras@ietf.org)
Received: from dinaras.cnri.reston.va.us (host-4-46.cnri.reston.va.us [10.27.4.46])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00874;
	Thu, 10 Jul 2003 09:22:05 -0400 (EDT)
Message-Id: <5.1.0.14.2.20030710092021.04d47ae0@odin>
X-Sender: dinaras@odin
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Thu, 10 Jul 2003 09:22:11 -0400
To: Simon Spero <ses@unc.edu>, "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>,
        ietf-ldapbis@OpenLDAP.org
From: Dinara Suleymanova <dinaras@ietf.org>
Subject: Re: Agenda for LDAPBIS @ IETF#57
Cc: agenda@ietf.org
In-Reply-To: <96624968.1057828259@[192.168.1.101]>
References: <5.2.0.9.0.20030708070442.01bb5a60@127.0.0.1>
 <5.2.0.9.0.20030708070442.01bb5a60@127.0.0.1>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

Hi Kurt,

If your initial request came with the request for multicast then you should 
have it.
But unfortunately, it was not in your request. So the multicast room was 
not assigned to you.

Dinara Suleymanova

At 09:10 AM 7/10/03 -0400, Simon Spero wrote:
>--On Tuesday, July 08, 2003 7:16 AM -0700 "Kurt D. Zeilenga" 
><Kurt@OpenLDAP.org> wrote:
>
>>LDAP (v3) Revision (LDAPBIS) WG
>
>>TUESDAY, July 15, 2003
>>1415-1515 Afternoon Sessions II
>
>Is this going to multicast? I'm assuming all times are Z+2?


From owner-ietf-ldapbis@OpenLDAP.org  Mon Jul 14 03:20:31 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA29318
	for <ldapbis-archive@lists.ietf.org>; Mon, 14 Jul 2003 03:20:30 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6E7GLkn006077;
	Mon, 14 Jul 2003 07:19:17 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h6E76paR005693;
	Mon, 14 Jul 2003 07:06:51 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 14 Jul 2003 07:06:51 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6E76okb005683
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 14 Jul 2003 07:06:50 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from nomad.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.8/8.12.8) with ESMTP id h6E76hc8080394;
	Mon, 14 Jul 2003 07:06:45 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030714053706.01cda048@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Mon, 14 Jul 2003 05:54:08 +0200
To: "Jim Sermersheim" <jimse@novell.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: ABNF of numericoid
Cc: <ietf-ldapbis@OpenLDAP.org>, "Duane Buss" <DBuss@novell.com>,
        "Steve McLain" <SMCLAIN@novell.com>, "Tom Doman" <TDoman@novell.com>
In-Reply-To: <sf0c4714.048@prv-mail20.provo.novell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

At 12:45 AM 7/10/2003, Jim Sermersheim wrote:
>All,
>
>In [Models], we define:
>numericoid = number *( DOT number )
>
>This allows an invalid oid like 23.666.<whatever>
>
>Are there usages of numericoid that need to allow these non-valid oids?
>If not, I think it'd be better to show the proper restrictions on the
>first two numbers.

I think it inappropriate to restrict the syntax of a OID
based upon current assignments and assignment practices.
These are subject to change.   numericoid, like the BER
encoding of an OID, needs to be capable of representing
any OID value allowed by X.680.

For example, 3 is a valid representation of an unassigned
OID. It may one day be assigned.  However, assigned or not,
3 may be a reasonable value of an attribute of syntax OID.

I can think of a number of applications where storing
unassigned OIDs in a directory may be useful.  For example,
in an application which tracked usage of unassigned OIDs in
Internet protocols.

Kurt 



From owner-ietf-ldapbis@OpenLDAP.org  Mon Jul 14 03:49:35 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA00055
	for <ldapbis-archive@lists.ietf.org>; Mon, 14 Jul 2003 03:49:34 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6E7kMkr008215;
	Mon, 14 Jul 2003 07:48:46 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h6E7k0r7008197;
	Mon, 14 Jul 2003 07:46:00 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 14 Jul 2003 07:46:00 +0000
Received: from prv-mail20.provo.novell.com (prv-mail20.provo.novell.com [137.65.81.122])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6E7jxkb008186
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 14 Jul 2003 07:45:59 GMT
	(envelope-from jimse@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Mon, 14 Jul 2003 01:45:35 -0600
Message-Id: <sf120b3f.046@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.1 
Date: Mon, 14 Jul 2003 01:43:20 -0600
From: "Jim Sermersheim" <jimse@novell.com>
To: <ietf-ldapbis@OpenLDAP.org>
Cc: "Duane Buss" <DBuss.PRV-1.PROVO@novell.com>,
        "Steve McLain" <SMCLAIN@novell.com>,
        "Tom Doman" <TDoman.PRV-1.PROVO@novell.com>
Subject: Re: ABNF of numericoid
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

>numericoid, like the BER
>encoding of an OID, needs to be capable of representing
>any OID value allowed by X.680.

Don't the BER-encoding rules for packing the first two object
identifier components into a single octet ((X * 40) + Y) constrain them
(albeit not constrained to today's constraints)?

Jim


>>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 7/14/03 5:54:08 AM >>>
At 12:45 AM 7/10/2003, Jim Sermersheim wrote:
>All,
>
>In [Models], we define:
>numericoid = number *( DOT number )
>
>This allows an invalid oid like 23.666.<whatever>
>
>Are there usages of numericoid that need to allow these non-valid
oids?
>If not, I think it'd be better to show the proper restrictions on the
>first two numbers.

I think it inappropriate to restrict the syntax of a OID
based upon current assignments and assignment practices.
These are subject to change.   numericoid, like the BER
encoding of an OID, needs to be capable of representing
any OID value allowed by X.680.

For example, 3 is a valid representation of an unassigned
OID. It may one day be assigned.  However, assigned or not,
3 may be a reasonable value of an attribute of syntax OID.

I can think of a number of applications where storing
unassigned OIDs in a directory may be useful.  For example,
in an application which tracked usage of unassigned OIDs in
Internet protocols.

Kurt 



From owner-ietf-ldapbis@OpenLDAP.org  Mon Jul 14 03:53:33 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA00201
	for <ldapbis-archive@lists.ietf.org>; Mon, 14 Jul 2003 03:53:32 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6E7qMkf008644;
	Mon, 14 Jul 2003 07:52:25 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h6E7qFgn008634;
	Mon, 14 Jul 2003 07:52:15 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 14 Jul 2003 07:52:15 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6E7qEkb008623
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 14 Jul 2003 07:52:14 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from nomad.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.8/8.12.8) with ESMTP id h6E7q3c6080709;
	Mon, 14 Jul 2003 07:52:04 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030714094611.01d4f898@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Mon, 14 Jul 2003 09:48:52 +0200
To: Alexey Melnikov <Alexey.Melnikov@isode.com>, Simon Spero <ses@unc.edu>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: Agenda for LDAPBIS @ IETF#57
Cc: ietf-ldapbis@OpenLDAP.org
In-Reply-To: <3F0DDFF6.20AE6525@isode.com>
References: <5.2.0.9.0.20030708070442.01bb5a60@127.0.0.1>
 <96624968.1057828259@[192.168.1.101]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

At 11:51 PM 7/10/2003, Alexey Melnikov wrote:
>Simon Spero wrote:
>> Is this going to multicast? I'm assuming all times are Z+2?

Yes.

>Can somebody at least take Jabber notes? 

We'll try to get our session scribe to Jabber...

Kurt, LDAPBIS co-chair




From owner-ietf-ldapbis@OpenLDAP.org  Mon Jul 14 04:36:35 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01883
	for <ldapbis-archive@lists.ietf.org>; Mon, 14 Jul 2003 04:36:34 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6E8YMkh010448;
	Mon, 14 Jul 2003 08:34:32 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h6E8WQAo010390;
	Mon, 14 Jul 2003 08:32:26 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 14 Jul 2003 08:32:26 +0000
Received: from ausyms50.ca.com ([155.35.248.106])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6E8WOkb010359
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 14 Jul 2003 08:32:24 GMT
	(envelope-from Ron.Ramsay@ca.com)
Received: from ausyms21.ca.com ([155.35.201.5]) by ausyms50.ca.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Mon, 14 Jul 2003 18:32:01 +1000
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: ABNF of numericoid
Date: Mon, 14 Jul 2003 18:32:00 +1000
Message-ID: <1395B4B334FCC143B36AF788E68B63814C064C@ausyms21.ca.com>
Thread-Topic: ABNF of numericoid
Thread-Index: AcNJ3GGVe2W9buruQ+O7UxfTwOqUZAABXP+A
From: "Ramsay, Ron" <Ron.Ramsay@ca.com>
To: "Jim Sermersheim" <jimse@novell.com>, <ietf-ldapbis@OpenLDAP.org>
X-OriginalArrivalTime: 14 Jul 2003 08:32:01.0152 (UTC) FILETIME=[658A8800:01C349E2]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by boole.openldap.org id h6E8WPkb010381
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.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

Is the packing rule: X < 6 && Y < 40
or is it: X < 3 && (X < 2) ? Y < 40 : Y < 175

?

-----Original Message-----
From: Jim Sermersheim [mailto:jimse@novell.com]
Sent: Monday, 14 July 2003 17:43
To: ietf-ldapbis@OpenLDAP.org
Cc: Duane Buss; Steve McLain; Tom Doman
Subject: Re: ABNF of numericoid


>numericoid, like the BER
>encoding of an OID, needs to be capable of representing
>any OID value allowed by X.680.

Don't the BER-encoding rules for packing the first two object
identifier components into a single octet ((X * 40) + Y) constrain them
(albeit not constrained to today's constraints)?

Jim


>>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 7/14/03 5:54:08 AM >>>
At 12:45 AM 7/10/2003, Jim Sermersheim wrote:
>All,
>
>In [Models], we define:
>numericoid = number *( DOT number )
>
>This allows an invalid oid like 23.666.<whatever>
>
>Are there usages of numericoid that need to allow these non-valid
oids?
>If not, I think it'd be better to show the proper restrictions on the
>first two numbers.

I think it inappropriate to restrict the syntax of a OID
based upon current assignments and assignment practices.
These are subject to change.   numericoid, like the BER
encoding of an OID, needs to be capable of representing
any OID value allowed by X.680.

For example, 3 is a valid representation of an unassigned
OID. It may one day be assigned.  However, assigned or not,
3 may be a reasonable value of an attribute of syntax OID.

I can think of a number of applications where storing
unassigned OIDs in a directory may be useful.  For example,
in an application which tracked usage of unassigned OIDs in
Internet protocols.

Kurt 





From owner-ietf-ldapbis@OpenLDAP.org  Mon Jul 14 05:04:15 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02807
	for <ldapbis-archive@lists.ietf.org>; Mon, 14 Jul 2003 05:04:14 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6E8qMlJ012061;
	Mon, 14 Jul 2003 09:03:11 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h6E8l7gw011697;
	Mon, 14 Jul 2003 08:47:07 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 14 Jul 2003 08:47:07 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6E8l6kb011686
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 14 Jul 2003 08:47:06 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from nomad.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.8/8.12.8) with ESMTP id h6E8l2c6081026;
	Mon, 14 Jul 2003 08:47:03 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030714102517.01d53a78@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Mon, 14 Jul 2003 10:43:51 +0200
To: "Jim Sermersheim" <jimse@novell.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: ABNF of numericoid
Cc: <ietf-ldapbis@OpenLDAP.org>, "Duane Buss" <DBuss.PRV-1.PROVO@novell.com>,
        "Steve McLain" <SMCLAIN@novell.com>,
        "Tom Doman" <TDoman.PRV-1.PROVO@novell.com>
In-Reply-To: <sf120b3f.046@prv-mail20.provo.novell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

I've been advised that my previous post is mostly incorrect.
Steven will post the real scoop.

Kurt



From owner-ietf-ldapbis@OpenLDAP.org  Mon Jul 14 17:26:17 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26936
	for <ldapbis-archive@lists.ietf.org>; Mon, 14 Jul 2003 17:26:17 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6ELMRkf075701;
	Mon, 14 Jul 2003 21:24:29 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h6ELJ7qU075580;
	Mon, 14 Jul 2003 21:19:07 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 14 Jul 2003 21:19:07 +0000
Received: from prv-mail20.provo.novell.com (prv-mail20.provo.novell.com [137.65.81.122])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6ELIxkb075534
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 14 Jul 2003 21:19:02 GMT
	(envelope-from jimse@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Mon, 14 Jul 2003 15:18:36 -0600
Message-Id: <sf12c9cc.021@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.1 
Date: Mon, 14 Jul 2003 15:16:38 -0600
From: "Jim Sermersheim" <jimse@novell.com>
To: <ietf-ldapbis@OpenLDAP.org>
Subject: Protocol: Ignore SEQUENCE elements...
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

All,
 
There is the statement in [Protocol] that instructs:
"Because of the implied extensibility, clients and servers MUST ignore
trailing SEQUENCE elements whose tags they do not recognize."
 
This is basically the same text as RFC2251 (we added the _why_, and the
word "trailing").
 
But I think this falls short of what it really intends to say. I think
that what it really intends to say is that:
"protocol peers MUST ignore the presence of arbitrary unexpected
extension additions above those defined (if any) in a SEQUENCE or SET
type, or of an unknown alternative in a CHOICE type, or an unknown
ENUMERATION in an enumerated type, or of an unexpected length or value
of a type whose constraint is extensible."

I just stole most of that from X.680, thus it could be shortened with a
reference, but I think the information might be handy. Also, we should
likely preserve the "trailing" word.

a) Am I basing this on some false assumption/information?
b) Do we want to make this change?

Jim


From owner-ietf-ldapbis@OpenLDAP.org  Tue Jul 15 05:58:05 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA11884
	for <ldapbis-archive@lists.ietf.org>; Tue, 15 Jul 2003 05:58:03 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6F9qVkf030775;
	Tue, 15 Jul 2003 09:56:59 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h6F9nQAf030618;
	Tue, 15 Jul 2003 09:49:26 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 15 Jul 2003 09:49:26 +0000
Received: from prv-mail25.provo.novell.com (prv-mail25.provo.novell.com [137.65.81.121])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6F9nPkb030593
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 15 Jul 2003 09:49:25 GMT
	(envelope-from GVithalprasad@novell.com)
Received: from INET-PRV1-MTA by prv-mail25.provo.novell.com
	with Novell_GroupWise; Tue, 15 Jul 2003 03:49:05 -0600
Message-Id: <sf1379b1.070@prv-mail25.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.1 
Date: Tue, 15 Jul 2003 03:48:28 -0600
From: "Vithalprasad Gaitonde" <GVithalprasad@novell.com>
To: <ietf-ldapbis@OpenLDAP.org>
Subject: Re: Agenda for LDAPBIS @ IETF#57
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Since Roger is not here, I will present the slides on authmeth that he
sent to me.

Prasad

>>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 07/08 7:46 PM >>>
LDAP (v3) Revision (LDAPBIS) WG 

TUESDAY, July 15, 2003
1415-1515 Afternoon Sessions II
Hall LM

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

1) Preliminaries - 5m - chairs
2) draft-ietf-ldapbis-protocol - 20m - editor*
3) draft-ietf-ldapbis-authmeth - 20m - editor*
4) Other issues / Open mic - as time permits - WG

* other WG members will fill in where the editor is unavailable 



From owner-ietf-ldapbis@OpenLDAP.org  Wed Jul 16 13:10:55 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08780
	for <ldapbis-archive@lists.ietf.org>; Wed, 16 Jul 2003 13:10:52 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6GH4fkf000801;
	Wed, 16 Jul 2003 17:09:45 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h6GH0Q0U099487;
	Wed, 16 Jul 2003 17:00:26 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 16 Jul 2003 17:00:26 +0000
Received: from boole.openldap.org (kurt@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6GH0Pkb099475
	for <ietf-ldapbis@openldap.org>; Wed, 16 Jul 2003 17:00:25 GMT
	(envelope-from kurt@boole.openldap.org)
Received: (from kurt@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) id h6GH0PED099474
	for ietf-ldapbis@openldap.org; Wed, 16 Jul 2003 17:00:25 GMT
	(envelope-from kurt)
Received: from usergg026.dsl.pipex.com (usergg026.dsl.pipex.com [62.190.174.26])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6GDYfkb085799
	for <ietf-ldapbis@openldap.org>; Wed, 16 Jul 2003 13:34:42 GMT
	(envelope-from David.Wilson@isode.com)
Received: from 82-43-128-26.cable.ubr03.mort.blueyonder.co.uk ([82.43.128.26]) by usergg026.dsl.pipex.com
          via TCP (with SMTP (internal)) with ESMTP
          for <ietf-ldapbis@openldap.org>;
          Wed, 16 Jul 2003 14:34:28 +0100
Subject: Re: draft-ietf-ldapbis-strprep-00.txt
From: David Wilson <David.Wilson@isode.com>
To: ietf-ldapbis@OpenLDAP.org
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Ximian Evolution 1.0.8 (1.0.8-9.7x.1) 
Date: 16 Jul 2003 14:34:27 +0100
Message-Id: <1058362468.28249.271.camel@alpha.isode.net>
Mime-Version: 1.0
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit



For our business, the use of X.500/LDAP for X.400 messaging is 
important. One aspect of that is the mapping of X.400 O/R addresses to 
DNs (e.g. RFC 1836). To avoid having to do any complicated string 
mapping, it is very useful if the matching rules in the Directory 
service match the requirements for equivalence for X.400 O/R address 
attribute values. The latter is specified in X.402 (ISO 10021-2) Section
18.4. For our purposes the main issue is here: 

g) In a Teletex String, the Non-spacing underline graphic character 
shall be considered insignificant, as shall all control functions except
Space and those used for code extension procedures. 

(Although I think drafts have proposed ISO 10646 values, I don't think 
these have been ratified. So we are basically dealing with 
PrintableString and TeletexString values). 

If this is interpreted as meaning that CR and LF, for instance are to be
ignored, then this does not make sense to me. I cannot see that 

        "foo" CR LF "bar" 

should match "foobar". The mapping of the standard "carriage movement" 
control characters to space makes much more sense. 

However, there remains the non-spacing underline graphic character 
(which is code 12/12, xcc, in its normal position). I presume this is 
present in the character set to provide an underlining function for a 
physical terminal (the same kind of function performed on an ANSI 
terminal by a control function for rendition). T.61 does not specify 
that this non-spacing character forms any new characters, unlike the 
other non-spacing diacriticals (c.f. T.61 Annex B). 

The corresponding Unicode character is U+0332, and there is also U+0333 
which is the double underline. Unicode 2 had a compatibility composition
of space + U+0332 to U+005F, i.e. the normal underscore. However, this 
is not present in Unicode 4.01. 

All of this is a long-winded way of saying that I think that 

        COMBINING LOW LINE (U+0332) 
        COMBINING DOUBLE LOW LINE (U+0333) 

should also be mapped to nothing (section 2.2). 

regards 

David Wilson                             David.Wilson@isode.com
Isode Limited                            Tel: +44 020 8607 9125 
http://www.isode.com


From owner-ietf-ldapbis@OpenLDAP.org  Thu Jul 17 03:26:13 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA19817
	for <ldapbis-archive@lists.ietf.org>; Thu, 17 Jul 2003 03:26:13 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6H7Mkkf036550;
	Thu, 17 Jul 2003 07:24:45 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h6H7K9BL036494;
	Thu, 17 Jul 2003 07:20:09 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 17 Jul 2003 07:20:09 +0000
Received: from prv-mail20.provo.novell.com (prv-mail20.provo.novell.com [137.65.81.122])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6H7K8kb036477
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 17 Jul 2003 07:20:08 GMT
	(envelope-from jimse@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Thu, 17 Jul 2003 01:19:47 -0600
Message-Id: <sf15f9b3.079@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.1 
Date: Wed, 16 Jul 2003 15:39:28 -0600
From: "Jim Sermersheim" <jimse@novell.com>
To: <ietf-ldapbis@OpenLDAP.org>
Subject: RE: Attribute Name Length Bounds
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__Part84DAA300.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.

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

All,
 
At this point it seems clear that it would be a good thing to make a
clarification to [Protocols]. That clarification would state something
like: all octets of a ber-encoded LDAP PDU are significant. No octets
may be ignored unless they are part of extended elements that are
themselves ignored.
 
Whether or not we want the TS to enforce mandatory minimums for element
lengths (such as attribute type names) is an issue in the data model
(and/or schema) doc(s).
 
Jim

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

<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 5.50.4926.2500" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Microsoft Sans Serif">
<DIV>All,</DIV>
<DIV>&nbsp;</DIV>
<DIV>At this point it seems clear that it would be a good thing to make a clarification to [Protocols]. That clarification would state something like:&nbsp;all octets of a ber-encoded LDAP PDU are significant. No octets may be ignored unless they are part of extended elements that are themselves ignored.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Whether or not we want the TS to&nbsp;enforce mandatory minimums for element lengths (such as attribute type names) is an issue in the data model (and/or schema) doc(s).</DIV>
<DIV>&nbsp;</DIV>
<DIV>Jim</DIV></BODY></HTML>
--=__Part84DAA300.0__=--


From owner-ietf-ldapbis@OpenLDAP.org  Thu Jul 17 03:53:57 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA21380
	for <ldapbis-archive@lists.ietf.org>; Thu, 17 Jul 2003 03:53:57 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6H7qkkf037450;
	Thu, 17 Jul 2003 07:52:53 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h6H7migK037350;
	Thu, 17 Jul 2003 07:48:44 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 17 Jul 2003 07:48:44 +0000
Received: from ausyms50.ca.com ([155.35.248.106])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6H7mgkb037338
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 17 Jul 2003 07:48:43 GMT
	(envelope-from Ron.Ramsay@ca.com)
Received: from ausyms21.ca.com ([155.35.201.5]) by ausyms50.ca.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Thu, 17 Jul 2003 17:48:21 +1000
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C34C37.CAFCA274"
Subject: RE: Attribute Name Length Bounds
Date: Thu, 17 Jul 2003 17:48:20 +1000
Message-ID: <1395B4B334FCC143B36AF788E68B63814DFB4E@ausyms21.ca.com>
Thread-Topic: Attribute Name Length Bounds
Thread-Index: AcNMNI77fRMjJHkCQkmashYT1S4v+QAAv+DA
From: "Ramsay, Ron" <Ron.Ramsay@ca.com>
To: "Jim Sermersheim" <jimse@novell.com>, <ietf-ldapbis@OpenLDAP.org>
X-OriginalArrivalTime: 17 Jul 2003 07:48:21.0153 (UTC) FILETIME=[CB23A910:01C34C37]
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C34C37.CAFCA274
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Jim,
=20
Is there a point to the 'clarification'? Isn't it like saying that all =
octets of a JPEG file are significant? Sorry, I don't see the point.
=20
Ron

-----Original Message-----
From: Jim Sermersheim [mailto:jimse@novell.com]
Sent: Thursday, 17 July 2003 07:39
To: ietf-ldapbis@OpenLDAP.org
Subject: RE: Attribute Name Length Bounds


All,
=20
At this point it seems clear that it would be a good thing to make a =
clarification to [Protocols]. That clarification would state something =
like: all octets of a ber-encoded LDAP PDU are significant. No octets =
may be ignored unless they are part of extended elements that are =
themselves ignored.
=20
Whether or not we want the TS to enforce mandatory minimums for element =
lengths (such as attribute type names) is an issue in the data model =
(and/or schema) doc(s).
=20
Jim


------_=_NextPart_001_01C34C37.CAFCA274
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<META content=3D"MSHTML 5.50.4807.2300" name=3DGENERATOR></HEAD>
<BODY style=3D"MARGIN: 4px 4px 1px; FONT: 10pt Microsoft Sans Serif">
<DIV><SPAN class=3D488394607-17072003>Hi Jim,</SPAN></DIV>
<DIV><SPAN class=3D488394607-17072003></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D488394607-17072003>Is there a point to the =
'clarification'?=20
Isn't it like saying that all octets of a JPEG file are significant? =
Sorry, I=20
don't see the point.</SPAN></DIV>
<DIV><SPAN class=3D488394607-17072003></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D488394607-17072003>Ron</SPAN></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT=20
  face=3DTahoma>-----Original Message-----<BR><B>From:</B> Jim =
Sermersheim=20
  [mailto:jimse@novell.com]<BR><B>Sent:</B> Thursday, 17 July 2003=20
  07:39<BR><B>To:</B> ietf-ldapbis@OpenLDAP.org<BR><B>Subject:</B> RE: =
Attribute=20
  Name Length Bounds<BR><BR></FONT></DIV>
  <DIV>All,</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>At this point it seems clear that it would be a good thing to =
make a=20
  clarification to [Protocols]. That clarification would state something =

  like:&nbsp;all octets of a ber-encoded LDAP PDU are significant. No =
octets may=20
  be ignored unless they are part of extended elements that are =
themselves=20
  ignored.</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>Whether or not we want the TS to&nbsp;enforce mandatory minimums =
for=20
  element lengths (such as attribute type names) is an issue in the data =
model=20
  (and/or schema) doc(s).</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>Jim</DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C34C37.CAFCA274--


From owner-ietf-ldapbis@OpenLDAP.org  Thu Jul 17 04:52:51 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA23978
	for <ldapbis-archive@lists.ietf.org>; Thu, 17 Jul 2003 04:52:50 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6H8ell7039014;
	Thu, 17 Jul 2003 08:51:48 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h6H8cFfS038888;
	Thu, 17 Jul 2003 08:38:15 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 17 Jul 2003 08:38:15 +0000
Received: from prv-mail20.provo.novell.com (prv-mail20.provo.novell.com [137.65.81.122])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6H8cEkb038868
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 17 Jul 2003 08:38:14 GMT
	(envelope-from jimse@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Thu, 17 Jul 2003 02:37:53 -0600
Message-Id: <sf160c01.030@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.1 
Date: Thu, 17 Jul 2003 02:35:22 -0600
From: "Jim Sermersheim" <jimse@novell.com>
To: <Ron.Ramsay@ca.com>, <ietf-ldapbis@OpenLDAP.org>
Subject: RE: Attribute Name Length Bounds
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__PartC49AE0DA.1__="
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

This is a MIME message. If you are reading this text, you may want to 
consider changing to a mail reader or gateway that understands how to 
properly handle MIME multipart messages.

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

I think you're right, it doesn't cross the typical mind that one can
silently ignore sections of values. Apparently it did cross the mind of
at least one implementor, as it was pointed out in the IETF57 LDAPBIS
meeting that at least one implementor ignores some octets in certain PDU
values.
 
I believe there is text in X.680 that specifies that all octets are
significant--this clarification would really just be a repetition of
that statement. Maybe another way of looking at it is: this is an item
called out in a reference document that we need to carry into the
referring document because people aren't fully reading or understanding
the reference document.
 
Jim

>>> "Ramsay, Ron" <Ron.Ramsay@ca.com> 7/17/03 9:48:20 AM >>>

Hi Jim,
 
Is there a point to the 'clarification'? Isn't it like saying that all
octets of a JPEG file are significant? Sorry, I don't see the point.
 
Ron
-----Original Message-----
From: Jim Sermersheim [mailto:jimse@novell.com]
Sent: Thursday, 17 July 2003 07:39
To: ietf-ldapbis@OpenLDAP.org
Subject: RE: Attribute Name Length Bounds


All,
 
At this point it seems clear that it would be a good thing to make a
clarification to [Protocols]. That clarification would state something
like: all octets of a ber-encoded LDAP PDU are significant. No octets
may be ignored unless they are part of extended elements that are
themselves ignored.
 
Whether or not we want the TS to enforce mandatory minimums for element
lengths (such as attribute type names) is an issue in the data model
(and/or schema) doc(s).
 
Jim


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

<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 5.50.4926.2500" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Microsoft Sans Serif">
<DIV>I think you're right, it doesn't cross the typical mind that one can silently ignore sections of values. Apparently it did cross the mind of at least one implementor, as it was pointed out in the IETF57 LDAPBIS&nbsp;meeting that at least one implementor ignores some octets in certain PDU values.</DIV>
<DIV>&nbsp;</DIV>
<DIV>I believe there is text in X.680 that specifies that all octets are significant--this clarification would really just be a repetition of that statement. Maybe another way of looking at it is: this is&nbsp;an item called out in a reference document that we need to carry into the referring document because people aren't fully reading or understanding the reference document.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Jim<BR><BR>&gt;&gt;&gt; "Ramsay, Ron" &lt;Ron.Ramsay@ca.com&gt; 7/17/03 9:48:20 AM &gt;&gt;&gt;<BR></DIV>
<DIV style="FONT: 10pt Microsoft Sans Serif; COLOR: #000000">
<DIV><SPAN class=488394607-17072003>Hi Jim,</SPAN></DIV>
<DIV><SPAN class=488394607-17072003></SPAN>&nbsp;</DIV>
<DIV><SPAN class=488394607-17072003>Is there a point to the 'clarification'? Isn't it like saying that all octets of a JPEG file are significant? Sorry, I don't see the point.</SPAN></DIV>
<DIV><SPAN class=488394607-17072003></SPAN>&nbsp;</DIV>
<DIV><SPAN class=488394607-17072003>Ron</SPAN></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma>-----Original Message-----<BR><B>From:</B> Jim Sermersheim [mailto:jimse@novell.com]<BR><B>Sent:</B> Thursday, 17 July 2003 07:39<BR><B>To:</B> ietf-ldapbis@OpenLDAP.org<BR><B>Subject:</B> RE: Attribute Name Length Bounds<BR><BR></FONT></DIV>
<DIV>All,</DIV>
<DIV>&nbsp;</DIV>
<DIV>At this point it seems clear that it would be a good thing to make a clarification to [Protocols]. That clarification would state something like:&nbsp;all octets of a ber-encoded LDAP PDU are significant. No octets may be ignored unless they are part of extended elements that are themselves ignored.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Whether or not we want the TS to&nbsp;enforce mandatory minimums for element lengths (such as attribute type names) is an issue in the data model (and/or schema) doc(s).</DIV>
<DIV>&nbsp;</DIV>
<DIV>Jim</DIV></BLOCKQUOTE></DIV></BODY></HTML>
--=__PartC49AE0DA.1__=--


From owner-ietf-ldapbis@OpenLDAP.org  Thu Jul 17 04:59:55 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA24136
	for <ldapbis-archive@lists.ietf.org>; Thu, 17 Jul 2003 04:59:54 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6H8wkkf040057;
	Thu, 17 Jul 2003 08:58:51 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h6H8vO1Q040014;
	Thu, 17 Jul 2003 08:57:24 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 17 Jul 2003 08:57:24 +0000
Received: from ausyms50.ca.com ([155.35.248.106])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6H8vMkb039995
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 17 Jul 2003 08:57:23 GMT
	(envelope-from Ron.Ramsay@ca.com)
Received: from ausyms21.ca.com ([155.35.201.5]) by ausyms50.ca.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Thu, 17 Jul 2003 18:57:01 +1000
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C34C41.62C42D95"
Subject: RE: Attribute Name Length Bounds
Date: Thu, 17 Jul 2003 18:57:01 +1000
Message-ID: <1395B4B334FCC143B36AF788E68B63814DFB98@ausyms21.ca.com>
Thread-Topic: Attribute Name Length Bounds
Thread-Index: AcNMPsk/3T86Bd42TL6qe26ZLK+3NwAAdFiA
From: "Ramsay, Ron" <Ron.Ramsay@ca.com>
To: "Jim Sermersheim" <jimse@novell.com>, <ietf-ldapbis@OpenLDAP.org>
X-OriginalArrivalTime: 17 Jul 2003 08:57:01.0272 (UTC) FILETIME=[62EBED80:01C34C41]
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C34C41.62C42D95
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Was the implementer actually ignoring octets in the PDU or was the =
implementer in fact ignoring octets in values taken from the PDU? It =
would seem strange, nay impossible, to ignore octets in a PDU. This =
means you would read the ID, read the length, take the first 20 bytes =
then .. what? Stop? If you stop taking bytes then you may not be at the =
next tag, so the decode would fail. If you continue taking bytes but =
don't store them, then you do regard the bytes in the PDU as =
significant.
=20
Therefore, I don't believe you can EVER ignore bytes IN a PDU. You may =
ignore them after slecting the value from the PDU, but not IN the PDU.
=20
Ron

-----Original Message-----
From: Jim Sermersheim [mailto:jimse@novell.com]
Sent: Thursday, 17 July 2003 18:35
To: Ramsay, Ron; ietf-ldapbis@OpenLDAP.org
Subject: RE: Attribute Name Length Bounds


I think you're right, it doesn't cross the typical mind that one can =
silently ignore sections of values. Apparently it did cross the mind of =
at least one implementor, as it was pointed out in the IETF57 LDAPBIS =
meeting that at least one implementor ignores some octets in certain PDU =
values.
=20
I believe there is text in X.680 that specifies that all octets are =
significant--this clarification would really just be a repetition of =
that statement. Maybe another way of looking at it is: this is an item =
called out in a reference document that we need to carry into the =
referring document because people aren't fully reading or understanding =
the reference document.
=20
Jim

>>> "Ramsay, Ron" <Ron.Ramsay@ca.com> 7/17/03 9:48:20 AM >>>

Hi Jim,
=20
Is there a point to the 'clarification'? Isn't it like saying that all =
octets of a JPEG file are significant? Sorry, I don't see the point.
=20
Ron

-----Original Message-----
From: Jim Sermersheim [mailto:jimse@novell.com]
Sent: Thursday, 17 July 2003 07:39
To: ietf-ldapbis@OpenLDAP.org
Subject: RE: Attribute Name Length Bounds


All,
=20
At this point it seems clear that it would be a good thing to make a =
clarification to [Protocols]. That clarification would state something =
like: all octets of a ber-encoded LDAP PDU are significant. No octets =
may be ignored unless they are part of extended elements that are =
themselves ignored.
=20
Whether or not we want the TS to enforce mandatory minimums for element =
lengths (such as attribute type names) is an issue in the data model =
(and/or schema) doc(s).
=20
Jim


------_=_NextPart_001_01C34C41.62C42D95
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<META content=3D"MSHTML 5.50.4807.2300" name=3DGENERATOR></HEAD>
<BODY style=3D"MARGIN: 4px 4px 1px; FONT: 10pt Microsoft Sans Serif">
<DIV><SPAN class=3D263255108-17072003>Was the implementer actually =
ignoring octets=20
in the PDU or was the implementer in fact ignoring octets in values =
taken from=20
the PDU? It would seem strange, nay impossible, to ignore octets in a =
PDU. This=20
means you would read the ID, read the length, take the first 20 bytes =
then ..=20
what? Stop? If you stop taking bytes then you may not be at the next =
tag, so the=20
decode would fail. If you continue taking bytes but don't store them, =
then you=20
do regard the bytes in the PDU as significant.</SPAN></DIV>
<DIV><SPAN class=3D263255108-17072003></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D263255108-17072003>Therefore, I don't believe you can =
EVER=20
ignore bytes IN a PDU. You may ignore them after slecting the value from =
the=20
PDU, but not IN the PDU.</SPAN></DIV>
<DIV><SPAN class=3D263255108-17072003></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D263255108-17072003>Ron</SPAN></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT=20
  face=3DTahoma>-----Original Message-----<BR><B>From:</B> Jim =
Sermersheim=20
  [mailto:jimse@novell.com]<BR><B>Sent:</B> Thursday, 17 July 2003=20
  18:35<BR><B>To:</B> Ramsay, Ron; =
ietf-ldapbis@OpenLDAP.org<BR><B>Subject:</B>=20
  RE: Attribute Name Length Bounds<BR><BR></FONT></DIV>
  <DIV>I think you're right, it doesn't cross the typical mind that one =
can=20
  silently ignore sections of values. Apparently it did cross the mind =
of at=20
  least one implementor, as it was pointed out in the IETF57=20
  LDAPBIS&nbsp;meeting that at least one implementor ignores some octets =
in=20
  certain PDU values.</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>I believe there is text in X.680 that specifies that all octets =
are=20
  significant--this clarification would really just be a repetition of =
that=20
  statement. Maybe another way of looking at it is: this is&nbsp;an item =
called=20
  out in a reference document that we need to carry into the referring =
document=20
  because people aren't fully reading or understanding the reference=20
  document.</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>Jim<BR><BR>&gt;&gt;&gt; "Ramsay, Ron" &lt;Ron.Ramsay@ca.com&gt; =
7/17/03=20
  9:48:20 AM &gt;&gt;&gt;<BR></DIV>
  <DIV style=3D"FONT: 10pt Microsoft Sans Serif; COLOR: #000000">
  <DIV><SPAN class=3D488394607-17072003>Hi Jim,</SPAN></DIV>
  <DIV><SPAN class=3D488394607-17072003></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D488394607-17072003>Is there a point to the =
'clarification'?=20
  Isn't it like saying that all octets of a JPEG file are significant? =
Sorry, I=20
  don't see the point.</SPAN></DIV>
  <DIV><SPAN class=3D488394607-17072003></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D488394607-17072003>Ron</SPAN></DIV>
  <BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
    <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT=20
    face=3DTahoma>-----Original Message-----<BR><B>From:</B> Jim =
Sermersheim=20
    [mailto:jimse@novell.com]<BR><B>Sent:</B> Thursday, 17 July 2003=20
    07:39<BR><B>To:</B> ietf-ldapbis@OpenLDAP.org<BR><B>Subject:</B> RE: =

    Attribute Name Length Bounds<BR><BR></FONT></DIV>
    <DIV>All,</DIV>
    <DIV>&nbsp;</DIV>
    <DIV>At this point it seems clear that it would be a good thing to =
make a=20
    clarification to [Protocols]. That clarification would state =
something=20
    like:&nbsp;all octets of a ber-encoded LDAP PDU are significant. No =
octets=20
    may be ignored unless they are part of extended elements that are =
themselves=20
    ignored.</DIV>
    <DIV>&nbsp;</DIV>
    <DIV>Whether or not we want the TS to&nbsp;enforce mandatory =
minimums for=20
    element lengths (such as attribute type names) is an issue in the =
data model=20
    (and/or schema) doc(s).</DIV>
    <DIV>&nbsp;</DIV>
    <DIV>Jim</DIV></BLOCKQUOTE></DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C34C41.62C42D95--


From owner-ietf-ldapbis@OpenLDAP.org  Thu Jul 17 05:18:11 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA25129
	for <ldapbis-archive@lists.ietf.org>; Thu, 17 Jul 2003 05:18:11 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6H9Glkf040853;
	Thu, 17 Jul 2003 09:16:59 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h6H9FeJJ040764;
	Thu, 17 Jul 2003 09:15:40 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 17 Jul 2003 09:15:40 +0000
Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6H9Fdkb040752
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 17 Jul 2003 09:15:39 GMT
	(envelope-from rlmorgan@washington.edu)
Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9])
	by mxout1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h6H9FXoa029863;
	Thu, 17 Jul 2003 02:15:33 -0700
Received: from [81.160.241.11] ([81.160.241.11])
	(authenticated bits=0)
	by smtp.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h6H9FTXa012550
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT);
	Thu, 17 Jul 2003 02:15:32 -0700
Date: Thu, 17 Jul 2003 11:15:53 +0200 (CEST)
From: "RL 'Bob' Morgan" <rlmorgan@washington.edu>
X-X-Sender: rlmorgan@localhost.localdomain
To: Jim Sermersheim <jimse@novell.com>
cc: IETF ldapbis WG <ietf-ldapbis@OpenLDAP.org>
Subject: RE: Attribute Name Length Bounds
In-Reply-To: <sf15f9b3.079@prv-mail20.provo.novell.com>
Message-ID: <Pine.LNX.4.44.0307171001070.1073-100000@localhost.localdomain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>


On Wed, 16 Jul 2003, Jim Sermersheim wrote:

> At this point it seems clear that it would be a good thing to make a
> clarification to [Protocols]. That clarification would state something
> like: all octets of a ber-encoded LDAP PDU are significant. No octets
> may be ignored unless they are part of extended elements that are
> themselves ignored.

It seems to me that the point is to give implementors advice about what to
do when any protocol elements exceed implementation-specific length
boundaries.  I agree with Ron that the significance of "all octets are
significant" isn't necessarily clear ...

I was going to recommend that this advice be added as another bullet in
the "Implementation Guidelines" section (since it applies to both server
and client, maybe adding a "general" 6.x section would be the clearest).

But then I read again these paragraphs from section 4.1.1 of protocol-16:

   If the server receives a PDU from the client in which the LDAPMessage
   SEQUENCE tag cannot be recognized, the messageID cannot be parsed,
   the tag of the protocolOp is not recognized as a request, or the
   encoding structures or lengths of data fields are found to be
   incorrect, then the server MAY return the Notice of Disconnection
   described in section 4.4.1, with the resultCode set to protocolError,
   and MUST immediately close the connection.

   In other cases where the client or server cannot parse a PDU, it
   SHOULD abruptly close the connection where further communication
   (including providing notice) would be pernicious. Otherwise, server
   implementations MUST return an appropriate response to the request,
   with the resultCode set to protocolError.

I would think that not being able to fit a PDU element into your
implementation's data slots would be an instance of "cannot parse".  If
so, then this case is already covered by the above text (where we should
still probably add something like: "including not being able to store a
PDU element in implementation-specific data structure" to the above).
Whether the above text is actually correct may be another question ...

If PDU-element-too-big-to-fit is not an instance of "cannot parse", then I
think adding advice in section 6 would be the right thing to do.

 - RL "Bob"




From owner-ietf-ldapbis@OpenLDAP.org  Thu Jul 17 15:55:05 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20469
	for <ldapbis-archive@lists.ietf.org>; Thu, 17 Jul 2003 15:55:01 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6HJkokl079464;
	Thu, 17 Jul 2003 19:53:48 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h6HJhJuN079244;
	Thu, 17 Jul 2003 19:43:19 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 17 Jul 2003 19:43:19 +0000
Received: from prv-mail20.provo.novell.com (prv-mail20.provo.novell.com [137.65.81.122])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6HJhIkb079225
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 17 Jul 2003 19:43:18 GMT
	(envelope-from jimse@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Thu, 17 Jul 2003 13:42:57 -0600
Message-Id: <sf16a7e1.057@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.1 
Date: Thu, 17 Jul 2003 13:40:49 -0600
From: "Jim Sermersheim" <jimse@novell.com>
To: <ietf-ldapbis@OpenLDAP.org>
Subject: RE: Attribute Name Length Bounds
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__Part6B354FD1.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.

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

I also see that we could just add "or exceed server limits" to the end
of the phrase "or the encoding structures or lengths of data fields are
found to be incorrect" in the first paragraph. But I'm not sure...
 
This section talks about data that is either malformed or cannot be/is
not  recognized, so it seems like a good fit. It splits the problems
into two classes (those that cause the connection to terminate, and
those that simply return protocolError).
 
Adding the change above causes a connection termination. The change Bob
suggests allows one to differentiate between something that looks like
an attack (say some size is 20gb), and something that simply exceeds a
small limit, and act accordingly.
 
Which seems more correct to others (and do both seem incorrect to
anyone)?
 
While I think this is a good fix to add, does it fix the problem? After
reading http://www.openldap.org/lists/ietf-ldapbis/200306/msg00065.html
the answer is "Yes". Then when I read
http://www.openldap.org/lists/ietf-ldapbis/200306/msg00071.html, it
seems to say "Not really". 
Does requiring the server to return an error when it can't handle a
too-big attribute name solve this particular problem? If not--and we
still want to talk about mandatory minimums for schema names, we need to
do it in the context of [Models].
 
As a side note, I also wonder if these two paragraphs belong in Section
4 rather than 4.1.1.
 
Jim

>>> "RL 'Bob' Morgan" <rlmorgan@washington.edu> 7/17/03 11:15:53 AM
>>>

On Wed, 16 Jul 2003, Jim Sermersheim wrote:

> At this point it seems clear that it would be a good thing to make a
> clarification to [Protocols]. That clarification would state
something
> like: all octets of a ber-encoded LDAP PDU are significant. No
octets
> may be ignored unless they are part of extended elements that are
> themselves ignored.

It seems to me that the point is to give implementors advice about what
to
do when any protocol elements exceed implementation-specific length
boundaries. I agree with Ron that the significance of "all octets are
significant" isn't necessarily clear ...

I was going to recommend that this advice be added as another bullet
in
the "Implementation Guidelines" section (since it applies to both
server
and client, maybe adding a "general" 6.x section would be the
clearest).

But then I read again these paragraphs from section 4.1.1 of
protocol-16:

If the server receives a PDU from the client in which the LDAPMessage
SEQUENCE tag cannot be recognized, the messageID cannot be parsed,
the tag of the protocolOp is not recognized as a request, or the
encoding structures or lengths of data fields are found to be
incorrect, then the server MAY return the Notice of Disconnection
described in section 4.4.1, with the resultCode set to protocolError,
and MUST immediately close the connection.

In other cases where the client or server cannot parse a PDU, it
SHOULD abruptly close the connection where further communication
(including providing notice) would be pernicious. Otherwise, server
implementations MUST return an appropriate response to the request,
with the resultCode set to protocolError.

I would think that not being able to fit a PDU element into your
implementation's data slots would be an instance of "cannot parse". If
so, then this case is already covered by the above text (where we
should
still probably add something like: "including not being able to store
a
PDU element in implementation-specific data structure" to the above).
Whether the above text is actually correct may be another question ...

If PDU-element-too-big-to-fit is not an instance of "cannot parse",
then I
think adding advice in section 6 would be the right thing to do.

- RL "Bob"




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

<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 5.50.4926.2500" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Microsoft Sans Serif">
<DIV>I also see that we could just add "or exceed server limits" to the end of the phrase "or the encoding structures or lengths of data fields are found to be incorrect" in the first paragraph. But I'm not sure...</DIV>
<DIV>&nbsp;</DIV>
<DIV>This section talks about data that is either malformed or cannot be/is not&nbsp;&nbsp;recognized, so it seems like a good fit. It&nbsp;splits the problems into two&nbsp;classes (those that cause the connection to terminate, and those that simply return protocolError).</DIV>
<DIV>&nbsp;</DIV>
<DIV>Adding the change above causes a connection termination. The change Bob suggests allows one to differentiate between something that looks like an attack (say some size is 20gb), and something that simply exceeds a small limit, and act accordingly.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Which seems more correct to others (and do both seem incorrect to anyone)?</DIV>
<DIV>&nbsp;</DIV>
<DIV>While I think this is a good fix to add, does&nbsp;it fix the problem? After reading <A href="http://www.openldap.org/lists/ietf-ldapbis/200306/msg00065.html">http://www.openldap.org/lists/ietf-ldapbis/200306/msg00065.html</A>&nbsp;the answer is "Yes". Then when I read <A href="http://www.openldap.org/lists/ietf-ldapbis/200306/msg00071.html">http://www.openldap.org/lists/ietf-ldapbis/200306/msg00071.html</A>, it seems to say "Not really". </DIV>
<DIV>Does requiring&nbsp;the server to return an error when it can't handle a too-big attribute name solve this particular problem? If not--and we still want to talk about mandatory minimums for schema names, we need to do it in the context of [Models].</DIV>
<DIV>&nbsp;</DIV>
<DIV>As a side note, I also wonder if these two paragraphs&nbsp;belong in Section 4 rather than 4.1.1.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Jim</DIV>
<DIV><BR>&gt;&gt;&gt; "RL 'Bob' Morgan" &lt;rlmorgan@washington.edu&gt; 7/17/03 11:15:53 AM &gt;&gt;&gt;<BR><BR>On Wed, 16 Jul 2003, Jim Sermersheim wrote:<BR><BR>&gt; At this point it seems clear that it would be a good thing to make a<BR>&gt; clarification to [Protocols]. That clarification would state something<BR>&gt; like: all octets of a ber-encoded LDAP PDU are significant. No octets<BR>&gt; may be ignored unless they are part of extended elements that are<BR>&gt; themselves ignored.<BR><BR>It seems to me that the point is to give implementors advice about what to<BR>do when any protocol elements exceed implementation-specific length<BR>boundaries. I agree with Ron that the significance of "all octets are<BR>significant" isn't necessarily clear ...<BR><BR>I was going to recommend that this advice be added as another bullet in<BR>the "Implementation Guidelines" section (since it applies to both server<BR>and client, maybe adding a "general" 6.x section would be the cle!
 arest).<BR><BR>But then I read again these paragraphs from section 4.1.1 of protocol-16:<BR><BR>If the server receives a PDU from the client in which the LDAPMessage<BR>SEQUENCE tag cannot be recognized, the messageID cannot be parsed,<BR>the tag of the protocolOp is not recognized as a request, or the<BR>encoding structures or lengths of data fields are found to be<BR>incorrect, then the server MAY return the Notice of Disconnection<BR>described in section 4.4.1, with the resultCode set to protocolError,<BR>and MUST immediately close the connection.<BR><BR>In other cases where the client or server cannot parse a PDU, it<BR>SHOULD abruptly close the connection where further communication<BR>(including providing notice) would be pernicious. Otherwise, server<BR>implementations MUST return an appropriate response to the request,<BR>with the resultCode set to protocolError.<BR><BR>I would think that not being able to fit a PDU element into your<BR>implementation's data slots w!
 ould be an instance of "cannot parse". If<BR>so, then this cas!
 e is alr

eady covered by the above text (where we should<BR>still probably add something like: "including not being able to store a<BR>PDU element in implementation-specific data structure" to the above).<BR>Whether the above text is actually correct may be another question ...<BR><BR>If PDU-element-too-big-to-fit is not an instance of "cannot parse", then I<BR>think adding advice in section 6 would be the right thing to do.<BR><BR>- RL "Bob"<BR><BR><BR></DIV></BODY></HTML>
--=__Part6B354FD1.0__=--


From owner-ietf-ldapbis@OpenLDAP.org  Thu Jul 17 16:30:01 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21484
	for <ldapbis-archive@lists.ietf.org>; Thu, 17 Jul 2003 16:30:00 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6HKAomT081016;
	Thu, 17 Jul 2003 20:28:58 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h6HK8V16080870;
	Thu, 17 Jul 2003 20:08:31 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 17 Jul 2003 20:08:31 +0000
Received: from tconl91223.tconl.com (tconl91223.tconl.com [204.26.91.223])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6HK8Tkb080848
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 17 Jul 2003 20:08:29 GMT
	(envelope-from jayhawk@tconl91223.tconl.com)
Received: (from jayhawk@localhost)
	by tconl91223.tconl.com (8.11.6/8.11.0) id h6HK83H01766;
	Thu, 17 Jul 2003 15:08:03 -0500
Date: Thu, 17 Jul 2003 15:08:03 -0500
From: Ryan Moats <rmoats@lemurnetworks.net>
To: Jim Sermersheim <jimse@novell.com>
Cc: ietf-ldapbis@OpenLDAP.org
Subject: Re: Attribute Name Length Bounds
Message-ID: <20030717150803.B1457@privateer.local.windrose.omaha.ne.us>
Reply-To: rmoats@lemurnetworks.net
References: <sf16a7e1.057@prv-mail20.provo.novell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <sf16a7e1.057@prv-mail20.provo.novell.com>; from jimse@novell.com on Thu, Jul 17, 2003 at 01:40:49PM -0600
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

On Thu, Jul 17, 2003 at 01:40:49PM -0600, Jim Sermersheim wrote:
| I also see that we could just add "or exceed server limits" to the end
| of the phrase "or the encoding structures or lengths of data fields are
| found to be incorrect" in the first paragraph. But I'm not sure...
|  
| This section talks about data that is either malformed or cannot be/is
| not  recognized, so it seems like a good fit. It splits the problems
| into two classes (those that cause the connection to terminate, and
| those that simply return protocolError).
|  
| Adding the change above causes a connection termination. The change Bob
| suggests allows one to differentiate between something that looks like
| an attack (say some size is 20gb), and something that simply exceeds a
| small limit, and act accordingly.
|  
| Which seems more correct to others (and do both seem incorrect to
| anyone)?
|  
| While I think this is a good fix to add, does it fix the problem? After
| reading http://www.openldap.org/lists/ietf-ldapbis/200306/msg00065.html
| the answer is "Yes". Then when I read
| http://www.openldap.org/lists/ietf-ldapbis/200306/msg00071.html, it
| seems to say "Not really". 
| Does requiring the server to return an error when it can't handle a
| too-big attribute name solve this particular problem? If not--and we
| still want to talk about mandatory minimums for schema names, we need to
| do it in the context of [Models].

Speaking as a schema designer, this doesn't help me because it doesn't
address the fundamental issue of ensuring that the proposed schema works
on an implementation.  I don't see how a schema designer can have any
confidence that a schema will work unless there is a mandatory minimum.

Ryan Moats



From owner-ietf-ldapbis@OpenLDAP.org  Tue Jul 22 19:57:38 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01246
	for <ldapbis-archive@lists.ietf.org>; Tue, 22 Jul 2003 19:57:35 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6MNsU31025935;
	Tue, 22 Jul 2003 23:55:44 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h6MNqlkx025836;
	Tue, 22 Jul 2003 23:52:47 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 22 Jul 2003 23:52:47 +0000
Received: from prv-mail20.provo.novell.com (prv-mail20.provo.novell.com [137.65.81.122])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6MNqk2v025820
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 22 Jul 2003 23:52:46 GMT
	(envelope-from jimse@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Tue, 22 Jul 2003 17:52:26 -0600
Message-Id: <sf1d79da.045@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.1 
Date: Tue, 22 Jul 2003 17:50:04 -0600
From: "Jim Sermersheim" <jimse@novell.com>
To: <ietf-ldapbis@OpenLDAP.org>
Subject: Models: precluded attributes
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

In section 4.1.6 (Dit Content Rules), the following paragraph is hard to
parse:

  The list of precluded attributes cannot include any attribute listed
  as mandatory in rule, the structural object class, or any of the
  allowed auxiliary object classes.

In particular, I'm not sure that it states that the NOT list cannot
contain an attribute in the MUST list of the DIT Content Rule itself (it
only talks about the structural object class and all the aux classes).

Jim


From owner-ietf-ldapbis@OpenLDAP.org  Tue Jul 22 20:07:33 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA01450
	for <ldapbis-archive@lists.ietf.org>; Tue, 22 Jul 2003 20:07:32 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6N06U31026531;
	Wed, 23 Jul 2003 00:06:32 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h6N00Wjs026158;
	Wed, 23 Jul 2003 00:00:32 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 23 Jul 2003 00:00:32 +0000
Received: from prv-mail20.provo.novell.com (prv-mail20.provo.novell.com [137.65.81.122])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6N00V2v026144
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 23 Jul 2003 00:00:31 GMT
	(envelope-from jimse@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Tue, 22 Jul 2003 18:00:11 -0600
Message-Id: <sf1d7bab.017@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.1 
Date: Tue, 22 Jul 2003 17:57:25 -0600
From: "Jim Sermersheim" <jimse@novell.com>
To: <ietf-ldapbis@OpenLDAP.org>
Subject: Models: updating DIT Content Rules
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__PartF0AEDF75.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.

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

If a structural object class exists without a DIT content rule, and
entries of that structural object class exist in the DIT, what are the
rules for later adding a DIT content rule for that structural object
class? The same issue exists for updates to existing DIT content rules.
 
Obviously, a DIT content rule which would invalidate existing entries
could/should not be added. This could happen due to the addition of MUST
or NOT attributes or removing AUX classes, or adding AUX classes which
have MUSTs that are already in the NOT list.. Should there be language
along the lines of "A DIT content rule SHALL NOT be added or updated in
a way that would invalidate existing entries"?
 
Jim

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

<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 5.50.4926.2500" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Microsoft Sans Serif">
<DIV>If a structural object class exists without a DIT content rule, and entries of that structural object class exist in the DIT, what are the rules for later adding a DIT content rule for that structural object class? The same issue exists for updates to existing DIT content rules.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Obviously,&nbsp;a DIT content rule which would invalidate existing entries could/should not be added. This could happen due to the addition of MUST or NOT attributes or removing AUX classes, or adding AUX classes which have MUSTs that are already in the NOT list.. Should there be language along the lines of "A DIT content rule SHALL NOT be added or updated in a way that would invalidate existing entries"?</DIV>
<DIV>&nbsp;</DIV>
<DIV>Jim</DIV></BODY></HTML>
--=__PartF0AEDF75.0__=--


From owner-ietf-ldapbis@OpenLDAP.org  Wed Jul 23 04:33:50 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA05925
	for <ldapbis-archive@lists.ietf.org>; Wed, 23 Jul 2003 04:33:50 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6N8UX31042515;
	Wed, 23 Jul 2003 08:31:25 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h6N8SSs9042433;
	Wed, 23 Jul 2003 08:28:28 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 23 Jul 2003 08:28:28 +0000
Received: from prv-mail25.provo.novell.com (prv-mail25.provo.novell.com [137.65.81.121])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6N8SR2v042417
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 23 Jul 2003 08:28:27 GMT
	(envelope-from gvithalprasad@novell.com)
Received: from INET-PRV1-MTA by prv-mail25.provo.novell.com
	with Novell_GroupWise; Wed, 23 Jul 2003 02:28:06 -0600
Message-Id: <sf1df2b6.063@prv-mail25.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.1 
Date: Wed, 23 Jul 2003 02:27:47 -0600
From: "Vithalprasad Gaitonde" <gvithalprasad@novell.com>
To: <ietf-ldapbis@OpenLDAP.org>
Subject: Fwd: Re: result code for a deleted identity on a connection
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="=__Part1D433113.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.

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

Roger/Jim,
Sometime back we discussed this on the list.
Probably we should make the necessary edits for this in AuthMeth
(clarification of server behaviour when the bind identity of an
established connection is deleted) and Protocol ( edit of when
strongAuthRequired can be sent).

-Prasad
--=__Part1D433113.0__=
Content-Type: message/rfc822

Return-path: <owner-ietf-ldapbis@OpenLDAP.org>
Received: from prv1-mx.provo.novell.com [192.233.80.9]
	by prv-mail10.provo.novell.com; Fri, 09 May 2003 18:35:48 -0600
Received: from boole.openldap.org [204.152.186.50]
	by prv1-mx.provo.novell.com; Fri, 09 May 2003 18:35:16 -0600
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4A0PuEv052042;
	Sat, 10 May 2003 00:33:17 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h4A0OVw7051990;
	Sat, 10 May 2003 00:24:31 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Sat, 10 May 2003 00:24:31 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h4A0OUEh051978
	for <ietf-ldapbis@OpenLDAP.org>; Sat, 10 May 2003 00:24:30 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from nomad.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.8/8.12.8) with ESMTP id h4A0ORc6046980;
	Sat, 10 May 2003 00:24:28 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030509171928.023ab700@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Fri, 09 May 2003 17:21:55 -0700
To: "Vithalprasad Gaitonde" <gvithalprasad@novell.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: result code for a deleted identity on a connection
Cc: <ietf-ldapbis@OpenLDAP.org>, "Vijay KN" <KNVIJAY@novell.com>,
   "Savitha R" <RSAVITHA@novell.com>
In-Reply-To: <seb5a874.019@prv-mail25.provo.novell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

At 10:55 PM 5/4/2003, Vithalprasad Gaitonde wrote:
>"But I'm thinking RFC 2251, 4.4.1 should be clarified as well:
>        - strongAuthRequired: The server has detected that an
>establish
>          security association between the client and server has
>          unexpectedly failed or been compromised, or that the
>          server now requires the client to authenticate using a
>          strong(er) mechanism."
>But what does strong(er) imply in the case which we are talking
>about...

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

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

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

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


--=__Part1D433113.0__=--


From owner-ietf-ldapbis@OpenLDAP.org  Wed Jul 23 12:38:58 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19162
	for <ldapbis-archive@lists.ietf.org>; Wed, 23 Jul 2003 12:38:58 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6NGaZ31067755;
	Wed, 23 Jul 2003 16:37:47 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h6NGYd8p067488;
	Wed, 23 Jul 2003 16:34:39 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Wed, 23 Jul 2003 16:34:39 +0000
Received: from prv-mail20.provo.novell.com (prv-mail20.provo.novell.com [137.65.81.122])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6NGYc2v067461
	for <ietf-ldapbis@OpenLDAP.org>; Wed, 23 Jul 2003 16:34:38 GMT
	(envelope-from jimse@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Wed, 23 Jul 2003 10:34:17 -0600
Message-Id: <sf1e64a9.010@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.1 
Date: Wed, 23 Jul 2003 10:32:02 -0600
From: "Jim Sermersheim" <jimse@novell.com>
To: <ietf-ldapbis@OpenLDAP.org>
Subject: Fwd: Re: result code for a deleted identity on a connection
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Prasad,
 
Currently Protocol says:
(in Notice of Disconnection)
- strongAuthRequired: The server has detected that an establish
security association between the client and server has unexpectedly
failed or been compromised, or that the server now requires the client
to authenticate using a strong(er) mechanism.
 
(in A.2)
strongAuthRequired (8)
Except when returned in a Notice of Disconnect (see section 4.4.1),
this indicates that the server requires the client to authentication
using a strong(er) mechanism.
 
Do you think more needs to be added/changed (aside from the two typos)?
There is nothing that restricts which operation responses
strongAuthRequired is returned in.
 
I prefer not to mention specific scenarios (like the one mentioned
below), because I don't want to restrict other errors from being
returned. 
If the scenario below happens, a server should be free to:
a) revert the authN/authZ state to anonymous and allow operations to
succeed or fail (with insufficientAccessRights) as they normally would.
b) revert the auth state to unknown and fail all non-authN requests
c) send a notice of disconnect
d) do a or b and also send some unsolicited notification which notifies
that the connection state has changed
e) not even be aware that a change has happened and proceed as if the
identity still exists.
f) others that I haven't thought of.
 
Jim

>>> "Vithalprasad Gaitonde" <gvithalprasad@novell.com> 7/23/03 2:27:47
AM >>>
Roger/Jim,
Sometime back we discussed this on the list.
Probably we should make the necessary edits for this in AuthMeth
(clarification of server behaviour when the bind identity of an
established connection is deleted) and Protocol ( edit of when
strongAuthRequired can be sent).

-Prasad



From owner-ietf-ldapbis@OpenLDAP.org  Mon Jul 28 08:51:53 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00036
	for <ldapbis-archive@lists.ietf.org>; Mon, 28 Jul 2003 08:51:49 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6SCnF31088656;
	Mon, 28 Jul 2003 12:50:26 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h6SCn4DL088644;
	Mon, 28 Jul 2003 12:49:04 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Mon, 28 Jul 2003 12:49:04 +0000
Received: from prv-mail25.provo.novell.com (prv-mail25.provo.novell.com [137.65.81.121])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6SCn22v088634
	for <ietf-ldapbis@OpenLDAP.org>; Mon, 28 Jul 2003 12:49:02 GMT
	(envelope-from gvithalprasad@novell.com)
Received: from INET-PRV1-MTA by prv-mail25.provo.novell.com
	with Novell_GroupWise; Mon, 28 Jul 2003 06:48:42 -0600
Message-Id: <sf24c74a.013@prv-mail25.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.1 
Date: Mon, 28 Jul 2003 06:48:23 -0600
From: "Vithalprasad Gaitonde" <gvithalprasad@novell.com>
To: <ietf-ldapbis@OpenLDAP.org>
Subject: Fwd: Re: result code for a deleted identity on a connection
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Jim,
Two items:
1. Does the case need a representation in the state transition diagram
that Roger has been working on in his authmethd draft. (This question
should probably go to Roger).
2. You mention "e) not even be aware that a change has happened and
proceed as if the
identity still exists."  Leaving this behaviour as option to the
server, could have some serious security implications.  When I read this
and see the IESG note regrading security implications in 2251 especially
with respect to update operations, I wonder if progressing the draft
would have problems because of these security implications.

Prasad

>>> "Jim Sermersheim" <jimse@novell.com> 7/23/2003 10:02:02 PM >>>
Prasad,
 
Currently Protocol says:
(in Notice of Disconnection)
- strongAuthRequired: The server has detected that an establish
security association between the client and server has unexpectedly
failed or been compromised, or that the server now requires the client
to authenticate using a strong(er) mechanism.
 
(in A.2)
strongAuthRequired (8)
Except when returned in a Notice of Disconnect (see section 4.4.1),
this indicates that the server requires the client to authentication
using a strong(er) mechanism.
 
Do you think more needs to be added/changed (aside from the two
typos)?
There is nothing that restricts which operation responses
strongAuthRequired is returned in.
 
I prefer not to mention specific scenarios (like the one mentioned
below), because I don't want to restrict other errors from being
returned. 
If the scenario below happens, a server should be free to:
a) revert the authN/authZ state to anonymous and allow operations to
succeed or fail (with insufficientAccessRights) as they normally
would.
b) revert the auth state to unknown and fail all non-authN requests
c) send a notice of disconnect
d) do a or b and also send some unsolicited notification which
notifies
that the connection state has changed
e) not even be aware that a change has happened and proceed as if the
identity still exists.
f) others that I haven't thought of.
 
Jim

>>> "Vithalprasad Gaitonde" <gvithalprasad@novell.com> 7/23/03 2:27:47
AM >>>
Roger/Jim,
Sometime back we discussed this on the list.
Probably we should make the necessary edits for this in AuthMeth
(clarification of server behaviour when the bind identity of an
established connection is deleted) and Protocol ( edit of when
strongAuthRequired can be sent).

-Prasad



From owner-ietf-ldapbis@OpenLDAP.org  Tue Jul 29 02:04:31 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA05937
	for <ldapbis-archive@lists.ietf.org>; Tue, 29 Jul 2003 02:04:30 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6T61K31030883;
	Tue, 29 Jul 2003 06:01:54 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h6T5w8Wf030685;
	Tue, 29 Jul 2003 05:58:08 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 29 Jul 2003 05:58:08 +0000
Received: from prv-mail20.provo.novell.com (prv-mail20.provo.novell.com [137.65.81.122])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6T5w62v030672
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 29 Jul 2003 05:58:06 GMT
	(envelope-from jimse@novell.com)
Received: from INET-PRV-MTA by prv-mail20.provo.novell.com
	with Novell_GroupWise; Mon, 28 Jul 2003 23:57:42 -0600
Message-Id: <sf25b876.043@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.1 
Date: Mon, 28 Jul 2003 23:55:23 -0600
From: "Jim Sermersheim" <jimse@novell.com>
To: <ietf-ldapbis@OpenLDAP.org>
Subject: Fwd: Re: result code for a deleted identity on a connection
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__Part2678325B.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.

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

Regarding #2: Are you proposing that we add specific instructions for
this scenario? I'm not sure that we can find two interoperable
implementations that would adhere to any new recommendation. Aside from
that (because that alone shouldn't interfere with us solving a serious
security implication), is this a serious security implication? 
 
The general scenario is that a bind succeeded, and later, the identity
(or its credentials) become invalid (perhaps the identity is represented
as a DN and that object is deleted, or perhaps a ticket expired, or a
cert expired, or any number of other incidents may have happened to the
identity or its credentials such that if that bind were to be re-issued
again, it would fail--yet the connection (on which the bind succeeded)
is still open, and then some subsequent request is made. Is this
accurate, or are you only trying to address the specific issue of a
simple bind, followed by a deletion of the bind DN?
 
If the specific problem is being addressed, we also need to consider
what happens when:
- the password is changed
- the DN is moved or renamed
- the DN is not local and authentication was chained
- other policy has caused the "account" to be "locked"
- etc.
 
If the general problem is being addressed, then there are a number of
other considerations to be made.
 
In either case, it seems to be opening a level of complexity never
before described in the TS, and prescribing implementation behavior
beyond a level in which implementors can handle. I note that there are
similar analogies that are unspecified. For example, is a server forced
to calculate authorization for each operation, or can it cache certain
types of authZ data when the client performs a bind? If the server is
allowed to cache, then changes to authZ data (ACIs) may go unnoticed,
thus creating a security breach. To date, this level of detail has been
left to implementations. 
 
If we don't allow option e below, then we are saying that we will
mandate behavior--that we will force servers to know when an identity
(or possibly any of the other items above) has changed. Are we willing
to begin mandating this level of behavior?
 
Jim


>>> "Vithalprasad Gaitonde" <gvithalprasad@novell.com> 7/28/03 6:48:23
AM >>>
Jim,
Two items:
1. Does the case need a representation in the state transition diagram
that Roger has been working on in his authmethd draft. (This question
should probably go to Roger).
2. You mention "e) not even be aware that a change has happened and
proceed as if the
identity still exists." Leaving this behaviour as option to the
server, could have some serious security implications. When I read
this
and see the IESG note regrading security implications in 2251
especially
with respect to update operations, I wonder if progressing the draft
would have problems because of these security implications.

Prasad

>>> "Jim Sermersheim" < jimse@novell.com > 7/23/2003 10:02:02 PM >>>
Prasad,

Currently Protocol says:
(in Notice of Disconnection)
- strongAuthRequired: The server has detected that an establish
security association between the client and server has unexpectedly
failed or been compromised, or that the server now requires the client
to authenticate using a strong(er) mechanism.

(in A.2)
strongAuthRequired (8)
Except when returned in a Notice of Disconnect (see section 4.4.1),
this indicates that the server requires the client to authentication
using a strong(er) mechanism.

Do you think more needs to be added/changed (aside from the two
typos)?
There is nothing that restricts which operation responses
strongAuthRequired is returned in.

I prefer not to mention specific scenarios (like the one mentioned
below), because I don't want to restrict other errors from being
returned. 
If the scenario below happens, a server should be free to:
a) revert the authN/authZ state to anonymous and allow operations to
succeed or fail (with insufficientAccessRights) as they normally
would.
b) revert the auth state to unknown and fail all non-authN requests
c) send a notice of disconnect
d) do a or b and also send some unsolicited notification which
notifies
that the connection state has changed
e) not even be aware that a change has happened and proceed as if the
identity still exists.
f) others that I haven't thought of.

Jim

>>> "Vithalprasad Gaitonde" < gvithalprasad@novell.com > 7/23/03
2:27:47
AM >>>
Roger/Jim,
Sometime back we discussed this on the list.
Probably we should make the necessary edits for this in AuthMeth
(clarification of server behaviour when the bind identity of an
established connection is deleted) and Protocol ( edit of when
strongAuthRequired can be sent).

-Prasad



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

<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 5.50.4926.2500" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Microsoft Sans Serif">
<DIV>Regarding #2: Are you proposing that we add specific instructions for this scenario? I'm not sure that we can find two interoperable implementations that would adhere to any new recommendation. Aside from that (because that alone shouldn't interfere with us solving a serious security implication), is this a serious security implication? </DIV>
<DIV>&nbsp;</DIV>
<DIV>The general scenario is that a bind succeeded, and later, the identity (or its credentials) become invalid (perhaps the identity is represented as a DN and that object is deleted, or perhaps a ticket expired, or a cert expired, or any number of other incidents may have happened to the identity or its credentials such that if that bind were to be re-issued again, it would fail--yet the connection (on which the bind succeeded) is still open, and then some subsequent request is made. Is this accurate, or are you only trying to address the specific issue of a simple bind, followed by a deletion of the bind DN?</DIV>
<DIV>&nbsp;</DIV>
<DIV>If the specific problem is being addressed, we also need to consider what happens when:</DIV>
<DIV>-&nbsp;the password is changed</DIV>
<DIV>- the DN is moved or renamed</DIV>
<DIV>- the DN is not local and authentication was chained</DIV>
<DIV>- other policy has caused the "account" to be "locked"</DIV>
<DIV>- etc.</DIV>
<DIV>&nbsp;</DIV>
<DIV>If the general problem is being addressed, then there are a number of other considerations to be made.</DIV>
<DIV>&nbsp;</DIV>
<DIV>In either case, it seems to be opening a level of complexity never before described in the TS, and prescribing implementation behavior beyond a level in which implementors can handle. I note that there are similar analogies that are unspecified. For example, is a server forced to calculate authorization for each operation, or can it cache certain types of authZ data when the&nbsp;client performs a bind? If the server is allowed to cache, then changes to authZ data (ACIs) may go unnoticed, thus creating a security breach. To date, this level of detail has been left to implementations. </DIV>
<DIV>&nbsp;</DIV>
<DIV>If we don't allow option e below, then we are saying that we will mandate behavior--that we will force servers to know when an identity (or possibly any of the other items above) has changed. Are we willing to begin mandating this level of behavior?</DIV>
<DIV>&nbsp;</DIV>
<DIV>Jim</DIV>
<DIV><BR><BR>&gt;&gt;&gt; "Vithalprasad Gaitonde" &lt;gvithalprasad@novell.com&gt; 7/28/03 6:48:23 AM &gt;&gt;&gt;<BR>Jim,<BR>Two items:<BR>1. Does the case need a representation in the state transition diagram<BR>that Roger has been working on in his authmethd draft. (This question<BR>should probably go to Roger).<BR>2. You mention "e) not even be aware that a change has happened and<BR>proceed as if the<BR>identity still exists." Leaving this behaviour as option to the<BR>server, could have some serious security implications. When I read this<BR>and see the IESG note regrading security implications in 2251 especially<BR>with respect to update operations, I wonder if progressing the draft<BR>would have problems because of these security implications.<BR><BR>Prasad<BR><BR>&gt;&gt;&gt; "Jim Sermersheim" &lt;<U> <A href="mailto:jimse@novell.com">jimse@novell.com</A></U> &gt; 7/23/2003 10:02:02 PM &gt;&gt;&gt;<BR>Prasad,<BR><BR>Currently Protocol says:<BR>(in Notice of Disconne!
 ction)<BR>- strongAuthRequired: The server has detected that an establish<BR>security association between the client and server has unexpectedly<BR>failed or been compromised, or that the server now requires the client<BR>to authenticate using a strong(er) mechanism.<BR><BR>(in A.2)<BR>strongAuthRequired (8)<BR>Except when returned in a Notice of Disconnect (see section 4.4.1),<BR>this indicates that the server requires the client to authentication<BR>using a strong(er) mechanism.<BR><BR>Do you think more needs to be added/changed (aside from the two<BR>typos)?<BR>There is nothing that restricts which operation responses<BR>strongAuthRequired is returned in.<BR><BR>I prefer not to mention specific scenarios (like the one mentioned<BR>below), because I don't want to restrict other errors from being<BR>returned. <BR>If the scenario below happens, a server should be free to:<BR>a) revert the authN/authZ state to anonymous and allow operations to<BR>succeed or fail (with insuff!
 icientAccessRights) as they normally<BR>would.<BR>b) revert th!
 e auth s

tate to unknown and fail all non-authN requests<BR>c) send a notice of disconnect<BR>d) do a or b and also send some unsolicited notification which<BR>notifies<BR>that the connection state has changed<BR>e) not even be aware that a change has happened and proceed as if the<BR>identity still exists.<BR>f) others that I haven't thought of.<BR><BR>Jim<BR><BR>&gt;&gt;&gt; "Vithalprasad Gaitonde" &lt;<U> <A href="mailto:gvithalprasad@novell.com">gvithalprasad@novell.com</A></U> &gt; 7/23/03 2:27:47<BR>AM &gt;&gt;&gt;<BR>Roger/Jim,<BR>Sometime back we discussed this on the list.<BR>Probably we should make the necessary edits for this in AuthMeth<BR>(clarification of server behaviour when the bind identity of an<BR>established connection is deleted) and Protocol ( edit of when<BR>strongAuthRequired can be sent).<BR><BR>-Prasad<BR><BR></DIV></BODY></HTML>
--=__Part2678325B.0__=--


From owner-ietf-ldapbis@OpenLDAP.org  Tue Jul 29 03:27:28 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA14714
	for <ldapbis-archive@lists.ietf.org>; Tue, 29 Jul 2003 03:27:27 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6T7PL31034363;
	Tue, 29 Jul 2003 07:25:36 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h6T7LA6o034265;
	Tue, 29 Jul 2003 07:21:10 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 29 Jul 2003 07:21:10 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6T7L82v034255
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 29 Jul 2003 07:21:08 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from nomad.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.8/8.12.8) with ESMTP id h6T7L2c6043634;
	Tue, 29 Jul 2003 07:21:03 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030729090709.01b8ef10@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Tue, 29 Jul 2003 09:17:40 +0200
To: "Jim Sermersheim" <jimse@novell.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: Fwd: Re: result code for a deleted identity on a connection
Cc: <ietf-ldapbis@OpenLDAP.org>
In-Reply-To: <sf25b876.043@prv-mail20.provo.novell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

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


At 07:55 AM 7/29/2003, Jim Sermersheim wrote:
>Regarding #2: Are you proposing that we add specific instructions for this scenario? I'm not sure that we can find two interoperable implementations that would adhere to any new recommendation. Aside from that (because that alone shouldn't interfere with us solving a serious security implication), is this a serious security implication? 
> 
>The general scenario is that a bind succeeded, and later, the identity (or its credentials) become invalid (perhaps the identity is represented as a DN and that object is deleted, or perhaps a ticket expired, or a cert expired, or any number of other incidents may have happened to the identity or its credentials such that if that bind were to be re-issued again, it would fail--yet the connection (on which the bind succeeded) is still open, and then some subsequent request is made. Is this accurate, or are you only trying to address the specific issue of a simple bind, followed by a deletion of the bind DN?
> 
>If the specific problem is being addressed, we also need to consider what happens when:
>- the password is changed
>- the DN is moved or renamed
>- the DN is not local and authentication was chained
>- other policy has caused the "account" to be "locked"
>- etc.
> 
>If the general problem is being addressed, then there are a number of other considerations to be made.
> 
>In either case, it seems to be opening a level of complexity never before described in the TS, and prescribing implementation behavior beyond a level in which implementors can handle. I note that there are similar analogies that are unspecified. For example, is a server forced to calculate authorization for each operation, or can it cache certain types of authZ data when the client performs a bind? If the server is allowed to cache, then changes to authZ data (ACIs) may go unnoticed, thus creating a security breach. To date, this level of detail has been left to implementations. 
> 
>If we don't allow option e below, then we are saying that we will mandate behavior--that we will force servers to know when an identity (or possibly any of the other items above) has changed. Are we willing to begin mandating this level of behavior?
> 
>Jim
>
>
>>>> "Vithalprasad Gaitonde" <gvithalprasad@novell.com> 7/28/03 6:48:23 AM >>>
>Jim,
>Two items:
>1. Does the case need a representation in the state transition diagram
>that Roger has been working on in his authmethd draft. (This question
>should probably go to Roger).
>2. You mention "e) not even be aware that a change has happened and
>proceed as if the
>identity still exists." Leaving this behaviour as option to the
>server, could have some serious security implications. When I read this
>and see the IESG note regrading security implications in 2251 especially
>with respect to update operations, I wonder if progressing the draft
>would have problems because of these security implications.
>
>Prasad
>
>>>> "Jim Sermersheim" < <mailto:jimse@novell.com>jimse@novell.com > 7/23/2003 10:02:02 PM >>>
>Prasad,
>
>Currently Protocol says:
>(in Notice of Disconne! ction)
>- strongAuthRequired: The server has detected that an establish
>security association between the client and server has unexpectedly
>failed or been compromised, or that the server now requires the client
>to authenticate using a strong(er) mechanism.
>
>(in A.2)
>strongAuthRequired (8)
>Except when returned in a Notice of Disconnect (see section 4.4.1),
>this indicates that the server requires the client to authentication
>using a strong(er) mechanism.
>
>Do you think more needs to be added/changed (aside from the two
>typos)?
>There is nothing that restricts which operation responses
>strongAuthRequired is returned in.
>
>I prefer not to mention specific scenarios (like the one mentioned
>below), because I don't want to restrict other errors from being
>returned. 
>If the scenario below happens, a server should be free to:
>a) revert the authN/authZ state to anonymous and allow operations to
>succeed or fail (with insuff! icientAccessRights) as they normally
>would.
>b) revert th! e auth s tate to unknown and fail all non-authN requests
>c) send a notice of disconnect
>d) do a or b and also send some unsolicited notification which
>notifies
>that the connection state has changed
>e) not even be aware that a change has happened and proceed as if the
>identity still exists.
>f) others that I haven't thought of.
>
>Jim
>
>>>> "Vithalprasad Gaitonde" < <mailto:gvithalprasad@novell.com>gvithalprasad@novell.com > 7/23/03 2:27:47
>AM >>>
>Roger/Jim,
>Sometime back we discussed this on the list.
>Probably we should make the necessary edits for this in AuthMeth
>(clarification of server behaviour when the bind identity of an
>established connection is deleted) and Protocol ( edit of when
>strongAuthRequired can be sent).
>
>-Prasad



From owner-ietf-ldapbis@OpenLDAP.org  Tue Jul 29 03:56:43 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA15093
	for <ldapbis-archive@lists.ietf.org>; Tue, 29 Jul 2003 03:56:43 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6T7tL31036215;
	Tue, 29 Jul 2003 07:55:24 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h6T7oOA4035935;
	Tue, 29 Jul 2003 07:50:24 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 29 Jul 2003 07:50:23 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6T7oM2v035925
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 29 Jul 2003 07:50:22 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from nomad.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.8/8.12.8) with ESMTP id h6T7oAc6043878;
	Tue, 29 Jul 2003 07:50:11 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030729094242.01ce7970@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Tue, 29 Jul 2003 09:46:49 +0200
To: "Jim Sermersheim" <jimse@novell.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: Models: updating DIT Content Rules
Cc: <ietf-ldapbis@OpenLDAP.org>
In-Reply-To: <sf1d7bab.017@prv-mail20.provo.novell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

At 01:57 AM 7/23/2003, Jim Sermersheim wrote:
>If a structural object class exists without a DIT content rule, and entries of that structural object class exist in the DIT, what are the rules for later adding a DIT content rule for that structural object class? The same issue exists for updates to existing DIT content rules.
> 
>Obviously, a DIT content rule which would invalidate existing entries could/should not be added. This could happen due to the addition of MUST or NOT attributes or removing AUX classes, or adding AUX classes which have MUSTs that are already in the NOT list.. Should there be language along the lines of "A DIT content rule SHALL NOT be added or updated in a way that would invalidate existing entries"?

Given that this means:
        Server implementations MUST ensure that schema is not
        updated in a manner which invalidates entries present
        in the DIT.

No, that should not be added as a) I don't believe implementations
do that and 2) it may be extremely difficult to implement.

If I recall correctly, there is language elsewhere in the TS which
suggests that existing entries may not conform to the subschema,
but if modified, must be made conformant by that modification.

That's the general rule I believe should be followed.

Kurt 



From owner-ietf-ldapbis@OpenLDAP.org  Tue Jul 29 04:03:26 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA15291
	for <ldapbis-archive@lists.ietf.org>; Tue, 29 Jul 2003 04:03:25 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6T81L31036469;
	Tue, 29 Jul 2003 08:01:23 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h6T7x5xk036373;
	Tue, 29 Jul 2003 07:59:05 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 29 Jul 2003 07:59:05 +0000
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6T7x32v036362
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 29 Jul 2003 07:59:03 GMT
	(envelope-from Kurt@OpenLDAP.org)
Received: from nomad.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.8/8.12.8) with ESMTP id h6T7wwc6043927;
	Tue, 29 Jul 2003 07:58:59 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030729095312.01bf2790@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Tue, 29 Jul 2003 09:55:37 +0200
To: "Jim Sermersheim" <jimse@novell.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: Models: precluded attributes
Cc: <ietf-ldapbis@OpenLDAP.org>
In-Reply-To: <sf1d79da.045@prv-mail20.provo.novell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>

At 01:50 AM 7/23/2003, Jim Sermersheim wrote:
>In section 4.1.6 (Dit Content Rules), the following paragraph is hard to
>parse:
>
>  The list of precluded attributes cannot include any attribute listed
>  as mandatory in rule, the structural object class, or any of the
>  allowed auxiliary object classes.
>
>In particular, I'm not sure that it states that the NOT list cannot
>contain an attribute in the MUST list of the DIT Content Rule itself (it
>only talks about the structural object class and all the aux classes).

"in (the) rule" covers it.  I'll add the missing "the".



From owner-ietf-ldapbis@OpenLDAP.org  Tue Jul 29 04:08:29 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA15353
	for <ldapbis-archive@lists.ietf.org>; Tue, 29 Jul 2003 04:08:28 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6T87L31036673;
	Tue, 29 Jul 2003 08:07:24 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h6T872xQ036658;
	Tue, 29 Jul 2003 08:07:02 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 29 Jul 2003 08:07:02 +0000
Received: from nb2.stroeder.com (krl9-d9bb4f58.pool.mediaWays.net [217.187.79.88])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6T86x2v036620;
	Tue, 29 Jul 2003 08:06:59 GMT
	(envelope-from michael@stroeder.com)
Received: from localhost (localhost [127.0.0.1])
	by nb2.stroeder.com (Postfix) with ESMTP
	id D57E553F7B; Tue, 29 Jul 2003 10:06:36 +0200 (CEST)
Received: from stroeder.com (localhost [127.0.0.1])
	by nb2.stroeder.com (Postfix) with ESMTP
	id 1D20735976; Tue, 29 Jul 2003 10:06:36 +0200 (CEST)
Message-ID: <3F262B0B.1010808@stroeder.com>
Date: Tue, 29 Jul 2003 10:06:35 +0200
From: =?ISO-8859-1?Q?Michael_Str=F6der?= <michael@stroeder.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030626
X-Accept-Language: de-de, de, en-us, en
MIME-Version: 1.0
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Cc: Jim Sermersheim <jimse@novell.com>, ietf-ldapbis@OpenLDAP.org
Subject: Re: Fwd: Re: result code for a deleted identity on a connection
References: <5.2.0.9.0.20030729090709.01b8ef10@127.0.0.1>
In-Reply-To: <5.2.0.9.0.20030729090709.01b8ef10@127.0.0.1>
X-Enigmail-Version: 0.76.3.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by AMaViS 0.3.12pre8
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

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

+1

Ciao, Michael.



From owner-ietf-ldapbis@OpenLDAP.org  Tue Jul 29 08:30:45 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA20802
	for <ldapbis-archive@lists.ietf.org>; Tue, 29 Jul 2003 08:30:44 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6TCJN3H056628;
	Tue, 29 Jul 2003 12:26:38 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h6TCG0pH055964;
	Tue, 29 Jul 2003 12:16:00 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Tue, 29 Jul 2003 12:16:00 +0000
Received: from e3.ny.us.ibm.com (e3.ny.us.ibm.com [32.97.182.103])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6TCFx2v055885
	for <ietf-ldapbis@OpenLDAP.org>; Tue, 29 Jul 2003 12:15:59 GMT
	(envelope-from jmcmeek@us.ibm.com)
Received: from northrelay04.pok.ibm.com (northrelay04.pok.ibm.com [9.56.224.206])
	by e3.ny.us.ibm.com (8.12.9/8.12.2) with ESMTP id h6TCFJpW147784;
	Tue, 29 Jul 2003 08:15:19 -0400
Received: from d27ml001.rchland.ibm.com (d01av02.pok.ibm.com [9.56.224.216])
	by northrelay04.pok.ibm.com (8.12.9/NCO/VER6.5) with ESMTP id h6TCFHhB042730;
	Tue, 29 Jul 2003 08:15:17 -0400
Subject: Re: Fwd: Re: result code for a deleted identity on a connection
To: ietf-ldapbis@OpenLDAP.org, Jim Sermersheim <jimse@novell.com>
X-Mailer: Lotus Notes Release 5.0.12   February 13, 2003
Message-ID: <OF66A2B3FD.47BC54BD-ON86256D72.0041EDA1-86256D72.00435182@us.ibm.com>
From: John McMeeking <jmcmeek@us.ibm.com>
Date: Tue, 29 Jul 2003 07:15:14 -0500
X-MIMETrack: Serialize by Router on d27ml001/27/M/IBM(Release 6.0.2CF1|June 9, 2003) at
 07/29/2003 07:15:17 AM
MIME-Version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by boole.openldap.org id h6TCFx2v055953
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.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 also favor leaving this to the Security Considerations section.

I was trying to remember how operating systems I have worked on handle
this.  Unfortunately, the number of times I have been in a position to even
try the experiment is close to zero.  But I suspect this is handled in
different ways.  I know that at least one operating system does not allow
deleting a user while there are jobs running under that user; the
administrator must first boot the user off the system (probably disabling
the account first).  And I think this discussion was in the context of
AuthMeth which addresses authentication methods where the server may not be
(probably isn't) the authentication authority.  For a server to be aware of
events like deletion of an account in a Kerberos realm or revocation of
certificates (outside of the authentication process) is asking a lot.

John  McMeeking



                                                                                                                                          
                      Michael Ströder                                                                                                     
                      <michael@stroeder.co        To:       "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>                                        
                      m>                          cc:       Jim Sermersheim <jimse@novell.com>, ietf-ldapbis@OpenLDAP.org                 
                      Sent by:                    Subject:  Re: Fwd: Re: result code for a deleted identity on a connection               
                      owner-ietf-ldapbis@O                                                                                                
                      penLDAP.org                                                                                                         
                                                                                                                                          
                                                                                                                                          
                      07/29/2003 03:06 AM                                                                                                 
                                                                                                                                          
                                                                                                                                          




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

+1

Ciao, Michael.







From owner-ietf-ldapbis@OpenLDAP.org  Thu Jul 31 03:50:27 2003
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA15131
	for <ldapbis-archive@lists.ietf.org>; Thu, 31 Jul 2003 03:50:24 -0400 (EDT)
Received: from boole.openldap.org (smmsp@localhost [IPv6:::1])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6V7hb31088861;
	Thu, 31 Jul 2003 07:47:58 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: from localhost (majordomo@localhost)
	by boole.openldap.org (8.12.9/8.12.9/Submit) with SMTP id h6V7cNcA088706;
	Thu, 31 Jul 2003 07:38:23 GMT
	(envelope-from owner-ietf-ldapbis@OpenLDAP.org)
Received: by OpenLDAP.org (bulk_mailer v1.13); Thu, 31 Jul 2003 07:38:23 +0000
Received: from adacel.com (gunsmoke.adacel.com.au [210.11.130.7])
	by boole.openldap.org (8.12.9/8.12.9) with ESMTP id h6V7cK2v088677
	for <ietf-ldapbis@OpenLDAP.org>; Thu, 31 Jul 2003 07:38:21 GMT
	(envelope-from steven.legg@adacel.com.au)
Received: from nexus.adacel.com (Not Verified[10.32.240.1]) by adacel.com with NetIQ MailMarshal (v5.5.3.16)
	id <B00011df0b>; Thu, 31 Jul 2003 17:34:00 +1000
Received: (qmail 23966 invoked from network); 31 Jul 2003 07:33:28 -0000
Received: from unknown (HELO osmium) (10.32.24.165)
  by nexus.adacel.com with SMTP; 31 Jul 2003 07:33:28 -0000
Reply-To: <steven.legg@adacel.com.au>
From: "Steven Legg" <steven.legg@adacel.com.au>
To: "'Kurt D. Zeilenga'" <Kurt@OpenLDAP.org>
Cc: <ietf-ldapbis@OpenLDAP.org>, "'Duane Buss'" <DBuss.PRV-1.PROVO@novell.com>,
        "'Steve McLain'" <SMCLAIN@novell.com>,
        "'Tom Doman'" <TDoman.PRV-1.PROVO@novell.com>,
        "'Jim Sermersheim'" <jimse@novell.com>
Subject: RE: ABNF of numericoid
Date: Thu, 31 Jul 2003 17:37:53 +1000
Message-ID: <024e01c35736$a7615450$a518200a@osmium.mtwav.adacel.com.au>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2120.0
In-Reply-To: <5.2.0.9.0.20030714102517.01d53a78@127.0.0.1>
Importance: Normal
Sender: owner-ietf-ldapbis@OpenLDAP.org
Priority: non-urgent
X-Loop: OpenLDAP
Precedence: bulk
Comment: ietf-ldapbis mailing list <http://www.OpenLDAP.org/lists/>
List-Archive: <http://www.OpenLDAP.org/lists/ietf-ldapbis/>
List-Help: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=help>
List-Unsubscribe: <mailto:ietf-ldapbis-request@OpenLDAP.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


X.680 defers to X.660 for the definition of OBJECT IDENTIFIER,
but notes that an OBJECT IDENTIFIER must have at least two components.
I don't have a copy of X.660 to check what other requirements
there are, however it is worth noting that the BER encoding of
OBJECT IDENTIFIER only supports values where the first component
is 0, 1 or 2. If the first component is 0 or 1 then the second
component must be in the range 0 to 39. If the first component
is 2 then the second component is unlimited.

Regards,
Steven

> -----Original Message-----
> From: owner-ietf-ldapbis@OpenLDAP.org
> [mailto:owner-ietf-ldapbis@OpenLDAP.org]On Behalf Of Kurt D. Zeilenga
> Sent: Monday, 14 July 2003 18:44
> To: Jim Sermersheim
> Cc: ietf-ldapbis@OpenLDAP.org; Duane Buss; Steve McLain; Tom Doman
> Subject: Re: ABNF of numericoid
> 
> 
> I've been advised that my previous post is mostly incorrect.
> Steven will post the real scoop.
> 
> Kurt
> 
> 


