<!DOCTYPE html> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body> <div class="moz-cite-prefix">Moin, am 30.04.24 um 13:57 schrieb Simon-Jan Haytink: </div> <blockquote type="cite" cite="mid:e8fbf961-49ff-4ffc-84d7-34978f9fc40a@ripe.net"> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> <span style="font-size:11pt;font-family:Arial,sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;white-space:pre-wrap;">As an association, we need to ensure we do not become too dependent on large multinational contributors that can easily move registrations to other RIRs. </blockquote> Well, IANAL, but I'd like to understand why anybody should be able to move "their" resources out of the RIPE Service Region in the first place. If they are not to be used within the RIPE Service Region anymore, clearly the provisions for allocating these resources (from those managed by the RIPE NCC for the RIPE Service Region) don't apply anymore, hence these have to be returned to the RIPE NCC. <blockquote type="cite" cite="mid:e8fbf961-49ff-4ffc-84d7-34978f9fc40a@ripe.net"><span style="font-size:11pt;font-family:Arial,sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;white-space:pre-wrap;">We see and have accepted the fact that last year’s category model was not without its flaws. To ensure we can actually submit a model that is as good as possible, we will need time to further consult with our members, and that could well result in a category or tiered model. […] <span style="font-size:11pt;font-family:Arial,sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;white-space:pre-wrap;">Overall, we see and acknowledge the need to seriously review our charging model, but what we are asking for is time and stability in the short term so we can put in the required work to come up with a model that works.</blockquote> So, what happened between April 2023 and April 2024 in this area? Did I miss the request for input for a new charging model after the proposed category model failed approvement last year? See, I do read your lines, but I fail to see appropriate action by the Board in this regard — only after the current backfire came statements like yours, but that's just too little much too late, imho. Regards, -kai <pre class="moz-signature" cols="999">-- Kai Siering Senior System Engineer mail.de GmbH Münsterstraße 3 D-33330 Gütersloh Tel.: +49 (0) 5241 / 74 34 986 Fax: +49 (0) 5241 / 74 34 987 E-Mail: <a class="moz-txt-link-abbreviated" href="mailto:k.siering@team.mail.de">k.siering@team.mail.de</a> Web: <a class="moz-txt-link-freetext" href="https://mail.de/">https://mail.de/</a> Geschäftsführender Gesellschafter: Fabian Bock Sitz der Gesellschaft Nordhastedt Handelsregister Pinneberg HRB 8007 PI Steuernummer 18 293 20020</pre> </body> </html>