<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi Gene,<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On May 6, 2024, at 8:38 PM, Eugene Y Chang <<a href="mailto:eugene.chang@ieee.org" class="">eugene.chang@ieee.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta charset="UTF-8" class=""><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">It seems like you signed off on this challenge.<span class="Apple-converted-space"> </span></span>Don’t do that. Help give me the tools to push this to the next level.</div></blockquote></div><br class=""><div class="">Not at all - I'm definitely signed up for this. But I collected all these points so we can be clear-eyed about the objections that people cite. </div><div class=""><br class=""></div><div class="">Bufferbloat definitely exists. And there are straightforward technical solutions. And as you say, our challenge is to find a way to build the case for broad adoption of these techniques. </div><div class=""><br class=""></div><div class="">Best regards,</div><div class=""><br class=""></div><div class="">Rich</div></div></body></html>