- ncc-services-wg - mailman.ripe.net

Call for presentations at RIPE 90
by Rob Evans 24 Mar '25

24 Mar '25

Hi all, We are seven weeks away from the start of RIPE 90 in the lovely city of Lisbon. The RIPE NCC Services Working Group is scheduled, as is traditional, for Wednesday afternoon, immediately prior to the General Meeting. If you have an item for the agenda, please let us know via <ncc-services-wg-chairs(a)ripe.net <mailto:ncc-services-wg-chairs@ripe.net>>. Cheers, Rob on behalf of Janos and Stefan.

1 0

Enabling Partial Payment Online Options
by Simon-Jan Haytink 06 Mar '25

06 Mar '25

** *Dear all,* * We have been investigating the option of partial online payments made via credit card and we have some good news to report. We expect that we will be able to provide this option in our systems later in March for all members who need it. I realise this comes quite late in the current payment cycle, but we hope it will provide a good option for those who still need it. Members in our service region who are affected by war or natural disasters can request a payment extension. If these members need the partial payments option later in the month, requesting a payment extension will help ensure your membership status remains unaffected. You can apply for an extension using the form at: https://www.ripe.net/participate/forms/apply/payment-extension-form/ <https://www.ripe.net/participate/forms/apply/payment-extension-form/> I’d like to note that when using the partial payments option, the closing procedure will remain valid, and we ask that you pay as soon as possible. https://www.ripe.net/publications/docs/ripe-833/ <https://www.ripe.net/publications/docs/ripe-833/> We will let you know when the new partial payments facility is available. Best regards, Simon Jan Haytink RIPE NCC CFO *

1 0

Invoices partial payment
by Max Tulyev 18 Feb '25

18 Feb '25

Hi All, I would like to ask NCC to implement the posibility to pay the RIPE NCC invoices with credit card in several payments, i.e. implement partial payment of the invoice? As the NCC bills increased, it is not possible to pay it with the card at once, because of payment limits in many banks. Even the base fee without a lot of ASNs and sponsored resources may not fit. May be other LIRs have similar problems - please tell support it. Thank you!

6 9

RIPE NCC Quarterly Planning Q1 2025
by Adonis Stergiopoulos 19 Dec '24

19 Dec '24

Dear colleagues, We have now published the Q1 2025 quarterly plans for our development teams: https://www.ripe.net/support/documentation/quarterly-planning These plans include the work items that will be carried out over the next quarter and give you the chance to provide your feedback and suggestions that the RIPE NCC should be working on going forward. The plans cover the following areas: - RIPE Database - Business Applications, including the LIR Portal, Registry Services and other applications. - DNS and K-root - RIPE Atlas - RIPEstat - Resource Public Key Infrastructure (RPKI) - Routing Information Service (RIS) - Information Security, Risk, and Compliance - Training and Certification Please share your suggestions on this list or the RIPE NCC Forum: https://forum.ripe.net/ Kind regards, Adonis Stergiopoulos Senior Marketing & Communications Officer RIPE NCC

1 0

Notification of Updates to the RIPE NCC Procedural Document: Closure Procedure
by Theodoros Fyllaridis 25 Oct '24

25 Oct '24

Dear colleagues, The RIPE NCC Procedural document 'Closure of Members, Deregistration of Internet Resources and Legacy Resources' has been reviewed and updated. You can find the updated document at: https://www.ripe.net/publications/docs/ripe-833/. The following amendments were made: ----------------------------------- 1. Non-compliance with RIPE Policies: SSA termination and deregistration ----------------------------------- Section A.1.2. Termination by the RIPE NCC (1.2.1.1.b.) was amended through the addition of the word “repeatedly”. Previously the Closure Procedure suggested that allocations and assignments in contravention of the RIPE policies could lead to the termination of the SSA, even if the contravention took place only once. The amendments suggest that the SSA may be terminated if allocations and assignments are repeatedly not made and used in accordance with RIPE policies. This change creates an escalation process. If a violation of the RIPE community’s policies occurs only once, we will proceed with the deregistration of relevant resources. In case such violations take place repeatedly, we will proceed with the termination of the SSA. Section B. Deregistration of Internet Number Resources (1.b.) was amended by replacing “Invalidity of assignment criteria [...] relevant Internet number resources” with “Allocations/assignments in contravention of RIPE Policies [...] deregister the relevant records”. This provision only addressed a certain type of RIPE policy violation, which is no longer applicable. With these amendments, the old criterion has been removed and it allows the RIPE NCC to deregister the relevant records if allocations/assignments are not made and used in accordance with any RIPE policies. ----------------------------------- 2. SSA/Legacy Agreement termination for non-payment ----------------------------------- Members must pay their fees within 30 days from the date of the invoice. According to the previous version of the Closure Procedure, the RIPE NCC terminated the progress of any open requests for services and suspended the membership after 90 days from the date of the invoice. This time period has changed to 60 days and subsequently, Sections A. Closure of Member – Termination of the RIPE NCC Standard Service Agreement, (1.2.2.e.) and C.1. Termination of the Legacy Services (1.2.2.2.e.) have been amended accordingly to reflect this change. ----------------------------------- 3. Legacy Internet Resources ----------------------------------- The Closure Procedure previously stated that if the RIPE NCC became aware of reasons for terminating or upon the termination of the Legacy Services/Agreement, the RIPE NCC would take certain measures, such as: - Add the remark “No-contract”/”Under Review” in the RIPE Database resource object - Add a warning statement to the relevant records in the RIPE Database mentioning that the Legacy Internet Resources are not covered by a contractual relationship/are not in compliance with data accuracy requirements - Revoke any certificates generated by the RIPE NCC Resource Certification (RPKI) Service relating to Legacy Internet Resources - Withdraw the reverse delegation These measures should not be applied for the following reasons: - Technical amendments regarding attributes in the RIPE Database that took place some years ago allow resource holders to add, change, or remove some attributes, including the remarks line. The requirement for the RIPE NCC to add remarks/statements in the RIPE Database is no longer relevant, as the remarks can be removed at any time by the Legacy Holder. - RIPE NCC Certification (RPKI) Service is only revoked after the termination of the Legacy Services/Agreement and not when the RIPE NCC first becomes aware of any reasons for terminating the Legacy Service/Agreement. - Reverse DNS is an essential service that cannot be denied and RIPE NCC provides it regardless of the contractual status. Therefore, Sections C.1. Termination of the Legacy Services (1.1.2.1. and 1.2.2.1.) and C.2 Consequences were amended accordingly to reflect the above. Also, the Closure Procedure previously stated that upon deregistration of Legacy Internet resources, the RIPE NCC would: - Withdraw the reverse delegation; and - Delete all relevant objects in the RIPE Database, including allocation/assignment and route objects. Upon deregistration, we also revoke any certificates generated by the RIPE NCC Certification (RPKI) Service, therefore this step was added to Section C.4. Deregistration of Legacy Internet Resources which was amended accordingly. ----------------------------------- 4. Other changes ----------------------------------- 4.1. Section A.1.2. Termination by the RIPE NCC (1.2.1.2.) Previously the Closure Procedure stated that the termination notice would officially inform about the termination of the SSA, state the reasons for the termination, and detail the planned arrangements regarding the Internet number resources that were distributed to the Member. The wording "distributed to the Member" implied that resources were distributed to the Member by the RIPE NCC and may exclude resources received via transfers or Legacy Internet resources. For clarity, we replaced the wording “distributed to” with “registered to”. 4.2. Section A.2.1.2. Registration of Distributed Internet Number Resources We removed the word “distributed” from the title, since it implied that Internet resources were distributed to the Member by the RIPE NCC and may exclude resources received in any other way. We also added a note to clarify that this section does not apply to Legacy Internet Resources. 4.3. Sections: A.2. Consequences (2.1.1., 2.1.2.), B2. Procedures for Deregistration of Different Types of Internet Number Resources (2.1., 2.2.) In several sections, the RPKI service is referred to as RIPE NCC Resource Certification (RPKI) Service. RIPE NCC Certification (RPKI) Service is how it is referred to in RIPE NCC Certification Service Terms and Conditions. For consistency purposes, this wording is updated throughout the Closure Procedure. 4.4. Section A.2. Consequences 2.1. End of Provision of RIPE NCC Services (2.1.1.) The previous wording stated that by the end of provision of RIPE NCC Services, the RIPE NCC would stop providing services, including participation in RIPE NCC training courses. Since last year, training courses (webinars) are available to non-members, therefore we updated the wording “RIPE NCC training courses” to “training and certification services offered to Members”, which is more accurate. Kind regards, Theodoros Fyllaridis Legal Counsel RIPE NCC

1 0

Language Support and Community-Sourced Translations
by Fergal Cunningham 24 Oct '24

24 Oct '24

Dear all, I want to let you know that we have moved our translated content to a new language centre on www.ripe.net. You can access it from the languages icon on the top right of our website, or go directly to: https://www.ripe.net/languages/ We currently provide material in six languages (Arabic, Farsi, Italian, Russian, Spanish and Turkish). And we are now opening up translations to the membership and community. You can help us translate content into your language by filling out the volunteer form at: https://www.ripe.net/participate/forms/apply/ripe-community-translators/ I explain all this and what we hope to achieve with these initiatives in a RIPE Labs article at: https://labs.ripe.net/author/fergalc/language-support-and-community-sourced… All the best, Fergal Cunningham Head of Membership Engagement RIPE NCC

1 0

2nd RIPE Labs article on the Draft Activity plan and Budget 2025 published
by Simon-Jan Haytink 22 Oct '24

22 Oct '24

Dear all, Yesterday, I published a RIPE Labs article on the RIPE NCC’s draft budget for 2025: https://labs.ripe.net/author/Simon-Jan/financial-stability-and-beyond-a-loo… In a follow up to Hans Petter's article on the RIPE NCC’s Draft Activity Plan, I take a look at the RIPE NCC's budget 2025, our financial stability and beyond. If you have any comments or questions, let me know! Kind regards, Simon Jan Haytink Chief Financial Office RIPE NCC

1 0

Co-chair nomination
by Rob Evans 18 Oct '24

18 Oct '24

Colleagues, The deadline for nominating candidates to be the NCC Services WG co-chair has now passed and we have received one nomination, Stefan Wahl. Stefan, feel free to introduce yourself. Ahead of the WG meeting in two weeks, I encourage messages of support (or otherwise) to the list or the existing WG co-chairs. Cheers, Rob on behalf of the RIPE NCC Services WG Co-chairs.

5 4

RIPE Labs article on the Draft Activity Plan and Budget 2025
by Hans Petter Holen 18 Oct '24

18 Oct '24

Dear all, Earlier this week, I published a RIPE Labs article on the RIPE NCC’s Draft Activity Plan and Budget 2025: https://labs.ripe.net/author/hans_petter_holen/building-resilience-the-ripe… In the article, I talk through the overall picture of the draft Activity Plan for 2025 and our commitment to long term resilience. If you have any feedback on the draft document or my article, please let me know on this mailing list or in person at RIPE 89. Kind regards, Hans Petter Holen Managing Director and CEO RIPE NCC

1 0

Draft agenda for RIPE 89 and call for co-chair nominations
by Rob Evans 11 Oct '24

11 Oct '24

Dear colleagues, We are four weeks away from the RIE NCC Services Working Group meeting at RIPE 89 in Prague, here is the draft agenda and the call for nominations to be one of the co-chairs of this working group. Draft Agenda 1. Welcome, admin. 2. Announcement of co-chair selection process (5 mins) 3. Planning for the Registry 2025, Hans Petter Holen, Managing Director, RIPE NCC (20 mins) 4. Planning for Information Services 2025, Felipe Victolla Silveira, Chief Technology Officer, RIPE NCC (20 mins) 5. Planning for External Engagement and Community 2025, Hisham Ibrahim, Chief Community Officer, RIPE NCC (20 mins) 6. Planning for Organisational Stability 2025, Hans Petter Holen, Managing Director, RIPE NCC (20 mins) 7. AOB (5 mins) Call for RIPE NCC Services Working Group Chair Please DO NOT reply to this message if you wish to volunteer or propose a volunteer. In accordance with the chair selection process we announce that the term of one of our co-chairs (Bijal Sanghani) will soon expire and we would like to invite volunteers, or nominations, for someone to become a co-chair of the RIPE NCC Services working group. Anyone may volunteer, and anyone may be nominated by someone else. To do this, please send a mail to ncc-services-wg-chairs(a)ripe.net before the end of Tuesday 15th October 2024. It would be helpful for candidates to provide some words as to why they think they ought to be a co-chair, what new ideas, or improvements they might bring, and so on. We will publish the list of volunteers, along with anything the volunteers include with their nomination, to this mailing list on Wednesday 16th October 2024. Discussion and support (or opposition) for each candidate can then be offered on the list. At the NCC Services working group session at RIPE 89, Janos and Rob will announce the candidate based on the mailing list discussion. Timeline Wednesday 2 October This call for volunteers posted to the ncc-services-wg mail list Tuesday 15 Oct Deadline for volunteers Wednesday 16 Oct List of volunteers and call for support posted to the mail list Tuesday 29 Oct Deadline for showing support for volunteers on the mail list Wednesday 30 Oct NCC Services WG session at RIPE 89 References The RIPE working group chair job description is included in ripe-692: https://www.ripe.net/publications/docs/ripe-692 A guide for New RIPE WG Chairs is in RIPE-765: https://www.ripe.net/publications/docs/ripe-765 The tasks associated with the RIPE WG Chair Collective are described in RIPE-749: https://www.ripe.net/publications/docs/ripe-749 The guidelines for managing WG mailing lists are in RIPE-764: https://www.ripe.net/publications/docs/ripe-764 The RIPE NCC Services working group chair selection process is documented here: https://www.ripe.net/participate/ripe/wg/active-wg/services/ripe-ncc-servic… RIPE WG Chair Training is available on the RIPE NCC Academy: https://academy.ripe.net/enrol/index.php?id=16#section-1 Of course, the RIPE Code of Conduct is described in RIPE-766: https://www.ripe.net/publications/docs/ripe-766 As always, please feel free to reach out to any of the chairs directly, to us as a group at ncc-services-wg-chairs(a)ripe.net, or discuss this or any other any relevant topic on this mailing list. All the very best, Rob on behalf of the RIPE NCC Service WG Co-chairs

1 1