- mat-wg - mailman.ripe.net

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