4 ms·
>Sadly protocols are made by those who show up This is a very high burden to place on casual feedback from somebody trying to be nice.
by oddlyaromatic 9y ago
>Sadly protocols are made by those who show up
This is a very high burden to place on casual feedback from somebody trying to be nice.
- deleted 9y ago[deleted]
- brongondwana 9y agoI'm not quite sure how to respond to this. The IETF is aware that there's already a high burden on people, that decisions tend to be made mostly by the people who can get to meetings and talk in the rooms where standards are hashed out. Having said that, I'm not sure I agree that it's an unreasonable burden to ask somebody to join a mailing list and defend an opinion if they want to influence a standard which will hopefully be useful for tens of years and implemented by hundreds or thousands of people. Any additional complexity for server and client implementers becomes quite a lot of work multiplied by all those people, and the additional burden of implementing a bigger standard may even be enough to discourage people from using it at all. And it's a fact, the decisions are made by those who show up and put the work in. Wishing it was otherwise doesn't change the reality that we need to make tradeoffs and that the IETF favours rough consensus and working code. Both of which take work. I will forward this discussion to the mailing list, that's about all I can do as chair, I won't proxy all the IETF work over to comments on HN!
- oddlyaromatic 9y agoThat makes sense. I think you jumped to quickly to interpreting the original comment as an intent to influence the standard. I read it as just "here is a thought that might be useful/relevant to the people who are making the thing so that they can use it as they see fit when making the standard". No big deal either way!