Call for volunteers or nominations for RIPE IoT Working Group co-chair
Dear Colleagues As Constanze's term as IoT WG co-chair is about to end with RIPE 84, this is a call for nominations or volunteers to co-chair the RIPE IoT working group. *********************************************************************** Please DO NOT reply to this message if you wish to propose a volunteer. *********************************************************************** I would ask for each candidate to start a new thread with, e.g., "[name] for co-chair", and for members to utter their support by replying to the respective thread. Provided there are no reasoned objections from the WG, I'd like to set *May 16th* as a deadline for showing support on the mailing list, so that we can announce the decision on *18th May* during the IoT WG sesssion at RIPE 84. More information about WG co-chair responsibilities (https://www.ripe.net/publications/docs/ripe-692). If you'd like further information, don't hesitate to contact me or Constanze. Have a nice day! Sandoche
sandoche Balakrichenan <sandoche.balakrichenan@afnic.fr> wrote: > As Constanze's term as IoT WG co-chair is about to end with RIPE 84, > this is a call for nominations or volunteers to co-chair the RIPE IoT > working group. > *********************************************************************** > Please DO NOT reply to this message if you wish to propose a volunteer. > *********************************************************************** Hi, I am replying with meta-questions/suggestions. > I would ask for each candidate to start a new thread with, e.g., > "[name] for co-chair", and for members to utter their support by > replying to the respective thread. I went to read the IoT WG charter wondering what it was we were supposed to be doing in the first place :-) https://www.ripe.net/participate/ripe/wg/active-wg/iot says: The Internet of Things (IoT) Working Group will operate under the following charter: (1) To discuss challenges and opportunities of "IoT" for the RIPE community (2) To serve as a focal point for the RIPE NCC regarding community input to their IoT activities, including liaisons with other organisations (3) To invite IoT communities for a dialogue on matters of operational relevance, including security, the numbering system, and applicability of standards (4) To develop positions of the RIPE community on IoT matters {I numbered the points} I think that we've done a small bit of (4). I don't think that we've done (2) at all. On (1) and (3) we've done bit and pieces. I bring this up because I won't really know who a good co-chair is until I have a better idea what we are doing. Or to put it another way, maybe candidates could also say what they would do this way. I also wonder about whether physical attendance at RIPE meetings is a MUST, or just a WOULD BE NICE, and whether participants from outside the RIPE region are appropriate. -- ] Never tell me the odds! | ipv6 mesh networks [ ] Michael Richardson, Sandelman Software Works | network architect [ ] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
On 13 Apr 2022, at 19:58, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
I think that we've done a small bit of (4). I don't think that we've done (2) at all.
We have. Marco has given the WG a couple of updates on what’s been going on at ITU SG20 and the NCC’s activities there. ISTR we’ve had a few reports from the IETF’s IoT-related WGs and some hackathons. Another aspect of point 2 -- community input on the NCC’s IoT activities -- is dependent on what sort of IoT questions the NCC gets from other organisations and fora: governmet roundtables and the like.
I bring this up because I won't really know who a good co-chair is until I have a better idea what we are doing. Or to put it another way, maybe candidates could also say what they would do this way.
Well now’s your chance Michael. :-) What would you do as co-chair?
I also wonder about whether physical attendance at RIPE meetings is a MUST, or just a WOULD BE NICE, and whether participants from outside the RIPE region are appropriate.
IMO, it would be difficult but not impossible to have a remote co-chair. There’s usually one co-chair running the meeting while the other does the behind-the-scenes gophering. I think it's advisable for the co-chairs to be physically present for most RIPE meetings so they can participate in hallway chats and discussions over beer/coffee. Which is the real point of RIPE meetings. Participants from outside the RIPE region are just as welcome as anybody else IMO. RIPE has had co-chairs who were based outside RIPE’s service region or had out-of-region nationality. Maybe it still does. I would hope the WG picks its co-chairs based on merit rather than who issued their passport. These are of course just the opinions of an Old Fart who doesn’t and won’t chair anything. It’s up to the WG to decide these things for itself.
A relevant call to share: *************************************** 12th International Conference on the Internet of Things (https://iot-conference.org<https://iot-conference.org/>) November 7-10 @ Technical University of Delft, The Netherlands The International Conference on the Internet of Things is the premier gathering for visionary and groundbreaking research in IoT and closely-related fields. It connects world-class researchers with leading industry experts to steer innovation in multiple IoT verticals (e.g., smart industry, smart cities, smart health, smart environment). Since its start in 2008, the conference has been backed by strong support from leading academic institutions as well as industry. Call for Workshop Proposals IoT 2022 invites full-day and half-day workshop proposals with a clearly defined scope that falls in the general topics of the conference. We also encourage submission of workshop proposals that follow alternative formats such as hackathons, plugfests, demo jams, and breakout sessions as long as they can be conducted in hybrid settings. Workshops should provide an informal and vibrant forum for researchers and industry practitioners to share their research results and practical experiences. This year, we encourage submissions related, but not limited to, IoT-enabled alternate realities as well as assured autonomy and resilient IoT. IoT 2022 will publish accepted workshop papers in companion proceedings to the conference’s main proceedings. Workshop proposals should be submitted no later than May 25, 2022 to workshops-iot2022-IDE@tudelft.nl<mailto:workshops-iot2022-IDE@tudelft.nl>, and will be subject to a rolling acceptance process, reviewed by workshop program chairs. Organizers should submit a 200 words abstract, along with a single PDF file of 4 pages maximum in the ACM SIGCHI Extended Abstracts Format. More information is available on the conference webpage. Important Dates * Workshop proposal submission: May 25, 2022 * Notification of workshop acceptance: Rolling, typically within three weeks but no later than June 30 * Workshop papers Submission deadlines: Camera ready date no later than October 17, 2022 * Workshop dates: TBD within November 7-10, 2022 All times and dates AOE. Workshop Program Chairs: Aaron Ding & Kimberly Garcia *************************************** Aaron
Jim Reid <jim@rfc1035.com> wrote: >> I bring this up because I won't really know who a good co-chair is >> until I have a better idea what we are doing. Or to put it another >> way, maybe candidates could also say what they would do this way. > Well now’s your chance Michael. :-) What would you do as co-chair? I'm no longer convinced that there is actually any relevant work for us to do. So, I might actually just close the group. I'm not convinced that the people who are participating in this WG are connected to the right operational places in ISPs. I think that we are all (quite experienced and smart) IoT hackers who have ideas about what the right thing to do, but we don't actually to implement our ideas much. > Participants from outside the RIPE region are just as welcome as > anybody else IMO. RIPE has had co-chairs who were based outside RIPE’s > service region or had out-of-region nationality. Maybe it still does. I > would hope the WG picks its co-chairs based on merit rather than who > issued their passport. It's not about passports, I think, but about attendance. I won't volunteer as co-chair for the reason that I don't think that I'll attend many meetings in person. -- Michael Richardson <mcr+IETF@sandelman.ca> . o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide
Jim Reid <jim@rfc1035.com> wrote: >> I bring this up because I won't really know who a good co-chair is >> until I have a better idea what we are doing. Or to put it another >> way, maybe candidates could also say what they would do this way.
> Well now’s your chance Michael. :-) What would you do as co-chair?
I'm no longer convinced that there is actually any relevant work for us to do. ==> Based upon the response from the survey and discussion with the community, one of the issue seems to be that the scope of the WG is quite open. One is not sure the category of discussions (about ioT) that
So, I might actually just close the group. ==> Keeping the group open or closing it should also be a discussion
On 14/04/2022 01:32, Michael Richardson wrote: they can have in the mailing list. that we should discuss about.
I'm not convinced that the people who are participating in this WG are connected to the right operational places in ISPs. ==> We do have ISP stakeholders in the community. We had discussions with one or two and even tried to have a interim meeting specifically focused on ISP's. It didn't happen.
Sandoche.
Dear all, Anyone interested in volunteering as a co-chair is encouraged to step forward. Details about the process is explained in my previous mail below. Sandoche. On 13/04/2022 12:27, sandoche Balakrichenan wrote:
Dear Colleagues
As Constanze's term as IoT WG co-chair is about to end with RIPE 84, this is a call for nominations or volunteers to co-chair the RIPE IoT working group.
*********************************************************************** Please DO NOT reply to this message if you wish to propose a volunteer. ***********************************************************************
I would ask for each candidate to start a new thread with, e.g., "[name] for co-chair", and for members to utter their support by replying to the respective thread.
Provided there are no reasoned objections from the WG, I'd like to set *May 16th* as a deadline for showing support on the mailing list, so that we can announce the decision on *18th May* during the IoT WG sesssion at RIPE 84.
More information about WG co-chair responsibilities (https://www.ripe.net/publications/docs/ripe-692). If you'd like further information, don't hesitate to contact me or Constanze.
Have a nice day! Sandoche
_______________________________________________ iot-wg mailing list iot-wg@ripe.net https://lists.ripe.net/mailman/listinfo/iot-wg
To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit:https://lists.ripe.net/mailman/listinfo/iot-wg
-- Sandoche BALAKRICHENAN Head of R&D Partnerships @ Afnic LoRaWAN Academia WG Chair & RIPE IoT WG Co-Chair
Dear Colleagues, Anyone interested in volunteering as a co-chair is encouraged to step forward. Details about the process is explained in my previous mail below. Sandoche.
On 13/04/2022 12:27, sandoche Balakrichenan wrote:
Dear Colleagues
As Constanze's term as IoT WG co-chair is about to end with RIPE 84, this is a call for nominations or volunteers to co-chair the RIPE IoT working group.
*********************************************************************** Please DO NOT reply to this message if you wish to propose a volunteer. ***********************************************************************
I would ask for each candidate to start a new thread with, e.g., "[name] for co-chair", and for members to utter their support by replying to the respective thread.
Provided there are no reasoned objections from the WG, I'd like to set *May 16th* as a deadline for showing support on the mailing list, so that we can announce the decision on *18th May* during the IoT WG sesssion at RIPE 84.
More information about WG co-chair responsibilities (https://www.ripe.net/publications/docs/ripe-692). If you'd like further information, don't hesitate to contact me or Constanze.
Have a nice day! Sandoche
_______________________________________________ iot-wg mailing list iot-wg@ripe.net https://lists.ripe.net/mailman/listinfo/iot-wg
To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit:https://lists.ripe.net/mailman/listinfo/iot-wg
-- Sandoche BALAKRICHENAN Head of R&D Partnerships @ Afnic LoRaWAN Academia WG Chair & RIPE IoT WG Co-Chair
_______________________________________________ iot-wg mailing list iot-wg@ripe.net https://lists.ripe.net/mailman/listinfo/iot-wg
To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit:https://lists.ripe.net/mailman/listinfo/iot-wg
-- Sandoche BALAKRICHENAN Head of R&D Partnerships @ Afnic LoRaWAN Academia WG Chair & RIPE IoT WG Co-Chair
Dear Colleagues, We still don't have a Candidature for the IoT WG Co-Chair. As you know, Constanze is not standing for the second term and it would be helpful to have a new Co-Chair announced during the RIPE 84 IoT WG session on Wednesday 18th May. Details about the process is explained in the mail below. Sandoche
On 13/04/2022 12:27, sandoche Balakrichenan wrote:
Dear Colleagues
As Constanze's term as IoT WG co-chair is about to end with RIPE 84, this is a call for nominations or volunteers to co-chair the RIPE IoT working group.
*********************************************************************** Please DO NOT reply to this message if you wish to propose a volunteer. ***********************************************************************
I would ask for each candidate to start a new thread with, e.g., "[name] for co-chair", and for members to utter their support by replying to the respective thread.
Provided there are no reasoned objections from the WG, I'd like to set *May 16th* as a deadline for showing support on the mailing list, so that we can announce the decision on *18th May* during the IoT WG sesssion at RIPE 84.
More information about WG co-chair responsibilities (https://www.ripe.net/publications/docs/ripe-692). If you'd like further information, don't hesitate to contact me or Constanze.
Have a nice day! Sandoche
participants (4)
-
Aaron Ding -
Jim Reid -
Michael Richardson -
sandoche Balakrichenan