Hi, Please find my comments below.
> On 8 Feb 2017, at 22:50, XMPP Extensions Editor <[email protected]> wrote: > > This message constitutes notice of a Last Call for comments on XEP-0233 (XMPP > Server Registration for use with Kerberos V5). > > Abstract: This specification defines the Kerberos principal name of an XMPP > server. It also details a method by which a connecting client can determine > this Kerberos principal name when authenticating using the "GSSAPI" SASL > mechanism. > > URL: http://xmpp.org/extensions/xep-0233.html > > This Last Call begins today and shall end at the close of business on > 2017-02-22. > > 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? Yes. The specification clarifies the Kerberos Principal Name in the Microsoft SSPI environment. > 2. Does the specification solve the problem stated in the introduction and > requirements? Yes. > 3. Do you plan to implement this specification in your code? If not, why not? Yes, Isode has implemented this specification. > 4. Do you have any security concerns related to this specification? No. > 5. Is the specification accurate and clearly written? I have tested various scenarios including interoperability between GSS-API & SSPI, and the specification is in line with the results. Regards, Mili Verma > > Your feedback is appreciated! > _______________________________________________ > Standards mailing list > Info: https://mail.jabber.org/mailman/listinfo/standards > Unsubscribe: [email protected] > _______________________________________________ _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
