Christian Huitema <> Mon, 07 June 1993 16:47 UTC

Received: from by IETF.CNRI.Reston.VA.US id aa29509; 7 Jun 93 12:47 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa29505; 7 Jun 93 12:47 EDT
Received: from by CNRI.Reston.VA.US id aa07688; 7 Jun 93 12:47 EDT
Received: from by with local SMTP id <>; Mon, 7 Jun 1993 17:32:26 +0100
Received: from by with Internet SMTP id <>; Mon, 7 Jun 1993 17:31:07 +0100
Received: by (5.65c/IDA-1.2.8) id AA13409; Mon, 7 Jun 1993 18:31:38 +0200
Message-Id: <>
To: Tim Howes <>
Subject: Re: LDAP
In-Reply-To: Your message of "07 Jun 93 11:07:10 EDT." <>
Date: Mon, 07 Jun 93 18:31:36 +0200
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Christian Huitema <>

	For resultCodes of noSuchObject, aliasProblem, invalidDNSyntax,
	isLeaf, and aliasDereferencingProblem, the matchedDN field is
	set to the name of the lowest entry (object or alias) in the
	DIT that was matched and is a truncated form of the name
	provided or, if an alias has been dereferenced, of the
	resulting name.  The matchedDN field should be set to a NULL DN
	(a zero length string) in all other cases.

The alias case is very ennoying. Suppose I provide <CN=Name, OU=Foo, O=Bar,
C= XX>, and that LDAP returns the "matched attributes" <C=Foobar, C=YY>. How do
I know whether this matched 2 or 3 components? Should we return a "matched
name parts" count in complement to the matched attributes? Or an alias

Christian Huitema
Aliases stink.