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] irr locking (Was: Bogon ASN Filter Policy)
- Previous message (by thread): [routing-wg] Bogon ASN Filter Policy
- Next message (by thread): [routing-wg] Bogon ASN Filter Policy
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Job Snijders
job at ntt.net
Wed Jun 8 12:02:01 CEST 2016
Hi Rafal, On Wed, Jun 08, 2016 at 07:00:54AM +0000, Rafal.Jankowski at thomsonreuters.com wrote: > And by the way could you please let me know what is the current status > of implementing so called "IRR Lockdown" in NTT? If I remember > correctly you planned in NTT to filter out route announcements for > prefixes present in RIPE but not having correct Route Registry in > RIPE. I'm just asking for my curiosity what is the current status for > that plan? We are facing two types of challenges: getting all impacted parties to move their route objects to the appropiate place. Secondly, from a software development perspective, it is somewhat difficult to bolt the irrlockdown features we want onto the existing IRRd daemon. We might postpone the irrlockdown until the IRRd roadmap is more clear. We've been toying with the idea to start from scratch in a modern language and create a backwards compatible, easy to extend, daemon which would then be "IRRd 4". Will keep you posted. Kind regards, Job
- Previous message (by thread): [routing-wg] Bogon ASN Filter Policy
- Next message (by thread): [routing-wg] Bogon ASN Filter Policy
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]