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

Mark Nottingham <> Sun, 27 November 2016 06:57 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 9932B129413 for <>; Sat, 26 Nov 2016 22:57:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -8.398
X-Spam-Status: No, score=-8.398 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.497, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id F-Q13QHrmQyc for <>; Sat, 26 Nov 2016 22:57:54 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id D8D82120727 for <>; Sat, 26 Nov 2016 22:57:54 -0800 (PST)
Received: from lists by with local (Exim 4.80) (envelope-from <>) id 1cAtLq-0000PD-P7 for; Sun, 27 Nov 2016 06:54:14 +0000
Resent-Date: Sun, 27 Nov 2016 06:54:14 +0000
Resent-Message-Id: <>
Received: from ([]) by with esmtps (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <>) id 1cAtLf-0000Nd-36 for; Sun, 27 Nov 2016 06:54:03 +0000
Received: from ([]) by with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2) (envelope-from <>) id 1cAtLX-0003Yk-E8 for; Sun, 27 Nov 2016 06:53:57 +0000
Received: from [] (unknown []) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPSA id C9F7B22E253; Sun, 27 Nov 2016 01:53:29 -0500 (EST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\))
From: Mark Nottingham <>
In-Reply-To: <>
Date: Sun, 27 Nov 2016 17:53:26 +1100
Cc: Willy Tarreau <>, Andy Green <>, Van Catha <>, " Group" <>, Wenbo Zhu <>, Martin Thomson <>
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <> <> <> <> <> <> <> <> <> <>
To: Takeshi Yoshino <>
X-Mailer: Apple Mail (2.3251)
Received-SPF: pass client-ip=;;
X-W3C-Hub-Spam-Status: No, score=-8.0
X-W3C-Hub-Spam-Report: AWL=1.629, BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_DB=-1, W3C_IRA=-1, W3C_IRR=-3, W3C_WL=-1
X-W3C-Scan-Sig: 1cAtLX-0003Yk-E8 3d9377c852894f555569a174099545e2
Subject: Re: WiSH: A General Purpose Message Framing over Byte-Stream Oriented Wire Protocols (HTTP)
Archived-At: <>
X-Mailing-List: <> archive/latest/33020
Precedence: list
List-Id: <>
List-Help: <>
List-Post: <>
List-Unsubscribe: <>

> On 25 Nov. 2016, at 7:25 pm, Takeshi Yoshino <> 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.
> > 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.


Mark Nottingham