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

Tobias Oberstein <tobias.oberstein@tavendo.de> Sun, 13 September 2015 20:44 UTC

Return-Path: <tobias.oberstein@tavendo.de>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1A891B2AAA for <hybi@ietfa.amsl.com>; Sun, 13 Sep 2015 13:44:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.069
X-Spam-Level:
X-Spam-Status: No, score=0.069 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_SORBS_WEB=0.77] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Au6PGl2bg7dL for <hybi@ietfa.amsl.com>; Sun, 13 Sep 2015 13:44:23 -0700 (PDT)
Received: from EXHUB020-3.exch020.serverdata.net (exhub020-3.exch020.serverdata.net [206.225.164.30]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1430D1A0366 for <hybi@ietf.org>; Sun, 13 Sep 2015 13:44:23 -0700 (PDT)
Received: from [192.168.43.73] (89.204.130.38) by smtpx20.serverdata.net (206.225.164.35) with Microsoft SMTP Server (TLS) id 8.3.377.0; Sun, 13 Sep 2015 13:44:21 -0700
To: Barry Leiba <barryleiba@computer.org>, Salvatore Loreto <salvatore.loreto@ericsson.com>
References: <20150824112514.18998.33071.idtracker@ietfa.amsl.com> <CAH9hSJbDBih=-pc=F0E9=7hLcL+nyHo+qc=nvsYaXmV=hiA7ZQ@mail.gmail.com> <CAC4RtVAgrr5jK9xu3PfEqbmC8fB6pfZ98SDR6z+yKyRBEgcFSA@mail.gmail.com> <CAH9hSJYLDrio25+vboJ1GzsW937s2yRURjhdXhT5A25bDKdOyw@mail.gmail.com> <7730FEFF-FA09-4278-A8BF-B3325E6C2EC1@ericsson.com> <CAC4RtVDbC7+DD84MULXDa0wPuud_1msLdy4AdLoQN7_x8HHAbw@mail.gmail.com>
From: Tobias Oberstein <tobias.oberstein@tavendo.de>
Message-ID: <55F5E021.2000803@tavendo.de>
Date: Sun, 13 Sep 2015 22:44:17 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <CAC4RtVDbC7+DD84MULXDa0wPuud_1msLdy4AdLoQN7_x8HHAbw@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/hybi/7O6sE8X57EBCD3m1sxldQq1J-3s>
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] I-D Action: draft-ietf-hybi-permessage-compression-28.txt
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hybi/>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Sep 2015 20:44:24 -0000

> 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.

>
> 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.

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