APNIC Home APNIC Home
Info & FAQ |  Resource services |  Training |  Meetings |  Membership |  Documents |  Whois & Search |  Internet community

You're here:  Home  Mailing Lists wg-ipv6-guide 


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Wg-ipv6-guide] RE: Wg-ipv6-guide digest, Vol 1 #10 - 1 msg



All,

I have to say thank you to all.
We haven't finished some discussions, but I summarized a lot of comments
and advices up to now.
If there are some misunderstandings, point out, please.

Akira


------------------------------------------------------------------------
9 Subsequent Allocations

 - An example of a typical ISP.

  (1) 1st subsequent allocation
    A typical ISP receives /32 that is 65,536 * /48s as an initial
    allocation.
    If this ISP allocates or assigns 7,132 * /48s to it's customers and
    its POPs, this ISP has a right of the 1st subsequent allocation.
    
    7,132 is from the HD-Ratio table ( Policy : Appendix A )
    
   Example 
    assignments to POPs                   326 * /48
    assignments to end sites            6,500 * /48
    assignments through downstream ISP    306 * /48
    ------------------------------------------------
    total                               7,132 * /48s 


  (2) 2nd subsequent allocation
    This ISP receives additional /32 from an adjacent address block as
    the second allocation.  Now, this ISP has one /31 address block.
    If this ISP allocates or assigns 12,417 * /48s including the
    previous 7,132 * /48s to it's customers and its POPs, this ISP has a
    right of the 2nd subsequent allocation.

    12,417 is from the HD-Ratio table ( Policy : Appendix A )



 - Utilization in case of Sub-allocation
    Utilization is calculated based on the number of /48 assignments
    which are registered in the registry database(*) including
    /48 assignments through downstream ISPs. It is not based on the size
    of sub-allocations to the downstream ISPs.
    (*) needed clarified definition.

    If a sub-allocation is made to a down stream ISP, but assignments
    are not registered in the database, it will not considered utilized.
    e.g.) /40 sub-allocation is made to a downstream ISP. 2*/48 is
          assigned from this block. In this case, 2*/48 is considered as
          utilized, not /40(256*/48).
   
    So, LIRs should carefully consider and justify the sub-allocation
    size'. 

   <note> In IPv4, Sub-allocations to downstream ISPs are considered as
          assignment.



 - RIRs/NIRs do not request to LIRs for a Second Opinion Requests (SOR)
   for sub-allocations to downstream ISPs. 
   
   <note> In IPv4, To prevent LIRs from making unrealistic
          sub-allocations, RIRs/NIRs have a policy requesting for an SOR,
          so that RIRs/NIRs can see the details of the allocations.



 - RIRs temporarily reserve 8 * /32 adjacent address blocks for each
   organization. This space is worth /29.  But unless each organization
   obtains additional allocation, these spaces can be allocated to other
   organizations based on the Space Allocation System.
   http://xxx.xxx.apnic.net

------------------------------------------------------------------------



-- 
Akira Nakagawa <akira@pwd.ad.jp>