- mat-wg - mailman.ripe.net

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

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

Two years of selective peering with RIS
by Michela Galante 23 Nov '23

23 Nov '23

Dear colleagues, We published an article on RIPE Labs where we talk about our RIS peering strategy of the last two years, what we've achieved so far, and why we've temporarily removed the peering form from our website: https://labs.ripe.net/author/emileaben/two-years-of-selective-peering-with-… We would love to hear your thoughts about it either here on this mailing list, in the Forum or live at RIPE 87. Best regards, Michela Galante RIPE NCC

1 0

PEARG: Guidelines for Performing Safe Measurement on the Internet
by Stephen Strowes 16 Nov '23

16 Nov '23

Hi, There is an open request on the IRTF's PEARG list, seeking feedback on a draft document, "Guidelines for Performing Safe Measurement on the Internet". The MAT WG has expertise and probably feedback to share. The request with appropriate pointers is here: https://mailarchive.ietf.org/arch/msg/pearg/-qGRRbBAZ2YAytwt4lpxVcQ7OZE/ Feedback on the draft is welcome either on their RG discuss list, or by filing issues directly against the git repo. Cheers, S.

1 0

Unauthenticated user access to RIPE Atlas
by Ben Cartwright-Cox 03 Nov '23

03 Nov '23

Hello everybody! I was wondering around what are the rules and views on “open user access” to RIPE Atlas ( as in non-authenticated users being able to make RIPE atlas measurements) I ask because as of this morning I noticed that hurricane electric’s bgp.he.net tool is now allowing users to make right atlas measurements without any authentication to RIPE Atlas, this was surprising to me as when I asked a NCC staff member at the last meeting in Berlin about doing something similar to this I was explicitly told that this would not be desired. I cannot remember who told me this ( and I don't have an easy way of finding out again ) but assuming this is allowed I will happily copy this for bgp.tools But I'd like to check with Atlas people before doing such a thing.

2 5

Call for presentations for MAT WG at RIPE87
by Stephen Strowes 24 Oct '23

24 Oct '23

Hi all, RIPE87 is coming up: the meeting will take place 27 November -- 1 December. Once again, we are seeking your presentations for the next MAT WG session, scheduled on Tuesday, 28 November! Presentations for the WG session are preferably 10-15min long. Please include in your proposal: * a title * a draft copy of your proposed presentation, even if just an outline * a paragraph describing the topic, and why the topic is of interest for 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 **Friday, 27 October** 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. For our planning, 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

new discussion list for discussing network neutrality/title ii issues rationally
by Dave Taht 11 Oct '23

11 Oct '23

With the return of the NN discussion and regulation in the USA as of Oct 19th... https://www.fcc.gov/document/fcc-chairwoman-rosenworcels-net-neutrality-rem… and especially with my lack of knowledge and understanding of pending EU regulation, I decided to start a good ole fashioned mailing list to try and sort it all out, which is up to nearly 200 members now. Sign up here: https://lists.bufferbloat.net/listinfo/nnagain I am especially interested in finding new blood of all sorts (engineers, lawyers, scientists, foss folk, and infrastructure folk) willing to discuss possible brighter futures for the internet (with us old farts via this archaic method. I considered trying mastodon but it was too complicated). New metrics for videoconferencing, as well as lower layer metrics like MTTR an MTBF are on my mind, as is finding ways to improve QoE for everyone, and de-crapification of the upper layers of the stack, as well as of the gear we buy. There is a separate NPRM going on for a new FCC CyberSecurity label, which I would like to see more teeth pushed into, honestly. My hope is, one day, we can provide good feedback into various overwhelmed government processes, as we did here, 7+ years ago. http://www.taht.net/~d/fcc_saner_software_practices.pdf PS - is anyone here participating in the renewed cybergeography project? -- Oct 30: https://netdevconf.info/0x17/news/the-maestro-and-the-music-bof.html Dave Täht CSO, LibreQos

1 0

RIPE Atlas, RIPEstat and RIS Quarterly Planning Q4 2023
by Robert Kisteleki 04 Oct '23

04 Oct '23

Dear colleagues, The quarterly plans for RIPE Atlas, RIPEstat and RIS can now be found at: https://www.ripe.net/support/documentation/quarterly-planning We hope that by providing these plans, we can better inform the community of the ongoing developments in the tools we operate and get feedback on our work. If you have any input on our plans or want to let us know what you would like to see us work on, please let us know. Kind regards, Robert Kisteleki Principal Engineer RIPE NCC

1 0