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

Re: [ncc-services-wg] Policy Document URLs
by Sander Steffann 12 Nov '21

12 Nov '21

Hi Angela, > On www.ripe.net, the tab "Publications" leads to the RIPE Document store (https://www.ripe.net/publications/docs) > > There, under "RIPE Documents by Category" you can find a link to all RIPE current documents (https://www.ripe.net/publications/docs/ripe-documents) > and the links to different groups of documents. You’re describing the path of where to click to reach the documents. What was requested were stable URLs to link to specific documents. We don’t want to tell people how to navigate the RIPE website. We want to link to a document :) Cheers Sander

3 4

Co-chair volunteers
by Rob Evans 10 Nov '21

10 Nov '21

Dear colleagues, > Wed 10 Nov List of volunteers and call for support posted to the mail list > Tue 23 Nov Deadline for showing support for volunteers on the mail list > Wed 24 Nov NCC Services WG session at RIPE 83 The nomination period for co-chairs of the NCC Services working group has closed and we have just one volunteer, Bijal Sanghani. Please voice support (or otherwise) on this list by the end of Tuesday 23rd November. The co-chairs have noted that there have been no other volunteers either last year or this year, even though it wasn't clear whether the incumbent chairs were going to re-stand. We'll have a think about the best way to proceed for the next time a co-chair is due to stand-down. Cheers, Kurtis and Rob

2 1

Draft RIPE NCC Strategy 2022-2026
by Hans Petter Holen 03 Nov '21

03 Nov '21

Dear colleagues, Today we published our Draft RIPE NCC Strategy 2022-2026. You can see the announcement I made to the membership at: https://www.ripe.net/ripe/mail/archives/ncc-announce/2021-October/001524.ht… We are also keen to get input from the RIPE community on our strategy, and I invite you to provide your feedback on this mailing list or on the Membership Discussion mailing list if you are subscribed there <members-discuss(a)ripe.net>. Kind regards, Hans Petter Holen Managing Director RIPE NCC

3 2

Call for volunteers to co-chair the RIPE NCC Services Working Group
by Rob Evans 26 Oct '21

26 Oct '21

Dear Colleagues, This is a call for nominations or volunteers to co-chair the RIPE NCC Services working group. ********************* Please DO NOT reply to this message if you wish to volunteer or propose a volunteer. ********************* Call for RIPE NCC Services Working Group Chair ---------------------------------------------- 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 9th November 2021. 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 10th November 2021. Discussion and support (or opposition) for each candidate can then be offered on the list. At the NCC Services working group session at RIPE 83, Kurtis and Rob hope to announce consensus based on the mailing list discussion. Timeline -------- Tue 26 Oct This call for volunteers posted to the ncc-services-wg mail list Tue 9 Nov Deadline for volunteers Wed 10 Nov List of volunteers and call for support posted to the mail list Tue 23 Nov Deadline for showing support for volunteers on the mail list Wed 24 Nov NCC Services WG session at RIPE 83 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… 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. [With thanks to Dave Knight for the text this was cribbed from.]

1 0

RIPE 83 call for Agenda Items - NCC Services WG
by Bijal Sanghani 26 Oct '21

26 Oct '21

Dear NCC-Services WG, RIPE83 is fast approaching and we have a few spaces free on the agenda. If you would like to suggest a topic for discussion or have a presentation you have or would like to see presented please get in touch with the working group chairs at ncc-services-wg-chairs(a)ripe.net <mailto:ncc-services-wg-chairs@ripe.net>. Remember, this is your opportunity to let the RIPE NCC know what you want from them :) Best regards, RIPE NCC Services WG Chairs

1 0

Policy Document URLs
by Cynthia Revström 22 Oct '21

22 Oct '21

(I am sorry if this is the wrong list for this topic, please direct me to the appropriate list if so) Hi, I was just sending someone a link to the current IPv6 policy and I remembered how often those links get outdated when placed in random wikis or FAQs for more info. This made me wonder if there could be (or already is) some kind of shortcut URLs for common documents[1] like these that would always point to the current version. Such as " https://www.ripe.net/publications/s/ipv6-allocation-and-assignment-policy" or "https://www.ripe.net/publications/s/ipv6-policy" or something like that. [1]: by "common documents" I mean docs like the assignment/allocation policies, the NCC articles of association, things related to code of conduct etc. basically things which are likely to be referenced quite often -Cynthia

3 2

Help us Build a Sustainable European Cloud
by Michael J. Oghia 04 Oct '21

04 Oct '21

Hi everyone, My name is Michael Oghia. I'm a long-time RIPE community member, and currently the Director of Communications & External Relations at the Sustainable Digital Infrastructure Alliance (SDIA <https://sdialliance.org>) – a non-profit network of more than 65 organisations working to catalyse the transition to a sustainable digital economy. Mirjam recently encouraged me to join this WG given the recent discussion about the NCC's (now paused) cloud plans. She mentioned that the topic of a good European alternative came up in the discussion, which is why I'm eager to share my latest RIPE Labs post with you all since it's relevant. Over the summer, SDIA published a three-part series introducing our manifesto for a sustainable European cloud, one that’s open-source, fair, and creates economic opportunities for all. Such digital infrastructure will reflect European values, and provide a blueprint that others around the world can draw inspiration from to further develop their own digital economies. The post, published today, provides a summary of each part, an invitation to read them, and a call to action to help us make our vision a reality. You can read it at: https://labs.ripe.net/author/michael_oghia/help-us-build-a-sustainable-euro… In case anyone would like to discuss further, please don't hesitate to reach out. Best, -Michael __________________ Director of Communications & External Relations Sustainable Digital Infrastructure Alliance (SDIA <https://sdialliance.org/> ) ICT sustainability advocate | IRPC <https://internetrightsandprinciples.org/> Steering Committee member Belgrade, Serbia (UTC+2) | Twitter <https://www.twitter.com/MikeOghia> | LinkedIn <https://www.linkedin.com/in/mikeoghia> <https://www.linkedin.com/in/mikeoghia>

3 4

RIPE NCC Planning Q4 2021
by Felipe Victolla Silveira 30 Sep '21

30 Sep '21

Dear colleagues, We are now publishing the quarterly planning for all our development teams. These are available at: https://www.ripe.net/support/documentation/quarterly-planning <https://www.ripe.net/support/documentation/quarterly-planning> 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. Last quarter, we published our plans for RPKI and this was shared with the Routing Working Group. Today we publish our planning for the RIPE Database and our Business Applications, which includes work we will carry out with the LIR Portal, registry services and other applications the RIPE NCC provides for its members and community. We will provide status updates as the work progresses and add input from the community to the pages. We will also archive previous plans so you can track how we progress with our work. If you have comments or questions about our planning, I hope you'll let us know. Kind regards, Felipe Victolla Silveira Chief Operations Officer RIPE NCC

1 0

RIPE NCC transparency and response SLA
by noc＠netispro.com 24 Sep '21

24 Sep '21

Hi All, I remember that such issues were repeatedly discussed at the RIPE meetings, but I would still like to raise the question of the transparency of the RIPE NCC procedures and response SLA for the (future) members' requests. Our company is already an active RIPE NCC member and on August 18 we decided to open an additional LIR account in order to get an allocation for our operations through the waiting list. The application was processed as usual until we paid the invoice and returned our signed agreement (August 20). After that the whole request got out of control and over the last 10 days we've received only standard replies that the Registry Services team experiences "heavy workload" and our application is postponed again and again without any additional request or explanation. Thus, despite the stated aim of "providing a response within one working day", our request remains in processing for a significant time and the RIPE NCC refuses to even provide any details on the reasons or the exact processing time. It's also very funny that some replies from the RIPE NCC refer to the additional Due Diligence checks that are required for our application, but since we are incorporated in a country with a public transparent corporate register, are not subject to any EU sanctions and already hold a RIPE NCC membership that was duly checked before the activation, it just looks like an unconvincing excuse that only misleads us. I have discussed this issue with other members and many of them told me that they have encountered similar problems when submitting various kinds of requests (allocation, assignment, transfers) in the past. It looks like the RIPE NCC can simply stockpile inconvenient, complex or any other requests without any valid reason and for any period of time. Thus, I kindly ask the RIPE NCC to comment on this issue and answer a couple of questions: 1. Why some of the requests are delayed due to the "heavy workload" excuse while the requests submitted later are timely processed? 2. Why we (as an applicant) aren't able to get any information on our request status and exact processing time for weeks? 3. Are similar cases actually reflected in the internal ticket statistics and what measures are taken by the management to solve this problem? Kind regards, Elina

3 7

Re: [ncc-services-wg] [ncc-announce] [news] Using Third Parties to Automate Our Due Diligence
by Nick Hilliard 17 Sep '21

17 Sep '21

Felipe Victolla Silveira wrote on 16/09/2021 13:14: > We will be working with iDenfy, a specialised provider in automated > ID validation and remote identification services, to ensure a high > standard of diligence and security across all ID documents that we > process. Once this is ready, members will upload personal > identification documents directly to the iDenfy system using a secure > link that we send. In addition to maintaining a high level of > security, iDenfy will ensure that this data is deleted within 14 days > of being submitted. In line with GDPR, we remain the ‘data > controller’. Work is currently underway to integrate our external > request processes with iDenfy’s systems and we plan for this to go > live on 23 September. Hi Felipe, https://www.idenfy.com/identity-verification-service/ can you confirm that there will be an option to decline automated biometric analysis, specifically including facial / feature analysis? Nick

2 1