- ripe-list - mailman.ripe.net

unsubscribe
by Steven Green 04 Mar '21

04 Mar '21

Please unsubscribe me Thanks, Steven Green Information Technology Manager Michigan HIDTA 26211 Central Park Blvd. STE 400 Southfield, Michigan 48076 https://www.whitehouse.gov/ondcp/ "CONFIDENTIALITY NOTICE: This message, including any attachments, is for the sole use of the intended recipient and may contain Michigan HIDTA and law enforcement sensitive, confidential or privileged information. It contains information that may be exempt from public release under the Freedom of Information Act (5 U.S.C. 552). Any unauthorized review, use, copying, dissemination, disclosure or distribution of such information by anyone other than the intended recipient is strictly prohibited. No portion of this email transmission and any attachments should be furnished to the public or the media, either in written or verbal form. If you have received this message in error, please contact Steven Green at (248) 728-3707 and delete all copies of the original message."

1 0

New on RIPE Labs: The RIPE Chair Team Reports - February 2021
by Alun Davies 03 Mar '21

03 Mar '21

Dear colleagues, On RIPE Labs now, the RIPE Chair Team reports on a month of conversations around policy development and continued efforts to secure a stable governance framework for the RIPE community. Read more from Mirjam and Niall: https://labs.ripe.net/Members/mirjam_kuhne/the-ripe-chair-team-reports-febr… Kind regards, Alun Davies RIPE Labs Editor RIPE NCC

1 0

Update Regarding RIPE NCC Access: Please Enable Two-Step Verification
by Ivo Dijkhuis 03 Mar '21

03 Mar '21

Dear colleagues, We recently announced that RIPE NCC Access, our single sign-on (SSO) service, had been targeted by a "credential-stuffing" attack. Our investigation has since identified five SSO accounts that we believe were breached. Only one of these accounts is associated with an LIR, but this is inactive and does not hold any IP resources. We have locked all five SSO accounts and notified the account holders. Many of you also suggested potential security improvements. These will be included in a detailed review of RIPE NCC Access. Finally, please help us to keep your accounts secure by enabling two-step verification for your RIPE NCC Access account. You can find instructions on enabling two-step verification at: https://www.ripe.net/participate/member-support/ripe-ncc-access/two-step-ve… In case of any suspicious activity on your account, report it to <security(a)ripe.net>. Regards, Ivo Dijkhuis Senior Information Security Officer, RIPE NCC

1 0

New on RIPE Labs: Transforming Information Security to Secure Businesses
by Alun Davies 01 Mar '21

01 Mar '21

Dear colleagues, In the first of a series of guest posts, Kathleen Moriarty of the Center for Internet Security (CIS) examines five trends that are already leading the way to better information security. On RIPE Labs now, learn more about the evidence for these trends and what can be done to help maximise their impact: https://labs.ripe.net/Members/kathleen_moriarty/transforming-information-se… Kind regards, Alun Davies RIPE Labs Editor RIPE NCC

1 0

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