Dear All, I was not at the recent RIPE Mtg and so may be behind the curve. I have been trying to see what is the status of the deployment of RPSLng, and testing the tools. My simple test worked OK, but I can't do more without having more objects to test against. These would need to be inserted by others. There was some traffic on the RPSLng list during the autumn, and near as I can make out there is still some dispute about some details of the syntax; I am not able to contribute meaningfully to that debate. I do note that the contentious items appeared to relate to the aut-num object. It seems to me we need: 1) Agreement 2) Deployment 3) Population 4) and for us, JunOS support The production database contains inet6num: objects. It does not contain or support route6: objects. Is anything in dispute about the route6: object? If not, could the production server be updated to support it, as a step forward. This would allow organisations to enter their route6: objects, and more extensive testing could then be done against these, using -f to keep the aut-num local. This would allow a bit of (2) and (3) in advance of complete (1). It would focus people's minds a bit. At present I have no lever to get customers to do (3) when any route6: objects they enter can only be in the test db. At the moment it feels like everyone is waiting for everyone else :-) Is this justified or am I completely at sea? Cheers, -- Tim