[arin-ppml] Fwd: Draft Policy 2009-5: IPv6 Multiple Discrete Networks

Tue Jul 21 15:06:08 EDT 2009

Scott,

Thanks for the explanation.  

--celeste.

----- Original Message -----
From: Scott Leibrand <scottleibrand at gmail.com>
Date: Tuesday, July 21, 2009 11:48 am
Subject: Re: [arin-ppml] Fwd: Draft Policy 2009-5: IPv6 Multiple Discrete Networks
To: Celeste Anderson <celestea at usc.edu>
Cc: arin-ppml at arin.net

> It looks like that was carried over from the IPv4 Multiple Discrete 
> Networks policy (https://www.arin.net/policy/nrpm.html#four5).
> 
> If several smaller entities each need addresses for separate 
> networks, 
> they should apply independently as separate organizations.  If a 
> single 
> organization runs multiple discrete networks, they can't apply for 
> space 
> for each network independently, so this policy is needed to allow 
> them 
> to do so.
> 
> If this policy were applied to a consortium of smaller independent 
> entities, then such entities could create such a consortium for the 
> sole 
> purpose of getting around the ARIN fee structure.
> 
> -Scott
> 
> Celeste Anderson wrote:
> > I am curious as to why a consortium of smaller independent 
> entities is excluded from this policy.  I apologize if I missed 
> this in a previous discussion. 
> >
> > --celeste.
> >   
> >
> > ------------------------------------------------------------------
> ------
> >
> > Subject:
> > [arin-ppml] Draft Policy 2009-5: IPv6 Multiple Discrete Networks
> > From:
> > Member Services <info at arin.net>
> > Date:
> > Tue, 21 Jul 2009 10:45:48 -0400
> > To:
> > arin-ppml at arin.net
> >
> > To:
> > arin-ppml at arin.net
> >
> >
> > Draft Policy 2009-5
> > IPv6 Multiple Discrete Networks
> >
> > On 16 July 2009 the ARIN Advisory Council (AC) selected "Draft 
> Policy> 2009-5: IPv6 Multiple Discrete Networks" for adoption 
> discussion on the
> > PPML and at the Public Policy Meeting in Dearborn.
> >
> > The draft was developed by the AC from "Policy Proposal 84. IPv6
> > Multiple Discrete Networks". Per the Policy Development Process 
> the AC
> > submitted text to ARIN for a staff and legal assessment prior to
> > selection as a draft policy. After review of the assessment the 
> text was
> > revised (item 5 was added to the text). The assessment, along 
> with the
> > original text that was assessed, is located below the draft policy.
> >
> > You are encouraged to discuss Draft Policy 2009-5 on the PPML 
> prior to
> > the ARIN XXIV Public Policy Meeting. Both the discussion on the 
> list and
> > at the meeting will be used by the ARIN Advisory Council to 
> determine> the community consensus regarding adopting this as policy.
> >
> > Draft Policy 2009-5 is below and can be found at:
> > https://www.arin.net/policy/proposals/2009_5.html
> >
> > The ARIN Policy Development Process can be found at:
> > https://www.arin.net/policy/pdp.html
> >
> > Draft Policies and Proposals under discussion can be found at:
> > https://www.arin.net/policy/proposals/index.html
> >
> > Regards,
> >
> > Member Services
> > American Registry for Internet Numbers (ARIN)
> >
> >
> > ## * ##
> >
> >
> > Draft Policy 2009-5
> > IPv6 Multiple Discrete Networks
> >
> > Version/Date: 21 July 2009
> >
> > Policy statement:
> >
> > Organizations with multiple discrete IPv6 networks desiring to 
> request> new or additional address space under a single 
> Organization ID must meet
> > the following criteria:
> >
> >   1. The organization shall be a single entity and not a 
> consortium of
> >      smaller independent entities.
> >   2. The organization must have compelling criteria for creating
> >      discrete networks.
> >      Examples of a discrete network might include:
> >          * Regulatory restrictions for data transmission,
> >          * Geographic distance and diversity between networks,
> >          * Autonomous multihomed discrete networks.
> >   3. The organization must keep detailed records on how it has
> >      allocated space to each location, including the date of each
> >      allocation.
> >   4. The organization should notify ARIN at the time of the request
> >      their desire to apply this policy to their account.
> >   5. Requests for additional space:
> >
> >       a. Organization must specify on the application which discreet
> > network(s) the request applies to.
> >
> >       b. Each network will be judged against the existing 
> utilization> criteria specified in 6.5.2 as if it were a separate 
> organization,> rather than collectively as would be done for 
> requests outside of this
> > policy.
> >
> > Rationale:
> >
> > This proposed policy is suggested as NRPM 6.11.
> >
> > The policy is intended to provide parity between current IPv4 
> policy and
> > allow discrete network operators to obtain IPv6 space.
> >
> > Timetable for implementation: Immediately
> >
> >
> > #####
> >
> >
> > Staff Assessment
> >
> > Proposal: IPv6 Multiple Discrete Networks
> >
> > Date of Assessment: 7 July 2009
> >
> > Text assessed: 23 June 2009
> >
> > 1. Summary (Staff Understanding)
> >
> > This proposal would allow network operators to request /32s 
> (ISPs) or
> > /48s (End-users), or larger blocks as justified, for each of their
> > discrete networks. They would first need to meet current policy 
> criteria> for initial IPv6 allocations or assignments as described 
> in NRPM section
> > 6.5.1 or section 6.5.8 (as appropriate). The organization must have
> > compelling criteria to create discrete networks, must keep detailed
> > records, and must tell ARIN at the beginning of the request that 
> they> are applying under this policy.
> >
> > 2. Comments
> >
> > A. ARIN Staff Comments
> >
> >    * The proposal says that it is for requesting new or additional
> >      address space, but it does not include criteria for additional
> >      requests. This means that staff would likely have to revert to
> >      existing NRPM 6.5.2 criteria for requesting additional IPv6
> >      address space.
> >    * This policy creates no significant operational impact and would
> >      require very little staff time or effort to implement.
> >    * This policy could be utilized by network operators running
> >      multiple discrete networks who in the past, may have been 
> denied>      under current policy and/or forced to open multiple 
> accounts to
> >      accomplish their goals.
> >
> > B. ARIN General Counsel
> >
> >    * Counsel saw no issues with this proposal.
> >
> > 3. Resource Impact
> >
> > This policy would have minimal resource impact. It is estimated that
> > implementation would occur within three months after ratification 
> by the
> > ARIN Board of Trustees. The following would be needed in order to 
> > implement:
> >
> >    * Updated guidelines
> >    * Staff training
> >
> > 4. Proposal Text
> >
> > Proposal: IPv6 Multiple Discrete Networks
> >
> > Version/Date: 23 June 2009
> >
> > Organizations with multiple discrete IPv6 networks desiring to 
> request> new or additional address space under a single 
> Organization ID must meet
> > the following criteria:
> >
> > 1. The organization shall be a single entity and not a consortium of
> > smaller independent entities.
> >
> > 2. The organization must have compelling criteria for creating 
> discrete> networks. Examples of a discrete network might include:
> >
> > a. Regulatory restrictions for data transmission,
> >
> > b. Geographic distance and diversity between networks,
> >
> > c. Autonomous multihomed discrete networks.
> >
> > 3. The organization must keep detailed records on how it has 
> allocated> space to each location, including the date of each 
> allocation.>
> > 4. The organization should notify ARIN at the time of the request 
> their> desire to apply this policy to their account.
> >
> > Rationale:
> >
> > This proposed policy is suggested as NRPM 6.11. The policy is 
> intended> to provide parity between current IPv4 policy and allow 
> discrete network
> > operators to obtain IPv6 space.
> >
> >
> >
> >
> >
> >
> > _______________________________________________
> > PPML
> > You are receiving this message because you are subscribed to
> > the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
> > Unsubscribe or manage your mailing list subscription at:
> > http://lists.arin.net/mailman/listinfo/arin-ppml
> > Please contact info at arin.net if you experience any issues.
> > ------------------------------------------------------------------
> ------
> >
> > _______________________________________________
> > PPML
> > You are receiving this message because you are subscribed to
> > the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
> > Unsubscribe or manage your mailing list subscription at:
> > http://lists.arin.net/mailman/listinfo/arin-ppml
> > Please contact info at arin.net if you experience any issues.
> 