Re: [tsvwg] L4S operational guidance draft

[[e-mail]]

Hi Wes,

Done. The draft requires more text (the authors left marks themselves, so that isn't news). 

  5.  Researchers

  5.1.  Detection of Classic ECN FIFO Bottlenecks

     TODO: Describe active testing methods, in-band or out-of-band, that
     can distinguish FIFO from FQ.

I'd appreciate a requirements definition of that test. What is desired regarding properties not directly linked to what is called "classic ECN" and FQ. Desired test duration, applicability for a network section (I'd guess that access links are more important), properties like whether controlled bottleneck congestion is required (I think, it is), and suggested test functionality in the presence of background traffic (the test shouldn't disturb active application flows).
I personally would also prefer references, so that active measurement experts without ECN know-how have a chance to understand what's required for such a test without having to search and read numbers of volumes. I'm not out for a discussion on the list (more text in the draft, please). 

Regards,

Ruediger

-----Ursprüngliche Nachricht-----
Von: tsvwg <[e-mail]> Im Auftrag von Wesley Eddy
Gesendet: Montag, 16. November 2020 19:32
An: [e-mail]
Betreff: [tsvwg] L4S operational guidance draft

In today's meeting, it was mentioned that the L4S operational guidance draft is part of the "safety case" for advancing other L4S drafts.  It's not as mature as the other docs yet (e.g. there are several"TODO" 
portions), but we want to understand if people think it's going in the right direction and will be suitable for this purpose as it's sketched, or what else should be added/changed/etc.

This is on the agenda for Wednesday's meeting.

So, if you have bandwidth, please check out the L4S operational guidance draft prior to the Wednesday meeting, so that we can get a better sense of how to proceed:

https://datatracker.ietf.org/doc/draft-white-tsvwg-l4sops/