[sig-routing] Re: [JPNIC irr-coordinate 4] Re: About APNIC IRR

[Philip Smith <pfs@cisco.com>]

At 14:43 17/07/00 +0900, Kuniaki Kondo wrote:

>  Does this mean that APNIC and another NIRs as JPNIC, KERIN, TWNIC, etc,
>  has been mirroring with each other? If my understanding is correct,
>  at least, I could not search APNIC whois objects from JPNIC. And,
>  JPNIC has not had IRR server.

APNIC mirrors JPNIC/KRNIC/TWNIC. The latter do not mirror the APNIC 
database, as far as I'm aware.

>  Therefore, Users who would like to get
>  some whois information like a AS Object, need to search three times as
>  ARIN, APNIC and RIPE whois database.

Correct. This has always been so. Not hard, as the rule is basically you 
start at ARIN, and if they don't have it, they point to either of the other 
two registries. Has worked for me over the years.

>  So do I. I also think that we should concider the whois IRR databases as
>  separate entities.
>  But, the whois and IRR has similer information. Example is that
>  AS object which is registed in APNIC whois database, is included
>  as-in/as-out. I think that these information is for RR.

It can exist in an RR, yup. Why can't it be mandatory for allocation of an 
AS? I think it is a good thing - the profusion of ASes and large amount of 
multihoming is taking the Internet into uncharted waters when it comes to 
stability.

>  Actually, I think that IR is collecting and opening to the general
>  on viewpoing of maneging of the Internet number resouces.
>  If my understanding is correct, they would manage just administration
>  information, I think.
>
>  Recently, a part of the whois and IRR information have been duplicate,
>  like this.

Recently? as-in and as-out have always been APNIC policy. Recently to me is 
within the last few months. TBH, I wish that ARIN and RIPE NCC had similar 
policies, as we might have fewer vanishing ASes than we do today.

>  At first, I think that we should separete responsibility
>  between the whois and IRR.

What is your reasoning? Remember, I come from Europe where the RIPE NCC has 
been operating both a whois database and Routing Registry very 
successfully. Indeed, I'd strongly argue that the regional registry is the 
*only* place a public routing registry should be run. If that were the case 
today throughout the world, we would not be seeing the splinters we are 
seeing at the moment.

>   I think that this point is a big problem.
>   Information which is managed RR usually duplicate. And, a part of
>   these information has been not done maintenance. Therefore, these
>   information can not keep consistency.

How do you force ISPs to ensure the information is consistent? It's a good 
question. There is no magic switch we can pull which makes their network 
stop working due to bad registration information.

>   And, the number of current RR is too many, then when we would like
>   to collect the informatin of AS as AS Object from IRR, we can not
>   configure IRR on full mesh mirroring. And then, we cannot get
>   information enough.
>   Therefor, I think that for keeping consistency need responsible
>   organization for coordinating IRR.
>
>   In this meaning, I think that IR is the better organization
>   which is clarified management area and hierarchy of responsibility.

Sure.... Sounds like a good topic for the Routing SIG at the upcoming APNIC 
meeting in Brisbane.

philip
--

*              sig-routing:  APNIC SIG on IP routing technology and policy issues           *
* To unsubscribe: send "unsubscribe" to sig-routing-request@apnic.net *