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

Martin Thomson <> Thu, 27 February 2020 13:33 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 1D32D3A0877 for <>; Thu, 27 Feb 2020 05:33:37 -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 x7-tgUaXDXcE for <>; Thu, 27 Feb 2020 05:33:35 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 5A1493A086C for <>; Thu, 27 Feb 2020 05:33:35 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 0A63E8C117B for <>; Thu, 27 Feb 2020 05:33:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1582810414; bh=Gf8n7jAsY8zgfcvSszYbe7CwuCABnUyyyW1BCyFlwbM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=aWahQLYkAOCPm3NUHGCAczD0qBGIvAVplNGekrTEM1fxpWo0+QywVXS/uQoxZBtPt amQvN9kjBEonW3S1wue7D5k7pbl8P2j492o9A1LQLqlBycvA7KYw94qL2uHavc5mz6 pwyI5aFGcbkXscsEpiIrEutwBMNYCp1DvAtE1WCs=
Date: Thu, 27 Feb 2020 05:33:33 -0800
From: Martin Thomson <>
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_5e57c52deee4f_717f3fec016cd96439496e"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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 13:33:38 -0000

martinthomson 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.

I guess that I misread it, but here is an alternative...

An endpoint can coalesce packet from multiple packet number spaces with a probe. This allows the peer can drive loss recovery even when it is unable to process some packet types. Endpoints can include a PING frame in packets from spaces other than the one that caused the probe to be sent.

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