This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/routing-wg@ripe.net/
[routing-wg] TC x IRRd 4.2
- Previous message (by thread): [routing-wg] [anti-abuse-wg] AS8003 and U.S. Department of Defense routing
- Next message (by thread): [routing-wg] TC x IRRd 4.2
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Rubens Kuhl
rubensk at gmail.com
Wed Apr 28 03:18:32 CEST 2021
Hi all. TC IRR, an IRR operator focused on Brazilian networks, just changed to IRRd 4.2. The new version allowed TC to deploy RPKI validation (thanks NTT for sponsoring that development) and expose HTTPS endpoints for WHOIS and submission that we hope will foster innovation around the database. Every precaution was taken for this migration to be seamless for other IRR operators, including matching of serial numbers. Every IRR server that mirrored TC and supported -j status query was verified that it followed and still correctly follows database journals. But if anything appears broken, please let me know or e-mail db-admin at bgp.net.br. Thanks, Rubens -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/routing-wg/attachments/20210427/92ea88b4/attachment.html>
- Previous message (by thread): [routing-wg] [anti-abuse-wg] AS8003 and U.S. Department of Defense routing
- Next message (by thread): [routing-wg] TC x IRRd 4.2
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]