Re: [quicwg/base-drafts] recovery: clarifying the priority of Probe packet contents (#3780)

Junho Choi <notifications@github.com> Mon, 22 June 2020 17:23 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 3BCAC3A0FD8 for <quic-issues@ietfa.amsl.com>; Mon, 22 Jun 2020 10:23:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.555
X-Spam-Level:
X-Spam-Status: No, score=-1.555 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.001, SPF_HELO_NONE=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 P7Wj0YtzDRIq for <quic-issues@ietfa.amsl.com>; Mon, 22 Jun 2020 10:23:44 -0700 (PDT)
Received: from out-27.smtp.github.com (out-27.smtp.github.com [192.30.252.210]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D9F163A0FC2 for <quic-issues@ietf.org>; Mon, 22 Jun 2020 10:23:43 -0700 (PDT)
Received: from github-lowworker-1ac52d7.ash1-iad.github.net (github-lowworker-1ac52d7.ash1-iad.github.net [10.56.25.52]) by smtp.github.com (Postfix) with ESMTP id D45ADE0B79 for <quic-issues@ietf.org>; Mon, 22 Jun 2020 10:23:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1592846622; bh=vds9Ztn01sv1xKWlH8K2AVS1kNtZIvN3Za2eMkfYdxs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=o4oOq19P510A8Xe9idX8PLb87ilWF8ckXM7CLQe/Qtvh464eyGKXIjq+TI+30HQ8i 8z9kVeA0RpAFacWGvmX/rn+p9OWk0WY0Th8FZkVcbkYcmjYuHRVShrwzvGdPHTussl pqO3nPRGaHlzzGnvoYT1ETbrVYvRZH3bODpCPlkY=
Date: Mon, 22 Jun 2020 10:23:42 -0700
From: Junho Choi <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKYLYCNVPR3XSYR63FV47TFB5EVBNHHCMOWLJI@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3780/647667407@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3780@github.com>
References: <quicwg/base-drafts/issues/3780@github.com>
Subject: Re: [quicwg/base-drafts] recovery: clarifying the priority of Probe packet contents (#3780)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ef0e91ec380a_556a3f97a50cd95c12141e"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: junhochoi
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/RhhXya4WN3-H1A-WBT5PMgt115U>
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: Mon, 22 Jun 2020 17:23:45 -0000

> Logically it should be the most urgent data among all the available streams.

I think this is the right answer but need some clarification on the draft text.

I think there is 2 different approach for the content of Probe packet depending on the role of Probe packet: 1) if the tail loss is most concerning (what's what I understand from TLP) then we would send a new data if available, or newest lost to move the right edge and update ACK ranges. 2) If HoL is most concerning then we would send oldest lost data (or highest priority data) to move the left edge (but it may be delivered already, because we may lost some acks)

However the draft says we always try to send a new data first regardless of lost data, so I assume 1). But if the priority is simply on the urgent data, we don't need to send a new data first.


-- 
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/3780#issuecomment-647667407