Re: [quicwg/base-drafts] Latency Spin Bit (#609)

Christian Huitema <notifications@github.com> Thu, 08 June 2017 08:46 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 4FEF1129C5C for <quic-issues@ietfa.amsl.com>; Thu, 8 Jun 2017 01:46:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.182
X-Spam-Level:
X-Spam-Status: No, score=-8.182 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-2.8, 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 BxYUuxUI7DaF for <quic-issues@ietfa.amsl.com>; Thu, 8 Jun 2017 01:46:09 -0700 (PDT)
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2-ext2.iad.github.net [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8FD78129C59 for <quic-issues@ietf.org>; Thu, 8 Jun 2017 01:46:09 -0700 (PDT)
Date: Thu, 08 Jun 2017 01:46:08 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1496911568; bh=j+3xmDxPt5id3aGOg+hdUcijADmmFbO7HqNIQjePRus=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=maT+UJulpnJxc0Dsn19c75EXXaedXVkvhqozyrT7u7q7m0jUMx1C0cgyGb5bnzNQJ ulNrE1hyozvpyyYMNFPcROjIEG8LN9u7yBNuLj60WwF3YSkyyOpRQPpuNUdlYGXKYs ZMe2RVzMxdyNVIFh902HUkaxUwjSKAIN5KhPM3RU=
From: Christian Huitema <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab3ecc578103681765b38ac3e02927e8714fc9286192cf000000011550d0d092a169ce0df938a1@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/c307039989@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_59390ed0bf223_2573ff04c09bc2c1869e"; 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/6lMP9C_9OmnTVYSRTHheooFvkeY>
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: Thu, 08 Jun 2017 08:46:11 -0000

I get Martin's point about per path signal, which it indeed is. But then, we don't really have an end-to-end vs path distinction yet. In the current transport draft, there seems to be just one path at a time. I think the distinction will only become apparent when we start specifying QUIC multipath.

-- 
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#issuecomment-307039989