Re: [quicwg/base-drafts] Retransmit server initial upon second Initial (#3080)

ianswett <> Thu, 27 February 2020 04:02 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id A4DC13A106E for <>; Wed, 26 Feb 2020 20:02:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.696
X-Spam-Status: No, score=-1.696 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_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id IoR-vxF0qNgd for <>; Wed, 26 Feb 2020 20:02:23 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id D8F593A106C for <>; Wed, 26 Feb 2020 20:02:22 -0800 (PST)
Date: Wed, 26 Feb 2020 20:02:22 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1582776142; bh=PWna6xa+azP+8GkMTZr5JYxVnly40wELDlNt/TOYKR4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=DpaFW1qcWtP/hIvaE4s+NgJIywDodZhoRpw8I9IPOu++pd0TWJqqrr7o5wah1sF5E Wtpjevp8SA7n7dUKS48lkQO1cUFaqwSC62Sls75HE43Sp/PJsuBU2ccD1lo2Pxh05j 70QvV89l+O0Xh4XQWSUswqWi30eIQ2QW38LX8oGY=
From: ianswett <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/3080/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Retransmit server initial upon second Initial (#3080)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e573f4e48c23_632d3f7f578cd960114524"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 27 Feb 2020 04:02:25 -0000

ianswett commented on this pull request.

> +Peers can also use coalesced packets to ensure that each datagram elicits at least
+one acknowledgement.  For example, clients can coalesce an Initial packet
+containing PING and PADDING frames with a 0-RTT data packet and a server can
+coalesce an Initial packet containing a PING frame with one or more packets in
+its first flight.

Thanks, I'm hoping to write text that's consistent with our approach(ie: one should not assume anything about other QUIC packets that happen to be in the same datagram) and yet note that implementations may want to bundle a small packet(ie: a PING) along with another packet in order to ensure one of the two receives an acknowledgement.  Feel free to suggest clearer text.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: