IETF Logo Mail Archive

Re: [quicwg/base-drafts] RTT Initial measurement (#2607)

ianswett <notifications@github.com> Fri, 12 April 2019 14:07 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 667D3120715 for <quic-issues@ietfa.amsl.com>; Fri, 12 Apr 2019 07:07:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3
X-Spam-Level:
X-Spam-Status: No, score=-3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 4fHkjoqutimg for <quic-issues@ietfa.amsl.com>; Fri, 12 Apr 2019 07:07:39 -0700 (PDT)
Received: from o8.sgmail.github.com (o8.sgmail.github.com [167.89.101.199]) (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 45FE4120714 for <quic-issues@ietf.org>; Fri, 12 Apr 2019 07:07:39 -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=U/ctidVrhNv9n1s+fvyjL7DYwPg=; b=kr8cxXi4EpeXi+Z7 +dXHgi7bYo7W4KTy/5OKO7rVPLcUMThr357lVhcByiiK40N7wRyGGTdXp2ChSC0O p1XJUrWlv7CCwaFXiYAPOEhqCyWKKUntv9w4yKmymsTi37rhTWDpdysLzC9NQ2Ra 9aYh4ngsQDYPEo8hDUq/LtHH5qQ=
Received: by filter0932p1las1.sendgrid.net with SMTP id filter0932p1las1-3879-5CB09B99-22 2019-04-12 14:07:21.735554475 +0000 UTC m=+307962.748221455
Received: from github-lowworker-e55e3e3.cp1-iad.github.net (unknown [192.30.252.41]) by ismtpd0050p1iad1.sendgrid.net (SG) with ESMTP id uXvX9bFNSvWZ_N6_Cq2oaQ for <quic-issues@ietf.org>; Fri, 12 Apr 2019 14:07:21.517 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-e55e3e3.cp1-iad.github.net (Postfix) with ESMTP id 7C2FF18036D for <quic-issues@ietf.org>; Fri, 12 Apr 2019 07:07:21 -0700 (PDT)
Date: Fri, 12 Apr 2019 14:07:21 +0000
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab77c2f2ce1142f04d617a53b3eee45b08f21d8ed392cebabdce1992a169ce19bc0328@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2607/482587748@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2607@github.com>
References: <quicwg/base-drafts/issues/2607@github.com>
Subject: Re: [quicwg/base-drafts] RTT Initial measurement (#2607)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cb09b997a0e7_64dc3fe2f9ed45c466549"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3u24O8nGzSi4mdTmqhrnBxLdMC3CIvp3G5By Q/37y4aO9IQBNEQlFJm1m9eZKznqIIPQDmDh4NuuyQX2rq0GNW8gaa/tPUtpgD/iS4EKw/x5x/F6QG RuRnc277xYwiPo3NS58iXcpPUvIpfp/XebTIvMuo/AFQQtePL2v0mJPPuA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/AhAYyKe4Ie2INVBkwh1-e6QpufU>
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, 12 Apr 2019 14:07:41 -0000

I believe the MAY is only possible if the crypto stack provides a clear signal that it's received all crypto data in Initial or Handshake packets?  I wasn't sure how likely that was to be available, which is why it's a MAY, but I'm also happy to make it a SHOULD.

The text used to say you should always ACK crypto packets immediately, but a client might want to wait a short period of time and ACK the servers Initial in a coalesced packet with the client's Handshake ACK/CFIN, so it was adjusted to " a very short ack delay, such as the local timer granularity".

-- 
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/2607#issuecomment-482587748

v2.23.0 | Report a Bug | By Email