Re: Proposed XMPP Extension: Initial Authentication Pipelining

Dave Cridland <[email protected]>
Newsgroups gmane.network.jabber.standards-jig
Message-ID <CAKHUCzx9JA3e885NjpF143+kO+=gWtV_0uqHkJUxG2vyHXLT3Q@mail.gmail.com>
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 <[email protected]> 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 -- [email protected]
> To unsubscribe send an email to [email protected]
>

_______________________________________________
Standards mailing list -- [email protected]
To unsubscribe send an email to [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.