- ripe-list - mailman.ripe.net

NRO NC Call for Nominations
by Hans Petter Holen 18 Mar '21

18 Mar '21

Dear colleagues, This is a call for nominations from the RIPE NCC service region to fill Filiz Yilmaz’s seat on the Number Resource Organization (NRO) Number Council (NC). Filiz recently stepped down from her position and will end her term on 31 May 2021. On behalf of the RIPE NCC, I would like to express our appreciation for the contribution that Filiz made during her time on the NRO NC. The election for this NRO NC seat will take place during the RIPE 82 meeting that will be held virtually from 17-21 May 2021. All members of the Internet community who are attending the RIPE Meeting may vote in the election. The deadline for nominations is 23 April 2021. Any individual residing within the RIPE NCC service region is eligible for nomination, except Regional Internet Registry (RIR) staff members. Self-nominations are permitted. The nomination process is available at: https://www.ripe.net/nro-nc-nominations-process-may-2021 Please send your nominations to <nominations(a)ripe.net> by 23:59 UTC on 23 April 2021. All confirmed nominations will be listed on the RIPE NCC website by 26 April 2021. All nominees may submit a written statement in support of their nomination for publication on the RIPE NCC website. Other people can express support for nominated individuals by sending an email to <nominations(a)ripe.net>. Expressions of support will also be published on the RIPE NCC website. To find out more about the NRO NC and the election process, please see: https://www.ripe.net/nro-nc-may-2021 Regards Hans Petter Holen Managing Director RIPE NCC Important dates: 23 April 2021: Deadline for NRO NC nominations 26 April 2021: Deadline for all confirmed nominations to be published on the RIPE NCC website 17-21 May 2021: Election to fill NRO NC seat during RIPE 82 21 May 2021: Announce successful candidate in closing plenary of RIPE 82

1 0

Report from the IAB COVID-19 Network Impacts Workshop 2020
by Mirjam Kuehne 15 Mar '21

15 Mar '21

Dear colleagues, In case you missed this: The Internet Architecture Board (IAB) recently publish a report about a workshop held last year to discuss impacts COVID-19 has on the network: https://datatracker.ietf.org/doc/draft-iab-covid19-workshop/ Especially the list of conclusions at the end might be interesting for operators. Also note the long list of relevant references and position papers. Kind regards, Mirjam Kühne RIPE Chair

1 0

New on RIPE Labs: Where Does Zero Trust Begin and Why is it Important?
by Alun Davies 15 Mar '21

15 Mar '21

Dear colleagues, In the second of a series of guests posts on information security, Kathleen Moriarty from the Center for Internet Security (CIS) takes a close look at the benefits of zero trust architectures and what their increased adoption means for the industry. Read more on RIPE Labs: https://labs.ripe.net/Members/kathleen_moriarty/where-does-zero-trust-begin… Kind regards, Alun Davies RIPE Labs Editor RIPE NCC

1 0

2020 IANA Numbering Services Review Committee Report Published
by Antony Gollan 10 Mar '21

10 Mar '21

This message is sent on behalf of the Number Resource Organization (NRO). *** 2020 IANA Numbering Services Review Committee Report Published Dear colleagues, The IANA Numbering Services Review Committee (IANA RC) is pleased to announce that it has published the 2020 IANA Numbering Services Review Committee Report. This report follows a 30-day public comment period on the IANA Performance Matrix Summary Report published by the RIRs seeking input from the broader community. The IANA RC was formed in 2016 and is responsible for publishing an annual report as advice to the NRO EC for its evaluation of the IANA numbering services. The report is based on the 2020 IANA Performance Matrix Summary Report, as well as on any input gathered from the global number community. The 2020 IANA Numbering Services Review Committee Report is published at: https://www.nro.net/2020-IANA-RC-Report We note that no incidents were reported in the IANA Numbering services to the RIRs in 2020. Kind regards, Bertrand Cherrier Chair, IANA Numbering Services Review Committee References: - IANA Stewardship Transition Archive: https://www.nro.net/internet-governance/iana/iana-stewardship-transition/ - Number Community Proposal: https://www.nro.net/wp-content/uploads/ICG-RFP-Number-Resource-Proposal.pdf - The SLA for the IANA Numbering Services: https://www.nro.net/wp-content/uploads/SLA-Executed-ICANN-RIRS.pdf - IANA Numbering Services Review Committee: https://www.nro.net/accountability/operational/iana-numbering-services-revi… *** Regards Antony Gollan Team Manager Communications RIPE NCC

1 0

New on RIPE Labs: HR from Home - Adapting in a Year of COVID
by Alun Davies 10 Mar '21

10 Mar '21

Dear colleagues, One year after the RIPE NCC made the move from a vibrant office in the centre of Amsterdam to fully remote work, HR Director Carolien Vos talks about what we’ve done to adapt. On RIPE Labs now, read what steps we've taken as an organisation to support staff wellbeing and keep working our way through the pandemic: https://labs.ripe.net/Members/carolien_vos/hr-from-home-adapting-in-a-year-… Kind regards, Alun Davies RIPE Labs Editor RIPE NCC

1 0

Notice to the ASO Community on Rejection Action to ICANN Board Resolutions on FY22 IANA Budget
by Antony Gollan 08 Mar '21

08 Mar '21

This message is sent on behalf of the Number Resource Organization (NRO). *** Notice to the ASO Community on Rejection Action to ICANN Board Resolutions on FY22 IANA Budget Dear RIR community, On 8 February 2021, the ICANN Board of Directors adopted resolutions regarding the following: - FY22 IANA Budget https://www.icann.org/resources/board-material/resolutions-2021-02-08-en The approved FY22 IANA Budget is available at: https://www.icann.org/en/system/files/files/adopted-iana-opplan-budget-fy22… This resolution (FY22 IANA Budget) is subject to Rejection Action Petitions from the community. The Address Supporting Organization as a Decisional Participant received a notice from the ICANN Secretary pursuant to Section 22.4(a)(v) of the ICANN Bylaws: https://www.icann.org/resources/pages/governance/bylaws-en/#article22 Any member of the ASO community can submit a rejection petition on the matter. If you are interested in submitting a Rejection Action Petition to the ASO, please consult Section 2 of Annex D of the ICANN Bylaws for the requirements which must be met by a Rejection Action Petition: https://www.icann.org/resources/pages/governance/bylaws-en/#annexD The period for submitting rejection petitions commenced on 19 February 2021 and will end on Friday 13 March 2021 at 07:59 UTC. Any Rejection Action Petition should be sent to the ASO Secretariat (secretariat [at] aso.icann.org) before the deadline. Kind Regards ASO Secretariat *** Regards Antony Gollan RIPE NCC

1 0

Stepping down from ICANN ASO AC/NRO NC
by Filiz Yilmaz 05 Mar '21

05 Mar '21

Dear colleagues, I am sending this mail to inform you that I will not be able to continue my post at the ICANN ASO Address Council (ASO AC), aka the NRO Number Council (NRO NC), after 31 May 2021. The decision did not come easy but had to be made due to various circumstances. I have full confidence that the RIPE Community will find an excellent replacement to fill in the vacancy in the next couple of months. I would like to thank Nurani Nimpuno and Hervé Clément with whom I’ve worked closely at the council in the recent years. I also thank you for your trust in me and giving me the opportunity to represent the RIPE Community at the ICANN fora. Kind regards Filiz Yilmaz

7 6

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