Re: [quicwg/base-drafts] VN packets may be dropped more often when the QUIC bit is 0 (#2400)

Jana Iyengar <> Fri, 22 February 2019 02:30 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 738DB130E11 for <>; Thu, 21 Feb 2019 18:30:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -8.002
X-Spam-Status: No, score=-8.002 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_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-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 ocpLMK0qUd_C for <>; Thu, 21 Feb 2019 18:30:43 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 8808E128B33 for <>; Thu, 21 Feb 2019 18:30:43 -0800 (PST)
Date: Thu, 21 Feb 2019 18:30:42 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1550802642; bh=SdVeq/uw7kKh9BSwvBbYHe6LIAh04FWLk19lhwZp0vI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=xmm5KCY0DQmtQEzeCPxlALYnPqy3akj0IgHWmCB0WWCV8aJZrI4IRjAfCRMEg+771 Z/174CtqmC09wWpVmN0eDiSMj0Of1Ml9OA7A5qOTkBCmtX+DTe7xZg3f3yugzCLxHa lZQLyvQp8ujWl0XKFlVrGkPNcKCRMq+7MXibBqIE=
From: Jana Iyengar <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2400/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] VN packets may be dropped more often when the QUIC bit is 0 (#2400)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c6f5ed26e7c5_3e743f9465ad45c4461284"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: janaiyengar
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: Fri, 22 Feb 2019 02:30:46 -0000

IIRC, the bit was a result of us wanting to demux with various other protocols, and as such, the entire purpose of the bit is to allow identification of QUIC. This may not be a feature we like, but it is a feature.

I don't think we should be talking about the bit, but about co-existence with the other protocols. We discussed this, @martinthomson made a presentation about it (in Montreal, I think), and we agreed to co-exist.

While it can be seen as a natural consequence of setting the QUIC bit, I think the question we want to ask is whether we ought to make this co-existence an invariant. If so, what is the minimal set of packets that need to be demux-able with these other protocols. (We've been over this before, but I don't think we discussed whether it was adequate to demux only for the long header.)

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