July 2021 - ripe-list - mailman.ripe.net

RIPE Database Requirements Task Force – Draft Report Published
by Bijal Sanghani 11 Aug '21

11 Aug '21

Dear colleagues, The RIPE Database Requirements Task Force has just published a draft report for your review: https://www.ripe.net/participate/ripe/tf/rdb-requirements-tf/the-ripe-datab… In this third draft, we’ve added new recommendations and edited our document based on feedback received via emails, survey and during our third BoF in May. Please review this draft and share any comments on the ripe-list before Friday, 13 August 2021. The task force will reconvene in August to discuss the feedback received and work on its final report that will be published ahead of RIPE 83. We look forward to your feedback. Best Regards, Bijal Sanghani

1 1

Call for AFRINIC’s registry service migration to other RIRs
by Paul Wollner 01 Aug '21

01 Aug '21

The concerns expressed by TISPA, as well as other concerned parties and especially by AFRINIC's own admission in the news outlet lexpress.mu, which is attached to this email, regarding the AFRINIC’s inability to keep providing its core registry functions due to its inability to meet its financial requirements. I suggest that in order not hold end users, ISPs and any other business's hostage, for the interest of continue service of AFRINIC’s core registry service, we should urgently call for NRO fulfil their responsibility as well as commitment to the global internet to take over AFRINIC’s registration service for the time being, until litigation is settled some time later. (https://www.nro.net/accountability/rir-accountability/joint-rir-stability-f…) That way, no end user or business will ever impacted however results come out of litigation. Regards Paul Wollner

4 3

shatel contact
by Randy Bush 25 Jul '21

25 Jul '21

apologies to use the list for an operational issue :) anyone with friends/contacts in shatel? many sources in their customer cone are pinging a friend's well-known infrastructure site annoyingly. i wrote to the abuse contact (in american <blush>), and got back an email from RT. i asked my son-in-law to translate and he laughed, it's farsi, not arabic <reblush>. google translate says it is a pretty useless "if you have an account maybe we can help," and of course i do not have an account. any help appreciated. thanks. randy

1 0

Interim RIPE NCC Services WG Session on Cloud Strategy
by Felipe Victolla Silveira 22 Jul '21

22 Jul '21

Dear colleagues, The RIPE NCC Services WG will be holding an interim session on our cloud strategy on 28 July at 16:00 (UTC+2). If you would like to participate, you can find the details for this session here: https://www.ripe.net/ripe/mail/archives/ncc-services-wg/2021-July/003446.ht… <https://www.ripe.net/ripe/mail/archives/ncc-services-wg/2021-July/003446.ht…> At this session we will give an update on our current thinking and hear more from the RIPE community* to see if we can find a path towards rough consensus. We will publish an initial draft strategy shortly after the WG session and continue the discussion from there. Our strategy will also include some principles for how we will engage with the community around our core services and we will discuss this in the session as well. Kind regards, Felipe Silveira Chief Operations Officer RIPE NCC *The beginning of this discussion in the RIPE NCC Services WG can be found at: https://www.ripe.net/ripe/mail/archives/ncc-services-wg/2021-June/003408.ht… <https://www.ripe.net/ripe/mail/archives/ncc-services-wg/2021-June/003408.ht…>

1 0

Three new ripe-documents published under RIPE Governance Category
by Mirjam Kuehne 20 Jul '21

20 Jul '21

Dear colleagues, As mentioned in my recent update on RIPE Labs, the following three documents are now available in the RIPE Document Store: A Guide for New RIPE Working Group Chairs (ripe-765) https://www.ripe.net/publications/docs/ripe-765 Mailing List Guidelines for RIPE Working Group Chairs (ripe-764) https://www.ripe.net/publications/docs/ripe-764 RIPE Meeting Programme Committee: Appointment, Roles and Responsibilities (ripe-763) https://www.ripe.net/publications/docs/ripe-763 You can find other documents related to RIPE Governance here: https://www.ripe.net/publications/docs/ripe-documents/ripe-governance Kind regards, Mirjam Kühne

2 2

Open House today : RIPE Community Resilience and Wellbeing
by Erik Bais 14 Jul '21

14 Jul '21

Hi, This is a short reminder that today is the Open House online meeting for the RIPE Community Resilience and Wellbeing session that we did during the RIPE82 plenary. If you like to join, please make sure you register: https://www.ripe.net/participate/meetings/open-house Regards, Erik Bais

1 0

NRO Statement on Allegations Against AFRINIC
by Ulka Athale 13 Jul '21

13 Jul '21

This message is sent on behalf of the Number Resource Organization (NRO) ------------------------ The original statement is available at: https://www.nro.net/statement-of-the-number-resource-organization-on-allega… ------------------------- Statement of the Number Resource Organization on Allegations Against AFRINIC It has come to the attention of the Number Resource Organization (“NRO”) that certain members of the Internet community have expressed concerns regarding AFRINIC, the Regional Internet Registry (“RIR”) for Africa, and its operations. Through messages posted on various community mailing lists, allegations have been made against AFRINIC and the performance of its duties as an RIR. While the issues raised are best resolved by the RIR at issue, the NRO provides the following statement to the global Internet community. Each RIR manages services in its respective region. AFRINIC has been duly recognized globally to administer number resources in its region. The very nature of the allegations reveals a disagreement with AFRINIC on its implementation of its Registration Services Agreement as well as community-developed policy. All RIRs, on occasion, face allegations of errors in implementation of policy or agreements, and such disputes, being routine in nature, are best handled by the individual RIR and/or its community and related legal and courts system. It would be inappropriate for the NRO or any other organization to address issues that relate to the RIR’s service region and policies developed by its community. NRO Executive Council Regards, Ulka Athale Senior Communications Officer RIPE NCC

1 0

Hisham Ibrahim Appointed Chief Community Officer
by Hans Petter Holen 12 Jul '21

12 Jul '21

Dear colleagues, I am pleased to announce the appointment of Hisham Ibrahim as our new Chief Community Officer, leading our community and engagement activities. Engagement is at the heart of all our activities as the secretariat to the RIPE community and as a membership organisation. Our community and engagement activities include community development, public policy and Internet governance, learning and development, communications, membership engagement, event organisation and our web presence. Hisham has over 15 years of experience in Internet policy and technology and a deep knowledge of the European, African and Middle Eastern markets, and is actively involved in several NOGs, peering and technical forums across three continents. I welcome him to this new role and look forward to seeing him strengthen our efforts to better serve the community and membership. Kind regards, Hans Petter Holen Managing Director, RIPE NCC

1 0

Global internet stability is at risk due to AFRINIC's current mismanagement
by Anthony Ubah 08 Jul '21

08 Jul '21

Dear Community, We are writing this letter to let you know that AFRINIC's recent actions have brought some serious risks to the hundreds of millions of users of the Internet Ecosystem. A global internet depends on cooperation. Being one of five regional Internet Registries, AFRINIC has the power to delete the registration of more than a hundred million IP addresses. This power could be even more destructive with the addition of AS0 ROAs for space which is disputed or reclaimed. Therefore, billions users and large scale content and services that rely on those IP addresses could face instant lost of connection if AFRINIC starts revoking registrations of its members with IP addresses used in active service. Such disconnection will disrupt the connectivity of users as well as impact service at a global scale that has never been seen in human history. AFRINIC has been sending the following lines to members who have active users and service in their IP addresses: *“(AFRINIC) will in its sole discretion determine whether to immediately terminate the said Agreement as well as to proceed with the reclaiming of the aforesaid IP Number Resources.* *You are further informed that AFRINIC shall not be held liable for any loss or damage of whatever nature arising out of the present notice or any action that AFRINIC may take in accordance thereof.”* We have confirmed that many members have also received such notice on AFRINIC's pretense of violation of their RSA (Registration Service Agreement), in addition to their Bylaws, their CPM (Consolidate Policy Manual). The combined scale of those members services impacts tens of millions of Internet users and services globally. AFRINIC's claims were mainly based on the following: *1. "Any change in network or service provided, will request AFRINIC's approval and is subject to re-justification of the allocation.(NOT assignment)."* In reality, the CPM has provided a distinctive use of "Allocation" and "Assignment". Its intended allocations are for general purpose that LIRs can use or assign (or in some cases sub-allocate) and assignments are made within an allocation (or directly from AFRINIC to end users) to serve a specific purpose. To request an LIR to return its allocation when the specific purpose of the assignment has changed, has never happened in any RIR, and was never the intention of any RIR policy. *2. "AFRINIC space cannot be used outside of the AFRINIC region with the exception of soft landing space only for the purpose of supporting connectivity back to Africa. "* In fact, the community has manifested its consensus regarding the fact that there is no regional restrictions for the use of IP addresses for pre-soft landing space. The only territorial restrictions to ever gain consensus in the community specifically covers space issued after the start of the soft landing policy which is clearly stipulated under the CPM. Any act by AFRINIC to disregard this is a blatant act against the community-approved document, CPM. 3. Multiple AFRINIC resource members have been asked to provide information about third parties *that are not using addresses issued to said resource member (e.g. about BYOA(Bring Your Own Address) transit customers).* In scenarios where one resource member (A) is a customer of another resource member (B), there have been multiple instances of AFRINIC demanding that B report utilisation details of A. B is not responsible for the RIR compliance of B's customers except in regards to space issued to B under B's registration service agreement (RSA). Hence, AFRINIC's actions here attempt to force the resource member to violate customer confidentiality and potentially violate data protection laws. We know of a number of members whose resource requests have been delayed or denied pending compliance with such demands. In some cases, AFRINIC has gone so far as to threaten RSA termination based on failure to comply with these demands. *4. "AFRINIC can disconnect millions of users and services without taking any liability and at their will whenever they would like."* *(All the references to AFRINIC's claims, in their actual wording that were sent to the resource members, have been attached at the bottom of this letter, except for point 4, which was shared at the beginning of the letter)* The above claims do not correspond with AFRINIC's governing documents (CPM, RSA, and bylaw). They are a misinterpretation of those documents that have led to an incorrect conclusion. Using those claims to manage people’s network and trying to reclaim people active and legitimately utilised IP addresses without having any concerns about the end users or services that are being impacted is a direct and serious threat to the global internet. We are hoping the global community can realise and act together, to right this wrong. If you are part of AFRINIC's resource membership, please speak out and express your need for:: *1. **The freedom to run your network as you see fit* *2. **The ability to protect the internet connectivity of your users.* 3. *The ability to disclose only that data which is necessary for the legitimate administrative purposes of the registry.* The reference details of AFRINIC’s claims are shown as below: *Point 1:* *“AFRINIC acknowledges the feedback provided and further takes note that the current utilisation of the allocated no longer matches the "needs" expressed when resources were issued, in accordance with the RSA and we hereby refer you to clause 6(d)(iii) of the RSA; which your organisation signed, thereby acknowledged and agreed that the “right of use” of IP Number Resources is bestowed within the ambit of the “need” which is* *justified in its application and for no other purpose during the currency of the present agreement.”* *Point 2:* *“AFRINIC space cannot be used outside of the AFRINIC region with the exception of soft landing space only for the purpose of supporting connectivity back to Africa according to section 6 of the bylaw"* Section 6 of the bylaws only states what type of membership each entity qualifies for and the requirements of said membership, nothing about IP usage. The relevant portion of section 6 is below: 6.1) Subject to the other provisions of this Article, membership shall be open to: ● Any Person who is geographically based within, and providing services in the African region, and who is engaged in the use of, or business of providing, open system protocol network services; or ● Any other Person who is approved by the Board or the members. *Point 3:* AFRINIC requests the following information to its member regarding a customer that does not use his AFRINIC IP: *“Kindly provide the name and the actual service being provided to that client. Moreover, please share with us the reason that the client gave to justify their need for a third-party AS number. You may alternatively share the agreement which you have with that particular customer.”* The signatures of dozens of community members and resource members are attached in the Google drive link below : https://drive.google.com/drive/folders/1-4ihJZjnDpca4F0JUL8N3yY_eoGhiEjX?us… Regards,

1 0

Updated Draft Code of Conduct Published for Review
by Leo Vegoda 07 Jul '21

07 Jul '21

Dear RIPE community, As promised at RIPE 82, we have published an updated draft RIPE Code of Conduct. A clean text version of the document and a redline version, showing all the changes from the version published in March, can be found at: https://www.ripe.net/publications/docs/ripe-documents/other-documents/copy_… Please send comments in support of this draft, or asking for specific changes, to the RIPE Discussion List by 17 September 2021. The RIPE Chair will evaluate the community’s consensus based on comments made. Some of the key changes in this draft: - We have numbered the major sections and simplified some of the language - We have expanded the introduction to provide background on the discussion that led to the development of this document - We have added a new “Call to Action” section - We have clarified the language in the “Scope” section and removed the bulleted lists there - We simplified the subsection on law - We added a new subsection on aggressive behaviour in the “Behaviour” section - We added a section noting that reports that are not made in good faith, such as in retaliation for another report, can be rejected We have also published a RIPE Labs article about why we made the changes you’ll see in the new draft. https://labs.ripe.net/author/leo_vegoda/updated-draft-ripe-code-of-conduct/ We will hold a session with the community to discuss the changes, which has been scheduled for 1 September 2021. We recognise that it will not be possible for everyone to attend this webinar so it will be recorded and published, and we will release more information about the session nearer the time. Kind regards, Leo Vegoda for the Code of Conduct TF

2 1