Re: [Wg-ipv6-guide] (ToC11) Database Registration

[(Tomohiro -INSTALLER-Fujisaki/$BF#:j(B $BCR9((B )<fujisaki@syce.net>]

Nakagawa-san,

 | I think a) is best.
 | It might be a workload for LIRs. But it's very clear in case of abuse.
 | And it may reduse time each time to trace whose address block it is.

I agree with this, but

 | about c) :  
 | If some LIRs don't register, people can't know if it isn't allocated
 | or it is allocated but not registered. So doing nothing is better than
 | doing by some organization.  b) is better than c) as my opinion.

I prefer c) rather than b). From a viewpoint of LIRs, I think it's
better to have a choice whether to demand downstream ISPs to manage
the delegation block or not. I think it's not a matter to complainants
to whom they contact if they can get proper response.

 | > <Allocations to downstream ISPs>
 | >  It is ambiguous in the policy document, and these are the
 | >  possibilities in implementation:
 | > 
 | >  a) All allocations to downstream ISPs must be registered in RIR/NIR
 | >     database 
 | >      e.g) If a /40 allocation is made to a downtream ISP, this will be
 | >           registered in the database
 | > 
 | >     Pros: Appropriate contact point(dowstream ISP) available on whois
 | >           database even when no assignments are made under that range
 | >     Cons: It will not be considered in calculating utilization, so no
 | >           strong motivation
 | >           It is rare case where allocations are made to downstream
 | >           ISPs, but no assignments are made/when registered
 | >           assignments do not have updated information
 | > 
 | >  b) Allocations to downstream ISPs should not be registered in RIR/NIR
 | >     database
 | >      e.g) Even if a /40 allocation is made to a downtream ISP, it will
 | >           not be registered in the database
 | >         
 | >     Pros: Reduces extra work for LIRs to register downstream allocations
 | >    
 | >     Cons: No appropriate point of contact for sub-allocated range when
 | >           allocations are made to downstream ISP, but no assignments
 | >           are registered
 | > 
 | >  c) It is upto LIRs to register allocations for downtream ISPs in the
 | >     RIR/NIR database
 | >     e.g) If a /40 allocation is made to a downtream ISP, it is upto an
 | >          LIR whether to register this sub-allocated range
 | > 
 | >     Pros: Allows flexibility. LIRs do not need to register
 | >           sub-allocations if they agree to be an abuse contact on
 | >           behalf of its downtream ISPs
 | > 
 | >     Cons: Inconsistency in database registration

--
Tomohiro Fujisaki, Nippon Telegraph and Telephone Coproration.