[Standards] Call for Experience: XEP-0229: Stream Compression with LZW

Dave Cridland dave at cridland.net
Thu Mar 22 11:29:01 UTC 2018

I'm very interested to see if there has been any implementation of this
specification at all. If there hasn't been, then of course it cannot
advance, and I would in this case prefer to deprecate it.

On Thu, 22 Mar 2018, 07:59 Jonas Wielicki, <jonas at wielicki.name> wrote:

> The XEP Editor would like to Call for Experience with XEP-0229 before
> presenting it to the Council for advancing it to Final status.
> During the Call for Experience, please answer the following questions:
> 1. What software has XEP-0229 implemented? Please note that the
> protocol must be implemented in at least two separate codebases (at
> least one of which must be free or open-source software) in order to
> advance from Draft to Final.
> 2. Have developers experienced any problems with the protocol as
> defined in XEP-0229? If so, please describe the problems and, if
> possible, suggested solutions.
> 3. Is the text of XEP-0229 clear and unambiguous? Are more examples
> needed? Is the conformance language (MAY/SHOULD/MUST) appropriate?
> Have developers found the text confusing at all? Please describe any
> suggestions you have for improving the text.
> If you have any comments about advancing XEP-0229 from Draft to Final,
> please provide them by the close of business on 2018-04-05. After the
> Call for Experience, this XEP might undergo revisions to address
> feedback received, after which it will be presented to the XMPP
> Council for voting to a status of Final.
> You can review the specification here:
> https://xmpp.org/extensions/xep-0229.html
> Please send all feedback to the standards at xmpp.org discussion list.
> _______________________________________________
> Standards mailing list
> Info: https://mail.jabber.org/mailman/listinfo/standards
> Unsubscribe: Standards-unsubscribe at xmpp.org
> _______________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/standards/attachments/20180322/3025830a/attachment-0001.html>

More information about the Standards mailing list