Re: [hybi] The Web Application Messaging Protocol => Draft RFC

Tobias Oberstein <tobias.oberstein@tavendo.de> Mon, 28 September 2015 10:01 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 120861B331C for <hybi@ietfa.amsl.com>; Mon, 28 Sep 2015 03:01:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 TyYu0mGplty6 for <hybi@ietfa.amsl.com>; Mon, 28 Sep 2015 03:01:27 -0700 (PDT)
Received: from EXHUB020-1.exch020.serverdata.net (exhub020-1.exch020.serverdata.net [206.225.164.28]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F7061B330D for <hybi@ietf.org>; Mon, 28 Sep 2015 03:01:27 -0700 (PDT)
Received: from [192.168.43.73] (89.204.130.17) by smtpx20.serverdata.net (206.225.164.33) with Microsoft SMTP Server (TLS) id 8.3.377.0; Mon, 28 Sep 2015 03:01:26 -0700
To: Takeshi Yoshino <tyoshino@google.com>
References: <55FAD8C4.5080706@tavendo.de> <56080E1B.4000107@tavendo.de> <CAH9hSJa-qzN95eaC79y=vtc+CTaBX4W9nubQEWkvOMdhb2yzbA@mail.gmail.com>
From: Tobias Oberstein <tobias.oberstein@tavendo.de>
Message-ID: <56090FF1.50501@tavendo.de>
Date: Mon, 28 Sep 2015 12:01:21 +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: <CAH9hSJa-qzN95eaC79y=vtc+CTaBX4W9nubQEWkvOMdhb2yzbA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/hybi/EU2XNKED4cfqr04-c0lk-vpoN8M>
Cc: =?UTF-8?Q?Alexander_G=c3=b6dde?= <alexander.goedde@tavendo.de>, "hybi@ietf.org" <hybi@ietf.org>, Barry Leiba <barryleiba@computer.org>
Subject: Re: [hybi] The Web Application Messaging Protocol => Draft RFC
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: Mon, 28 Sep 2015 10:01:29 -0000

Takeshi,

thanks for your hints! I've read through the documents you mentioned and 
went through submission (only had to change version number).

So this worked .. here:

https://tools.ietf.org/html/draft-oberstet-hybi-tavendo-wamp-00

Awesome!

(Nits: Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 20 
comments (--).)

/Tobias

> Then, submit at https://datatracker.ietf.org/submit/ (or just submit w/o
> idnits and you'll see rejection if there's any nits). The submitted I-D
> shows up on tools.ietf.org <http://tools.ietf.org>.
>
> Submission tool instructions:
> https://datatracker.ietf.org/submit/tool-instructions/
>
>     Anything else to do?
>
>     /Tobias
>
>
>     Am 17.09.2015 um 17:14 schrieb Tobias Oberstein:
>
>         Hi,
>
>         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 ..
>
>         Cheers,
>         /Tobias
>
>         _______________________________________________
>         hybi mailing list
>         hybi@ietf.org <mailto:hybi@ietf.org>
>         https://www.ietf.org/mailman/listinfo/hybi
>
>
>     _______________________________________________
>     hybi mailing list
>     hybi@ietf.org <mailto:hybi@ietf.org>
>     https://www.ietf.org/mailman/listinfo/hybi
>
>