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
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
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
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
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
