April 2022 - ripe-list - mailman.ripe.net

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

Draft Document: RIPE Task Forces - Definition and Guidelines - v3
by Niall O'Reilly 27 May '22

27 May '22

Dear Colleagues, [Please view this message as either plain text or HTML, according to your preference.] In view of significant comments received during what we had expected to be a restricted last call, Mirjam and I have decided to make a fresh draft of the proposed document on RIPE Task Forces and to make this available for your review [here][v3]. An onward link leads to an [alternative presentation][v3chg] of the draft, in which recent changes are highlighted. We are very grateful to Boris Duval and Antony Gollan, who did most of the real work. We plan to close the review period just before 24:00 UTC on Sunday 10 April next, and to announce a two-week last-call period shortly after that. Please let us know what you think, in sufficient numbers so that we can understand whether the draft enjoys community consensus. For your convenience, the table below shows the dates when successive drafts of this proposed RIPE Document were announced. | Date | From | Remarks | |------------:|:-----------|:------------------------------------------------| | 19 Nov 2021 | M.Kuehne | [002363][] Draft; suggestions invited | | 16 Dec 2021 | N.O'Reilly | [002402][] Update; last call closing 14 Jan | | 3 Feb 2022 | N.O'Reilly | [002444][] Update; last call extended to 18 Feb | | 23 Mar 2022 | N.O'Reilly | [v3][] Fresh draft for review until 10 Apr | Best regards, Niall O’Reilly --- [002363]: https://www.ripe.net/ripe/mail/archives/ripe-list/2021-November/002363.html [002402]: https://www.ripe.net/ripe/mail/archives/ripe-list/2021-December/002402.html [002444]: https://www.ripe.net/ripe/mail/archives/ripe-list/2022-February/002444.html [v3]: https://www.ripe.net/publications/docs/ripe-documents/other-documents/ripe-… [v3chg]: https://ripe.net/publications/docs/ripe-documents/other-documents/ripe-task…

12 19

Code of Conduct BoF at RIPE 84
by Leo Vegoda 29 Apr '22

29 Apr '22

Dear RIPE community, The Code of Conduct TF will be conducting a BoF session at RIPE 84. We will discuss important information about the Code of Conduct Team, including details about its recruitment and training procedures. Anyone interested in joining the Code of Conduct Team is encouraged to attend to learn more. Virtual participation via Meetecho will also be possible during the session. We also want to extend the call for feedback on the draft process document that we have published. You can find the document here: https://www.ripe.net/publications/docs/ripe-documents/other-documents/draft… We have two questions for the community about their preferences for the Code of Conduct process: 1. How much authority should we delegate to the Code of Conduct Team—an advisory capacity, or a higher threshold? 2. Are you happy with the Code of Conduct Team's approach to temporary retention of personal data? Please share your feedback on the RIPE Discussion List by 9 May 2022. It will be useful to hear responses to our questions and/or any comments on the document, including general approval or otherwise. Many thanks, Leo Vegoda for the Code of Conduct TF

1 0

Revised PDP - Draft version 3 for your review
by Mirjam Kuehne 29 Apr '22

29 Apr '22

Dear colleagues, The deadline for comments to the changes we proposed to the revised Policy Development Process (PDP) document has passed. We reviewed the suggestions we received and made some adjustments accordingly. The new version (v3) is here: https://www.ripe.net/publications/docs/ripe-documents/other-documents/polic… At the top of the document you will find a link to a page showing the diff to v2 (and also a diff to ripe-710, the current PDP document). Below you find the main considerations and changes we made. In addition to that, the communication experts at the RIPE NCC cleaned up and tightened the language throughout the document to avoid misunderstandings. Before issuing a last call, we would like to ask you to review this new version again carefully and provide any feedback before 27 May 2022. In order to be able to build consensus, it is also important to let us know if you are happy with this revised version of the document. Kind regards, Mirjam Kühne RIPE Chair ========= Main changes and considerations in revised PDP v3: 1. Introduction We removed the distinction between author and owner and the sentence related to that distinction in the introduction. 2. The Process Based on feedback received for earlier versions of this draft, we kept the strong suggestion to share an idea with the community before it enters the formal policy process. We clarified that this is not mandatory and strengthened the motivation. 2.1. Status of a proposal We reviewed the suggestion to add a fourth status “abandoned” in addition to open, accepted and withdrawn. We decided not to add “abandoned” as this case is already covered by "withdrawn" or “open” (in case someone else picks up the proposal). 4. Appeals Process We did not see enough support for introducing a separate appeals body. But based on experience with the first appeal, the entire appeals process is defined a lot more clearly now. 5. Changes to the PDP We received a comment that changes to the PDP should follow the same process as other documents in RIPE. RIPE documents are typically agreed by community consensus. While a specific, formal process has been agreed for development of RIPE policy, enthusiasm in the community for using this process for other RIPE documents is currently low. Therefore we kept section 5. that describes how the PDP document is changed through community consensus.

1 0

New on the RIPE Labs Podcast: Keep Ukraine Connected
by Alun Davies 27 Apr '22

27 Apr '22

Dear colleagues, A little over a month ago, the Global NOG Alliance put out a call to this mailing list asking people to help keep Ukraine connected by donating hardware that could be used to rebuild the country's Internet infrastructure. Just a few weeks later, they delivered their first shipment of vital hardware into the country. In this new episode of the RIPE Labs podcast, I catch up with the team to talk about how the first delivery went, how this all got started, and what's coming next: https://labs.ripe.net/author/alun_davies/keep-ukraine-connected/ Best regards, Alun Davies RIPE Labs Editor RIPE NCC

1 0

IGF 2022 Call for Workshop Proposals
by Chris Buckridge 19 Apr '22

19 Apr '22

Dear colleagues, Please find below the call for workshop proposals for this year’s Internet Governance Forum (IGF), which is planned to take place in Ethiopia in November, but which will be a fully hybrid event (so you don’t need to be on-site to be an active participant, or even session organiser!). This IGF is happening at a very dynamic and significant moment for Internet governance - this is playing out in a variety of ways, not least in how the world’s governments are trying to engage with the Internet and exert varying degrees of control over its use and operations. You’ll note in the call for proposals that the IGF this year has been structured around five themes (each workshop proposal should relate back to at least one of these themes) - this is a deliberate strategy to reflect the themes that the UN has identified for a “Global Digital Compact” that it plans to develop in 2023 (see Commitment #7 here: https://www.un.org/en/content/common-agenda-report/#download <https://www.un.org/en/content/common-agenda-report/#download>). By structuring the conference in this way, it’s hoped that the IGF discussions will provide multistakeholder input to this development of this Global Digital Compact. The RIPE NCC (and our fellow RIRs) will be looking at how best to participate in IGF 2022, and will be happy to work with members of the RIPE community to ensure that this community’s perspectives and concerns are reflected in the discussions. If you’ve got any questions about the IGF or this process, please feel free to drop me a mail! Cheers Chris ——— Chris Buckridge Advisor to the Managing Director, Global Strategic Engagement RIPE NCC (…and your friendly neighbourhood IGF MAG member!) > Begin forwarded message: > > From: Chengetai Masango <chengetai.masango(a)un.org <mailto:chengetai.masango@un.org>> > Subject: [IGFmaglist] IGF 2022 Call for Workshop Proposals > Date: 15 April 2022 at 15:35:29 CEST > To: MAG-public <igfmaglist(a)intgovforum.org <mailto:igfmaglist@intgovforum.org>> > > Dear All, > > The IGF 2022 Call for Workshop Proposals <https://www.intgovforum.org/en/content/igf-2022-call-for-workshop-proposals> has now been published on the IGF Website: > > IGF 2022 Call for Workshop Proposals | Internet Governance Forum (intgovforum.org) <https://www.intgovforum.org/en/content/igf-2022-call-for-workshop-proposals> > > The deadline for submission is 3 June 2022, 23:59 UTC. > > We would be grateful if you could inform your respective networks. > > Best regards > > Chengetai > _______________________________________________ > Igfmaglist mailing list > Igfmaglist(a)intgovforum.org <mailto:Igfmaglist@intgovforum.org> > To unsubscribe or manage your options please go to http://intgovforum.org/mailman/listinfo/igfmaglist_intgovforum.org <http://intgovforum.org/mailman/listinfo/igfmaglist_intgovforum.org>

1 0

New on RIPE Labs: The RIPE Chair Team Reports - March 2022
by Alun Davies 14 Apr '22

14 Apr '22

Dear colleagues, In this month’s update from the RIPE Chair Team, read about the work that’s being done to make sure RIPE 84 will be an engaging and interesting event for those taking part both in person and online: https://labs.ripe.net/author/mirjam_kuhne/the-ripe-chair-team-reports-march… Best regards, Alun Davies RIPE Labs Editor RIPE NCC

1 0

RIPE Code of Conduct Process - Draft for Community Review
by Leo Vegoda 12 Apr '22

12 Apr '22

Dear RIPE community, The Code of Conduct TF has published a draft process document for your review. You can find it here: https://www.ripe.net/publications/docs/ripe-documents/other-documents/draft… We have also published a blog post that summarises the document and asks some specific questions here: https://labs.ripe.net/author/leo_vegoda/ripe-code-of-conduct-process/ The blog asks two specific questions. One is on the extent of authority to be delegated to the Code of Conduct Team. The other is on data retention. Please review the draft. Let us know your thoughts on our questions. And if you have other feedback then please share that, too. It's important to know if there is general support for the approach described in our draft. Many thanks, Leo Vegoda for the Code of Conduct TF

1 0

Second call for presentations RIPE 84
by Franziska Lichtblau 11 Apr '22

11 Apr '22

Dear RIPE community, the second round of our call for presentations for RIPE 84 in Berlin is still open. The RIPE Programme Committee is seeking content proposals from the RIPE community for the plenary sessions, lightning talks and BoFs. RIPE 84 is going to be a hybrid meeting this year so both in-person and virtual presentations would be accepted and encouraged. The deadline to submit a presentation proposal is Sunday, 17 April 2022. Proposals submitted after this date will only be considered if there are still time slots available. Red more about CfP amd submit your presentation proposal at: https://ripe84.ripe.net/submit-topic/cfp/ More about RIPE84 meeting: https://ripe84.ripe.net/ Best, Franziska Lichtblau (on behalf of the RIPE PC)

1 0

RIPE Working Group Chairs Collective Meeting Summary (March 2022)
by Mirjam Kuehne 11 Apr '22

11 Apr '22

Dear colleagues, The RIPE Working Group Chairs met in March to start preparing for the RIPE 84 Meeting in May. You can find a summary from the meeting here: https://www.ripe.net/participate/ripe/wg/wg-chairs/working-group-chair-coll… Kind Regards, Mirjam Kühne RIPE Chair

1 0

New on the RIPE Labs Podcast: Measuring Damage on the Internet
by Alun Davies 07 Apr '22

07 Apr '22

Dear colleagues, I’m pleased to announce we just released the first episode of the brand new RIPE Labs Podcast! In this episode, I ask Emile Aben how visualisations created from data available in RIPE Atlas and RIS can help network operators understand what's going on when parts of the Internet get damaged. Find out what Emile has to say about keeping things ‘lit’ and why better observability makes for a more stable Internet: https://labs.ripe.net/author/alun_davies/measuring-damage-on-the-internet/ Hope you enjoy our podcast and stay tuned for more! Best regards, Alun Davies RIPE Labs Editor RIPE NCC

1 0

ASO Call for Nominations to 2022 ICANN NomCom
by Ulka Athale 07 Apr '22

07 Apr '22

This message is sent on behalf of the Number Resource Organization (NRO). *** 7 April 2022 ICANN’s Nominating Committee (NomCom) is responsible for the selection of eight ICANN Board Members, two Public Technical Identifiers (PTI) directors, and other selections as set forth in the ICANN Bylaws. The 2022 NomCom will fill eight open leadership positions: three members of the ICANN Board of Directors, one member of the Public Technical Identifiers (PTI) Board of Directors, two regional representatives to the At-Large Advisory Committee (ALAC), one member of the Generic Names Supporting Organization (GNSO) Council, and one member of the Country Code Names Supporting Organization (ccNSO) Council. *The Address Supporting Organization Address Council (ASO AC) is pleased to invite nominations for candidates from the Internet Numbers Community to run for an open seat on the 2022 ICANN NomCom as delegate of the ASO.* The term for the elected delegate will be one year starting in the Annual General Meeting ICANN 75 in Kuala Lumpur in September 2022. Specific criteria and requirements regarding the NomCom composition and NomCom delegates are outlined in Article 8, Sections 8.2 and 8.4 of the ICANN Bylaws (https://www.icann.org/resources/pages/governance/bylaws-en/#article8). Criteria for the selection of the delegate to the NomCom include: 1. Accomplished persons of integrity, objectivity, and intelligence, with reputations for sound judgment and open minds, and with experience and competence with collegial large group decision-making; 2. Persons with wide contacts, broad experience in the Internet community, and a commitment to the success of ICANN; 3. Persons whom the selecting body is confident will consult widely and accept input in carrying out their responsibilities; 4. Persons who are neutral and objective, without any fixed personal commitments to individuals, organizations, or commercial objectives in carrying out their Nominating Committee responsibilities; 5. Persons with an understanding of ICANN’s mission and the potential impact of ICANN’s activities on the broader Internet community who are willing to serve as volunteers, without compensation other than the reimbursement of certain expenses; and 6. Persons who are able to work and communicate in written and spoken English. -------------------- Time Commitment for the ASO NomCom Representative -------------------- All positions require regular participation in virtual meetings via telephone and Zoom. The positions may involve significant international travel when pandemic-related travel restrictions lift. Reasonable and properly documented expenses incurred in the course of service by all selected leaders will be reimbursed. More information at the ICANN NomCom Webpage https://www.icann.org/nomcom2022 -------------------- Deadlines and Important Dates -------------------- The ASO AC will be responsible for the selection of the delegate based on the following timeline: Announcement of call for nominations for 2022 ICANN NomCom: 7 April 2022 Nomination period ends: 7 May 2022 Evaluation of nominations by the ASO AC: 8 to 18 May 2022 Voting period by the ASO AC: 19 to 26 May 2022 Announcement of selected delegate: around 27 May 2022 Nominations should be sent to secretariat [at] aso [dot] icann [dot] org by 7 May 2022 23:59 UTC, along with answers to the following questions (all questions are mandatory). A CV may also be provided. 1. Have you read the time commitment for NomCom and are you willing to commit the time required to fulfill this role? 2. Have you been part of a Nomination Committee in the past with ICANN or with any other organization? 3. How many ICANN/RIR meetings you have attended in last five years? Which SOs/ACs do you actively follow? 4. Please briefly share why do you would like to join NomCom as the ASO-AC appointee. Kind regards, ASO Secretariat *** Regards, Ulka Athale Senior Communications Officer RIPE NCC

1 0

An Open Internet Remains the Goal
by Hans Petter Holen 06 Apr '22

06 Apr '22

Dear colleagues, In this RIPE Labs article, I explain in detail why the RIPE NCC as an institution and many of my colleagues in the technical community believe it is crucial that we preserve the integrity of the RIPE Registry and that we continue to support all of our members, even in times of conflict: https://labs.ripe.net/author/hans_petter_holen/an-open-internet-remains-the… Best regards, Hans Petter Holen Managing Director RIPE NCC

1 0

"Keep Ukraine Connected" initiative: request for fiber optic welder/splicer kits and UPS systems
by Jan Zorz - Go6 04 Apr '22

04 Apr '22

Dear RIPE community, Sorry for another rather long email, but there are more and more requests from Ukraine operators coming in and we have no other way of getting specific equipment other than ask you - the community! Lately we got specific requests for fiber optics welding/splicing kits, specially from Kharkiv region that is/was under brutal attacks and lots of infrastructure is damaged. Let me copy/paste parts of messages that keep coming in so you get the feeling what people that are trying to keep the lights on in the fibers in Ukraine are dealing with: "In Kharkiv we provide continuous network access to other Ukrainian operators and providers. Our network suffers critical loads now because of shelling, and our co-workers repair it, sometimes, under the shots. We lack necessary equipment and tools and are not able to order. There is an urgent need for an optical fiber welding machine ( as we have to work in difficult conditions). The amount of work is growing, but the maintenance is missing. We want to ask you, if it’s possible, to give us at least one machine fujikura or fitel. We’ll be glad to receive even a used one, the most important is it should work." "I also wanted to ask - Do you have, maybe some power backup systems? Also there are our partners in the city - internet provider, who have de-energized nodes for 2-3 thousand active subscribers, in which there is simply no electricity ..." "is there any possibility to send some more of the same optical fiber machines? and if it is possible two or three of the simplest optical reflectometers." We are getting more and more similar requests, so our question to community would be if anyone has any new/used/spare FO welding/splicing kit to donate to Ukraine friends to keep the Internet up&running and people connected? Same goes for UPS systems... We at GNA have secured one Fujikura 41S+ Fusion Splicer Kit with CT50 Cleaver - partially donated by one of their distributors, partially covered by money donations to GNA "Keep Ukraine Connected" initiative that many of you sent in last couple of weeks and we are very grateful for!!! First delivery of requested hardware to Ukraine is now being coordinated with with our colleagues from the Ukrainian Association of Rights Holders and Content Providers, the Ukrainian Internet Association (UAI) and Ukraine Ministry of Digital Transformation and will take place next week. We would like to secure more fiber optics repair equipment and UPS systems before next delivery, so please - if you are willing and can help - contact us at ukraine(a)nogalliance.org for hardware donation or donate some funds at below web page so we are able to purchase needed equipment and send it to Ukraine with next delivery. https://keepukraineconnected.org/ Thank you again, Jan Žorž on behalf of GNA/KUC initiative

1 0

30 Years Ago Today
by Daniel Karrenberg 03 Apr '22

03 Apr '22

3 3