February 2021 - ripe-list - mailman.ripe.net

Reminder: Call for Public Comments on the 2020 IANA Performance Matrix Summary Report
by Antony Gollan 25 Feb '21

25 Feb '21

This message is sent on behalf of the Number Resource Organization (NRO). *** Reminder: Call for Public Comments on the 2020 IANA Performance Matrix Summary Report Dear colleagues, This is a reminder that the IANA Review Committee (IANA RC) has launched a public comment period of 30 days, seeking comments and input from the community on the IANA Numbering Services performance and the 2020 IANA Performance Matrix Summary Report: https://www.nro.net/2020-RIR-IANA-summary-report Some background: As a result of the successful IANA Stewardship transition in 2016, the IANA Numbering Services are now being managed through an SLA between ICANN and the five Regional Internet Registries (RIRs). As part of the result of the IANA Stewardship transition, the IANA RC was established in 2016. The IANA RC is composed of representatives from each RIR region and advises and assists the RIRs in the review of the IANA Numbering Services. The IANA services are today provided by Public Technical Identifiers (PTI), which publishes monthly performance reports on the IANA Numbering Services: https://www.iana.org/performance/numbers Based on these monthly performance reports, the five RIRs have produced the 2020 IANA Performance Matrix Summary Report: https://www.nro.net/2020-RIR-IANA-summary-report The IANA RC encourages all members of the Internet number community to review the public IANA Performance Matrix Summary Report. Comments on the IANA service performance should be sent to: iana-performance [at] nro [dot] net. The IANA RC will publish an annual report in March 2021, as advice to the NRO EC with its evaluation of the IANA Numbering services. The report will be based on the IANA Performance Matrix Summary Report, as well as any input gathered on the performance from the global number community. The public comment period ends on Friday, 5 March 2021 at 23:59 UTC. All public comments will be published on the NRO Website in the dedicated IANA RC section (https://www.nro.net/iana-rc-reports), and will be considered as input to the final report by IANA. At the end of the 30-day public comment period, the IANA RC will meet and evaluate all input to the final report. The final IANA RC 2020 Report will be published at: https://www.nro.net/iana-rc-reports Kind regards, Bertrand Cherrier Chair, IANA Numbering Services Review Committee *** Regards Antony Gollan Senior Communications Officer RIPE NCC

1 0

Re: [ripe-list] [anti-abuse-wg] RIPE AA-WG discussion
by Cynthia Revström 23 Feb '21

23 Feb '21

It is possible but I highly doubt it. > We at Abusix run Abuse Desk for dozens of Service Providers of any size and any type of product. From Cloud to DC-Services, Cable, and so on. That sounds so much like marketing and irrelevant if it wasn't. Also if it wasn't marketing, why would he ask for me to schedule a video call? Once again I could be wrong, and if I am, I am sorry, but I can't see how this isn't marketing. -Cynthia On Mon, Feb 22, 2021 at 6:18 PM Volker Greimann <vgreimann(a)key-systems.net> wrote: > I think you totally misread his mail. It reads to me as a proposal to help > you understand the processes used by many providers, not as a sales pitch. > > Best, > -- > Volker A. Greimann > General Counsel and Policy Manager > *KEY-SYSTEMS GMBH* > > T: +49 6894 9396901 > M: +49 6894 9396851 > F: +49 6894 9396851 > W: www.key-systems.net > > Key-Systems GmbH is a company registered at the local court of > Saarbruecken, Germany with the registration no. HR B 18835 > CEO: Oliver Fries and Robert Birkner > > Part of the CentralNic Group PLC (LON: CNIC) a company registered in > England and Wales with company number 8576358. > > This email and any files transmitted are confidential and intended only > for the person(s) directly addressed. If you are not the intended > recipient, any use, copying, transmission, distribution, or other forms of > dissemination is strictly prohibited. If you have received this email in > error, please notify the sender immediately and permanently delete this > email with any files that may be attached. > > > On Mon, Feb 22, 2021 at 6:12 PM Cynthia Revström via anti-abuse-wg < > anti-abuse-wg(a)ripe.net> wrote: > >> Hi, >> >> (intro) >> Tobias Knecht sent me an email (which this is a reply to) abusing his >> position as co-chair in order to try to sell me services based on what I >> said on a mailing list. >> >> (mainly towards Tobias) >> Replying to me based on a mailing list post in order to try to sell me >> services is bad enough. >> To do it as a co-chair and then to use the fact that you are co-chair as >> a selling point is much worse. >> >> I find this utterly appalling behaviour from a co-chair of a working >> group, I didn't reach out to you, you weren't even in the thread at all. >> >> also this: >> > As a Co-Chair I didn't want to jump into the mix on the mailing list, >> that's why I'm reaching out to you directly. >> >> I mean that is sort of the point of co-chairs generally speaking but yeah >> it is going to look bad if you are trying to sell something, because it is >> bad. >> >> (mainly towards chair team and aa-wg chairs) >> A co-chair of a working group should absolutely be warned or removed if >> they abuse their position to sell their services. >> >> I also somehow doubt that this is the first time, I could be wrong, but >> idk why this would be the first time. >> >> I hate it when for example Cogent sends me emails trying to sell me >> services despite me never having contacted them (outside of replying saying >> I am not interested). >> But this is more like if the Cogent sales people were co-chairs of the >> db-wg. >> >> Also with a subject like "RIPE AA-WG discussion" I initially thought it >> was actually about something I said or whatever, in his role as co-chair, >> it didn't appear like it was a sales email. >> >> I have also CC'd the aa-wg and ripe list as this is too appalling to be >> held private. >> >> -Cynthia >> >> >> On Mon, Feb 22, 2021 at 5:50 PM Tobias Knecht <tk(a)abusix.com> wrote: >> >>> Hello Cynthia, >>> >>> my name is Tobias. I'm a Co-Chair of the Anti-Abuse Working Group and >>> also Founder and CEO of Abusix. >>> >>> >>> As a Co-Chair I didn't want to jump into the mix on the mailing list, >>> that's why I'm reaching out to you directly. >>> >>> We at Abusix run Abuse Desk for dozens of Service Providers of any size >>> and any type of product. From Cloud to DC-Services, Cable, and so on. >>> >>> Happy to jump on a call and answer the questions you have and tell you >>> about how our clients handle those things. >>> >>> Feel free to reach out via email or just pick a time in my calendar: >>> https://calendly.com/tobias-knecht/30min >>> >>> Thanks and stay safe. >>> >>> Tobias >>> >>> -- >>> >>> >>> Tobias Knecht >>> >>> Founder & CEO >>> >>> >>> >>> T. >>> >>> +49 170 455 98 45 >>> >>> abusix.com >>> <https://cloud.letsignit.com/collect/bc/5fc946660b5c6b0008d672f1?p=3QW9LKZRN…> >>> >>> Book a meeting >>> <https://cloud.letsignit.com/collect/bc/5fc946660b5c6b0008d672f1?p=3QW9LKZRN…> >>> >>> >>> >>> [image: My Logo] >>> >>> >>> >>> >>> <https://cloud.letsignit.com/collect/bc/5fc946660b5c6b0008d672f1?p=3QW9LKZRN…> >>> >>> >>> <https://cloud.letsignit.com/collect/bc/5fc946660b5c6b0008d672f1?p=3QW9LKZRN…> >>> >>> >>> <https://cloud.letsignit.com/collect/bc/5fc946660b5c6b0008d672f1?p=3QW9LKZRN…> >>> >>> >>> >>> >>> >>> CONFIDENTIALITY This email and any attachments are confidential and may >>> also be privileged or otherwise protected from disclosure. If you are not >>> the named recipient, please notify the sender immediately and do not >>> disclose the contents to another person, use it for any purpose, or store >>> or copy the information in any medium. >>> >>> >>

3 3

Re: [ripe-list] RIPE AA-WG discussion
by Cynthia Revström 22 Feb '21

22 Feb '21

Hi, (intro) Tobias Knecht sent me an email (which this is a reply to) abusing his position as co-chair in order to try to sell me services based on what I said on a mailing list. (mainly towards Tobias) Replying to me based on a mailing list post in order to try to sell me services is bad enough. To do it as a co-chair and then to use the fact that you are co-chair as a selling point is much worse. I find this utterly appalling behaviour from a co-chair of a working group, I didn't reach out to you, you weren't even in the thread at all. also this: > As a Co-Chair I didn't want to jump into the mix on the mailing list, that's why I'm reaching out to you directly. I mean that is sort of the point of co-chairs generally speaking but yeah it is going to look bad if you are trying to sell something, because it is bad. (mainly towards chair team and aa-wg chairs) A co-chair of a working group should absolutely be warned or removed if they abuse their position to sell their services. I also somehow doubt that this is the first time, I could be wrong, but idk why this would be the first time. I hate it when for example Cogent sends me emails trying to sell me services despite me never having contacted them (outside of replying saying I am not interested). But this is more like if the Cogent sales people were co-chairs of the db-wg. Also with a subject like "RIPE AA-WG discussion" I initially thought it was actually about something I said or whatever, in his role as co-chair, it didn't appear like it was a sales email. I have also CC'd the aa-wg and ripe list as this is too appalling to be held private. -Cynthia On Mon, Feb 22, 2021 at 5:50 PM Tobias Knecht <tk(a)abusix.com> wrote: > Hello Cynthia, > > my name is Tobias. I'm a Co-Chair of the Anti-Abuse Working Group and also > Founder and CEO of Abusix. > > > As a Co-Chair I didn't want to jump into the mix on the mailing list, > that's why I'm reaching out to you directly. > > We at Abusix run Abuse Desk for dozens of Service Providers of any size > and any type of product. From Cloud to DC-Services, Cable, and so on. > > Happy to jump on a call and answer the questions you have and tell you > about how our clients handle those things. > > Feel free to reach out via email or just pick a time in my calendar: > https://calendly.com/tobias-knecht/30min > > Thanks and stay safe. > > Tobias > > -- > > > Tobias Knecht > > Founder & CEO > > > > T. > > +49 170 455 98 45 > > abusix.com > <https://cloud.letsignit.com/collect/bc/5fc946660b5c6b0008d672f1?p=3QW9LKZRN…> > > Book a meeting > <https://cloud.letsignit.com/collect/bc/5fc946660b5c6b0008d672f1?p=3QW9LKZRN…> > > > > [image: My Logo] > > > > > <https://cloud.letsignit.com/collect/bc/5fc946660b5c6b0008d672f1?p=3QW9LKZRN…> > > > <https://cloud.letsignit.com/collect/bc/5fc946660b5c6b0008d672f1?p=3QW9LKZRN…> > > > <https://cloud.letsignit.com/collect/bc/5fc946660b5c6b0008d672f1?p=3QW9LKZRN…> > > > > > > CONFIDENTIALITY This email and any attachments are confidential and may > also be privileged or otherwise protected from disclosure. If you are not > the named recipient, please notify the sender immediately and do not > disclose the contents to another person, use it for any purpose, or store > or copy the information in any medium. > >

1 0

Attack on RIPE NCC Access - Please Enable Two-Factor Authentication
by RIPE NCC Security 19 Feb '21

19 Feb '21

Dear colleagues, Last weekend, RIPE NCC Access, our single sign-on (SSO) service was affected by what appears to be a deliberate ‘credential-stuffing’ attack, which caused some downtime. We mitigated the attack, and we are now taking steps to ensure that our services are better protected against such threats in the future. Our preliminary investigations do not indicate that any SSO accounts have been compromised. If we do find that an account has been affected in the course of our investigations, we will contact the account holder individually to inform them. We would like to ask you to enable two-factor authentication on your RIPE NCC Access account if you have not already done so to ensure that your account is secure. In general, using two-factor authentication across all your accounts can help limit your exposure to such attacks. We will keep you informed about any relevant developments. If you have noticed any suspicious activity in your RIPE NCC Access account, please contact us immediately at security(a)ripe.net. Best regards, Ivo Dijkhuis Senior Information Security Officer, RIPE NCC

3 3

Call for Presentations: RIPE 82
by Brian Nisbet 16 Feb '21

16 Feb '21

*RIPE 82 will be a free virtual event and will take place from 17-21 May 2021* The RIPE Programme Committee (PC) is now seeking content proposals from the RIPE community for the plenary sessions, lightning talks and BoFs. Please note that no workshops or tutorials will be organised at this meeting. The RIPE 82 Meeting plan is available here: https://ripe82.ripe.net/programme/meeting-plan/ You have until *19 March 2021* to submit your presentations proposals. Proposals submitted after this date will be considered depending on the slots still available in the programme. The PC is looking for presentations covering topics of network engineering and operations, including but not limited to: - IPv6 deployment - Managing IPv4 scarcity - Data centre technologies - Network and DNS operations - Internet governance and regulatory practices - Network and routing security - Content delivery - Internet peering and mobile data exchange - Connected Things (aka. Internet of Things - IoT) RIPE Meeting attendees are quite sensitive to keeping presentations non-commercial, and product marketing talks are strongly discouraged. Most successful talks focus on operational experience, research results, or case studies. For example, presenters wishing to describe a commercial solution should focus on the underlying technology and should not attempt a product demonstration. --------------------------------------------------------------------- Submissions --------------------------------------------------------------------- The following general requirements apply: - Proposals must be submitted using the meeting submission system, https://ripe82.ripe.net/submit-topic/submission-form/ - All presentation proposals will only be considered by the PC if they contain at least draft presentation slides (slides may be updated later on). For panels, proposals must contain a clear description, as well as the names of invited panelists, presenters and moderators. - Presenters should indicate how much time their presentations will require. Here’s an indication of the average duration of each session format: o Plenary presentations: 20-25 minutes presentation with 10-5 minutes discussion o Lightning talks: 10 minutes for both the presentation and discussion o BoFs: one hour - Lightning talks should also be submitted using the same meeting submission system and can be submitted any time up to and including the meeting week. The allocation of lightning talks will be announced the week before the RIPE Meeting. - Presenters who propose a BoF are encouraged to include speakers from several (perhaps even competing) companies and/or a neutral facilitator. More detail on the presentation formats can be found here: https://ripe82.ripe.net/submit-topic/presentation-formats/ --------------------------------------------------------------------- Plenary or Working Group? --------------------------------------------------------------------- Presenters should be clear on whether they wish to submit a presentation for a plenary or working group session. At present, most working groups will solicit policy proposals, discussion points or other content directly via their mailing lists. If you’re not sure what kind of session you should be presenting at, please visit: https://ripe82.ripe.net/submit-topic/plenary-or-wg/ --------------------------------------------------------------------- The RIPE Meeting Code of Conduct --------------------------------------------------------------------- To ensure that RIPE Meeting values are upheld and that attendees experience a professional, respectful and safe meeting is a priority, please read the RIPE Meeting Code of Conduct: https://www.ripe.net/participate/meetings/ripe-meetings/ripe-meeting-code-o… --------------------------------------------------------------------- If you have any questions or requests concerning content submissions, please email pc(a)ripe.net . Franziska, Brian & Jan On Behalf of the RIPE PC Brian Nisbet Service Operations Manager HEAnet CLG, Ireland's National Education and Research Network 1st Floor, 5 George's Dock, IFSC, Dublin D01 X8N7, Ireland +35316609040 brian.nisbet(a)heanet.ie www.heanet.ie Registered in Ireland, No. 275301. CRA No. 20036270

1 0

RIPE WG Chairs Selection and Terms
by Mirjam Kuehne 12 Feb '21

12 Feb '21

Dear colleagues, I think we all agree that the overall goal is to have a good and diverse set of WG chairs and we want to work with all WGs to facilitate that. Following the recommendations from the Accountability Task Force, we've started looking at the chair selection criteria of all RIPE Working Groups. Currently most WGs have terms or regular calls for nominations defined as part of their selection criteria. We will continue this review. Kind regards, Mirjam

8 11

DBTF Questionnaire – Deadline Extended to 22 February 2021
by Bijal Sanghani 12 Feb '21

12 Feb '21

Dear colleagues, We’ve received 20 replies so far to the RIPE Database Requirements Task Force (DBTF) questionnaire. Thank you for that and the discussion on the mailing list. As we would like more feedback on these questions, we’ve decided to extend the deadline to 22 February 2021. The questionnaire takes less than 10 minutes and really will give us valuable feedback to consider for our final draft. You can take the questionnaire here: https://www.surveymonkey.com/r/ZM222M3 Thank you for your participation and support. Have a lovely weekend! Kind regards, Bijal Sanghani RIPE DBTF Chair

1 0

excuses for my response to provocations in the list yesterday
by JORDI PALET MARTINEZ 12 Feb '21

12 Feb '21

Hi all, Yesterday I should have reacted in a different way, ignoring the provocations, so I want to ask excuses for that. I think we (all) in those situations must privately ask the chairs to enforce he AUP and call to the order to the authors of inappropriate postings. I need to make clear that I still believe (not just this time) it is wrong to issue any subtle "warning" (or whatever you want to call it) to participants in any discussion. We, as it can't be other way, can disagree if a proposal, idea, problem statement, solution, is good or bad; that's it and that's what the discussion should be about. We are all free to ignore/delete emails from anyone if we believe that he/she is sending too many emails, but those emails, in general, except in clear cases that we all remember for spam, publicity of electoral candidates, etc., need to be allowed without restriction, because people are discussing about something that is in the scope of the list (apply this to any WG list as well). If we believe that something is out of the scope, we should call the chairs to tell to the poster, but not do ourselves and even less, do what I did: responding to them. If we look into previous discussions, same people that attacked me yesterday has sent (many times) more than "n" emails. So, if we want to define that, let's have it in the PDP or AUP, so it applies to everybody in the same way. My response to their provocation is only upsetting more people from the community against my proposals or ideas, so I'm helping them to achieve what they wanted: to ruin the discussion. Is not an excuse, but you also need to understand that this is not a consequence of a few minutes of "bad energy" from my side, but also a cumulus of private emails (sometimes from the same people that exposed themselves in the list), and attacks in different lists (often from the same people as well), such as mentions to the "Spanish Inquisition", among others. I tend to not overreact to those, even ignore them, or answer politely, but it seems that I should instead, report every single case to the chairs and avoid forming "dark clouds" and then having "storms". I'm not alone on this (and I got a couple of people writing me about that this time). We discussed long time ago, I think it was in the Diversity TF, how people take advantage of better knowledge of English to abuse and attack non-native speaker ones (or people that is not so fluent). We have mention about the lack of participation. Those subtle attacks definitively don't help to improve that, on the other way around, some people get scared, overreact, or go away. It is even more sad that some of those provocations come from people that are (or have been) chairs of WGs and I think they must be exemplary. It looks like some of them believe they are kings. Maybe one more thing to change in the PDP is a maximum number of terms to avoid this. I think also sanctions of the AUP should be stricter in those cases and this shows that also we are missing in the PDP a procedure for recalling chairs. For those that aren’t aware, this just happened in AFRINIC (a Recall Committee has decided that both cochairs are recalled with immediate effect, in short because they violated the PDP and took decisions or attributions beyond what is set in the PDP). Regards, Jordi @jordipalet ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.

10 16

Paging: A Microsoft engineer, preferably in charge of Outlook 365 mail service
by Carsten Schiefner 11 Feb '21

11 Feb '21

Dear all - could this person please be in touch by PM? Or be recommended to me by somebody else, also by PM? Thanks & best, -C.

1 0

Re: [ripe-list] RIPE Working Group Chair Collective Meeting Summary
by JORDI PALET MARTINEZ 10 Feb '21

10 Feb '21

Yesterday I avoided responding to the list and responded only to Leo, as I did to other emails, but I think that's wrong. We have the list to discuss about any relevant topic, and should not refrain despite of provocations, otherwise, the list becomes useless. So here is it: Fully agree, your text is precise. I forgot that not everybody in the list is participating ... Is like in the IETF, you are "a member" just by subscribing. Tks! Regards, Jordi @jordipalet El 9/2/21 16:29, "Leo Vegoda" <leo(a)vegoda.org> escribió: On Tue, Feb 9, 2021 at 5:56 AM JORDI PALET MARTINEZ via ripe-list <ripe-list(a)ripe.net> wrote: [...] > To be part of this community you just need to participate. No. To be a member of this community you only need to be present. That presence only requires joining a mailing list so that a person can choose to observe or participate. Posting to mailing lists is not a requirement. Regards, Leo ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.

1 0