Re: [quicwg/base-drafts] DetectLostPackets not called in anti-deadlock case (#3298)

ianswett <notifications@github.com> Thu, 12 December 2019 13:32 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 C2BCA1200DF for <quic-issues@ietfa.amsl.com>; Thu, 12 Dec 2019 05:32:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.454
X-Spam-Level:
X-Spam-Status: No, score=-6.454 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, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 O-ua4B5p0zaA for <quic-issues@ietfa.amsl.com>; Thu, 12 Dec 2019 05:32:37 -0800 (PST)
Received: from out-22.smtp.github.com (out-22.smtp.github.com [192.30.252.205]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 20F5F120013 for <quic-issues@ietf.org>; Thu, 12 Dec 2019 05:32:37 -0800 (PST)
Received: from github-lowworker-b19c547.va3-iad.github.net (github-lowworker-b19c547.va3-iad.github.net [10.48.17.66]) by smtp.github.com (Postfix) with ESMTP id 2267EA054D for <quic-issues@ietf.org>; Thu, 12 Dec 2019 05:32:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1576157556; bh=kUhCQrPgBVEmmYiaxLnblgQkKchJxM+LbaVMVSrXgJw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=bjYPNxz9mpzt9NVc54bNeFb29R+dXVZmY0uyGVO1NBGa1W8hL26I6U4lgkUgEtczJ Oj5/rtbAsUXut19XVZZ4NncufMQYuoWbhKAfs+RBG387YWgKU7+uSM98s9y7Qe5Qju K0vVw/JkpWr/g6UTvfRovV99ngBKfQu/Gkvagx2I=
Date: Thu, 12 Dec 2019 05:32:36 -0800
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK6HNQ5O6OPVB7AVHNV375Z7JEVBNHHB76FHYU@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3298/565008101@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3298@github.com>
References: <quicwg/base-drafts/issues/3298@github.com>
Subject: Re: [quicwg/base-drafts] DetectLostPackets not called in anti-deadlock case (#3298)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5df24174126fc_5863fa7c42cd96c1179d8"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
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/cCgvoYMqL0T_6PunZthfkZW9Ja8>
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, 12 Dec 2019 13:32:39 -0000

I'm not sure what you're buffering model is, but I'd expect a RTX to only create a small amount of extra metadata, not a copy of the entire packet.  How you do it depends upon whether you retransmit the payload of the original packet without changing it or use another approach, but it's intended to be low cost.

Is your concern on the client side or the server?

-- 
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/3298#issuecomment-565008101