On 14 Jun 2015, at 12:29 AM, Bryan Fields Bryan@bryanfields.net wrote:
Spec is all that's needed. Code means we're developing something that's non-standard, and means no router vendor will support it.
When I get a feature implemented in TiMOS there needs to be a business case for it. Every vendor is like this, and unfortunately AMPRnet users have no pull to get a protocol implemented.
Yes, this is how it was for >20 years but it seems to be changing rapidly. By separating the routing logic from the device intended to forward the packets, we can (re-)invent protocols and use OpenFlow to make it work with existing equipment. You can't hack a custom AMPRNet protocol into Mikrotik RouterOS? No problem... it does OpenFlow switching too.
I would say that in future the situation will be reversed - vendors will *only* support the protocols once they are proven to work by "rough consensus and running code" (probably by incorporating that very same code into their products). It is an exciting time for networking, and seems like something hams should pounce on...