RIPE DB transition and RFC2725

Dear colleagues,

Yes, I know the deadline for transition comments is over, but
after studying RFC2725 we need a confirmation for our understanding.

RFC2725 defined the need for an "as-block" object for each related
"aut-num" object and an "inetnum" object for each related "route" object.

The assignment of AS blocks and IP space is managed by IANA.
 * http://www.isi.edu/in-notes/iana/assignments/as-numbers
 * http://www.isi.edu/in-notes/iana/assignments/ipv4-address-space

Does the new RIPE DB manage only "as-blocks" and "inetnums" which are
assigned to RIPE ?

 1/ And if I'm right, is it true that we can't store our ASes 702, 1270
    and a lot of routes (assigned to ARIN) in the new RIPE database ?

 2/ And is it true that we therefore can't set our route (assigned to RIPE)
    objects origin to our ASes ?

The solution for 1/ is moving to ARIN, but what might be the solution for 2/
?

You say a big ISP is anyway talking to multiple IRRs, but I think customers
who want to peer with these can't get complete information while using RIPE
DB only.


Cheers
Frank

-- 
Frank Bohnsack                       email  fb at de.uu.net
UUNET, A Worldcom Company            phone  +49 (0)231 972-1495
EMEA Access & Backbone Networks      fax    +49 (0)231 972-1188
Team Dortmund                        web    www.de.uu.net