Date: Fri, 10 Apr 2020 06:00:19 -0700
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+AFTOJK2WKUNMDATKUHIQM6V4TRHOHEVBNHHCHD36DQ@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3571/612018097@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3571@github.com>
References: <quicwg/base-drafts/issues/3571@github.com>
Subject: Re: [quicwg/base-drafts] SHOULD implement adaptive packet threshold
 loss detection (#3571)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5e906de399f2d_29ba3faba82cd95c1302c1";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/Yfl0OnxMZjdH3Ag2CVyJ6UaJQCs>


----==_mimepart_5e906de399f2d_29ba3faba82cd95c1302c1
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

I still intend RACK to be an informational reference(PR uses a ?, not a !), not normative.  The intent was to update from an older informational reference(TCP-NCR) to a newer one.

This mechanism was deployed in Linux long before RACK.

It seems your point is that by changing from MAY to SHOULD, that puts a requirement upon us to fully describe the algorithm in text and pseudocode?  I don't see that as a hard requirement, and as you can see in my PR, I didn't intent to do that.

-- 
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/3571#issuecomment-612018097
----==_mimepart_5e906de399f2d_29ba3faba82cd95c1302c1
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

<p></p>
<p>I still intend RACK to be an informational reference(PR uses a ?, not a !), not normative.  The intent was to update from an older informational reference(TCP-NCR) to a newer one.</p>
<p>This mechanism was deployed in Linux long before RACK.</p>
<p>It seems your point is that by changing from MAY to SHOULD, that puts a requirement upon us to fully describe the algorithm in text and pseudocode?  I don't see that as a hard requirement, and as you can see in my PR, I didn't intent to do that.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">&mdash;<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/quicwg/base-drafts/issues/3571#issuecomment-612018097">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AFTOJK6UQJBQACYHF7KOEZTRL4J6HANCNFSM4MD6VX6A">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AFTOJK3XZTEAAUK2ZTUSE3LRL4J6HA5CNFSM4MD6VX6KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOER5KPMI.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/quicwg/base-drafts/issues/3571#issuecomment-612018097",
"url": "https://github.com/quicwg/base-drafts/issues/3571#issuecomment-612018097",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>
----==_mimepart_5e906de399f2d_29ba3faba82cd95c1302c1--