- mat-wg - mailman.ripe.net

MAT WG agenda for RIPE89
by Massimo Candela 29 Oct '24

29 Oct '24

Dear all, The MAT working group session will take place on Tuesday 29 October at 16:00 CET. This is the agenda: 16:00 - 16:05 - Welcome - Chairs 16:05 - 16:20 - Measuring and Visualizing DNS Watersheds - Jim Cowie 16:20 - 16:30 - A First Look at User-Installed Residential Proxies From a Network Operator's Perspective - Etienne Khan 16:30 - 16:45 - IoT bricks over v6 - Tianrui Hu 16:45 - 17:00 - Target Acquired? Evaluating Target Generation Algorithms for IPv6 - Lion Steger 17:00 - 17:15 - What’s in the Dataset? Unboxing the APNIC User Populations - Vasilis Giotsas 17:15 - 17:25 - RPKI flutter - Emile Aben 17:25 - 17:30 - Closing Remarks - Chairs If you are not already registered: https://ripe89.ripe.net/attend/register/ See you in Prague! Ciao, Massimo (for the MAT WG chairs)

1 1

A Detailed Look at Our Recent RIPE Atlas Infrastructure Migration
by Robert Kisteleki 02 Oct '24

02 Oct '24

Dear colleagues, Today we published a RIPE Labs article about the work we've been doing on the RIPE Atlas infrastructure. Please feel free to read it here: https://labs.ripe.net/author/kistel/a-detailed-look-at-our-recent-ripe-atla… Regards, Robert Kisteleki RIPE NCC

1 0

Changes to the RIPEstat UI
by Ties de Kock 01 Oct '24

01 Oct '24

Dear colleagues, Over the next few months, we will be making changes to RIPEstat, our information service and open data platform. Most noteworthy, we will introduce a new user interface (UI) that combines elements of the two previous versions introduced in 2013 and 2020. Initially, we will focus on reverting to the 2013 UI and adding the unique features that were available only in the 2020 UI. Afterwards, we will continue building on what we have, and on what we learned, and build something better that aligns with what our users need. Finally, we will sunset the 2020 UI as we continue developing the newer user interface. Our decision was made after extensive user research whilst we maintained two interfaces for a few years, and tried to bridge the gap between the ‘old’ and ‘new’. Our aim now is not simply to bring back an older platform, but to focus on the elements that matter to RIPEstat users the most, and build on them to modernise the product altogether. You can read more details about our decision in our RIPE Labs article: https://labs.ripe.net/author/adonis_stergiopoulos/streamlining-ripestat-bui… We welcome your comments on this mailing list, on the RIPE NCC Forum or by emailing us at stat(a)ripe.net. Kind regards, Ties de Kock Specialist software engineer RIPE NCC

1 0

Some historical RIPEstat data will not be available from 24 September
by Felipe Silveira 30 Sep '24

30 Sep '24

Dear colleagues, As we shared back in May, we have been working to reduce our data centre footprint by managing the data for RIS and RIPEstat more efficiently[1]. We have experienced some problems which mean that parts of the historical RIPEstat data will not be available for an extended period. To reduce our data centre usage, we have been exporting RIS-related datasets from the database that contains our largest datasets (HBase) to a new environment, which allows us to decommission our old Hadoop cluster. During the migration, we encountered timeouts and memory limitations with old servers and software that held historical data. Here we faced a difficult choice: we could either extend our data centre contracts at considerable additional cost, or we could accept that certain historical data would not be available to users for an extended period. We decided on the second approach. It is important to be clear that we haven’t lost anything here. However, this does mean that we will not be able to provide aggregated historical data for a number of API calls and their corresponding widgets for some time after we complete our migration. These include: as-path-length, as-routing-consistency, asn-neighbours, asn-neighbours-history, bgp-update-activity, bgp-state, bgp-updates, bgplay, ris-peerings, routing-status, visbility. As mentioned, this has been a difficult process. We may still encounter other issues when we make the switch to the new environment tomorrow (24 September). My team is doing their utmost to keep any disruption to a minimum, but there are no guarantees everything will go to plan. We will be looking at the most efficient way to rebuild access to the historical data in the coming months, and we will share more details in an article on RIPE Labs soon. Kind regards, Felipe Victolla Silveira Chief Technology Officer RIPE NCC [1] For more on this, refer to the following: - Reducing our Data Centre Footprint (RIPE Labs): https://labs.ripe.net/author/felipe_victolla_silveira/reducing-the-ripe-ncc… - RIPE 88 Technology Update (slides 10-20): https://ripe88.ripe.net/wp-content/uploads/presentations/89-RIPE-88-RIPE-NC…

3 2

RIPEstat database migration postponed
by Felipe Silveira 26 Sep '24

26 Sep '24

Dear colleagues, Following Monday’s announcement, we have decided to postpone the move of our largest datasets (HBase) to a new environment by one month. As I mentioned in my last email, this has been an unexpectedly complex process that has required a massive effort from our engineering teams. To ensure that RIPEstat will continue operating, we did not feel confident going ahead when this could result in the service being severely disrupted. I am sure many of you have questions. We plan to publish a RIPE Labs article with more details soon, including which historical data will be delayed when the migration is fully completed. Kind regards, Felipe Victolla Silveira Chief Technology Officer RIPE NCC

1 0

Call for presentations for MAT WG at RIPE 89
by Massimo Candela 26 Aug '24

26 Aug '24

Hi all, RIPE89 will take place 28 Oct - 1 Nov in Prague. We are seeking presentations for the MAT WG session, scheduled on Tuesday, 29 Oct! Interesting topics (not limited to): * Measurement research, preferably with operational impact * Operational initiatives that could inspire new research directions * Projects focused on network data collection * Tools for network data analysis and visualization * Innovative measurement techniques and proposals Submit your proposal at mat-wg-chairs [at] ripe.net by **Friday 4 October**. Include in your proposal: * a title * a draft of the presentation (an outline is okay) * a paragraph describing the topic and why it is of interest to the community * if you are planning to present in person or remote. Thanks! Nina, Stephen, Massimo as WG Chairs

1 0

Join the Using RIPE Atlas Webinar on 4 July 2024 - Registration Open
by training mailbox 28 Jun '24

28 Jun '24

Dear colleagues, We are pleased to announce that the RIPE NCC will host another *Using RIPE Atlas Webinar* session on *Thursday, 4 July 2024*. *Duration*: 2 hours *Cost*: Free *Open to*: Everyone interested This webinar helps you to monitor your network and troubleshoot it with RIPE Atlas. Create specific tailor-made measurements that suit your needs using API calls or the command line interface. *Prerequisites:* - Basic knowledge of networks - How the Internet works - Basic understanding of IP, ASN, domains - Familiarity with pings and traceroutes *After this webinar, you will be able to:* - Monitor your network using RIPE Atlas measurements - Troubleshoot your network using measurements from RIPE Atlas - Use the RIPE Atlas command line interface and the API to create tailor-made measurements For more *information and registration*, please visit: https://learning.ripe.net/w/courses/17-using-ripe-atlas-webinar *Help Us Spread the Word*: We'd greatly appreciate your support in promoting this webinar. Please share our social media posts with your network: *LinkedIn*: https://www.linkedin.com/posts/ripe-ncc_webinar-onlinelearning-bgp-activity… *Facebook*: https://www.facebook.com/share/p/9XkXAtTPxve7dH3E/ *X (Twitter)*: https://x.com/ripencc/status/1805210020272914863 Thank you for your assistance in helping us reach a wider audience. Kind regards, Olivia Ruimwijk RIPE NCC -- To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://www.ripe.net/mailman/listinfo/mat-wg/

1 0

Session started at RIPE88
by Massimo Candela 22 May '24

22 May '24

Hi all, The MAT session started at RIPE88. Join remotely at: https://ripe88.ripe.net/live/main/ Ciao, Massimo

2 1

Summary of the discussions about previous proposals
by Robert Kisteleki 13 May '24

13 May '24

[This is the same message I sent to the RIPE Atlas ML. The majority of the content relates to RIPE Atlas.] Dear all, In response to community feedback, as well as to the observed behaviour of RIPE Atlas, earlier we put out some proposals about some aspects of future behaviour of RIPE Atlas. We’d like to summarise what we’ve heard so far (written responses as well as verbal discussions we participated in), and the path we plan to take based on these. Probe farming: There were many voices who agreed with some form of limiting this behaviour. We were also asked to reach out to users who are using many probes this way now. We did and the short summary is that most (but not all) answers give reasonable justification. Conclusion: we’ll add the relatively simple proposed rules (in short: limit the number of software probes from the same IP/prefix). Later on we can consider softer approaches, e.g. reducing the number of credits given to hosts with excess probes or using probe similarity metrics. Measurement aggregators: We proposed to embrace this existing phenomenon, ask these users to in the future give the system an indication about the distinct clients they serve, and perhaps step up as sponsors in such cases. We received many responses to this proposal. For the most part, current aggregators who responded stated that they have no significant issues with providing such client information – in an anonymised way of course. At the same time some of them stated that adding a “mandatory sponsorship” would discourage them from using RIPE Atlas in the future. Some argued that by having enough credits to do so, they were in fact contributing positively to the network already, and in fact some of them are or were sponsors. Conclusion: we’ll add the features needed to implement such aggregations, and work on incentives for these users to become RIPE Atlas sponsors. We’ll also add the need for proper attribution to the service, similar to what the commercial use policy describes. We may also look at additional requirements to ensure proper funding for our membership services. Data retention principles: This proposal was a high level one and we received limited feedback. One discussion raised how “financially sustainable” is defined; perhaps the best summary of this is the recent RIPE Labs article published by our CTO Felipe: https://labs.ripe.net/author/felipe_victolla_silveira/reducing-the-ripe-ncc… Conclusion: we are implementing our data storage and access features along the principles we laid out. For transparency, we’ll also include summaries of proposals we put out earlier (see: https://labs.ripe.net/author/kistel/five-proposals-for-a-better-ripe-atlas/), for which we haven’t provided a written conclusion. Remove per-hop “late” packets from traceroute [LATE-PACKETS]: we only heard support for this, therefore it’s in our plans now. Measure well-known CDNs [CDN-HTTP]: Multiple responses argued that by selecting a “short list” of CDNs that are included by default, there’s an implicit statement and/or bias in the system towards bigger providers, contributing to some aspects of centralisation. Others pointed out that this approach reflects the reality of generic users, since the majority of the content they consume is provided by said CDNs. In addition, there were some voices supporting this proposal because of the value it provides to (smaller) CDNs or because it incentivises probe hosts to join or to keep their probes connected. Based on these discussions we’ll not go ahead with a full set of CDN measurements; however we’ll try a smaller scale experiment to discover the potential benefits to all users. Generic HTTP measurements [GENERIC-HTTP]: the discussions centered around some reiterations of the previous arguments (i.e. the safety of both the probe host and the providers’ sides) and if/how the proposed opt-in activity of the probe host would help this. Given these arguments, and that only a few voices expressed their explicit support for this, we’ll put this activity on hold; we can revisit this if/when the community wishes so. Add support for STARTTLS measurements [STARTTLS]: there were lengthy discussions about how certain SMTP servers may react to such incoming measurements. The general agreement was that this measurement type can be useful, with the confirmation that these checks will explicitly stop after STARTTLS (i.e. they will not have the ability to even try initiating sending mails or such). Remove support for non-public measurements [ONLY-PUBLIC]: the discussion raised both arguments for and against changing the system’s behaviour. Some people also raised the possibility of making private measurements more costly (in terms of credits). We’d also like to note the reference to the data retention principles (private measurement results are not available to all users, therefore we’ll only store them for a limited time). All in all, for the time being we do not plan to make behavioural changes about this feature. Regards, Robert Kisteleki RIPE NCC

1 0

MAT WG agenda @ RIPE 88
by Stephen Strowes 10 May '24

10 May '24

Hi all, RIPE 88 is on the horizon! The MAT working group session will take place on Tuesday 21 May at 16:00 CEST. If you are not already registered, information on how to attend the meeting is available here: https://ripe88.ripe.net/attend/register/ Our current agenda is: - 16:00: Welcome (WG chairs) - 16:05: 20 Years of Inferring Inter-domain Routing Policies (Savvas Kastanaki) - 16:25: WHOIS Right? An analysis of WHOIS and RDAP consistency (Simon Fernandez) - 16:40: Analysis of Usage Patterns in RIPE Atlas Measurements (Pavlos Sermpezis) - 16:55: WetLinks and Starlink on the Road: Exploring the Stationary and Mobile Performance of Starlink (Eric Lanfer) - 17:15: NCC Update (Robert Kisteleki) - 17:30 Session closes This agenda ought to be reflected on the meeting plan soon: https://ripe88.ripe.net/programme/meeting-plan/mat-wg/ Hope to see you there, either online or in-person! Cheers, -S, as WG co-chair

1 0

Call for presentations for MAT WG at RIPE 88
by Stephen Strowes 08 Apr '24

08 Apr '24

Hi all, RIPE88 is coming up: the meeting will take place 20 -- 24 May. Once again, we are seeking your presentations for the next MAT WG session, scheduled on Tuesday, 21 May! Presentations for the WG session are preferably 10-15min long. Please include in your proposal: * a title * a draft copy of your proposed presentation; an outline is okay! * a paragraph describing the topic and why it is of interest to the community. Interesting topics include (but are not limited to): recent measurement research which has an operational impact; recent operational work that may open avenues to research; projects, tools, or datasets that support either operations or research. Please submit your presentation proposal by **Monday 29 April** by emailing us at mat-wg-chairs at ripe.net. We will make our selections and post the agenda soon after. RIPE meetings are fully hybrid with sessions facilitated through meetecho. We encourage presentations from anywhere; to help us plan, we'd appreciate it if you can indicate whether you are likely to be online or on-site. Please ask if you have any questions regarding the setup on either side. Thanks! Nina, Massimo, Stephen, as WG co-chairs

1 1

RIS beacon ROA configuration error
by Martin Pels (RIPE NCC) 04 Mar '24

04 Mar '24

Dear all, As documented on [1], we operate several RIS Routing Beacons for RPKI. Due to a configuration error, two of the beacons were advertised with an incorrect RPKI status for several days. This concerns the "RPKI Unknown" beacons, which are the following prefixes: * 2001:7fb:ff03::/48 * 84.205.83.0/24 For both these prefixes, a ROA was created at 2024-02-27 7:55 UTC, turning these announcements into RPKI Valid. Upon receiving a report about this incorrect change we have removed the ROA again. This was done at 2024-03-04 11:31 UTC. Kind regards, Martin Pels RIPE NCC [1] https://ris.ripe.net/docs/routing-beacons/#special-beaconing-setups

1 0

Fast-paced RIS beacon changed schedule unexpectedly
by Ben Cartwright-Cox 07 Feb '24

07 Feb '24

Hey all, Did anyone know why the "Fast-paced beacons" that RIS provides has swapped schedules from Announcements at XX:10, XX:30, XX:50 Withdrawals at XX:00, XX:20, XX:40 to Announcements at XX:00, XX:20, XX:40 Withdrawals at XX:10, XX:30, XX:50 ? Sadly the internet archive does not archive https://ris.ripe.net/docs/routing-beacons/ page so I have no web page proof. However I did copy and paste the schedule into a code comment and as far as I can tell, the schedule "inverted" on 2024-02-01 at 09:10 UTC. Any ideas? Am I finally losing my mind? I see that there were changes scheduled to be made on February 1st 2024 ( https://www.ripe.net/ripe/mail/archives/ris-users/2023-December/000755.html ), But they did not mention changing the schedules of the fast paced beacons! Thanks Ben

2 1

RIPE87 meeting minutes
by Stephen Strowes 06 Feb '24

06 Feb '24

Hi all, Minutes from the WG session at RIPE 87 are now online at: https://www.ripe.net/community/wg/active-wg/mat/minutes/mat-working-group-m… Cheers, -S, as co-chair

1 0

RIS anchor/beacon changes
by Martin Pels (RIPE NCC) 02 Feb '24

02 Feb '24

Dear all, In the coming months we will be making several changes in the prefix advertisements by RIS Route Collectors. These changes were discussed previously on RIPE Labs[0]. January 2nd 2024 ---------------- The following BGP announcements will be disabled: * IPv4 anchor+beacon announcements on RRC04, RRC07, RRC10, RRC13, RRC14, RRC15, RRC16, RRC21 and RRC22 * IPv4 anycast failover simulation beacon (84.205.72.0/24) on RRC03 and RRC14 All IPv6 anchor+beacon announcements will remain. February 1st 2024 ----------------- We will be enabling the following new prefix advertisements: * A single anycast IPv4 and IPv6 anchor+beacon pair per RIR region, advertised from each RRC in this region. * An anycast IPv4 /25 and /28 anchor, advertised from one RRC per RIR region * An anycast IPv6 /56 and /64 anchor, advertised from one RRC per RIR region To accommodate these changes we will also modify the encoding used in the BGP AGGREGATOR attribute. For full details and an overview of all anchor and beacon prefixes, please refer to our updated documentation[1]. Kind regards, Martin Pels RIPE NCC [0] https://labs.ripe.net/author/emileaben/ris-beaconing-shining-a-light-on-bgp… [1] https://ris.ripe.net/docs/routing-beacons

1 1

Changes to the rpki archives on ftp.ripe.net
by Ties de Kock 26 Jan '24

26 Jan '24

Dear colleagues, As you may know, the RIPE NCC publishes daily RPKI dumps for all trust anchors on ftp.ripe.net/rpki. Today, we have made some changes to this longitudinal dataset. We have added: * The compressed JSON output of a validator (output.json.xz). We added this because it contains validated ASPA and BGPsec payloads. * A compressed version of the CSV file of ROAs (roas.csv.xz) * A xz compressed archive of the validated and unvalidated objects (repo.tar.xz) We made this change because it significantly reduces the size of the files. At this point, we do not plan to re-compress historic files. However, to realise the savings, we must stop producing the larger version at some point and clean up the "duplicate" files from the transition period. For now, we will create the old (roas.csv, repo.tar.gz) and new (roas.csv.xz, repo.tar.xz) side by side during a transition period. We plan to stop creating the old format after a transition period of at least a month, taking into account the feedback we receive. We will inform you when this happens. Ties de Kock Specialist Software Engineer RIPE NCC

1 1

Fwd: [SIG-NOC] Network Performance and Monitoring Workshop - 14 February 2024
by Vesna Manojlovic 24 Jan '24

24 Jan '24

Dear all, Kindly see the announcement below for the upcoming event on 14 February. Network Performance and Monitoring Workshop This Workshop is organised by the Monitoring task in the Network Development work package (WP6) of the GN5-1 project. Continuing from previous successful workshops, this new edition will bring together network operators, researchers and other members of the GÉANT and NREN community interested in network performance and monitoring, to present and discuss the future development of network performance and monitoring tools and platforms. Registrations and agenda: https://events.geant.org/event/1588/ For more information, please contact: network-performance-monitoring(a)lists.geant.org

2 1

Possible new RIS Beacon? (Alternating visible pair)
by Ben Cartwright-Cox 22 Jan '24

22 Jan '24

Hey everybody, On my seemingly never ending task to find all "stuck" BGP sessions, I feel like there is an interesting thing that could be done for the RIPE RIS Beacons, and that is a pair of prefixes that alternate between being visible and invisible (IE: unannounced). I looked at the current estate of beacon prefixes and couldn't find anything that would fit this use case already. This would be useful to be able to tell if a prefix or session has got a stuck prefix at that current moment in time, by being able to check the time and see if the presence of a prefix shouldn't be visible. In the interests of full disclosure this would be very useful for bgp.tools to instantly “spot check” BGP feeds to see if they have stuck prefixes or not. What does everybody think? This should "only" require two /24s and two /48s, and I think this would also help researchers see the severity of stuck sessions in a much more measurable way than having to wait for hours for the beacons to go on or off! (Apologies if this is not the right place for this kind of discussion, but there were previous mails about the beacons here, so I figured here was a good place) Cheers Ben

2 2

Open positions at HPI, Potsdam
by Vaibhav Bajpai 05 Jan '24

05 Jan '24

Dear colleagues, I am looking for Postdocs and PhD students to bootstrap a research group on data-intensive Internet computing at the Hasso Plattner Institute. These are full-time positions in the Berlin metropolitan area. We do systems research, and publish papers at the intersection of Internet measurements, security and privacy. The work place is in Potsdam, Germany. Interested candidates, please feel welcome to send me your application directly via E-mail (vaibhav.bajpai(a)hpi.de) Kind regards, -- Vaibhav ------------------------ Prof. Dr. Vaibhav Bajpai, www.vaibhavbajpai.com

1 0

RIPE NCC measurement data retention
by Robert Kisteleki 21 Dec '23

21 Dec '23

Dear all, We've just published a proposal about establishing principles around how the RIPE NCC retains and publishes Internet measurement data, specifically in RIS and RIPE Atlas: https://labs.ripe.net/author/kistel/ripe-ncc-measurement-data-retention-pri… We would be very happy to see discussions about this here on the mailing list, on the RIPE NCC Forum, or live at RIPE87. Regards, Robert Kisteleki RIPE NCC

8 7

RIPE Atlas, RIPEstat and RIS Quarterly Planning Q1 2024
by Adonis Stergiopoulos 20 Dec '23

20 Dec '23

Dear colleagues, The quarterly plans for RIPE Atlas, RIPEstat and RIS for Q1 2024 can now be found at: https://www.ripe.net/support/documentation/quarterly-planning <https://www.ripe.net/support/documentation/quarterly-planning> By sharing these plans with you, we want to inform you of the ongoing developments in the tools we operate and get your feedback on other work items you would like us to focus on. If you have any input on our plans, please let us know. Kind regards, Adonis Stergiopoulos Senior Marketing & Communications Officer RIPE NCC

1 0

The role of aggregators in RIPE Atlas
by Robert Kisteleki 11 Dec '23

11 Dec '23

Dear all, We've just published a proposal about recognising the role of "aggregators" in RIPE Atlas: https://labs.ripe.net/author/kistel/the-role-of-aggregators-in-ripe-atlas/ We would be very happy to see discussions about this here on the mailing list, on the RIPE NCC Forum, or live at RIPE87. Regards, Robert Kisteleki RIPE NCC

3 2

RIPE Labs post: Does The Internet Route Around Damage?
by Emile Aben 30 Nov '23

30 Nov '23

Dear colleagues, We analysed last week's AMS-IX outage from the perspective of RIPE Atlas, to shed some light on the question if the Internet routes around damage. Our analysis is here: https://labs.ripe.net/author/emileaben/does-the-internet-route-around-damag… Kind regards, Emile Aben RIPE NCC

3 4

2024 Internet Society Pulse Research Fellowship
by Amreesh Phokeer 29 Nov '23

29 Nov '23

Hi all, Are you interested in Internet measurement research and have a project or tool in mind that contributes to upholding an open, globally connected, secure, and trustworthy Internet? The call for applications is now open. More details here: https://pulse.internetsociety.org/fellowship If you want to learn more from 2023 Pulse fellows, join next week’s 2023 Pulse Research Fellowship Review webinar: https://isoc.zoom.us/webinar/register/WN_JL4H5rBIS82PjUVhIFhC5w Regards, -- Amreesh Phokeer

2 3

MAT Agenda - RIPE87
by Massimo Candela 28 Nov '23

28 Nov '23

Dear all, The MAT agenda for RIPE87 (Rome) is out: https://ripe87.ripe.net/programme/meeting-plan/mat-wg/ The session will take place in the main room on Tuesday, November 28 at 16:00 (UTC+1). We'll provide the streaming link. The current agenda is: * Measuring Internet Censorship with OONI (Arturo Filastò) * Where the !?*! Are the Packets Going? (Luca Sani) * Ah, This Is How Packets Get Here! Measuring Reverse Paths on the Public Internet (Valentin Heinrich) * ECN with QUIC: Challenges in the Wild? (Sander Constantin) * RIPE NCC Tools Update (Robert Kisteleki) See you in Rome! Ciao, Massimo (on behalf of the MAT chairs)

1 1