Re: [quicwg/base-drafts] What resets idle timeout? (#2149)

Benjamin Saunders <notifications@github.com> Fri, 18 January 2019 07:21 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 12BA4131145 for <quic-issues@ietfa.amsl.com>; Thu, 17 Jan 2019 23:21:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.935
X-Spam-Level:
X-Spam-Status: No, score=-10.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-4.553, 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 FaFv4m_2QsvB for <quic-issues@ietfa.amsl.com>; Thu, 17 Jan 2019 23:20:58 -0800 (PST)
Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 73CAB12F295 for <quic-issues@ietf.org>; Thu, 17 Jan 2019 23:20:58 -0800 (PST)
Date: Thu, 17 Jan 2019 23:20:57 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1547796057; bh=SmWu6RneT9mls6LLIZAO/Phadpw0kozZU56lvYExYzo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=DAVAwNnR9y+qWkf1b0AF9sYYeV9lY1+gFlzhB+696WN1UtEFQ2ANauEJLvZk8GkaQ YNPl3qjC3h9dZRyHEG/WK4iyBZnje335UrVKbxqCt/b0OipsBB5qgVPxCqYdS1c+D3 ZegpdynOedM5sU29ywc24QZNw5jPTZNMheZV7Pwo=
From: Benjamin Saunders <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab95fd4f1f9e519086ee11f3e545d8d00e0d0a7cd992cf000000011859405992a169ce174b8a33@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2149/455450715@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2149@github.com>
References: <quicwg/base-drafts/issues/2149@github.com>
Subject: Re: [quicwg/base-drafts] What resets idle timeout? (#2149)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c417e5949412_62f83fe38e4d45c095636"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: Ralith
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/xXSiHWB2w1GlHeemgio-fSnXZLA>
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, 18 Jan 2019 07:21:00 -0000

I like the look of the wording change in ac59e11. Is there something blocking it from being applied?

-- 
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/2149#issuecomment-455450715