- members-discuss - mailman.ripe.net

Moderation of the Members Discuss Mailing List
by Christian Kaufmann 08 Mar '22

08 Mar '22

Dear members, The RIPE NCC Executive Board resolved to temporarily moderate the members-discuss mailing list starting from Saturday, 5 March 2022, 23:00 UTC+1 and until further notice. The mailing list will be moderated in accordance with the purpose of the mailing list and the principles of the RIPE Code of Conduct by a designated member of the RIPE NCC Executive Board and a RIPE NCC staff member. All emails, accepted or rejected, will be archived on the RIPE NCC website. The archive of all mails sent is available at: https://www.ripe.net/ripe/mail/archives/members-discuss-unmoderated/ Kind regards, Christian Kaufmann Chairman of the RIPE NCC Executive Board

1 0

Re: [members-discuss] [ENOG discuss] Hа: Re: A request to terminate ENOG
by Dmitry Kohmanyuk 05 Mar '22

05 Mar '22

Ms.Nadezhda Kupina, > On 2022-03-04, at 15:52, Nadezhda O. Kupina <NOKupina(a)akado-telecom.ru> wrote: > > Добрый день! > Мы, как операторы связи, должны быть аполитичны! > Не надо смешивать политику и оказание услуг связи пользователям. > Today, world wide telecommunications leader Cogent has complety canceled, terminated, dissolved, and disconnected all circuits, links, and operator premises equipment serving their customers in Russian Federation. There was less than 2 days notice of the fact. The law of its jurisdiction, United States, did not compel it to this drastic action, as no sanctions has been levied against telecom operators in Russia yet (ok, perhaps couple of State Duma parliamentary members owns an ISP - although I highly doubt that.) During the undeclared war, Ukrainian National railway operator, Ukrzaliznytsya, has terminated all interconnect points with RZhD, Russian railways. They did so to inhibit a flow of weapons and military, and carry neither insignia nor flags. I would like to remind our community of our meeting in Minsk. Would you go there now? There are missiles shot, southward from it. The purpose of ENOG was the same of my favorite company, Nokia, whose slogan was “connecting people.” We cannot do it until the bloodshed stops, the criminal regime of Russia goes to trial in The Hague, and the complicit in war crime population of Russia goes through the process of deputinization. [1] I am using this opportunity to resign from ENOG PC. I can be last member that went to most meetings, and was still hoping for good. Until now. I have ENOG logos on my credit cards. The RIPE community can definitely decide to resurrect the ENOG, perhaps in this way: to join some countries with SEE, and some with MENOG. I would not join until this war ends. [1] https://en.wikipedia.org/wiki/Denazification

3 2

RIPE NCC Planning Q1 2022
by Fergal Cunningham 11 Jan '22

11 Jan '22

Dear members, We have now published our Q1 2022 plans for our development teams. These are available 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, the RIPE Database and our Business Applications, including the LIR Portal, registry services and other applications. We also include for the first time the plans from our Learning and Development Team for our e-learning courses, webinars and Certified Professionals exams. If you have any input on our plans or want to let us know what you would like to see the RIPE NCC work on, please let us know. We will add your feedback to the pages and our teams will consider it for future plans. Kind regards, Fergal Cunningham Head of Membership Engagement RIPE NCC

1 0

Request for view only access in the LIR Portal
by Theodoros Polychniatis 08 Dec '21

08 Dec '21

Dear members, We received this request on the NCC Services WG list: https://www.ripe.net/ripe/mail/archives/ncc-services-wg/2021-November/00350… We would be interested to hear if this is something other members would like to see or if there are other aspects of LIR Portal access privileges they would like to see us consider. We'll keep an eye on feedback here and on the NCC Services WG list. Best regards, Theo -- Theodoros Polychniatis Asst. Manager Software Engineering RIPE NCC

4 4

Your opinion about Temporary Assignment request
by Sergei Volgapkin 27 Oct '21

27 Oct '21

Dear members, May you find the time to tell your opinion about situation with "Temporary Internet Number Assignment Policies" (https://www.ripe.net/publications/docs/ripe-587). We've found that RIPE Team can reply you in this manner "/at this moment we have not received //*sufficient evidence*//in order to see that the request for a temporary assignment is justified/"/./ If you ask about examples of "sufficient evidence" you may get the answer like this "/I am afraid that we are not able to give any examples. Temporary assignments are provided on a case-by-case basis and there is not a 'standard template' for this./" It means that RIPE able selectively accept requests for the temporary assignments and not every LIR has the same capabilities. I think that this service should have just standard request form. I'm appreciate for your time and answers. Regards -- Sergei

3 3

Re: [members-discuss] [ncc-announce] [GM] Draft RIPE NCC Activity Plan and Budget 2022
by Hank Nussbacher 27 Oct '21

27 Oct '21

On 26/10/2021 16:52, Hans Petter Holen wrote: I would like to see 1MEuro allocated for the distribution of physical RIPE probes. I do not think RIPE should be "requesting donations" for this (see: https://atlas.ripe.net/get-involved/become-a-sponsor/ ) but rather our membership fees should be used to handle RIPE probe distribution. The 1MEuro can be taken from the 8Meuro allocated to section 3: 3.1 Community Building and Member Engagement (5MEuro) 3.2 Community Learning and Development (2.6MEuro) 3.3 Community Coordination and Collaboration (1.4MEuro) Regards, Hank > Dear members, > > The Draft RIPE NCC Activity Plan and Budget 2022 is now available as a > PDF for your review at: > https://www.ripe.net/draft-activity-plan-budget-2022 > > This is the clearest way that you can learn about our plans for next > year and shape the direction we take as an organisation. We ask that you > read it and share any feedback on <members-discuss(a)ripe.net>. > > For the first time, accompanying this year’s Activity Plan is a separate > strategy document that looks ahead to the next five years. You will find > this in a separate announcement. > > Members can now comment on these draft documents, after which they will > be discussed at the General Meeting (GM) alongside RIPE 83 on Wednesday, > 24 November 2021. The Executive Board will consider all feedback on our > activities and strategy before publishing the final versions in December > 2021. > > Please note that if you want to participate or vote in the GM, you will > need to register via the General Meeting section in my.ripe.net. You can > find more information about the GM, including the draft agenda, at: > https://www.ripe.net/participate/meetings/gm/meetings/nov-2021 > > Kind regards > > Hans Petter Holen > Managing Director > RIPE NCC >

1 0

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

30 Sep '21

Dear members, 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

Re: [members-discuss] Registry Services Ticket Response Time
by Elvis Daniel Velea 23 Sep '21

23 Sep '21

Dear Felipe, while we wait for you to crop up a roadmap, I am still waiting for the statistics I asked from Marco weeks ago. Marco, I’d like to see real numbers and not just .. this Q we handled x% more tickets than last Q. Usually when statistics are presented this way, without backing numbers, they express a story you want us to see and not the whole picture. So, while Felipe works on the roadmap, please send us the statistics that you already have about number of tickets handled daily, number of FTEs working on those tickets daily and make sure we receive these numbers for at least since you stopped showing this information transparently (circa 2015). I hope you can provide these numbers swiftly and it won’t take weeks to provide them but rather days (you’ve been working on these stats/numbers since my initial e-mail requesting them, right?) Also, you avoid to respond to one very important question: how many working days in this year have you respected the agreed SLA and how many working days you failed to respect it. I am sure you already have this number and can provide it _today_. Elvis PS: I have yet to see a ticket handled within the SLA for months, still hope this will change swiftly and not months/quarters from now On Tue, Sep 7, 2021 at 08:11 Felipe Victolla Silveira <fvictolla(a)ripe.net> wrote: > Dear Gert, Elvis, > > First, let me recognise that the ticketing system has been a sore point > for a number of years and we have made little progress in addressing the > issues that you and others have raised. We are not overly proud of our > record here. > > In the next few weeks, we plan to publish roadmaps with our plans for the > next quarter[1]. We will make sure the ticketing system is covered here. > > Given there are other areas which may need priority, I can't promise that > you will be completely satisfied by what we propose in terms of the > ticketing system. However, having public roadmaps should help to inform > discussions about what we focus on and where trade-offs need to be made. > Publishing more detail about our plans and tracking feedback or changes > should also make it easier to hold us to account when we fail to deliver. > > So, if you can bear with us a little longer, once this is ready we can > continue the discussion on this list, using these roadmaps as a starting > point. > > Kind regards, > Felipe > > [1] Using our recent RPKI roadmap as a model: > > https://www.ripe.net/manage-ips-and-asns/resource-management/rpki/rpki-plan… > > On 6 Sep 2021, at 18:07, Gert Doering <gert(a)space.net> wrote: > > Hi, > > On Mon, Aug 30, 2021 at 09:06:54PM -0700, Elvis Daniel Velea wrote: > > PS: Note that I wanted to also send an e-mail about the RIPE NCC's > ticketing system (zendesk) to the members-discuss mailing list and to > the board members. I will wait for an answer to the e-mail I sent to HPH > one week ago (which he promised he'll forward to the relevant team for a > reply). > > > The ticket system from hell. > > I'm looking forward to read the issues *you* have with it. > > My complaints have been delivered to Felipe in person, years ago, and > been summarily ignored. As far as I can see. > > But that might be better suited in its own thread, and in ncc-services. > > Gert Doering > -- NetMaster > -- > have you enabled IPv6 on something today...? > > SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael > Emmer > Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann > D-80807 Muenchen HRB: 136055 (AG Muenchen) > Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279 > > _______________________________________________ > members-discuss mailing list > members-discuss(a)ripe.net > https://lists.ripe.net/mailman/listinfo/members-discuss > Unsubscribe: > https://lists.ripe.net/mailman/options/members-discuss/rsstaff%40ripe.net > > > -- This message was sent from a mobile device. Some typos may be possible.

4 10

Re: [members-discuss] Registry Services Ticket Response Time
by rk＠indyntech.com 14 Sep '21

14 Sep '21

Dear Marco, Our company is a new member, but we also faced all these ticket processing issues. During August our requests were processed within the usual 2-3 business days, but then something incomprehensible happened. I'm glad that the other members are also worried, but it seems strange to me that, the RIPE NCC management has not taken any adequate measures over the past months, and that it does not process members' requests in chronological order, for example, as we see in the previous message: > See ticket #398137, for example. Ticket opened Aug 26 at 4AM, <...> resolved only next Monday? And we sent the documents to our ticket #396762 on Aug 25 and it's still in processing for these 2 weeks without ANY response since Aug 27. I have also tried to check the status over the phone and all the staff was reported to be so busy to reply. How come that the old good 1 day SLA has been discontinued and the RIPE NCC can now simply ignore their members for weeks? Why ticket #398137 that was submitted by Elvis later was processed earlier and our ticket is still stored with an unknown status? What is the current SLA and who is responsible for it? If the management does not cope with this task why is the executive board not notified of this problem and the issue is not widely discussed with the community? Kind regards, Roman Kalinin

4 4

Ticketing System / Roadmaps
by Felipe Victolla Silveira 07 Sep '21

07 Sep '21

Dear Gert, Elvis, First, let me recognise that the ticketing system has been a sore point for a number of years and we have made little progress in addressing the issues that you and others have raised. We are not overly proud of our record here. In the next few weeks, we plan to publish roadmaps with our plans for the next quarter[1]. We will make sure the ticketing system is covered here. Given there are other areas which may need priority, I can't promise that you will be completely satisfied by what we propose in terms of the ticketing system. However, having public roadmaps should help to inform discussions about what we focus on and where trade-offs need to be made. Publishing more detail about our plans and tracking feedback or changes should also make it easier to hold us to account when we fail to deliver. So, if you can bear with us a little longer, once this is ready we can continue the discussion on this list, using these roadmaps as a starting point. Kind regards, Felipe Victolla Silveira Chief Operations Officer RIPE NCC [1] Using our recent RPKI roadmap as a model: https://www.ripe.net/manage-ips-and-asns/resource-management/rpki/rpki-plan…

1 0