[Standards] dialback: piggybacking

Peter Saint-Andre stpeter at jabber.org
Thu Jun 21 10:42:07 CDT 2007

Matthias Wimmer wrote:
> Philipp Hancke schrieb:
>> Most of the complexity of piggybacking must be implemented on the
>> originating server. There are (lots of) pitfalls when deciding whether
>> to use piggybacking on 1.0 streams which are encrypted by TLS or
>> authenticated by SASL, etc.
>> Yet, as the spec does not mandate that you MUST reuse a connection, you
>> don't have to implement 'active' piggybacking.
>> What about discouraging active usage ("you don't want to implement
>> that") while keeping 'passive' support (on the receiving  server) for
>> backward compability?
> I would not like to see active piggybacking discouraged. But maybe it
> would really be a good idea to make passive support a MUST (should not
> be hard to implement) while active support could get downgreaded from

It's worth considering.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 7358 bytes
Desc: S/MIME Cryptographic Signature
Url : http://mail.jabber.org/pipermail/standards/attachments/20070621/b4332d4d/smime-0001.bin

More information about the Standards mailing list