Re: [quicwg/base-drafts] Dead path timeout (#1638)
mirjak <notifications@github.com> Thu, 09 August 2018 16:45 UTC
Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.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 DA7FA130E44 for <quic-issues@ietfa.amsl.com>; Thu, 9 Aug 2018 09:45:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.009
X-Spam-Level:
X-Spam-Status: No, score=-3.009 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_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=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 gfRoZP9r-Up6 for <quic-issues@ietfa.amsl.com>; Thu, 9 Aug 2018 09:45:57 -0700 (PDT)
Received: from o1.sgmail.github.com (o1.sgmail.github.com [192.254.114.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6522F130DE7 for <quic-issues@ietf.org>; Thu, 9 Aug 2018 09:45:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=wPJARIYZTagcDTWMBBjJdXOGDGM=; b=qIT4KHcmVzKXQhta MRT8zna4cMvQwliJ/HGejyK8DW/YHoAesRpSumrMIxGK/UWDDoHEX5pK1ruZi/1N 36+nRwEdXJJaUuNbjeD6Gs3FdZkUnQ84OFWgsXwR68zAzG5YytW1KvEoAVSt/ZK+ 7US+PDX0yYhAXJ1cArvtEuskzJ4=
Received: by filter0843p1las1.sendgrid.net with SMTP id filter0843p1las1-26577-5B6C6FC3-28 2018-08-09 16:45:55.944489064 +0000 UTC m=+155121.229978724
Received: from github-lowworker17-cp1-prd.iad.github.net (unknown [192.30.252.44]) by ismtpd0019p1iad2.sendgrid.net (SG) with ESMTP id 0gVWiMJ0Q2e7nxc0CT8llA for <quic-issues@ietf.org>; Thu, 09 Aug 2018 16:45:55.771 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker17-cp1-prd.iad.github.net (Postfix) with ESMTP id BF821C07CD for <quic-issues@ietf.org>; Thu, 9 Aug 2018 09:45:55 -0700 (PDT)
Date: Thu, 09 Aug 2018 16:45:56 +0000
From: mirjak <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab29ba16b1e2ae6b67e68a83bda8eb5b47de69d6b592cf00000001178431c392a169ce14c50a90@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1638/411822769@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1638@github.com>
References: <quicwg/base-drafts/issues/1638@github.com>
Subject: Re: [quicwg/base-drafts] Dead path timeout (#1638)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b6c6fc3be4c8_48d53fb39d4be62453406d"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mirjak
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3u3gU6Lby4ALgNNkQfjqvniuNG89RN8TsMKn b4mtV92nMrxx2q+cIU/4nszW0Id8FOO2TB2kN32JuFEstLlXdLq1H2aP6CE9sEYX/0UqN0ZeAwRh9A SxA/JnVa7Pv8k25w0zkIT8aqrwO+gZNqzvY+oWrF3JvLFEsP2npXHxycFQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/mFwRbmDgQ-2mkJjaCW7P_-kglss>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.27
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, 09 Aug 2018 16:46:01 -0000
Is it the transport that should automatically try to reconnect or the application? In the later case it's just the question about when should the transport give up and tell the application and probably to we want to fail the transport fast than TCP usually does? -- 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/1638#issuecomment-411822769
- [quicwg/base-drafts] Dead path timeout (#1638) janaiyengar
- Re: [quicwg/base-drafts] Dead path timeout (#1638) ianswett
- Re: [quicwg/base-drafts] Dead path timeout (#1638) ianswett
- Re: [quicwg/base-drafts] Dead path timeout (#1638) mirjak
- Re: [quicwg/base-drafts] Dead path timeout (#1638) Martin Thomson
- Re: [quicwg/base-drafts] Dead path timeout (#1638) mirjak
- Re: [quicwg/base-drafts] Dead path timeout (#1638) janaiyengar
- Re: [quicwg/base-drafts] Dead path timeout (#1638) Martin Thomson
- Re: [quicwg/base-drafts] Dead path timeout (#1638) Martin Thomson