دریافت Outlook برای Android<https://aka.ms/AAb9ysg>
________________________________ فرستنده: [email protected] <[email protected]> تاریخ ارسال: چهارشنبه, ژانویهٔ 28, 2026 1:24:18 ب.ظ گیرنده: [email protected] <[email protected]> موضوع: mat-wg Digest, Vol 150, Issue 1 Send mat-wg mailing list submissions to [email protected] To subscribe or unsubscribe via email, send a message with subject or body 'help' to [email protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of mat-wg digest..." Today's Topics: 1. Re: RPKIViews 2021-2025 Amalgamations: a near-complete capture of the entire RPKI (Job Snijders) 2. What is up with PCH? (Malte Tashiro) 3. Re: What is up with PCH? (Thomas Holterbach) ---------------------------------------------------------------------- Message: 1 Date: Fri, 23 Jan 2026 14:11:02 +0000 From: Job Snijders <[email protected]> Subject: [mat-wg] Re: RPKIViews 2021-2025 Amalgamations: a near-complete capture of the entire RPKI To: [email protected] Message-ID: <[email protected]> Content-Type: text/plain; charset=us-ascii Dear all, A query on the dataset shows the following statistics for the 'rpki.ripe.net' hosted CA system, in 2025: object type count ROA 107,465 ASPA: 518 Certificate: 29,365 CRL 20,455,248 Manifest 20,455,248 It would be super cool to learn from RIPE NCC itself (as ground truth) how many CRLs/ROAs/Manifest objects the RIPE NCC issued according to their own logs & database. It would be quite helpful, because this way we can get sense of the 'completeness' of the RPKIViews amalgamations. I asked a few other RIRs... but it seems that the ones I asked didn't have issuance logs available. Does the RIPE NCC have an estimate how many ROAs/MFTs/CRLs/Certificates it issued in 2025 within the scope of 'rsync://rpki.ripe.net/repository'? Kind regards, Job On Fri, Jan 23, 2026 at 12:44:46PM +0000, Job Snijders wrote: > This might interest some of you: a (nearly?) complete capture of the raw > RPKI data of the last 5 years. > > Kind regards, > > Job > > ----- Forwarded message from Job Snijders <[email protected]> ----- > Date: Fri, 23 Jan 2026 10:43:37 +0000 > From: Job Snijders <[email protected]> > To: [email protected] > Subject: RPKIViews 2021-2025 Amalgamations: a near-complete capture of the > entire RPKI > > Dear all, > > The RPKI is an infrastructure which helps secure the global Internet > routing system. The RPKI is a distributed database. RPKIViews.org is a > global multi-perspective data collection initiative. I've normalized, > deduplicated, merged, sorted, and recompressed tens of terabytes of RPKI > data, resulting in handy datasets named the "RPKIViews Amalgamations". > These compact datasets together contain basically every ROA, ASPA, CRL, > Manifest, and Certificate that were issued in the last 5 years. > > RPKIViews 2021 Amalgamation, 46,507,392 RPKI objects > doi: https://doi.org/10.5281/zenodo.18082494 > compressed: 33.8 gigabytes (uncompressed: 78.1 gigabytes). > > RPKIViews 2022 Amalgamation, 51,850,445 RPKI objects > doi: https://doi.org/10.5281/zenodo.18327144 > compressed: 41.7 gigabytes (uncompressed: 110.2 gigabytes). > > RPKIViews 2023 Amalgamation, 57,286,485 RPKI objects > doi: https://doi.org/10.5281/zenodo.18327429 > compressed: 48.7 gigabytes (uncompressed: 111.8 gigabytes). > > RPKIViews 2024 Amalgamation, 56,586,149 RPKI objects > doi: https://doi.org/10.5281/zenodo.18328474 > compressed: 51.4 gigabytes (uncompressed: 115.5 gigabytes). > > RPKIViews 2025 Amalgamation, 61,524,413 RPKI objects > doi: https://doi.org/10.5281/zenodo.18332099 > compressed: 58.4 gigabytes (uncompressed: 145.0 gigabytes) > > The DER-encoded objects originally were fetched from publication servers > which were discovered using the Trust Anchor Locators of the following > Regional Internet Registries: AfriNIC, APNIC, ARIN, LACNIC, and RIPE > NCC. Not all objects contained within this dataset comply with the > requirements of modern day RPKI relying party implementations. > > The following file naming scheme is used for the tar archive members: > every filename is the URL-safe Base64-encoded SHA-256 message digest of > the object's ASN.1 encoded content. For performance reasons, the > directory hierarchy is constructed using the last few bytes of the > filename. The file's recorded last-modification timestamp is constructed > following the procedure outlined in RFC 9589. The tar achive adheres to > the IEEE Std 100.2 POSIX.2 "USTAR" interchange format and is compressed > in "--long -19" Zstandard (RFC 8878) form. Individual objects can be > inspected as JSON with "rpki-client -jf ./path/to/object" (filemode). > > Happy hacking & sleuthing! :-) > > Kind regards, > > Job > > ----- End forwarded message ----- ------------------------------ Message: 2 Date: Wed, 28 Jan 2026 16:38:26 +0900 From: Malte Tashiro <[email protected]> Subject: [mat-wg] What is up with PCH? To: [email protected] Message-ID: <[email protected]> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------zuZw50mLi4xbWhdAwFNcntbu" Hello there, does anyone by chance know what's up with PCH data? https://www.pch.net/resources/Routing_Data/ The page for the daily routing snapshots became unresponsive sometime in November last year and has been consistently serving error 503 recently. I've opened a ticket back then but got no response, so maybe somebody here knows the reason. Best, Malte -------------- next part -------------- A message part incompatible with plain text digests has been removed ... Name: OpenPGP_0x7D82498BEF2E08F8.asc Type: application/pgp-keys Size: 644 bytes Desc: OpenPGP public key -------------- next part -------------- A message part incompatible with plain text digests has been removed ... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 236 bytes Desc: OpenPGP digital signature ------------------------------ Message: 3 Date: Wed, 28 Jan 2026 10:53:53 +0100 From: Thomas Holterbach <[email protected]> Subject: [mat-wg] Re: What is up with PCH? To: Malte Tashiro <[email protected]> Cc: [email protected] Message-ID: <[email protected]> Content-Type: multipart/alternative; boundary="Apple-Mail=_4BC453FE-9E3A-4390-A9BA-6333BAF20732" Hello Malte, Good question. We reported the issue to them quite quickly in November, as we collect their data for bgproutes.io. They told us they had to change a server because many crawlers were downloading the data and overloading their infrastructure. It was apparently supposed to last only a few days, but it has now been several months. I hope they will be able to resume the platform, we really like it there! Best regards, Thomas > On 28 Jan 2026, at 08:38, Malte Tashiro via mat-wg <[email protected]> wrote: > > Hello there, > > does anyone by chance know what's up with PCH data? > https://www.pch.net/resources/Routing_Data/ > > The page for the daily routing snapshots became unresponsive sometime in > November last year and has been consistently serving error 503 recently. > I've opened a ticket back then but got no response, so maybe somebody here > knows the reason. > > Best, > Malte > <OpenPGP_0x7D82498BEF2E08F8.asc>----- > To unsubscribe from this mailing list or change your subscription options, > please visit: https://mailman.ripe.net/mailman3/lists/mat-wg.ripe.net/ > As we have migrated to Mailman 3, you will need to create an account with the > email matching your subscription before you can change your settings. > More details at: https://www.ripe.net/membership/mail/mailman-3-migration/ -------------- next part -------------- A message part incompatible with plain text digests has been removed ... Name: not available Type: text/html Size: 2072 bytes Desc: not available ------------------------------ Subject: Digest Footer ----- To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/mat-wg.ripe.net/ As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings. More details at: https://www.ripe.net/membership/mail/mailman-3-migration/ ------------------------------ End of mat-wg Digest, Vol 150, Issue 1 **************************************
----- To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/mat-wg.ripe.net/ As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings. More details at: https://www.ripe.net/membership/mail/mailman-3-migration/
