cooperation-wg

Download

cooperation-wg@ripe.net

September 2026

3 participants
2 discussions

Welcoming new Cooperation Working Group Co-Chair
by Desiree Miloshevic 08 Sep '26

08 Sep '26

Dear cooperation WG members, Following Julf’s email bellow, please welcome Peter Koch as the new Cooperation Working Group Co-Chair. Upon Peter’s and Bastiaan’s agreement, Bastiaan Gosling’s term will start at the end of RIPE93, so we will hold off on congratulating him until then. We already have quite a few talks submitted for the RIPE93 WG session, but we always look forward to members' suggestions on topics of interest, and hereby invite you to submit your talk. Best regards, Achilleas, Peter and Desiree — RIPE Coop WG Co-Chairs — cut here -- ...two new co-chairs, one starting ASAP and one starting November 1 as Achilleas will be stepping down after RIPE93, so we have decided to select both Bastiaan and Peter, and allow them to decide amongst themselves who starts when. On behalf of the co-chair team I thank Bastiaan and Peter for volunteering, and want to remind everyone that being a WG co-chair is a purely voluntary job, with co-chairs normally covering their participation expenses themselves (just like presenters at WG sessions), so a big Thank You to both! As, when I stepped down at RIPE92, I agreed to stay on in an assisting function for the selection process, I now conclude that my job is done and I can fully step down as co-chair. Many thanks once again to all WG members and speakers, and especially my co-chairs Desiree and Acchilleas. Julf (on behalf of the coop WG chair team) --end--

2 1

Fwd: [ncc-services-wg] Draft liaison statement on Public ENUM under e164.arpa for the September 2026 ITU-T Study Group 2 meeting
by Jim Reid 07 Sep '26

07 Sep '26

Whoops! You wanted followup on this list and not ncc-services. Oh well... Here it is again. > Begin forwarded message: > > From: Jim Reid <jim(a)rfc1035.com> > Subject: [ncc-services-wg] Re: Draft liaison statement on Public ENUM under e164.arpa for the September 2026 ITU-T Study Group 2 meeting > Date: 24 August 2026 at 14:36:01 BST > To: Hisham Ibrahim <HMI(a)ripe.net> > Cc: ncc-services-wg(a)ripe.net > > > >> On 17 Aug 2026, at 15:48, Hisham Ibrahim <HMI(a)ripe.net> wrote: >> >> I would appreciate feedback on my draft and I would appreciate it if you could share any comments or concerns, particularly on the technical, procedural or governance aspects, by 25 August, so that the RIPE NCC can incorporate the feedback before finalizing the submission. > > Hisham, your proposed document is deeply flawed and unfit for purpose. That means I object to your proposal and obviously do not support it. I could go into this in detail but there's not enough time to do that. A submission to the next Study Group 2 meeting has to be submitted by tomorrow. BTW, that submission must be submitted as a Contribution. It can't be a Liaison Statement. Contact me off-list if you want an explanation. > > The Contribution that gets submitted by the NCC must be short and leave no loose ends that would open opportunities for nit-picking, requests for clarification, further unwelcome interference by the ITU and so on. Your suggested text won't do that. The objective must be to kill off C196 and leave no opportunities at ITU for exhuming it. C196 needs two shots to the head, just to be sure. If C196 drags on and on and on, it will be bad for everyone. > > Here's the text that should go in this Contribution. I hope it gets community support. > > The RIPE NCC regrets to inform Study Group 2 and the TSB that Contribution SG2-C-0196 (C196), was ill-prepared and based on misunderstandings. It does not reflect the opinion of the NCC or the RIPE Community. The RIPE NCC sincerely apologises for the confusion which has been caused. C196 should therefore be withdrawn. We respectfully request colleagues pay no further attention to C196 and proceed on the basis it had never been submitted to Study Group 2. > > We are happy to confirm there are no technical or procedural changes to the operation of the e164.arpa ENUM registry. RIPE NCC is pleased to inform Study Group 2 and the TSB that the current, long-standing agreements around this registry remain in place and are unchanged. It has no plans to alter them. The RIPE NCC will continue to operate this registry in the same neutral, stable and professional manner as it has done since e164.arpa was created. > ----- > 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/

10 10