Re: [quicwg/base-drafts] Order of Compound Packets (#1287)
Nick Banks <notifications@github.com> Thu, 12 April 2018 01:12 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 988E412D87C for <quic-issues@ietfa.amsl.com>; Wed, 11 Apr 2018 18:12:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.009
X-Spam-Level:
X-Spam-Status: No, score=-8.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, RCVD_IN_DNSWL_HI=-5, 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 spXusdlPL6NY for <quic-issues@ietfa.amsl.com>; Wed, 11 Apr 2018 18:12:46 -0700 (PDT)
Received: from out-3.smtp.github.com (out-3.smtp.github.com [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 CD26412D883 for <quic-issues@ietf.org>; Wed, 11 Apr 2018 18:12:45 -0700 (PDT)
Date: Wed, 11 Apr 2018 18:12:45 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1523495565; bh=pTTeHiId6zCn6FH+qY+yL+BKnBcXmbBcdUdbK1xMRg0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=MyXd/Y804kE8utyhUJ7tZdqLp97Q54/8rYtmKu+Je0uZSBqM/f+ZWKlkfGtb/D03T uz2wIwjoEjdcIjmHPTRE3Ug+oYL2THEuEzOMuK2i/fq32rFzbcJhQ4GW/PA19YWRNm 7jJyXH9jlpIo/kYS8tDQTg1MuNuW7kMWmz5apNGs=
From: Nick Banks <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab96367cba5681c3af401f1c1eae0c6a64df07440292cf0000000116e6748d92a169ce12ae7fcb@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/380643219@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_5aceb28d3bbe0_582a3f8fc1fa6f288701d"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: nibanks
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/35rcNyNBnRDBu33-9HuyjzI6XaI>
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:12:48 -0000
@kazuho I agree that's an interesting idea to be able to append a new packet to an already queued up one, but practically I don't know how often it would occur. How often will this new packet end up being a handshake one? I'd expect nearly never. Handshakes would likely be the first ones that needed to be sent out in the first place. If the current queued packet is 1-RTT you can't add to it. And if the currently queued is handshake, then you can already queue to it. The problem with my deferred packet processing is that I don't want to allocate additional state to keep track of which packets in the UDP payload have already been processed and which haven't. I just want to keep track of the "next" one to process. -- 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-380643219
- Re: [quicwg/base-drafts] Order of Coalesced Packe… Martin Thomson
- Re: [quicwg/base-drafts] Order of Coalesced Packe… Nick Banks
- Re: [quicwg/base-drafts] Order of Coalesced Packe… MikkelFJ
- Re: [quicwg/base-drafts] Order of Coalesced Packe… Nick Banks
- Re: [quicwg/base-drafts] Order of Coalesced Packe… MikkelFJ
- Re: [quicwg/base-drafts] Order of Coalesced Packe… Mike Bishop
- Re: [quicwg/base-drafts] Order of Coalesced Packe… Mike Bishop
- Re: [quicwg/base-drafts] Order of Coalesced Packe… Mike Bishop
- Re: [quicwg/base-drafts] Order of Coalesced Packe… Martin Thomson
- [quicwg/base-drafts] Order of Compound Packets (#… Nick Banks
- Re: [quicwg/base-drafts] Order of Compound Packet… Dmitri Tikhonov
- Re: [quicwg/base-drafts] Order of Compound Packet… Kazuho Oku
- Re: [quicwg/base-drafts] Order of Compound Packet… Kazuho Oku
- Re: [quicwg/base-drafts] Order of Compound Packet… Nick Banks
- Re: [quicwg/base-drafts] Order of Compound Packet… Nick Banks
- Re: [quicwg/base-drafts] Order of Compound Packet… Martin Thomson
- Re: [quicwg/base-drafts] Order of Compound Packet… Nick Banks