Nadim, fundamentally, you can always read documents to support your own perspective. That's human nature.
What you are seeing in this discussion is that a massive majority of working group participants believe that your perspective is mistaken. You can of course continue to insist that it is not, and this is your right and privilege. But what you are hearing is that we, the working group, would really like to stop being bombarded by repeated messages where someone who is in the rough (go read RFC7282 if you don't know what that phrase means) insists on re-litigating a point that's been resolved to the satisfaction of the working group. This amounts to a denial-of-service attack, and works very much against the open process in the iETF. Most of us do IETF standards work in support of a day job where we are paid to write software or maintain systems, not to endlessly debate standards. So this behavior makes it too expensive for us to participate. This is really important, Nadim. I've done both sorts of jobs—I had a job for a long time that paid me to do standards work as my main task, and I could spend as much time as I wanted discussing what I thought. Now I have a job where I'm building things. I think the quality of my work has improved a lot as a result of this, but at the expense of my ability to participate when working groups turn toxic as a result of these denial-of-service attacks. The IETF needs practitioners, not just standards wonks. No criticism to either group: this is a pracitcal matter. So when you read that document, please, keep this in mind. There is a HUGE cost to the kind of discourse that we've had on the TLS mailing list the past month. You seem to be a considerate person, and I think you're doing your best, but there's a reason the consensus on "draconian" moderation came out the way it did, and you really should pay attention and not just assume we're all jerks who are out to suppress your opinions. _______________________________________________ TLS mailing list -- [email protected] To unsubscribe send an email to [email protected]
