- 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

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 09 May '24

09 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