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

2023-03 Policy Proposal "Voluntary Transfer Lock" Implemented
by Angela Dall'Ara 03 Jan '24

03 Jan '24

Dear colleagues, We are pleased to announce that we have implemented the RIPE Policy Proposal 2023-03 “Voluntary Transfer Lock”. The new policy allows the holders of resources registered with the RIPE NCC to inform the RIPE NCC that certain resources must not be transferred for a certain amount of time. The archived policy proposal can be found at: https://www.ripe.net/participate/policies/proposals/2023-03 The RIPE Document "Voluntary Transfer Lock" is available at: https://www.ripe.net/publications/docs/ripe-806 The Request Form and Procedure are available at: https://www.ripe.net/manage-ips-and-asns/resource-transfers-and-mergers/vol… Kind regards, Angela Dall'Ara Policy Officer RIPE NCC

1 0

RIPE NCC Quarterly Planning Q1 2024
by Fergal Cunningham 20 Dec '23

20 Dec '23

Dear all, The Q1 2024 quarterly plans for our development teams are now published at: https://www.ripe.net/support/documentation/quarterly-planning Our quarterly planning includes the work we will be carrying out in the next few months in: - RPKI - Learning & Development - RIPE Database - Business Applications, including the LIR Portal, Registry Services and other applications - DNS and K-root - RIPE Atlas - RIPEstat - RIS - Information Technology - Information Security, Risk and Compliance The goals of publishing our planning are to be transparent about the work we will be carrying out in the coming months, to get your input on those plans, and to foster a dialogue with our members and the community about what you would like to see the RIPE NCC work on going forward. If you have any input on these plans or suggestions for future work, please reach out to us. Kind regards, Fergal Cunningham Head of Membership Engagement RIPE NCC

1 0

Figuring out RIPE meetings
by Shane Kerr 05 Dec '23

05 Dec '23

Dear RIPE NCC services working group, I spoke up during the RIPE NCC services working group during the AOB (any other business) time at the end of the session during the RIPE 87 meeting. We only had a very short amount of time, and I did not warn anyone. More than one person asked me for clarification, so I thought I should send an e-mail to explain. This is that e-mail. There are two places where discussions about the RIPE meeting could happen, either in the RIPE list (with the whole RIPE community) or in the RIPE NCC services working group (for non-member RIPE NCC services). I picked the RIPE NCC services, because I think it is basically about implementation and not about over-arching meeting goals. There is definitely discussion to be had about meeting goals - for example how to deal with a meeting that grows over time - but that is not my focus here. Basically I wanted to rant a bit about two things: 1. The last few meeting locations have not been great. 2. Communication about meetings has been been poor. The most recent meeting, near Rome, was in a location that meant you had to either stay in the meeting venue hotel or take a taxi to get to the meeting every day. It was also far away from the actual city, so getting out to visit a restaurant or even just be away from the venue at all took some time. There are a lot of valid complaints about the way the meeting venue was laid out, but my main concern was the choice of venue itself. The meeting before this, RIPE 86 in Rotterdam, was in a conference center. That is not necessarily bad - RIPE 78 in Rotterdam was in a conference center that was actually pretty good. In the case of RIPE 86 in Rotterdam the conference center was far from anything else, including hotels and restaurants. It could be reached by public transport or by just cycling or walking, so it was better than Rome, but still not great. RIPE 85 in Belgrade was probably a better location as far as venue. The main issues with that meeting were due to it being in Serbia, which has both benefits and drawbacks, but discussion about which countries or regions are appropriate for a RIPE meeting probably belongs on the RIPE list. I realize that there are a lot of reasons why venues were chosen, but I feel like we as the RIPE community have no insight into these. Which leads me to my second point of communication being poor. To me, it feels like we (the RIPE community) are basically just observers in how our own meetings are arranged, and end up having to accept whatever is delivered by our vendor (the RIPE NCC). I do not think this is how anyone wants the RIPE meetings to be arranged, and I definitely do not think that there is any blame here... possibly we have all kind of slowly moved into a situation where the RIPE NCC has done such a good job of handling meetings over the years that we just let them handle everything apart from the actual agendas and discussions. What I was asking for at the microphone at RIPE 87 was for more communication about future meeting planning from the RIPE NCC, and if possible some discussion around it. Arranging conferences or meetings has been especially difficult since the end of the COVID-19 lockdowns, but we (the RIPE community) are in this together along with the RIPE NCC. The RIPE community is willing to help when it makes sense, and can be trusted to be understanding otherwise. Hisham from the RIPE NCC grabbed for a quick chat some time after the RIPE NCC services working group session. He was very open about the challenges that the RIPE NCC are facing planing RIPE meetings, as well as a lot of the thought processes they have around selecting cities, picking venues, and so on. The meetings have not been dropped or ignored, and I know that the RIPE NCC is going to be giving us some interesting articles meeting organization in the near future. I really appreciate him reaching out to me, and look forward to everyone learning about the efforts around meeting planning. Anyway, that's it. No secret agenda or hidden meanings, I promise! 😄 Cheers, -- Shane

7 7

Re: [ncc-services-wg] New article on RIPE Labs: Redesigning ripe.net
by Phillip Oldham 27 Nov '23

27 Nov '23

Hello Aleksi Thanks for your feedback. I think I need to clarify a couple of things, which I should have made a little more clear in the article. Firstly, the article relates specifically to www.ripe.net, our public website. These changes won’t affect the functionality or design of our other websites such as the RIPE Database, stat.ripe.net, atlas.ripe.net, etc. This means that your workflow shouldn’t be affected if you’re using one of these tools. Secondly, in the article, “fully responsive design” refers to the practice of making a website’s layout change based on the size of the screen on which it is presented. Generally this practice doesn’t change the content on the page itself, instead it moves the content around to best fit the screen size and orientation. For example, a page displayed on a tablet device would use a slightly smaller font size and reduced image sizes compared to how the page would display on the larger screen of a laptop. The page’s HTML and contents would be the same in both cases, and the transition between layouts doesn't require the page to reload. This also shouldn’t affect your workflow, and the changes we’re making in this respect will be limited to the www.ripe.net website. I hope this answers your concerns. If not, please feel free to reach out and I can provide more detail. Best regards Phillip Oldham Manager, Web Services RIPE NCC On 21/11/2023 10:53, ncc-services-wg-request(a)ripe.net wrote: > Date: Tue, 21 Nov 2023 11:53:39 +0200 > From: Aleksi Suhonen <ripe-ml-2023(a)ssd.axu.tm> > To: ncc-services-wg(a)ripe.net > Subject: Re: [ncc-services-wg] New article on RIPE Labs: Redesigning > ripe.net > Message-ID: <4ea8f573-85e8-4566-b7e2-002e7528e38f(a)ssd.axu.tm> > Content-Type: text/plain; charset=UTF-8; format=flowed > > Hello, > > On 10/11/2023 16:37, Phillip Oldham wrote: >> Following up on plans laid out back in our Activity Plan and Budget >> 2023, over the past year we've been working towards improving >> ripe.net. In this new article on RIPE Labs, I give an overview of the >> changes we have in mind and a sneak preview of the new design: > The previous iteration (or two?) have been plagued by things that look > like links, but are not in fact links, so you can't open them in another > tab. I hope this design pattern will be discontinued. > > When working with a smallish number of RIPE objects, I like to open them > all into separate tabs first. Then I go through the tabs and check each > object for the changes required, if any, and then close them as they > have been dealt with. Once I run out of tabs, I know I've covered > everything, and I can sleep soundly. > > The RIPE labs article talks about "fully responsive design" which to me > sounds like I would need to responsively make a new search for objects > after each object I've handled. This is a nightmare, as I'd > inevitably/accidentally end up checking some objects several times, and > at the end of the day I still couldn't be sure that I've done everything > I set out to do. > > My 2 cents, >

1 0

Candidates for NCC Services WG Co-chair
by Rob Evans 24 Nov '23

24 Nov '23

Dear colleagues, The nomination period for co-chair of the NCC Services Working Group closed yesterday, and we are happy to say we have two candidates: - Stefan Wahl - Janos Zsako Between now and our meeting in Rome, we'd like to invite the candidates to say why they would like to co-chair the working group, and we'd ask participants in the WG to express support for one or other candidate. Cheers, Rob & Bijal

6 5

RIPE Labs article on maintaining a strong organisation through 2024
by Hans Petter Holen 23 Nov '23

23 Nov '23

Dear all, Today I published the final RIPE Labs article in a series focused on the RIPE NCC’s Draft Activity Plan and Budget 2024: https://labs.ripe.net/author/hans_petter_holen/strong-and-stable-in-2024-th… In this last instalment, I focus on how we will maintain a strong and stable organisation through the work of the Organisational Sustainability area of the RIPE NCC as well as a final word on the draft activity plan. If you have feedback on the draft document please let me know on the members-discuss mailing list or in person next week at RIPE 87. Kind regards, Hans Petter Holen Managing Director and Chief Executive Officer RIPE NCC

1 0

New article on RIPE Labs: Redesigning ripe.net
by Phillip Oldham 21 Nov '23

21 Nov '23

Dear colleagues, Following up on plans laid out back in our Activity Plan and Budget 2023, over the past year we've been working towards improving ripe.net. In this new article on RIPE Labs, I give an overview of the changes we have in mind and a sneak preview of the new design: https://labs.ripe.net/author/phillip-oldham/page-under-construction-redesig… Phillip Oldham (he/him) <poldham(a)ripe.net> Manager, Web Services RIPE NCC Stationsplein 11, 1012 AB Amsterdam

2 1

Decommissioning Recognised IPv4 Transfer Brokers List and IPv4 Transfer Listing Service
by James Kennedy 20 Nov '23

20 Nov '23

Dear colleagues, At its meeting on 6 October 2023, the RIPE NCC Executive Board resolved to decommission the Recognised IPv4 Transfer Brokers List and the IPv4 Transfer Listing Service [1]. Following from this, we are currently in the process of removing the brokers list and informing all of the brokers that we have signed a ‘Recognised IPv4 Broker Agreement’ with. The Recognised IPv4 Transfer Brokers List will be removed from our website on 31 December 2023. We also plan to start decommissioning the IPv4 Transfer Listing Service after RIPE 87 and expect this to be completed in Q1 2024. As noted in the Executive Board meeting minutes, the brokers list is no longer fulfilling its intended purpose. At the same time, the IPv4 Transfer Listing Service has reached the end of its life and requires significant development work, which we do not have the resources for. The Board therefore decided to retire both services. Ending these services makes us wonder what role, if any, the RIPE NCC should play in the IPv4 transfer market going forward. I will briefly discuss this in my update at the RIPE NCC Services Working Group during RIPE 87 next week. We plan to start a consultation in early 2024 to ask members and the community what they would like to see from us here. Regards, James Kennedy Chief Registry Officer RIPE NCC [1] 168th Executive Board Meeting Minutes: https://www.ripe.net/about-us/executive-board/minutes/2023/minutes-168th-ex…

1 0

NCC Services WG Draft Agenda - RIPE87
by Bijal Sanghani 13 Nov '23

13 Nov '23

Dear colleague, Please see below and shortly online the draft agenda for the NCC Services WG session at RIPE87: Date: Wednesday 29 November 2023 Time: 14.00 - 15.30 Chair: Kurtis Lindqvist Co-Chair: Rob Evans, Bijal Sanghani A. Administrative Matters (5 minutes) Welcome Select a scribe Finalise agenda Approve minutes from RIPE 86 B. RIPE NCC Update - Hans Petter Holen, RIPE NCC (30 minutes) C. Registry Update - James Kennedy RIPE NCC (15 minutes) D. RIPE NCC Survey 2023 - Brenda Mainland, Survey Matters and Fergal Cunningham, RIPE NCC (20 mins) E. RIPE NCC Website Redesign - Phillip Oldham, RIPE NCC (10 minutes) F. RIPE NCC Services Chair Selection - RIPE NCC Service WG Chairs (5 minutes) Z. AOB - RIPE NCC Service WG Chairs (5 minutes) We'd like to take this opportunity to remind you that nominations to be co-chair of NCC Services close this Wednesday, 15th November. If you're interested, please contact Rob or myself. We look forward to seeing you at RIPE87! Best regards, RIPE NCC Services WG Chairs

1 0

Update of RIPE NCC Procedural Document : Closure Procedure
by Kevin Brennan 06 Nov '23

06 Nov '23

Dear colleagues, The RIPE NCC Procedural document 'Closure of Members, Deregistration of Internet Resources and Legacy Resources' has been reviewed and updated. The following is an overview of the amendment made. Section A.1.2.2. (e) Termination with Immediate Effect was amended through deletion of the wording which required official postal notification, alongside the official notification by email, for termination of the RIPE NCC Standard Service Agreement (SSA) in the case of non-payment of the annual contribution (service fee) after a period of 120 days from the date of invoice. The main reason for this change is that the final notification of termination of the SSA by post is superfluous in the case of termination of the SSA due to non-payment as the member has already received numerous periodic notifications over the course of 120 days and the cause for termination in these instances cannot, in any event, be refuted. Further, termination due to non-payment is the most frequent cause for termination of the SSA and therefore removing the postal notification requirement will reduce the RIPE NCC's administrative burden and associated costs. Thus, in future cases whereby a member’s SSA is terminated due to non-payment the member will receive official notification by email only to their registered contacts. You can find the updated documents at: https://www.ripe.net/publications/docs/ripe-808 Kind regards, Kevin Brennan Legal Counsel RIPE NCC

1 0