Hi, This is my first post to this list, so please forgive me if this is not the correct list for this topic. I've been looking at the route objects for the RFC3068 address space so that I could help AS8379 add their route object since they route this /24. route: 192.88.99.0/24 remarks: See RFC 3068 remarks: "An Anycast Prefix for 6to4 Relay Routers" remarks: Christian Huitema remarks: June 2001 We had much difficulty creating the newest object due to the previous recursive autnum authentication. With the help of Simon Leinen @Switch, Pekka Savola @FUnet and Robert Blechinger @Cybernet, we've changed the authorisation protecting the existing objects, to enable new members of the RFC3068 project to easily be able to enter their route objects for this /24 into the RIPE database. Each route object for 192.88.99.0/24 now includes the line :- mnt-routes: RFC3068-MNT This is a new maintainer that we've created, which currently has two authentication methods: an MD5-encrypted password and PGP. Once PGP is more widely used, we'll remove the MD5 password. When a new object needs to be created for this same /24 prefix, the originating AS need only pass the auth for this RFC3068-MNT and their own maintainer, rather than that of all the existing originating ASes. I've found this URL helpful to understand this process : http://www.ripe.net/ripencc/faq/database/route-creation-checks.html We wanted to let the IPv6 RIPE community know about this, so that when a new company joins the RFC3068 project, they know who to ask to get the MD5 password. The mntner object lists all our contact details. Please let us know if you have any questions! Best regards, Emma Emma Apted Peering Co-ordinator, Engineering & Standards --------------------------------------------------- PSINet Europe Intelligent e-business infrastructure Tel: +44 1223 577132 - Fax: +44 1223 577138 http://www.psineteurope.co.uk