IETF Logo Mail Archive

Re: [quicwg/base-drafts] Explicit support for on-path calculation of loss and congestion of QUIC flows (#632)

Brian Trammell <notifications@github.com> Fri, 16 June 2017 14:47 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 346B0131996 for <quic-issues@ietfa.amsl.com>; Fri, 16 Jun 2017 07:47:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.397
X-Spam-Level:
X-Spam-Status: No, score=-3.397 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_28=1.404, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-2.8, RP_MATCHES_RCVD=-0.001, 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 dJ5z3PlO-Bow for <quic-issues@ietfa.amsl.com>; Fri, 16 Jun 2017 07:47:03 -0700 (PDT)
Received: from o4.sgmail.github.com (o4.sgmail.github.com [192.254.112.99]) (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 0694713184B for <quic-issues@ietf.org>; Fri, 16 Jun 2017 07:42:06 -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=Zo5rV0w9DOShdrZLbQXi4/Bn4vo=; b=MiAiq4LShseR4T/w UpQRNie32y9ne9p/kZ+raQx+fC5ekWQrpTH5uebAY2338d0XDnNnOiNMpaLBkHeR cewq4524HqBD5uLgK1lQkKbnJWvWX9wYw4yvD1VFqANI1J7l5wAv0BhNNxR1WgCI Jdq8F+Rhk1H9WE+Nl8Mz/1IPJig=
Received: by filter0458p1mdw1.sendgrid.net with SMTP id filter0458p1mdw1-22350-5943EE13-40 2017-06-16 14:41:23.352291688 +0000 UTC
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0002p1iad1.sendgrid.net (SG) with ESMTP id hvBZCRhiRaSiwfnh3RnoIg for <quic-issues@ietf.org>; Fri, 16 Jun 2017 14:41:23.388 +0000 (UTC)
Date: Fri, 16 Jun 2017 07:41:23 -0700
From: Brian Trammell <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abc9a71fe405ff40f5edef615196d3d938ada2ea6b92cf00000001155bb01392a169ce0e0f95f5@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/309044294@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_5943ee133dcb5_205f3fe5462b9c2c77530"; 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
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3ZVBlKN/p70MXLQuURZ9LXx1j8ZJOMCsScsr p/zxCSENK9XXWqgxnb6fr7fqvTJeKLsltp67F7TI/2pitYZivo/jua6KbfwQs59n/evP0q43XOCDLC DygLM/uCf8ZSj7zAhyH7D61F3McuPlzjLm/Q7TmGp6INgkgH6rrb/94gHtJ3CuG6P+VeX7FsOizlTF 8=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/GsXsRS_sJ1hbwMQlyKJ2CUbRzgg>
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: Fri, 16 Jun 2017 14:47:05 -0000

Yes, this is to cover loss estimation. We didn't discuss this at the interim, but it did come up in my survey of exported, passively measured metrics. This is here for completeness.

It's less important to react to loss on a per-flow basis than it is latency, though. So as long as (1) we can assume UDP and TCP traffic are treated equivalently by the link/queue at which the loss occurs and (2) there is some TCP traffic through that link/queue, inference-based observation of TCP will continue to work.

-- 
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-309044294

v2.39.1 | Report a Bug | By Email | System Status