<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="">Hi Karen (and everyone else),<div class=""><br class=""></div><div class="">Sorry for the lack of formality in this review, but I just added my comments inline to the document. I hope that approach is palatable and ingestible by the group.</div><div class=""><br class=""></div><div class="">To the comment below, I think this comes up a few times in my inline comments too. In short, I don’t think we can know what the status of name collision incidences are without defining and then measuring/testing for them. I would not say the WPAD collision is a one-off. My 0.02 is that it’s evidence of a (possibly broader) problem. My guess is that the rate of incidence of the set of name collisions problems is unlikely characterized by just this one. I would guess it’s greater than, not equal to. That said, I wonder how well the WPAD vulnerability has been addressed? If we take it as a starting point of a known name collision type, how have we remediated it, and how well is that working?</div><div class=""><br class=""></div><div class="">I very much regret that I cannot make the calls, as I would guess it would be easier to contribute, but I hope these thoughts might be useful.</div><div class=""><br class=""></div><div class="">Eric</div><div class=""><br class=""></div><div class=""></div></body></html>