[Standards] Proposed XMPP Extension: Token-based reconnection

Florian Schmaus flo at geekplace.eu
Sat Feb 6 11:22:49 UTC 2016

On 05.02.2016 20:04, Lance Stout wrote:
> Integrating this sort of token authentication with XEP-0198 would be the
> bigger win, because then SASL could be skipped entirely along with the
> initial stream setup (like how we can use BOSH with pre-binding). The 
> stream management ID could easily be a JWT or equivalent token that would
> be sufficient for authentication. The missing piece would be allowing
> the <resumed/> element to include a new ID value (I'm not sure why it
> currently returns the 'previous' ID without allowing a new ID).

Exactly. I always thought a fast reconnect (fr) mechanism based on
stream management should work something like this:

1. Client receives secure reconnect token via <enabled/> (or <resumed/>)


2. Client stream is terminated

3. Client tries to reconnect and resume the previous stream by
3.1 Performing a DNS SRV lookup on _xmpp-fastreconnect._tcp.<xmpp-domain>
3.2 Connecting to one of the host discovered by the DNS SRV lookup
3.3 Performing TLS right-away
3.4 Sending a


Nonza. Where the 'h' attribute contains the sequence number of the last
handled stanza.

If the stream can be resumed, the server replies with


Which is analogous to xep198's resume/resumed step.

What do you think? I'm willing to XEPify this, if the approach is
considered useful.

- Florian

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 603 bytes
Desc: OpenPGP digital signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20160206/2798c48e/attachment.sig>

More information about the Standards mailing list