Plan for remaining open design issues

[Lars Eggert <[e-mail]>]

Hi,

if you look at the late-stage process project board (https://github.com/quicwg/base-drafts/projects/5), you'll find three remaining open design issues:

* Text on ECN probing
  https://github.com/quicwg/base-drafts/issues/3585

* Changing the Default QUIC ACK Policy
  https://github.com/quicwg/base-drafts/issues/3529

* QUIC PTO is too conservative, causing a measurable regression in tail latency
  https://github.com/quicwg/base-drafts/issues/3526

I'd like to outline how we intend to handle resolution of those:

Lucas is about to issue a consensus call for a bunch of issues for which we seem to have converged on resolutions. When this consensus call ends, all resolutions of issues for which he have confirmed consensus will be incorporated into the next -28 draft versions.

We then intend to give implementors a bit of time to confirm that the changes in -28 are implementable as specified and interoperate. (We'll likely schedule a virtual interop event for this.)

During the consensus call and the implementation/interop period of -28, we strongly encourage interested parties to drive the discussion on the three issues above (and potentially any issues that may fail to get consensus during the upcoming call).

If any such issues seem to gain consensus, we'll do another consensus cycle and issue -29. Otherwise, we intend to try a WGLC on -28 as-is.

Lars