As this thread winds down, I have to say (as a side note) that I do like RFC 1777's use of the term "session" over our term "association".
Just couldn't resist picking at the not-yet-healed scab.
>>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 10/26/04 1:08:09 AM >>> Ron: > So , please, chapter and verse! Section 4.3. But, as discussed on this list before, clarification of that section was needed to make it clear the purpose of the Unbind operation is to gracefully terminate the connection and everything it carries. At 10:50 PM 10/25/2004, Jim Sermersheim wrote: >[protocol] is more explicit than "may close the connection", and says "The function of the Unbind Operation is to terminate an LDAP exchange and close the connection". This does remove ambiguity and resolves some interoperability issues (i.e. RFC 2251 failed to specify the AuthN state of a protocol session post Unbind). Correct. We could even be more precise in that the Unbind request causes the termination of the LDAP exchange and the graceful closure of the SASL layer, graceful closure of the TLS layer, and graceful close of the connection. >Ron, are you asserting that we should go back to RFC 2251 semantics, >or RFC 1777 semantics. This question is ambiguous as there is/was contention as to what those semantics were. A better question would be: If the Unbind operation is not disconnect operation, what is it? >If we go back to RFC 2251 semantics (which are underspecified), Again, ambiguous. Some would argue that [Protocol] and RFC 2251 are consistent here. That is, the function in both is to gracefully terminate the connection (and everything it carries). |