7 ms·
I'm not convinced, though there are, obviously, advantages to RFCs and IETF. The primary disadvantage is speed. A private corporation innovating on its full st
by shadowgovt 6y ago
I'm not convinced, though there are, obviously, advantages to RFCs and IETF.
The primary disadvantage is speed. A private corporation innovating on its full stack can come up with a faster and more secure HTTP alternative for their use case in the time it takes the RFC process to get up in the morning and find its shoes. Google has a streamed cloud gaming service running in its web browser right now; how long would it take the RFC process to kick out the protocols necessary to enable that?
- nitrogen 6y agoThere are already RFCs for realtime streaming of data. Also IIUC the RFC process often starts with a draft based on am existing implementation.
- owowow 6y agoOnLive was streaming games years before Google entered the space, there isn't much novelty in what Stadia has done.
- hombre_fatal 6y agoThe novelty will be if it's profitable / something people want.
- cat199 6y agothis is what organizations that participate in the RFC ecosystem have always done - they just view protocol-level interop and open standards as important.
- dragonwriter 6y ago> A private corporation innovating on its full stack can come up with a faster and more secure HTTP alternative for their use case in the time it takes the RFC process to get up in the morning and find its shoes. But...that's part of standards process. It's quite common for the actors like Google to propose a new/revised standard after implementing it independently SPDY (became HTTP/2), HTTP over QUIC (became HTTP/3), Web SQL DB (became dead, but still started the standardization process), etc., all went this route.
- josephg 6y agoExactly. I was talking to people at the IETF about this last year. One person said the ideal use of the IETF (and RFC process) is to take situations when multiple companies have solved the same problem. The IETF puts everyone in a room (/mailing list) together and lets us collectively figure out a single interoperable protocol that all the members can implement in order to make their systems compatible. The golden path isn't "Joe blogs needs a protocol for something so he writes an RFC". Its "Joe need a protocol. He writes his own and iterates on it. Later he meets Sarah and Dave who've all written similar protocols to solve the same problem at their own organizations. Together they approach the IETF and form a working group to discuss a standard." Reality is usually much more messy than this; but generally the IETF should never be a bottleneck for people who want to write code and try things out. Racing ahead of whats written in RFCs doesn't stand in opposition to the RFC process. The opposite - racing ahead is a necessary part of the process, because we need collective experience in how to solve a problem in order to write good standards.
- johannes1234321 6y agoThere is another downside to IETF/RFC/public standard: it's hard to move forward. My favorite example: e-mail. SMTP and IMAP are old and have so many issues. On the SMTP side it is hard to identify authorized senders, which is a reason for spam, IMAP doesn't really work nice with mobile devices. On the other hand there are messengers like WhatsApp which solves many of those issues and allows adding features (for good or bad) and contrary to mail is fully encrypted and signed (assuming Facebook didn't break it, yet, after adding Signal's technology)
- jacquesm 6y agoRFCs don't get changed, they get replaced by new ones. Until we find something that is 'good enough'. SMTP and IMAP are now older than quite a few of HN's readers. They could be replaced by something better, all someone would have to do is design it and put out a new RFC. What is true though is that once a protocol is 'good enough and it gains mass adoption that change is hard but this is more to be blamed on human nature and inertia than that it is to be blamed on the RFC system in itself.
- johncolanduoni 6y agoUnless your plan is to change human nature, where the “blame” goes is pretty academic. The inertia is still an issue when going the RFC route, and less of an issue when standards are developed first to fill a specific need for an interested party.
- jacquesm 6y agoThe inertia is a good measure for how successful a particular protocol version is. See for instance IPV4 and how hard it is to get rid of it. And that inertia is good, you don't want to rip up your standards every two years.
- shadowgovt 6y agoEvery two years, no. When the standard starts to actively limit further development, though... https://en.m.wikipedia.org/wiki/IPv4_address_exhaustion https://en.m.wikipedia.org/wiki/IPv4_address_exhaustion
- chrisandchris 6y agoI don‘t know that much about how the standardization in machine building is done, just from using this standards when working in this industry. However, I would assume a lot of those standards took very long to establish but they are stable, work basically everywhere and are easy to understand. A lot of standards coming from Google are - so it seems - here to solve things just Google likes to solve and nobody else mostly does not care about. And it‘s not standardization if you‘re the only one caring about it and forcing it onto other.