Re: WiSH: A General Purpose Message Framing over Byte-Stream Oriented Wire Protocols (HTTP)

Takeshi Yoshino <tyoshino@google.com> Fri, 16 December 2016 04:10 UTC

Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CEA5912947E for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 15 Dec 2016 20:10:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.896
X-Spam-Level:
X-Spam-Status: No, score=-9.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-2.896, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
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 RBKtC6WN0WIy for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 15 Dec 2016 20:10:51 -0800 (PST)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7F69A126B6D for <httpbisa-archive-bis2Juki@lists.ietf.org>; Thu, 15 Dec 2016 20:02:38 -0800 (PST)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1cHjfr-0005B5-NO for ietf-http-wg-dist@listhub.w3.org; Fri, 16 Dec 2016 03:59:11 +0000
Resent-Date: Fri, 16 Dec 2016 03:59:11 +0000
Resent-Message-Id: <E1cHjfr-0005B5-NO@frink.w3.org>
Received: from mimas.w3.org ([128.30.52.79]) by frink.w3.org with esmtps (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <tyoshino@google.com>) id 1cHjfb-00059X-SW for ietf-http-wg@listhub.w3.org; Fri, 16 Dec 2016 03:58:55 +0000
Received: from mail-it0-f45.google.com ([209.85.214.45]) by mimas.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from <tyoshino@google.com>) id 1cHjfV-0008Lj-Hs for ietf-http-wg@w3.org; Fri, 16 Dec 2016 03:58:50 +0000
Received: by mail-it0-f45.google.com with SMTP id j191so9886471ita.1 for <ietf-http-wg@w3.org>; Thu, 15 Dec 2016 19:58:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=p8VEk5/eDV0ST3/cxKVcCC97SY54jhdtZOEYkBNGDfE=; b=KGKCvVjQQCxAL0hs/tWhoXftesyoM4dqTUbfxc7pOl+tl/+leb2sSnmzs0I/Td7hV1 fRAqSinMdCiWwEIE5RWJJdvgtIVqz9ekp4v+kpRHzeUpxzhqJK1gCwQm5j/iUb1zJXiA hHK9/tOK6oYyomtZoDuWIAwfygocpOnxMld0IKIVnhv5E4R9PcSP940ebCcbgtVfLJu4 ciFehc0b84hNKf83mRmF3mrEh8HHnwPR7jRFZtIRchyfWBuJpvmrPlS6jHuwZHJr8RrT Bj5ehp4egFLIbOG6Tv1X7xK/yNgOYjzb7T/gmFqLSX7RvijKY7jC3ZYHPpzO6sqzL537 B+LQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=p8VEk5/eDV0ST3/cxKVcCC97SY54jhdtZOEYkBNGDfE=; b=Oz3vzzmCPoGvBxJf8T88TS4tWqciWVvOml9Y7XPK00xKiScbthkWmPC2ryxXlF2ynA v+cWYSesChAdQCrqh88IEspJQZGYPzUDA3BdInvhy/FAmX9hRJXqjSbn8Ktxli8Rl/a3 08Y+rmAN9Pcp2PKioy5W133zg/5YV4oo+A9D/Nh+52ViBQinoqdigxvWs+GPKwLpxjG/ 2cBxudxZ2QEaH4ItOVSlGYHC9morJHfwpV34UPV2YGJcHio1FKdtMCLwbtlC76CY8nRE mr1DwvdqUP1ahsJry+kbNO6392bgjLlHLp7trOxnC6CDv5PnITYAzzdOG0KJrDYB60QS 6eTQ==
X-Gm-Message-State: AKaTC03aUyDTo4ygXh0erbnc90Vecxe8FaUiprdeRGALs8fpJhcsyDrtqwGeCtdXHnrMefyYZJa6DCWyGzWhZ6lu
X-Received: by 10.36.3.1 with SMTP id e1mr1731446ite.97.1481860703099; Thu, 15 Dec 2016 19:58:23 -0800 (PST)
MIME-Version: 1.0
Received: by 10.79.4.14 with HTTP; Thu, 15 Dec 2016 19:58:01 -0800 (PST)
In-Reply-To: <3125F5F9-FC15-46A7-9B94-4DCC4F3D823E@isode.com>
References: <CAH9hSJZB0SyFiqLqLjd9R-T11yTa12Ekb-H8hYwfc6FeOjD2xQ@mail.gmail.com> <CAP8-FqmU+uBas5zH8oQHkt0zh18YrBm-O-umGPGMkLAjShw1Gw@mail.gmail.com> <CAH9hSJa10DLSozTpXjETyFX0bVYqfRbRFJnmFQNRGeSuZVKWPQ@mail.gmail.com> <CAG-EYChszHdWhp=o+fdOW+pAN90t61MExzsLnteM3tmf9=N0Yw@mail.gmail.com> <CAH9hSJbNk83FT0WqB1tHJvEfaU5CMoAaKRdvy8NTb4zgEUdzBw@mail.gmail.com> <CAG-EYCjwptZcsHeDKwyRBhLTREEC4zxXxtTZvNLe2m1ei2r55g@mail.gmail.com> <437A6E14-03A9-42DD-A4B8-921C80EC5729@mnot.net> <1480035079.3044.1.camel@warmcat.com> <8E039C1D-A9B6-40E4-937E-A55D327FBDC5@mnot.net> <1480041123.3044.3.camel@warmcat.com> <20161125065208.GB4488@1wt.eu> <CAH9hSJacZp4LqAp61yCTsVqSeomSc5aZfTFjQUfbmHrOqr3VGg@mail.gmail.com> <DCFCC7B0-717E-496A-8B4D-C409A1B965F0@mnot.net> <CAG-EYCiVExcyHLoXB1ixQCKduxUPTVOnVX1XrmFJ3b72Y8AAFg@mail.gmail.com> <3125F5F9-FC15-46A7-9B94-4DCC4F3D823E@isode.com>
From: Takeshi Yoshino <tyoshino@google.com>
Date: Fri, 16 Dec 2016 12:58:01 +0900
Message-ID: <CAH9hSJaQKkZJ1ndg6Gy2J63dKezMstEOp+aPTWewKiJQkhdZvA@mail.gmail.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
Cc: Van Catha <vans554@gmail.com>, Mark Nottingham <mnot@mnot.net>, Willy Tarreau <w@1wt.eu>, Andy Green <andy@warmcat.com>, "ietf-http-wg@w3.org Group" <ietf-http-wg@w3.org>, Wenbo Zhu <wenboz@google.com>, Martin Thomson <martin.thomson@gmail.com>
Content-Type: multipart/alternative; boundary=001a1144a00cd0edc90543be9456
Received-SPF: pass client-ip=209.85.214.45; envelope-from=tyoshino@google.com; helo=mail-it0-f45.google.com
X-W3C-Hub-Spam-Status: No, score=-7.8
X-W3C-Hub-Spam-Report: AWL=2.064, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.099, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, W3C_AA=-1, W3C_DB=-1, W3C_IRA=-1, W3C_WL=-1
X-W3C-Scan-Sig: mimas.w3.org 1cHjfV-0008Lj-Hs 61ebf62fa4c9f1c46829837ee25ef639
X-Original-To: ietf-http-wg@w3.org
Subject: Re: WiSH: A General Purpose Message Framing over Byte-Stream Oriented Wire Protocols (HTTP)
Archived-At: <http://www.w3.org/mid/CAH9hSJaQKkZJ1ndg6Gy2J63dKezMstEOp+aPTWewKiJQkhdZvA@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/33203
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

Thank you everyone for all the feedback.

I'd like to start some thread soon at HyBi to get more feedback to WiSH
from WebSocket users, and also figure out how to standardize it in
parallel. I've also shared the idea briefly with annevk at WHATWG and going
to start some discussion there, too.

Again, thank you.

Takeshi

On Thu, Dec 1, 2016 at 10:13 PM, Alexey Melnikov <alexey.melnikov@isode.com>
wrote:

> Hi,
>
> On 27 Nov 2016, at 14:36, Van Catha <vans554@gmail.com> wrote:
>
> So can we form a new WG then and focus on doing this right vs making
> WebSocket2.  The focus earlier was to get the already coded clients and API
> (websocket API) to be able to work with websockets layered on HTTP2/QUIC,
> if we are in it for the long haul now we might as well form a new group and
> create something more long term?
>
> Long haul meaning maybe making websockets its own protocol, detaching from
> HTTP2, having its own ALPN, etc.
>
>
> Interested parties should email art-ads@ietf.org and start the chartering
> discussion. Your friendly area directors will help you with the process.
>
>
> On Sun, Nov 27, 2016 at 1:53 AM, Mark Nottingham <mnot@mnot.net> wrote:
>
>>
>> > On 25 Nov. 2016, at 7:25 pm, Takeshi Yoshino <tyoshino@google.com>
>> wrote:
>> >
>> > Thanks all.
>> >
>> > IESG and IETF don't have unlimited resource. Conclusion of HyBi did
>> make sense.
>> >
>> > As noted by Barry in his mail about WG conclusion and as Mark said, we
>> can form a supervision again once there's enough interest.
>> > https://mailarchive.ietf.org/arch/msg/hybi/vreF1jd3I-vsyWN1TiRnFSCEoVI
>> >
>> > > What *is* in-scope here is how (if at all) that protocol interacts
>> with HTTP, including HTTP/2; there are several ways you could implement
>> WebSockets over HTTP/2, and a few pitfalls in doing so that the people on
>> this list will be able to give you feedback on.
>> >
>> > One of the keys of the WiSH proposal is to focus on API level
>> compatibility with WebSocket. But except for that point, it's a general
>> proposal of application of HTTP semantics and HTTP/2's power for
>> full-duplex messaging in the Web. The proposal (one done by Yutaka in 2014
>> and Van's one also) heavily depends on what the HTTP WG produces (specs,
>> documents and possibly any kind of official/unofficial communications). So,
>> I think there shouldn't be no doubt on need for close work with HTTP WG.
>> >
>> > That said, I agree we need to have the right structure of the community
>> to have the "best" work mode based on various metrics (level of interest
>> for each proposal, their complexity, scope, etc.), and the IESG and the
>> co-chairs are trying to do the best in making the right decision, I think.
>> >
>> > > However, it's hard to do that before there's agreement in the WS
>> community about what the requirements are. Ideally, that community would
>> bring a single proposal that has broad support here for review.
>> >
>> > Mark, does this post of yours imply that you're seeing HyBi ML as one
>> effective representative of WS community at this point with HTTP WG chair
>> hat on?
>>
>> I'm seeing it as the obvious place to hold the discussion; it doesn't
>> have any official status (beyond being the place where hybi happened
>> before), but it's typical practice to keep IETF mailing lists open after a
>> WG concludes, so that the interested parts of the community have a forum.
>>
>> Cheers,
>>
>>
>> --
>> Mark Nottingham   https://www.mnot.net/
>>
>>
>