[quicwg/base-drafts] Can VN and Retry packets be coalesced? (#2407)

Marten Seemann <notifications@github.com> Mon, 04 February 2019 10:06 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 CF6C6130E3F for <quic-issues@ietfa.amsl.com>; Mon, 4 Feb 2019 02:06:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -11.007
X-Spam-Level:
X-Spam-Status: No, score=-11.007 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_20=1.546, 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 pSa4Iztu575z for <quic-issues@ietfa.amsl.com>; Mon, 4 Feb 2019 02:06:23 -0800 (PST)
Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3A9B4130E2E for <quic-issues@ietf.org>; Mon, 4 Feb 2019 02:06:23 -0800 (PST)
Date: Mon, 04 Feb 2019 02:06:21 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1549274781; bh=8XbC3p0VGPMjs7HHtmUIqNSAsXZb/8bErO7+0y6RSeA=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=jBlc+YmlqxKv7se7t2ZypL5PPuTyj3jkDOgdKCH4qn2kmPG5aUCr6lPABdEB9aY+C k8twJdQ/rqjrsrWCoWA4iNcTVb0OUgSefMtRCAcuMqRvbQWw7plbXw5bZu1FroZuWI OYe4QWqLRCUTy3lUdqVmuW//DwhG6Q3cvRCUUczk=
From: Marten Seemann <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab4de3dc94181ed1a108a737a3b0e1dcfe492b62c992cf00000001186fd09d92a169ce1836f98b@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2407@github.com>
Subject: [quicwg/base-drafts] Can VN and Retry packets be coalesced? (#2407)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c580e9d839f7_17ba3ff932ad45c462113"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: marten-seemann
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/8ldycntOJ0CiJrnrkbXAnGUkXLU>
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: Mon, 04 Feb 2019 10:06:25 -0000

They don't have a length field, so the only place they could go is at the end of a packet.
As the spec currently stands, it's valid to send a packet like this.

There's little value in doing that. Do we want to continue to allow this?

-- 
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/2407