This message constitutes notice of a Last Call for comments on
XEP-0388.
Title: Extensible SASL Profile
Abstract:
This document describes a replacement for the SASL profile documented
in RFC 6120 which allows for greater extensibility.
URL: https://xmpp.org/extensions/xep-0388.html
This Last
This message constitutes notice of a Last Call for comments on
XEP-0386.
Title: Bind 2
Abstract:
This specification provides a single-request replacement for several
activities an XMPP client needs to do at startup.
URL: https://xmpp.org/extensions/xep-0386.html
This Last Call begins today and
On Mon, 18 Mar 2024 at 14:19, Stephen Paul Weber
wrote:
> >1. Is this specification needed to fill gaps in the XMPP protocol
> >stack or to clarify an existing protocol?
>
> Yes, we currently have no way to use multiple SASL or otherwise to acheive
> a
> similar result.
>
> >2. Does the
However it does lack any way to support indicating to the server
which
credential will be used, other than perhaps by implication from the SASL
mechanism.
That's not the purview of a SASL profile. If a SASL mechanism supports
multiple credentials, that's entirely encapsulated within that
Good morning Council Members,
the next XMPP Council Meeting will take place on, Tuesday, March 19
2024 at 16:00 UTC in xmpp:coun...@muc.xmpp.org?join
The Agenda is as follows:
1) Roll call
2) Agenda Bashing
3) Editors update
* LAST CALL: XEP-0388 (Extensible SASL Profile)
* LAST CALL:
On Mon, 18 Mar 2024 at 08:59, Daniel Gultsch wrote:
>
> This message constitutes notice of a Last Call for comments on
> XEP-0386.
>
> Title: Bind 2
> Abstract:
> This specification provides a single-request replacement for several
> activities an XMPP client needs to do at startup.
>
> URL:
1. Is this specification needed to fill gaps in the XMPP protocol
stack or to clarify an existing protocol?
"Needed" is a strong word, but it is useful to have everything enabled at
once.
2. Does the specification solve the problem stated in the introduction
and requirements?
Yes
3. Do
On Mon, 18 Mar 2024 at 09:00, Daniel Gultsch wrote:
> This message constitutes notice of a Last Call for comments on
> XEP-0388.
>
> Title: Extensible SASL Profile
> Abstract:
> This document describes a replacement for the SASL profile documented
> in RFC 6120 which allows for greater
1. Is this specification needed to fill gaps in the XMPP protocol
stack or to clarify an existing protocol?
Yes, we currently have no way to use multiple SASL or otherwise to acheive a
similar result.
2. Does the specification solve the problem stated in the introduction
and requirements?
On Mon, 18 Mar 2024, 17:32 Stephen Paul Weber,
wrote:
> >> However it does lack any way to support indicating to the server
> >> which
> >> credential will be used, other than perhaps by implication from the SASL
> >> mechanism.
> >>
> >>
> >That's not the purview of a SASL profile. If a SASL
> This message constitutes notice of a Last Call for comments on
> XEP-0388.
>
> Title: Extensible SASL Profile
> Abstract:
> This document describes a replacement for the SASL profile documented
> in RFC 6120 which allows for greater extensibility.
>
> URL:
> Yes, I have implemented this for xmpp.js -- except for "tasks" which I have
> not implemented and I think there are no official profiles of, making that a
> somewhat more risky area of the spec.
There is a task defined in XEP-0480 (for upgrading server-stored SCRAM hashes,
for example from
12 matches
Mail list logo
