IETF Logo Mail Archive

Re: [quicwg/base-drafts] Mixing connection IDs is OK (#3870)

Martin Thomson <notifications@github.com> Thu, 09 July 2020 01:08 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 F00663A0AD6 for <quic-issues@ietfa.amsl.com>; Wed, 8 Jul 2020 18:08:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.009
X-Spam-Level:
X-Spam-Status: No, score=-2.009 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, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_16=1.092, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, 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 S4DxDyRtF_GU for <quic-issues@ietfa.amsl.com>; Wed, 8 Jul 2020 18:08:01 -0700 (PDT)
Received: from out-21.smtp.github.com (out-21.smtp.github.com [192.30.252.204]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 67B153A0AD5 for <quic-issues@ietf.org>; Wed, 8 Jul 2020 18:08:01 -0700 (PDT)
Received: from github-lowworker-9bcb4a1.ac4-iad.github.net (github-lowworker-9bcb4a1.ac4-iad.github.net [10.52.25.84]) by smtp.github.com (Postfix) with ESMTP id B88D0A003F for <quic-issues@ietf.org>; Wed, 8 Jul 2020 18:08:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1594256880; bh=XjMDB1fMde6O/pBZrdL12iWi6skvugaiYt20gJVzRSU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=KuYUDHOrrJvAEjm35KcEvREGMkklzhtPbTmja1kZAkHH7N/L5CzXuColjpwNkfMV2 JR22Zf/JTsbAwh4v55vuPOH1pDyOFIVKv5aCebrf5yqM3SBNaFCU3flDvbNEHyAgNK DwCaFF5sJbVkwa4/3C4mKTysaJvAceP0/j1Ree9o=
Date: Wed, 08 Jul 2020 18:08:00 -0700
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK7XZ2HEG32O5GFMVTF5CJHPBEVBNHHCN3DNBM@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3870/c655835809@github.com>
In-Reply-To: <quicwg/base-drafts/pull/3870@github.com>
References: <quicwg/base-drafts/pull/3870@github.com>
Subject: Re: [quicwg/base-drafts] Mixing connection IDs is OK (#3870)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5f066df0a8d0e_64fa3fe4aeecd95c210498"; 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/HHXcYqQG-scMgX2Z5dnS5PrJA8M>
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, 09 Jul 2020 01:08:03 -0000

This is not something we can guarantee in general as we don't protect the assembly of packets into datagrams.  If you feel strongly about that, please open an issue.  

FWIW, I think that most stacks will do this just fine, but I'm concerned that if start to build on top of mechanisms that aren't authenticated, we get unpredictable results.  Maybe QUICv2 can authenticate how packets are coalesced.

-- 
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/pull/3870#issuecomment-655835809

v2.23.0 | Report a Bug | By Email