Re: [arin-ppml] Policy proposal 2019-9
We use our 4.10 IPs for IPv6 facilitation including customers who don’t have IPv6 access because their ISPs are lazy and won’t deploy IPv6 so we assign them an IPv4 for Point to point access then they use our network for IPv6. Were also using them for border dual stack NATs, DNS, etc. We have a seperate need for IPv4 for our and our customers and clients that *do not* facilitate IPv6 deployment. We must use our 4.10 IPs as prescribed and cannot use them in an unrestricted manner as we wish. Thus, we remain on the waiting list for a /22. Sent from my iPhone > On Jul 31, 2019, at 22:23, John Curran wrote: > >> On 30 Jul 2019, at 8:37 PM, Michael Williams via ARIN-PPML >> wrote: >> >> I am against the policy as written. > > Michael - > > It would be helpful if you could elaborate a bit on your response, as the > ARIN Advisory Council is charged with noting “any specific concerns expressed > by a significant portion of the community” – without additional clarity as to > the reason for your opposition, it is not possible for them to know if the > issue is your particular concern, or perhaps more widely held. > > So: why are you against the policy as written? > > Thanks! > /John > > John Curran > President and CEO > American Registry for Internet Numbers > > > > ___ ARIN-PPML You are receiving this message because you are subscribed to the ARIN Public Policy Mailing List (ARIN-PPML@arin.net). Unsubscribe or manage your mailing list subscription at: https://lists.arin.net/mailman/listinfo/arin-ppml Please contact i...@arin.net if you experience any issues.
Re: [arin-ppml] Policy proposal 2019-9
On 30 Jul 2019, at 8:37 PM, Michael Williams via ARIN-PPML wrote: > > I am against the policy as written. Michael - It would be helpful if you could elaborate a bit on your response, as the ARIN Advisory Council is charged with noting “any specific concerns expressed by a significant portion of the community” – without additional clarity as to the reason for your opposition, it is not possible for them to know if the issue is your particular concern, or perhaps more widely held. So: why are you against the policy as written? Thanks! /John John Curran President and CEO American Registry for Internet Numbers ___ ARIN-PPML You are receiving this message because you are subscribed to the ARIN Public Policy Mailing List (ARIN-PPML@arin.net). Unsubscribe or manage your mailing list subscription at: https://lists.arin.net/mailman/listinfo/arin-ppml Please contact i...@arin.net if you experience any issues.
Re: [arin-ppml] Policy proposal 2019-9
I am against the policy as written. Sent from my iPhone On Jul 31, 2019, at 09:57, Rudolph Daniel wrote: I support this revised version of draft policy ARIN-2019-9 as written. RD On Tue, Jul 30, 2019, 15:50 wrote: > Send ARIN-PPML mailing list submissions to > arin-ppml@arin.net > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.arin.net/mailman/listinfo/arin-ppml > or, via email, send a message with subject or body 'help' to > arin-ppml-requ...@arin.net > > You can reach the person managing the list at > arin-ppml-ow...@arin.net > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of ARIN-PPML digest..." > > > Today's Topics: > >1. Re: Revised - Draft Policy ARIN-2019-9: Clarify Interactions > Between NRPM 4.10 IPv6 Transition Space Requests and NRPM 4.1.8.2 > Unmet Needs Requests (Kat Hunter) >2. Re: Revised - Draft Policy ARIN-2019-9: Clarify Interactions > Between NRPM 4.10 IPv6 Transition Space Requests and NRPM 4.1.8.2 > Unmet Needs Requests (Brian Jones) > > > -- > > Message: 1 > Date: Tue, 30 Jul 2019 13:33:07 -0400 > From: Kat Hunter > To: Brian Jones > Cc: ARIN-PPML > Subject: Re: [arin-ppml] Revised - Draft Policy ARIN-2019-9: Clarify > Interactions Between NRPM 4.10 IPv6 Transition Space Requests and > NRPM > 4.1.8.2 Unmet Needs Requests > Message-ID: > ucieaj6vq3yljrbkzswhqyn98whwza5gqi2zhzm2aax6...@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > All- Staff and legal review has been completed for 2019-9. Please take a > moment to review the comments. For those that supported this, do you still > support the policy given the staff notes. Additionally, we'd like to hear > from anyone that this may impact in a negative way. > > Policy: https://www.arin.net/participate/policy/drafts/2019_9/ > Staff and Legal Review > https://www.arin.net/participate/policy/drafts/2019_9/#slr > > "ARIN Staff Comments > > This policy could be implemented as written. Current policy is that any > organization on the waiting list that receives IPv4 addresses through a > transfer are removed from the waiting list, but those receiving an NRPM > 4.10 (Dedicated IPv4 Block to Facilitate IPv6 Deployment) assignment are > not removed from the waiting list. The proposed change would result those > organizations receiving an NRPM 4.10 assignment also being removed from the > waiting list. > > Staff notes that adding the ??or an allocation request fulfilled under > Section 4.10?? may be detrimental to some organizations, as address space > received per NRPM 4.10 must be used in a manner consistent with IPv6 > translation services and cannot be used for other purposes such as customer > assignments, shared hosting services, etc. > > Organizations need IPv4 address space to assign to their customers, and > many organizations will request a block from the Waiting List to be used > for their customer assignments but still need some IPv4 space for > deployment of IPv6 translation services as outlined in section NRPM 4.10. > Removing organizations from the Waiting List when they receive a NRPM 4.10 > assignment would hinder the existing IPv4 operations & growth of > organizations, and may provide a disincentive to IPv6 deployment." > > > > -Kat Hunter > > > On Mon, Jul 15, 2019 at 1:42 PM Brian Jones wrote: > > > I support this revised version of draft policy ARIN-2019-9 as written. > > > > Brian > > > > > > On Thu, May 23, 2019, 12:44 PM ARIN wrote: > > > >> The following has been revised: > >> > >> * Draft Policy ARIN-2019-9: Clarify Interactions Between NRPM 4.10 IPv6 > >> Transition Space Requests and NRPM 4.1.8.2 Unmet Needs Requests > >> > >> Revised text is below and can be found at: > >> https://www.arin.net/participate/policy/drafts/2019_9/ > >> > >> You are encouraged to discuss all Draft Policies on PPML. The AC will > >> evaluate the discussion in order to assess the conformance of this Draft > >> Policy with ARIN's Principles of Internet number resource policy as > >> stated in the Policy Development Process (PDP). Specifically, these > >> principles are: > >> > >> * Enabling Fair and Impartial Number Resource Administration > >> * Technically Sound > >> * Supported by the Community > >> > >> The PDP can be found at: > >> https://www.arin.net/participate/policy/pdp/ > >> > >> Draft Policies and Proposals under discussion can be found at: > >> https://www.arin.net/participate/policy/drafts/ > >> > >> Regards, > >> > >> Sean Hopkins > >> Policy Analyst > >> American Registry for Internet Numbers (ARIN) > >> > >> > >> > >> Draft Policy ARIN-2019-9: Clarify Interactions Between NRPM 4.10 IPv6 > >> Transition Space Requests and NRPM 4.1.8.2 Unmet Needs Requests > >> > >> Problem Statement: > >> > >> It has been observed that an organization requesting IPv4 resources > >> under
[arin-ppml] Policy proposal 2019-9
I support this revised version of draft policy ARIN-2019-9 as written. RD On Tue, Jul 30, 2019, 15:50 wrote: > Send ARIN-PPML mailing list submissions to > arin-ppml@arin.net > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.arin.net/mailman/listinfo/arin-ppml > or, via email, send a message with subject or body 'help' to > arin-ppml-requ...@arin.net > > You can reach the person managing the list at > arin-ppml-ow...@arin.net > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of ARIN-PPML digest..." > > > Today's Topics: > >1. Re: Revised - Draft Policy ARIN-2019-9: Clarify Interactions > Between NRPM 4.10 IPv6 Transition Space Requests and NRPM 4.1.8.2 > Unmet Needs Requests (Kat Hunter) >2. Re: Revised - Draft Policy ARIN-2019-9: Clarify Interactions > Between NRPM 4.10 IPv6 Transition Space Requests and NRPM 4.1.8.2 > Unmet Needs Requests (Brian Jones) > > > -- > > Message: 1 > Date: Tue, 30 Jul 2019 13:33:07 -0400 > From: Kat Hunter > To: Brian Jones > Cc: ARIN-PPML > Subject: Re: [arin-ppml] Revised - Draft Policy ARIN-2019-9: Clarify > Interactions Between NRPM 4.10 IPv6 Transition Space Requests and > NRPM > 4.1.8.2 Unmet Needs Requests > Message-ID: > ucieaj6vq3yljrbkzswhqyn98whwza5gqi2zhzm2aax6...@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > All- Staff and legal review has been completed for 2019-9. Please take a > moment to review the comments. For those that supported this, do you still > support the policy given the staff notes. Additionally, we'd like to hear > from anyone that this may impact in a negative way. > > Policy: https://www.arin.net/participate/policy/drafts/2019_9/ > Staff and Legal Review > https://www.arin.net/participate/policy/drafts/2019_9/#slr > > "ARIN Staff Comments > > This policy could be implemented as written. Current policy is that any > organization on the waiting list that receives IPv4 addresses through a > transfer are removed from the waiting list, but those receiving an NRPM > 4.10 (Dedicated IPv4 Block to Facilitate IPv6 Deployment) assignment are > not removed from the waiting list. The proposed change would result those > organizations receiving an NRPM 4.10 assignment also being removed from the > waiting list. > > Staff notes that adding the ??or an allocation request fulfilled under > Section 4.10?? may be detrimental to some organizations, as address space > received per NRPM 4.10 must be used in a manner consistent with IPv6 > translation services and cannot be used for other purposes such as customer > assignments, shared hosting services, etc. > > Organizations need IPv4 address space to assign to their customers, and > many organizations will request a block from the Waiting List to be used > for their customer assignments but still need some IPv4 space for > deployment of IPv6 translation services as outlined in section NRPM 4.10. > Removing organizations from the Waiting List when they receive a NRPM 4.10 > assignment would hinder the existing IPv4 operations & growth of > organizations, and may provide a disincentive to IPv6 deployment." > > > > -Kat Hunter > > > On Mon, Jul 15, 2019 at 1:42 PM Brian Jones wrote: > > > I support this revised version of draft policy ARIN-2019-9 as written. > > > > Brian > > > > > > On Thu, May 23, 2019, 12:44 PM ARIN wrote: > > > >> The following has been revised: > >> > >> * Draft Policy ARIN-2019-9: Clarify Interactions Between NRPM 4.10 IPv6 > >> Transition Space Requests and NRPM 4.1.8.2 Unmet Needs Requests > >> > >> Revised text is below and can be found at: > >> https://www.arin.net/participate/policy/drafts/2019_9/ > >> > >> You are encouraged to discuss all Draft Policies on PPML. The AC will > >> evaluate the discussion in order to assess the conformance of this Draft > >> Policy with ARIN's Principles of Internet number resource policy as > >> stated in the Policy Development Process (PDP). Specifically, these > >> principles are: > >> > >> * Enabling Fair and Impartial Number Resource Administration > >> * Technically Sound > >> * Supported by the Community > >> > >> The PDP can be found at: > >> https://www.arin.net/participate/policy/pdp/ > >> > >> Draft Policies and Proposals under discussion can be found at: > >> https://www.arin.net/participate/policy/drafts/ > >> > >> Regards, > >> > >> Sean Hopkins > >> Policy Analyst > >> American Registry for Internet Numbers (ARIN) > >> > >> > >> > >> Draft Policy ARIN-2019-9: Clarify Interactions Between NRPM 4.10 IPv6 > >> Transition Space Requests and NRPM 4.1.8.2 Unmet Needs Requests > >> > >> Problem Statement: > >> > >> It has been observed that an organization requesting IPv4 resources > >> under NRPM Section 4.10, Dedicated IPv4 Block To Facilitate IPv6 > >> Deployment, can also request similar or the
