I can do Jabber scribe again; just prefix something with \"Mic:\" or similar and I'll relay it
", "time": "2022-07-25T19:01:51Z"}, {"author": "C. Heard", "text": "Mr Black your volume is low, thanks
", "time": "2022-07-25T19:45:13Z"}, {"author": "Jonathan Morton", "text": "quickly checking the TOS bit assignments, 000001 was \"Precedence 0, High Reliability\" in the old (pre-DS) system
", "time": "2022-07-25T19:50:15Z"}, {"author": "Jonathan Morton", "text": "in the same vein, 45 decimal is 55 octal, 101101 binary
", "time": "2022-07-25T19:55:04Z"}, {"author": "Gorry Fairhurst", "text": "ToS precedence has been deprecated for a wee while
", "time": "2022-07-25T20:05:34Z"}, {"author": "Jonathan Morton", "text": "my view is: since nodes not supporting the PHB SHOULD already treat it as default, simply accept that wifi stations in default condition meet that definition
", "time": "2022-07-25T20:08:16Z"}, {"author": "Louis Chan", "text": "For WiFi, the bandwidth is varying frequently, and there are multiple clients sharing the channel. I do not see how it would work.
", "time": "2022-07-25T20:09:06Z"}, {"author": "Jason Livingood", "text": "+1 on the local use point --- good suggestion!
", "time": "2022-07-25T20:10:47Z"}, {"author": "Gorry Fairhurst", "text": "I'm going to miss the L4S Hackathon Demo... being remote really does have disadvantages ... if you do make a video or photo, I'll take a look and likely will be impressed!
", "time": "2022-07-25T20:16:10Z"}, {"author": "Chris Box", "text": "Those L4S results are amazing. Well done to everyone who has contributed to this. It will transform network experience.
", "time": "2022-07-25T20:23:42Z"}, {"author": "Jonathan Morton", "text": "I'm less impressed - these are simple runs under ideal conditions
", "time": "2022-07-25T20:24:51Z"}, {"author": "Jonathan Morton", "text": "it's the more complex cases that are likely to throw up trouble
", "time": "2022-07-25T20:25:14Z"}, {"author": "Chris Box", "text": "Speaking as someone who is not regularly involved in this WG, is there some work to be done to define complex test cases so that we can measure it? Or is it more a case of relying on real-world deployment and measuring the effect across all users/conditions/paths?
", "time": "2022-07-25T20:28:08Z"}, {"author": "Jonathan Morton", "text": "Pete Heist and I had done much more in-depth adversarial testing previously
", "time": "2022-07-25T20:28:51Z"}, {"author": "Jonathan Morton", "text": "also, we had roughly this level of functionality in SCE at IETF 101
", "time": "2022-07-25T20:29:24Z"}, {"author": "Gorry Fairhurst", "text": "But SCE wasn't an adopted work item, to me it seems like good progress that the L4S spec is being implemented... I'm still looking forward to the photos!
", "time": "2022-07-25T20:31:31Z"}, {"author": "Jonathan Morton", "text": "IMHO there are still some fundamental unresolved problems in L4S
", "time": "2022-07-25T20:32:45Z"}, {"author": "Jonathan Morton", "text": "which is what we created SCE to address
", "time": "2022-07-25T20:32:57Z"}, {"author": "Chris Box", "text": "@Gorry Stuart had some pictures in his HotRFC slides: https://datatracker.ietf.org/meeting/114/materials/slides-114-hotrfc-sessa-network-latency-00.pdf
", "time": "2022-07-25T20:44:04Z"}, {"author": "Gorry Fairhurst", "text": "@Chris thanks I'll look.
", "time": "2022-07-25T20:46:05Z"}, {"author": "Gorry Fairhurst", "text": "@Martin thanks for the offer for future connections, support and insights
", "time": "2022-07-25T21:02:13Z"}, {"author": "Ana Custura", "text": "thanks!
", "time": "2022-07-25T21:02:47Z"}]