- mat-wg - mailman.ripe.net

New on RIPE Labs: Splitting the Ping
by Alun Davies 24 Mar '21

24 Mar '21

Dear colleagues, Pings provide a simple measure of how long it takes to get there and back across the Internet. What's not so simple is working out how long the trip there took versus the trip back. In this guest post on RIPE Labs, Ben Cox introduces a method for splitting the ping: https://labs.ripe.net/Members/ben_cox/splitting-the-ping Kind regards, Alun Davies RIPE Labs Editor RIPE NCC

1 0

From Data Ethics to Data Justice: RIPE Labs article about Data Feminism
by Vesna Manojlovic 11 Mar '21

11 Mar '21

Dear all, On 8. March, for International Women’s Day, we published an article on RIPE Labs about data science from an intersectional feminism perspective: https://labs.ripe.net/Members/becha/data-feminism-from-data-ethics-to-data-… In the article, I explore how the RIPE community can benefit from involving users in the design processes for collecting, storing and visualising data. As network operators, we have the power to create systems that use data for good, or for harm - and I am pointing out the questions to be asked about challenging and changing those structures. For the MAT-WG specifically, there are other interesting links: open data sources for researchers; code available for developers to re-use, and there is potential for cooperation with the academic community. Regards, Vesna Manojlovic Community Builder RIPE NCC

1 0

RIPE Atlas measurements documentation wiki
by Emile Aben 15 Feb '21

15 Feb '21

Dear all, We're trying something new! We have a part of our public RIPE Atlas github pages dedicated to documenting RIPE Atlas measurements better. Read all about it, including an example around measuring RPKI repositories, of how this is useful here: https://labs.ripe.net/Members/emileaben/tracking-rpki-repository-performanc… or directly go to the 'RIPE Atlas measurements bundles' wiki: https://github.com/RIPE-Atlas-Community/ripe-atlas-tips-and-tricks/wiki/Mea… Kind regards, Emile Aben RIPE NCC

1 0

RIPE Atlas testing of reserved IPv4 addresses
by Seth David Schoen 26 Jan '21

26 Jan '21

Hi mat-wg, I'm Seth, formerly a staff technologist at EFF and one of the co-developers of Let's Encrypt and Certbot. Recently, I've been working with John Gilmore on the IPv4 Unicast Extensions Project, which aims to make some of the IPv4 address blocks that were reserved in the 1980s and 1990s (and that continue to be unused, or nearly so) available for addressing and routing on the Internet. This project involves many different kinds of work, including writing software patches to make various OSes and devices willing to generate and accept packets to reserved addresses, writing Internet-Drafts to describe addressing policy changes with IETF, testing devices to see how they actually treat such packets, talking to various constituencies about these proposals, and working with the Internet measurement community to understand how the Internet as a whole treats packets to or from currently-reserved address ranges, and how that treatment evolves over time. Two prominent examples that are already supported by Linux hosts are the netblocks 0/8 ("this network") and 240/4 ("experimental"/"future use"). According to Internet standards created in the 1980s and still in effect, these address ranges cannot be allocated and should not be assigned to hosts or used on the public Internet. However, several key implementations started allowing 240/4 addresses about 11 years ago during an earlier IETF attempt to open up that netblock, including Linux, Android, macOS, iOS, and Solaris. In 2019, Linux kernel version 5.3 allowed ordinary unicast use of 0/8. Today, there are rumors that various organizations are currently using such reserved addresses as unofficial RFC 1918-like private address space, without formal policy coordination with anyone. (There is even some public documentation from Google suggesting making private use of 240/4.) I participated in the Atlas probe deployathon in November and successfully got a probe up and running. I have also been talking to a few RIPE people about our interests and managed to confirm that (regardless of their underlying OS or network treatment) the Atlas software probes will reject probing any reserved address space, while the backend infrastructure will refuse to ask probes to connect to it. So, I'm here to introduce our project and ask the community's view about removing these restrictions so that such addresses can actually be probed and measured. We understand and hope that the majority of such tests would currently result in errors. Even the errors themselves could be interesting: for example, we would like to know how often routing to reserved address ranges fails on a probe host, versus on the probe host's first-hop router, versus inside of ISP infrastructure. We would also like to see how this changes over time as a result of OS software changes that roll out into the field. We would also like to see whether we can detect unofficial use of particular reserved address ranges as private address space. Our medium-term goal is to advertise global routes to portions of these reserved address spaces, and use the probes to assess how well those routes propagate through the Internet, and find where blockages occur. Clearly, we can't do this until both the probe firmware, and the central dispatcher, allow tests to these addresses. Our long-term goal is to have these addresses treated as ordinary unicast addresses by all nodes, including Atlas probes, so the Atlas changes to remove the restrictions would be useful permanent changes.

1 0

Address Assignment Practices in IPv4 and IPv6
by Stephen D. Strowes 21 Jan '21

21 Jan '21

Hi all, We've published a study on the stability of IPv4/IPv6 assignments in domestic ISPs, and the size of the IPv6 prefixes that networks typically assign to subscribers. We look at this from two different angles: what can we measure from RIPE Atlas, and what do operators state in the RIPE Database? In particular, understanding the size of IPv6 delegated prefixes is important for applications such as host reputation & blocklists, geolocation, and research on network measurement. The RIPE Database offers the community a way to share information on their prefix delegations, and deserves some attention! Read more here: https://labs.ripe.net/Members/stephen_strowes/address-assignment-practices-… Cheers, S.

1 0

New on RIPE Labs: Our First Glance at the Uganda Internet Shutdown
by Alun Davies 14 Jan '21

14 Jan '21

Dear colleagues, We've used RIPE NCC tools and datasets to put together some initial observations on the Internet shutdown currently taking place in Uganda. We hope our tools and visualisations will help support further analysis of the impact of the shutdown: https://labs.ripe.net/Members/becha/our-first-glance-at-the-uganda-internet… Kind regards, Alun Davies RIPE NCC

1 0

New Internet Country Report: Gulf Region
by Suzanne Taylor 15 Dec '20

15 Dec '20

Dear colleagues, We’ve published the latest in our series of country reports, this time looking at the Internet landscape in eight countries in the Gulf region. This is the sixth such country report that the RIPE NCC has produced as part of an ongoing effort to support Internet development throughout our service region by making our data and insights available to both local technical communities and decision makers. The report looks at the state of the Internet in the Gulf region, including its market landscape and regulatory environment, Internet number resources and opportunities for growth, regional connectivity, routing and routing security, and the operators and paths providing international transit into the region. We also reach a number of conclusions about what is needed to further develop the Internet in the Gulf region. You can learn more and download the report from RIPE Labs: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-ncc-internet-count… <https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-ncc-internet-count…> Please let us know if you have any feedback on the report or are interested in learning more about RIPE NCC data. And please share it with any of your colleagues who might be interested. Best regards, Suzanne _____________ Suzanne Taylor RIPE NCC

1 0

Today: RIPE Atlas Software Probes Deployathon!
by Vesna Manojlovic 25 Nov '20

25 Nov '20

Dear colleagues, We're looking forward to celebrating 10 years of RIPE Atlas by deploying software probes - and there's still time for *you* to join us! We have 120+ registered participants from more than 20 countries, that will get help from RIPE NCC staff, with mentors from the community that speak your language. There are also several ideas for hackathon projects, by more advanced RIPE Atlas community experts. We will be online all day today with sessions scheduled at regular intervals. You can join in for the presentations that interest you, or spend some time in one of the online platforms only open today: * SpatialChat for social interactions & hacking * Two Zoom rooms, for presentations, Q&As and live demo's * Slack for chat and technical / code sharing -------------------------- Zoom Presentations Schedule -------------------------- Living Room (English): 08:00 UTC, 11:00 UTC, 15:00 UTC Sun Room (Russian): 09:00 UTC Sun Room (Spanish): 14:00 UTC The Closing Session will take place in the Living Room: 16:00 UTC The full schedule and access codes are on RIPE Labs: https://labs.ripe.net/Members/becha/lets-deploy-together-ripe-atlas-softwar… Kind regards, Vesna Manojlovic Community Builder RIPE NCC

1 0

Fwd: Second call for nominations: IRTF ANRP 2021
by Stephen D. Strowes 19 Nov '20

19 Nov '20

Hi, The nomination deadline for the IRTF Applied Networking Research Prize (ANRP) is only a few days away. Details below! Have you seen work recently that would be deserving of funding and focus at an upcoming IETF/IRTF meeting (e.g., recent work you saw at RIPE81 or IMC, or the amazing work your students are doing)? Please consider nominating! Cheers, S. -------- Forwarded Message -------- Subject: Second call for nominations: IRTF ANRP 2021 Date: Mon, 2 Nov 2020 23:35:02 +0000 From: Colin Perkins <csp(a)csperkins.org> To: IETF Mailing List <ietf(a)ietf.org> APPLIED NETWORKING RESEARCH PRIZE (ANRP) 2021 https://irtf.org/anrp/ ******************************************************************* *** Submit nominations for the 2021 award period of the *** *** Applied Networking Research Prize until November 22, 2020 *** *** *** *** (Please share this announcement with your colleagues.) *** ******************************************************************* The Applied Networking Research Prize (ANRP) is awarded to recognise the best recent results in applied networking, interesting new research ideas of potential relevance to the Internet standards community, and upcoming people that are likely to have an impact on Internet standards and technologies, with a particular focus on cases where these people or ideas would not otherwise get much exposure or be able to participate in the discussion. We encourage nominations of researchers with relevant research results, interesting ideas, and new perspectives. The award will offer them the opportunity to present and discuss their work with the engineers, network operators, policy makers, and scientists that participate in the Internet Engineering Task Force (IETF) and its research arm, the Internet Research Task Force (IRTF). Both self- and third-party nominations for this prize are encouraged. The Applied Networking Research Prize (ANRP) consists of: • a cash prize of $1000 (USD) • an invited talk at the IRTF Open Meeting • a travel grant to attend a week-long IETF meeting (airfare, hotel, registration, stipend - COVID-19 permitting) • recognition at the IETF plenary • an invitation to related social activities In addition, prize winners may be offered additional travel grants to attend future IETF and/or IRTF meetings. Such grants are made at the discretion of the award committee, based on community feedback, engagement with the community, and potential future impact. Applied Networking Research Prize awards are made once per calendar year. Each year, several winners will be chosen and invited to present their work at one of the three IETF meetings during the following year. # HOW TO NOMINATE Nominations are for a single author of an original, peer-reviewed, journal, conference or workshop paper that was recently published or accepted for publication. The nominee must be one of the main authors of the nominated paper. Both self-nominations (nominating one’s own paper) and third-party nominations (nominating someone else’s paper) are encouraged. The nominated paper should provide a scientific foundation for possible future engineering work in the IETF, or research and experimentation in the IRTF. It should analyse the behaviour of Internet protocols in operational deployments or realistic testbeds, make an important contribution to the understanding of Internet scalability, performance, reliability, security or capability, or otherwise be of relevance to ongoing or future IETF or IRTF activities. Nominations must briefly describe how the nominated paper relates to these goals. They should describe how involving the nominee in the IETF and IRTF process, and bringing them to an IETF meeting, would help to foster the transition of the results and/or ideas into new IETF engineering work or IRTF experimentation, or otherwise seed new activities that will have an impact on the real-world Internet. The goal of the Applied Networking Research Prize (ANRP) is to foster the transitioning of research results into real-world benefits for the Internet. Therefore, applicants must indicate that they (or the nominee, in case of third-party nominations) are available to attend at least one of the IETF meetings in the following year. In-person attendance is desirable, where possible, but due to the impact of the COVID-19 pandemic remote participation options will be available for ANRP prize winners at all IETF meetings in 2021. Nominations are submitted via https://irtf.org/anrp/ and must include: • the name and email address of the nominee; • a bibliographic reference to the published (or accepted) nominated paper; • a PDF copy of the nominated paper; • a statement that describes how the nominated paper fulfills the goals of the award and how the nominee would engage with the IETF and/or IRTF community; • a statement of the nominees availability to present their work at the IETF meetings in during 2021; • a statement that the nominee accepts that the IRTF Intellectual Property Rights disclosure rules will apply to their award talk at the IRTF open meeting; • a brief biography or CV for the nominee; and • optionally, any other supporting information (link to nominee’s web site, etc.) All nominees will be notified by email about the decision regarding their nomination. Nominations for the Applied Networking Research Prize (ANRP) are not considered to be contributions to the IETF or IRTF. However, the invited talks at the IRTF Open Meeting are considered to be contributions and the IRTF Intellectual Property Rights disclosure rules apply. # IMPORTANT DATES Applications close: November 22, 2020 (hard) Notifications: December 18, 2020 # SPONSORS The Applied Networking Research Prize is supported by the Internet Society in coordination with the Internet Research Task Force (IRTF). Additional corporate sponsorship is kindly provided by Comcast and NBC Universal. If your organisation would like to support the ANRP, please contact anrp(a)irtf.org.

1 0

New on RIPE Labs: Join Us for a RIPE NCC Open House on 10 Years of RIPE Atlas
by Alun Davies 17 Nov '20

17 Nov '20

Dear colleagues, Tomorrow we’ll he holding a RIPE NCC Open House event to celebrate 10 years of RIPE Atlas. Join us for a mix of presentations, diverse use cases from external speakers, and open discussion between the people who are helping expand RIPE Atlas right now. In this new article on RIPE Labs, we tell you what we’ve got lined up and invite you to register: https://labs.ripe.net/Members/alun_davies/join-us-for-a-ripe-ncc-open-house… Kind regards, Alun Davies RIPE NCC

1 0