[tsvwg] L4S drafts: Next Steps

["Black, David" <[e-mail]>]

The WG chairs have consulted among ourselves and with our AD (Martin Duke).
Our guidance to the WG and the L4S draft authors is that at least the following two things need to be done before WGLC will become possible on the L4S drafts:
[1] Rework the "Prague Requirements" into the following two entities, which will overlap:
a.       Transport-protocol-agnostic normative requirements for all congestion-controlled traffic that uses the L4S low latency queue.
*  The DualQ AQM design relies upon traffic adhering to these requirements.
b.       Design and implementation guidelines for new congestion controls that meet the normative requirements (a).
*  Ultimately, the choice of whether a particular aspect is a guideline (b) or requirement (a) is a WG "rough consensus" decision.
     Success of this exercise will be judged by the WG reaching "rough consensus" that multiple transport protocol implementations
     currently meet and/or are reasonably expected to be able to meet the normative requirements (a).
[2] Build the safety case for L4S experimental Internet-wide deployment in the L4S Ops draft.
a.       This safety case does not rely on endpoints running TCP Prague, though it can assume endpoints are meeting the reworked Prague requirements
b.       Ops draft will provide guidance on how to detect L4S problems on their RFC 3168 network, and how to mitigate them.
c.       Ops draft must consider these scenarios:
*   An unsophisticated user purchases an L4S endpoint and runs it on a service provider's single-queue RFC 3168 network.
*   L4S traffic from another domain enters an RFC 3168 single-queue network (e.g. a peer-to-peer application)
     Success of this exercise will be judged by the WG reaching "rough consensus" that deployment of the L4S experiment
     is unlikely to cause significant damage to the Internet, and that any damage that results is expected to be tolerable.
Thanks, --David [as TSVWG WG co-chair]
----------------------------------------------------------------
David L. Black, Senior Distinguished Engineer
Dell Technologies, Infrastructure Systems Group
176 South St., Hopkinton, MA  01748
[phone]<tel:[phone]>           Mobile: [phone]<tel:[phone]>
[e-mail]<mailto:[e-mail]>
----------------------------------------------------------------