Re: [quicwg/base-drafts] Idle timeout interaction with RTO (#1429)

Martin Thomson <notifications@github.com> Mon, 11 June 2018 22:12 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 1CADD130EB4 for <quic-issues@ietfa.amsl.com>; Mon, 11 Jun 2018 15:12:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.01
X-Spam-Level:
X-Spam-Status: No, score=-8.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] 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 dw5B5PG_UmnK for <quic-issues@ietfa.amsl.com>; Mon, 11 Jun 2018 15:12:12 -0700 (PDT)
Received: from out-6.smtp.github.com (out-6.smtp.github.com [192.30.252.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CD627130ED8 for <quic-issues@ietf.org>; Mon, 11 Jun 2018 15:12:11 -0700 (PDT)
Date: Mon, 11 Jun 2018 15:12:11 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528755131; bh=HgycouaEzBV3BlNp4TLGxMo79Z5PZ9QRvEj7gXnwBgE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=a6OxCjc8jVv0gx++jONtCo3HHwlzoZ5hkVP5pfX6oreGuZbAWsi08exp6ibTuZ2YT abxgB8hCwJpq/+SjyipXEX2mY8O1nNCbecWipw8tJZd/uBmONCiqvIjOwcjSZd6+PD 6TYDzI0uYZpC99sI3eMl0983U71kmVJad1eT5tfw=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab762af9aa1ac85650981797d3a8b565c43e8c994292cf000000011736b5bb92a169ce13af8711@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1429/396403848@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1429@github.com>
References: <quicwg/base-drafts/issues/1429@github.com>
Subject: Re: [quicwg/base-drafts] Idle timeout interaction with RTO (#1429)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b1ef3bb1c507_15572af5b838cf6055573"; 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
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/Ztyisq_bS76U37iAyalvMXnSUe8>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.26
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: Mon, 11 Jun 2018 22:12:15 -0000

How does that work when a client receives an ACK (which doesn't generate any response), then has a long quiescent period after which it sends a request?  That doesn't seem right.  Is there a limit on the time between receipt and sending?

-- 
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/1429#issuecomment-396403848