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/[email protected]/
[routing-wg] Registering in RIPE routes for prefixes in address space not managed by RIPE
- Previous message (by thread): [routing-wg] [training] RIPE NCC Training Courses January-March 2016
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Rafal.Jankowski at thomsonreuters.com
Rafal.Jankowski at thomsonreuters.com
Thu Dec 24 13:35:06 CET 2015
Hi, I can see there are some routes registered in RIPE for prefixes under administration of different RIRs. For example https://apps.db.ripe.net/search/lookup.html?source=ripe&key=23.59.96.0/20AS20940&type=route The 23/8 is an Arin address space. I'm wondering what is the recommended approach for registering routes related to non-RIPE prefixes: -to register them only in RIPE (because of the security mechanisms implemented for RIPE database objects?), -to register them in both RIPE and appropriate (according to IANA http://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml) RIR (probably not because of extra effort required and the risk of data inconsistency) -or register only in the RIR appropriate to the IANA address space and not to register in RIPE BTW I recently started using http://irrexplorer.nlnog.net and according to its logic route registered in RIPE for non RIPE prefix is OK (not perfect, but OK - displayed with green label). Are there any other tools that help to verify whois/irr data accuracy? Regards, Rafał ________________________________ This e-mail is for the sole use of the intended recipient and contains information that may be privileged and/or confidential. If you are not an intended recipient, please notify the sender by return e-mail and delete this e-mail and any attachments. Certain required legal entity disclosures can be accessed on our website.<http://site.thomsonreuters.com/site/disclosures/> -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/routing-wg/attachments/20151224/aaf13e1f/attachment.html>
- Previous message (by thread): [routing-wg] [training] RIPE NCC Training Courses January-March 2016
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]