Re: LDAPEXT status and last calls

["Kurt D. Zeilenga" <Kurt@OpenLDAP.Org>]

Though most of draft-ietf-ldapext-ldap-c-api-01.txt is okay,
I believe there are still a number of outstanding issues that
must be discussed and resolved before last call should be made.
I believe the draft will require significant revision before it
can be progressed as a proposed standard.  I do not believe a WG
last call should be made on this draft at this time.

In particular, I believe the following issues must be
addressed before it should be progressed:

* UTF-8 requirement for DNs/string values
	Needs to be clarified what is required of the implementation
	when using LDAPv2 and detailing specific translation requirements.
* Header requirements should be detailed.

Also, all the "Outstanding Issues" should be resolved:

23.1 multithreaded apps
	Could be described as an extension...
	(I am willing to work on such).

23.3 client control for chasing referrals
	Could be described as an extension...

23.4 hostname:port and IPv6
	How is this resolved in URLs?  (ie: proto://host:port/ must also
	conflict with IPv6)  Recommend we resolve the LDAP IPv6 issue
	similiar to however it is being resolved with URL's.

23.5 SASL API
	Could be described as an extension...

23.6 charsets other than UTF-8
	Should be handled as an extension (I am working on such).

23.7 Session Options
	ldap_get/set_option interface should be nailed down.

23.9 LDAP C API extension mechanism
	should be nailed down.

--Kurt