1 Dec
2025
1 Dec
'25
1:54 p.m.
The XMPP Extensions Editor has received a proposal for a new XEP.
Title: Initial Authentication Pipelining
Abstract:
This specification defines a protocol for discovering if the SASL2
<authenticate> can be pipelined safely along with the stream open, and
if so allows the client to perform this pipelining safely.
URL: https://xmpp.org/extensions/inbox/iap.html
The Council will decide in the next two weeks whether to accept this
proposal as an official XEP.
2 Dec
2 Dec
4:27 a.m.
There's been no discussion (that I'm aware of) on this one. I'm willing to
be convinced that it's not useful - but I personally feel it's safer than
the JFDI approach in (or implied in) FAST.
I haven't implemented this one, either - though I think it's simple enough
that it'd be easy to do so.
I'll try to make the Council meeting in case there are questions.
On Mon, 1 Dec 2025 at 20:54, Daniel Gultsch <daniel(a)gultsch.de> wrote:
The XMPP Extensions Editor has received a proposal for
a new XEP.
Title: Initial Authentication Pipelining
Abstract:
This specification defines a protocol for discovering if the SASL2
<authenticate> can be pipelined safely along with the stream open, and
if so allows the client to perform this pipelining safely.
URL: https://xmpp.org/extensions/inbox/iap.html
The Council will decide in the next two weeks whether to accept this
proposal as an official XEP.
_______________________________________________
Standards mailing list -- standards(a)xmpp.org
To unsubscribe send an email to standards-leave(a)xmpp.org
0
days inactive
1
days old
1 comments
2 participants
participants (2)
-
Daniel Gultsch -
Dave Cridland