December 2023 - mat-wg - mailman.ripe.net

some thoughts on add-path and bmp at ripe/ris
by Randy Bush 25 Sep '25

25 Sep '25

i have some small thoughts on add-path and BMP in RIPE/RIS. this may hinder more than help, unfortunately. as a researcher, of course i would love a wider view into the AS graph and the views of as many ASs as possible. nom nom. but ... add-path, if not done very carefully, and documented in detail for each peer, will produce views i will not understand. it is analogous to not knowing what view a BGP peer gives RIS today. did it give me a full Nth view into peer X? is the path that of a peer, a customer, a provider? and add-path is worse because it prunes in configuration and vendor- dependent and otherwise unpredictable ways. and, as an operator if P is a RIS peer, and they give RIS BMP showing their input from their peers, upstreams, and customers, those peers, upstreams, and customers have not given thir consent to have their internals published! if they want to have RIS publish their internals, they would peer with RIS and choose what view they present. and, of course, the researcher does not know what view, peer, upstream, or customer P's BMP peer is giving them. same problem as above under add-path. randy

3 4

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

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