Re: [quicwg/base-drafts] Latency Spin Bit (#609)
Christian Huitema <notifications@github.com> Tue, 13 June 2017 03:07 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 055EE1294A8 for <quic-issues@ietfa.amsl.com>; Mon, 12 Jun 2017 20:07:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.018
X-Spam-Level:
X-Spam-Status: No, score=-7.018 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_32=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, 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 Y1H8VvsusykP for <quic-issues@ietfa.amsl.com>; Mon, 12 Jun 2017 20:07:00 -0700 (PDT)
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2-ext8.iad.github.net [192.30.252.199]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 914F8127337 for <quic-issues@ietf.org>; Mon, 12 Jun 2017 20:07:00 -0700 (PDT)
Date: Mon, 12 Jun 2017 20:06:59 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1497323219; bh=WprXNxgp3tP77CvtWOB8zCu3HlHfihgvlEc24W6wUvg=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=0Lj3+DW76T79aPHvrFFDs78Hs3Sxqkngdh0wlwPOtDSs3pp3Ds3x5JPFZwvmZuQrx d18WhNY9h+IrdWDIrNElAj3lteEPs/qLN4mfL+srN75z5s84IUbdAkAoXqDt4l6mkn N9KcIsgoAJFQRWw6VjU3rdx32jmxmiJD8Z/tr9CA=
From: Christian Huitema <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4aba4acb835c5431d58e71882ec36713e85432c70a192cf00000001155718d392a169ce0df938a1@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/609/review/43611308@github.com>
In-Reply-To: <quicwg/base-drafts/pull/609@github.com>
References: <quicwg/base-drafts/pull/609@github.com>
Subject: Re: [quicwg/base-drafts] Latency Spin Bit (#609)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_593f56d3c62bd_7a283faed0893c309017"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: huitema
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/FA-Jt_1meamGuGrDWUeUauWFvnU>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.22
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, 13 Jun 2017 03:07:02 -0000
huitema commented on this pull request. > @@ -827,6 +848,24 @@ Implementations MUST assume that an unsupported version uses an unknown packet format. All other fields MUST be ignored when processing a packet that contains an unsupported version. +## Latency Spin Bit + +The latency spin bit enables latency monitoring from observation points on +the network path. This bit is set as follow: + +* The connection responder sets the spin bit value to the value of the + spin bit in the last packet received from the connection initiator. Ian, there are two references to quiescence in the current draft. One about the Ping frame, "The default is to send a PING frame after 15 seconds of quiescence." The other about flow control, "it is generally considered best to not let the sender go into quiescence if avoidable." But the concept of quiescence is not well defined. Is it just "has not sent packet for a long time"? What would you suggest to do? -- 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/609#discussion_r121573754
- [quicwg/base-drafts] Latency Spin Bit (#609) Christian Huitema
- Re: [quicwg/base-drafts] Latency Spin Bit (#609) Brian Trammell
- Re: [quicwg/base-drafts] Latency Spin Bit (#609) Christian Huitema
- Re: [quicwg/base-drafts] Latency Spin Bit (#609) hardie
- Re: [quicwg/base-drafts] Latency Spin Bit (#609) Martin Thomson
- Re: [quicwg/base-drafts] Latency Spin Bit (#609) Brian Trammell
- Re: [quicwg/base-drafts] Latency Spin Bit (#609) MikkelFJ
- Re: [quicwg/base-drafts] Latency Spin Bit (#609) mirjak
- Re: [quicwg/base-drafts] Latency Spin Bit (#609) Christian Huitema
- Re: [quicwg/base-drafts] Latency Spin Bit (#609) Christian Huitema
- Re: [quicwg/base-drafts] Latency Spin Bit (#609) mirjak
- Re: [quicwg/base-drafts] Latency Spin Bit (#609) Christian Huitema
- Re: [quicwg/base-drafts] Latency Spin Bit (#609) Christian Huitema
- Re: [quicwg/base-drafts] Latency Spin Bit (#609) ianswett
- Re: [quicwg/base-drafts] Latency Spin Bit (#609) Christian Huitema
- Re: [quicwg/base-drafts] Latency Spin Bit (#609) mirjak
- Re: [quicwg/base-drafts] Latency Spin Bit (#609) MikkelFJ
- Re: [quicwg/base-drafts] Latency Spin Bit (#609) ianswett
- Re: [quicwg/base-drafts] Latency Spin Bit (#609) Martin Thomson
- Re: [quicwg/base-drafts] Latency Spin Bit (#609) Martin Thomson
- Re: [quicwg/base-drafts] Latency Spin Bit (#609) Martin Thomson
- Re: [quicwg/base-drafts] Latency Spin Bit (#609) Christian Huitema
- Re: [quicwg/base-drafts] Latency Spin Bit (#609) Christian Huitema
- Re: [quicwg/base-drafts] Latency Spin Bit (#609) MikkelFJ
- Re: [quicwg/base-drafts] Latency Spin Bit (#609) ianswett
- Re: [quicwg/base-drafts] Latency Spin Bit (#609) ianswett
- Re: [quicwg/base-drafts] Latency Spin Bit (#609) ianswett
- Re: [quicwg/base-drafts] Latency Spin Bit (#609) janaiyengar
- Re: [quicwg/base-drafts] Latency Spin Bit (#609) Brian Trammell
- Re: [quicwg/base-drafts] Latency Spin Bit (#609) Brian Trammell
- Re: [quicwg/base-drafts] Latency Spin Bit (#609) ianswett
- Re: [quicwg/base-drafts] Latency Spin Bit (#609) janaiyengar
- Re: [quicwg/base-drafts] Latency Spin Bit (#609) ianswett
- Re: [quicwg/base-drafts] Latency Spin Bit (#609) janaiyengar
- Re: [quicwg/base-drafts] Latency Spin Bit (#609) ianswett
- Re: [quicwg/base-drafts] Latency Spin Bit (#609) MikkelFJ
- Re: [quicwg/base-drafts] Latency Spin Bit (#609) Martin Thomson
- Re: [quicwg/base-drafts] Latency Spin Bit (#609) Christian Huitema
- Re: [quicwg/base-drafts] Latency Spin Bit (#609) Christian Huitema
- Re: [quicwg/base-drafts] Latency Spin Bit (#609) Christian Huitema
- Re: [quicwg/base-drafts] Latency Spin Bit (#609) ianswett
- Re: [quicwg/base-drafts] Latency Spin Bit (#609) Martin Thomson
- Re: [quicwg/base-drafts] Latency Spin Bit (#609) Martin Thomson