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] Network failed [was re: Notification of RIPE Database changes]
- Previous message (by thread): [routing-wg] [training] RIPE NCC Training Courses October-December 2013
- Next message (by thread): [routing-wg] Network failed [was re: Notification of RIPE Database changes]
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Denis Walker
denis at ripe.net
Thu Aug 22 16:19:20 CEST 2013
Dear colleagues, Apologies for the delay in replying. It took me a while to find the time to write this article. I have written a RIPE Labs article explaining the background of how the RIPE Database works as an open, global Internet Routing Registry: https://labs.ripe.net/Members/denis/using-the-ripe-database-as-an-internet-routing-registry The article outlines the different scenarios, which explain how the reported situation occurred. I also raised a few questions in the article that I have heard whispered over the years. Perhaps it is time to review how this aspect of the database works. I also wrote an email to the Address Policy Working Group recently outlining the can/can't do list of actions regarding the aut-num object, which may be of interest in this discussion: http://www.ripe.net/ripe/mail/archives/address-policy-wg/2013-August/008174.html Regards Denis Walker Business Analyst RIPE NCC Database Team
- Previous message (by thread): [routing-wg] [training] RIPE NCC Training Courses October-December 2013
- Next message (by thread): [routing-wg] Network failed [was re: Notification of RIPE Database changes]
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]