Date: Mon, 07 Jan 2019 19:57:39 +0000 (UTC)
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+0166e4ab4cf52a6a531b67b96610f023fd938bb9310a6f5292cf00000001184b713292a169ce1762ed93@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2205/452061707@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2205@github.com>
References: <quicwg/base-drafts/issues/2205@github.com>
Subject: Re: [quicwg/base-drafts] Largest acked in ACK frame MUST NOT decrease
 (#2205)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5c33af32d716a_6e563fca334d45bc101029";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/OniHsBw2HhfXmwLeu3myQOuJFB8>

----==_mimepart_5c33af32d716a_6e563fca334d45bc101029
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

@gloinul 
> What I don't know if it is resolved fully is the implementation requirements is that a sender MUST be capable of handling an ACK frame with Largest Acknowledged that is smaller than highest received? From my perspective there are good and valid arguments why this may be required, however I think consensus needs to be established on that.

I am not sure if I'm following the context, but my understanding is that a sender MUST be capable of that, because we allow an endpoint to simply retransmit the payload of a packet that is being deemed lost; see #1612.

-- 
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/2205#issuecomment-452061707
----==_mimepart_5c33af32d716a_6e563fca334d45bc101029
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p><a class=3D"user-mention" data-hovercard-type=3D"user" data-hovercard-ur=
l=3D"/hovercards?user_id=3D11295323" data-octo-click=3D"hovercard-link-clic=
k" data-octo-dimensions=3D"link_type:self" href=3D"https://github.com/gloin=
ul">@gloinul</a></p>
<blockquote>
<p>What I don't know if it is resolved fully is the implementation requirem=
ents is that a sender MUST be capable of handling an ACK frame with Largest=
 Acknowledged that is smaller than highest received? From my perspective th=
ere are good and valid arguments why this may be required, however I think =
consensus needs to be established on that.</p>
</blockquote>
<p>I am not sure if I'm following the context, but my understanding is that=
 a sender MUST be capable of that, because we allow an endpoint to simply r=
etransmit the payload of a packet that is being deemed lost; see <a class=
=3D"issue-link js-issue-link" data-error-text=3D"Failed to load issue title=
" data-id=3D"346019788" data-permission-text=3D"Issue title is private" dat=
a-url=3D"https://github.com/quicwg/base-drafts/issues/1612" data-hovercard-=
type=3D"issue" data-hovercard-url=3D"/quicwg/base-drafts/issues/1612/hoverc=
ard" href=3D"https://github.com/quicwg/base-drafts/issues/1612">#1612</a>.<=
/p>

<p style=3D"font-size:small;-webkit-text-size-adjust:none;color:#666;">&mda=
sh;<br />You are receiving this because you are subscribed to this thread.<=
br />Reply to this email directly, <a href=3D"https://github.com/quicwg/bas=
e-drafts/issues/2205#issuecomment-452061707">view it on GitHub</a>, or <a h=
ref=3D"https://github.com/notifications/unsubscribe-auth/AWbkq1v23m0SRt-PIV=
zER_c9fI6_09xBks5vA6aygaJpZM4ZZLl3">mute the thread</a>.<img src=3D"https:/=
/github.com/notifications/beacon/AWbkq8tuR8-EuLyyutuFLEvoF4-1Jc3Uks5vA6ayga=
JpZM4ZZLl3.gif" height=3D"1" width=3D"1" alt=3D"" /></p>
<script type=3D"application/json" data-scope=3D"inboxmarkup">{"api_version"=
:"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"Gi=
tHub"},"entity":{"external_key":"github/quicwg/base-drafts","title":"quicwg=
/base-drafts","subtitle":"GitHub repository","main_image_url":"https://gith=
ub.githubassets.com/images/email/message_cards/header.png","avatar_image_ur=
l":"https://github.githubassets.com/images/email/message_cards/avatar.png",=
"action":{"name":"Open in GitHub","url":"https://github.com/quicwg/base-dra=
fts"}},"updates":{"snippets":[{"icon":"PERSON","message":"@kazuho in #2205:=
 @gloinul \r\n\u003e What I don't know if it is resolved fully is the imple=
mentation requirements is that a sender MUST be capable of handling an ACK =
frame with Largest Acknowledged that is smaller than highest received? From=
 my perspective there are good and valid arguments why this may be required=
, however I think consensus needs to be established on that.\r\n\r\nI am no=
t sure if I'm following the context, but my understanding is that a sender =
MUST be capable of that, because we allow an endpoint to simply retransmit =
the payload of a packet that is being deemed lost; see #1612."}],"action":{=
"name":"View Issue","url":"https://github.com/quicwg/base-drafts/issues/220=
5#issuecomment-452061707"}}}</script>
<script type=3D"application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/quicwg/base-drafts/issues/2205#issuecomment-4=
52061707",
"url": "https://github.com/quicwg/base-drafts/issues/2205#issuecomment-4520=
61707",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>=

----==_mimepart_5c33af32d716a_6e563fca334d45bc101029--