Re: [quicwg/base-drafts] Explicit support for on-path calculation of loss and congestion of QUIC flows (#632)
Brian Trammell <notifications@github.com> Tue, 20 June 2017 08:22 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 882DF129408 for <quic-issues@ietfa.amsl.com>; Tue, 20 Jun 2017 01:22:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.52
X-Spam-Level:
X-Spam-Status: No, score=-6.52 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.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 2mBhbe4gw0ux for <quic-issues@ietfa.amsl.com>; Tue, 20 Jun 2017 01:22:44 -0700 (PDT)
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2-ext1.iad.github.net [192.30.252.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F92B1292FD for <quic-issues@ietf.org>; Tue, 20 Jun 2017 01:22:44 -0700 (PDT)
Date: Tue, 20 Jun 2017 01:22:43 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1497946963; bh=VueskypianQ7BQ48m/iSZ9FflsFKw8TquptxIpG3dBE=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ASws6Oyp9f29WAoALBw/SFlxx+Tyftij2j3t2jcnuobxHAg05mRzSEbqlfS4iTkyl 8uzV8Ahwv2pjVg+u9pL+QFsD2pNvDjP6N1AA5r2yfMJ0teuKuqPB7xUGMPWkEZ0GH5 sVnGOATfwHqypG8D0TpJ8xHCjUkCfyoCDpiK5Ybk=
From: Brian Trammell <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4aba8436b2cb84530ca14eb2040b76aa75c6f44b53f92cf0000000115609d5392a169ce0e0f95f5@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/632/309680807@github.com>
In-Reply-To: <quicwg/base-drafts/issues/632@github.com>
References: <quicwg/base-drafts/issues/632@github.com>
Subject: Re: [quicwg/base-drafts] Explicit support for on-path calculation of loss and congestion of QUIC flows (#632)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5948db532a389_27cc3ff070039c38378b6"; 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/aOKJ_Lo3S4eCY90ZSVe1Q8l-4v4>
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, 20 Jun 2017 08:22:46 -0000
So it turns out I actually agree with Lars here: loss, in and of itself, is a relatively useless metric without other things to correlate with. Requiring ECN negotiation for QUIC would actually do more for the (long-term) measurability of the protocol than mandating loss exposure, in part because future QUICs may have different transmission schedulers which would react differently to loss. The question is how useful CE mark based measurement will be in the intermediate term, as we transition from relatively little marking on path to "some" marking on path. More useful would be a generalization of the ConEx mechanism, which could certainly go into a debug header, and would allow a single point to get information about CE markings (as well as loss) both on the upstream and the downstream. Would need to look into whether any TCP-centric assumptions were built into that mechanism. -- 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/632#issuecomment-309680807
- [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-… Brian Trammell
- Re: [quicwg/base-drafts] Explicit support for on-… Christian Huitema
- Re: [quicwg/base-drafts] Explicit support for on-… Brian Trammell
- Re: [quicwg/base-drafts] Explicit support for on-… Lars Eggert
- Re: [quicwg/base-drafts] Explicit support for on-… ianswett
- Re: [quicwg/base-drafts] Explicit support for on-… Brian Trammell
- Re: [quicwg/base-drafts] On-path calculation of l… Brian Trammell
- Re: [quicwg/base-drafts] On-path calculation of l… Martin Thomson
- Re: [quicwg/base-drafts] On-path calculation of l… Martin Thomson