IETF Logo Mail Archive

Re: [quicwg/base-drafts] Add psuedocode for ACK sending logic in recovery (#1716)

ianswett <notifications@github.com> Thu, 30 August 2018 12:30 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 006CF130E67 for <quic-issues@ietfa.amsl.com>; Thu, 30 Aug 2018 05:30:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.009
X-Spam-Level:
X-Spam-Status: No, score=-3.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 djIqxzUONsg8 for <quic-issues@ietfa.amsl.com>; Thu, 30 Aug 2018 05:30:26 -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 6BE791292AD for <quic-issues@ietf.org>; Thu, 30 Aug 2018 05:30:24 -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=zemyFINJ9u+9u27nmdxhRmSvrpk=; b=DoOEEJGX+CWRE0f9 vzE5v1/j1Bn5CTLbKTs9tDA6stTde5AnvpI+slxA5kxbAcw5zGKFvyikDcaSA/Bb ZQEAt0jVKSILB5pSbm8TW5Y3+iuVnLmyXEZchcG2aQ5yrxL6CAXiWTWTEbuI5tj4 +u1flWiK1Khtn3Tpk3NV4DFjaJc=
Received: by filter0581p1iad2.sendgrid.net with SMTP id filter0581p1iad2-26151-5B87E35E-42 2018-08-30 12:30:22.785783577 +0000 UTC m=+1089300.836700141
Received: from github-lowworker-7a54cd2.cp1-iad.github.net (unknown [192.30.252.44]) by ismtpd0009p1iad2.sendgrid.net (SG) with ESMTP id Zkx-IBn1RDSxRkh4FsXKKw for <quic-issues@ietf.org>; Thu, 30 Aug 2018 12:30:22.783 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-7a54cd2.cp1-iad.github.net (Postfix) with ESMTP id B21513412CB for <quic-issues@ietf.org>; Thu, 30 Aug 2018 05:30:22 -0700 (PDT)
Date: Thu, 30 Aug 2018 12:30:23 +0000
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abbeef1a4ed466095abd4bc1f53df5e7d091e2f62d92cf00000001179fa55e92a169ce152ebf40@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1716/417301983@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1716@github.com>
References: <quicwg/base-drafts/issues/1716@github.com>
Subject: Re: [quicwg/base-drafts] Add psuedocode for ACK sending logic in recovery (#1716)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b87e35eb04df_2eae3fd449cd45bc8522f"; 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
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0+cTKtER+apsRD6mCWQzZAboGqMlwSgXlQHq DxTVwiDlRqqSyrNtxHgITVcsodbI1BAzTAR5GqVbPgFEcUKxUZZFGEWbS5zcIPrfQqPSCznvH+YP+V nsMpd0zhvaZbtFa3l/e7vq/2bqEaf95ayXA74bx0lU1S6baLoMnU+Q5ngGgyVSLq51Yhsu2MDwFPEH A=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/EnKYDPvbo6hiFgBAQxyx3wenOWU>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.27
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 Aug 2018 12:30:28 -0000

There are no IETF standard rate based algorithms I'm aware of, but my real objection would be that the recovery doc could become very long.  I think the example of Reno is simple to understand and covers the important differences between TCP and QUIC that may effect congestion control implementations?

-- 
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/1716#issuecomment-417301983

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