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

Junho Choi <notifications@github.com> Thu, 18 June 2020 16: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 E720E3A0D34 for <quic-issues@ietfa.amsl.com>; Thu, 18 Jun 2020 09:51:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.099
X-Spam-Level:
X-Spam-Status: No, score=-3.099 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_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H2=-0.001, 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 HShDcJoKFi8W for <quic-issues@ietfa.amsl.com>; Thu, 18 Jun 2020 09:51:47 -0700 (PDT)
Received: from out-24.smtp.github.com (out-24.smtp.github.com [192.30.252.207]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2ED283A0D1C for <quic-issues@ietf.org>; Thu, 18 Jun 2020 09:51:47 -0700 (PDT)
Received: from github-lowworker-c5134a3.ac4-iad.github.net (github-lowworker-c5134a3.ac4-iad.github.net [10.52.23.55]) by smtp.github.com (Postfix) with ESMTP id 6F8956A049E for <quic-issues@ietf.org>; Thu, 18 Jun 2020 09:51:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1592499106; bh=H+3eIZQR9yGDEhNRK6EvtBZs87r67gjmwireeeRQzS4=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=OU8qXLDca1oYuWcK3AqOq7FQR2/lXVjVeIgOjcMJAGWm8XKw9WRLL8z0OVq67xp7R D5x5dqJcHvBF+Y4kLJdeYznpZpI978f7S0gEJW1EyY8Mu9sHA+ko9iEvKUGIz2JYMd RKrEoJ6b/y4jxRIn5l4gXzGvWnzKa+2xcYglauIk=
Date: Thu, 18 Jun 2020 09:51:46 -0700
From: Junho Choi <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK3GP6IHONXDN5XQDX54656KFEVBNHHCMOWLJI@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@github.com>
Subject: [quicwg/base-drafts] recovery: Clarifying the priority of Probe packet (#3780)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5eeb9ba260e5c_3b793fdc198cd96430077"; 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/Ue_dDIpUQOTct4aNWHRY1PpsxXQ>
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, 18 Jun 2020 16:51:49 -0000

Currently "Sending Probe Packets" define the priority what to be in Probe packet as follows:

- A probe packet SHOULD carry new data when possible.
- A probe packet MAY carry retransmitted unacknowledged data when new data is unavailable.

And also says "Implementations MAY use alternative strategies for determining the content of probe packets, including sending new or retransmitted data based on the application's priorities."

When there is no new data, we need to choose which one to retransmit when there is a multiple data loss in the sender. Since QUIC's Probe packet approach is a combined experience of TCP TLP and RTO and I believe Probe packet is more similar to TLP. RACK draft says (https://datatracker.ietf.org/doc/html/draft-ietf-tcpm-rack-08#section-7.3) "The probe data segment can either be new, previously unsent data, or a retransmission of previously sent data just below SND.NXT" so it's pretty clear which one to send among the lost data (newest one).

Is there any reason that it's up to the implementers when it need to choose which one to send from lost data? It's better to clarify which one to send among retransmitted unacknowledged data, from oldest or newest when there is multiple data packet lost.

I think it's better to send newest (unacked) one first to follow the reasoning of TLP (new to the old), but there may be some reason why the current draft doesn't define it clearly.

https://github.com/cloudflare/quiche/pull/562#discussion_r441864077 has some background and my comment.

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