<font face="arial" size="3"><p style="margin:0;padding:0;font-family: arial; font-size: 12pt; overflow-wrap: break-word;">A question from a bystander/ Why is the L4S proposal such a major fork that it needs wo be thought of as if it were an alternative to current IPv4 and IPv6 packets?</p>
<p style="margin:0;padding:0;font-family: arial; font-size: 12pt; overflow-wrap: break-word;"> </p>
<p style="margin:0;padding:0;font-family: arial; font-size: 12pt; overflow-wrap: break-word;">Shouldn't all traffic be in this new class called scalable low loss low latency traffic?</p>
<p style="margin:0;padding:0;font-family: arial; font-size: 12pt; overflow-wrap: break-word;"> </p>
<p style="margin:0;padding:0;font-family: arial; font-size: 12pt; overflow-wrap: break-word;">In a sense, the proposal seems to be like running two Internets (A and B) on the same cables.</p>
<p style="margin:0;padding:0;font-family: arial; font-size: 12pt; overflow-wrap: break-word;"> </p>
<p style="margin:0;padding:0;font-family: arial; font-size: 12pt; overflow-wrap: break-word;">That seems control-theoretically unstable since neither one knows about the other, yet they share resources and influence the dynamics of each other.</p>
<p style="margin:0;padding:0;font-family: arial; font-size: 12pt; overflow-wrap: break-word;"> </p>
<p style="margin:0;padding:0;font-family: arial; font-size: 12pt; overflow-wrap: break-word;">One would need to prove that they are compatible and cause performance to converge when used at the same time.</p>
<p style="margin:0;padding:0;font-family: arial; font-size: 12pt; overflow-wrap: break-word;"> </p>
<p style="margin:0;padding:0;font-family: arial; font-size: 12pt; overflow-wrap: break-word;">If that's been answered, great.</p>
<p style="margin:0;padding:0;font-family: arial; font-size: 12pt; overflow-wrap: break-word;"> </p>
<p style="margin:0;padding:0;font-family: arial; font-size: 12pt; overflow-wrap: break-word;">Remember, the IP datagram and routing layer is the single neck of the hourglass that regulates everything.</p>
<p style="margin:0;padding:0;font-family: arial; font-size: 12pt; overflow-wrap: break-word;"> </p>
<p style="margin:0;padding:0;font-family: arial; font-size: 12pt; overflow-wrap: break-word;"> </p>
<p style="margin:0;padding:0;font-family: arial; font-size: 12pt; overflow-wrap: break-word;">-----Original Message-----<br />From: "Dave Taht" <dave.taht@gmail.com><br />Sent: Wednesday, April 3, 2019 11:30am<br />To: "ECN-Sane" <ecn-sane@lists.bufferbloat.net><br />Subject: [Ecn-sane] where the l4s ect1 takeover is documented<br /><br /></p>
<div id="SafeStyles1554322321">
<p style="margin:0;padding:0;font-family: arial; font-size: 12pt; overflow-wrap: break-word;">It's in: Appendix B.1 of:<br /><br />https://tools.ietf.org/html/draft-ietf-tsvwg-ecn-l4s-id-02#appendix-B.1<br /><br />Which is sort of like the vogons demolishing the internet for a cable<br />industry bypass..<br /><br />“But the plans were on display…”<br />“On display? I eventually had to go down to the cellar to find them.”<br />“That’s the display department.”<br />“With a flashlight.”<br />“Ah, well, the lights had probably gone.”<br />“So had the stairs.”<br />“But look, you found the notice, didn’t you?”<br />“Yes,” said Dave, “yes I did. It was on display in the bottom of a<br />locked filing cabinet stuck in a disused lavatory with a sign on the<br />door saying ‘Beware of the Leopard.”<br /><br /><br />-- <br /><br />Dave Täht<br />CTO, TekLibre, LLC<br />http://www.teklibre.com<br />Tel: 1-831-205-9740<br />_______________________________________________<br />Ecn-sane mailing list<br />Ecn-sane@lists.bufferbloat.net<br />https://lists.bufferbloat.net/listinfo/ecn-sane</p>
</div></font>