Re: [hybi] The Web Application Messaging Protocol => Draft RFC
Takeshi Yoshino <tyoshino@google.com> Mon, 28 September 2015 02:21 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 C55971B304E for <hybi@ietfa.amsl.com>; Sun, 27 Sep 2015 19:21:27 -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 A4r-XkPz1eOR for <hybi@ietfa.amsl.com>; Sun, 27 Sep 2015 19:21:24 -0700 (PDT)
Received: from mail-oi0-x22d.google.com (mail-oi0-x22d.google.com [IPv6:2607:f8b0:4003:c06::22d]) (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 61BE41B304A for <hybi@ietf.org>; Sun, 27 Sep 2015 19:21:24 -0700 (PDT)
Received: by oixx17 with SMTP id x17so83291982oix.0 for <hybi@ietf.org>; Sun, 27 Sep 2015 19:21:23 -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=mttW6twCq7VNTtXwPANw3QiE/T9yNz/Ilb5M9vDNz84=; b=GUUPkKi+VqBUQfDJ8mbost/U8n/3oPn/wu+4+5c2hqExq9MpEzWjZ8GwHI81GehfQr /dbDhNojT2OFXqIfWpjoZy43dKFu6TO/hT71vDcle96gJ4GYmpCZp0LO0xZO2iwOoEkQ 32gzneCtOjJH66tQ/rsSK++cOvQLufWp0WBeryiHK0z8TWJly2upZJV4eFIx21mDM1XJ l4gHvH4gcREQjaC+Lbl35sIXgu3y39X3tgMJkc4DD1and/m3ITixzipM+lkTgjQ7dCql BV3uT/Ha3UCAhrRGw269FleGJwljwzyJzI33q1uQCUuijX6m+Ta3x3MnSx4vYnqm7UX0 d6Cg==
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=mttW6twCq7VNTtXwPANw3QiE/T9yNz/Ilb5M9vDNz84=; b=A+WKjPpIaIYEkNceU/oVahe9iXugAEMZqgsndUQkTfeYNM4a4DZYv5JehzKlVRWJGI eryqhGMLYdscjVOk4EU0UveYOOxscQWOAuYxmIjOcWSNmoC5+W0wAfxgKxs7lf9EO8/S DmXjaoMzdBViCpoBStWQGJDX5FXbO2fWB3brwYfA2depfZmNsDKsTbjxjuQUKqtqdOiD ECURjBBo4uJE/YDzrq3sEPn6xRv3aTNebOvkhYuDlBoN/DUSGSEn73U9vWQbMge0u8iH S7VUTLM+vCUJ0VcwufaQVCLCzFvdu+8ys9nCZVtotQRR5Pu+Gdv2NPzz8ajvnWKXhdUs MR/Q==
X-Gm-Message-State: ALoCoQnp9Z67WUSFDT1cSlPZrx9JIwpNVr0LnPxRyitKwMH9wKgtmSD5xINxLoMxrBA+dh6fRwOu
X-Received: by 10.202.183.3 with SMTP id h3mr7904116oif.58.1443406883562; Sun, 27 Sep 2015 19:21:23 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.202.221.87 with HTTP; Sun, 27 Sep 2015 19:21:03 -0700 (PDT)
In-Reply-To: <56080E1B.4000107@tavendo.de>
References: <55FAD8C4.5080706@tavendo.de> <56080E1B.4000107@tavendo.de>
From: Takeshi Yoshino <tyoshino@google.com>
Date: Mon, 28 Sep 2015 11:21:03 +0900
Message-ID: <CAH9hSJa-qzN95eaC79y=vtc+CTaBX4W9nubQEWkvOMdhb2yzbA@mail.gmail.com>
To: Tobias Oberstein <tobias.oberstein@tavendo.de>
Content-Type: multipart/alternative; boundary="001a113ce59c8fd82a0520c55a8f"
Archived-At: <http://mailarchive.ietf.org/arch/msg/hybi/5jWFwPsDNRznGC3-r1goupAK7Ls>
Cc: Alexander Gödde <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:21:27 -0000
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 >
- [hybi] The Web Application Messaging Protocol Tobias Oberstein
- Re: [hybi] The Web Application Messaging Protocol… Tobias Oberstein
- Re: [hybi] The Web Application Messaging Protocol… Takeshi Yoshino
- Re: [hybi] The Web Application Messaging Protocol… Takeshi Yoshino
- Re: [hybi] The Web Application Messaging Protocol… Tobias Oberstein