Date: Wed, 07 Nov 2018 18:37:35 -0800
From: Bob Briscoe <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+0166e4ab372db1a5b1c042af48b010ab9180655a2e9271d392cf0000000117fb636f92a169ce168acaf3@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/436852616@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_5be3a16fcab33_7bac3fceb2ad45c497330";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/hvVNpYw7gRU01pqLZPkoESvtDb0>


----==_mimepart_5be3a16fcab33_7bac3fceb2ad45c497330
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

Regarding whether the interaction mode is 'always repeat' or 'set and change'. I have no strong views. My goal was to suggest the simplest possible protocol that would induce minimal push-back from implementers. Also, perhaps one that could be back-ported to TCP, to leverage shared experience.

On the question of whether ack_ratio would change frequently, if the sender is routinely setting it to cwnd/8 (say) it will change frequently. Similarly if the sender has implemented AckCC (but I suspect AckCC won't often be active).

Whatever, this mechanism is not an invariant, so the approach can be changed based on experience.

@ianswett I've added goals (my subsequent scenarios posting was intended to serve that purpose, but yes that's good practice for a first post). 

-- 
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-436852616
----==_mimepart_5be3a16fcab33_7bac3fceb2ad45c497330
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p>Regarding whether the interaction mode is 'always repeat' or 'set and =
change'. I have no strong views. My goal was to suggest the simplest poss=
ible protocol that would induce minimal push-back from implementers. Also=
, perhaps one that could be back-ported to TCP, to leverage shared experi=
ence.</p>
<p>On the question of whether ack_ratio would change frequently, if the s=
ender is routinely setting it to cwnd/8 (say) it will change frequently. =
Similarly if the sender has implemented AckCC (but I suspect AckCC won't =
often be active).</p>
<p>Whatever, this mechanism is not an invariant, so the approach can be c=
hanged based on experience.</p>
<p><a class=3D"user-mention" data-hovercard-type=3D"user" data-hovercard-=
url=3D"/hovercards?user_id=3D20072817" data-octo-click=3D"hovercard-link-=
click" data-octo-dimensions=3D"link_type:self" href=3D"https://github.com=
/ianswett">@ianswett</a> I've added goals (my subsequent scenarios postin=
g was intended to serve that purpose, but yes that's good practice for a =
first post).</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-436852616">view it on GitHub</a>,=
 or <a href=3D"https://github.com/notifications/unsubscribe-auth/AWbkqyQz=
4cmiTrx1AN5QYiLHcB53pFaeks5us5jvgaJpZM4YSA-X">mute the thread</a>.<img sr=
c=3D"https://github.com/notifications/beacon/AWbkqwlxhAAMtAQsSj268Ib-Yu8C=
rf4bks5us5jvgaJpZM4YSA-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":"@bbri=
scoe in #1978: Regarding whether the interaction mode is 'always repeat' =
or 'set and change'. I have no strong views. My goal was to suggest the s=
implest possible protocol that would induce minimal push-back from implem=
enters. Also, perhaps one that could be back-ported to TCP, to leverage s=
hared experience.\r\n\r\nOn the question of whether ack_ratio would chang=
e frequently, if the sender is routinely setting it to cwnd/8 (say) it wi=
ll change frequently. Similarly if the sender has implemented AckCC (but =
I suspect AckCC won't often be active).\r\n\r\nWhatever, this mechanism i=
s not an invariant, so the approach can be changed based on experience.\r=
\n\r\n@ianswett I've added goals (my subsequent scenarios posting was int=
ended to serve that purpose, but yes that's good practice for a first pos=
t). "}],"action":{"name":"View Issue","url":"https://github.com/quicwg/ba=
se-drafts/issues/1978#issuecomment-436852616"}}}</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=
-436852616",
"url": "https://github.com/quicwg/base-drafts/issues/1978#issuecomment-43=
6852616",
"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": "**Bob Briscoe**",
"activityImage": "https://assets-cdn.github.com/images/email/message_card=
s/avatar.png",
"activitySubtitle": "@bbriscoe",
"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=
6852616"
}
],
"@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_5be3a16fcab33_7bac3fceb2ad45c497330--