Re: [Standards] Stanza Size Limits (was Re: [jdev] Communicate between two client instances of the same ID)
On Tuesday 02 September 2008 21:47:55 Peter Saint-Andre wrote: > http://www.xmpp.org/extensions/inbox/stanzalimits.html > > We never published that, though... Oh, cool. I was going to suggest a XEP for that stuff, too. :) I still think the minimum recommended supported size belongs in xmpp-core though. -Justin
Re: [Standards] Stanza Size Limits (was Re: [jdev] Communicate between two client instances of the same ID)
Justin Karneges wrote: Dragging this over from jdev: Hmm. XMPP is not optimized for sending around 100k+ messages. Would 64KB chunks a reasonable thing to do? That's probably still too high. There is currently no specified maximum size for XMPP stanzas, but individual implementations may enforce different values. The original jabberd 1.0 server had around a 10KB maximum. The general consensus is that stanzas should be "small", and this is largely in part because large stanzas block transmission of other stanzas (you cannot send many stanzas in parallel over one stream). Right now it's fuzzy as to how small you should chunk your data for maximum compatibility. I think we should define the largest stanza size that must be supported by clients and servers. We could just make this value 1 bytes, from the opening '<' to the final '>' of the stanza. The text should go into RFC 3920bis as a SHOULD. This way, stanzas 1 bytes or smaller are guaranteed to succeed in transmission. Stanzas larger than 1 bytes would still be transmittable, but without any guarantees that the other side will accept it (which is not any worse than the situation today). A question: which stanza error are we supposed to use to reject a stanza that is too large? Such an error would be very useful to determine the MTU. http://www.xmpp.org/extensions/inbox/stanzalimits.html We never published that, though... /psa smime.p7s Description: S/MIME Cryptographic Signature
[Standards] Stanza Size Limits (was Re: [jdev] Communicate between two client instances of the same ID)
Dragging this over from jdev: > > > Hmm. XMPP is not optimized for sending around 100k+ messages. > > > > Would 64KB chunks a reasonable thing to do? > > That's probably still too high. There is currently no specified maximum > size for XMPP stanzas, but individual implementations may enforce different > values. The original jabberd 1.0 server had around a 10KB maximum. The > general consensus is that stanzas should be "small", and this is largely in > part because large stanzas block transmission of other stanzas (you cannot > send many stanzas in parallel over one stream). Right now it's fuzzy as to how small you should chunk your data for maximum compatibility. I think we should define the largest stanza size that must be supported by clients and servers. We could just make this value 1 bytes, from the opening '<' to the final '>' of the stanza. The text should go into RFC 3920bis as a SHOULD. This way, stanzas 1 bytes or smaller are guaranteed to succeed in transmission. Stanzas larger than 1 bytes would still be transmittable, but without any guarantees that the other side will accept it (which is not any worse than the situation today). A question: which stanza error are we supposed to use to reject a stanza that is too large? Such an error would be very useful to determine the MTU. -Justin
[Standards] Proposed XMPP Extension: C2C Authentication using TLS
The XMPP Extensions Editor has received a proposal for a new XEP. Title: C2C Authentication using TLS Abstract: This document describes how to negotiate TLS extensions when using TLS for end-to-end XML streams between two clients. It covers X.509 certificates with an without CA, the use of OpenPGP, Shared Remote Passwords (SRP) and how to use one extension to bootstrap a trust relationship. URL: http://www.xmpp.org/extensions/inbox/c2ctls.html The XMPP Council will decide at its next meeting whether to accept this proposal as an official XEP.
Re: [Standards] Proposed XMPP Extension: Direct MUC Invitations
Peter Saint-Andre wrote: In the Council meeting just ended, Kevin Smith suggested that we might want to bring back the old jabber:x:conference namespace: You have been invited to the [EMAIL PROTECTED] room. Older clients already support that, so the suggestion seems reasonable to me. Seeing no objections, I've updated the proposal to use jabber:x:conference, see version 0.0.5: http://www.xmpp.org/extensions/inbox/direct-invitations.html /psa smime.p7s Description: S/MIME Cryptographic Signature