- ripe-list - mailman.ripe.net

DNSSEC Root Key Signing Key (KSK) for the Domain Name System
by Christopher Hawker 27 Mar '25

27 Mar '25

Hello Everyone, As many of you may know, one of the functions of the Internet Assigned Numbers Authority (IANA) is the global coordination of the DNS Root Zone. One of the core components to DNS is DNSSEC. The Root Key Signing Key (KSK) acts as the trust anchor for DNSSEC for the Domain Name System, and this trust anchor is configured in DNSSEC-aware resolvers to facilitate validation of DNS data. This is how your DNS servers are able to cryptographically validate the authenticity of DNS records they receive and serve. For more information pertaining to DNSSEC, how it operates, the KSK and the relevant policies and procedures, I recommend visiting https://www.iana.org/dnssec for more info. In order to ensure the security of the KSK, IANA utilises Hardware Security Modules (HSM) to generate the KSK pair of public and private keys, which in turn are used to sign the Zone Signing Key (ZSK), that itself is used to sign DNS records (RRsets) within a DNS zone. As it currently stands, both of these HSMs currently reside in high-security Key Management Facilities (KMFs) in the USA, with one facility located in Culpeper VA, and the other in El Segundo CA. Now, while the locations of these HSMs are highly secure, both of them are located on US soil. As most people who are familiar with redundancy, this is not a good idea for a number of reasons (which I won't go into detail here as it's outside the scope of this email). What we as a community MUST DO, is look at the relocation of one of these HSMs to an alternate country such as Singapore or Switzerland (regarded as two safe countries) to ensure the continued integrity of the Root KSK. Unfortunately, section 4.2(b) of the IANA Naming Function Contract (https://pti.cdn.icann.org/resources/151/IANA_Naming_Function_Contract.pdf) between the Internet Corporation for Assigned Names and Numbers (ICANN) and Public Technical Identifiers (PTI) that govern how IANA performs its functions prohibits the operation of functions outside of the US. Given that the Internet is one of the most critical pieces of global (and not just US-based) infrastructure, I feel that this section of the contract must be reviewed (and deleted or modified to allow for PTI to perform the functions from Singapore, Switzerland or another safe jurisdiction) to maintain the integrity of the Domain Name System. The Second IANA Naming Function Review Team (IFRT2) have released an initial draft report of its analysis, issues and recommendations which also incorporates a review of the Contract between ICANN and PTI. The IFRT2 have opened a public call for comments on the draft report, before they submit their Final Report to ICANN's Board of Directors which they expect to do before June this year. The Public Comment period closes for submissions on 28 April 2025 at 23:59hrs UTC, and I strongly encourage everyone to read the report and provide input regarding support to relocating one of the Key Management Facilities across the Pacific or Atlantic Oceans. To view the report and submit a comment, please go to https://www.icann.org/en/public-comment/proceeding/second-iana-naming-funct…. In order to submit a comment on the report, you will need an account on https://account.icann.org/. In closing, I cannot stress one thing enough - this is in no way speaks to the professionalism of ICANN's staff. The team at ICANN perform some of the hardest work out there, ensuring the integrity and stability of the Internet as we know it today and for that they cannot be thanked enough. This recommendation to move one of the KMFs overseas is simply to help protect it from potential political instability, bias, and to encourage neutralism. We're already doing it with the operation of the DNS Root Zone, let's take it one step further and strengthen the security of DNSSEC and the Root KSK. If you have any questions, please do feel free to ask, either on-list or off-list. Regards, Christopher Hawker

1 0

Second Call for Presentations for RIPE90
by Massimiliano Stucchi 19 Mar '25

19 Mar '25

Dear colleagues, The RIPE Programme Committee (PC) is now opening the second call for presentations seeking for content proposals from the RIPE community for the plenary sessions, lightning talks and BoFs. RIPE90 is going to be a hybrid meeting so both in-person and virtual presentations would be accepted and encouraged. The deadline to submit a presentation proposal is 8th of April 2025. Proposals submitted after this date will only be considered if there are still time slots available. Already submitted presentations which have not received an acceptance or rejection notification yet are still under consideration. Read more about the CfP and submit your presentation proposal at: https://ripe90.ripe.net/submit-topic/cfp/ More about RIPE90 meeting: https://ripe90.ripe.net/ Regards, Massimiliano Stucchi (On Behalf of the RIPE Programme Committee)

1 0

2024 IANA Numbering Services Review Committee Report Published
by Ulka Athale 18 Mar '25

18 Mar '25

This message is sent on behalf of the NRO Secretariat. The announcement can be viewed at: https://www.nro.net/2024-iana-numbering-services-review-committee-report-pu… ---------------------------------------- 2024 IANA Numbering Services Review Committee Report Published ---------------------------------------- The IANA Numbering Services Review Committee (IANA RC) is pleased to announce that it has published the 2024 IANA Numbering Services Review Committee Report. 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. This report follows a 30-day public comment period on the RIR IANA Numbering Services Review Matrix published by the RIRs seeking input from the broader community. It is based on the 2024 RIR IANA Numbering Services Review Matrix, as well as on any input gathered from the global number community. The 2024 IANA Numbering Services Review Committee Report is now published at: https://www.nro.net/wp-content/uploads/2024-IANA-RC-Report.pdf On behalf of the IANA Review Committee Nick Nugent Chair, IANA Numbering Services Review Committee ---------------------------------------- Background Information The IANA Numbering Services Review Committee (“RC”) committee, comprising of community representatives from each Regional Internet Registry (“RIR”) region, advises RIRs on the IANA Functions Operator’s performance of the IANA Numbering Services and adherence to the Service Level Agreement (“SLA”) between the IANA Numbering Services Operator and the RIRs (as defined in the Number Community Proposal). Their role is to advise and assist the Number Resource Organization Executive Committee (“NRO EC”) in a periodic review of SLA compliance for the IANA Numbering Services provided to the Number Community. The RC submits an annual report of its findings to the NRO EC. This committee was established in October 2016 for this purpose with representatives from all five RIR regions upon the recommendation of the Internet Number Community as part of the IANA Stewardship Transition. You can find information at: https://www.nro.net/internet-governance/iana/ ---------------------------------------- Kind regards, Ulka Athale RIPE NCC www.ripe.net

2 1

Survey on Segment Routing deployment
by Dekinder Florian 14 Mar '25

14 Mar '25

Hello RIPE community, I recently shared a survey (2 months ago) as part of a research project on segment routing (SR) deployment practices among network operators. The goal is to gain insights into how SR is currently deployed and managed across different ASes. If you are involved in SR management in your network and if you missed the first request, I would greatly appreciate your input. The survey takes no more than 5 minutes to complete. https://docs.google.com/forms/d/e/1FAIpQLSd9d77tMC_azhcfWWCMR_nHCBlfzu8VI-v… Thank you in advance for your time and contribution! Best regards, Florian Dekinder

1 0

Call for Nominations (RIPE Chair / Vice Chair)
by RIPE NomCom Chair 12 Mar '25

12 Mar '25

Dear RIPE participants, This year, a nominating committee (NomCom), with help from the wider community, will select two people to fill the positions of RIPE Chair and Vice Chair. As chair of the 2025 RIPE NomCom, I would like to invite you to nominate candidates for these positions. As members of the RIPE community, you will have some idea of what the RIPE Chair is responsible for and what kind of person you would like to see in this role as well as the Vice Chair role. Please think about suitable candidates, engage with them, discuss this with your peers, and nominate people who will have the support of the community. You may nominate any member of the RIPE community for either position. Self-nominations are also permitted. NomCom members and members of the RIPE NCC Executive Board are not eligible to be considered. Send your nominations to nominations(a)ripenomcom.org and include a description of the skills or expertise that make your candidate a desirable choice. Please also include a working email address or telephone number for the nominee and indicate whether they are aware of your nomination. The NomCom will also be interested in your opinion about the performance of the incumbent RIPE Chair, Mirjam Kühne, and RIPE Vice Chair, Niall O'Reilly. The NomCom is also interested in any lessons and observations we or the community can take away from the previous NomCom and the first nominated RIPE Chair / Vice Chair term which is drawing to a close. The deadline for all nominations is Sunday, March 30th 23:59 UTC. You can find more information in the relevant RIPE Documents: ripe-714: A brief description of the RIPE Chair’s role. [1] ripe-787: Information about the selection process. [2] ripe-788: Detailed information about the RIPE NomCom [3] RIPE NomCom web site: https://ripenomcom.org/ All information regarding the RIPE Chair / Vice Chair remuneration can be found in the Remuneration document (authored by the RIPE NCC) [4] We are happy to answer any further questions you may have. Jan Žorž Chair of the 2025 RIPE NomCom [1] - https://www.ripe.net/publications/docs/ripe-714/ [2] - https://www.ripe.net/publications/docs/ripe-787/ [3] - https://www.ripe.net/publications/docs/ripe-788/ [4] - https://ripenomcom.org/wp-content/uploads/2025/02/2025-02-03-RIPE-Chair-Rem… -- Anything that can be configured can be misconfigured. [RFC5505]

1 1

[news] Gabor de Wit Appointed Chief Registry Operations Officer
by Hans Petter Holen 11 Mar '25

11 Mar '25

Dear colleagues, We are pleased to announce that Gabor de Wit will start as our new Chief Registry Operations Officer as of 1 May 2025. After an extensive search, we concluded that Gabor is the best candidate for the job. Gabor has strong leadership experience with both a technical and business background. During the hiring process, Gabor showed his capabilities in leadership, people management, project and change management, and stakeholder engagement. I will continue to fill the role of Acting Chief Registry Officer in the interim. I am confident that Gabor has what it takes to succeed in this role and I ask that you join me in welcoming him to this important role for the RIPE NCC and the RIPE community. Kind regards, Hans Petter Holen CEO and Managing Director, RIPE NCC

1 0

iFog GmbH - Contact
by Christopher Hawker 09 Mar '25

09 Mar '25

Hello All, I have been attempting to reach out to iFog on a number of occasions now about their AS-SET (and the removal of ours from theirs), however, their NOC has not responded to any emails. Two things: 1. If anyone from iFog is on this list, can you please remove AS153346 from AS-IFOG, as well as AS153346:AS-HAWKNET from AS-FOGIXP? No one is responding to your NOC emails. 2. What is the process for reporting unresponsive Whois contact information to RIPE NCC? Regards, Christopher Hawker

1 0

RIPE Labs Article Competition - RIPE 90
by Alun Davies 04 Mar '25

04 Mar '25

Dear colleagues, This is a reminder that the RIPE Labs Article Competition for RIPE 90 is open! If you have something interesting to say about the Internet, but you don't usually get the chance to come share those things at RIPE Meetings, this is a really good opportunity to fix that. The author of the winning article will receive free tickets, travel, and accommodation for the upcoming RIPE Meeting in Lisbon this May. The competition deadline is 4 April and you can get more information on how to enter over on RIPE Labs: https://labs.ripe.net/competitions/ripe-labs-article-competition-ripe-90/ Kind regards, Alun Davies RIPE Labs Editor RIPE NCC

1 0

ICP-2 Principles Questionnaire Report and Data Published
by Ulka Athale 24 Feb '25

24 Feb '25

This message is sent on behalf of the Number Resource Organization (NRO) ------------------------- The announcement is available at: https://www.nro.net/icp-2-principles-questionnaire-report-and-data-publishe… ------------------------- ICP-2 Principles Questionnaire Report and Data Published ------------------------- The Number Resource Organization Number Council* (NRO NC) has completed its qualitative analysis and summary of the community responses received to the questionnaire on the proposed principles to update ICP-2. The questionnaire was open from 8 October until 6 December 2024. During this window, we received 298 individual submissions from the Regional Internet Registry (RIR) communities. The summary and the raw data questionnaire are available here: https://www.nro.net/policy/internet-coordination-policy-2/icp-2-principles-… This summary provides an overview of the input received, first and foremost, to support the drafting of the updated ICP-2 document, and secondly, to report back to the RIR communities. Thirdly, the feedback provides important insights that will be valuable for the future implementation of the updated version of ICP-2. The summary does not include the NRO NC’s opinions on or responses to the comments submitted, nor does it include an evaluation of the communities’ opinion on the principles. The NRO NC will continue to discuss the communities’ feedback as well as the input received through ICANN’s public comment while drafting the updated ICP-2 document. For each proposed principle, respondents could express their level of agreement through a five-point opinion scale (Strongly Agree, Agree, Neutral, Disagree, or Strongly Disagree) and provide comments. Additionally, they could share general feedback at the end of the questionnaire. It was noted in reviewing the responses that approximately half were found to be duplicate comments. The duplicate responses were consolidated and considered as a single input. It is important to note that these near-identical responses have also been included in this analysis. We have provided more details on how these responses were identified and treated in the Methodology section of the summary and the PDF containing the text of the comments. Further, many responses provided a rating that did not match the content of the response. In these cases, we prioritised the content of the response, rather than using the rating. For the purposes of transparency, the full datasets with the duplicate responses, as well as a filtered dataset without duplicate answers are available in both PDF and CSV formats. We encourage you to browse through the actual data along with reading our summary. We sincerely thank everyone who has shared their insights. It was a long questionnaire, and we appreciate the time, thought and effort put in by our respondents. The NRO NC *The Number Resource Organization Number Council (NRO NC) is also known as the Address Supporting Organization Address Council (ASO AC) within ICANN, where it serves as the body responsible for overseeing global policy development related to Internet number resources. ------------------------- Kind regards, Ulka Athale RIPE NCC www.ripe.net

1 0

Introducing the New RIPEstat UI
by Ties de Kock 21 Feb '25

21 Feb '25

Dear colleagues, We're pleased to present a first look at the new RIPEstat. This will become the default interface for RIPEstat as of 26 February 2025: https://beta.stat.ripe.net/ In October last year, we decided it was time to streamline things and start the process of moving back to a single, consolidated RIPEstat UI. The goal was to come up with something that would stay true to the foundations of the original interface from 2013—for which many users voiced a preference in testing and feedback—but also to introduce some much-needed changes that would, among other things, bring it in line with the modern theme now familiar across other RIPE NCC applications. Until then, to get a head start on collecting feedback for the new UI, we invite you to take a look at the beta version above and share any feedback you might have so we can keep learning and incorporating your input into the design. Please note that the 2020 version (aka the RIPEstat app) will initially remain available but will no longer be supported. We will sunset it six months after the release of the new UI. To learn more about the new RIPEstat UI and what’s changing, check out this article: https://labs.ripe.net/author/ties/introducing-the-new-ripestat-ui/ Best regards, Ties de Kock, On behalf of the RIPEstat team

1 1