[ppml] 2005-1 status

Marshall Eubanks tme at multicasttech.com
Mon Jan 30 05:54:37 EST 2006


So, just to be clear, a site that is multihomed and in one physical  
location will get a
/44 ?

Regards
Marshall

On Jan 29, 2006, at 10:39 PM, Kevin Loch wrote:

> This is the latest draft for the revision of 2005-1. We
> are interested in feedback before we submit it as the
> formal revision.  For qualification purposes it is much
> closer to the original 2005-1.  Unlike any previous version
> assignment size is variable (explained in the justification
> section).
>
> Add new definition in section 6.2 of the NRPM:
>
>    6.2.10 Physical Location
>
>      A distinct physical location is identified by a unique street
>      address within an organization.  Different apartment, suite,  
> room,
>      unit or other similar identifiers at the same address for the  
> same
>      organization are not considered unique.
>
> Add new subsection in section 6.5 of the NRPM:
>
>    6.5.8. Direct assignments to large/multihomed end sites
>
>      6.5.8.1. To qualify for a direct assignment, an
>               organization must:
>
>        a) not be an IPv6 LIR;
>        b) meet at least ONE of the following requirements:
>
>          1) Have an IPv4 assignment or allocation directly from an  
> RIR,
>             the IANA or legacy registry
>          2) Qualify for an IPv4 assignment or allocation from ARIN  
> under
>             the IPv4 policy currently in effect
>          3) Be currently multihomed using IPv6 to two or more separate
>             LIR's using at least one /48 assigned to them by each LIR.
>
>        6.5.8.2. Direct assignment size to large/multihomed end sites
>
>          Organizations that meet the direct end site assignment  
> criteria
>          are eligible to receive a direct assignment.  The size of the
>          assignment is based on the number of distinct physical  
> locations
>          where the assignment will be used. The following table  
> will be
>          used to determine the assignment size:
>
>           +-------------------------+
>           | Locations  | Assignment |
>           +------------+------------+
>           |       1-13 |    /44     |
>           |     14-183 |    /40     |
>           |   184-2486 |    /36     |
>           | 2487-33688 |    /32     |
>           +------------+------------+
>
>           For organizations requesting an assignment shorter than / 
> 32 the
>           HD ratio method will be used.  For the HD ratio the  
> utilization
>           threshold is based on the numbmer of distinct physical
>           locations that will be using IPv6.  The HD ratio used  
> will be
>           the same as in section 6.5.2.2.
>
>         6.5.8.3. Subsequent Assignment Size
>
>            An organization may receive an additional assignment  
> when it
>            has grown to include enough distinct physical locations to
>            justify the larger assignment. Where possible, the  
> assignment
>            will be made from an adjacent address block.
>
> Justification:
>
> In IPv4 policy there are three major types of organizations that
> addresses are delegated to.
>
>    o ISP's receive allocations directly from ARIN or from other ISP's
>    o End Users receive assignments from ISP's
>    o "Large" and/or multihomed End Users may receive assignments  
> directly
>      from ARIN.
>
> The third category is currently missing from IPv6 policy and
> this is believed to be severely hindering deployment by those
> organizations. In IPv6 policy-speak:
>
>    o LIR's receive allocations directly from ARIN
>    o End Sites receive assignments from LIR's
>
> This policy proposes:
>
>    o "Large" and/or multihomed End Sites receive assignments directly
>      from ARIN.
>
> This  policy applies to organizations with networks that are
> large and/or complex enough to justify direct assignments.  Like their
> IPv4 counterparts they do not make assignments to external
> organizations. They instead assign space internally to their own
> facilities. Similarly to IPv4 These internal assignments are not
> submitted to ARIN via swip/rwhois.
>
> A IPv6 network is considered eligible if it is multihomed.
> For transition purposes an organization with an IPv4 assignment or
> allocation from an RIR (or the legacy RIR) is automatically considered
> elligible, regardless of whether they were considered an ISP or End
> User under IPv4 policy.  It is expected that the IPv6 only (non
> transition) requirements will be further refined as experience is
> gained.
>
> Since no /48's are assigned to external organizations, assignment size
> is determined solely by the number of distinct physical locations  
> to be
> served (based on the 1 /48 per POP precedent for LIR's).  It is  
> expected
> that almost all assignments will fall between /44-/32. That assignment
> range has been limited to nibble boundaries to simplify reverse dns.
> The assignment thresholds for that range were determined using an HD
> ratio of 0.94 in accordance with 2005-5.  A minimum assignment size of
> /44 is proposed to allow for some growth and flexibility of use for  
> the
> smallest applicants.  /32's are not assigned by default because it  
> would
> be unnecessarilly wasteful for the vast majority of assignments.
>
> - Kevin
> _______________________________________________
> PPML mailing list
> PPML at arin.net
> http://lists.arin.net/mailman/listinfo/ppml




More information about the ARIN-PPML mailing list