[ppml] Get you IPv6 Today, lets update the policy

[Klement, Charles]

Hello,

Are there currently any plans underway to accommodate the needs of
Multihomed enterprises?  If my understanding is correct (please correct me)
The hierarchical nature of IPv6 would not allow me to have multiple transit
providers.  This makes IPv6 a nonstarter for me.

Is there some loophole where I can qualify as a LIR and "sell" service to my
remote sites?

-charles

-----Original Message-----
From: Richard Jimmerson [mailto:richardj at arin.net] 
Sent: Tuesday, January 07, 2003 1:33 PM
To: john at chagres.net
Cc: ppml at arin.net
Subject: RE: [ppml] Get you IPv6 Today, lets update the policy


Hello John,

Thank you for your participation on the list.  I've provided some
clarification to some of the points you have raised, below.

> a) be an LIR

In the ARIN region the term ISP is used in exchange for LIR (Local
Internet Registry).

> So the first barrier is that you must be a ARIN customer

This is not the case.  In the ARIN region you do not first have to be a
customer of the RIR to request Internet addressing resources.

> and that requires you to have received a v4 block from ARIN
> directly.
> Thus you can not be a ISP that receives its space from its
> upstream.  
>
> All non-ARIN customers are hereby excluded, you fail requirement

This is not stated in the policy, and is not true.  It is not a
prerequisite to have obtained IPv4 address space from ARIN before
requesting IPv6 address space.  Organizations may request IPv6 address
space from ARIN regardless of their IPv4 registration history.

> In addition, research and development groups within end sites
> are excluded from receiving IPv6 space and thus can't develop
> cool new applications or services that make use of and would
> support the deployment of v6 space.

These organizations may be able to obtain address space from the 6bone.
ARIN also has a proposed policy under discussion, "Experimental Internet
Resource Allocations," that may be applicable in some of these cases.

> d) plan to deploy 200 /48 sites/customers
> You have to be able to provide 200 sites with v6 services within
> 2 years.  Chicken and Egg.  Can't start without having the space,
> can't get the space because you don't know if you can support 8.33
> new v6 connections per month.

In the policy document, item (d) is stated as such:

  d) have a plan for making at least 200 /48 assignments to 
     other organizations within two years.

ARIN does not scrutinize plans from requesting organizations for meeting
this requirement.  All we require is they state they have a plan for
making these assignments.

Although I do not foresee that ARIN will go after organizations two
years down the line and revoke their allocation if they were unable to
make assignments to 200 customers, I can understand how this statement
in the policy may cause some concern for requesting organizations.

If there is concern that this or other statements in the policy are
causing hesitation on the part of organizations who want to request IPv6
address space, perhaps it is time to consider changes in accordance with
the procedures set forth in the ARIN Internet Resource Policy Evaluation
Process.

Best Regards,

Richard Jimmerson
Director of Operations
American Registry for Internet Numbers (ARIN) 


> -----Original Message-----
> From: owner-ppml at arin.net [mailto:owner-ppml at arin.net] On 
> Behalf Of John M. Brown
> Sent: Tuesday, January 07, 2003 3:40 PM
> To: ppml at arin.net
> Subject: [ppml] Get you IPv6 Today, lets update the policy
> 
> 
> In the interest of fostering a more active deployment and
> development of IPv6 space within the ARIN region, I'm interested
> in hearing what people would want to see changed in the policy.
> 
> The ARIN region is behind other regions in deployment of v6, thus
> it seems to make sense that we need to mod the policy for our
> region.  Maybe continue an "early adopters" waiver for another 24
> months or something like that.
> 
> 
> Below is my understanding of 5.1.1 of the policy and I'm attempting
> to illustrate where it breaks with folks.
> 
> 
> It appears that Sec 5.1.1 states you must 
> 
> a) be an LIR
> b) not be an end-site
> c) plan to provide v6 connections via /48's
> d) plan to deploy 200 /48 sites/customers
> 
> In the ARIN region, an LIR would be the entity that receives
> space from ARIN and reassigns this to end-sites or other
> transit type sites.
> 
> ----------
> Requirement A.
> So the first barrier is that you must be a ARIN customer
> and that requires you to have received a v4 block from ARIN
> directly.
> 
> Thus you can not be a ISP that receives its space from its
> upstream.  
> 
> All non-ARIN customers are hereby excluded, you fail requirement
>   A.
> 
> ---------
> Requirement B.
> 
> You can not be an end-site.  Per section 2.9 of the policy
> definition of an End-Site, all web hosting companies are hereby
> excluded.  You might be able to argue that your web clients are the
> "end user", but from a routing point of view you don't provide
> transit to other sites.  2.9 seems to support this notion.
> 
> In addition, research and development groups within end sites
> are excluded from receiving IPv6 space and thus can't develop
> cool new applications or services that make use of and would
> support the deployment of v6 space.
> 
> Service companies are excluded in that they can't get space,
> learn how to use it, so that they can then help other clients
> (LIR's etc) spin up the protocol.
> 
> 
> ------------
> Requirement C.
> 
> Requires that you provide v6 connectivity to others..  Well i guess
> if you have the space, then you could provide space.
> 
> 
> ------------
> 
> Requirement D.
> 
> You have to be able to provide 200 sites with v6 services within
> 2 years.  Chicken and Egg.  Can't start without having the space,
> can't get the space because you don't know if you can support 8.33
> new v6 connections per month.
>