October 2022 - ripe-list - mailman.ripe.net

Call for Topics for RIPE 85 Community Plenary
by Mirjam Kuehne 19 Apr '23

19 Apr '23

Dear colleagues, The call for proposals for RIPE 85 has been opened. The RIPE community plenary will take place on Thursday, 27 October, in the afternoon. If there are any specific topics you would like to discuss during this session, please let us know before 5 September. Kind regards, Mirjam Kühne RIPE Chair

1 1

v6
by Randy Bush 31 Oct '22

31 Oct '22

It's been 15 years, RIPE 55 to RIPE 85, since Gary Feldman sang "The Day the ROuters Died." We finally had a meeting where v6 transit was dominant. randy

5 4

Closing Discussion [was: A frank discussion]
by Mirjam Kuehne 31 Oct '22

31 Oct '22

Dear all, I don’t see any new arguments or new information in the recent mails sent on this topic. Everything has been said. I am closing this discussion now. Kind regards, Mirjam Kühne RIPE Chair and RIPE List Moderator

1 0

A frank discussion
by Lu Heng 29 Oct '22

29 Oct '22

Dear RIPE community and RIPE NCC members: You may be well aware of RIPE NCC management's refusal to acknowledge the serious governance issue in AFRINIC and the fact that the management keeps involving itself closely with governmental bodies, ever since the miscarriage of their NRO letter to make AFRINIC a specialized agency of United Nations. Recently, during the ITU Conference, it is said that the RIPE NCC management team seemed to have approached the American government and European Union government as a means to interfere with the ongoing matters. As someone who has had engaged closely with the community for many years, I believe it is of utmost importance for the community to be aware of the seriousness of the matter, and a frank discussion is more than necessary in the upcoming RIPE meeting. For RIPE NCC to make their case of seems deep interference with government and for me to exchange with the community any views and differences. My dispute with AFRINIC (despite it is sub-judice), is essentially a "policy dispute" between members of RIR and the RIR management. Court pocceding is also part of bottom up community driven process when the dispute can not be resolved amicably. However, NRO's request to make RIR an ITU-like body, and RIPE NCC's apparent consistent engagement with government officials to interfere in the matter, I think it is high time for the community to be aware of, discuss and decide whether such involvement is proper in a community driven, bottom-up registry who has been independent of governmental influences for more than three decades I have submitted an lighting talk for the plenary and got rejected. I have attached the rejection letter here for your perusal. It is disconcerting to me because the matter is of utmost urgency and importance for the community and the RIR system. The purpose of the current letter is to re-state my intention of an open, frank, heart-to-heart discussion with the community. I will appreciate if any working group chair can pick up the subject and do an BoF during the working group sessions. I believe the graveness of the issue requires such a discussion - transparency and accountability are the two core values of this community. Here is the letter I received: Dear Lu Heng, We regret to inform you that your Lightning Talk submission for RIPE 85 titled 'A difficult reality' has not been accepted into the Plenary session. >From the PC's perspective the presentation does not fit the RIPE plenary. If your submission refers to the role of the RIPE NCC, then we suggest the NCC Services WG as the appropriate venue to start this discussion. If you want to have a discussion about the RIPE community as a policy making body, then we feel the RIPE community plenary is the right place to go. Thank you, Franziska Lichtblau on behalf of the Programme Committee My reply: Hi The presentation is about ripe community’s view on current actions taken by NRO and RIPE NCC. The matter is extremely serious and I believe ripe community should be aware. And yes, this is about where boundaries of ripe community policy making and how many people should be aware and participate community. I feel current ripe community is not truly inclusive enough for every internet user aware. I think best we have a frank discussion and inform the community, rather have me go to some channels of communication, and community might feel not informed and asking why. And THIS IS REALLY NOT ABOUT NCC SERVICE. If PC have future questions welcome to send me zoom link to discuss. Lu Heng Chief Executive Officer LARUS Limited Email H.Lu@LARUS.netmailto:a.yan@outsideheaven.com Office tel:+852+29888918 Address A3, 11/F, TML Tower, Tsuen Wan, N.T, Hong Kong SAR Website: LARUS.net This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.

10 27

NRO NC Election Result
by Hans Petter Holen 28 Oct '22

28 Oct '22

Dear colleagues, We are pleased to announce that James Kennedy was re-elected to the Number Resource Organization Number Council (NRO NC) at the elections held during RIPE 85 (24-28 October 2022). James will serve a three-year term starting on 1 January 2023 and ending on 31 December 2025. Details on the election process and the NRO NC are available at: https://www.ripe.net/nro-nc/nominations-oct-2022/ We would like to congratulate James on his appointment! Kind regards, Hans Petter Holen Managing Director RIPE NCC

1 0

Re: [ripe-list] [members-discuss] A frank discussion
by Lu Heng 28 Oct '22

28 Oct '22

Hi Alex: See inline: Lu Heng Chief Executive Officer LARUS Limited Email H.Lu@LARUS.netmailto:a.yan@outsideheaven.com Office tel:+852+29888918 Address A3, 11/F, TML Tower, Tsuen Wan, N.T, Hong Kong SAR Website: LARUS.net This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. ---- On Thu, 27 Oct 2022 21:00:11 +0800 Alex Le Heux <aleheux(a)tucowsinc.com> wrote --- What I support: - The RIPE NCC cooperating with other governance structures in the world. - The RIPE NCC taking any action it deems neccessary to safeguard the RIR system from outside threats and support other RIRs in their proper functioning. Asking RIR to be specialised agency of the united nation is none of above, unless you consider give RIR leadership immunity in order to escape community scrutiny is "protecting RIR system from outside threats". What I do not support: - Continued attempts by some members to gaslight the RIPE NCC into not doing the above. Revealing the attempt by RIR leadership to give up community to the united nation is not gaslighting RIPE NCC not doing above as well. It called Whistleblowing. If Community indeed want to be specialised agency of the united nation collectively, it is not up to me to make such decision, I would not agree, but if this indeed is the community position, we can be open and transparent about it. Keep confusing the community on "giving up community for governmental control" with "cooperation with governmental body", is not helping here. Alex Le Heux _______________________________________________ members-discuss mailing list mailto:members-discuss@ripe.net https://lists.ripe.net/mailman/listinfo/members-discuss Unsubscribe: https://lists.ripe.net/mailman/options/members-discuss/h.lu%40larus.net

1 0

Re: [ripe-list] [members-discuss] A frank discussion
by Sander Steffann 28 Oct '22

28 Oct '22

Hi, > On 27 Oct 2022, at 15:00, Alex Le Heux <aleheux(a)tucowsinc.com> wrote: > > What I support: > > - The RIPE NCC cooperating with other governance structures in the world. > - The RIPE NCC taking any action it deems neccessary to safeguard the RIR system from outside threats and support other RIRs in their proper functioning. > > What I do not support: > > - Continued attempts by some members to gaslight the RIPE NCC into not doing the above. Thank you for summarising this, +1 Cheers, Sander

1 0

RIPE 85 Highlights - Day 4
by RIPE NCC Event Team 28 Oct '22

28 Oct '22

Dear colleagues, Thursday was the second and last day of the RIPE Working Group sessions – you can find some highlights from the day at: https://ripe85.ripe.net/programme/blog/ Today we continue with several plenary sessions and lightning talks followed by the Closing Plenary. The meeting will close at 12:30 (UTC+2). You can find the meeting plan at: https://ripe85.ripe.net/programme/meeting-plan/ Stay tuned for what’s happening at RIPE 85 by following @ripemeeting on Twitter and using the #RIPE85 hashtag. Kind regards, RIPE Meeting Team

1 0

SBAS Survey Results
by David Hausheer 27 Oct '22

27 Oct '22

Dear RIPE, in December 2021, the RIPE community was asked [1] to help by answering to a survey about the Secure Backbone AS (SBAS) architecture. Now, we would like to follow-up with the results of that survey which are included in a recent USENIX paper: Creating a Secure Underlay for the Internet https://www.usenix.org/system/files/sec22-birge-lee.pdf A full description of survey questions and results is contained in a tech report: https://arxiv.org/abs/2206.06879 [1] https://www.ripe.net/ripe/mail/archives/ripe-list/2021-December/002400.html Kind regards, David Hausheer

1 0

on the existence of this list: a suggestion
by Joe Abley 27 Oct '22

27 Oct '22

Hi all, Having foolishly neglected to either register to attend this week's meeting in person or on-line (you can follow the stream without registering, but I don't think you can send questions to the mic line), I thought I would send some small thoughts about the question of moderation of this list to this list. I would suggest that this list is used today for three main purposes: 1. Announcements; 2. Controversial topics and undesirable commentary that in recent times has often triggered active moderation; 3. Discussions about the operation, nature, purpose and value of the list itself, of which this e-mail is an example. It seems to me that there are better ways of achieving (1) than an open mailing list; we would arguably be better off without (2) altogether and (3) only has value so long as the list in its current form continues to exist. The days in which this list was used to advance the ideals of the community (and hence the Internet) in a practical, meaningful or operational way are long past, I think. Those conversations continue but they do not happen here. I think this is more likely to be a natural consequence of generational differences in the way that people communicate than a result of the way this list is implemented or operated. Other communication platforms are widely used today (and have long been widely used) for conversations relating to the Internet, the RIPE community and the RIPE NCC. I do not think this list is a necessary prerequisite for accountability or transparency. Unless people really think (2) and (3) have a value that exceeds the demonstrated cost of keeping this list alive, I suggest it should be closed. It's surely healthier for a community to adapt than it is to cling onto the past. Joe

1 0

RIPE 85 Highlights - Day 3
by RIPE NCC Event Team 27 Oct '22

27 Oct '22

Dear colleagues, Yesterday at RIPE 85 saw more than 1096 people registered. On Meetecho, there were 254 unique participants in the main room and 115 unique participants in the side room, and more joined in via the RIPE 85 livestream and YouTube. Wednesday was the first day of the RIPE Working Group sessions – you can find some highlights from the day at: https://ripe85.ripe.net/programme/blog/ Today we continue with more working group sessions: Anti-Abuse, MAT, DNS, IoT, Database and Cooperation. You can find the meeting plan at: https://ripe85.ripe.net/programme/meeting-plan/ Stay tuned for what’s happening at RIPE 85 by following @RIPEMeeting on Twitter and using the #RIPE85 hashtag. Kind regards, RIPE Meeting Team

1 0

RIPE 85 Highlights - Day 2
by RIPE NCC Event Team 26 Oct '22

26 Oct '22

Dear colleagues, The second day of RIPE 85 ended with 1050 people registered. On Meetecho, there were 244 unique participants in the main room and 43 unique participants in the side room, and more joined in via the RIPE 85 livestream and YouTube. Tuesday we continued with plenary sessions and held two BoFs. You can find some highlights from the day at: https://ripe85.ripe.net/programme/blog/ Today, we kick off our working group sessions: Routing, Address Policy, Open Source, IPv6, Connect and RIPE NCC Services. You can find the meeting plan at: https://ripe85.ripe.net/programme/meeting-plan/ Stay tuned for what’s happening at RIPE 85 by following @ripemeeting on Twitter and using the #RIPE85 hashtag. Kind regards, RIPE Meeting Team

1 0

Re: [ripe-list] [members-discuss] A frank discussion
by Lu Heng 25 Oct '22

25 Oct '22

Hi Toma:That is exactly what Hans have been trying to confuse the community about.NRO letter is asking the government taking over RIR in exchange for immunity for RIR leadership , not asking government being part of community, but essentially ignore all the other stake holders, have government taking oversight rule -and abandon the 30 years community self governance. I am all for government stay as part of the community in multi stake holder model.But this is not the problem, and not the discussion needed here.Lu HengChief Executive Officer LARUS LimitedEmail H.Lu(a)LARUS.net Office +852 2988 8918 Address A3, 11/F, TML Tower, Tsuen Wan, N.T, Hong Kong SARWebsite: LARUS.netThis email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.---- On Tue, 25 Oct 2022 23:00:26 +0800 ximaera(a)gmail.com<ximaera(a)gmail.com> wrote ----Peace, On Mon, Oct 24, 2022 at 10:11 AM Lu Heng <h.lu(a)larus.net> wrote: > For RIPE NCC to make their case of seems deep interference with government > > [..] > > NRO's request to make RIR an ITU-like body, and RIPE NCC's apparent > consistent engagement with government officials to interfere in the matter, > I think it is high time for the community to be aware of, discuss and > decide whether such involvement is proper in a community driven, > bottom-up registry who has been independent of governmental > influences for more than three decades Outreach and mutual knowledge sharing between ASO/NRO and governments/intergovernmental organizations is neither anything new, nor a sign of any change in the way number resource authorities perform their duties in the multistakeholder model. You may want to get acquainted, for instance, with ICANN GAC duties and operations. https://gac.icann.org/about -- Töma

2 2

RIPE 85 Highlights - Day 1
by RIPE NCC Event Team 25 Oct '22

25 Oct '22

Dear colleagues, The first day of RIPE 85 kicked off with over 390 attendees registered onsite for the meeting. Here are the highlights: - The meeting was opened by Mirjam Kühne, the RIPE Chair, who welcomed attendees for our second hybrid RIPE Meeting. - Presentations throughout the plenary sessions were well-attended, with 324 unique participants in the main room on Meetecho and 132 unique participants in the side room, and more joining in via the RIPE 85 livestream and YouTube. - We wrapped up the first day with a welcome reception to meet the RIPE Chair Team, Mirjam Kühne and Niall O'Reilly, and the RIPE NCC Executive Board. You can catch up with what happened on Day One by reading our Daily Meeting Report: https://ripe85.ripe.net/programme/blog/ Today we continue with the plenary sessions and two BoFs. You can find the meeting plan at: https://ripe85.ripe.net/programme/meeting-plan/ -------------------- PC Elections -------------------- The call for nominations is still open until 15:30 (UTC+2) today. You can nominate yourself or someone else by sending an email with a biography and photograph to pc [at] ripe [dot] net. There are currently two seats up for election to the RIPE Programme Committee. The RIPE PC online voting system will open today at 16:00 (UTC+2) and close on Thursday, 27 October at 17:00 (UTC+2). The results will be announced during the closing plenary on Friday. --- Stay tuned to what’s happening at RIPE 85 by following @RIPEMeeting on Twitter and using the #RIPE85 hashtag. Kind regards, RIPE Meeting Team

1 0

RIPE 85 Opens Today
by RIPE NCC Event Team 24 Oct '22

24 Oct '22

Dear colleagues, RIPE Chair Mirjam Kühne will open RIPE 85 today at 14:00 (UTC+2). You can follow our second hybrid RIPE Meeting online in the following ways: - On Meetecho - Via the livestream on the RIPE 85 website - On YouTube More information on how to participate can be found at: https://ripe85.ripe.net/ To stay up-to-date with the latest RIPE Meeting updates, follow us on Twitter: @ripemeeting, #ripe85 Kind regards, RIPE Meeting Team

1 0

LIR and Member Agreements
by denis walker 21 Oct '22

21 Oct '22

Colleagues [I make no apologies for the length of this email. There are so many errors to discuss. For an overview you can stop reading at the line of '----'. Below that is the detailed review of all the errors.] I have been reading lots of policies, procedures and agreements/contracts over the last couple of months to catch up with current and historical developments of address policy and it's application to allocating resources. It has been an eye opener. Right now I want to focus mainly on the 'RIPE NCC LIR Account Agreement'. Most of the documents I have read are poorly written. This is probably one of the worst. I will itemise below the details of what is wrong with this document. But firstly I will point out some of the serious mistakes. In this agreement there is a definition in Article 1... -RIPE NCC services The Membership Services provided through an LIR account as specified in the current version of the RIPE NCC Activity Plan. In the 'RIPE NCC Standard Service Agreement" there is also this definition in Article 1... -RIPE NCC services The Membership Services as specified in the current version of the RIPE NCC Activity Plan. There are no Membership Services specified in the current version of the RIPE NCC Activity Plan. There hasn't been such a specification since the activity plan of 2017. So for the last 5 years all the active SSAs and LIR Agreements have been referring to an 'empty list'. As both these agreements revolve heavily around these services, I have no idea what the legal significance is of agreements based on an empty list of services. Another serious issue is the absolute, total lack of any legal definition of an LIR (Local Internet Registry) and LIR account and the relationship between LIR and Member. I have not been able to find any such definitions anywhere on the ripe.net website. I fear they may be mentioned in some early RIPE document written 20 years ago that no one could reasonably be expected to find in relation to these agreements. Then we have in Article 3 of the SSA: "the Member acknowledges and accepts that it has obtained the right to use the RIPE NCC services under the conditions outlined in this agreement." And in Article 3 of the LIR Agreement: "the Member acknowledges and accepts that it has obtained the right to use the RIPE NCC services through this LIR account under the conditions outlined in this Agreement." So under what conditions can a Member use these (undefined) services? -those in the SSA -those in the LIR Agreement -a superset of the two sets -the intersection of the two sets ********** I want to put forward a suggestion that the RIPE NCC engages the services of, or employs, a professional contract lawyer to review and if necessary re-write all of the agreements/contracts used by the RIPE NCC. Or at least someone with legal training and experience in the area of contract writing. ********** It was said in a zoom meeting last Wednesday (about reviewing the PDP) that we should keep to a minimum the legal terminology and rely on common sense. That was a valid mindset in the 1990s when the internet was mostly an 'old boys/girls club'. In 2022 this is a very different global, critical industry. The IPv4 market has also changed this industry. There is so much money invested in IPv4 addresses that one 'wrong' decision by the RIPE community could face a legal challenge. If the RIPE NCC has to go to court to defend such an action they would have a better defence based on rock solid, well written, legally watertight contracts than based on a set of poorly written, contradictory documents, common sense and a generally accepted view of how things work(ed). Almost every document I have read has mistakes in it. Some have lots more than others. I wondered why people sign contracts with so many mistakes. Then I realised that most of the Members are not native English speakers, and neither are their lawyers. They almost certainly pass these documents through some translation app. Probably they accept some of the errors as translation errors. So if they go to court over these contracts it will be a case of an LIR arguing over what they think they signed, vs the RIPE NCC defending what they think they wrote. Neither will be a true reflection of reality. I know some people will criticise me for pointing out 'trivial' grammar errors in this document. (Some people will just criticise me anyway.) They will say they are not important. There are much bigger issues to deal with. We don't want to get lawyers involved in this process. Common sense will always prevail. If it ain't broke don't fix it...etc etc. This LIR Agreement is a legal contract at the core of the RIRs business (and it is broken). The quality of this document should reflect the professionalism of the RIR. As a legal contract it should be rock solid, well written and legally watertight. If there is ever a legal dispute with a Member, this contract, along with the equally error ridden SSA, may take centre stage. Do you really want to gamble on a contract that looks like it was written as an undergraduate project? For a native English speaker reading these documents, the grammar errors just leap off the page. They are trivial to find and fix. (So why have they not already been fixed?) For the legal and other content errors, a contract lawyer would not be expected to make such basic, clumsy mistakes. It is the three 'C's that present the biggest problem - Consistency, Continuity and Contradiction. Someone needs to have a clear view in their mind of the entire document set. When a document is changed or a new document is written they should know where to look to ensure integrity is maintained across the whole set. That simply has not been the case up to now. ---------------------------------------------------- So let's look at this LIR agreement in more detail. I am basing my comments on this version: https://www.ripe.net/about-us/legal/ripe-ncc-lir-account-agreement There is no definition of LIR or LIR account or any explanation of the relationship between a Member and an LIR (account). Article 1 "The Membership Services provided through an LIR account as specified in the current version of the RIPE NCC Activity Plan." There is no list of services in the activity plan. Article 2.2 "To enter into this Agreement for additional LIR accounts the Member must send to the RIPE NCC...one copy of the Agreement containing the handwritten signature of an authorised representative of the Member." This is ambiguous. It could suggest you sign one agreement for the initial LIR and one agreement for all additional LIR accounts, not one agreement for 'each' additional account. It should say: "To enter into this Agreement for each additional LIR account, the Member must..." Is it possible for a Member to delegate operational control of an LIR account to another (anonymous) company or natural person in the same way some Members delegate management of their RIPE Database objects to a consultant? It is not clear if an LIR account is an administrative concept or something tangible that can be delegated. As the initial LIR account is not subject to any agreement (see below) that one can certainly be delegated. Article 2.3 "The RIPE NCC reserves the right to amend this Agreement. The RIPE NCC shall notify the Member of such amendments at least one month before these amendments come into effect." This clause is almost certainly unenforceable. It is also ridiculous. It says the RIPE NCC can make any change it wants to this agreement at any time (after you have signed it) without any consultation with any individual, group or community and without any consensus, approval or acceptance and put the change into effect and expect all LIRs to comply with the change. If the NCC wants to fix the simple grammar errors, they would probably get away with it. Any substantive change would almost certainly be met with a legal challenge. They cannot impose a substantive change on 20k+ signatories. The SSA says: "2.3 The Member acknowledges and accepts that the RIPE NCC Standard Service Agreement may be amended by a resolution of the General Meeting of the RIPE NCC according to the procedure outlined in the RIPE NCC Articles of Association. An amendment shall automatically become effective upon the date mentioned in the resolution or the date of first publication of the resolution of the General Meeting and the full text of the amended agreement on https://www.ripe.net, whichever is the latest, without the re-signing of the RIPE NCC Standard Service Agreement being necessary." The same conditions must apply to changing the LIR Agreement. Article 3.3 "The Member acknowledges applicability of, and adheres to, the RIPE Policies and RIPE NCC procedural documents." Use of 'Member' and 'LIR' are interchanged throughout these documents. This agreement is about an LIR account. Do policies also apply to the LIR account or just to the Member? This is not clearly defined. Article 3.4 "The Member shall provide the RIPE NCC with complete, updated and accurate information necessary for the provision of the RIPE NCC services and shall assist the RIPE NCC with audits and security checks as outlined in the RIPE NCC procedural documents, and in particular with the RIPE NCC procedural document “Due Diligence for the Quality of the RIPE NCC Registration Data”." Is this the same information required by Article 2.2 of the SSA? Articles 2, 3 and 6 of the SSA overlap considerably with Articles 2 and 3 of the LIR Agreement. Such overlaps encourage contradictions between separate contracts. Article 3.6 refers to the document ‘Closure of Members, Deregistration of Internet Resources and Legacy Internet Resources' https://www.ripe.net/publications/docs/ripe-775 This document (ripe-775) was last updated on 30 Dec 2021, which is quite recent. Yet in Section B.1.b it says: "Internet number resources are allocated/assigned based on a specific need. When the original technical requirements or the business purpose for the use of the Internet number resources changes, the allocation/assignment becomes invalid. If the RIPE NCC notices any change in the original technical criteria or the original business purposes for using the Internet number resources, the RIPE NCC is authorised to deregister the relevant Internet number resources." This conflicts with ripe-733 'IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region', Section 5.1 which says: "On application for IPv4 resources LIRs will receive IPv4 addresses according to the following: - All allocation requests are placed on a first-come-first-served waiting list. No guarantees are given about the waiting time. - The size of the allocation made will be exactly one /24. - The sum of all allocations made to a single LIR by the RIPE NCC is limited to a maximum of 256 IPv4 addresses (a single /24). If this allocation limit has been reached or exceeded, an LIR cannot request an IPv4 allocation under this policy." No mention of any 'need' based requirement. This has been the case at least since November 2019. This shows the lack of continuity and contradictions between these documents. Article 3.7 says: "Unless otherwise specified in this Agreement, this Agreement is valid only for one specific LIR account. If the Member wishes to operate an additional LIR accounts, the Member shall sign an additional RIPE NCC LIR Account Agreement." Note the plurality of "an additional LIR accounts". It may be a simple typo. But as written it supports my comment above on Article 2.2 that maybe only one agreement needs to be signed for all additional LIR accounts. Article 4.2 "The Member's obligation to pay any fees corresponding for the LIR account of this Agreement" 'for' instead of 'to' - Another simple grammar error. Article 4.3 "The Member shall make the payment to the RIPE NCC within 30 days of date of invoice" of 'the' date - Another simple grammar error. (Or perhaps even 'within 30 days of the date of the invoice') Article 4.4 "without prejudice to any other of the RIPE NCC's rights which it may revoke against the Member in connection with the latter's failure to effect (timely) the payment." 'other' is in the wrong place, 'to any of the RIPE NCC's other rights' 'revoke' instead of 'invoke' '(timely) the payment' instead of 'the (timely) payment' More simple grammar errors. Article 4.1 refers to the 'RIPE NCC Charging Scheme 2022' and Article 4.6 refers to the 'RIPE NCC Billing Procedure and Fee Schedule' document This takes us off into billing and fees documents. I have reviewed these documents at the end. Article 5.2 "The Member shall be entitled to terminate this Agreement at any time." It doesn't say if the Member needs to give any notice period. Maybe: "The Member shall be entitled to terminate this Agreement at any time with immediate effect." Article 6.1 "The Member shall also be liable for all aspects of its use and all that ensues from its use from the Internet number resources." It should say 'its use of the Internet...' This wording, 'its use', only puts liability onto the Member if they use the resources themselves. It does not put liability onto the Member if they allow someone else to use the resources by assigning them. The wording should be 'the use' or 'any use'. Then the Member accepts full liability for use of these resources by anyone. Article 6.6 "The Member shall indemnify the RIPE NCC against any and all third party claims filed against the RIPE NCC in relation to the Member's use of the RIPE NCC services." Again the indemnity is limited to claims resulting from only the Member's use of the services. This article should say: "The Member shall indemnify the RIPE NCC against any and all third party claims filed against the RIPE NCC in relation to the any use of the RIPE NCC services provided to this Member through any of it's LIR accounts." Then it doesn't matter who is using the services. Article 6.7 "In any event the RIPE NCC's liability shall be limited to a maximum amount equivalent to the Member's service fee of the relevant financial year" This may apply in the event of the Member filing a claim against the RIPE NCC. If a third party files a claim against the RIPE NCC, I don't think the RIPE NCC can set it's own limit on the claim within an agreement the third party has not signed. Article 7.2 "The RIPE NCC's intellectual property (agreements, documents, software, databases, website, etc.) may only be used, reproduced and made available to third parties upon prior written authorisation from the RIPE NCC." If the Member has been allocated address space and they sub-allocate part of that space to another organisation, this is an acceptable use of the address space. By making assignments from the sub-allocation the second organisation will make use of the RIPE Database. This is an acceptable use of the RIPE NCC's intellectual property (database) without written authorisation needed. Article 8.2 "Any disputes that may arise from this Agreement shall be settled in accordance with the RIPE NCC Conflict Arbitration Procedure." This highlights one of the base issues with this LIR Agreement. It clearly started life as a copy of the SSA which was then modified to create the LIR Agreement. If you replace 'this Agreement' with 'the RIPE NCC SSA' you have the basis of Article 11.2 of the SSA. The problem in this Article 8.2 is that the Conflict Arbitration Procedure (ripe-691) is specific to the SSA. Disputes arising from the LIR Agreement are not within scope, according to both the Introduction and Section A.1. of the Procedure. But even in Article 11.2 of the SSA "shall be settled" should be changed to "may be settled". There is always the option to take a dispute to a national court. (Incidentally after a quick read, I only found one error in ripe-691. In Section C.1. "timeframe cannot not exceed".) Article 2.2 "By signing the RIPE NCC Standard Service Agreement as instructed by the RIPE NCC the Member confirms that they have read, understood and agree to be bound by the terms of this agreement for an initial LIR account." After writing all of the above I was told by a Member that they don't sign an LIR Agreement for their initial LIR account. It is somehow implied by signing the SSA. The LIR Agreement is only signed for additional LIR accounts. Now I understand the intention of the wording of Article 2.2 but it is complete madness. You can NOT hold me to the terms of this agreement because I signed some other agreement that makes no mention of this one. IF the SSA included something like this "The LIR Agreement forms an integral part of this SSA. By signing the SSA the Member agrees to be bound by the terms of the LIR Agreement for their initial LIR account." then it would be valid. BUT the SSA makes no mention anywhere of the LIR Agreement. In fact the SSA only mentions 'LIR' 7 times and they are all links to the 'Closure of LIR...' procedure. Article 6.1 of the SSA does say: The Member acknowledges applicability of, and adheres to, the RIPE Policies and RIPE NCC procedural documents. The RIPE Policies and the RIPE NCC procedural documents are publicly available from the RIPE NCC Document Store. These documents, which may be revised and updated from time to time, form an integral part of and apply fully to the RIPE NCC Standard Service Agreement. Each revised document will receive a new document number and can be found on https://www.ripe.net." It then includes a non-exclusive list of these documents, which does not include the LIR Agreement. There are several key points in Article 6.1 that specifically EXCLUDE the LIR Agreement from being an integral part of the SSA. Although the term 'procedural documents' is not defined anywhere, just like LIR, it would be a considerable stretch of the imagination to include an agreement or contract in a commonly understood definition of a procedural document. It also specifically says in 6.1 that the 'procedural documents are publicly available from the RIPE NCC Document Store'. The LIR Agreement is not listed in the document store. It also says 'Each revised document will receive a new document number'. Unlike the SSA, the LIR Agreement does not have a document number. The LIR Agreement is therefore NOT an integral part of the SSA. Signing the SSA does not bind a Member to the terms of the LIR Agreement. This opens an entire can of worms. None of the Member's initial LIR accounts are registered as LIR accounts. None of them are subject to any terms or conditions. As the charging scheme requires a service fee per (registered) LIR and these initial LIR accounts are not registered, technically Members do not need to pay a fee for their initial LIR accounts. Another interesting point is that all RIPE NCC procedural documents are said to form an integral part of the SSA. These documents may be 'revised and updated'. Article 2.3 of the SSA says changes to the SSA need a resolution by the GM. Under what conditions can a procedural document be changed if it is an integral part of the SSA? How is a new procedural document implemented if it becomes an integral part of the SSA? ********** As I said at the start of this email, it will benefit the RIPE NCC to employ someone qualified or experienced in contract law to review and re-write all the NCC's contracts and agreements so they actually say what they were intended to mean. ********** Moving on to the billing docs referenced in the LIR Agreement, there seems to be 3 significant documents which contradict each other. One even contradicts itself. The referenced 'RIPE NCC Billing Procedure and Fee Schedule' document https://www.ripe.net/participate/member-support/payment is marked as last updated on 19 Dec 2018 but refers to the fees for 2022 and has probably been updated each year. What it says is confusing: "RIPE NCC members pay a membership fee every year. For 2022, this fee is €1,400. This is charged on a pro rata basis for new member. New members also pay a sign-up fee, which is currently €1,000. Members can have more than one LIR account, but they must pay the membership and sign-up fee for each LIR account." Again total confusion between Members and LIR accounts. The 'RIPE NCC Charging Scheme 2022' refers to this as a 'service fee' not a 'membership fee'. It doesn't make sense to refer to it as a membership fee and then say it is paid per LIR account. This wording also suggests that there is a sign-up and annual fee for being a member and also a sign-up and annual fee for each LIR account, including the initial LIR account. It makes no distinction between initial and additional LIR accounts. 'This is charged on a pro rata basis for new member.' should say 'new members' - Another simple grammar error. In the 'RIPE NCC Charging Scheme 2022' document https://www.ripe.net/publications/docs/ripe-771 it says: "New members or additional LIR account registrations also pay an additional one-time sign-up fee alongside their annual contribution." Again this is grammatically totally wrong. It uses 'or' instead of 'and'. Also an 'LIR account' is not an entity that can pay anything. It should say: "An additional one-time sign-up fee is paid alongside the annual contribution for new members and when new LIR accounts are registered." In the 'RIPE NCC Billing Procedure 2022' document https://www.ripe.net/participate/member-support/payment/ripe-ncc-billing-pr… it has the same incorrect sentence as the Charging Scheme document: "New members or additional LIR account registrations also pay an additional one-time sign-up fee alongside their annual contribution." In 2.1 the image does not match the table immediately following the image. In Column A of the table it should show the one-time sign-up fee for New Members as 'per LIR account'. For Existing Members it should show the one-time sign-up fee for 'Additional LIR accounts' also in Column A. In 3. it is not clear if the service fees for all LIR accounts set up by a new member will be applied pro rata. Also there is no mention if the service fees for an existing member who sets up additional LIR accounts during the year will pay a pro rata fee for the new LIR accounts. It also says the 'pro rata for each quarter' will be based on 'the time of the year the membership application is submitted.' This has to be the time of year the SSA is concluded. You cannot reasonably charge for services before the period in which the services are made available. In 3.1 it says "The annual invoices will be sent to members between the end of the first quarter and the beginning of the second quarter of 2022." This time period does not exist. It has to be either 'after the end of the first quarter' or 'before the start of the second quarter'. In 3.2 it says "Members are responsible for providing and maintaining correct billing." It should be 'billing details'. In 3.3 it suggests that payment for any Member LIR account can come from any source. There doesn't appear to be any requirement for the payment details to match up with the Member legal entity or natural person. Surely this is open to abuse, fraud or money laundering possibilities? I have done an extensive review here of the LIR Agreement and touched on some of the errors in the SSA and billing documents. Almost every policy, procedure, agreement, contract, document I have read has one or more grammar and/or content errors. Maybe it is time for a full review.... cheers denis co-chair DB-WG

16 23

New on RIPE Labs: RIPE Chair Team Report October 2022
by herve.clement＠orange.com 20 Oct '22

20 Oct '22

Dear all, I've realised after my yesterday message that I should have mentioned all the presentations/events dedicated to the ASO AC (NRO NC) next week in Belgrade: - There will be Wednesday morning an ASO AC activities update presented by James Kennedy during the Address Policy Working Group (https://ripe85.ripe.net/programme/meeting-plan/ap-wg/), - followed by a presentation of the NRO NC election (https://www.ripe.net/participate/internet-governance/internet-technical-com…) This election will also be presented Monday Afternoon (https://ripe85.ripe.net/programme/meeting-plan/plenary/) For all information don't hesitate to contact the RIPE (NCC) ASO AC representatives: - James Kennedy (jameskennedy001(a)gmail.com) - Sander Steffann (sander(a)steffann.nl) - or myself (herve.clement(a)orange.com) Kind regards Hervé -----Message d'origine----- De : CLEMENT Herve INNOV/NET Envoyé : mercredi 19 octobre 2022 23:51 À : RIPE List <ripe-list(a)ripe.net> Cc : 'Mirjam Kuehne' <mir(a)zu-hause.nl> Objet : RE: [ripe-list] New on RIPE Labs: RIPE Chair Team Report October 2022 Dear all, Thanks Mirjam for sharing this link. I would like to add that the ASO AC (Addressing Supporting Organisation Address Council - https://aso.icann.org/) will meet face-to-face during RIPE 85 on Monday 24 and 25 October from 9am to 12:30pm in Lavender Room. This meeting is open and, as the capacity of the room will probably be limited, a Zoom session will also be provided. The agenda is not completed yet, but I can share that the following subjects will be discussed: - Introductions - Day Job + Other - NRO EC - 2023 ASO Review (Informal) - Operational Procedure Review (https://aso.icann.org/documents/operational-documents/operating-procedures-…) - Work Plan 2022/2023 - Global vs Globally Coordinated Policy - PTI - Post Covid - ICANN 76 participation Don't hesitate if you have any questions. Hervé ASO AC Vice-Chair Orange Restricted -----Message d'origine----- De : ripe-list <ripe-list-bounces(a)ripe.net> De la part de Mirjam Kuehne Envoyé : mercredi 19 octobre 2022 09:46 À : RIPE List <ripe-list(a)ripe.net> Objet : [ripe-list] New on RIPE Labs: RIPE Chair Team Report October 2022 Dear colleagues, RIPE 85 takes place next week! The agenda is set, and attendees are preparing for what promises to be another vibrant RIPE Meeting. In this month's report, we look at what to expect next week and what else is happening in the community. https://labs.ripe.net/author/mirjam_kuhne/the-ripe-chair-team-reports-octob… Kind regards, Mirjam Kühne RIPE Chair -- To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/ripe-list _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

1 0

New on RIPE Labs: RIPE Chair Team Report October 2022
by Mirjam Kuehne 19 Oct '22

19 Oct '22

Dear colleagues, RIPE 85 takes place next week! The agenda is set, and attendees are preparing for what promises to be another vibrant RIPE Meeting. In this month's report, we look at what to expect next week and what else is happening in the community. https://labs.ripe.net/author/mirjam_kuhne/the-ripe-chair-team-reports-octob… Kind regards, Mirjam Kühne RIPE Chair

2 1

RIPE 85 is taking place next week!
by RIPE NCC Event Team 19 Oct '22

19 Oct '22

Dear colleagues, RIPE 85 will take place in a hybrid format from 24-28 October 2022. If you haven’t yet registered, follow this link to secure your place: https://ripe85.ripe.net/attend/register/ The meeting plan and draft programme are available online: https://ripe85.ripe.net/programme/meeting-plan/ More information about RIPE 85 can be found at: https://ripe85.ripe.net/ For updates about the meeting, follow us on Twitter @ripemeeting and by using the hashtag #RIPE85 . Kind regards, Alexandra Vos Event Organiser RIPE NCC

1 0

New on RIPE Labs: Updates to the RIPE Code of Conduct Process Documents
by Alun Davies 18 Oct '22

18 Oct '22

Dear colleagues, Having received feedback from the community, the RIPE Code of Conduct Task Force will be making further updates to the RIPE Code of Conduct Process Documents. In this article, read up on what updates they intend to make in light of that feedback, and how you can contribute to the discussion further at RIPE 85: https://labs.ripe.net/author/leo_vegoda/updates-to-the-ripe-code-of-conduct… Best regards, Alun Davies RIPE Labs Editor RIPE NCC

1 0

Join the Programme Committee @ RIPE 85
by Brian Nisbet 18 Oct '22

18 Oct '22

Colleagues, As usual at RIPE 85 there will be an opportunity to join the Programme Committee for the meetings. The RIPE Programme Committee is responsible for recruiting and selecting presentations for the RIPE Meeting Plenary sessions. There are currently two seats up for election to the RIPE PC. Please send nominations, with a biography, statement of interest and photograph, to pc(a)ripe.net The Charter of the RIPE Programme Committee - https://www.ripe.net/publications/docs/ripe-763 - provides more information about the composition and roles of the RIPE PC. Nominations for the RIPE 85 PC elections can be sent in from today, Tuesday, 18 October, until Tuesday, 25 October, 15:30 CEST (UTC+2). Please include a recent picture and short biography with your nomination. We will announce the PC elections at the RIPE meeting opening sessions, but interested parties can already nominate themselves. We will close candidate nominations on Tuesday, 25 October at 15:30 CEST (UTC+2) and publish the biographies on the RIPE Meeting web site. The RIPE PC online voting system will be open from Tuesday, 25 October, 16:00 CEST (UTC+2) until Thursday, 27 October, 17:00 CEST (UTC+2), for community members to cast their votes. The total voting numbers may be public. The official announcement of the elected RIPE PC members will be on the morning of Friday, 28 October, during the closing plenary session. This information is replicated on the RIPE 85 website with a breakdown of the important dates: https://ripe85.ripe.net/programme/ripe-pc/become-a-member/ Regards, Brian On Behalf of the RIPE PC Brian Nisbet (he/him) Service Operations Manager HEAnet CLG, Ireland's National Education and Research Network 1st Floor, 5 George's Dock, IFSC, Dublin D01 X8N7, Ireland +35316609040 brian.nisbet(a)heanet.ie www.heanet.ie Registered in Ireland, No. 275301. CRA No. 20036270

1 0

Polishing of RIPE Chair Selection Process
by Daniel Karrenberg 17 Oct '22

17 Oct '22

Greetings, The RIPE NomCom 2020 recommended to make the following improvements to the RIPE Chair selection process [ripe-762]: Consider changing ripe-728 to codify the use of a reserve list of volunteers in case voting members resign from the committee. Consider clarifying the example time-lines in ripe-727 and ripe-728 in the light of experience On request of the RIPE Chair I have drafted the attached revisions to these documents implementing these recommendations. Notes: Using a reserve list is not without alternatives. The IETF has had much relevant discussion about 'gaming' the volunteer selection process recently; see https://mailarchive.ietf.org/arch/browse/eligibility-discuss/# . My experience as NomCom chair strongly suggests to avoid complicating the procedures beyond the endurance of the volunteers involved. A simple reserve list is sufficient for our purposes. A wording change in ripe-728 tightens the time for getting the NomCom organised from 60 days prior to the consultation RIPE meeting to 90 days prior. This is necessary to enable the full NomCom rather than just the NomCom chair to issue the call for nominations. The time line appendix should be removed entirely from ripe-728 and the one in ripe-727 should be replaced with the attached one. Let's avoid cluttering the ripe-list and discuss this over on our venerable ripe-chair-discuss list please. Daniel

1 0

Response to the Two Documents from the Code of Conduct Task Force
by Leo Vegoda 13 Oct '22

13 Oct '22

Dear RIPE community, The Code of Conduct TF appreciates all of the feedback you have given on the draft process documents we shared. We will consider the many useful comments carefully as we review the documents one more time. We will soon publish a blog post addressing a number of these concerns in more detail. Some points we hope will be cleared up by our explanation, but others will require us to make changes in the draft documents, which we will lay out in the blog post. After publishing the blog, we will share the updated draft documents for your review. Kind regards, Leo Vegoda for the Code of Conduct TF

1 0

Apply for Quantum Internet Hackathon: 1-2 December, 6 locations & online
by Vesna Manojlovic 11 Oct '22

11 Oct '22

Dear RIPE colleagues :) The RIPE NCC is co-organising a Quantum Internet Hackathon simultaneously in six nodes on 1-2 December 2022. Join us in Amsterdam, Dublin, Padua, Poznan, Sarajevo, Tashkent - and online! Apply here: https://www.ripe.net/participate/forms/apply/quantum-internet-hackathon-202… Top-3 Goals of this event: * Sharing existing software and protocols for the Quantum Internet * Producing tools & documentation, or learning/interaction materials * Forging connections between participants and between nodes Partner organisations: PSNC, GÉANT, SURF, Trinity College Dublin, QuTech, University of Padova, INHA University in Uzbekistan, Maynooth University, University of Sarajevo, RIPE NCC Find out more here: https://labs.ripe.net/author/karla-white/take-part-in-the-quantum-internet-… Regards, Vesna -- Senior Community Builder, RIPE NCC https://labs.ripe.net/author/becha/

1 0

Re: [ripe-list] [members-discuss] Is NRO trying to make RIR into an ITU sister today?
by Hans Petter Holen 06 Oct '22

06 Oct '22

Dear Lu, I refer you to my last response[1] and repeat that we have no interest in debating Mauritian legal issues. I suggest you discuss this with the AFRINIC community. Regards Hans Petter Holen Managing Director RIPE NCC [1] Clarifications on NRO Letter to Mauritian Government: https://www.ripe.net/ripe/mail/archives/members-discuss/2022-July/004607.ht… >

1 0