Can we see if the Kitten IETF list (which tends to cover the use of TLS channel bindings with SASL mechanisms) has any comments on this before advancing it? I appreciate this is a departure from our process, strictly speaking, but it feels like a bit of outreach might benefit this and we could consider it part of the Last Call.
Dave. On Mon, 6 May 2024 at 18:22, Daniel Gultsch <[email protected]> wrote: > This message constitutes notice of a Last Call for comments on > XEP-0440. > > Title: SASL Channel-Binding Type Capability > Abstract: > This specification allows servers to annouce their supported SASL > channel-binding types to clients. > > URL: https://xmpp.org/extensions/xep-0440.html > > This Last Call begins today and shall end at the close of business on > 2024-05-20. > > Please consider the following questions during this Last Call and send > your feedback to the [email protected] discussion list: > > 1. Is this specification needed to fill gaps in the XMPP protocol > stack or to clarify an existing protocol? > > 2. Does the specification solve the problem stated in the introduction > and requirements? > > 3. Do you plan to implement this specification in your code? If not, > why not? > > 4. Do you have any security concerns related to this specification? > > 5. Is the specification accurate and clearly written? > > Your feedback is appreciated! > _______________________________________________ > Standards mailing list -- [email protected] > To unsubscribe send an email to [email protected] >
_______________________________________________ Standards mailing list -- [email protected] To unsubscribe send an email to [email protected]
