[lir-wg] AS Number Policy - continued

>>>   And defining the proper place for a registration is another "minor"
>>>   technical issue
>>>   (Q: portability of AS numbers amongst RIR service areas?).
>>>   But we could give it a try...
>>
>> Well, portably I guess is an issue anyway as the database refer to each
>> other (or do they only do that if there is no match? I am not really
>> into  the whois data...).
>
>   I am not aware of any (real) implementation of RPS-Dist yet...
>
>   So - no, not really (a nice research topic in itself!).
>   I was simply picking some "random" numbers here:

This ofcourse brings up a non-technical question. Should a AS owner be 
allowed to transfer it to another RIR? I don't see a reason why not 
(actually I see tons of reasons why they should). It will however create a 
real problem for the databases, and more or less eliminates the current 
"referal by allocation block" answers as we have today. But this is more a 
database implementation problem, or even a data registration problem. My 
vote would be to remove the "referal" objects (if they even are objects). 
There are clients that will search each of the databases anyway.

I am not really into the DB-WG work, or the history of this, but somehow I 
would assume that data mirroring is the  easiest (for some definition of 
easy) solution. Just like we have the -RIPE for contacts, I could see 
something simliare for AS-numbers. And yes - I do realise it's a bit more 
to it than that.




> aut-num:      AS1755
> as-name:      AS1755
> descr:        Ebone Transit Core
> import:       from AS1 accept  ANY
> import:       from AS109 accept AS109
> [ ...... ] #
> [ ...... ] # half a mile of routing policy and communities :-)
> [ ...... ] #
> mnt-by:       AS1755-MNT
> mnt-lower:    AS1755-MNT
> changed:      bart-apps at ebone.net 20020702
> source:       RIPE

Certain people should update their objects..:)


>   And while "we" RIPE DB do have a referral mechanism in place for
>   _domains_, .... ;-)
>
>   And I think both ARIN and APNIC are working on a ("central", similar to
>   the RIPE Region's) routing registry, but it may still be a long way...


WEll, routing registry is one thing - just "copying" the objects or at 
least the owner would be a great start. We don't need to copy all of the 
RPSL data neccessarily (although that would be a good step too...:) ), but 
at least the current data in the ARIN and APNIC AS objects.

- kurtis -