From nobody Tue Sep 1 06:31:36 2015 Return-Path: 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 32B2C1B5681 for ; Tue, 1 Sep 2015 06:31:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.2 X-Spam-Level: X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] 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 EqDpfbDs7h6b for ; Tue, 1 Sep 2015 06:31:33 -0700 (PDT) Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2628E1B6C16 for ; Tue, 1 Sep 2015 06:31:27 -0700 (PDT) X-AuditID: c1b4fb3a-f79136d0000071e2-3d-55e5a8ae1e43 Received: from ESESSHC018.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id E5.D1.29154.EA8A5E55; Tue, 1 Sep 2015 15:31:26 +0200 (CEST) Received: from ESESSMB109.ericsson.se ([169.254.9.159]) by ESESSHC018.ericsson.se ([153.88.183.72]) with mapi id 14.03.0248.002; Tue, 1 Sep 2015 15:31:25 +0200 From: Salvatore Loreto To: Takeshi Yoshino Thread-Topic: [hybi] I-D Action: draft-ietf-hybi-permessage-compression-28.txt Thread-Index: AQHQ3l+S/EFgCf4yEkytb4X1k3hZOJ4a4dAAgAVBVICAAJM6AIAG4FkA Date: Tue, 1 Sep 2015 13:31:25 +0000 Message-ID: <7730FEFF-FA09-4278-A8BF-B3325E6C2EC1@ericsson.com> References: <20150824112514.18998.33071.idtracker@ietfa.amsl.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [153.88.183.147] Content-Type: multipart/alternative; boundary="_000_7730FEFFFA094278A8BFB3325E6C2EC1ericssoncom_" MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprFIsWRmVeSWpSXmKPExsUyM+Jvje66FU9DDfp/SlgcWnyJ1eL9y21M FtteHWZ1YPZoWdXL7LFgU6nHkiU/mQKYo7hsUlJzMstSi/TtErgyOjuPshU8D6qYeesUewPj DvcuRk4OCQETifOz9zJC2GISF+6tZ+ti5OIQEjjKKPF40kkWCGcxo8T13uWsIFVsAmYSzx9u YQaxRQQ0JVZefcgGYjMLeElMur6RCcQWFvCVuHJ7KStETYDEhevX2CBsN4k3sy4C9XJwsAio SCx6BXYEr4C9RHvvDFaIXdOYJCZfnwXWyykQKNE9cTtYLyPQdd9PrWGC2CUucevJfCaIqwUk luw5zwxhi0q8fPyPFWS+hICSxLStaRDlyRKf329nhtglKHFy5hOWCYyis5BMmoWkbBaSMoi4 jsSC3Z/YIGxtiWULXzPD2GcOPIbqtZb4d+U1I7KaBYwcqxhFi1OLi3PTjYz0Uosyk4uL8/P0 8lJLNjECI/Pglt9WOxgPPnc8xCjAwajEw7uA7WmoEGtiWXFl7iFGaQ4WJXHeZqYHoUIC6Ykl qdmpqQWpRfFFpTmpxYcYmTg4pRoYyxPVe15rTk5jympfHstZZ5jesDvcQewo44a+pjidZ9zB BhPFb0b4y887u/vC94pfG564NH5wMRXp3jZH8nvUH9kNM7U07XknXzley8csOXlT/r4i/9e2 e774XC7Sd118fE5a/g3uL30Pjq9abRfz7MSBSbwp9xN2hdl+Z75e5nX1ocGih1E9SizFGYmG WsxFxYkAod4AKa0CAAA= Archived-At: Cc: "hybi@ietf.org" , Barry Leiba Subject: Re: [hybi] I-D Action: draft-ietf-hybi-permessage-compression-28.txt X-BeenThere: hybi@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Server-Initiated HTTP List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Sep 2015 13:31:35 -0000 --_000_7730FEFFFA094278A8BFB3325E6C2EC1ericssoncom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable IMO it is ready for approval br Salvatore On 28 Aug 2015, at 06:30, Takeshi Yoshino > wrote: +salvatore explicitly Takeshi On Fri, Aug 28, 2015 at 4:43 AM, Barry Leiba > wrote: Document shepherd: Is version -28 ready for approval? Or are any other changes needed? Barry On Mon, Aug 24, 2015 at 7:28 AM, Takeshi Yoshino > wrote: > Fixed one editorial issue pointed out by Ben. > > Takeshi > > On Mon, Aug 24, 2015 at 8:25 PM, > wrote: >> >> >> A New Internet-Draft is available from the on-line Internet-Drafts >> directories. >> This draft is a work item of the BiDirectional or Server-Initiated HTTP >> Working Group of the IETF. >> >> Title : Compression Extensions for WebSocket >> Author : Takeshi Yoshino >> Filename : draft-ietf-hybi-permessage-compression-28.txt >> Pages : 32 >> Date : 2015-08-24 >> >> Abstract: >> This document defines a framework for creating WebSocket extensions >> that add compression functionality to the WebSocket Protocol. An >> extension based on this framework compresses the payload data portion >> of WebSocket data messages on a per-message basis using parameters >> negotiated during the opening handshake. This framework provides a >> general method for applying a compression algorithm to the contents >> of WebSocket messages. Each compression algorithm has to be defined >> in a document defining the extension by specifying parameter >> negotiation and payload transformation algorithm in detail. This >> document also specifies one specific compression extension using the >> DEFLATE algorithm. >> >> Please send feedback to the hybi@ietf.org maili= ng list. >> >> >> The IETF datatracker status page for this draft is: >> https://datatracker.ietf.org/doc/draft-ietf-hybi-permessage-compression/ >> >> There's also a htmlized version available at: >> https://tools.ietf.org/html/draft-ietf-hybi-permessage-compression-28 >> >> A diff from the previous version is available at: >> >> https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-hybi-permessage-compressi= on-28 >> >> >> Please note that it may take a couple of minutes from the time of >> submission >> until the htmlized version and diff are available at tools.ietf.org. >> >> Internet-Drafts are also available by anonymous FTP at: >> ftp://ftp.ietf.org/internet-drafts/ >> >> _______________________________________________ >> 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 > --_000_7730FEFFFA094278A8BFB3325E6C2EC1ericssoncom_ Content-Type: text/html; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable IMO it is ready for approval

br
Salvatore

On 28 Aug 2015, at 06:30, Takeshi Yoshino <tyoshino@google.com> wrote:
+salvatore explicitly

Takeshi

On Fri, Aug 28, 2015 at 4:43 AM, Barry Leiba <barryleiba@computer.org> wrote:
Document shepherd:
Is version -28 ready for approval?  Or are any other changes needed?
Barry

On Mon, Aug 24, 2015 at 7:28 AM, Takeshi Yoshino <tyoshino@google.com> wrote:
> Fixed one editorial issue pointed out by Ben.
>
> Takeshi
>
> On Mon, Aug 24, 2015 at 8:25 PM, <internet-drafts@ietf.org> wrote:
>>
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts=
>> directories.
>>  This draft is a work item of the BiDirectional or Server-Ini= tiated HTTP
>> Working Group of the IETF.
>>
>>         Title        =    : Compression Extensions for WebSocket
>>         Author       =   : Takeshi Yoshino
>>         Filename      &nbs= p; : draft-ietf-hybi-permessage-compression-28.txt
>>         Pages        =    : 32
>>         Date        &= nbsp;   : 2015-08-24
>>
>> Abstract:
>>    This document defines a framework for creating WebSoc= ket extensions
>>    that add compression functionality to the WebSocket P= rotocol.  An
>>    extension based on this framework compresses the payl= oad data portion
>>    of WebSocket data messages on a per-message basis usi= ng parameters
>>    negotiated during the opening handshake.  This f= ramework provides a
>>    general method for applying a compression algorithm t= o the contents
>>    of WebSocket messages.  Each compression algorit= hm has to be defined
>>    in a document defining the extension by specifying pa= rameter
>>    negotiation and payload transformation algorithm in d= etail.  This
>>    document also specifies one specific compression exte= nsion using the
>>    DEFLATE algorithm.
>>
>>    Please send feedback to the hybi@ietf.org mailing list.
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-hybi-permessage-compression/
>>
>> There's also a htmlized version available at:
>>
https://tools.ietf.org/html/draft-ietf-hybi-permessage-compression-28 >>
>> A diff from the previous version is available at:
>>
>> https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-hybi-permessage-compression-= 28
>>
>>
>> Please note that it may take a couple of minutes from the time of<= br class=3D""> >> submission
>> until the htmlized version and diff are available at tools.ietf.org.
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> _______________________________________________
>> 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
>


--_000_7730FEFFFA094278A8BFB3325E6C2EC1ericssoncom_-- From nobody Tue Sep 1 07:13:36 2015 Return-Path: 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 642FE1A873B for ; Tue, 1 Sep 2015 07:13:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.278 X-Spam-Level: X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 fkUs2MQ_JwkU for ; Tue, 1 Sep 2015 07:13:29 -0700 (PDT) Received: from mail-ig0-x244.google.com (mail-ig0-x244.google.com [IPv6:2607:f8b0:4001:c05::244]) (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 3C1381B2BF3 for ; Tue, 1 Sep 2015 07:13:29 -0700 (PDT) Received: by igbbp9 with SMTP id bp9so199748igb.0 for ; Tue, 01 Sep 2015 07:13:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=oqWFF2HQpoAm+yzeMDmZlNKGXfN5/zcU7sPNEjRp5ns=; b=bn+/GBTp2lsQ0e9ZFWa8NsImwHbxj3qODC6yLUVZgLRUuQVXFrk4nwBYaZuX0J1zJy nLhBV3b58h3Zy75ynok0cykC7BHhPiuY8DipGDQlCdjLrQD9AeqE+edimVOWVKAbi/SN s+1ipl6ye+HDVqTvJzi8b8qIyM0YrmW8jFxmDIGoHMRzU3Ns6uHGNhHG+0PSaa+j0AYW 2Vzvuj1xRcX9RcMMxncR/dGmDJazvUIDwhIHoTfUp7JnCu4C1XbLFR/9bfgBVEhHXfRE 7tZHGuzog46wvfqU2IkT++r9iwSZrTrNI2yuJTYg4gWdvQ6GE6XjqKRu5kBAwS1X8gcO 5otw== MIME-Version: 1.0 X-Received: by 10.50.50.134 with SMTP id c6mr2573419igo.33.1441116806674; Tue, 01 Sep 2015 07:13:26 -0700 (PDT) Sender: barryleiba.mailing.lists@gmail.com Received: by 10.107.140.23 with HTTP; Tue, 1 Sep 2015 07:13:26 -0700 (PDT) In-Reply-To: <7730FEFF-FA09-4278-A8BF-B3325E6C2EC1@ericsson.com> References: <20150824112514.18998.33071.idtracker@ietfa.amsl.com> <7730FEFF-FA09-4278-A8BF-B3325E6C2EC1@ericsson.com> Date: Tue, 1 Sep 2015 10:13:26 -0400 X-Google-Sender-Auth: QohasxqDfCSt-w1Yg6Lz-eKNjnY Message-ID: From: Barry Leiba To: Salvatore Loreto Content-Type: text/plain; charset=UTF-8 Archived-At: Cc: "hybi@ietf.org" Subject: Re: [hybi] I-D Action: draft-ietf-hybi-permessage-compression-28.txt X-BeenThere: hybi@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Server-Initiated HTTP List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Sep 2015 14:13:30 -0000 > IMO it is ready for approval Great; I've checked it too, and I agree. I've approved it, and you should see the announcement soon. The working group will remain open until the RFC is published, after which I'll close the working group, but leave the mailing list open for continued related discussion (such as Anne's recent question). Barry From nobody Tue Sep 1 15:07:03 2015 Return-Path: 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 D21D11B4A81; Tue, 1 Sep 2015 15:07:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.9 X-Spam-Level: X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] 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 9IJ5AtNeQmCL; Tue, 1 Sep 2015 15:06:59 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 02F6A1B4A83; Tue, 1 Sep 2015 15:06:50 -0700 (PDT) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: The IESG To: "IETF-Announce" X-Test-IDTracker: no X-IETF-IDTracker: 6.4.1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20150901220650.2333.20235.idtracker@ietfa.amsl.com> Date: Tue, 01 Sep 2015 15:06:50 -0700 Archived-At: Cc: hybi chair , hybi mailing list , RFC Editor Subject: [hybi] Protocol Action: 'Compression Extensions for WebSocket' to Proposed Standard (draft-ietf-hybi-permessage-compression-28.txt) X-BeenThere: hybi@ietf.org X-Mailman-Version: 2.1.15 List-Id: Server-Initiated HTTP List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Sep 2015 22:07:01 -0000 The IESG has approved the following document: - 'Compression Extensions for WebSocket' (draft-ietf-hybi-permessage-compression-28.txt) as Proposed Standard This document is the product of the BiDirectional or Server-Initiated HTTP Working Group. The IESG contact persons are Ben Campbell, Barry Leiba and Alissa Cooper. A URL of this Internet Draft is: https://datatracker.ietf.org/doc/draft-ietf-hybi-permessage-compression/ Technical Summary This document specifies a framework for creating WebSocket extensions that add compression functionality to the WebSocket Protocol. Extensions based on this framework compress the payload of non-control WebSocket messages using a specified compression algorithm. One reserved bit RSV1 in the WebSocket frame header is allocated to control application of compression for each message. This document also specifies one specific compression extension using DEFLATE. Review and Consensus The compression extension has been discussed extensively within the HyBi group almost since the beginning of the WebSockets standardization process. Initially, the wg decided that in order to maintain progress on WebSockets, it would not work on extensions until the WebSocket spec was finished, so this waited for that to happen. The initial version of the compression spec was based on per-frame compression, but at IETF84 in Vancouver (and as confirmed on the mailing list), the HyBi WG decided to change from per-frame to per-message compression. There has not been any notable controversy about this document. Chrome supports the old per-frame deflate draft, and they plan to update it to the current proposal soon. pywebsocket supports permessage-compression-04, but needs some changes to extension parameter parsing to be compliant with -05. The Jetty web server also supports an earlier version of per-message compression. Personnel Salvatore Loreto is the document shepherd. Barry Leiba is the responsible Area Director. From nobody Sat Sep 5 10:25:25 2015 Return-Path: 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 7394E1B2DEB for ; Sat, 5 Sep 2015 10:25:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.622 X-Spam-Level: X-Spam-Status: No, score=0.622 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, 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 58ZqkVMWBorv for ; Sat, 5 Sep 2015 10:25:23 -0700 (PDT) Received: from homiemail-a14.g.dreamhost.com (homie.mail.dreamhost.com [208.97.132.208]) by ietfa.amsl.com (Postfix) with ESMTP id 641C71B2DD7 for ; Sat, 5 Sep 2015 10:25:23 -0700 (PDT) Received: from homiemail-a14.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a14.g.dreamhost.com (Postfix) with ESMTP id DEC47392082 for ; Sat, 5 Sep 2015 10:25:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=annevk.nl; h=mime-version :date:message-id:subject:from:to:content-type; s=annevk.nl; bh=k 96WE88UT4tVJ7hlAA64cQFq26s=; b=gCcATZrUVXQVncMqPBX8QKp3/PNUKXZz9 0B34LnCeIcxktT7s5cZdmqoaIsdqg4Y9R6RNgzbY1R5JwoYn2TfNtcZG1V6zBe9/ aOjYX+dEg+Fhcxrld+54gx7C9zuDPTinIgidF/FJzchUPfjmYp0Mp/0QKhAzTQLn M/kuXy+mc0= Received: from mail-yk0-f175.google.com (mail-yk0-f175.google.com [209.85.160.175]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: annevk@annevk.nl) by homiemail-a14.g.dreamhost.com (Postfix) with ESMTPSA id C61A0392081 for ; Sat, 5 Sep 2015 10:25:22 -0700 (PDT) Received: by ykek143 with SMTP id k143so48044773yke.2 for ; Sat, 05 Sep 2015 10:25:22 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.129.33.10 with SMTP id h10mr11570533ywh.47.1441473922197; Sat, 05 Sep 2015 10:25:22 -0700 (PDT) Received: by 10.37.50.2 with HTTP; Sat, 5 Sep 2015 10:25:22 -0700 (PDT) Date: Sat, 5 Sep 2015 19:25:22 +0200 Message-ID: From: Anne van Kesteren To: "hybi@ietf.org" Content-Type: text/plain; charset=UTF-8 Archived-At: Subject: [hybi] "Establish a WebSocket Connection" does not allow for cookies X-BeenThere: hybi@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Server-Initiated HTTP List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Sep 2015 17:25:24 -0000 After the tenth protocol draft this algorithm broke a hook the API standard was using and those authoring the WebSocket API were never notified. See https://www.w3.org/Bugs/Public/show_bug.cgi?id=27869 for details. How do you suggest this gets fixed? -- https://annevankesteren.nl/ From nobody Sat Sep 5 10:27:59 2015 Return-Path: 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 CC6721B2E47 for ; Sat, 5 Sep 2015 10:27:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.078 X-Spam-Level: X-Spam-Status: No, score=-2.078 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, 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 g_h8PlJYKl9U for ; Sat, 5 Sep 2015 10:27:56 -0700 (PDT) Received: from homiemail-a1.g.dreamhost.com (homie.mail.dreamhost.com [208.97.132.208]) by ietfa.amsl.com (Postfix) with ESMTP id 9FAA01B2E3F for ; Sat, 5 Sep 2015 10:27:56 -0700 (PDT) Received: from homiemail-a1.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a1.g.dreamhost.com (Postfix) with ESMTP id 5C06834806C for ; Sat, 5 Sep 2015 10:27:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=annevk.nl; h=mime-version :date:message-id:subject:from:to:content-type; s=annevk.nl; bh=C +70DDHi6wKVf2Jc6Bna7+pnCw4=; b=PQevjmJK4n16O37xt+cYd6JRpzCvliLu/ 6QimvmLPawYNF+hH2BEV+MDOs0RhDFkD1zhbpIpMGFmdgSqiqz2CLOzsGowlimXZ jHFtcuWinOwxEv/VWq8zSMBFUfqIV+2g9pMnOMHX1FiUs4srvC2FA6qS6INdmG42 PXw5kQ6KD8= Received: from mail-yk0-f170.google.com (mail-yk0-f170.google.com [209.85.160.170]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: annevk@annevk.nl) by homiemail-a1.g.dreamhost.com (Postfix) with ESMTPSA id 4D12D348062 for ; Sat, 5 Sep 2015 10:27:56 -0700 (PDT) Received: by ykek143 with SMTP id k143so48072994yke.2 for ; Sat, 05 Sep 2015 10:27:55 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.129.92.8 with SMTP id q8mr11228426ywb.163.1441474075757; Sat, 05 Sep 2015 10:27:55 -0700 (PDT) Received: by 10.37.50.2 with HTTP; Sat, 5 Sep 2015 10:27:55 -0700 (PDT) Date: Sat, 5 Sep 2015 19:27:55 +0200 Message-ID: From: Anne van Kesteren To: "hybi@ietf.org" Content-Type: text/plain; charset=UTF-8 Archived-At: Subject: [hybi] WebSocket and HSTS X-BeenThere: hybi@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Server-Initiated HTTP List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Sep 2015 17:27:57 -0000 I was wondering if you were interested in updating the protocol to account for HSTS or whether I should patch that in the API standard somehow. See https://www.w3.org/Bugs/Public/show_bug.cgi?id=27554 for details. -- https://annevankesteren.nl/ From nobody Sat Sep 5 11:09:09 2015 Return-Path: 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 A6F0E1B3858 for ; Sat, 5 Sep 2015 11:09:07 -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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 O0rmaj_Nqj5g for ; Sat, 5 Sep 2015 11:09:06 -0700 (PDT) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A48A21B3850 for ; Sat, 5 Sep 2015 11:09:05 -0700 (PDT) Received: from [192.168.2.177] ([84.187.35.114]) by mail.gmx.com (mrgmx101) with ESMTPSA (Nemesis) id 0M7kwW-1Ym77W2lo8-00vRXv; Sat, 05 Sep 2015 20:09:02 +0200 To: Anne van Kesteren , "hybi@ietf.org" References: From: Julian Reschke Message-ID: <55EB2FBF.4080602@gmx.de> Date: Sat, 5 Sep 2015 20:09:03 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:ePTdhHN/4+4cSMYiHV0WoLPqxnT9u9nfwECyVjJomO66jnCj8v6 nPqO7gC4KVFUQBJrJM7ThWU87NWxHMwmzFXlSYKj0NQRRLY51YEjQG+v3l4KtJRlPDPXhZy STu8JH+tHRM11jp1wOFyhI2D2jg+09bfDIjfEs7cyrDIUyue+ejX7u+NA5Rw4C2Y0RyEx7V 3ptMB8pNO60/cJVw81H9w== X-UI-Out-Filterresults: notjunk:1;V01:K0:stMhcMbFO9U=:hlwX+591ogykYw1d1ugy+V fSoUXzfjsnTw69DDYPmQiTNRPjj2D1J0HqkgFG7dM4pvW8GjDsVPUqpGglLKlwQ9TBMhWgrX5 oQFy60hU0nw9+MCYar6G+e6ZyVTQZdw4Jm2YzSVe7td4VOeqOC2e1OZxZeEw2+jpm2i8iT7Cn i653J9nbHkifn7a7QyrIPYILpbHPM9cZ7mj/8Kf1nUZYb02oKpm8QId14vSTEVfO+3kzPpVeR 7HZdTGRTim4j25Sou14xsZ0PN1OQhQni+nG+nB84832UdvnYEJYwMZ354YuhJxzdqFpTSG9f9 z69OeH5WmGJtGuEQqYSkVmHn97sWPVGM/dgqfGBSXuFzHtKQlOE1zJC8MNGDUC3V0uf99Basi Yx/ME8hEofx+W2aNsn1jBINFzrIp0V8Ar+aDtliYzGca5KnsQIJhtpN0DVrEd2cgyxeQA5hiq TuIN7CnKAWmQY5QH8Xd5Zp5SkV9hsucmZy9HAf+eIZHG34iKUXmfMJdSi4dpHWHvnZOADC4P4 17nX+b7zIyOlHNkAI9diD/WnLZrB+eGKPq9HuVO8v3md1jmyO5MKUYA8dpMWW5O1JR8mefhlM P8QxJbb3KGQgXbc466XGUCInEjpi9ogvZJ1hZjV0hLKIMnwgxlPfOIcqka1FlbTtaE5qRR50k uuQRJrLdMbVQYsvzX88sM8OJyMK/TuvX3rnCTQqyKx19zOgWsnQ3wV7ovko4ddXgDOgEDUNJd WIWCKjYJqbu+oo+D8F/Axhnikhv3k5DBM8WC8Q== Archived-At: Subject: Re: [hybi] "Establish a WebSocket Connection" does not allow for cookies X-BeenThere: hybi@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Server-Initiated HTTP List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Sep 2015 18:09:07 -0000 On 2015-09-05 19:25, Anne van Kesteren wrote: > After the tenth protocol draft this algorithm broke a hook the API > standard was using and those authoring the WebSocket API were never > notified. > > See https://www.w3.org/Bugs/Public/show_bug.cgi?id=27869 for details. > > How do you suggest this gets fixed? The subject line is misleading. , item 12 in the second list is: > 12. The request MAY include any other header fields, for example, > cookies [RFC6265] and/or authentication-related header fields > such as the |Authorization| header field [RFC2616], which are > processed according to documents that define them. Best regards, Julian From nobody Sun Sep 6 08:12:30 2015 Return-Path: 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 E97061B30AD for ; Sun, 6 Sep 2015 08:12:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.622 X-Spam-Level: X-Spam-Status: No, score=0.622 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, 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 WDcdVmDqZI7T for ; Sun, 6 Sep 2015 08:12:29 -0700 (PDT) Received: from homiemail-a7.g.dreamhost.com (homie.mail.dreamhost.com [208.97.132.208]) by ietfa.amsl.com (Postfix) with ESMTP id 036631B2A22 for ; Sun, 6 Sep 2015 08:12:28 -0700 (PDT) Received: from homiemail-a7.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a7.g.dreamhost.com (Postfix) with ESMTP id 9E98E25C072 for ; Sun, 6 Sep 2015 08:12:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=annevk.nl; h=mime-version :in-reply-to:references:date:message-id:subject:from:to:cc: content-type; s=annevk.nl; bh=uelxuatknZhQeYo8BMJYEJeZIGk=; b=MB 9XSrTuBSG63RlfY7gWesLub36AkDmSTMmpq+dZhioJtlh9rBfeWoIqWG02wy8+NX +B4wBSp5GupL7iWNaqhtYAzTE+YYIayHuj78ieicuLCiqrKVraV0Hws4RShJ8ZvO CVcsIQEjbXUUit+LNxoG0PMmG0PeLI309ErbnkJSc= Received: from mail-yk0-f174.google.com (mail-yk0-f174.google.com [209.85.160.174]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: annevk@annevk.nl) by homiemail-a7.g.dreamhost.com (Postfix) with ESMTPSA id 8552225C06D for ; Sun, 6 Sep 2015 08:12:27 -0700 (PDT) Received: by ykcf206 with SMTP id f206so60989743ykc.3 for ; Sun, 06 Sep 2015 08:12:26 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.13.211.133 with SMTP id v127mr15742250ywd.90.1441552346720; Sun, 06 Sep 2015 08:12:26 -0700 (PDT) Received: by 10.37.50.2 with HTTP; Sun, 6 Sep 2015 08:12:26 -0700 (PDT) In-Reply-To: <55EB2FBF.4080602@gmx.de> References: <55EB2FBF.4080602@gmx.de> Date: Sun, 6 Sep 2015 17:12:26 +0200 Message-ID: From: Anne van Kesteren To: Julian Reschke Content-Type: text/plain; charset=UTF-8 Archived-At: Cc: "hybi@ietf.org" Subject: Re: [hybi] "Establish a WebSocket Connection" does not allow for cookies X-BeenThere: hybi@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Server-Initiated HTTP List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Sep 2015 15:12:30 -0000 On Sat, Sep 5, 2015 at 8:09 PM, Julian Reschke wrote: > On 2015-09-05 19:25, Anne van Kesteren wrote: >> After the tenth protocol draft this algorithm broke a hook the API >> standard was using and those authoring the WebSocket API were never >> notified. >> >> See https://www.w3.org/Bugs/Public/show_bug.cgi?id=27869 for details. >> >> How do you suggest this gets fixed? > > The subject line is misleading. It's the name of the algorithm defined in the RFC that takes a set number of arguments of which headers and/or cookies are not an acceptable argument. > , item 12 in the second > list is: > >> 12. The request MAY include any other header fields, for example, >> cookies [RFC6265] and/or authentication-related header fields >> such as the |Authorization| header field [RFC2616], which are >> processed according to documents that define them. This step cannot be influenced from the API. The "request" is constructed by this algorithm and the influence the API has over it is carefully defined. -- https://annevankesteren.nl/ From nobody Sun Sep 13 13:44:26 2015 Return-Path: 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 A1A891B2AAA for ; Sun, 13 Sep 2015 13:44:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.069 X-Spam-Level: X-Spam-Status: No, score=0.069 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_SORBS_WEB=0.77] 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 Au6PGl2bg7dL for ; Sun, 13 Sep 2015 13:44:23 -0700 (PDT) Received: from EXHUB020-3.exch020.serverdata.net (exhub020-3.exch020.serverdata.net [206.225.164.30]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1430D1A0366 for ; Sun, 13 Sep 2015 13:44:23 -0700 (PDT) Received: from [192.168.43.73] (89.204.130.38) by smtpx20.serverdata.net (206.225.164.35) with Microsoft SMTP Server (TLS) id 8.3.377.0; Sun, 13 Sep 2015 13:44:21 -0700 To: Barry Leiba , Salvatore Loreto References: <20150824112514.18998.33071.idtracker@ietfa.amsl.com> <7730FEFF-FA09-4278-A8BF-B3325E6C2EC1@ericsson.com> From: Tobias Oberstein Message-ID: <55F5E021.2000803@tavendo.de> Date: Sun, 13 Sep 2015 22:44:17 +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: Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit Archived-At: Cc: "hybi@ietf.org" Subject: Re: [hybi] I-D Action: draft-ietf-hybi-permessage-compression-28.txt X-BeenThere: hybi@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Server-Initiated HTTP List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Sep 2015 20:44:24 -0000 > Great; I've checked it too, and I agree. I've approved it, and you > should see the announcement soon. Awesome! The WebSocket compression extension is of great practical value. > > The working group will remain open until the RFC is published, after > which I'll close the working group, but leave the mailing list open Regarding the closing of the working group, I would like to ask what is required to recharter the WG to work on a specific WebSocket subprotocol. The current WG charter has this to say: """ The working group will also serve as a discussion venue for subprotocols. However, no subprotocol is currently chartered as a deliverable, and the WG must be rechartered to work on any subprotocols. """ http://datatracker.ietf.org/doc/charter-ietf-hybi/ The subprotocol I would like to start working on is: "The Web Application Messaging Protocol (WAMP)" http://wamp.ws/ https://github.com/tavendo/WAMP/ http://www.iana.org/assignments/websocket/websocket.xml#subprotocol-name WAMP was the 3rd WebSocket subprotocol officially registered at IANA, has gone through 3+ years of development, has nearly two dozen independent and interoparable implementations, and an active community. I have asked on the WAMP implementors mailing list if there is interest in working on a RFC for WAMP, and multiple responses indicate that there is indeed interest: https://groups.google.com/forum/#!topic/wampws/LlKjMF3ZJf8 I am original author of WAMP, and have been active during the development of WebSocket and the WebSocket compression extension on the Hybi working group. I also created and maintain the Autobahn WebSocket testsuite - an automated testsuite for WS used by most implementors. http://autobahn.ws/testsuite/ Apart from that I wrote a couple of WebSocket implementations in different languages. However, I never wrote an RFC nor do I know a lot about IETF processes and such. Hence my naive question: what's required to start working on WAMP within the context of this WG? Cheers, /Tobias From nobody Mon Sep 14 02:05:57 2015 Return-Path: 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 C92831A0102 for ; Mon, 14 Sep 2015 02:05:55 -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 DFNeKzL-U-2I for ; Mon, 14 Sep 2015 02:05:54 -0700 (PDT) Received: from mail-oi0-x235.google.com (mail-oi0-x235.google.com [IPv6:2607:f8b0:4003:c06::235]) (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 D10191B33A2 for ; Mon, 14 Sep 2015 02:05:54 -0700 (PDT) Received: by oibi136 with SMTP id i136so73335587oib.3 for ; Mon, 14 Sep 2015 02:05:54 -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=GV+ZegUabr0pTTmI83iELCkYolzDe8Hq4vJLBPEUCZU=; b=GXccymQzE46vBjraNund6tVAAscMk2ih/j/eVGTJz8eRShE8rBx827340z9m1X4XBH P1BEy0Fp76JIu8QRPmvcSLL4PbeX/bGW4NGaZFxAIz6Xi5s70Q7z+89r9kwieK74+LV/ aaadZzt2Mkl4urDtd7Qu8Ul4XKImr3FT1d7ECAh9Etu+3Vnq4HGjUV89IHwMP9cqKzPX CynkuKshP1Z4IkgRGc/3vj+WtL/4HMvJRUlhazdyj3/hHxUFyEpFycMqEDJXFfG2lhF7 8vLny7j23aUQMfHhoiuWPKxM5fpuSKiyYsMA/7Pw7ufgLntxc3PA1RqBdqm+HQjtv3fW LHSQ== 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=GV+ZegUabr0pTTmI83iELCkYolzDe8Hq4vJLBPEUCZU=; b=d9M7FWocpVnsaB+m8nXTv3P2UWcAJbUid6GJcVcCTkwDdveV+5Ztuno/vkNXNmlvin CbIXvLreOF3bCpqxQgPgqbaIJDzkZFBTd0BdUnpFvlDCz2W/lL+pasde8zgMkYm12tvo wqE9fOR75GNUMDvFx0qj7tJWMEkf8lBq2iFoxYQvW5ilQyeAbJ5gs+IBbvNGBwv2z3zF Id+qWSztWrST1P0P7E2QWAN07J7W5U6407fAPuBgV4W5wpYTpkuzA4q4FbmDOuMGqxUD +pdaaxZjEKh8GEboESyUX1IkH7SLHwyHvCsopIWLmiIfKdvFXCXTU3qWu11TFMx6Lkfd nvaQ== X-Gm-Message-State: ALoCoQmNNSnq+w9ggOp8hmnkiljagNLrIoEATmmWpMuA2pFoOeUOxT5SzHeV8oQjirQoNVLqdSYB X-Received: by 10.202.105.74 with SMTP id e71mr9795742oic.133.1442221554232; Mon, 14 Sep 2015 02:05:54 -0700 (PDT) MIME-Version: 1.0 Received: by 10.202.60.4 with HTTP; Mon, 14 Sep 2015 02:05:34 -0700 (PDT) In-Reply-To: References: <20150824112514.18998.33071.idtracker@ietfa.amsl.com> <7730FEFF-FA09-4278-A8BF-B3325E6C2EC1@ericsson.com> From: Takeshi Yoshino Date: Mon, 14 Sep 2015 18:05:34 +0900 Message-ID: To: Barry Leiba Content-Type: multipart/alternative; boundary=001a11408c786db917051fb15fd0 Archived-At: Cc: "hybi@ietf.org" Subject: Re: [hybi] I-D Action: draft-ietf-hybi-permessage-compression-28.txt X-BeenThere: hybi@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Server-Initiated HTTP List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Sep 2015 09:05:56 -0000 --001a11408c786db917051fb15fd0 Content-Type: text/plain; charset=UTF-8 Thanks so much, Sal, Barry for your support. On Tue, Sep 1, 2015 at 11:13 PM, Barry Leiba wrote: > > IMO it is ready for approval > > Great; I've checked it too, and I agree. I've approved it, and you > should see the announcement soon. > > The working group will remain open until the RFC is published, after > which I'll close the working group, but leave the mailing list open > for continued related discussion (such as Anne's recent question). > Great! > > Barry > --001a11408c786db917051fb15fd0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Thanks so much, Sal, Barry for your support.


On Tue, Sep 1, 2015 at 11:13 PM, Barry Leiba <barryleiba@compu= ter.org> wrote:
> IMO it is ready for approval

Great; I've checked it too, and I agree.=C2=A0 I've approved= it, and you
should see the announcement soon.

The working group will remain open until the RFC is published, after
which I'll close the working group, but leave the mailing list open
for continued related discussion (such as Anne's recent question).
<= /blockquote>

Great!
=C2=A0

Barry

--001a11408c786db917051fb15fd0-- From nobody Mon Sep 14 02:11:39 2015 Return-Path: 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 341851B3C17 for ; Mon, 14 Sep 2015 02:11:38 -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 q3WKL7Vq041y for ; Mon, 14 Sep 2015 02:11:36 -0700 (PDT) Received: from mail-oi0-x22e.google.com (mail-oi0-x22e.google.com [IPv6:2607:f8b0:4003:c06::22e]) (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 490411B3CFF for ; Mon, 14 Sep 2015 02:11:36 -0700 (PDT) Received: by oiev17 with SMTP id v17so72984835oie.1 for ; Mon, 14 Sep 2015 02:11:35 -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=9f8JJpTlNN1aWBon6CUxnHhHE5HzztpLKW06ky0aJr4=; b=Yx/Q1SCnmiFCqjupgJyi8xEp+LBdFy0BKYn1fW8gWCjiCNy8iWS/dtufWGxX6O+/0U o7tNDd7szsKs93zJW6Sox6wbsC09rOr3wq+y7D7BgJKwO21jFFV+l/EQ5AgctuMyIjcc 8e2TzmI9CTwPWOZ4YdYAXG7hgbIYhNzi8FaIijy8irAupa+ItDzX1AyDXXih051wQdD/ Vo2uadHKpDSOKD9CwDs4oul9OvFxOAR4uZqw3ZI2k3mrpbKUds7FjYFTXdaWmG67cEVp AvcCWnLS+IdXxBDNlVSFP49fhAhVrM3aNa3dt/xSEYftU/w1WY7lEzd3Ys/scft3RS0P lRVA== 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=9f8JJpTlNN1aWBon6CUxnHhHE5HzztpLKW06ky0aJr4=; b=k0KAmKlKsxR9tlldjCVWOa9V7Ih+YLtAS6+kMoaxSNEAavFFkIUaWp6/r0K+0MVkxX mBOL5MuiXgD+dlpnjZGDsF6xVFCOSZOBVzGlwyq7GeQ+hoV8anr2XtTocNClmIKf2X9s 6aIZX24RZM9ObyD2WA4pi8R0zTVRz7mT19qZVvSqqizVglTir6qQU6rLqV8WucQzRY35 OiGnW23kK8Cg8Mry1bTXO4OSMJy4p0rJzDCKHLsYC64h0h7RqxfUuhQVlrCF8kHptxp/ 3nsdabeg9VHgujKLubpkuATO7+ZyteybVShLwUcf5Avd5nBxO6k4bZVfgQwixDkjXdSY sXaQ== X-Gm-Message-State: ALoCoQk5aE+i/CTR6xeGAyfT8JKh4BORHg0oxYjAoqa4pjKk2/BKAul3OvT5b7mljbgoEySVjJIz X-Received: by 10.202.232.12 with SMTP id f12mr9077704oih.122.1442221895574; Mon, 14 Sep 2015 02:11:35 -0700 (PDT) MIME-Version: 1.0 Received: by 10.202.60.4 with HTTP; Mon, 14 Sep 2015 02:11:15 -0700 (PDT) In-Reply-To: <55F5E021.2000803@tavendo.de> References: <20150824112514.18998.33071.idtracker@ietfa.amsl.com> <7730FEFF-FA09-4278-A8BF-B3325E6C2EC1@ericsson.com> <55F5E021.2000803@tavendo.de> From: Takeshi Yoshino Date: Mon, 14 Sep 2015 18:11:15 +0900 Message-ID: To: Tobias Oberstein Content-Type: multipart/alternative; boundary=001a11408b6ec62034051fb17300 Archived-At: Cc: "hybi@ietf.org" , Barry Leiba Subject: Re: [hybi] I-D Action: draft-ietf-hybi-permessage-compression-28.txt X-BeenThere: hybi@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Server-Initiated HTTP List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Sep 2015 09:11:38 -0000 --001a11408b6ec62034051fb17300 Content-Type: text/plain; charset=UTF-8 On Mon, Sep 14, 2015 at 5:44 AM, Tobias Oberstein < tobias.oberstein@tavendo.de> wrote: > Great; I've checked it too, and I agree. I've approved it, and you >> should see the announcement soon. >> > > Awesome! The WebSocket compression extension is of great practical value. Thank you, Tobias for your continued contribution including discussion and building the reliable and comprehensive test suites. > > > >> The working group will remain open until the RFC is published, after >> which I'll close the working group, but leave the mailing list open >> > > Regarding the closing of the working group, I would like to ask what is > required to recharter the WG to work on a specific WebSocket subprotocol. > I also wonder what we'll lose and what we won't (in addition to the mailing list) after WG close. I was worried that we might lose the mailing list too. I guess at least we'll be unable to raise I-Ds as WG items while the WG is closed. > > The current WG charter has this to say: > > """ > The working group will also serve as a discussion venue for > subprotocols. However, no subprotocol is currently chartered as a > deliverable, and the WG must be rechartered to work on any > subprotocols. > """ http://datatracker.ietf.org/doc/charter-ietf-hybi/ > > The subprotocol I would like to start working on is: > > "The Web Application Messaging Protocol (WAMP)" > > http://wamp.ws/ > https://github.com/tavendo/WAMP/ > http://www.iana.org/assignments/websocket/websocket.xml#subprotocol-name > > WAMP was the 3rd WebSocket subprotocol officially registered at IANA, has > gone through 3+ years of development, has nearly two dozen independent and > interoparable implementations, and an active community. > > I have asked on the WAMP implementors mailing list if there is interest in > working on a RFC for WAMP, and multiple responses indicate that there is > indeed interest: > > https://groups.google.com/forum/#!topic/wampws/LlKjMF3ZJf8 > > I am original author of WAMP, and have been active during the development > of WebSocket and the WebSocket compression extension on the Hybi working > group. > > I also created and maintain the Autobahn WebSocket testsuite - an > automated testsuite for WS used by most implementors. > > http://autobahn.ws/testsuite/ > > Apart from that I wrote a couple of WebSocket implementations in different > languages. > > However, I never wrote an RFC nor do I know a lot about IETF processes and > such. > > Hence my naive question: what's required to start working on WAMP within > the context of this WG? > > Cheers, > /Tobias > > > > > _______________________________________________ > hybi mailing list > hybi@ietf.org > https://www.ietf.org/mailman/listinfo/hybi > --001a11408b6ec62034051fb17300 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On M= on, Sep 14, 2015 at 5:44 AM, Tobias Oberstein <tobias.oberstein@= tavendo.de> wrote:
Great; I've checked it too, and I agree.=C2=A0 I've approved it, an= d you
should see the announcement soon.

Awesome! The WebSocket compression extension is of great practical value.

Thank you, Tobias for your continued contrib= ution including discussion and building the reliable and comprehensive test= suites.
=C2=A0



The working group will remain open until the RFC is published, after
which I'll close the working group, but leave the mailing list open

Regarding the closing of the working group, I would like to ask what is req= uired to recharter the WG to work on a specific WebSocket subprotocol.
<= /blockquote>

I also wonder what we'll lose and what = we won't (in addition to the mailing list) after WG close. I was worrie= d that we might lose the mailing list too.

I guess= at least we'll be unable to raise I-Ds as WG items while the WG is clo= sed.
=C2=A0

The current WG charter has this to say:

"""
The working group will also serve as a discussion venue for
subprotocols.=C2=A0 However, no subprotocol is currently chartered as a
deliverable, and the WG must be rechartered to work on any
subprotocols.
""" http://datatracker.ietf.org/doc= /charter-ietf-hybi/

The subprotocol I would like to start working on is:

"The Web Application Messaging Protocol (WAMP)"

http://wam= p.ws/
https://github.com/tavendo/WAMP/
http://www.iana.org/assignme= nts/websocket/websocket.xml#subprotocol-name

WAMP was the 3rd WebSocket subprotocol officially registered at IANA, has g= one through 3+ years of development, has nearly two dozen independent and i= nteroparable implementations, and an active community.

I have asked on the WAMP implementors mailing list if there is interest in = working on a RFC for WAMP, and multiple responses indicate that there is in= deed interest:

https://groups.google.com/forum/#!topic/w= ampws/LlKjMF3ZJf8

I am original author of WAMP, and have been active during the development o= f WebSocket and the WebSocket compression extension on the Hybi working gro= up.

I also created and maintain the Autobahn WebSocket testsuite - an automated= testsuite for WS used by most implementors.

http://autobahn.ws/testsuite/

Apart from that I wrote a couple of WebSocket implementations in different = languages.

However, I never wrote an RFC nor do I know a lot about IETF processes and = such.

Hence my naive question: what's required to start working on WAMP withi= n the context of this WG?

Cheers,
/Tobias




_______________________________________________
hybi mailing list
hybi@ietf.org
https://www.ietf.org/mailman/listinfo/hybi

--001a11408b6ec62034051fb17300-- From nobody Mon Sep 14 03:44:35 2015 Return-Path: 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 D49571B5787 for ; Mon, 14 Sep 2015 03:44:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.2 X-Spam-Level: X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] 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 rSgFNhX5-aim for ; Mon, 14 Sep 2015 03:44:30 -0700 (PDT) Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AFCE71B5743 for ; Mon, 14 Sep 2015 03:44:29 -0700 (PDT) X-AuditID: c1b4fb3a-f79136d0000071e2-92-55f6a50b129d Received: from ESESSHC014.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 12.BB.29154.B05A6F55; Mon, 14 Sep 2015 12:44:27 +0200 (CEST) Received: from ESESSMB108.ericsson.se ([169.254.8.78]) by ESESSHC014.ericsson.se ([153.88.183.60]) with mapi id 14.03.0248.002; Mon, 14 Sep 2015 12:44:26 +0200 From: Salvatore Loreto To: Takeshi Yoshino , Tobias Oberstein Thread-Topic: [hybi] I-D Action: draft-ietf-hybi-permessage-compression-28.txt Thread-Index: AQHQ3l+S/EFgCf4yEkytb4X1k3hZOJ4a4dAAgAVBVICAAJM6AIAG4FkAgBN2fbyAAK8jgIAAOvtg Date: Mon, 14 Sep 2015 10:44:26 +0000 Message-ID: <2B9B48179856DC4FA00C93C79EB7E64A0E950202@ESESSMB108.ericsson.se> References: <20150824112514.18998.33071.idtracker@ietfa.amsl.com> <7730FEFF-FA09-4278-A8BF-B3325E6C2EC1@ericsson.com> <55F5E021.2000803@tavendo.de> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [153.88.183.17] Content-Type: multipart/alternative; boundary="_000_2B9B48179856DC4FA00C93C79EB7E64A0E950202ESESSMB108erics_" MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprFIsWRmVeSWpSXmKPExsUyM+JvjS730m+hBgcb5S0OLb7EavH+5TYm i3mLelgstr06zOrA4tGyqpfZY8GmUo8lS34yeVyZOoElgCWKyyYlNSezLLVI3y6BK2PFiiWM BU/aGCv2PellamCc0szYxcjJISFgIrHgcCeULSZx4d56ti5GLg4hgaOMEudutzBDOIsZJdYe bWMDqWITMJN4/nALM4gtIhAtsX9HHyuIzSzgJTHp+kYmEFtYwFfi66EGqJoAiQvXr7FB2FES U2+eAKthEVCV2DbzD1gNL1D9xF9dTBDLfjFL7Hq/EyzBKRAosfLQLLDzGIHO+35qDRPEMnGJ W0/mM0GcLSCxZM95ZghbVOLl439AB3EA2YoSy/vlIMrzJea8W8wIsUtQ4uTMJywTGEVnIZk0 C0nZLCRls4AmMQtoSqzfpQ9RoigxpfshO4StIdE6Zy47svgCRvZVjKLFqcXFuelGRnqpRZnJ xcX5eXp5qSWbGIGReXDLb6sdjAefOx5iFOBgVOLhffDxa6gQa2JZcWXuIUZpDhYlcd5mpgeh QgLpiSWp2ampBalF8UWlOanFhxiZODilGhgZvGeEGxWa/n+0utt6TXvhrV0rRO/vsryft66q 9/cqfnXByS0R03PjfoefP8Liday09Mz/54KKrqLG8X0n9JatdftSPIu99u+UX5VHHvSXVd+0 /cB7tMztcIOVe+gFzsajl09Kihm5HC+zzODjW1afndLJ/ULhpNRXnTlVemknVXMWPrE+dFKJ pTgj0VCLuag4EQAFmmASrQIAAA== Archived-At: Cc: "hybi@ietf.org" , Barry Leiba Subject: Re: [hybi] I-D Action: draft-ietf-hybi-permessage-compression-28.txt X-BeenThere: hybi@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Server-Initiated HTTP List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Sep 2015 10:44:33 -0000 --_000_2B9B48179856DC4FA00C93C79EB7E64A0E950202ESESSMB108erics_ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 SGkgVG9iaWENCg0KSW4gb3JkZXIgZm9yIHRoZSB3ZyB0byBiZSByZWNoYXJ0ZWQgLyByZXN1cnJl Y3RlZA0KSXQgaXMgbmVjZXNzYXJ5IHRvIGJlIGVub3VnaCBpbnRlcmVzdCBpbiB0aGUgd29yayBm cm9tIHNldmVyYWwgcGVvcGxlcy9jb21wYW5pZXMgb24gdGhlIGl0ZW1zDQpPdGhlciB0aGVuIGEg Y2xlYXIgdGVjaG5pY2FsIHByb3Bvc2FsKHMpDQoNCkF0IG1vbWVudCBpdCBzZWVtcyB0aGF0IHBl b3BsZSBhcmUgbW9yZSBpbnRlcmVzdGVkIHRvIGV2b2x2ZSBIVFRQMiB0aGVuIGluIFdlYlNvY2tl dC4NCg0KQnINClNhbHZhdG9yZQ0KDQpGcm9tOiBUYWtlc2hpIFlvc2hpbm8gW21haWx0bzp0eW9z aGlub0Bnb29nbGUuY29tXQ0KU2VudDogZGVuIDE0IHNlcHRlbWJlciAyMDE1IDExOjExDQpUbzog VG9iaWFzIE9iZXJzdGVpbg0KQ2M6IEJhcnJ5IExlaWJhOyBTYWx2YXRvcmUgTG9yZXRvOyBoeWJp QGlldGYub3JnDQpTdWJqZWN0OiBSZTogW2h5YmldIEktRCBBY3Rpb246IGRyYWZ0LWlldGYtaHli aS1wZXJtZXNzYWdlLWNvbXByZXNzaW9uLTI4LnR4dA0KDQpPbiBNb24sIFNlcCAxNCwgMjAxNSBh dCA1OjQ0IEFNLCBUb2JpYXMgT2JlcnN0ZWluIDx0b2JpYXMub2JlcnN0ZWluQHRhdmVuZG8uZGU8 bWFpbHRvOnRvYmlhcy5vYmVyc3RlaW5AdGF2ZW5kby5kZT4+IHdyb3RlOg0KR3JlYXQ7IEkndmUg Y2hlY2tlZCBpdCB0b28sIGFuZCBJIGFncmVlLiAgSSd2ZSBhcHByb3ZlZCBpdCwgYW5kIHlvdQ0K c2hvdWxkIHNlZSB0aGUgYW5ub3VuY2VtZW50IHNvb24uDQoNCkF3ZXNvbWUhIFRoZSBXZWJTb2Nr ZXQgY29tcHJlc3Npb24gZXh0ZW5zaW9uIGlzIG9mIGdyZWF0IHByYWN0aWNhbCB2YWx1ZS4NCg0K VGhhbmsgeW91LCBUb2JpYXMgZm9yIHlvdXIgY29udGludWVkIGNvbnRyaWJ1dGlvbiBpbmNsdWRp bmcgZGlzY3Vzc2lvbiBhbmQgYnVpbGRpbmcgdGhlIHJlbGlhYmxlIGFuZCBjb21wcmVoZW5zaXZl IHRlc3Qgc3VpdGVzLg0KDQoNCg0KVGhlIHdvcmtpbmcgZ3JvdXAgd2lsbCByZW1haW4gb3BlbiB1 bnRpbCB0aGUgUkZDIGlzIHB1Ymxpc2hlZCwgYWZ0ZXINCndoaWNoIEknbGwgY2xvc2UgdGhlIHdv cmtpbmcgZ3JvdXAsIGJ1dCBsZWF2ZSB0aGUgbWFpbGluZyBsaXN0IG9wZW4NCg0KUmVnYXJkaW5n IHRoZSBjbG9zaW5nIG9mIHRoZSB3b3JraW5nIGdyb3VwLCBJIHdvdWxkIGxpa2UgdG8gYXNrIHdo YXQgaXMgcmVxdWlyZWQgdG8gcmVjaGFydGVyIHRoZSBXRyB0byB3b3JrIG9uIGEgc3BlY2lmaWMg V2ViU29ja2V0IHN1YnByb3RvY29sLg0KDQpJIGFsc28gd29uZGVyIHdoYXQgd2UnbGwgbG9zZSBh bmQgd2hhdCB3ZSB3b24ndCAoaW4gYWRkaXRpb24gdG8gdGhlIG1haWxpbmcgbGlzdCkgYWZ0ZXIg V0cgY2xvc2UuIEkgd2FzIHdvcnJpZWQgdGhhdCB3ZSBtaWdodCBsb3NlIHRoZSBtYWlsaW5nIGxp c3QgdG9vLg0KDQpJIGd1ZXNzIGF0IGxlYXN0IHdlJ2xsIGJlIHVuYWJsZSB0byByYWlzZSBJLURz IGFzIFdHIGl0ZW1zIHdoaWxlIHRoZSBXRyBpcyBjbG9zZWQuDQoNCg0KVGhlIGN1cnJlbnQgV0cg Y2hhcnRlciBoYXMgdGhpcyB0byBzYXk6DQoNCiIiIg0KVGhlIHdvcmtpbmcgZ3JvdXAgd2lsbCBh bHNvIHNlcnZlIGFzIGEgZGlzY3Vzc2lvbiB2ZW51ZSBmb3INCnN1YnByb3RvY29scy4gIEhvd2V2 ZXIsIG5vIHN1YnByb3RvY29sIGlzIGN1cnJlbnRseSBjaGFydGVyZWQgYXMgYQ0KZGVsaXZlcmFi bGUsIGFuZCB0aGUgV0cgbXVzdCBiZSByZWNoYXJ0ZXJlZCB0byB3b3JrIG9uIGFueQ0Kc3VicHJv dG9jb2xzLg0KIiIiIGh0dHA6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvY2hhcnRlci1pZXRm LWh5YmkvDQoNClRoZSBzdWJwcm90b2NvbCBJIHdvdWxkIGxpa2UgdG8gc3RhcnQgd29ya2luZyBv biBpczoNCg0KIlRoZSBXZWIgQXBwbGljYXRpb24gTWVzc2FnaW5nIFByb3RvY29sIChXQU1QKSIN Cg0KaHR0cDovL3dhbXAud3MvDQpodHRwczovL2dpdGh1Yi5jb20vdGF2ZW5kby9XQU1QLw0KaHR0 cDovL3d3dy5pYW5hLm9yZy9hc3NpZ25tZW50cy93ZWJzb2NrZXQvd2Vic29ja2V0LnhtbCNzdWJw cm90b2NvbC1uYW1lDQoNCldBTVAgd2FzIHRoZSAzcmQgV2ViU29ja2V0IHN1YnByb3RvY29sIG9m ZmljaWFsbHkgcmVnaXN0ZXJlZCBhdCBJQU5BLCBoYXMgZ29uZSB0aHJvdWdoIDMrIHllYXJzIG9m IGRldmVsb3BtZW50LCBoYXMgbmVhcmx5IHR3byBkb3plbiBpbmRlcGVuZGVudCBhbmQgaW50ZXJv cGFyYWJsZSBpbXBsZW1lbnRhdGlvbnMsIGFuZCBhbiBhY3RpdmUgY29tbXVuaXR5Lg0KDQpJIGhh dmUgYXNrZWQgb24gdGhlIFdBTVAgaW1wbGVtZW50b3JzIG1haWxpbmcgbGlzdCBpZiB0aGVyZSBp cyBpbnRlcmVzdCBpbiB3b3JraW5nIG9uIGEgUkZDIGZvciBXQU1QLCBhbmQgbXVsdGlwbGUgcmVz cG9uc2VzIGluZGljYXRlIHRoYXQgdGhlcmUgaXMgaW5kZWVkIGludGVyZXN0Og0KDQpodHRwczov L2dyb3Vwcy5nb29nbGUuY29tL2ZvcnVtLyMhdG9waWMvd2FtcHdzL0xsS2pNRjNaSmY4DQoNCkkg YW0gb3JpZ2luYWwgYXV0aG9yIG9mIFdBTVAsIGFuZCBoYXZlIGJlZW4gYWN0aXZlIGR1cmluZyB0 aGUgZGV2ZWxvcG1lbnQgb2YgV2ViU29ja2V0IGFuZCB0aGUgV2ViU29ja2V0IGNvbXByZXNzaW9u IGV4dGVuc2lvbiBvbiB0aGUgSHliaSB3b3JraW5nIGdyb3VwLg0KDQpJIGFsc28gY3JlYXRlZCBh bmQgbWFpbnRhaW4gdGhlIEF1dG9iYWhuIFdlYlNvY2tldCB0ZXN0c3VpdGUgLSBhbiBhdXRvbWF0 ZWQgdGVzdHN1aXRlIGZvciBXUyB1c2VkIGJ5IG1vc3QgaW1wbGVtZW50b3JzLg0KDQpodHRwOi8v YXV0b2JhaG4ud3MvdGVzdHN1aXRlLw0KDQpBcGFydCBmcm9tIHRoYXQgSSB3cm90ZSBhIGNvdXBs ZSBvZiBXZWJTb2NrZXQgaW1wbGVtZW50YXRpb25zIGluIGRpZmZlcmVudCBsYW5ndWFnZXMuDQoN Ckhvd2V2ZXIsIEkgbmV2ZXIgd3JvdGUgYW4gUkZDIG5vciBkbyBJIGtub3cgYSBsb3QgYWJvdXQg SUVURiBwcm9jZXNzZXMgYW5kIHN1Y2guDQoNCkhlbmNlIG15IG5haXZlIHF1ZXN0aW9uOiB3aGF0 J3MgcmVxdWlyZWQgdG8gc3RhcnQgd29ya2luZyBvbiBXQU1QIHdpdGhpbiB0aGUgY29udGV4dCBv ZiB0aGlzIFdHPw0KDQpDaGVlcnMsDQovVG9iaWFzDQoNCg0KDQoNCl9fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQpoeWJpIG1haWxpbmcgbGlzdA0KaHliaUBp ZXRmLm9yZzxtYWlsdG86aHliaUBpZXRmLm9yZz4NCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxt YW4vbGlzdGluZm8vaHliaQ0KDQo= --_000_2B9B48179856DC4FA00C93C79EB7E64A0E950202ESESSMB108erics_ Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: base64 PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6 Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJ e2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQov KiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1z b05vcm1hbA0KCXttYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNp emU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLCJzZXJpZiI7fQ0KYTps aW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6 Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29I eXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxl Ow0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTcNCgl7bXNv LXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5z LXNlcmlmIjsNCgljb2xvcjojMUY0OTdEO30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10 eXBlOmV4cG9ydC1vbmx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7fQ0K QHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6NjEyLjBwdCA3OTIuMHB0Ow0KCW1hcmdpbjo3MC44 NXB0IDcwLjg1cHQgNzAuODVwdCA3MC44NXB0O30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpX b3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNo YXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRp Zl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0 Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0Pjwv eG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iRU4tVVMiIGxpbms9ImJsdWUi IHZsaW5rPSJwdXJwbGUiPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJN c29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90 O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj5IaSBU b2JpYTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0 eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1 b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bh bj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBw dDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7 Y29sb3I6IzFGNDk3RCI+SW4gb3JkZXIgZm9yIHRoZSB3ZyB0byBiZSByZWNoYXJ0ZWQgLyByZXN1 cnJlY3RlZA0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw YW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90 OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPkl0IGlzIG5lY2Vzc2FyeSB0 byBiZSBlbm91Z2ggaW50ZXJlc3QgaW4gdGhlIHdvcmsgZnJvbSBzZXZlcmFsIHBlb3BsZXMvY29t cGFuaWVzIG9uIHRoZSBpdGVtczxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29O b3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0Nh bGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj5PdGhlciB0 aGVuIGEgY2xlYXIgdGVjaG5pY2FsIHByb3Bvc2FsKHMpPG86cD48L286cD48L3NwYW4+PC9wPg0K PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1m YW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMx RjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkm cXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj5BdCBtb21lbnQgaXQg c2VlbXMgdGhhdCBwZW9wbGUgYXJlIG1vcmUgaW50ZXJlc3RlZCB0byBldm9sdmUgSFRUUDIgdGhl biBpbiBXZWJTb2NrZXQuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h bCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJy aSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7 PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250 LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1z ZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj5CcjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5 OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdE Ij5TYWx2YXRvcmU8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48 c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1 b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286 cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gc3R5bGU9ImZvbnQt c2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90O3NhbnMtc2Vy aWYmcXVvdDsiPkZyb206PC9zcGFuPjwvYj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtm b250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+IFRh a2VzaGkgWW9zaGlubyBbbWFpbHRvOnR5b3NoaW5vQGdvb2dsZS5jb21dDQo8YnI+DQo8Yj5TZW50 OjwvYj4gZGVuIDE0IHNlcHRlbWJlciAyMDE1IDExOjExPGJyPg0KPGI+VG86PC9iPiBUb2JpYXMg T2JlcnN0ZWluPGJyPg0KPGI+Q2M6PC9iPiBCYXJyeSBMZWliYTsgU2FsdmF0b3JlIExvcmV0bzsg aHliaUBpZXRmLm9yZzxicj4NCjxiPlN1YmplY3Q6PC9iPiBSZTogW2h5YmldIEktRCBBY3Rpb246 IGRyYWZ0LWlldGYtaHliaS1wZXJtZXNzYWdlLWNvbXByZXNzaW9uLTI4LnR4dDxvOnA+PC9vOnA+ PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0K PGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+T24gTW9uLCBTZXAgMTQs IDIwMTUgYXQgNTo0NCBBTSwgVG9iaWFzIE9iZXJzdGVpbiAmbHQ7PGEgaHJlZj0ibWFpbHRvOnRv Ymlhcy5vYmVyc3RlaW5AdGF2ZW5kby5kZSIgdGFyZ2V0PSJfYmxhbmsiPnRvYmlhcy5vYmVyc3Rl aW5AdGF2ZW5kby5kZTwvYT4mZ3Q7IHdyb3RlOjxvOnA+PC9vOnA+PC9wPg0KPGJsb2NrcXVvdGUg c3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7cGFkZGlu ZzowY20gMGNtIDBjbSA2LjBwdDttYXJnaW4tbGVmdDo0LjhwdDttYXJnaW4tcmlnaHQ6MGNtIj4N CjxwIGNsYXNzPSJNc29Ob3JtYWwiPkdyZWF0OyBJJ3ZlIGNoZWNrZWQgaXQgdG9vLCBhbmQgSSBh Z3JlZS4mbmJzcDsgSSd2ZSBhcHByb3ZlZCBpdCwgYW5kIHlvdTxicj4NCnNob3VsZCBzZWUgdGhl IGFubm91bmNlbWVudCBzb29uLjxvOnA+PC9vOnA+PC9wPg0KPC9ibG9ja3F1b3RlPg0KPHAgY2xh c3M9Ik1zb05vcm1hbCI+PGJyPg0KQXdlc29tZSEgVGhlIFdlYlNvY2tldCBjb21wcmVzc2lvbiBl eHRlbnNpb24gaXMgb2YgZ3JlYXQgcHJhY3RpY2FsIHZhbHVlLjxvOnA+PC9vOnA+PC9wPg0KPGRp dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8 ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+VGhhbmsgeW91LCBUb2JpYXMgZm9yIHlvdXIgY29u dGludWVkIGNvbnRyaWJ1dGlvbiBpbmNsdWRpbmcgZGlzY3Vzc2lvbiBhbmQgYnVpbGRpbmcgdGhl IHJlbGlhYmxlIGFuZCBjb21wcmVoZW5zaXZlIHRlc3Qgc3VpdGVzLjxvOnA+PC9vOnA+PC9wPg0K PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7PG86cD48L286cD48L3A+ DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xp ZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNi4wcHQ7bWFyZ2luLWxlZnQ6NC44 cHQ7bWFyZ2luLXJpZ2h0OjBjbSI+DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9y ZGVyLWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRkaW5nOjBjbSAwY20gMGNtIDYuMHB0O21h cmdpbi1sZWZ0OjQuOHB0O21hcmdpbi1yaWdodDowY20iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIg c3R5bGU9Im1hcmdpbi1ib3R0b206MTIuMHB0Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNs YXNzPSJNc29Ob3JtYWwiPjxicj4NClRoZSB3b3JraW5nIGdyb3VwIHdpbGwgcmVtYWluIG9wZW4g dW50aWwgdGhlIFJGQyBpcyBwdWJsaXNoZWQsIGFmdGVyPGJyPg0Kd2hpY2ggSSdsbCBjbG9zZSB0 aGUgd29ya2luZyBncm91cCwgYnV0IGxlYXZlIHRoZSBtYWlsaW5nIGxpc3Qgb3BlbjxvOnA+PC9v OnA+PC9wPg0KPC9ibG9ja3F1b3RlPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGJyPg0KUmVnYXJk aW5nIHRoZSBjbG9zaW5nIG9mIHRoZSB3b3JraW5nIGdyb3VwLCBJIHdvdWxkIGxpa2UgdG8gYXNr IHdoYXQgaXMgcmVxdWlyZWQgdG8gcmVjaGFydGVyIHRoZSBXRyB0byB3b3JrIG9uIGEgc3BlY2lm aWMgV2ViU29ja2V0IHN1YnByb3RvY29sLjxvOnA+PC9vOnA+PC9wPg0KPC9ibG9ja3F1b3RlPg0K PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+ DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SSBhbHNvIHdvbmRlciB3aGF0IHdlJ2xsIGxv c2UgYW5kIHdoYXQgd2Ugd29uJ3QgKGluIGFkZGl0aW9uIHRvIHRoZSBtYWlsaW5nIGxpc3QpIGFm dGVyIFdHIGNsb3NlLiBJIHdhcyB3b3JyaWVkIHRoYXQgd2UgbWlnaHQgbG9zZSB0aGUgbWFpbGlu ZyBsaXN0IHRvby48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O b3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z b05vcm1hbCI+SSBndWVzcyBhdCBsZWFzdCB3ZSdsbCBiZSB1bmFibGUgdG8gcmFpc2UgSS1EcyBh cyBXRyBpdGVtcyB3aGlsZSB0aGUgV0cgaXMgY2xvc2VkLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+ DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rp dj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjQ0ND Q0NDIDEuMHB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNi4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFy Z2luLXJpZ2h0OjBjbSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48YnI+DQpUaGUgY3VycmVudCBX RyBjaGFydGVyIGhhcyB0aGlzIHRvIHNheTo8YnI+DQo8YnI+DQomcXVvdDsmcXVvdDsmcXVvdDs8 YnI+DQpUaGUgd29ya2luZyBncm91cCB3aWxsIGFsc28gc2VydmUgYXMgYSBkaXNjdXNzaW9uIHZl bnVlIGZvcjxicj4NCnN1YnByb3RvY29scy4mbmJzcDsgSG93ZXZlciwgbm8gc3VicHJvdG9jb2wg aXMgY3VycmVudGx5IGNoYXJ0ZXJlZCBhcyBhPGJyPg0KZGVsaXZlcmFibGUsIGFuZCB0aGUgV0cg bXVzdCBiZSByZWNoYXJ0ZXJlZCB0byB3b3JrIG9uIGFueTxicj4NCnN1YnByb3RvY29scy48YnI+ DQomcXVvdDsmcXVvdDsmcXVvdDsgPGEgaHJlZj0iaHR0cDovL2RhdGF0cmFja2VyLmlldGYub3Jn L2RvYy9jaGFydGVyLWlldGYtaHliaS8iIHRhcmdldD0iX2JsYW5rIj4NCmh0dHA6Ly9kYXRhdHJh Y2tlci5pZXRmLm9yZy9kb2MvY2hhcnRlci1pZXRmLWh5YmkvPC9hPjxicj4NCjxicj4NClRoZSBz dWJwcm90b2NvbCBJIHdvdWxkIGxpa2UgdG8gc3RhcnQgd29ya2luZyBvbiBpczo8YnI+DQo8YnI+ DQomcXVvdDtUaGUgV2ViIEFwcGxpY2F0aW9uIE1lc3NhZ2luZyBQcm90b2NvbCAoV0FNUCkmcXVv dDs8YnI+DQo8YnI+DQo8YSBocmVmPSJodHRwOi8vd2FtcC53cy8iIHRhcmdldD0iX2JsYW5rIj5o dHRwOi8vd2FtcC53cy88L2E+PGJyPg0KPGEgaHJlZj0iaHR0cHM6Ly9naXRodWIuY29tL3RhdmVu ZG8vV0FNUC8iIHRhcmdldD0iX2JsYW5rIj5odHRwczovL2dpdGh1Yi5jb20vdGF2ZW5kby9XQU1Q LzwvYT48YnI+DQo8YSBocmVmPSJodHRwOi8vd3d3LmlhbmEub3JnL2Fzc2lnbm1lbnRzL3dlYnNv Y2tldC93ZWJzb2NrZXQueG1sI3N1YnByb3RvY29sLW5hbWUiIHRhcmdldD0iX2JsYW5rIj5odHRw Oi8vd3d3LmlhbmEub3JnL2Fzc2lnbm1lbnRzL3dlYnNvY2tldC93ZWJzb2NrZXQueG1sI3N1YnBy b3RvY29sLW5hbWU8L2E+PGJyPg0KPGJyPg0KV0FNUCB3YXMgdGhlIDNyZCBXZWJTb2NrZXQgc3Vi cHJvdG9jb2wgb2ZmaWNpYWxseSByZWdpc3RlcmVkIGF0IElBTkEsIGhhcyBnb25lIHRocm91Z2gg MyYjNDM7IHllYXJzIG9mIGRldmVsb3BtZW50LCBoYXMgbmVhcmx5IHR3byBkb3plbiBpbmRlcGVu ZGVudCBhbmQgaW50ZXJvcGFyYWJsZSBpbXBsZW1lbnRhdGlvbnMsIGFuZCBhbiBhY3RpdmUgY29t bXVuaXR5Ljxicj4NCjxicj4NCkkgaGF2ZSBhc2tlZCBvbiB0aGUgV0FNUCBpbXBsZW1lbnRvcnMg bWFpbGluZyBsaXN0IGlmIHRoZXJlIGlzIGludGVyZXN0IGluIHdvcmtpbmcgb24gYSBSRkMgZm9y IFdBTVAsIGFuZCBtdWx0aXBsZSByZXNwb25zZXMgaW5kaWNhdGUgdGhhdCB0aGVyZSBpcyBpbmRl ZWQgaW50ZXJlc3Q6PGJyPg0KPGJyPg0KPGEgaHJlZj0iaHR0cHM6Ly9ncm91cHMuZ29vZ2xlLmNv bS9mb3J1bS8jIXRvcGljL3dhbXB3cy9MbEtqTUYzWkpmOCIgdGFyZ2V0PSJfYmxhbmsiPmh0dHBz Oi8vZ3JvdXBzLmdvb2dsZS5jb20vZm9ydW0vIyF0b3BpYy93YW1wd3MvTGxLak1GM1pKZjg8L2E+ PGJyPg0KPGJyPg0KSSBhbSBvcmlnaW5hbCBhdXRob3Igb2YgV0FNUCwgYW5kIGhhdmUgYmVlbiBh Y3RpdmUgZHVyaW5nIHRoZSBkZXZlbG9wbWVudCBvZiBXZWJTb2NrZXQgYW5kIHRoZSBXZWJTb2Nr ZXQgY29tcHJlc3Npb24gZXh0ZW5zaW9uIG9uIHRoZSBIeWJpIHdvcmtpbmcgZ3JvdXAuPGJyPg0K PGJyPg0KSSBhbHNvIGNyZWF0ZWQgYW5kIG1haW50YWluIHRoZSBBdXRvYmFobiBXZWJTb2NrZXQg dGVzdHN1aXRlIC0gYW4gYXV0b21hdGVkIHRlc3RzdWl0ZSBmb3IgV1MgdXNlZCBieSBtb3N0IGlt cGxlbWVudG9ycy48YnI+DQo8YnI+DQo8YSBocmVmPSJodHRwOi8vYXV0b2JhaG4ud3MvdGVzdHN1 aXRlLyIgdGFyZ2V0PSJfYmxhbmsiPmh0dHA6Ly9hdXRvYmFobi53cy90ZXN0c3VpdGUvPC9hPjxi cj4NCjxicj4NCkFwYXJ0IGZyb20gdGhhdCBJIHdyb3RlIGEgY291cGxlIG9mIFdlYlNvY2tldCBp bXBsZW1lbnRhdGlvbnMgaW4gZGlmZmVyZW50IGxhbmd1YWdlcy48YnI+DQo8YnI+DQpIb3dldmVy LCBJIG5ldmVyIHdyb3RlIGFuIFJGQyBub3IgZG8gSSBrbm93IGEgbG90IGFib3V0IElFVEYgcHJv Y2Vzc2VzIGFuZCBzdWNoLjxicj4NCjxicj4NCkhlbmNlIG15IG5haXZlIHF1ZXN0aW9uOiB3aGF0 J3MgcmVxdWlyZWQgdG8gc3RhcnQgd29ya2luZyBvbiBXQU1QIHdpdGhpbiB0aGUgY29udGV4dCBv ZiB0aGlzIFdHPzxicj4NCjxicj4NCkNoZWVycyw8YnI+DQovVG9iaWFzPG86cD48L286cD48L3A+ DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxicj4NCjxicj4NCjxicj4NCjxi cj4NCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fPGJyPg0K aHliaSBtYWlsaW5nIGxpc3Q8YnI+DQo8YSBocmVmPSJtYWlsdG86aHliaUBpZXRmLm9yZyIgdGFy Z2V0PSJfYmxhbmsiPmh5YmlAaWV0Zi5vcmc8L2E+PGJyPg0KPGEgaHJlZj0iaHR0cHM6Ly93d3cu aWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9oeWJpIiB0YXJnZXQ9Il9ibGFuayI+aHR0cHM6Ly93 d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9oeWJpPC9hPjxvOnA+PC9vOnA+PC9wPg0KPC9k aXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+ PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2JvZHk+DQo8 L2h0bWw+DQo= --_000_2B9B48179856DC4FA00C93C79EB7E64A0E950202ESESSMB108erics_-- From nobody Mon Sep 14 04:29:44 2015 Return-Path: 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 29F9B1B4DB6 for ; Mon, 14 Sep 2015 04:29:44 -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 SEzfZKIyPWki for ; Mon, 14 Sep 2015 04:29:41 -0700 (PDT) Received: from EXHUB020-4.exch020.serverdata.net (exhub020-4.exch020.serverdata.net [206.225.164.31]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EE37F1B373F for ; Mon, 14 Sep 2015 04:29:40 -0700 (PDT) Received: from [192.168.1.140] (88.217.52.82) by smtpx20.serverdata.net (206.225.164.36) with Microsoft SMTP Server (TLS) id 8.3.377.0; Mon, 14 Sep 2015 04:29:39 -0700 To: Salvatore Loreto , Takeshi Yoshino References: <20150824112514.18998.33071.idtracker@ietfa.amsl.com> <7730FEFF-FA09-4278-A8BF-B3325E6C2EC1@ericsson.com> <55F5E021.2000803@tavendo.de> <2B9B48179856DC4FA00C93C79EB7E64A0E950202@ESESSMB108.ericsson.se> From: Tobias Oberstein Message-ID: <55F6AFA1.9070404@tavendo.de> Date: Mon, 14 Sep 2015 13:29:37 +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: <2B9B48179856DC4FA00C93C79EB7E64A0E950202@ESESSMB108.ericsson.se> Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit Archived-At: Cc: "hybi@ietf.org" , Barry Leiba Subject: Re: [hybi] I-D Action: draft-ietf-hybi-permessage-compression-28.txt X-BeenThere: hybi@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Server-Initiated HTTP List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Sep 2015 11:29:44 -0000 Hi Salvatore, > In order for the wg to be recharted / resurrected > > It is necessary to be enough interest in the work from several > peoples/companies on the items I figured that, and asked around in the WAMP community: https://groups.google.com/forum/#!topic/wampws/LlKjMF3ZJf8 For your convenience, here is the summary up to now: - Konstantin Burkalev, Atlantis communications, Russia - Elvis Stansvik, KTH Royal Inst. of Tech., Schweden - Francesco Longo, University of Messina, Italy - David Chappelle,Topology LP, Canada - Emile Cormier, Butterfly Energy Systems, Canada - Tobias Oberstein, Tavendo, Germany Among those, there are 4 WAMP implementors (have written and maintain one or more WAMP implementations). There are multiple companies and academia represented. I will DM more implementors and users .. I am pretty sure there is interest. How "much" interest is needed? How should we "proof"? Should I ask all to speak up on this mailing list? > > Other then a clear technical proposal(s) So do we need a draft RFC written _before_ we can request to recharter the WG? > > At moment it seems that people are more interested to evolve HTTP2 then > in WebSocket. Not sure, maybe there is a misunderstanding: what we would like to work on is a specific WebSocket _subprotocol_: an application layer protocol on top of WebSocket. We don't want to work on a WebSocket V2.0 or such. Apart from that: HTTP2 interest/uptake compared to WebSocket - we could of course have a discussion about that, but is that relevant for the _WebSocket_ WG? I mean: WebSocket _does_ have significant uptake, interest and use on the street. It has an RFC. Are you saying we should discontinue WebSocket just because there is HTTP2? I definitely would NOT buy that view, and I'd have some arguments (technical and other) to support that. But I'd like rather avoid getting into such discussions anyway (unproductive). HTTP2 does what it does - or not. But this is the WebSocket WG, which I would have assumed represents the interests and continues innovation in WS - not? Please excuse if I don't understand the right way to approach this under IETF traditions / wording .. or miss something. Not intended. Cheers, /Tobias > > Br > > Salvatore > > *From:*Takeshi Yoshino [mailto:tyoshino@google.com] > *Sent:* den 14 september 2015 11:11 > *To:* Tobias Oberstein > *Cc:* Barry Leiba; Salvatore Loreto; hybi@ietf.org > *Subject:* Re: [hybi] I-D Action: > draft-ietf-hybi-permessage-compression-28.txt > > On Mon, Sep 14, 2015 at 5:44 AM, Tobias Oberstein > > wrote: > > Great; I've checked it too, and I agree. I've approved it, and you > should see the announcement soon. > > > Awesome! The WebSocket compression extension is of great practical value. > > Thank you, Tobias for your continued contribution including discussion > and building the reliable and comprehensive test suites. > > > The working group will remain open until the RFC is published, after > which I'll close the working group, but leave the mailing list open > > > Regarding the closing of the working group, I would like to ask what > is required to recharter the WG to work on a specific WebSocket > subprotocol. > > I also wonder what we'll lose and what we won't (in addition to the > mailing list) after WG close. I was worried that we might lose the > mailing list too. > > I guess at least we'll be unable to raise I-Ds as WG items while the WG > is closed. > > > The current WG charter has this to say: > > """ > The working group will also serve as a discussion venue for > subprotocols. However, no subprotocol is currently chartered as a > deliverable, and the WG must be rechartered to work on any > subprotocols. > """ http://datatracker.ietf.org/doc/charter-ietf-hybi/ > > The subprotocol I would like to start working on is: > > "The Web Application Messaging Protocol (WAMP)" > > http://wamp.ws/ > https://github.com/tavendo/WAMP/ > http://www.iana.org/assignments/websocket/websocket.xml#subprotocol-name > > WAMP was the 3rd WebSocket subprotocol officially registered at > IANA, has gone through 3+ years of development, has nearly two dozen > independent and interoparable implementations, and an active community. > > I have asked on the WAMP implementors mailing list if there is > interest in working on a RFC for WAMP, and multiple responses > indicate that there is indeed interest: > > https://groups.google.com/forum/#!topic/wampws/LlKjMF3ZJf8 > > I am original author of WAMP, and have been active during the > development of WebSocket and the WebSocket compression extension on > the Hybi working group. > > I also created and maintain the Autobahn WebSocket testsuite - an > automated testsuite for WS used by most implementors. > > http://autobahn.ws/testsuite/ > > Apart from that I wrote a couple of WebSocket implementations in > different languages. > > However, I never wrote an RFC nor do I know a lot about IETF > processes and such. > > Hence my naive question: what's required to start working on WAMP > within the context of this WG? > > Cheers, > /Tobias > > > > > > _______________________________________________ > hybi mailing list > hybi@ietf.org > https://www.ietf.org/mailman/listinfo/hybi > From nobody Mon Sep 14 06:20:34 2015 Return-Path: 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 5CE951B2EE5 for ; Mon, 14 Sep 2015 06:20:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.278 X-Spam-Level: X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 0oYVpdJqW0Bg for ; Mon, 14 Sep 2015 06:20:32 -0700 (PDT) Received: from mail-vk0-x232.google.com (mail-vk0-x232.google.com [IPv6:2607:f8b0:400c:c05::232]) (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 21BB51A1BAE for ; Mon, 14 Sep 2015 06:20:32 -0700 (PDT) Received: by vkfp126 with SMTP id p126so58411177vkf.3 for ; Mon, 14 Sep 2015 06:20:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=oOLI0exSWdVnZi2vRRqn+0otSzRPZEc4n5S4huOAWmM=; b=d2gaaXsRY2iwPcFl4H8B6RJ3wZ2SUv/N6V+AXwq2qB08Paa06LvrKVZ0LQc+eIcaOT 0vpjRKuA68BwiPe5iAXwb/qPdFRiEwLnq1oxfiy97G3g0Vtz3E1sGiIromNmzdzqydZM fPCgfSkfSA3EK4qqkSkGpVXI+TWGa8kmfdS4Jr+t1FjqNZCV5bAE9ezKlccMfv9MMwnL a0zKhe1z0i7DSnNyVwnGST3cvfzQb58jiTL4luemLtLeKv2mv8My0lJ5RRkuLLVNu6Az PcAWOFvGdpptMlfMD+29JI3ALW+cysUTOr6h8BPUFyp2jwp4Vg7zwui5IS8SmGo7Nb0x bVuA== MIME-Version: 1.0 X-Received: by 10.31.132.131 with SMTP id g125mr13940039vkd.40.1442236831173; Mon, 14 Sep 2015 06:20:31 -0700 (PDT) Sender: barryleiba@gmail.com Received: by 10.31.88.196 with HTTP; Mon, 14 Sep 2015 06:20:31 -0700 (PDT) In-Reply-To: <55F6AFA1.9070404@tavendo.de> References: <20150824112514.18998.33071.idtracker@ietfa.amsl.com> <7730FEFF-FA09-4278-A8BF-B3325E6C2EC1@ericsson.com> <55F5E021.2000803@tavendo.de> <2B9B48179856DC4FA00C93C79EB7E64A0E950202@ESESSMB108.ericsson.se> <55F6AFA1.9070404@tavendo.de> Date: Mon, 14 Sep 2015 09:20:31 -0400 X-Google-Sender-Auth: nA4Wew8-B0i1XNo0BInADE43ofw Message-ID: From: Barry Leiba To: Tobias Oberstein Content-Type: text/plain; charset=UTF-8 Archived-At: Cc: "hybi@ietf.org" Subject: Re: [hybi] I-D Action: draft-ietf-hybi-permessage-compression-28.txt X-BeenThere: hybi@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Server-Initiated HTTP List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Sep 2015 13:20:33 -0000 >> In order for the wg to be recharted / resurrected >> It is necessary to be enough interest in the work from several >> peoples/companies on the items > > I figured that, and asked around in the WAMP community: ... > How "much" interest is needed? How should we "proof"? Should I ask all to > speak up on this mailing list? It's hard to put a number on it, but there needs to be enough interest and commitment to participate that we can rely on progressing documents and getting meaningful review. We have been having a lot of trouble with that over the past couple of *years*, so it's not just a moderate slowdown. That said, if we really *do* have enough commitment, I'm willing to recharter the working group. I can't speak for the chairs about whether they're willing to continue, but perhaps we could get new chairs to take it forward -- Salvatore and Gabriel have chaired this working group for a long time now. > So do we need a draft RFC written _before_ we can request to recharter the > WG? We don't *need* it, though a draft and some reviews of it would be some evidence that there's enough interest. >> At moment it seems that people are more interested to evolve HTTP2 then >> in WebSocket. > > Not sure, maybe there is a misunderstanding: what we would like to work on > is a specific WebSocket _subprotocol_: an application layer protocol on top > of WebSocket. We don't want to work on a WebSocket V2.0 or such. The point is that implementors are less interested in implementing websocket things, now that http/2 is here. Layering things on websockets might not be very useful if implementors are moving to http/2 instead, for such functions in the future. But, again, if there really is enough interest in implementing new function on websockets, and we can see that interest in commitment to work on the specs, then that might be fine. Barry From kostik.hunter@gmail.com Mon Sep 14 09:57:38 2015 Return-Path: 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 5E6D01B35F2 for ; Mon, 14 Sep 2015 09:57:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.698 X-Spam-Level: X-Spam-Status: No, score=-1.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FSL_MY_NAME_IS=0.001, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] 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 FyNJ4PZ0CpNG for ; Mon, 14 Sep 2015 09:57:36 -0700 (PDT) Received: from mail-la0-x22c.google.com (mail-la0-x22c.google.com [IPv6:2a00:1450:4010:c03::22c]) (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 F33431B2EE3 for ; Mon, 14 Sep 2015 09:57:35 -0700 (PDT) Received: by lamp12 with SMTP id p12so89894001lam.0 for ; Mon, 14 Sep 2015 09:57:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:message-id:mime-version:subject:date:references :to:in-reply-to; bh=35Vabkp9FBdXV03XPegeTGvnCw2hQzdEoCNmwXDjrts=; b=RCbA6xqLesfDhCvMlSxY/TKhHXMPZN49g5l9jRLtVOsLvPk7KLAAAX8ZLZTM5hdvLc ZHqKwkO5/yBZd3sGEEctwuFjNLR70QAXyTwxwaF1C6b001LdE5hddfltykBz8LUsjnO6 QT9ufte7dPYGV6/HMIG7awiBUjEPtzRrlrinoita2kOVOJI8muBberJvm6y5N3pofyat oezq2b0j1YXsgGTYl3CLb05Ryj1IG0BsVvw8ppywD50vMML2RtfXWSZ40LgJIXxFTQew VImJ1UMS05CJsTE90pRX2daTjdHYOhJXCHEDXv7fN2PqvR7Ly2ATkQecFjuYZvG3yhCz 4PkA== X-Received: by 10.112.25.69 with SMTP id a5mr15333279lbg.16.1442249854109; Mon, 14 Sep 2015 09:57:34 -0700 (PDT) Received: from [192.168.24.200] ([212.83.3.189]) by smtp.gmail.com with ESMTPSA id k15sm2547612laa.30.2015.09.14.09.57.33 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 14 Sep 2015 09:57:33 -0700 (PDT) From: =?utf-8?B?0JrQvtC90YHRgtCw0L3RgtC40L0g0JHRg9GA0LrQsNC70LXQsg==?= Content-Type: multipart/alternative; boundary="Apple-Mail=_B53D5F4E-C6BF-4A23-A48E-296C242940F4" Message-Id: <8027DC26-AE4B-4988-B6D5-9D57F090A518@gmail.com> Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Date: Mon, 14 Sep 2015 19:57:31 +0300 References: <20150824112514.18998.33071.idtracker@ietfa.amsl.com> <7730FEFF-FA09-4278-A8BF-B3325E6C2EC1@ericsson.com> <55F5E021.2000803@tavendo.de> <2B9B48179856DC4FA00C93C79EB7E64A0E950202@ESESSMB108.ericsson.se> <55F6AFA1.9070404@tavendo.de> To: hybi@ietf.org In-Reply-To: X-Mailer: Apple Mail (2.2104) Archived-At: Subject: Re: [hybi] I-D Action: draft-ietf-hybi-permessage-compression-28.txt X-BeenThere: hybi@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Server-Initiated HTTP List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Sep 2015 17:06:49 -0000 --Apple-Mail=_B53D5F4E-C6BF-4A23-A48E-296C242940F4 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi, Barry, Salvatore and all! My name is Konstantin, i=E2=80=99m a software architect in = telecommunication company,=20 also i=E2=80=99m author and maintainer of 3 WAMP implementations. Just want to say, that from my point of view there is enough interest in = WAMP libraries,=20 which, of course, are based on WAMP protocol.=20 I am already involved in development of WAMP spec, and i=E2=80=99m = willing to continue work on WAMP as RFC. I know different cases of WAMP usage, among them there are: * IoT devices and systems, I=E2=80=99m also working on a subject. And = right now small chips and devices (for ex. ESP8266) support only = http/1.1. * Mobile applications, based on JavaScript engines and platforms like = React Native And so on.=20 We (i mean WAMP implementators, like Tobias or Emile) are already doing = a big work in developing WAMP specification and fulfilling the gaps, and = there are more and more=20 people, involved in WAMP community. Just check the WAMP mailing list = (https://groups.google.com/forum/#!forum/wampws = ) > 14 =D1=81=D0=B5=D0=BD=D1=82. 2015 =D0=B3., =D0=B2 16:20, Barry Leiba = =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BB(=D0=B0= ): >=20 >>> In order for the wg to be recharted / resurrected >>> It is necessary to be enough interest in the work from several >>> peoples/companies on the items >>=20 >> I figured that, and asked around in the WAMP community: > ... >> How "much" interest is needed? How should we "proof"? Should I ask = all to >> speak up on this mailing list? >=20 > It's hard to put a number on it, but there needs to be enough interest > and commitment to participate that we can rely on progressing > documents and getting meaningful review. We have been having a lot of > trouble with that over the past couple of *years*, so it's not just a > moderate slowdown. >=20 > That said, if we really *do* have enough commitment, I'm willing to > recharter the working group. I can't speak for the chairs about > whether they're willing to continue, but perhaps we could get new > chairs to take it forward -- Salvatore and Gabriel have chaired this > working group for a long time now. >=20 >> So do we need a draft RFC written _before_ we can request to = recharter the >> WG? >=20 > We don't *need* it, though a draft and some reviews of it would be > some evidence that there's enough interest. >=20 >>> At moment it seems that people are more interested to evolve HTTP2 = then >>> in WebSocket. >>=20 >> Not sure, maybe there is a misunderstanding: what we would like to = work on >> is a specific WebSocket _subprotocol_: an application layer protocol = on top >> of WebSocket. We don't want to work on a WebSocket V2.0 or such. >=20 > The point is that implementors are less interested in implementing > websocket things, now that http/2 is here. Layering things on > websockets might not be very useful if implementors are moving to > http/2 instead, for such functions in the future. >=20 > But, again, if there really is enough interest in implementing new > function on websockets, and we can see that interest in commitment to > work on the specs, then that might be fine. >=20 > Barry >=20 > _______________________________________________ > hybi mailing list > hybi@ietf.org > https://www.ietf.org/mailman/listinfo/hybi With best regards, KOsTIK kostik.hunter@gmail.com --Apple-Mail=_B53D5F4E-C6BF-4A23-A48E-296C242940F4 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Hi, Barry, Salvatore and all!

My name is Konstantin, i=E2=80=99m a = software architect in telecommunication company, 
also i=E2=80=99m author and maintainer of 3 WAMP = implementations.

Just want to say, that from my point of view there is enough = interest in WAMP libraries, 
which, of course, = are based on WAMP protocol. 
I am already = involved in development of WAMP spec, and i=E2=80=99m willing to = continue work on WAMP as RFC.

I know different cases of WAMP usage, = among them there are:
* IoT devices and systems, = I=E2=80=99m also working on a subject. And right now small chips and = devices (for ex. ESP8266) support only http/1.1.
* = Mobile applications, based on JavaScript engines and platforms like = React Native
And so on. 

We (i mean WAMP = implementators, like Tobias or Emile) are already doing a big work in = developing WAMP specification and fulfilling the gaps, and there are = more and more 
people, involved in WAMP = community. Just check the WAMP mailing list (https://groups.google.com/forum/#!forum/wampws)


14 =D1=81=D0=B5=D0=BD=D1=82. 2015 =D0=B3., =D0=B2 16:20, = Barry Leiba <barryleiba@computer.org> =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0= =B0=D0=BB(=D0=B0):

In order for the wg to be recharted / resurrected
It is necessary to be enough interest in the work from = several
peoples/companies on the items

I figured that, and asked around = in the WAMP community:
...
How "much" interest is = needed? How should we "proof"? Should I ask all to
speak = up on this mailing list?

It's = hard to put a number on it, but there needs to be enough interest
and commitment to participate that we can rely on = progressing
documents and getting meaningful review. =  We have been having a lot of
trouble with that over = the past couple of *years*, so it's not just a
moderate = slowdown.

That said, if we really *do* have = enough commitment, I'm willing to
recharter the working = group.  I can't speak for the chairs about
whether = they're willing to continue, but perhaps we could get new
chairs to take it forward -- Salvatore and Gabriel have = chaired this
working group for a long time now.

So do we = need a draft RFC written _before_ we can request to recharter the
WG?

We don't *need* = it, though a draft and some reviews of it would be
some = evidence that there's enough interest.

At moment it seems that people are more interested to evolve = HTTP2 then
in WebSocket.

Not sure, maybe there is a misunderstanding: what we would = like to work on
is a specific WebSocket _subprotocol_: an = application layer protocol on top
of WebSocket. We don't = want to work on a WebSocket V2.0 or such.

The point is that implementors are less interested in = implementing
websocket things, now that http/2 is here. =  Layering things on
websockets might not be very = useful if implementors are moving to
http/2 instead, for = such functions in the future.

But, again, = if there really is enough interest in implementing new
function on websockets, and we can see that interest in = commitment to
work on the specs, then that might be = fine.

Barry

_______________________________________________
hybi mailing list
hybi@ietf.org
https://www.ietf.org/mailman/listinfo/hybi

With best regards, KOsTIK



= --Apple-Mail=_B53D5F4E-C6BF-4A23-A48E-296C242940F4-- From nobody Mon Sep 14 14:24:04 2015 Return-Path: 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 B059F1A8752 for ; Mon, 14 Sep 2015 14:24:02 -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 cb2nYsTFyRmo for ; Mon, 14 Sep 2015 14:24:01 -0700 (PDT) Received: from EXHUB020-5.exch020.serverdata.net (exhub020-5.exch020.serverdata.net [206.225.164.32]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D028A1A8A13 for ; Mon, 14 Sep 2015 14:24:00 -0700 (PDT) Received: from [192.168.43.73] (89.204.135.213) by smtpx20.serverdata.net (206.225.164.37) with Microsoft SMTP Server (TLS) id 8.3.377.0; Mon, 14 Sep 2015 14:23:59 -0700 To: Barry Leiba References: <20150824112514.18998.33071.idtracker@ietfa.amsl.com> <7730FEFF-FA09-4278-A8BF-B3325E6C2EC1@ericsson.com> <55F5E021.2000803@tavendo.de> <2B9B48179856DC4FA00C93C79EB7E64A0E950202@ESESSMB108.ericsson.se> <55F6AFA1.9070404@tavendo.de> From: Tobias Oberstein Message-ID: <55F73AEB.70104@tavendo.de> Date: Mon, 14 Sep 2015 23:23:55 +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: Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit Archived-At: Cc: "hybi@ietf.org" Subject: Re: [hybi] I-D Action: draft-ietf-hybi-permessage-compression-28.txt X-BeenThere: hybi@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Server-Initiated HTTP List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Sep 2015 21:24:02 -0000 >> How "much" interest is needed? How should we "proof"? Should I ask all to >> speak up on this mailing list? > > It's hard to put a number on it, but there needs to be enough interest > and commitment to participate that we can rely on progressing > documents and getting meaningful review. We have been having a lot of > trouble with that over the past couple of *years*, so it's not just a > moderate slowdown. Thanks for explaining and background. I now understand that real world usage and takeup is only one factor, but enough interest to do the concrete work on a spec document is what counts. Makes sense. To get a high quality spec, there needs to be peer review and discussion. It's part of the IETF mantra I guess, and I totally buy that. > That said, if we really *do* have enough commitment, I'm willing to > recharter the working group. I can't speak for the chairs about Awesome! Would you give us a bit time to organize enough commitment and write a draft? Some weeks before closing the WG (if we can't deliver)? > whether they're willing to continue, but perhaps we could get new > chairs to take it forward -- Salvatore and Gabriel have chaired this > working group for a long time now. > >> So do we need a draft RFC written _before_ we can request to recharter the >> WG? > > We don't *need* it, though a draft and some reviews of it would be > some evidence that there's enough interest. Ok, we can prepare a draft according to RFC style from this spec document ("WAMP basic profile") that we have: https://github.com/tavendo/WAMP/blob/master/spec/basic.md That spec has been extensively discussed and has gone through many iterations from Mar 2012 to now. Discussion is on GitHub (94 closed, 67 open issues right now) and the WAMP mailing list (171 threads, 151 subscribers). > The point is that implementors are less interested in implementing > websocket things, now that http/2 is here. Layering things on > websockets might not be very useful if implementors are moving to > http/2 instead, for such functions in the future. FWIW, WAMP originally could only run on top of WebSocket. And it's still the most used "transport". But WAMP nowerdays can _also_ run over RawSocket (essentially, minimally framed TCP with some handshake sugar) and HTTP-Longpoll, and don't see why we couldn't specify a HTTP/2 "transport binding" (that's WAMP lingo for defining a mapping of WAMP to an underlying transport). WAMP-over-WebSocket is definitely the most important one, as it is the only thing that (today) can run right into all browsers. It is also the only transport that provides full, transparent payload compresssion - thanks to the WebSocket compression extension. > But, again, if there really is enough interest in implementing new > function on websockets, and we can see that interest in commitment to > work on the specs, then that might be fine. Thanks! Please give us some time before closing the WG. Once the WG would have closed, I guess the bar would be much higher .. and where should we take it then? I have skimmed through the different IETF art areas, and the WGs and charters for the "Applications and Real-Time Area" in particular, and it appears to me, that WAMP would fit the Hybi-WG's mission .. Cheers, /Tobias From nobody Wed Sep 16 01:04:46 2015 Return-Path: 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 797A01B3873 for ; Wed, 16 Sep 2015 01:04:45 -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 WnBt1dAU3HFc for ; Wed, 16 Sep 2015 01:04:44 -0700 (PDT) Received: from mail-oi0-x236.google.com (mail-oi0-x236.google.com [IPv6:2607:f8b0:4003:c06::236]) (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 22C181B3878 for ; Wed, 16 Sep 2015 01:04:44 -0700 (PDT) Received: by oiww128 with SMTP id w128so115970694oiw.2 for ; Wed, 16 Sep 2015 01:04:43 -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=SSjeXWiZi1eAOiWpl4b2d/R8L9ekkUzZ0k9jD0fWG78=; b=Wro1j5QC//NnSENpLW+91huIzRDSbagUSrGGXx1+OHCpuLpYud5Gv9F77yZgZ5WEI2 zwkFWisN54E4mMnxz/lC4zpUDy4uz2EcmtS923Tf3FzYIzR6AZHjzUeIaX7sYdncYzjF P3z8Oyr0EIJ7mU8Oi+NwM1i32qm7019OOQubQWQ0SvP/aFzwoksidDcp1x8lqOdxu3KA q8ljCkVXnymnX1kP/TMQEboIEjX9IbW6EatjpGRLSPddXAjE4ktElyssiUyRH7iIevDo v2cDelbpRWkssQwK6rFTaD2JH2+8aYw7UiNTZljy5cf77EQKZPZ/y3h1hZYIVoWaHBYa gvIg== 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=SSjeXWiZi1eAOiWpl4b2d/R8L9ekkUzZ0k9jD0fWG78=; b=EbsQdjMR8TXROXJz1xVMrS3DsMr0pFkKlPqGJ0uKmv9btpFIks+qXPisF23lB3B7E8 +xLgs/0qrXQVGwLn51BcXgMQBszM/6FASHHO/6mPgdtoEpopCohELjaqYG32LapuQSvz nN34obQHaH1Jrw9f5VzxqdIBaKY+QZTRLbPvAGPncXOQThHVrujQuAhZ/WZPRcJVY+sU XEbtmN8KZrzFpxL2ZvqMinXCDG1YpfgVcBFeV9SnTvLYS3yUuOZFrI98nGztbmiBZxhh GGLZ7UGrLQl9pUmZ0BpU7PhotFsOA5qS9S151UrRd4dLHh92UUp/4hZmosQ1Sd3raRz2 Xp3Q== X-Gm-Message-State: ALoCoQm776/wCkfNDlmtndsyLwRokfg2WZHKxImgg/HcZQQ2Xh+Ry/9BfyOYMBBuAW2U9Yjm5K9K X-Received: by 10.202.105.74 with SMTP id e71mr21630636oic.133.1442390683467; Wed, 16 Sep 2015 01:04:43 -0700 (PDT) MIME-Version: 1.0 Received: by 10.202.60.4 with HTTP; Wed, 16 Sep 2015 01:04:23 -0700 (PDT) In-Reply-To: References: From: Takeshi Yoshino Date: Wed, 16 Sep 2015 17:04:23 +0900 Message-ID: To: Anne van Kesteren Content-Type: multipart/alternative; boundary=001a11408c7850f0b6051fd8c0e6 Archived-At: Cc: "hybi@ietf.org" Subject: Re: [hybi] WebSocket and HSTS X-BeenThere: hybi@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Server-Initiated HTTP List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Sep 2015 08:04:45 -0000 --001a11408c7850f0b6051fd8c0e6 Content-Type: text/plain; charset=UTF-8 Let's just take care of it at the API spec side. For HTTP, the Fetch algorithm has the step while the new HTTP RFCs don't. So, aligned. Takeshi On Sun, Sep 6, 2015 at 2:27 AM, Anne van Kesteren wrote: > I was wondering if you were interested in updating the protocol to > account for HSTS or whether I should patch that in the API standard > somehow. > > See https://www.w3.org/Bugs/Public/show_bug.cgi?id=27554 for details. > > > -- > https://annevankesteren.nl/ > > _______________________________________________ > hybi mailing list > hybi@ietf.org > https://www.ietf.org/mailman/listinfo/hybi > --001a11408c7850f0b6051fd8c0e6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Let's just take care of it at the API spec side.
<= br>
For HTTP, the Fetch algorithm has the step while the new HTTP= RFCs don't. So, aligned.

Takeshi

On Sun, Sep 6, 2015 at 2:27 AM, Anne van Kes= teren <annevk@annevk.nl> wrote:
I was wondering if you were interested in updating the protocol to
account for HSTS or whether I should patch that in the API standard
somehow.

See https://www.w3.org/Bugs/Public/show_bug.c= gi?id=3D27554 for details.


--
https://annevankesteren.nl/

_______________________________________________
hybi mailing list
hybi@ietf.org
https://www.ietf.org/mailman/listinfo/hybi

--001a11408c7850f0b6051fd8c0e6-- From nobody Wed Sep 16 01:20:56 2015 Return-Path: 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 623C31B38AD for ; Wed, 16 Sep 2015 01:20:54 -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 1eq4a198ZAC7 for ; Wed, 16 Sep 2015 01:20:52 -0700 (PDT) Received: from mail-oi0-x233.google.com (mail-oi0-x233.google.com [IPv6:2607:f8b0:4003:c06::233]) (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 3F1D01B38AB for ; Wed, 16 Sep 2015 01:20:52 -0700 (PDT) Received: by oibi136 with SMTP id i136so116877529oib.3 for ; Wed, 16 Sep 2015 01:20:51 -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=AK34NewLyzM6YDW19EeOvi8w+yhzk92G5El8jmsQcgE=; b=QYI75Ex4eErcPH2iez7tjg35+QqQKlyPiqRaDR2Zmw83BTx0tcuhFpoLsh7Mm6tnwO ztjptXFHBVtETMMJE6eqzQdMe/+uFI3HJM72FqEsUNgmefwEWp2kDQCfiQs3LRCzdipF crjg2H6KV1o0323UT4N6c7Pt79URl0WzZkMUikoPDWN/q73U1uY431pQri5k9vfP6ugT a7Tq6iLE5t5kpsGyZJ2rU0ecXlD9i2lmXjk9bth1R1BIrBrdOgVnSRhyDsMYXUGtiZ6d ll/vd1ETV8lTIlbtZ1QdPV0jduzW61pweJua2Tkt9lhiw99xtOyY2QmSULlesnkVFua4 eQgA== 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=AK34NewLyzM6YDW19EeOvi8w+yhzk92G5El8jmsQcgE=; b=EP7T9Grp7y4sroSY2wZwdnArGggI5l+mFCDkJy8ibkkGydJv6q9CgumAdARP2L2aZx W8X5MPOn9NHkdFhK57ATNnYiLqgGMSPZPE0vMhtuda66KrocCE6mifFElwj5/5hh/0+n r6wSbij4vnHTBPYYG5vJQWYyMO/Ggg1Mvb0FpSWRinEJ1+54pllXqpupvls0TE6cPASR sEPCVZi4pvI2/3KhRDNYLgQr5MeqdBlIfgp/N5EHM4NfKUPOX+YmvkM7Hs3PMoVGhBt3 H8WLBURqBD4/vhcjn0QYw/1/wFkg6axSM9RdlBK4jSTYea0WT3H8x8DaP5P3Z2deDsgr RcTw== X-Gm-Message-State: ALoCoQlc3DMfYWRH2ZFc1iFu4aHHzAzKa/pFdJdHL5br3+/qHhT2s757fHhKe0Fd95Nx5+A0xFHt X-Received: by 10.60.175.41 with SMTP id bx9mr22277243oec.46.1442391651465; Wed, 16 Sep 2015 01:20:51 -0700 (PDT) MIME-Version: 1.0 Received: by 10.202.60.4 with HTTP; Wed, 16 Sep 2015 01:20:31 -0700 (PDT) In-Reply-To: References: <55EB2FBF.4080602@gmx.de> From: Takeshi Yoshino Date: Wed, 16 Sep 2015 17:20:31 +0900 Message-ID: To: Anne van Kesteren Content-Type: multipart/alternative; boundary=047d7bd6ab64038006051fd8fa1c Archived-At: Cc: Julian Reschke , "hybi@ietf.org" Subject: Re: [hybi] "Establish a WebSocket Connection" does not allow for cookies X-BeenThere: hybi@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Server-Initiated HTTP List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Sep 2015 08:20:54 -0000 --047d7bd6ab64038006051fd8fa1c Content-Type: text/plain; charset=UTF-8 On Mon, Sep 7, 2015 at 12:12 AM, Anne van Kesteren wrote: > On Sat, Sep 5, 2015 at 8:09 PM, Julian Reschke > wrote: > > On 2015-09-05 19:25, Anne van Kesteren wrote: > >> After the tenth protocol draft this algorithm broke a hook the API > >> standard was using and those authoring the WebSocket API were never > >> notified. > >> > >> See https://www.w3.org/Bugs/Public/show_bug.cgi?id=27869 for details. > >> > >> How do you suggest this gets fixed? > > > > The subject line is misleading. > > It's the name of the algorithm defined in the RFC that takes a set > number of arguments of which headers and/or cookies are not an > acceptable argument. > > Yes, what to do is described in the step, but the identifier of the algorithm is gone. > > > , item 12 in the second > > list is: > > > >> 12. The request MAY include any other header fields, for example, > >> cookies [RFC6265] and/or authentication-related header fields > >> such as the |Authorization| header field [RFC2616], which are > >> processed according to documents that define them. > > This step cannot be influenced from the API. The "request" is > constructed by this algorithm and the influence the API has over it is > carefully defined. > It's not expecting any argument explicitly, but given the history of the spec, I think we should just proceed to influence this by e.g.: Replace the second sentence of the step 9 of https://html.spec.whatwg.org/multipage/comms.html#dom-websocket with When processing the step 12 of the requirements for an opening handshake from a client described in the "Client Requirements" section of the WebSocket protocol specification, include a Cookie header whose value is the cookie-string computed from the user's cookie store and the URL url; for these purposes this is not a "non-HTTP" API. [WSP] [COOKIES] > > > -- > https://annevankesteren.nl/ > > _______________________________________________ > hybi mailing list > hybi@ietf.org > https://www.ietf.org/mailman/listinfo/hybi > --047d7bd6ab64038006051fd8fa1c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On M= on, Sep 7, 2015 at 12:12 AM, Anne van Kesteren <annevk@annevk.nl> wrote:
On Sat, Sep 5, 2015 at 8:0= 9 PM, Julian Reschke <julian.re= schke@gmx.de> wrote:
> On 2015-09-05 19:25, Anne van Kesteren wrote:
>> After the tenth protocol draft this algorithm broke a hook the API=
>> standard was using and those authoring the WebSocket API were neve= r
>> notified.
>>
>> See https://www.w3.org/Bugs/Public/sh= ow_bug.cgi?id=3D27869 for details.
>>
>> How do you suggest this gets fixed?
>
> The subject line is misleading.

It's the name of the algorithm defined in the RFC that takes a s= et
number of arguments of which headers and/or cookies are not an
acceptable argument.


Yes, what to d= o is described in the step, but the identifier of the algorithm is gone.
=C2=A0

> <https://tools.ietf.org/html/rfc6455#section-= 4.1>, item 12 in the second
> list is:
>
>>=C2=A0 =C2=A0 12.=C2=A0 The request MAY include any other header fi= elds, for example,
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0cookies [RFC6265] and/or authenti= cation-related header fields
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0such as the |Authorization| heade= r field [RFC2616], which are
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0processed according to documents = that define them.

This step cannot be influenced from the API. The "request"= is
constructed by this algorithm and the influence the API has over it is
carefully defined.

It's not expecti= ng any argument explicitly, but given the history of the spec, I think we s= hould just proceed to influence this by e.g.:

Repl= ace the second sentence of the step 9 of https://html.spec.whatwg.org/mult= ipage/comms.html#dom-websocket with



--
https://annevankesteren.nl/

_______________________________________________
hybi mailing list
hybi@ietf.org
https://www.ietf.org/mailman/listinfo/hybi

--047d7bd6ab64038006051fd8fa1c-- From nobody Wed Sep 16 01:35:50 2015 Return-Path: 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 3F18C1B38E2 for ; Wed, 16 Sep 2015 01:35:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.078 X-Spam-Level: X-Spam-Status: No, score=-2.078 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, 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 D8lCObXiKw1S for ; Wed, 16 Sep 2015 01:35:47 -0700 (PDT) Received: from homiemail-a2.g.dreamhost.com (homie.mail.dreamhost.com [208.97.132.208]) by ietfa.amsl.com (Postfix) with ESMTP id CFD351B38E0 for ; Wed, 16 Sep 2015 01:35:47 -0700 (PDT) Received: from homiemail-a2.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a2.g.dreamhost.com (Postfix) with ESMTP id 4501328006D for ; Wed, 16 Sep 2015 01:35:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=annevk.nl; h=mime-version :in-reply-to:references:date:message-id:subject:from:to:cc: content-type; s=annevk.nl; bh=LEsoHZEW2qU0dtEdBpDhL0EsX2w=; b=Ol GsnUw1x4ELLhUH5w3bvmHgiWvUo7NwBpAjqYXr9Uqcb9uAdI/7d5ANjEYkCp7cEj Dj141RAvyEauGqIqWnSODpPa8sIAp0HgkI3WUj9MxSgoKkukf5gkUu+8tS/wg9UB nyqGFWWmwAIzDQikIdt6UQ4jf+RHXg4wXhOPqEVXQ= Received: from mail-yk0-f169.google.com (mail-yk0-f169.google.com [209.85.160.169]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: annevk@annevk.nl) by homiemail-a2.g.dreamhost.com (Postfix) with ESMTPSA id 04556280069 for ; Wed, 16 Sep 2015 01:35:47 -0700 (PDT) Received: by ykdg206 with SMTP id g206so211617808ykd.1 for ; Wed, 16 Sep 2015 01:35:46 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.13.255.6 with SMTP id p6mr26025448ywf.46.1442392546263; Wed, 16 Sep 2015 01:35:46 -0700 (PDT) Received: by 10.37.50.2 with HTTP; Wed, 16 Sep 2015 01:35:46 -0700 (PDT) In-Reply-To: References: Date: Wed, 16 Sep 2015 10:35:46 +0200 Message-ID: From: Anne van Kesteren To: Takeshi Yoshino Content-Type: text/plain; charset=UTF-8 Archived-At: Cc: "hybi@ietf.org" Subject: Re: [hybi] WebSocket and HSTS X-BeenThere: hybi@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Server-Initiated HTTP List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Sep 2015 08:35:49 -0000 On Wed, Sep 16, 2015 at 10:04 AM, Takeshi Yoshino wrote: > Let's just take care of it at the API spec side. > > For HTTP, the Fetch algorithm has the step while the new HTTP RFCs don't. > So, aligned. I guess that is fair. See https://github.com/whatwg/html/pull/149 for the proposed change to the HTML Standard (where the WebSocket API is defined). -- https://annevankesteren.nl/ From nobody Wed Sep 16 01:44:03 2015 Return-Path: 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 5C8561B38EC for ; Wed, 16 Sep 2015 01:44:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.078 X-Spam-Level: X-Spam-Status: No, score=-2.078 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, 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 JD2qIs2g2BXU for ; Wed, 16 Sep 2015 01:44:01 -0700 (PDT) Received: from homiemail-a37.g.dreamhost.com (homie.mail.dreamhost.com [208.97.132.208]) by ietfa.amsl.com (Postfix) with ESMTP id 33C321B38E2 for ; Wed, 16 Sep 2015 01:44:01 -0700 (PDT) Received: from homiemail-a37.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a37.g.dreamhost.com (Postfix) with ESMTP id E1634404003 for ; Wed, 16 Sep 2015 01:44:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=annevk.nl; h=mime-version :in-reply-to:references:date:message-id:subject:from:to:cc: content-type; s=annevk.nl; bh=qrPQXFw1fv1vTFUAGFvdO4XD8Y4=; b=O0 ZfUgBaB/P24uJwnI8a1hwl0Qa3Jy5SWXJGd4kgQKsaEo6z9NGLJhdxu4GITx9z98 RDXi1QUvSeNQwWnJ6eKSwdg02hgJZmU17d0GS7UTnIPcSfStfUvPXuUdX8F25DTr xOx6uE03iZFqboXAutSlmyGJme7ec1FvE624ghbr8= Received: from mail-yk0-f182.google.com (mail-yk0-f182.google.com [209.85.160.182]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: annevk@annevk.nl) by homiemail-a37.g.dreamhost.com (Postfix) with ESMTPSA id C60B6404001 for ; Wed, 16 Sep 2015 01:44:00 -0700 (PDT) Received: by ykdt18 with SMTP id t18so191686703ykd.3 for ; Wed, 16 Sep 2015 01:44:00 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.170.209.144 with SMTP id a138mr27286595ykf.5.1442393040156; Wed, 16 Sep 2015 01:44:00 -0700 (PDT) Received: by 10.37.50.2 with HTTP; Wed, 16 Sep 2015 01:43:59 -0700 (PDT) In-Reply-To: References: <55EB2FBF.4080602@gmx.de> Date: Wed, 16 Sep 2015 10:43:59 +0200 Message-ID: From: Anne van Kesteren To: Takeshi Yoshino Content-Type: text/plain; charset=UTF-8 Archived-At: Cc: Julian Reschke , "hybi@ietf.org" Subject: Re: [hybi] "Establish a WebSocket Connection" does not allow for cookies X-BeenThere: hybi@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Server-Initiated HTTP List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Sep 2015 08:44:02 -0000 On Wed, Sep 16, 2015 at 10:20 AM, Takeshi Yoshino wrote: > It's not expecting any argument explicitly, but given the history of the > spec, I think we should just proceed to influence this by e.g.: > > Replace the second sentence of the step 9 of > https://html.spec.whatwg.org/multipage/comms.html#dom-websocket with > > When processing the step 12 of the requirements for an opening handshake > from a client described in the href="https://tools.ietf.org/html/rfc6455#section-4.1">"Client Requirements" > section of the WebSocket protocol specification, include a Cookie > header whose value is the cookie-string computed from the user's cookie > store and the URL url; for these purposes this is not a "non-HTTP" API. > [WSP] [COOKIES] By "given the history of the spec" do you mean that we should not expect a clean fix to appear anytime soon on the IETF side and instead just use this monkey patch? I guess that's fine, it just seems far from ideal, especially given that it was done properly until draft eleven. -- https://annevankesteren.nl/ From nobody Wed Sep 16 01:48:40 2015 Return-Path: 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 104121B3901 for ; Wed, 16 Sep 2015 01:48:39 -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 RAQpeFiSTJ7U for ; Wed, 16 Sep 2015 01:48:37 -0700 (PDT) Received: from mail-oi0-x235.google.com (mail-oi0-x235.google.com [IPv6:2607:f8b0:4003:c06::235]) (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 92D561B38F8 for ; Wed, 16 Sep 2015 01:48:37 -0700 (PDT) Received: by oiev17 with SMTP id v17so117013061oie.1 for ; Wed, 16 Sep 2015 01:48:36 -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=DCk19Szpd+vXTXI1FOnzLZvRHbtLEkE1ea2RyVh8xtc=; b=gzjmPYCnHvqT6MP0JZhgW6vJtuPMVxbgdMQUuttjzvaSVjO5YpG7EA7p7FY1H07rtp miB4sOTJ30zR1qoLPMoBUlSyJTtL4z4p2Em5EfAtzP7fx1BlWw+C+qcleGUb8hsTasFb YbNlpNUbg8yvDjy8VA/ceD5kT5EejBKU+QOx4IxTy0hk9cN9QYyceUKeVa1N82lYBWgW y7veQtG79/l2tE7Nbb69eAGszABIilGmKf/NKrGWIX+77bF17yo2ZoEk8ieF6Wu8a93S h2p2rD0bQSPx5dPIHE62Md8mFHgBdddzSQFhPccZYV2/8gZqTvDTEdyndk/2WnamJv+o 7g7g== 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=DCk19Szpd+vXTXI1FOnzLZvRHbtLEkE1ea2RyVh8xtc=; b=kI1DuW/kREWORmdtyJegj+CxOORZKmOOeGc6uxxWOMCNwfeLTOR1diOXTvlsMG+q+j Np2wT+jJH3a6f4dB/ZfEJPSlo1rg+tTMxSo6aL+9f/upgedEYoYS7pgv0y6JNP5NS3r3 ONLueBrSFjZqQQ0RzwmYcPXNPBmFsl35qglWlMHS8T1fW/hEQ4K5oFWeAi+BpgcnPvc/ jQPJC1IcUVzmZ5rIYfwU+gHGmhO1HaDps84QwLKkZ+Z6+wVkyFEdim+frVkAF96igIUC fKo8NME2aC86stH8jM0XS9mN0RWgZbhmG8HVtzR4vv6bCJbnAlZMt779z1Wes1q5MikI EC4Q== X-Gm-Message-State: ALoCoQkjR86JtRqfYFUiu6N+/U1h2oToruTXZbU8TpHj+bXaj5gpHEZ9kao4i9+R1fbR0C2qDhQX X-Received: by 10.202.232.12 with SMTP id f12mr20354377oih.122.1442393316759; Wed, 16 Sep 2015 01:48:36 -0700 (PDT) MIME-Version: 1.0 Received: by 10.202.60.4 with HTTP; Wed, 16 Sep 2015 01:48:16 -0700 (PDT) In-Reply-To: References: <55EB2FBF.4080602@gmx.de> From: Takeshi Yoshino Date: Wed, 16 Sep 2015 17:48:16 +0900 Message-ID: To: Anne van Kesteren Content-Type: multipart/alternative; boundary=001a11408b6e45e2b6051fd95d1c Archived-At: Cc: Julian Reschke , "hybi@ietf.org" Subject: Re: [hybi] "Establish a WebSocket Connection" does not allow for cookies X-BeenThere: hybi@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Server-Initiated HTTP List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Sep 2015 08:48:39 -0000 --001a11408b6e45e2b6051fd95d1c Content-Type: text/plain; charset=UTF-8 On Wed, Sep 16, 2015 at 5:43 PM, Anne van Kesteren wrote: > On Wed, Sep 16, 2015 at 10:20 AM, Takeshi Yoshino > wrote: > > It's not expecting any argument explicitly, but given the history of the > > spec, I think we should just proceed to influence this by e.g.: > > > > Replace the second sentence of the step 9 of > > https://html.spec.whatwg.org/multipage/comms.html#dom-websocket with > > > > When processing the step 12 of the requirements for an opening handshake > > from a client described in the > href="https://tools.ietf.org/html/rfc6455#section-4.1">"Client > Requirements" > > section of the WebSocket protocol specification, include a Cookie > > header whose value is the cookie-string computed from the user's cookie > > store and the URL url; for these purposes this is not a "non-HTTP" API. > > [WSP] [COOKIES] > > By "given the history of the spec" do you mean that we should not > expect a clean fix to appear anytime soon on the IETF side and instead > just use this monkey patch? I guess that's fine, it just seems far > I meant that we can see this as expecting an argument though it's not explicitly expecting. In response to your comment "we cannot influence this sentence". > from ideal, especially given that it was done properly until draft > eleven. > > Ideally. Julian, do you think we can revive the identifier with a little work? What's your thoughts after Anne's recent reply. > > -- > https://annevankesteren.nl/ > --001a11408b6e45e2b6051fd95d1c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On W= ed, Sep 16, 2015 at 5:43 PM, Anne van Kesteren <annevk@annevk.nl> wrote:
On Wed, Sep = 16, 2015 at 10:20 AM, Takeshi Yoshino <tyoshino@google.com> wrote:
> It's not expecting any argument explicitly, but given the history = of the
> spec, I think we should just proceed to influence this by e.g.:
>
> Replace the second sentence of the step 9 of
> https://html.spec.whatwg.org/mul= tipage/comms.html#dom-websocket with
>
> When processing the step 12 of the requirements for an opening handsha= ke
> from a client described in the <a
> href=3D"https://tools.ietf.org/html/rfc6455= #section-4.1">"Client Requirements"
> section of=C2=A0 the WebSocket protocol specification</a>, inclu= de a Cookie
> header whose value is the cookie-string computed from the user's c= ookie
> store and the URL url; for these purposes this is not a "non-HTTP= " API.
> [WSP] [COOKIES]

By "given the history of the spec" do you mean that we sho= uld not
expect a clean fix to appear anytime soon on the IETF side and instead
just use this monkey patch? I guess that's fine, it just seems far
<= /blockquote>

I meant that we can see this as expecting a= n argument though it's not explicitly expecting. In response to your co= mment "we cannot influence this sentence".
=C2=A0
=
from ideal, especially given that it was done properly until draft
eleven.


Ideally. Julian, do you think we can revive the iden= tifier with a little work? What's your thoughts after Anne's recent= reply.
=C2=A0

--
https://annevankesteren.nl/

--001a11408b6e45e2b6051fd95d1c-- From matt@bonneau.com Wed Sep 16 10:09:48 2015 Return-Path: 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 BCA641B3B70 for ; Wed, 16 Sep 2015 10:09:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.078 X-Spam-Level: X-Spam-Status: No, score=-0.078 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 vzbQ4ElqKxAB for ; Wed, 16 Sep 2015 10:09:46 -0700 (PDT) Received: from mail-qg0-f52.google.com (mail-qg0-f52.google.com [209.85.192.52]) (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 10CD11B3AFC for ; Wed, 16 Sep 2015 10:09:46 -0700 (PDT) Received: by qgt47 with SMTP id 47so176917626qgt.2 for ; Wed, 16 Sep 2015 10:09:45 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=XagJhVdE6pVfwp7FpFDJf4VrWBxiw/NukRz1OGDxpQQ=; b=ZrLb6MOSd5g+KVrtcNUXsKCvfrHg9/EfXOUPiqiM5mOINYr7vIqTy9w7VI4hJ+ajm8 qMoE8yjL/Q7vaVCrA5w8QfYEii5W1Hwy1DyoRfapCmWHJTr+vTuNAhV7yARXQzIfrWem j1TVdKsZ/uTMgcw3Xn8nEGE2JcMkbka79PAkqbYrGsrNlxuDYKkQ1BZ8N1290eT1P8BI Qb+B+NxI1eCAusa4vKlkkbzvblLuKhYevgJykmPcL/sZ0vpUmN4vJLbWDHU09erQg8tE KDgwrU6akpUMVn3kzTw+sR2Xv06/7eTLxXStcNH2sUTVf+IUMdt0SN82XOUB8qa2i3CK Bdiw== X-Gm-Message-State: ALoCoQmh0NHlxzl2HTW0PN0pqSDZ6XjtRP5T6MtvAJtJPkPNfXjSTLcGipOn9xEB50iEE45TwnXU MIME-Version: 1.0 X-Received: by 10.140.235.9 with SMTP id g9mr40842705qhc.14.1442423384884; Wed, 16 Sep 2015 10:09:44 -0700 (PDT) Sender: matt@bonneau.com Received: by 10.55.162.194 with HTTP; Wed, 16 Sep 2015 10:09:44 -0700 (PDT) In-Reply-To: <55F73AEB.70104@tavendo.de> References: <20150824112514.18998.33071.idtracker@ietfa.amsl.com> <7730FEFF-FA09-4278-A8BF-B3325E6C2EC1@ericsson.com> <55F5E021.2000803@tavendo.de> <2B9B48179856DC4FA00C93C79EB7E64A0E950202@ESESSMB108.ericsson.se> <55F6AFA1.9070404@tavendo.de> <55F73AEB.70104@tavendo.de> Date: Wed, 16 Sep 2015 13:09:44 -0400 X-Google-Sender-Auth: _96KCWguGjLgJqoy4bDsXW9kZNw Message-ID: From: Matt Bonneau To: Tobias Oberstein Content-Type: multipart/alternative; boundary=001a113569d4797340051fe05d4c Archived-At: Cc: "hybi@ietf.org" , Barry Leiba Subject: Re: [hybi] I-D Action: draft-ietf-hybi-permessage-compression-28.txt X-BeenThere: hybi@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Server-Initiated HTTP List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Sep 2015 17:47:43 -0000 --001a113569d4797340051fe05d4c Content-Type: text/plain; charset=UTF-8 Hi Barry and Tobias, I would be willing to help out with the RFC process on WAMP. I have made pretty significant investments of time in creating implementations and working with the spec and also use WAMP regularly. I would welcome further development through the RFC process. Regards, Matt Bonneau On Mon, Sep 14, 2015 at 5:23 PM, Tobias Oberstein < tobias.oberstein@tavendo.de> wrote: > How "much" interest is needed? How should we "proof"? Should I ask all to >>> speak up on this mailing list? >>> >> >> It's hard to put a number on it, but there needs to be enough interest >> and commitment to participate that we can rely on progressing >> documents and getting meaningful review. We have been having a lot of >> trouble with that over the past couple of *years*, so it's not just a >> moderate slowdown. >> > > Thanks for explaining and background. I now understand that real world > usage and takeup is only one factor, but enough interest to do the concrete > work on a spec document is what counts. Makes sense. To get a high quality > spec, there needs to be peer review and discussion. It's part of the IETF > mantra I guess, and I totally buy that. > > That said, if we really *do* have enough commitment, I'm willing to >> recharter the working group. I can't speak for the chairs about >> > > Awesome! Would you give us a bit time to organize enough commitment and > write a draft? Some weeks before closing the WG (if we can't deliver)? > > whether they're willing to continue, but perhaps we could get new >> chairs to take it forward -- Salvatore and Gabriel have chaired this >> working group for a long time now. >> >> So do we need a draft RFC written _before_ we can request to recharter the >>> WG? >>> >> >> We don't *need* it, though a draft and some reviews of it would be >> some evidence that there's enough interest. >> > > Ok, we can prepare a draft according to RFC style from this spec document > ("WAMP basic profile") that we have: > > https://github.com/tavendo/WAMP/blob/master/spec/basic.md > > That spec has been extensively discussed and has gone through many > iterations from Mar 2012 to now. > > Discussion is on GitHub (94 closed, 67 open issues right now) and the WAMP > mailing list (171 threads, 151 subscribers). > > The point is that implementors are less interested in implementing >> websocket things, now that http/2 is here. Layering things on >> websockets might not be very useful if implementors are moving to >> http/2 instead, for such functions in the future. >> > > FWIW, WAMP originally could only run on top of WebSocket. And it's still > the most used "transport". But WAMP nowerdays can _also_ run over RawSocket > (essentially, minimally framed TCP with some handshake sugar) and > HTTP-Longpoll, and don't see why we couldn't specify a HTTP/2 "transport > binding" (that's WAMP lingo for defining a mapping of WAMP to an underlying > transport). > > WAMP-over-WebSocket is definitely the most important one, as it is the > only thing that (today) can run right into all browsers. It is also the > only transport that provides full, transparent payload compresssion - > thanks to the WebSocket compression extension. > > But, again, if there really is enough interest in implementing new >> function on websockets, and we can see that interest in commitment to >> work on the specs, then that might be fine. >> > > Thanks! Please give us some time before closing the WG. Once the WG would > have closed, I guess the bar would be much higher .. and where should we > take it then? I have skimmed through the different IETF art areas, and the > WGs and charters for the "Applications and Real-Time Area" in particular, > and it appears to me, that WAMP would fit the Hybi-WG's mission .. > > Cheers, > /Tobias > > > _______________________________________________ > hybi mailing list > hybi@ietf.org > https://www.ietf.org/mailman/listinfo/hybi > --001a113569d4797340051fe05d4c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Barry and Tobias,

I would be willing= to help out with the RFC process on WAMP.

I have = made pretty significant investments of time in creating implementations and= working with the spec and also use WAMP regularly. I would welcome further= development through the RFC process.

Regards,
Matt Bonneau=C2=A0

On Mon, Sep 14, 2015 at 5:23 PM, Tobias Oberstein <tobias.oberstein@tavendo.de> wrote:
How "much" interest is needed? How should we "proof"? S= hould I ask all to
speak up on this mailing list?

It's hard to put a number on it, but there needs to be enough interest<= br> and commitment to participate that we can rely on progressing
documents and getting meaningful review.=C2=A0 We have been having a lot of=
trouble with that over the past couple of *years*, so it's not just a moderate slowdown.

Thanks for explaining and background. I now understand that real world usag= e and takeup is only one factor, but enough interest to do the concrete wor= k on a spec document is what counts. Makes sense. To get a high quality spe= c, there needs to be peer review and discussion. It's part of the IETF = mantra I guess, and I totally buy that.

That said, if we really *do* have enough commitment, I'm willing to
recharter the working group.=C2=A0 I can't speak for the chairs about

Awesome! Would you give us a bit time to organize enough commitment and wri= te a draft? Some weeks before closing the WG (if we can't deliver)?

whether they're willing to continue, but perhaps we could get new
chairs to take it forward -- Salvatore and Gabriel have chaired this
working group for a long time now.

So do we need a draft RFC written _before_ we can request to recharter the<= br> WG?

We don't *need* it, though a draft and some reviews of it would be
some evidence that there's enough interest.

Ok, we can prepare a draft according to RFC style from this spec document (= "WAMP basic profile") that we have:

https://github.com/tavendo/WAMP/blob/mast= er/spec/basic.md

That spec has been extensively discussed and has gone through many iteratio= ns from Mar 2012 to now.

Discussion is on GitHub (94 closed, 67 open issues right now) and the WAMP = mailing list (171 threads, 151 subscribers).

The point is that implementors are less interested in implementing
websocket things, now that http/2 is here.=C2=A0 Layering things on
websockets might not be very useful if implementors are moving to
http/2 instead, for such functions in the future.

FWIW, WAMP originally could only run on top of WebSocket. And it's stil= l the most used "transport". But WAMP nowerdays can _also_ run ov= er RawSocket (essentially, minimally framed TCP with some handshake sugar) = and HTTP-Longpoll, and don't see why we couldn't specify a HTTP/2 &= quot;transport binding" (that's WAMP lingo for defining a mapping = of WAMP to an underlying transport).

WAMP-over-WebSocket is definitely the most important one, as it is the only= thing that (today) can run right into all browsers. It is also the only tr= ansport that provides full, transparent payload compresssion - thanks to th= e WebSocket compression extension.

But, again, if there really is enough interest in implementing new
function on websockets, and we can see that interest in commitment to
work on the specs, then that might be fine.

Thanks! Please give us some time before closing the WG. Once the WG would h= ave closed, I guess the bar would be much higher .. and where should we tak= e it then? I have skimmed through the different IETF art areas, and the WGs= and charters for the "Applications and Real-Time Area" in partic= ular, and it appears to me, that WAMP would fit the Hybi-WG's mission .= .

Cheers,
/Tobias


_______________________________________________
hybi mailing list
hybi@ietf.org
https://www.ietf.org/mailman/listinfo/hybi

--001a113569d4797340051fe05d4c-- From nobody Thu Sep 17 05:54:56 2015 Return-Path: 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 038DB1B2DE5 for ; Thu, 17 Sep 2015 05:54:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.201 X-Spam-Level: X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] 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 znVu60jgR2Xb for ; Thu, 17 Sep 2015 05:54:53 -0700 (PDT) Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 568471B2DEC for ; Thu, 17 Sep 2015 05:54:50 -0700 (PDT) X-AuditID: c1b4fb2d-f79626d000004282-0e-55fab818fef0 Received: from ESESSHC020.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 9B.B0.17026.818BAF55; Thu, 17 Sep 2015 14:54:48 +0200 (CEST) Received: from ESESSMB109.ericsson.se ([169.254.9.178]) by ESESSHC020.ericsson.se ([153.88.183.78]) with mapi id 14.03.0248.002; Thu, 17 Sep 2015 14:54:47 +0200 From: Salvatore Loreto To: Anne van Kesteren , Julian Reschke Thread-Topic: [hybi] "Establish a WebSocket Connection" does not allow for cookies Thread-Index: AQHQ5//cXjpSR1mS+kyyBSl2Pt2hRZ4uGl2AgAFg/ACAEUSLQA== Date: Thu, 17 Sep 2015 12:54:47 +0000 Message-ID: <2B9B48179856DC4FA00C93C79EB7E64A0E965F03@ESESSMB109.ericsson.se> References: <55EB2FBF.4080602@gmx.de> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [153.88.183.146] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrGLMWRmVeSWpSXmKPExsUyM+Jvja7Ejl+hBj8PKlsc+aZm8f7lNiaL zQ/fsDowe1y73sHs8eFjnMeSJT+ZApijuGxSUnMyy1KL9O0SuDLmT7jFUtDHW9H04SRzA+NZ ri5GTg4JAROJviUXGSFsMYkL99azdTFycQgJHGWUOHD6OhOEs4RR4tT7H0wgVWwCZhLPH25h BrFFBIIkZj3eDRZnFlCWuHpsBQuILSwQLPFw3nwWiJoQiTP3jrNC2E4S11d3sYPYLAKqEld3 rmMDsXkFfCUOLz7PCrFsM6NEx7//QCdxcHAKBEosup8IUsMIdN33U2ugdolL3HoynwniagGJ JXvOM0PYohIvH/9jhbCVJH5suMQCUa8jsWD3JzYIW1ti2cLXzBB7BSVOznzCMoFRbBaSsbOQ tMxC0jILScsCRpZVjKLFqcXFuelGxnqpRZnJxcX5eXp5qSWbGIERdXDLb90djKtfOx5iFOBg VOLhfRD2K1SINbGsuDL3EKM0B4uSOG8L04NQIYH0xJLU7NTUgtSi+KLSnNTiQ4xMHJxSDYxd UfmyC35GdlWwKKhtmyIh8TVy3cvPldoNM6Z4VhtUzq2eqOYd1WcouC/8ydGUozNaHXhf7/2/ vqdWJYd5+4VpT4+2bXzmPnFBfs9085WZR2YknjE07nOccGhbbOWLvKI5X3VmrZRas/NDj23B hKxj268fuLfQviv//0wTIb5Eh4/z+s46bn+nxFKckWioxVxUnAgANQGowYkCAAA= Archived-At: Cc: "hybi@ietf.org" Subject: Re: [hybi] "Establish a WebSocket Connection" does not allow for cookies X-BeenThere: hybi@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Server-Initiated HTTP List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 12:54:55 -0000 Not completely sure, but maybe we can worn on an Errata to clarify this br Salvatore -----Original Message----- From: hybi [mailto:hybi-bounces@ietf.org] On Behalf Of Anne van Kesteren Sent: den 6 september 2015 17:12 To: Julian Reschke Cc: hybi@ietf.org Subject: Re: [hybi] "Establish a WebSocket Connection" does not allow for c= ookies On Sat, Sep 5, 2015 at 8:09 PM, Julian Reschke wrot= e: > On 2015-09-05 19:25, Anne van Kesteren wrote: >> After the tenth protocol draft this algorithm broke a hook the API=20 >> standard was using and those authoring the WebSocket API were never=20 >> notified. >> >> See https://www.w3.org/Bugs/Public/show_bug.cgi?id=3D27869 for details. >> >> How do you suggest this gets fixed? > > The subject line is misleading. It's the name of the algorithm defined in the RFC that takes a set number o= f arguments of which headers and/or cookies are not an acceptable argument. > , item 12 in the=20 > second list is: > >> 12. The request MAY include any other header fields, for example, >> cookies [RFC6265] and/or authentication-related header fields >> such as the |Authorization| header field [RFC2616], which are >> processed according to documents that define them. This step cannot be influenced from the API. The "request" is constructed b= y this algorithm and the influence the API has over it is carefully defined= . -- https://annevankesteren.nl/ _______________________________________________ hybi mailing list hybi@ietf.org https://www.ietf.org/mailman/listinfo/hybi From nobody Thu Sep 17 08:14:19 2015 Return-Path: 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 84C421A1B60 for ; 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-Level: 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X5J-AKX9KuMC for ; Thu, 17 Sep 2015 08:14:15 -0700 (PDT) Received: from EXHUB020-4.exch020.serverdata.net (exhub020-4.exch020.serverdata.net [206.225.164.31]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB6591A86E9 for ; Thu, 17 Sep 2015 08:14:15 -0700 (PDT) Received: from [192.168.1.140] (88.217.36.200) by smtpx20.serverdata.net (206.225.164.36) with Microsoft SMTP Server (TLS) id 8.3.377.0; Thu, 17 Sep 2015 08:14:14 -0700 From: Tobias Oberstein To: "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: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 15:14:17 -0000 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 From nobody Fri Sep 18 19:01:37 2015 Return-Path: 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 54D3B1B414E for ; Fri, 18 Sep 2015 19:01:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.078 X-Spam-Level: X-Spam-Status: No, score=-0.078 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 QGcKlWp06yBR for ; Fri, 18 Sep 2015 19:01:33 -0700 (PDT) Received: from mail-ig0-f176.google.com (mail-ig0-f176.google.com [209.85.213.176]) (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 BC7031B414D for ; Fri, 18 Sep 2015 19:01:33 -0700 (PDT) Received: by igcrk20 with SMTP id rk20so29811772igc.1 for ; Fri, 18 Sep 2015 19:01:33 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=MCFKaq/a5Io+P362rL5/E0MwvkjrG7P0K/DXq/tZZFA=; b=gzr6KMX3YiaQXc4+tXwu6/jUezCMYw9Jbk3FBvRB+xHbkGHzx9A00wP707EL0lYEvg Rntz1utoIZjy0hpZG60/ENDdTGOoSKGCIFN65ZQiQFxAy1HCXYxcr9w5lBgFrzvIrQ3G 2nbV6IvHt0guI8IU05sukbHjjdS1HkrzP2QMuJGBkoJ++TBgDcIzLD1W0EsL0hKUkyr1 WRiW3YUQv7pbiA7OT4CvM4GLGUOVldOeAAc3Odf73IGp9FGqtarM3jTrLt1oJvNxw0BI w7+PfuELJzYKpz9OprKRnL6CFIi7E33+lZ/xn/hegMI0Jqfi6FB4uCBYLo3SUoBIuuiP ALKA== X-Gm-Message-State: ALoCoQkzVzztFonSNWeG3SXAk4TvUzRJu6IPQX7Nrc6KqBE/a3I8AFpKKjbvcWpCG1SfPs8TrUuE MIME-Version: 1.0 X-Received: by 10.50.60.100 with SMTP id g4mr1108262igr.41.1442628093034; Fri, 18 Sep 2015 19:01:33 -0700 (PDT) Received: by 10.79.0.136 with HTTP; Fri, 18 Sep 2015 19:01:32 -0700 (PDT) Date: Fri, 18 Sep 2015 21:01:32 -0500 Message-ID: From: Scott Morgan To: hybi@ietf.org Content-Type: multipart/alternative; boundary=047d7b10d10b0765e705201007e6 Archived-At: Subject: Re: [hybi] WAMP and protocol layers riding on Web Sockets and Java Web Socket implementation X-BeenThere: hybi@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Server-Initiated HTTP List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Sep 2015 02:01:35 -0000 --047d7b10d10b0765e705201007e6 Content-Type: text/plain; charset=UTF-8 Hi All, Tobias brought up WAMP a few days ago, and I have also done some work on a similar topic. My idea is more limited to routing, history (of a message), and sender information only and is here (very informal); https://github.com/adligo/taxi.adligo.org/blob/master/README.txt https://github.com/adligo/taxi.adligo.org/blob/master/diagrams/taxi_deployments.png https://github.com/adligo/taxi.adligo.org/blob/master/diagrams/taxi_download.png https://github.com/adligo/taxi.adligo.org/blob/master/diagrams/taxi_upload.png https://github.com/adligo/taxi.adligo.org/blob/master/diagrams/taxi_use_cases.png I am interested in any comments to TAXI which I am planning to put on top of Web Sockets sometime in the future. Please use the github issues feature for comments on TAXI. @Tobias I have some comments on WAMP https://github.com/adligo/taxi.adligo.org/blob/master/comments_on_similar_protocols/WAMP.txt Everyone, is there a list of protocol layers somewhere that could be placed on top of Web Sockets somewhere for things like publish, subscribe, RPC? Also, I have a Java implementation of Web Sockets which I am trying to get the Apache HttpComponents or JCP (I can't afford a membership) groups to pick up. If they are not interested does anyone know of a good source of funding for maintenance (i.e. Grants). http://cvs.adligo.org/viewvc/aws_client http://cvs.adligo.org/viewvc/aws_client_tests They will eventually end up on github; https://www.linkedin.com/pulse/fabricate-tests4j-now-githubcom-scott-morgan Cheers, Scott --047d7b10d10b0765e705201007e6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi All,

=C2=A0 =C2=A0Tobias brought u= p WAMP a few days ago, and I have also done some work on a similar topic. = =C2=A0 =C2=A0My idea is more limited to routing, history (of a message), an= d sender information only and is here (very informal);
https://github.com= /adligo/taxi.adligo.org/blob/master/diagrams/taxi_download.png

I am interested in any comments to= TAXI which I am planning to put on top of Web Sockets sometime in the futu= re.=C2=A0 Please use the github issues feature for comments on TAXI.
<= div class=3D"gmail_extra">
@Tobias I have some comments on WAMP
=
Everyone, is there a list of protocol la= yers somewhere that could be placed on top of Web Sockets somewhere for thi= ngs like publish, subscribe, RPC?

=
Also, I have a Java implementation of We= b Sockets which I am trying to get the Apache HttpComponents or JCP (I can&= #39;t afford a membership) groups to pick up.=C2=A0 If they are not=C2=A0interested does anyone know of a good= source of funding for=C2=A0maintenance=C2=A0(i.e. Grants).
=09 =09 =09

Cheers,

Scott

--047d7b10d10b0765e705201007e6-- From nobody Sun Sep 27 08:41:22 2015 Return-Path: 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 A68671B2ADC for ; Sun, 27 Sep 2015 08:41:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.1 X-Spam-Level: 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FGfaZpk3aMWf for ; Sun, 27 Sep 2015 08:41:19 -0700 (PDT) Received: from EXHUB020-4.exch020.serverdata.net (exhub020-4.exch020.serverdata.net [206.225.164.31]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DF9A51B2ADB for ; Sun, 27 Sep 2015 08:41:18 -0700 (PDT) Received: from [192.168.1.140] (88.217.49.51) by smtpx20.serverdata.net (206.225.164.36) with Microsoft SMTP Server (TLS) id 8.3.377.0; Sun, 27 Sep 2015 08:41:17 -0700 To: "hybi@ietf.org" References: <55FAD8C4.5080706@tavendo.de> From: Tobias Oberstein Message-ID: <56080E1B.4000107@tavendo.de> Date: Sun, 27 Sep 2015 17:41:15 +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: <55FAD8C4.5080706@tavendo.de> Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit Archived-At: Cc: =?UTF-8?Q?Alexander_G=c3=b6dde?= , 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Sep 2015 15:41:20 -0000 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? 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 > From nobody Sun Sep 27 19:21:29 2015 Return-Path: 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 ; 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 ; 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 ; Sun, 27 Sep 2015 19:21:24 -0700 (PDT) Received: by oixx17 with SMTP id x17so83291982oix.0 for ; 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 Date: Mon, 28 Sep 2015 11:21:03 +0900 Message-ID: To: Tobias Oberstein Content-Type: multipart/alternative; boundary=001a113ce59c8fd82a0520c55a8f Archived-At: Cc: =?UTF-8?Q?Alexander_G=C3=B6dde?= , "hybi@ietf.org" , Barry Leiba 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Sep 2015 02:21:27 -0000 --001a113ce59c8fd82a0520c55a8f Content-Type: text/plain; charset=UTF-8 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 > --001a113ce59c8fd82a0520c55a8f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
=C2=A0
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:=C2=A0 =C2=A0http://wamp.ws/
Specification:=C2=A0 https://github.com/tavendo/WAMP= /tree/master/spec
Mailing list:=C2=A0 =C2=A0https://groups.google.com/fo= rum/#!forum/wampws
Chat room:=C2=A0 =C2=A0 =C2=A0 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

--001a113ce59c8fd82a0520c55a8f-- From nobody Sun Sep 27 19:35:14 2015 Return-Path: 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 ; 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 ; 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 ; Sun, 27 Sep 2015 19:35:10 -0700 (PDT) Received: by obcxm10 with SMTP id xm10so15456469obc.3 for ; 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: References: <55FAD8C4.5080706@tavendo.de> <56080E1B.4000107@tavendo.de> From: Takeshi Yoshino Date: Mon, 28 Sep 2015 11:34:50 +0900 Message-ID: To: Tobias Oberstein Content-Type: multipart/alternative; boundary=e89a8ff2546ed3d93a0520c58b68 Archived-At: Cc: =?UTF-8?Q?Alexander_G=C3=B6dde?= , "hybi@ietf.org" , Barry Leiba 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Sep 2015 02:35:12 -0000 --e89a8ff2546ed3d93a0520c58b68 Content-Type: text/plain; charset=UTF-8 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 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 >> > > --e89a8ff2546ed3d93a0520c58b68 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Once the I-D gets adopted (e.g. https://www.ietf.org/mai= l-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 d= iscussion/editing again, and then the chairs sends it to IESG, i.e. AD, Bar= ry.


Takeshi

Use=C2=A0https://tools.ietf.org/tools/idnits/ to see nits in= your I-D.

Then, submit at https://datatracker.ietf.org/su= bmit/ (or just submit w/o idnits and you'll see rejection if there&= #39;s any nits). The submitted I-D shows up on tools.ietf.org.


<= /div>
=C2=A0
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:=C2=A0 =C2=A0http://wamp.ws/
Specification:=C2=A0 https://github.com/tavendo/WAMP= /tree/master/spec
Mailing list:=C2=A0 =C2=A0https://groups.google.com/fo= rum/#!forum/wampws
Chat room:=C2=A0 =C2=A0 =C2=A0 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


--e89a8ff2546ed3d93a0520c58b68-- From nobody Mon Sep 28 03:01:30 2015 Return-Path: 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 ; 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 ; 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 ; 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 References: <55FAD8C4.5080706@tavendo.de> <56080E1B.4000107@tavendo.de> From: Tobias Oberstein 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: Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit Archived-At: Cc: =?UTF-8?Q?Alexander_G=c3=b6dde?= , "hybi@ietf.org" , Barry Leiba 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 . > > 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 > >