Re: [quicwg/base-drafts] Lost Server Initial Takes Too Long to be Retransmitted (#3078)

ianswett <> Mon, 07 October 2019 01:16 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 911CF120074 for <>; Sun, 6 Oct 2019 18:16:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.454
X-Spam-Status: No, score=-6.454 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, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 AqGAA77oMHvk for <>; Sun, 6 Oct 2019 18:16:16 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id C1F7312002F for <>; Sun, 6 Oct 2019 18:16:15 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id CBDE3520647 for <>; Sun, 6 Oct 2019 18:16:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1570410974; bh=lnqng30TOTwK9StvXuXXCw3e1j5oCXUXB5iXVoi8chY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Poxqz5lR6AZg0vjpCWvVpJMn/wbbbhoVN/GrA2L4WAOSowcGl2H4V45V1weskvjDU /zU4mDZuCpwN8uGjCB1ZOPcEynauaGqmIl/3piEjWbEslhB7uUhsvFxqome1sDyuS6 /9XXKqb7gsaq6P0QrS6Kxswpn86tks3lPUj6Jo+M=
Date: Sun, 06 Oct 2019 18:16:14 -0700
From: ianswett <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/3078/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Lost Server Initial Takes Too Long to be Retransmitted (#3078)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d9a91debb008_59893fa6b4ecd96c3776ae"; 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: Mon, 07 Oct 2019 01:16:18 -0000

This problem also occurs when the server receives 0-RTT packets it cannot decrypt.  In that case, it would be ideal if it could do something to indicate something was received but not processed.  I guess it could send a PING in an Initial packet as an alternative to EMPTY_ACK?

I sent out a PR that I believe covers the most important points you mention.  PTAL.

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