Hi guys
For the last 2 or 3 RIPE Meetings a conversation has started just before
the meeting and carried on during the meeting. It is the same
conversation about what to do with ROUTE objects in the RIPE Database
for non RIPE resources. The same possible solutions have been proposed
at each meeting. By the end of the meeting the same conclusion is
drawn...something needs to be done. Then.....silence....until just
before the next meeting when the cycle is repeated. In fact if you look
at the archive for the routing and DB WGs nothing has been said about
this on the mailing lists since the start of RIPE 71.
So are we going to have this same conversation just before RIPE 72 and
end with the same result? Or do you think we could break this cycle and
have a different conclusion...decide to do something instead of deciding
something needs to be done. Subtle but significant difference.
The simple solution I proposed that would solve the consequences of
having these ROUTE objects in the RIPE Database was on the table 18
months ago. Most of the software building blocks for it already exist in
the database software, so it could be implemented in a month or so. Even
if this is not the final solution, as a temporary fix it could be up and
running so easily and improve the confidence in the IRR.
cheers
denis
