This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/iot-wg@ripe.net/
[iot-wg] re-rebooting the co-chair appointment process
- Previous message (by thread): [iot-wg] For information: ETSI releases IoT security standard
- Next message (by thread): [iot-wg] appointing another co-chair
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jim Reid
jim at rfc1035.com
Tue Feb 26 14:42:48 CET 2019
Colleagues, we're still missing a co-chair. The last attempt to find one didn't work out. Although a couple of names were mentioned, there were very few voices of support for any of them - certainly not enough to make a sound consensus decision. It's time for one more heave. I suggest a call for nominations/volunteers/stuckees which ends on April 5th. That gives us 6 weeks for potential co-chairs to be identified and hopefully someone to emerge as the new co-chair. If the results by then are still inconclusive, I'll talk to Hans-Petter about how best to invoke article 5 of our appointment process. Let's hope it doesn't come to that. Please limit your comments on this thread to the proposed time-line and how to solve the problem of lack of WG consensus if this happens this time. I'll post another article for would be co-chairs.
- Previous message (by thread): [iot-wg] For information: ETSI releases IoT security standard
- Next message (by thread): [iot-wg] appointing another co-chair
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ iot-wg Archives ]