Re: [quicwg/base-drafts] Coalescing Packet including Initial Packet would be over the MTU (#1546)
Kazuho Oku <notifications@github.com> Fri, 13 July 2018 00:21 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 76437131223 for <quic-issues@ietfa.amsl.com>; Thu, 12 Jul 2018 17:21:06 -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 FHcs2Hds2yPO for <quic-issues@ietfa.amsl.com>; Thu, 12 Jul 2018 17:21:03 -0700 (PDT)
Received: from out-6.smtp.github.com (out-6.smtp.github.com [192.30.252.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 47854130DC9 for <quic-issues@ietf.org>; Thu, 12 Jul 2018 17:21:03 -0700 (PDT)
Date: Thu, 12 Jul 2018 17:21:02 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1531441262; bh=EFo3t+qn4PClfMj7ODjDhF713saU2oLz2izqdqMKCBU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=tj5fqwkTuoVcR0XiDvDpIVPNg3hjO3ycYoKgN20PUdswGhgeWYzg4yAaBpM5iB7cy NaCSVaYVefQrtXPIwZtR3IcjJ7Ef7AqwptW6VeCBn6ynMjrWffPSNnDKrGrBYIz+Jt fPcumJZH5TzN6LUDBKdOFBgJELMRg4z6wV4u3/Jk=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab2bd20371fd5458a5c9f28af7db52921be516a34692cf00000001175fb26e92a169ce14453810@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1546/404689214@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1546@github.com>
References: <quicwg/base-drafts/issues/1546@github.com>
Subject: Re: [quicwg/base-drafts] Coalescing Packet including Initial Packet would be over the MTU (#1546)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b47f06e6ffa0_18b13f86a0fdef881560b0"; 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
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/r6RYVF5T9OQ_50-L0Zi2Zeeo9-A>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.27
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: Fri, 13 Jul 2018 00:21:07 -0000
> It is way simpler to send the client initial as is, and the 0-RTT data in a follow-up packet. If the implementation can predict that a 0-RTT will follow, it can refrain from padding the Initial packet, and make sure that the coalesced 0-RTT packet extends to the specified limit. Doable, even if not entirely natural. FWIW, you have the freedom to pad the 0-RTT packet of a coalesced datagram instead. IMO that is the natural way to combine Initial and 0-RTT into a single datagram. What picotls does when both 0-RTT key is available is: * construct Initial packet without padding * construct 0-RTT packet coalesced to the Initial * pad the 0-RTT packet if the datagram is going to be to small -- 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/1546#issuecomment-404689214
- [quicwg/base-drafts] Coalescing Packet including … Daiki AMINAKA
- Re: [quicwg/base-drafts] Coalescing Packet includ… Martin Thomson
- Re: [quicwg/base-drafts] Coalescing Packet includ… Christian Huitema
- Re: [quicwg/base-drafts] Coalescing Packet includ… Kazuho Oku
- Re: [quicwg/base-drafts] Coalescing Packet includ… Christian Huitema
- Re: [quicwg/base-drafts] Coalescing Packet includ… Martin Thomson