IETF Logo Mail Archive

Re: [quicwg/base-drafts] QUIC header format/demultiplexing (#426)

ianswett <notifications@github.com> Thu, 07 December 2017 16:19 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.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 8DFDD12947B for <quic-issues@ietfa.amsl.com>; Thu, 7 Dec 2017 08:19:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.019
X-Spam-Level:
X-Spam-Status: No, score=-2.019 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=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 nys0uTV6aPSt for <quic-issues@ietfa.amsl.com>; Thu, 7 Dec 2017 08:19:22 -0800 (PST)
Received: from o10.sgmail.github.com (o10.sgmail.github.com [167.89.101.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 573FB1201FA for <quic-issues@ietf.org>; Thu, 7 Dec 2017 08:19:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=ltjEDD3yaLzxcood3wPZA0Glt8Q=; b=Sxc4eG2kYUEQXJ7S 9dNlZw/D47tOfO1FGenzezV35Jn/jhpRSbvlGxo+atvrBeH0tDg7YRJnMGfkzH/m 0c06x0K1KL1M3yiQHTjXfj7846Frp1HMlM2R6jevam/LGnc2pPiBqPvJijkqpWr3 jD8/tPlXVgHzqFF/oaNeXUauTTo=
Received: by filter0411p1iad2.sendgrid.net with SMTP id filter0411p1iad2-26797-5A296A09-1 2017-12-07 16:19:21.134176298 +0000 UTC
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0008p1iad1.sendgrid.net (SG) with ESMTP id IRP70IIkSHqCvdknaPIh0g for <quic-issues@ietf.org>; Thu, 07 Dec 2017 16:19:21.014 +0000 (UTC)
Date: Thu, 07 Dec 2017 16:19:21 +0000
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab26539e925422a94069ae3887d3554e38be96ce0492cf0000000116412c0892a169ce0d018204@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/426/350017471@github.com>
In-Reply-To: <quicwg/base-drafts/issues/426@github.com>
References: <quicwg/base-drafts/issues/426@github.com>
Subject: Re: [quicwg/base-drafts] QUIC header format/demultiplexing (#426)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5a296a08d7279_9bfc3fc182040f28141173"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3xIjBrUpHI6F4mkiYfsGqLk283zaK0xFvIq9 7SBGUBpI3ynMQD7tSkMW+4ZmZmSikJp9P/A+OXFv5aN6ZgbU6m0/sqmfxBIR8/mKwI0FINDboXT+HK THuXhEgY0OusLSw0rg4f7AiGs/39CQrHMYIg7GgFxW+yyjn8pGloIRe6Z4e7xqEl96dNi3GVPqT/NY 4=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/HO4YyhTfOt9xv0Rr7hv6QLQoe98>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 07 Dec 2017 16:19:25 -0000

> @marten-seemann no, it doesn't assume that. In short header packets C = 1 to mean connection ID is omitted avoids collisions with STUN. If the Connection ID is present, then C = 0 which makes the first two bits of the packet match those of STUN packets, but if we change the legal values of Connection ID as in my previous we still avoid collisions with STUN when the Connection ID is present. No STUN FINGERPRINT needed in either case.

Sorry, but I'm still a bit confused on the connection ID bit flip in general.

As Marten mentions, there are use cases for both omitting the connection ID from all packets when multiplexing QUIC with WebRTC and use cases for including it.  So inverting the meaning doesn't help solve any problems, unless you don't care about one of these?

-- 
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/426#issuecomment-350017471

v2.35.0 | Report a Bug | By Email | System Status