IETF Logo Mail Archive

Re: [quicwg/base-drafts] New paths may seed initial_rtt (#2687)

Martin Thomson <notifications@github.com> Tue, 14 May 2019 01:29 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 246E912008C for <quic-issues@ietfa.amsl.com>; Mon, 13 May 2019 18:29:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.392
X-Spam-Level:
X-Spam-Status: No, score=-1.392 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 8eg3h0qV-z5G for <quic-issues@ietfa.amsl.com>; Mon, 13 May 2019 18:29:15 -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 D809F120026 for <quic-issues@ietf.org>; Mon, 13 May 2019 18:29:14 -0700 (PDT)
Date: Mon, 13 May 2019 18:29:13 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1557797353; bh=VCn3tf/vM7rdQwFCuQbCT+BC1mGYBXzeYHqCPcBiyHY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=u6kO7mhYuDeNHg2J+iMb6vcKmXXLfgngE5eMptsD40Zig8Qn4YOvc5V6k6ttvnLA+ 6tZdVB9zcpCFACGwgc6N8dg0yaquroK7gCiQljObSnkldVTVDMHYdUbwuFoY9m/mCF GjFFgqMmcR1iYoB3pgGQ9J2QirUBdz8qluQkcZoA=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKZEPGGSV35M2QSQDJ5245GGTEVBNHHBUYRXKM@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2687/c492044123@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2687@github.com>
References: <quicwg/base-drafts/pull/2687@github.com>
Subject: Re: [quicwg/base-drafts] New paths may seed initial_rtt (#2687)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cda19e9bac54_59d23f94f50cd96420482b"; 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/q8FO0wbOFA81_NEJvhehYx2a0Y8>
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: Tue, 14 May 2019 01:29:16 -0000

1. Do we really want to keep the requirement to respond with a PATH_RESPONSE *immediately*?

2. This doesn't talk about paths.  Now, we might infer from this that the RTT to a peer isn't likely to dramatically change when paths change, but we'd want to be saying that directly.

3. How does this sit with the change in #2637?

-- 
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/pull/2687#issuecomment-492044123

v2.29.0 | Report a Bug | By Email | System Status