Re: [hybi] I-D Action: draft-ietf-hybi-permessage-compression-28.txt

Hi Tobia

In order for the wg to be recharted / resurrected
It is necessary to be enough interest in the work from several peoples/companies on the items
Other then a clear technical proposal(s)

At moment it seems that people are more interested to evolve HTTP2 then in WebSocket.

Br
Salvatore

From: Takeshi Yoshino [mailto:tyoshino@google.com]
Sent: den 14 september 2015 11:11
To: Tobias Oberstein
Cc: Barry Leiba; Salvatore Loreto; hybi@ietf.org
Subject: Re: [hybi] I-D Action: draft-ietf-hybi-permessage-compression-28.txt

On Mon, Sep 14, 2015 at 5:44 AM, Tobias Oberstein <tobias.oberstein@tavendo.de<mailto:tobias.oberstein@tavendo.de>> wrote:
Great; I've checked it too, and I agree.  I've approved it, and you
should see the announcement soon.

Awesome! The WebSocket compression extension is of great practical value.

Thank you, Tobias for your continued contribution including discussion and building the reliable and comprehensive test suites.

The working group will remain open until the RFC is published, after
which I'll close the working group, but leave the mailing list open

Regarding the closing of the working group, I would like to ask what is required to recharter the WG to work on a specific WebSocket subprotocol.

I also wonder what we'll lose and what we won't (in addition to the mailing list) after WG close. I was worried that we might lose the mailing list too.

I guess at least we'll be unable to raise I-Ds as WG items while the WG is closed.

The current WG charter has this to say:

"""
The working group will also serve as a discussion venue for
subprotocols.  However, no subprotocol is currently chartered as a
deliverable, and the WG must be rechartered to work on any
subprotocols.
""" http://datatracker.ietf.org/doc/charter-ietf-hybi/

The subprotocol I would like to start working on is:

"The Web Application Messaging Protocol (WAMP)"

http://wamp.ws/
https://github.com/tavendo/WAMP/
http://www.iana.org/assignments/websocket/websocket.xml#subprotocol-name

WAMP was the 3rd WebSocket subprotocol officially registered at IANA, has gone through 3+ years of development, has nearly two dozen independent and interoparable implementations, and an active community.

I have asked on the WAMP implementors mailing list if there is interest in working on a RFC for WAMP, and multiple responses indicate that there is indeed interest:

https://groups.google.com/forum/#!topic/wampws/LlKjMF3ZJf8

I am original author of WAMP, and have been active during the development of WebSocket and the WebSocket compression extension on the Hybi working group.

I also created and maintain the Autobahn WebSocket testsuite - an automated testsuite for WS used by most implementors.

http://autobahn.ws/testsuite/

Apart from that I wrote a couple of WebSocket implementations in different languages.

However, I never wrote an RFC nor do I know a lot about IETF processes and such.

Hence my naive question: what's required to start working on WAMP within the context of this WG?

Cheers,
/Tobias

_______________________________________________
hybi mailing list
hybi@ietf.org<mailto:hybi@ietf.org>
https://www.ietf.org/mailman/listinfo/hybi