(Sending this from a private account as the one having posting rights). Dear Rob,
Much appreciated and I know from experience that time management for these meetings can be challenging, especially in a hybrid environment. And most certainly appreciate the care and respect for the AV-crew and everybody else who have little choice but to wait until we’re done, before they themselves can have a break. As for audio, I also don’t know - went to the testing protocol when connecting, Did notice an echo when I started to speak, so cut my own monitor to remove a possible source. Which at least probably explains part of the two-way comms issue. As for future interactions and looking for room of improvement, several meetings run a pre-agreed and pre-announced time for interventions, some even produce a visible clock. It ain’t ideal, but in my experience it does work. To the people thinking it was pre-recorded, it wasn’t, but maybe it should have been. To take a more general view on the topic, some stakeholders also have to take into consideration accountability to their own constituencies. Especially in the government sector people are less inclined or maybe not even permitted to speak freely and want to feel assured by having some pre-written text at hand. Whether, also with the other constraints you mentioned, this working group was the most appropriate or accommodating venue for this particular discussion, I leave to the community leadership to decide. On a personal note, I would recommend to also look in particular needs, habits or requirements for the various stakeholders in further and future work to improve the RIPE meetings in relation to diversity and inclusions. RIPE is and should remain a multi-stakeholder venue, some mutual adjustment could probably help to get and keep all stakeholders meaningfully engaged. As other speakers also attested to this afternoon, the subject at hand unfortunately and painfully shows the risks when a singular group stakeholder group runs off with the topic and devises their own solution. I have not yet looked up the transcripts, got some informal confirmation that my message came through. Looking forward to RIPE, together with the RIPE NCC, to provide some plan on how to deal with e164.arpa and the existing delegations underneath in manner that is consistent with responsible stewardship of the Internet’s unique identifiers, also in cases where a particular actor decides toi withdraw support from previously agreed arrangements. And apologies for taking so much time valuable floor time this afternoon, another lesson learned. Groet, MarcoH PS: yes, the instructions not working as designed, I still take a personal booboo. > On 20 May 2026, at 17:43, Rob Evans <[email protected]> wrote: > > Dear all, > > I wanted to note that the session today could have gone better, and your > co-chairs will be thinking about how we handle future sessions. We will take > the blame for that. > > There is a limit to how far we over-run due to the subsequent General > Meeting, and out of respect to the stenographers, note-takers, and > participants who may have other commitments. > > The presenters need to provide enough information for people to react to and > comment on, and that must balance with the amount of time for that > discussion. In the majority of meetings the discussion is limited. We knew > that would be different today, which is why I made a point of asking speakers > to keep to time and participants at the microphone to keep their comments > concise. > > I will find out what happened to Marco’s audio, but one lesson learned is > that there needs to be an effective two-way communication between the room > and remote participants. > > Meanwhile, can I encourage participants to take the topics up on the list? > > All the best, > Rob > > ----- > To unsubscribe from this mailing list or change your subscription options, > please visit: > https://mailman.ripe.net/mailman3/lists/ncc-services-wg.ripe.net/ > As we have migrated to Mailman 3, you will need to create an account with the > email matching your subscription before you can change your settings. > More details at: https://www.ripe.net/membership/mail/mailman-3-migration/ ----- To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/ncc-services-wg.ripe.net/ As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings. More details at: https://www.ripe.net/membership/mail/mailman-3-migration/
