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

Takeshi Yoshino <tyoshino@google.com> Mon, 28 September 2015 02:35 UTC

Return-Path: <tyoshino@google.com>
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 C7A271B307B for <hybi@ietfa.amsl.com>; Sun, 27 Sep 2015 19:35:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level:
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
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 vTfAMEddgBor for <hybi@ietfa.amsl.com>; Sun, 27 Sep 2015 19:35:11 -0700 (PDT)
Received: from mail-ob0-x234.google.com (mail-ob0-x234.google.com [IPv6:2607:f8b0:4003:c01::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D53711B3075 for <hybi@ietf.org>; Sun, 27 Sep 2015 19:35:10 -0700 (PDT)
Received: by obcxm10 with SMTP id xm10so15456469obc.3 for <hybi@ietf.org>; Sun, 27 Sep 2015 19:35:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=Qte5IRMrFyGUFpTyGygV7VWFca7bCo3EgVtNhMpqQrY=; b=n4BOflpTyiUlO+GJNQFYnD7JB33aOA8TdMj9g+m1Pzz6uh4CLtyis7P1JEbxbmMRrb mWz4O6Zw38LiUORF4BleRMjjwkF8/I2551nh7MxBtnH0Yh61c1p3h/jMOxsqq47SPaZA CQtAt9/CvlnQD+kKX9X+lv9IRuD525zgdc2jBcGjaOniWaWegpJuiOYogAUS/S/x6gXH g/Z2xJMS3kkPWqsjESXF/IdJUJrwvSKPAZ7Yx+0PMu+yIhdQekEyqKcXIDpNJh3I8mDm V+JHCI9zIfonQX8bULy0yUhBER/ovmPxw9PB6XsAAAI+ZvX5xpUlPmyt7GzMcFIM3Vq9 sFtw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=Qte5IRMrFyGUFpTyGygV7VWFca7bCo3EgVtNhMpqQrY=; b=QxFBnYePn0XAEukzAwDJjALd/0zGXAodse/6fNeQmjXa+VHp7sFJ3nBELrwIlqS6EJ T+DLreqxdKt+Whm4CSivmHZJqNFetZbHHSSX0xc1aRxYS1JekamGutc6TRpSfKCkpmzF 8k6/P3LOayk2VeAhl625uUT5swHFxp15GWKmxDtuej7zt6Vikne4qhwVYELcfEYlSH+4 1SUH4DoXmj/T3K5d7q0DZPNb7LPsCYUVrEmxkZgYs2c5acJZ90kW0vjetwQbf1YR192v diG+ZM1oRCptb+9szIbTWLWoDYi2SPMpP6T+WhLbDqoAIZ3nRtj3k0TLABgNFH0MogTH ZNqQ==
X-Gm-Message-State: ALoCoQm4okz9PS4UB7kVx1D8a5bJiaK+tJodBFb7OLNUliT3gWPkSRFcKPQhAce0XzJy3D7LiJ9f
X-Received: by 10.182.105.33 with SMTP id gj1mr8960695obb.77.1443407710094; Sun, 27 Sep 2015 19:35:10 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.202.221.87 with HTTP; Sun, 27 Sep 2015 19:34:50 -0700 (PDT)
In-Reply-To: <CAH9hSJa-qzN95eaC79y=vtc+CTaBX4W9nubQEWkvOMdhb2yzbA@mail.gmail.com>
References: <55FAD8C4.5080706@tavendo.de> <56080E1B.4000107@tavendo.de> <CAH9hSJa-qzN95eaC79y=vtc+CTaBX4W9nubQEWkvOMdhb2yzbA@mail.gmail.com>
From: Takeshi Yoshino <tyoshino@google.com>
Date: Mon, 28 Sep 2015 11:34:50 +0900
Message-ID: <CAH9hSJYs4rqOH2j2CadcPfRLBxHdV0KC0oWuLEnMmKgwJEb8eQ@mail.gmail.com>
To: Tobias Oberstein <tobias.oberstein@tavendo.de>
Content-Type: multipart/alternative; boundary=e89a8ff2546ed3d93a0520c58b68
Archived-At: <http://mailarchive.ietf.org/arch/msg/hybi/y7Uca839_4nu7IEqzZMm3p5gq68>
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 02:35:12 -0000

Once the I-D gets adopted (e.g.
https://www.ietf.org/mail-archive/web/hybi/current/msg09816.html) as an
IETF WG item, it'll be renamed to draft-ietf-hybi-tavendo-wamp-XX.txt.
Then, it goes through discussion/editing again, and then the chairs sends
it to IESG, i.e. AD, Barry.

See the history of permessage-deflate, http2 for example at
https://datatracker.ietf.org/doc/draft-ietf-hybi-permessage-compression/history/
and https://datatracker.ietf.org/doc/rfc7540/history/

Takeshi

On Mon, Sep 28, 2015 at 11:21 AM, Takeshi Yoshino <tyoshino@google.com>
wrote:

> On Mon, Sep 28, 2015 at 12:41 AM, Tobias Oberstein <
> tobias.oberstein@tavendo.de> wrote:
>
>> We've rewritten the WAMP spec (basic profile) into a RFC draft:
>>
>>
>> https://github.com/tavendo/WAMP/blob/master/rfc/draft-oberstet-hybi-tavendo-wamp-01.txt
>>
>> This is the first RFC style document we've written (well, Alex did the
>> rewriting;). We've tried hard to follow all formal rules and started to
>> reword the text so it better fits "RFC style".
>>
>> The the draft likely has more formal issues, but we now have a concrete
>> proposal text to discuss and work from on the content matter.
>>
>> Currently the draft is on GitHub, but I guess there is a process to get
>> each of the draft versions published.
>>
>> How does the process of publishing RFC draft work?
>>
>>
> General instructions here: https://www.ietf.org/id-info/
>
> See the NOTE WELL again at https://datatracker.ietf.org/submit/note-well/
>
> Use https://tools.ietf.org/tools/idnits/ to see nits in your I-D.
>
> 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.
>
> 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
>>> https://www.ietf.org/mailman/listinfo/hybi
>>>
>>>
>> _______________________________________________
>> hybi mailing list
>> hybi@ietf.org
>> https://www.ietf.org/mailman/listinfo/hybi
>>
>
>