Re: [quicwg/base-drafts] Consider merging WebSocket into HTTP/3 (#2953)

David Schinazi <> Mon, 05 August 2019 16:54 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B858812028B for <>; Mon, 5 Aug 2019 09:54:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.381
X-Spam-Status: No, score=-6.381 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id YDwkAxqTG9Fd for <>; Mon, 5 Aug 2019 09:54:47 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 3234E120297 for <>; Mon, 5 Aug 2019 09:54:47 -0700 (PDT)
Date: Mon, 05 Aug 2019 09:54:46 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1565024086; bh=qSNRZ7/4Co4HO9KE/9AAfUz0tEo64fSqHeajJTwAbsU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=N4K7kcw5rfdcvRjVAr0hFw7n5+xDY+tyEyGr0M48ZV+xarWG6tjjVllmj2k9XHlXP L0Mh+23JX6jsgU33Jf1QlVZM0GccsZTR6oSojZPtI7Fxxudca8M6yJQIg2/cXql+js AEh3ugwzGlXQUDxEtoSVCppE4X/31o+Pd8pFF7PY=
From: David Schinazi <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2953/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Consider merging WebSocket into HTTP/3 (#2953)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d485f5610219_67fe3fa9a60cd96c11225e"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: DavidSchinazi
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 05 Aug 2019 16:54:49 -0000

WebTransport also describes how to implement it, one of the ways is over HTTP/3:

It achieves the goal you describe of adding more communication modes without requiring re-authentication.

The current goal of the HTTPBIS and QUIC working groups with regard to HTTP/3 is to ship a minimum viable protocol that suits the needs of the web. What you propose, while a very worthwhile enhancement, is not required for a minimum viable protocol so I don't imagine it landing in QUICv1 or HTTP/3. This can be built as an extension to HTTP/3 or a future version.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: