[Standards] draft-ietf-xmpp-websocket-10

drichards at coversant.com drichards at coversant.com
Wed Oct 8 18:42:35 UTC 2014



> -----Original Message-----
> From: Standards [mailto:standards-bounces at xmpp.org] On Behalf Of Peter
> Saint-Andre - &yet
> Sent: Wednesday, October 08, 2014 12:15 PM
> To: standards at xmpp.org
> Subject: Re: [Standards] draft-ietf-xmpp-websocket-10
> 
> On 10/8/14, 11:04 AM, drichards at coversant.com wrote:
> > Section 3.2 of draft-ietf-xmpp-websocket-xx specifies that data frames
> > must be of type text and contain UTF-8 encoded data.  Was there some
> > reason for this since it makes XMPP stream compression not usable?
> 
> Hi Dave,
> 
> I think we'd recommend doing compression at the HTTP layer, just as for
> WebSocket we're doing security at the HTTP layer.
> 
> Also, the spec has been approved for publication and is in the RFC Editor
queue
> so it's too late to change it:
> 
> http://datatracker.ietf.org/doc/draft-ietf-xmpp-websocket/
> 
> And xmpp at ietf.org is the right list for IETF specs. :-)
> 
> Peter
> 
> --
> Peter Saint-Andre
> https://andyet.com/

Argh. No I don't take it back - all it is is a framework for creating
compression extensions.  It doesn't actually define any specific mechanisms.




More information about the Standards mailing list