NNSquad - Network Neutrality Squad
[ NNSquad ] A comment on Google's SPDY
Several people have asked how I feel about moves toward non-HTTP browser transport mechanisms (e.g., Google's SPDY project). In general, so long as the results are open sourced (and so non-proprietary), I'm definitely in favor of such research. Actual deployment of such systems brings in a number of issues, including possible skewing of users toward browsers that support "advanced" non-HTTP transports in conjunction with particular service providers, vs. browsers without such support. But to the extent that relevant data necessary for implementation in other browsers (and/or browser plugins) is made available in an essentially contemporaneous time frame, I do not feel that it is necessary for everyone to be "locked" into official HTTP standards all of the time. Also, choice of browsers is based on many factors other than speed (including cookie handling controls and other privacy-related features), so these decisions are not generally tied to single criteria. Still, there will likely be some competitive concerns that will need to be evaluated on a case by case basis. I should note that I have long advocated the exploration of alternative mechanisms for server<->user encryption -- that would potentially carry less overhead than existing SSL/TLS mechanisms -- toward the goal of pervasive, routine Internet encryption. My view is that research into HTTP alternatives such as SPDY could provide valuable insight and potentials in this area. --Lauren-- NNSquad Moderator