[quicwg/base-drafts] Consider merging WebSocket into HTTP/3 (#2953)
theoryfate <notifications@github.com> Mon, 05 August 2019 04:22 UTC
Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00FD6120131 for <quic-issues@ietfa.amsl.com>; Sun, 4 Aug 2019 21:22:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.383
X-Spam-Level:
X-Spam-Status: No, score=-6.383 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.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 cfmLJOd6sPk2 for <quic-issues@ietfa.amsl.com>; Sun, 4 Aug 2019 21:22:18 -0700 (PDT)
Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 488CA120024 for <quic-issues@ietf.org>; Sun, 4 Aug 2019 21:22:18 -0700 (PDT)
Date: Sun, 04 Aug 2019 21:22:17 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1564978937; bh=3pYn4XKEQ4ZoGg1mEoECA/iTauxGtwPpHeKchL5w3sI=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=zbl0/SjW6NjEXkxUKLSA+iVK1Qsq86ZN70+RpX+SFo1MJu8LGP55Ptc8D2GQST4FZ L8bmmQKPCyaB8hntyb5WgMq45LuVQoz2f3nHa0ybr/RmZXqGojVIffZ9AUpp/AniG4 cxWAWdCW2VrvLeJ8ykrrKBY/a2RP01REwjfk0dek=
From: theoryfate <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKZABIIRM3BKMEVHZJN3KTQXTEVBNHHBY2IXI4@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2953@github.com>
Subject: [quicwg/base-drafts] Consider merging WebSocket into HTTP/3 (#2953)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d47aef936b14_2dd03ff6d40cd9643488d1"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: theoryfate
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/6K3Ot-LL8O4JWqXqgpLaoCenMaw>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Aug 2019 04:22:20 -0000
Bootstrapping WebSockets with HTTP/2 is specified in RFC844. The principle is that WebSocket will take up one stream in HTTP/2 and use DATA frame transmission. The coupling between WebSocket and HTTP/2 is already very high. Why not directly merge into a single protocol? This can be designed to be simpler. We can design HTTP/3 as a full-featured protocol that supports working in a request/response mode and supports working in instant messaging mode, unifying the application layer transport protocol of the Web. We can design a special instant communication stream in HTTP/3, through simple handshake, and simple frame encapsulation. In fact, these can directly use the streamlined HTTP/3 header and data format, and the space occupied by compression will be Become smaller, frame encapsulation of WebSocket itself is no longer needed at all This way we no longer need WebSocket. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/quicwg/base-drafts/issues/2953
- [quicwg/base-drafts] Consider merging WebSocket i… theoryfate
- Re: [quicwg/base-drafts] Consider merging WebSock… ianswett
- Re: [quicwg/base-drafts] Consider merging WebSock… theoryfate
- Re: [quicwg/base-drafts] Consider merging WebSock… David Schinazi
- Re: [quicwg/base-drafts] Consider merging WebSock… Mike Bishop
- Re: [quicwg/base-drafts] Consider merging WebSock… Mike Bishop