IETF Logo Mail Archive

Re: [quicwg/base-drafts] SHOULD implement adaptive packet threshold loss detection (#3571)

Igor Lubashev <notifications@github.com> Thu, 30 April 2020 13:51 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 52B873A0766 for <quic-issues@ietfa.amsl.com>; Thu, 30 Apr 2020 06:51:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.373
X-Spam-Level:
X-Spam-Status: No, score=-2.373 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H2=-0.82, SPF_HELO_NONE=0.001, 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 ysHNJrsOpizG for <quic-issues@ietfa.amsl.com>; Thu, 30 Apr 2020 06:51:02 -0700 (PDT)
Received: from out-25.smtp.github.com (out-25.smtp.github.com [192.30.252.208]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 32D263A0765 for <quic-issues@ietf.org>; Thu, 30 Apr 2020 06:51:02 -0700 (PDT)
Received: from github-lowworker-2ef7ba1.ac4-iad.github.net (github-lowworker-2ef7ba1.ac4-iad.github.net [10.52.16.66]) by smtp.github.com (Postfix) with ESMTP id 60C8D282C66 for <quic-issues@ietf.org>; Thu, 30 Apr 2020 06:51:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1588254661; bh=UydUnKwkzaqxfctaGZWl8eqRHaCEki28C/WfNylLMIM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=OQ2bubSLnh1pxJyX/TPT+e4U2HNT9jl5U49IrFHW2CUW6BermZ+Ne9J4mwZNy7R9e QAw1WjuUh3fAVhmT4QlsViDLU24CxemNV47xCztdPuGuhEt9HGNUZdNVGaW8H5VpEu IOZEm4AbSr8rbBaXtE3JWz4tCTwRDzs3trX65mIU=
Date: Thu, 30 Apr 2020 06:51:01 -0700
From: Igor Lubashev <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKYEDAIX7KOYSO5OEXF4W24MLEVBNHHCHD36DQ@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3571/621865392@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3571@github.com>
References: <quicwg/base-drafts/issues/3571@github.com>
Subject: Re: [quicwg/base-drafts] SHOULD implement adaptive packet threshold loss detection (#3571)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5eaad7c551611_7c303fa9518cd964722df"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: igorlord
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/vGlXDfjZXFwbut5nnl6m-HM8INM>
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: Thu, 30 Apr 2020 13:51:07 -0000

@junhochoi The public data on this can be found in [slides presented for IETF 105](https://datatracker.ietf.org/meeting/105/materials/slides-105-maprg-packet-loss-signaling-for-encrypted-protocols).  Take a look at red "below the line" red dots on the graphs.  At the time we thought the red dots represented loss in our observer infrastructure, but additional analysis after the IETF meeting confirmed that the signal was mostly due to very high reordering (more than 31 subsequent packets arrive before an older packet has arrived).

-- 
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/3571#issuecomment-621865392

v2.23.0 | Report a Bug | By Email