MR> I agree that there are proposals which should have become a standard. But MR> if the majority of the FTSC members vote against it, I have to accept MR> that. For example, we had that with CDP, despite the fact that it is MR> still supported by a few nodes (and by much more in the past). It was MR> ignored for about 10 years and then voted down.
I would say a standard becomes a standard because a sufficient number of developers or users use it. That would shed a totally different role on the mandate of the FTSC.
Take for example the case of IPv6 ... it's as good as nowhere in the nodelist, yet there is FTSC-documentation dealing with it.
In the past, maybe more than 10 years ago, there was a sysop [who has departed the nodelist in the meantime] who wanted to push a particular issue past me and it didn't work, so he had himself elected in the FTSC and pushed it through that body although it wasn't used. Can't remember the name anymore nor what the issue was ... it wasn't accepted anyway and never made it to the nodelist.
