Live data from Hacker News

Google is working on creating a new protocol named QUIC to replace UDP

plus.google.com

1–10 of 118 posts

Re: Google is working on creating a new protocol named QUIC to replace UDP

#5
I'm all for innovation, but I become wary when a company that controls a sizeable proportion of the browser market-share and also serves a not insignificant proportion of all web traffic makes extensions like this.

SPDY, Dart and now this.

Re: Google is working on creating a new protocol named QUIC to replace UDP

#6
why does google need to come up with protocols? does the IETF and other processes in place for over a decade not work for them? I know nothing of the protocol (the link only mentions the 'cheeky' naming scheme and the source in the chrome tree); I'm merely commenting on googles motives...

Re: Google is working on creating a new protocol named QUIC to replace UDP

#8

I'm all for innovation, but I become wary when a company that controls a sizeable proportion of the browser market-share and also serves a not insignificant proportion of all web traffic makes extensions like this. SPDY, Dart and now this.

arguably, google are well positioned to see where improvements to traffic protocols can be made due to both chrome's large market share and their massive traffic requirements for google search et al.

Later on if/when their protocols are finalised and released, I'm sure one standards body or another will work to integrate them.

Re: Google is working on creating a new protocol named QUIC to replace UDP

#10

Can any boffins please explain what impact this might have in practice? Is this just going to mean faster and more secure data transfer, or are there wider implications?

Low uptake as routers will not have built-in support, and admins will be slow to enable it when and if it becomes available (unless its tunneled over another protocol).

Why not just push IPv6 adoption?

Post reply on HN