Re: Java LDAP API and the Java Community Process

[Rob Weltman <robw@worldspot.com>]

  In the Sun perception, there is no need for a Java LDAP API because of the existence of JNDI. There is almost zero possibility that a Java LDAP API would be considered by the JCP.

Rob


"Kurt D. Zeilenga" wrote:
> 
> The Java Community Program is the recognized organization
> responsible for publishing Java API specifications.
> 
> The JCP appears to independently review IETF Java API
> specifications prior to them becoming JCP approved
> specifications such as was done with RFC2853 (JCP 72), the
> Java GSSAPI API.  Though the RFC2853 was adopted "as is",
> the JCP could have adopted it with changes.  This clearly
> would have lead to interoperability problems between
> competing specifications.  It is unclear whether RFC2853
> should be progressed now that there is a JCP controlled
> revision process.
> 
> If and when the IETF LDAP Java is published as an RFC,
> it would likely be submitted to the JCP for review.  They
> may or may adopt it and if they do, they may make changes.
> This would lead to interoperability problems between
> competing specifications.
> 
> The JCP has on going work in LDAP (JNDI) and related
> networking services (SASL, TLS).  It seems reasonable to
> assume that the JCP would likely not accept an IETF Java
> API without change.
> 
> To avoid problems caused by having two competing Java LDAP
> API specifications, I recommend this work be continued under
> the auspices of the JCP and removed from the WG charter.
> 
> Kurt