quicwg/ops-drafts

Update Acknowledgment Efficiency Text isn't great.

Closed this issue · 0 comments

Previously scope of this text was agreed, but what appeared seems to me to have various NiTs:
• Saying "every other packet is acknowledged" is a recommendation in RC9000. I suggest citing also.
• The text seems to conflate endpoint processing optimisation, and network path performance optimisation: /constraint/ wasn't the correct word, but even /constrained/ was a value judgment on design traedoffs for any mobile/RF link - and many bandwidth-limited cabled link, which could be avoided by simply saying what is intended and saying either /which can impact performance of some types of network/ or /which can impact performance across some types of network/ ... depending on your viewpoint as an operator or application.
• I think we can do better than /Some...might/, suggesting removing some and leaving might.

This might be resolved in a PR #400.