I'd tentatively suggest that the IETF has served its purpose, and is now at risk of outliving it.
This matches my own experience, as the author of multiple internet standards drafts and someone who asked them whether it would be possible to open a group to discuss financial networking. What a hornet's nest that stirred up!
Key examples of outdated properties include: finnicky document format requirements (straight from the 1970s), no unicode support within documents (PITA), document character width limitations that can prevent the effective presentation of required information (no fix for this), monolingual nature of its website and resources, and its own bureaucracy despite its official stance: "this is not a bureaucracy".
It occurs to me that we could replace the IETF RFC process with a git repo or a blockchain. Github should probably do this proactively.
This matches my own experience, as the author of multiple internet standards drafts and someone who asked them whether it would be possible to open a group to discuss financial networking. What a hornet's nest that stirred up!
Key examples of outdated properties include: finnicky document format requirements (straight from the 1970s), no unicode support within documents (PITA), document character width limitations that can prevent the effective presentation of required information (no fix for this), monolingual nature of its website and resources, and its own bureaucracy despite its official stance: "this is not a bureaucracy".
It occurs to me that we could replace the IETF RFC process with a git repo or a blockchain. Github should probably do this proactively.