Re: [quicwg/base-drafts] On-path calculation of RTT (#631)
Brian Trammell <notifications@github.com> Wed, 07 November 2018 14:48 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 AB7D4130DD2 for <quic-issues@ietfa.amsl.com>; Wed, 7 Nov 2018 06:48:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.47
X-Spam-Level:
X-Spam-Status: No, score=-8.47 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.47, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 pBvONB-gaVAj for <quic-issues@ietfa.amsl.com>; Wed, 7 Nov 2018 06:47:59 -0800 (PST)
Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ED9D9130DCA for <quic-issues@ietf.org>; Wed, 7 Nov 2018 06:47:58 -0800 (PST)
Date: Wed, 07 Nov 2018 06:47:57 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1541602077; bh=3Sk9JmmwFesgqEpbijww/OpV/MNWVrk9v3ZsmQSPuA8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=vdvUBLmo2RzuuowFE7kKy2GBknF8ggVxB5N6ItX/zNNXSj5TaiQTA9N0zT0oILPa+ ZZfuMAoGevylsWtSQV0TwzORGGecBzQ12gljXdr4CCi15S9VwDO/wzWHa4vTGF9MgQ W6duwVc12WL0iwHGjOKgwMxFuiEvfxk1erOwfGrQ=
From: Brian Trammell <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab3b53d89c93b67b320c798f9a139dffb85fd8fc1392cf0000000117fabd1d92a169ce0e0f8270@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/631/436647244@github.com>
In-Reply-To: <quicwg/base-drafts/issues/631@github.com>
References: <quicwg/base-drafts/issues/631@github.com>
Subject: Re: [quicwg/base-drafts] On-path calculation of RTT (#631)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5be2fb1decf4a_672f3fa74c6d45c41221cf"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: britram
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/eajpRKy3QoJkbFiaJT8NV7byMvM>
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: Wed, 07 Nov 2018 14:48:01 -0000
Unparking, per rough consensus to go forward with the spin bit in BKK. I think the right way forward here is to: - refer to the spin-exp document from the new short header definition, once the first-octet discussion is complete (I checked the notes, but it's not clear that the discussion converged) - work out the details of a spin-bit based approach to signaling RTT in -spin-exp - work out the details of measuring the spin bit in -manageability (note: much of this is already in section 3.6, and needs only minor tweaks) - merge -spin-exp into -transport once we settle on the details. -- 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/631#issuecomment-436647244
- [quicwg/base-drafts] Explicit support for on-path… Brian Trammell
- Re: [quicwg/base-drafts] Explicit support for on-… janaiyengar
- Re: [quicwg/base-drafts] Explicit support for on-… janaiyengar
- Re: [quicwg/base-drafts] Explicit support for on-… Patrick McManus
- Re: [quicwg/base-drafts] Explicit support for on-… Martin Thomson
- Re: [quicwg/base-drafts] Explicit support for on-… Brian Trammell
- Re: [quicwg/base-drafts] Explicit support for on-… ianswett
- Re: [quicwg/base-drafts] Explicit support for on-… Brian Trammell
- Re: [quicwg/base-drafts] Explicit support for on-… ianswett
- Re: [quicwg/base-drafts] Explicit support for on-… janaiyengar
- Re: [quicwg/base-drafts] Explicit support for on-… janaiyengar
- Re: [quicwg/base-drafts] Explicit support for on-… ianswett
- Re: [quicwg/base-drafts] Explicit support for on-… Martin Thomson
- Re: [quicwg/base-drafts] Explicit support for on-… Christian Huitema
- Re: [quicwg/base-drafts] Explicit support for on-… Martin Thomson
- Re: [quicwg/base-drafts] Explicit support for on-… Christian Huitema
- Re: [quicwg/base-drafts] On-path calculation of R… Christian Huitema
- Re: [quicwg/base-drafts] On-path calculation of R… Christian Huitema
- Re: [quicwg/base-drafts] On-path calculation of R… Brian Trammell
- Re: [quicwg/base-drafts] On-path calculation of R… ianswett
- Re: [quicwg/base-drafts] On-path calculation of R… ianswett
- Re: [quicwg/base-drafts] On-path calculation of R… Martin Thomson
- Re: [quicwg/base-drafts] On-path calculation of R… mirjak
- Re: [quicwg/base-drafts] On-path calculation of R… ihlar
- Re: [quicwg/base-drafts] On-path calculation of R… Martin Thomson
- Re: [quicwg/base-drafts] On-path calculation of R… Brian Trammell
- Re: [quicwg/base-drafts] On-path calculation of R… janaiyengar
- Re: [quicwg/base-drafts] On-path calculation of R… janaiyengar