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

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
>