Hi all,

We published a new verison of the ACK frequency draft with a full editorial 
pass, particularly aligning the data sender/receiver terminology thoughout the 
whole draft. Thanks Ian!

Mirja



On 30.04.24, 11:21, "QUIC on behalf of [email protected] 
<mailto:[email protected]>" <[email protected] 
<mailto:[email protected]> on behalf of [email protected] 
<mailto:[email protected]>> wrote:


Internet-Draft draft-ietf-quic-ack-frequency-09.txt is now available. It is a
work item of the QUIC (QUIC) WG of the IETF.


Title: QUIC Acknowledgment Frequency
Authors: Jana Iyengar
Ian Swett
Mirja Kühlewind
Name: draft-ietf-quic-ack-frequency-09.txt
Pages: 18
Dates: 2024-04-30


Abstract:


This document specifies an extension to QUIC that enables an endpoint
to request its peer change its behavior when sending or delaying
acknowledgments.


Note to Readers


Discussion of this draft takes place on the QUIC working group
mailing list ([email protected] <mailto:[email protected]>), which is archived at
https://mailarchive.ietf.org/arch/search/?email_list=quic. Source 
<https://mailarchive.ietf.org/arch/search/?email_list=quic>
code and issues list for this draft can be found at
https://github.com/quicwg/ack-frequency 
<https://github.com/quicwg/ack-frequency>.


Working Group information can be found at https://github.com/quicwg 
<https://github.com/quicwg>.


The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-quic-ack-frequency/ 
<https://datatracker.ietf.org/doc/draft-ietf-quic-ack-frequency/>


There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-ietf-quic-ack-frequency-09.html 
<https://www.ietf.org/archive/id/draft-ietf-quic-ack-frequency-09.html>


A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-quic-ack-frequency-09 
<https://author-tools.ietf.org/iddiff?url2=draft-ietf-quic-ack-frequency-09>


Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts







Reply via email to