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 C4974128CE4
 for <quic-issues@ietfa.amsl.com>; Wed,  7 Nov 2018 04:05:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.47
X-Spam-Level: 
X-Spam-Status: No, score=-8.47 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.47, DKIM_SIGNED=0.1,
 DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001,
 MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 wd4cDu-Rkbz2 for <quic-issues@ietfa.amsl.com>;
 Wed,  7 Nov 2018 04:05:47 -0800 (PST)
Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by ietfa.amsl.com (Postfix) with ESMTPS id 67F51127133
 for <quic-issues@ietf.org>; Wed,  7 Nov 2018 04:05:47 -0800 (PST)
Date: Wed, 07 Nov 2018 04:05:46 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com;
 s=pf2014; t=1541592346;
 bh=NKIA+eBxPJ7M60GsEApqq2z46x/KIZ1sQ2lkWDUBiMY=;
 h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID:
 List-Archive:List-Post:List-Unsubscribe:From;
 b=rQFYjUvQU0s2mxsWJFaDct73isDhxO2EylTIIwKborzL5k0VSv67RhAUVclyhSC6N
 3HOTOjL7lFzcUrDLqNU3oefZeXdirYqOm+7JtdaUMvR4TDxZsjDB8D+sHAzTC8ESJe
 1FLU80SVQP8AB9WZq3hJnVg20COQb8876oUO/4f8=
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+0166e4abc64c19fc348eb6d62ce62773681defd8ce3dd4e592cf0000000117fa971a92a169ce168acaf3@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1978/436602034@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1978@github.com>
References: <quicwg/base-drafts/issues/1978@github.com>
Subject: Re: [quicwg/base-drafts] Sender-Controlled Delayed ACK Ratio (#1978)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5be2d51a72288_76ab3fdc97ad45b82042b7";
 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/zep90e_PSW3Ecxpz2shqdnQe5wg>
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: Wed, 07 Nov 2018 12:05:50 -0000


----==_mimepart_5be2d51a72288_76ab3fdc97ad45b82042b7
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

I agree it should change throughout the connection, but I believe the right mechanism for this would be a combination of a transport param and an UPDATE_TRANSPORT_PARAMS frame.  It turns out there's at least one other use for this frame already, which is initial stream flow control limit.

One reason why I believe this is a better approach is there's nowhere good to stick 3 bits in every QUIC packet.  Another reason is I expect people will not want to update this value that often, maybe once every few round trips at most.

An ability to request a MaxAckDelay would also be useful, but it would likely require a new MinMaxAckDelay transport param to inform the sender of the minimum value the sender could request and expect it to be honored.

-- 
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/1978#issuecomment-436602034
----==_mimepart_5be2d51a72288_76ab3fdc97ad45b82042b7
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p>I agree it should change throughout the connection, but I believe the =
right mechanism for this would be a combination of a transport param and =
an UPDATE_TRANSPORT_PARAMS frame.  It turns out there's at least one othe=
r use for this frame already, which is initial stream flow control limit.=
</p>
<p>One reason why I believe this is a better approach is there's nowhere =
good to stick 3 bits in every QUIC packet.  Another reason is I expect pe=
ople will not want to update this value that often, maybe once every few =
round trips at most.</p>
<p>An ability to request a MaxAckDelay would also be useful, but it would=
 likely require a new MinMaxAckDelay transport param to inform the sender=
 of the minimum value the sender could request and expect it to be honore=
d.</p>

<p style=3D"font-size:small;-webkit-text-size-adjust:none;color:#666;">&m=
dash;<br />You are receiving this because you are subscribed to this thre=
ad.<br />Reply to this email directly, <a href=3D"https://github.com/quic=
wg/base-drafts/issues/1978#issuecomment-436602034">view it on GitHub</a>,=
 or <a href=3D"https://github.com/notifications/unsubscribe-auth/AWbkqw-v=
M6Jl6O-XYVYr5aNvVAyu1jSCks5ussyagaJpZM4YSA-X">mute the thread</a>.<img sr=
c=3D"https://github.com/notifications/beacon/AWbkq-bM8OVqlBENEiq8Jno7dtHD=
jnO2ks5ussyagaJpZM4YSA-X.gif" height=3D"1" width=3D"1" alt=3D"" /></p>
<script type=3D"application/json" data-scope=3D"inboxmarkup">{"api_versio=
n":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name"=
:"GitHub"},"entity":{"external_key":"github/quicwg/base-drafts","title":"=
quicwg/base-drafts","subtitle":"GitHub repository","main_image_url":"http=
s://assets-cdn.github.com/images/email/message_cards/header.png","avatar_=
image_url":"https://assets-cdn.github.com/images/email/message_cards/avat=
ar.png","action":{"name":"Open in GitHub","url":"https://github.com/quicw=
g/base-drafts"}},"updates":{"snippets":[{"icon":"PERSON","message":"@ians=
wett in #1978: I agree it should change throughout the connection, but I =
believe the right mechanism for this would be a combination of a transpor=
t param and an UPDATE_TRANSPORT_PARAMS frame.  It turns out there's at le=
ast one other use for this frame already, which is initial stream flow co=
ntrol limit.\r\n\r\nOne reason why I believe this is a better approach is=
 there's nowhere good to stick 3 bits in every QUIC packet.  Another reas=
on is I expect people will not want to update this value that often, mayb=
e once every few round trips at most.\r\n\r\nAn ability to request a MaxA=
ckDelay would also be useful, but it would likely require a new MinMaxAck=
Delay transport param to inform the sender of the minimum value the sende=
r could request and expect it to be honored."}],"action":{"name":"View Is=
sue","url":"https://github.com/quicwg/base-drafts/issues/1978#issuecommen=
t-436602034"}}}</script>
<script type=3D"application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/quicwg/base-drafts/issues/1978#issuecomment=
-436602034",
"url": "https://github.com/quicwg/base-drafts/issues/1978#issuecomment-43=
6602034",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
},
{
"@type": "MessageCard",
"@context": "http://schema.org/extensions",
"hideOriginalBody": "false",
"originator": "AF6C5A86-E920-430C-9C59-A73278B5EFEB",
"title": "Re: [quicwg/base-drafts] Sender-Controlled Delayed ACK Ratio (#=
1978)",
"sections": [
{
"text": "",
"activityTitle": "**ianswett**",
"activityImage": "https://assets-cdn.github.com/images/email/message_card=
s/avatar.png",
"activitySubtitle": "@ianswett",
"facts": [

]
}
],
"potentialAction": [
{
"name": "Add a comment",
"@type": "ActionCard",
"inputs": [
{
"isMultiLine": true,
"@type": "TextInput",
"id": "IssueComment",
"isRequired": false
}
],
"actions": [
{
"name": "Comment",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n\"commandName\": \"IssueComment\",\n\"repositoryFullName\": \=
"quicwg/base-drafts\",\n\"issueId\": 1978,\n\"IssueComment\": \"{{IssueCo=
mment.value}}\"\n}"
}
]
},
{
"name": "Close issue",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n\"commandName\": \"IssueClose\",\n\"repositoryFullName\": \"q=
uicwg/base-drafts\",\n\"issueId\": 1978\n}"
},
{
"targets": [
{
"os": "default",
"uri": "https://github.com/quicwg/base-drafts/issues/1978#issuecomment-43=
6602034"
}
],
"@type": "OpenUri",
"name": "View on GitHub"
},
{
"name": "Unsubscribe",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n\"commandName\": \"MuteNotification\",\n\"threadId\": 4073757=
67\n}"
}
],
"themeColor": "26292E"
}
]</script>=

----==_mimepart_5be2d51a72288_76ab3fdc97ad45b82042b7--

