IETF Logo Mail Archive

Re: [quicwg/base-drafts] Order of Compound Packets (#1287)

Kazuho Oku <notifications@github.com> Thu, 12 April 2018 01:03 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 1149C12D871 for <quic-issues@ietfa.amsl.com>; Wed, 11 Apr 2018 18:03:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.009
X-Spam-Level:
X-Spam-Status: No, score=-3.009 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, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 woIEOwQfHCuv for <quic-issues@ietfa.amsl.com>; Wed, 11 Apr 2018 18:03:16 -0700 (PDT)
Received: from o6.sgmail.github.com (o6.sgmail.github.com [192.254.113.101]) (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 0D2E012D876 for <quic-issues@ietf.org>; Wed, 11 Apr 2018 18:03:15 -0700 (PDT)
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=ycX4sv/mvJ02c4kNGlp4BqWQRY8=; b=VaiO1EDwYfEwQKpf bW3xeuD96kj4D2JG9YGu4YJ00T7g+NVlDCrdr2veYojSfDVbOCEdL63kc9S8d+6M 2X6mDRDA5xnKrKyAyDiT64YKngluJBi5w6bDzVSTRyuLGKxWctedcs0OTug79MIQ 3BfE/hmgTUh6TAFYWS/m918xw9c=
Received: by filter0629p1mdw1.sendgrid.net with SMTP id filter0629p1mdw1-7043-5ACEB04F-7 2018-04-12 01:03:11.102954785 +0000 UTC
Received: from smtp.github.com (out-3.smtp.github.com [192.30.252.194]) by ismtpd0010p1iad1.sendgrid.net (SG) with ESMTP id lyjrt_teReCCtDjqu14MCg for <quic-issues@ietf.org>; Thu, 12 Apr 2018 01:03:11.029 +0000 (UTC)
Date: Thu, 12 Apr 2018 01:03:11 +0000
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab36eedab471fd857e6221182691931b83c8c3dc0e92cf0000000116e6724e92a169ce12ae7fcb@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1287/380641753@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1287@github.com>
References: <quicwg/base-drafts/issues/1287@github.com>
Subject: Re: [quicwg/base-drafts] Order of Compound Packets (#1287)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5aceb04ee7a33_760f2abf00f3eec41204f5"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0xeoEtEvHfGvzGaN+9xCF1Db+YH+rlI0rxXo U7dKUMVlZFC13cDG8bbmZ2bb6WiAT9mVZAsaW1FqE6+pVp9BLJFslXI7Lwvx+qFwV26rd6ZmNZa/zI 4T/b2lEP5nY9Lp7AnlrRJEIW+vFvQxQAxuWm9xXVD6zO7eemwnOzx8VKOT1brNYg/E/+t+i/gGEJXg 0=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/vMSVWVBY3uEDLBr6CmFYhgLLr9M>
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, 12 Apr 2018 01:03:18 -0000

@dtikhonov 
> I'd go as far as to say that there can be at most one long-header packet in a compound packet. (Is there a use case for having more than one?)

Handshake packets and 0-RTT packets are both long header packets, so we cannot say that.

Regarding adding restrictions on how packets can be combined, my weak preference goes to having no restriction, since it would allow us to process bundling after our QUIC implementation emits a packet.

Consider the case where we have a packet in the send queue (due to pacing) and then the client decides to send another packet. Wouldn't it be great if we could simply append the new packet to the packet already stored in the queue?

-- 
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/1287#issuecomment-380641753

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