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

MikkelFJ <> Fri, 13 March 2020 12:08 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 6C91E3A16B7 for <>; Fri, 13 Mar 2020 05:08:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.008
X-Spam-Status: No, score=-2.008 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_16=1.092, 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 kVddACJu6RpK for <>; Fri, 13 Mar 2020 05:08:09 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 1D96F3A16B6 for <>; Fri, 13 Mar 2020 05:08:08 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id CE1DF6601FA for <>; Fri, 13 Mar 2020 05:08:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1584101287; bh=7bz6t3pygeDUWTd7ulaUKcx8j29DUe2kcjHo9RF9w9Q=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=OViZoGH3Uh/7ccZIiKk9vxV+kmSeIkBh/zX1ts0ftQKbjoBJ3fU08/79JkdL604j7 /8hPdottNMnZTGUSP5yldbKOYE5XBb7fsiiryv3PAV6gxeMMga7aVqVhuMG9I6Syzo YpjU1mNU+j0XhaXOQskWiHa8hDQ6Az2x5hgOO1rs=
Date: Fri, 13 Mar 2020 05:08:07 -0700
From: MikkelFJ <>
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_5e6b77a7bbaf5_6f043ff555ecd9688517"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mikkelfj
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: Fri, 13 Mar 2020 12:08:11 -0000

My only problem is that I wouldn't know how to detect duplicate CRYPTO data from a cursory read. Normally you'd feed the data to a TLS blackbox and it would not necessarily provide the information needed. The alternative seems to be to inspect CRYPTO frames, but who is to say that duplicate data is always framed the same?

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