Re: [quicwg/base-drafts] Invariants: Unclarity in short headers (#2335)
Magnus Westerlund <notifications@github.com> Thu, 17 January 2019 09:03 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 D964812F1AC for <quic-issues@ietfa.amsl.com>; Thu, 17 Jan 2019 01:03:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -12.552
X-Spam-Level:
X-Spam-Status: No, score=-12.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-4.553, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, 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 jkCjOHwH6gZy for <quic-issues@ietfa.amsl.com>; Thu, 17 Jan 2019 01:03:56 -0800 (PST)
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 301A1124B0C for <quic-issues@ietf.org>; Thu, 17 Jan 2019 01:03:56 -0800 (PST)
Date: Thu, 17 Jan 2019 01:03:55 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1547715835; bh=iPTy9Ul/dIItHr/hPwhinYSojUs3pkM2k5d7Vyi+KvM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=aJdjgGzwsNE80ZQNOgizYZAAPlAmXqamNMFbkdcEextjWqqbNCU85TZS2jjTS4rwH Q0MtvXzSxhhQZbM0dpQPqPJv6/ci+Iorzua8X50E+7pnuKUfB1Uw2KKlgZt+CNnUOz oT2/jhOKwX1obsxFoXPoYgdbh/SvK57HFCgDLIyg=
From: Magnus Westerlund <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab8adfd3818f8b5b43adae05f8bf8a86f78554a1cf92cf00000001185806fb92a169ce17cd4834@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2335/455094782@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2335@github.com>
References: <quicwg/base-drafts/issues/2335@github.com>
Subject: Re: [quicwg/base-drafts] Invariants: Unclarity in short headers (#2335)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c4044fb1bd6_71823fb4f28d45b414334e"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: gloinul
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/XLuwaOcbIxMTB6aNGsskeVNrzQE>
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: Thu, 17 Jan 2019 09:03:58 -0000
Ok, the spec is in some sense clear that this can be of arbitary length. However, that this is not required to be consistent with the long header is far from obvious and probably should be explicitly remarked. An realization I didn't have before over this design is that a given destination IP address and UDP port that deals with multiple QUIC connections will be foreced to use one commond DCID length across all QUIC connections using that port, otherwise it will have to use prefixes for DCIDs to be able to determine how long the actual DCID field are to enable decoding the header protection. It might have been a misstake to not include an DCID length field. -- 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/2335#issuecomment-455094782
- [quicwg/base-drafts] Invariants: Unclarity in sho… Magnus Westerlund
- Re: [quicwg/base-drafts] Invariants: Unclarity in… Magnus Westerlund
- Re: [quicwg/base-drafts] Invariants: Unclarity in… Martin Thomson
- Re: [quicwg/base-drafts] Invariants: Unclarity in… Magnus Westerlund
- Re: [quicwg/base-drafts] Invariants: Unclarity in… MikkelFJ
- Re: [quicwg/base-drafts] Invariants: Unclarity in… Martin Thomson