IETF Logo Mail Archive

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

Martin Thomson <notifications@github.com> Wed, 06 December 2017 20:27 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 EE367126CC4 for <quic-issues@ietfa.amsl.com>; Wed, 6 Dec 2017 12:27:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.596
X-Spam-Level:
X-Spam-Status: No, score=-5.596 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, 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 0rx8flt2FYsD for <quic-issues@ietfa.amsl.com>; Wed, 6 Dec 2017 12:27:09 -0800 (PST)
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2-ext3.iad.github.net [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4AF941200FC for <quic-issues@ietf.org>; Wed, 6 Dec 2017 12:27:09 -0800 (PST)
Date: Wed, 06 Dec 2017 12:27:07 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1512592027; bh=1DdxG4PN/SDBEEtgbFAiQv9MyvTIs8Iuf496ua44dCQ=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ZSV69E/ioDCHpuQabqrAbeFNdTlXoPDd1J79CzTc8mShcs4VmodL+zNoxtFgD0vNR rzrTivEtyVsV67iEKqWIh+1QY08/P97uxr4k1O6XMzw8tBK9zvryIHcaF426jpkS2Q Ce1vlPE7fd8SfDoxxDII0CUtGDWxf0r8/zWToskc=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abce4126cdbb42379b4136789f3b8dcc3f1aa9114392cf000000011640149b92a169ce0d018204@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/349764267@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_5a28529b7ad86_108b3fb151e6ef281903dd"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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/IHg14gDsWtOPrjsjB8IsND0_bpM>
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: Wed, 06 Dec 2017 20:27:11 -0000

@janaiyengar, we have reserved no packet types.  We have just changed the values we use.  If we don't have the freedom to do that between QUIC versions, then the entire invariants exercise was pointless.  As @csperkins says, the hacky multiplexing scheme used for realtime uses will need to assess every QUIC version independently.  That's possible viable there because of the use of session negotiation (SDP and all that).

-- 
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-349764267

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