RE: ADSI and RFC 2251

[Ron Ramsay <Ron.Ramsay@OpenDirectory.com.au>]

Thank you for your reply. It settles a number of issues.

An aside:

If the client thinks it is in the v2 world, it shouldn't be sending a v3
bind?

If I do send notice of disconnection there is no further communication.
Our customer requires interoperability. BTW Innosoft Distributed
Directory Server version 4.4.2 responds with a positive bind response
and not a notice of disconnection - I guess it knows what is going on.

Ron.

> -----Original Message-----
> From:	Mark Wahl [SMTP:M.Wahl@INNOSOFT.COM]
> Sent:	Friday, July 16, 1999 5:29 AM
> To:	Ron Ramsay
> Cc:	'ietf-ldapext@netscape.com'
> Subject:	Re: ADSI and RFC 2251
> 
> 
> There is no CONTEXT PRIMITIVE 9 in the choice in the bind request
> defined
> by any IETF document.  Some old code from this vendor used nonstandard
> tags as there were no SASL framework defined for v2.  1777 defines 0,
> 1 and 2,
> and 2251 defines constructed 3.  Since there is a SASL framework for
> v3, the
> vendor MUST use an appropriate SASL mechanism.  Perhaps you are
> recieving a 
> bind from a client that is thinking it is still in a v2 world? I
> recommend 
> that your implementation should return a notice of disconnection and
> close the 
> connection.
> 
> You can find more information on these nonstandard and
> noninteroperable LDAP 
> Bind choices in the Microsoft Developer Network Library.  It will tell
> you
> what they were intended for but not what the field contents are.
> 
> Mark Wahl, Directory Product Architect
> Innosoft International, Inc.