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? Thanks
Received on Friday, 25 November 2016 08:26:17 UTC