Kurt Zeilenga wrote:
Changes from -02:- added channel binding type negotiation through pseudo-mechanism names- CB-tls-srv-endpoint - CB-tls-unique- If the server doesn't list any then the client assumes all channelbinding types available on the client side are also available on the server side. But the server SHOULD list them.I'm concerned that (today) the implementation of a SASL mechanism does not have easy access to the list of supported SASL mechanism exposed by the server.Given that mechanism negotiation is "protocol specific", this should not be surprising to anyone. In fact, protocols need not even provide a mechanism negotiation facility.
It is only a SHOULD in section 4, bullet 2. But the intent was to not declare older (pre-SASL framework) protocols non-compliant. But as far as I know, all protocols that lacked this facility have it now. As a side note, I feel quite strongly that this facility should be present in all new protocols.