[hybi] The Web Application Messaging Protocol

Tobias Oberstein <tobias.oberstein@tavendo.de> Thu, 17 September 2015 15:14 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 []) by ietfa.amsl.com (Postfix) with ESMTP id 84C421A1B60 for <hybi@ietfa.amsl.com>; Thu, 17 Sep 2015 08:14:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.1
X-Spam-Status: No, score=0.1 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id X5J-AKX9KuMC for <hybi@ietfa.amsl.com>; Thu, 17 Sep 2015 08:14:15 -0700 (PDT)
Received: from EXHUB020-4.exch020.serverdata.net (exhub020-4.exch020.serverdata.net []) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB6591A86E9 for <hybi@ietf.org>; Thu, 17 Sep 2015 08:14:15 -0700 (PDT)
Received: from [] ( by smtpx20.serverdata.net ( with Microsoft SMTP Server (TLS) id 8.3.377.0; Thu, 17 Sep 2015 08:14:14 -0700
From: Tobias Oberstein <tobias.oberstein@tavendo.de>
To: "hybi@ietf.org" <hybi@ietf.org>
Message-ID: <55FAD8C4.5080706@tavendo.de>
Date: Thu, 17 Sep 2015 17:14:12 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/hybi/FScTwSKeLjxCGAmy4RMU-saBxl4>
Subject: [hybi] The Web Application Messaging Protocol
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: Thu, 17 Sep 2015 15:14:17 -0000


the "Web Application Messaging Protocol" (WAMP) is a _WebSocket 
subprotocol_ that provides two application messaging patterns in one 
unified protocol:

- Remote Procedure Calls
- Publish & Subscribe

There is an open specification, multiple independent implementations and 
a growing user community. The protocol has seen takeup in particular 
with IoT applications.

Project site:	http://wamp.ws/
Specification:	https://github.com/tavendo/WAMP/tree/master/spec
Mailing list:	https://groups.google.com/forum/#!forum/wampws
Chat room:	https://gitter.im/tavendo/WAMP

While we do have a spec, having a proper RFC for WAMP would be a further 
step forward.

Working on a RFC and producing a high-quality document is a lot of work 
and requires significant commitment by multiple parties, since 
otherwise, sufficient peer review and feedback isn't guaranteed.

While a lot of contributors have been working over the last +3 years on 
WAMP, we need commitment to work on the _actual RFC_.

So if you do have interest in seeing a WAMP RFC, your input and feedback 
is welcome! Please reply ..