January 2025 - members-discuss

Call for Volunteers for Executive Board Election Code of Conduct Team
by Ondřej Filip 22 Jan '25

22 Jan '25

Dear members, This is a call for volunteers from the membership to join the Executive Board Election Code of Conduct Team for the May 2025 General Meeting election. The Executive Board election of 2025 will be the fifth to have a Code of Conduct (CoC) for Executive Board Election candidates. This is separate from the RIPE NCC Code of Conduct and RIPE community CoC. This code only applies to confirmed candidates during the election process. The Executive Board Election Code of Conduct Team will evaluate reports of violations of the CoC and if a violation has occurred. The team for 2024 was made up of five volunteers and the Executive Board would like to express thanks to Cynthia Revström, Sebastian Becker, Nick Hilliard, Dr. Omid Mahdi Ebadati and Arnold Nipper who carried out this important work. The Executive Board would now like to ask for volunteers from the membership to be on the Executive Board Election Code of Conduct Team for the May 2025 election. The task of this team will be to evaluate any reports of violations of the election Code of Conduct by candidates. If the team confirms that a violation of the election Code of Conduct has taken place, disqualification of the candidate in question can take place. If you are willing to participate in this role, please send an email to: agm(a)ripe.net by *Wednesday 12 February 2025*. The Board will then appoint members of the team from the list of volunteers. Members should not volunteer if they expect to become candidates in the election. The Executive Board Election Code of Conduct can be found at: https://www.ripe.net/s/gm/may-2025/eb-election/coc/ Kind regards, Ondřej Filip RIPE NCC Executive Board Chair

1 0

Charging Scheme Task Force 2024 Meeting Minutes (10 December 2024)
by Karla Liddle-White 15 Jan '25

15 Jan '25

Dear RIPE NCC members, The Charging Scheme Task Force held a meeting on 10 December 2024. The minutes from the meeting are now available at: https://www.ripe.net/membership/mail/member-and-community-consultations/cha… The task force welcomes comments on the minutes, either on this list or you can email the task force directly at: charging-scheme-task-force2024(a)ripe.net The first task force meeting of 2025 will be held this week and we will keep you informed of the progress being made. Best regards, Karla Liddle-White Communications Officer RIPE NCC

11 12

Re: Charging Scheme Task Force 2024 Meeting Minutes (10 December 2024)
by sdy＠a-n-t.ru 15 Jan '25

15 Jan '25

Ok! Friends if you did it (moving to IPv6) please return IPv4 to RIPE. More people will be happy! Why not? > +1 > > -- > Kind regards > Sebastian Becker > > [T-Logo mit Schriftzug "Connecting your world."] > > The compulsory statement can be found here: > www.telekom.com/compulsory-statement<http://www.telekom.com/compulsory-statement> > > > Am 14.01.25, 08:55 schrieb "Gert Doering" <gert(a)space.net>: > Hi, > > On Tue, Jan 14, 2025 at 06:01:41AM +0300, > sdy(a)a-n-t.ru<mailto:sdy@a-n-t.ru> wrote: >> -- My decision IPV4 problem: > > This is the problem. Stop being obsessed with IPv4, move to IPv6. > > Gert Doering > -- NetMaster > -- > have you enabled IPv6 on something today...? > > SpaceNet AG Vorstand: Sebastian v. Bomhard, Ingo Lalla, > Karin Schuler, Sebastian Cler > Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) > Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279 > > ----------------------------- Serbulov Dmitry ANT sdy(a)a-n-t.ru

9 10

Charging Scheme Task Force 2024 Meeting Minutes (10 December 2024) - v6 and Legacy v4
by Brandon Butterworth 14 Jan '25

14 Jan '25

v6 categories. Is this not the time to go to a flat charge per holder regardless of size and avoid re creating the v4 problem. If v6 should follow v4 problems then the same category issues may arise. v4 legacy resources: A few things seem self evident 1. holders don't trust what might happen if they convert it 2. holders should not be put in peril if you want them to convert 3. once it is not legacy there is no going back unless the holder has not changed anything about it (ie they can roll back to escape unfavourable policy only). 4. when legacy changes hands then it should lose legacy status, triggers will include: if sold in some manner the controlling organisation changes and is no longer clearly part of the same org (with vagueness to cover gaming, RIPE decides). It has to remain in essentially the same legacy state or it is no longer legacy. Simplest is to just require legacy holders to be a member either for the legacy or any other space (so only one membership). brandon

1 0