[quicwg/base-drafts] What data can be retried safely? (#2150)
ekr <notifications@github.com> Thu, 13 December 2018 19:35 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 93A73130E43 for <quic-issues@ietfa.amsl.com>; Thu, 13 Dec 2018 11:35:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.842
X-Spam-Level:
X-Spam-Status: No, score=-7.842 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 WqqKur5IlfNy for <quic-issues@ietfa.amsl.com>; Thu, 13 Dec 2018 11:35:01 -0800 (PST)
Received: from out-1.smtp.github.com (out-1.smtp.github.com [192.30.252.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BA1AE130E3F for <quic-issues@ietf.org>; Thu, 13 Dec 2018 11:35:00 -0800 (PST)
Date: Thu, 13 Dec 2018 11:34:59 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1544729699; bh=3mnNuCcGZbHTV2k644ky58fbJDaQzdTK87ahy3T6Ek0=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=Khyb2QQ01wXbJughRjv4NsRndZY06h1JzRiKb8Zj2mQLwLvEmhsTFJjrIJKn8D/CF 2K4fLNvjUekkuuJOuk+QmHa032eJjAhrAvz02dFOggN6SdWLWxu+yjJoAFPVyhx0i+ XkA11rErhaGbrOfC1jA2zDaVUbSgYhLCxUz5o+M4=
From: ekr <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab8f69c198e82ea90027c79a5b1507dda9d107f1cd92cf00000001182a766392a169ce174b8d98@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2150@github.com>
Subject: [quicwg/base-drafts] What data can be retried safely? (#2150)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c12b463d7ecc_3bbd3facb5cd45b410969"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ekr
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/DS2Qk8jyiWw6kMPj__GryYy7bn8>
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: Thu, 13 Dec 2018 19:35:03 -0000
```
The value for an idle timeout can be asymmetric. The value advertised by an
endpoint is only used to determine whether the connection is live at that
endpoint. An endpoint that sends packets near the end of the idle timeout
period of a peer risks having those packets discarded if its peer enters the
draining state before the packets arrive. If a peer could timeout within an RTO
(see Section 5.3.3 of {{QUIC-RECOVERY}}), it is advisable to test for liveness
before sending any data that cannot be retried safely.
```
What data can and cannot be retried safely?
--
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/2150