Re: [quicwg/base-drafts] Lost Server Initial Takes Too Long to be Retransmitted (#3078)
MikkelFJ <notifications@github.com> Fri, 13 March 2020 12:08 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 6C91E3A16B7 for <quic-issues@ietfa.amsl.com>; Fri, 13 Mar 2020 05:08:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.008
X-Spam-Level:
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: 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 kVddACJu6RpK for <quic-issues@ietfa.amsl.com>; Fri, 13 Mar 2020 05:08:09 -0700 (PDT)
Received: from out-23.smtp.github.com (out-23.smtp.github.com [192.30.252.206]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1D96F3A16B6 for <quic-issues@ietf.org>; Fri, 13 Mar 2020 05:08:08 -0700 (PDT)
Received: from github-lowworker-0f78100.ash1-iad.github.net (github-lowworker-0f78100.ash1-iad.github.net [10.56.25.48]) by smtp.github.com (Postfix) with ESMTP id CE1DF6601FA for <quic-issues@ietf.org>; Fri, 13 Mar 2020 05:08:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; 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 <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK5YELVPHDUAKV7ML654O5MKPEVBNHHB34LR2Y@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3078/598689639@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3078@github.com>
References: <quicwg/base-drafts/issues/3078@github.com>
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
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/B694J7L5gpLKsRmcA0FI2pXHBsI>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
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 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: https://github.com/quicwg/base-drafts/issues/3078#issuecomment-598689639
- Re: [quicwg/base-drafts] Lost Server Initial Take… Nick Banks
- [quicwg/base-drafts] Lost Server Initial Takes To… Nick Banks
- Re: [quicwg/base-drafts] Lost Server Initial Take… Marten Seemann
- Re: [quicwg/base-drafts] Lost Server Initial Take… ianswett
- Re: [quicwg/base-drafts] Lost Server Initial Take… Kazuho Oku
- Re: [quicwg/base-drafts] Lost Server Initial Take… MikkelFJ
- Re: [quicwg/base-drafts] Lost Server Initial Take… ianswett
- Re: [quicwg/base-drafts] Lost Server Initial Take… Christian Huitema
- Re: [quicwg/base-drafts] Lost Server Initial Take… Christian Huitema
- Re: [quicwg/base-drafts] Lost Server Initial Take… Lars Eggert
- Re: [quicwg/base-drafts] Lost Server Initial Take… Martin Thomson
- Re: [quicwg/base-drafts] Lost Server Initial Take… Lars Eggert
- Re: [quicwg/base-drafts] Lost Server Initial Take… Martin Thomson
- Re: [quicwg/base-drafts] Lost Server Initial Take… MikkelFJ
- Re: [quicwg/base-drafts] Lost Server Initial Take… ianswett
- Re: [quicwg/base-drafts] Lost Server Initial Take… ianswett