<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif;font-size:x-small">Yes, that is my understanding.</div><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div style="text-align:left"><font size="1"><br></font></div><div align="center" style="text-align:center"><span style="font-family:Verdana,sans-serif"><font size="1"><hr size="1" width="100%" noshade align="center"></font></span></div><p style="margin-bottom:12pt"><b><span style="font-family:Arial,sans-serif;color:navy"><font size="1">Michael B. Williams</font></span></b><span style="font-family:Verdana,sans-serif"><font size="1"> <br>Glexia, Inc. - An IT Company<br>USA Direct: <span title="Call with Google Voice"><span title="Call with Google Voice"><span title="Call with Google Voice"><span title="Call with Google Voice"><span id="gc-number-408" class="gc-cs-link" title="Call with Google Voice">+1 978 477 6797</span></span></span></span></span><br>USA Toll Free: <span title="Call with Google Voice"><span title="Call with Google Voice"><span title="Call with Google Voice"><span title="Call with Google Voice"><span id="gc-number-409" class="gc-cs-link" title="Call with Google Voice">+1 800 675 0297</span></span></span></span></span> x101<br></font></span><span style="font-family:Verdana,sans-serif;font-size:x-small">AUS Direct: </span><span title="Call with Google Voice" style="font-family:Verdana,sans-serif;font-size:x-small"><span title="Call with Google Voice"><span title="Call with Google Voice"><span title="Call with Google Voice">+61 3 8594 2265<br></span></span></span></span><span style="font-family:Verdana,sans-serif;font-size:x-small">AUS Toll Free: </span><span title="Call with Google Voice" style="font-family:Verdana,sans-serif;font-size:x-small"><span title="Call with Google Voice"><span title="Call with Google Voice"><span title="Call with Google Voice">+61 1800 931 724</span></span></span></span><span style="font-family:Verdana,sans-serif;font-size:x-small"> x101<br></span><span style="font-size:x-small;font-family:Verdana,sans-serif">Fax: </span><span title="Call with Google Voice" style="font-size:x-small;font-family:Verdana,sans-serif"><span title="Call with Google Voice"><span title="Call with Google Voice"><span title="Call with Google Voice"><span><span id="gc-number-410" class="gc-cs-link" title="Call with Google Voice">+1.815-301-5570</span></span><br></span></span></span></span><span style="font-size:x-small;font-family:Verdana,sans-serif"><a href="mailto:Michael.Williams@glexia.com" title="Michael.Williams@glexia.com" style="color:rgb(17,85,204);font-size:x-small;font-family:Verdana,sans-serif" target="_blank">Michael.Williams@glexia.com</a><font color="#000080"><br></font></span><a href="https://www.glexia.com/" title="http://www.glexia.com/" style="font-size:x-small;font-family:Verdana,sans-serif;color:rgb(17,85,204)" target="_blank">https://www.glexia.com/</a><br><a href="https://www.glexia.com.au/" title="http://www.glexia.com/" style="font-size:x-small;font-family:Verdana,sans-serif;color:rgb(17,85,204)" target="_blank">https://www.glexia.com.au/</a><br></p><p style="margin-bottom:12pt"><span style="font-family:Verdana,sans-serif"><font size="1"><b><span style="color:navy">Legal Notice:</span></b><br>The information in this electronic mail message is the sender's confidential business and may be legally privileged. It is intended solely for the addressee(s). Access to this internet electronic mail message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. <br></font><br></span></p></div></div></div></div></div></div></div></div></div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Aug 5, 2019 at 1:47 PM Rudolph Daniel <<a href="mailto:rudi.daniel@gmail.com">rudi.daniel@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto"><div>Am I correct in thinking that org's requesting ipv4 resources, not stipulated for v6 deployment use, can use the allocation for either purpose?</div><div dir="auto">RD<br><br><div class="gmail_quote" dir="auto"><div dir="ltr" class="gmail_attr">On Tue, Jul 30, 2019, 20:38 <<a href="mailto:arin-ppml-request@arin.net" target="_blank">arin-ppml-request@arin.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Send ARIN-PPML mailing list submissions to<br>
<a href="mailto:arin-ppml@arin.net" rel="noreferrer" target="_blank">arin-ppml@arin.net</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://lists.arin.net/mailman/listinfo/arin-ppml" rel="noreferrer noreferrer" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:arin-ppml-request@arin.net" rel="noreferrer" target="_blank">arin-ppml-request@arin.net</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:arin-ppml-owner@arin.net" rel="noreferrer" target="_blank">arin-ppml-owner@arin.net</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of ARIN-PPML digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: Policy proposal 2019-9 (Michael Williams)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Tue, 30 Jul 2019 17:37:21 -0700<br>
From: Michael Williams <<a href="mailto:michael.williams@glexia.com" rel="noreferrer" target="_blank">michael.williams@glexia.com</a>><br>
To: Rudolph Daniel <<a href="mailto:rudi.daniel@gmail.com" rel="noreferrer" target="_blank">rudi.daniel@gmail.com</a>><br>
Cc: <a href="mailto:arin-ppml@arin.net" rel="noreferrer" target="_blank">arin-ppml@arin.net</a><br>
Subject: Re: [arin-ppml] Policy proposal 2019-9<br>
Message-ID:<br>
<CAGj=<a href="mailto:18Ffpb3jSpB-AgvjkwB1rHEYzC%2BCaNKuwhToEHzV83BR6Q@mail.gmail.com" rel="noreferrer" target="_blank">18Ffpb3jSpB-AgvjkwB1rHEYzC+CaNKuwhToEHzV83BR6Q@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
I am against the policy as written.<br>
<br>
Sent from my iPhone<br>
<br>
On Jul 31, 2019, at 09:57, Rudolph Daniel <<a href="mailto:rudi.daniel@gmail.com" rel="noreferrer" target="_blank">rudi.daniel@gmail.com</a>> wrote:<br>
<br>
I support this revised version of draft policy ARIN-2019-9 as written.<br>
RD<br>
<br>
On Tue, Jul 30, 2019, 15:50 <<a href="mailto:arin-ppml-request@arin.net" rel="noreferrer" target="_blank">arin-ppml-request@arin.net</a>> wrote:<br>
<br>
> Send ARIN-PPML mailing list submissions to<br>
> <a href="mailto:arin-ppml@arin.net" rel="noreferrer" target="_blank">arin-ppml@arin.net</a><br>
><br>
> To subscribe or unsubscribe via the World Wide Web, visit<br>
> <a href="https://lists.arin.net/mailman/listinfo/arin-ppml" rel="noreferrer noreferrer" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
> or, via email, send a message with subject or body 'help' to<br>
> <a href="mailto:arin-ppml-request@arin.net" rel="noreferrer" target="_blank">arin-ppml-request@arin.net</a><br>
><br>
> You can reach the person managing the list at<br>
> <a href="mailto:arin-ppml-owner@arin.net" rel="noreferrer" target="_blank">arin-ppml-owner@arin.net</a><br>
><br>
> When replying, please edit your Subject line so it is more specific<br>
> than "Re: Contents of ARIN-PPML digest..."<br>
><br>
><br>
> Today's Topics:<br>
><br>
> 1. Re: Revised - Draft Policy ARIN-2019-9: Clarify Interactions<br>
> Between NRPM 4.10 IPv6 Transition Space Requests and NRPM 4.1.8.2<br>
> Unmet Needs Requests (Kat Hunter)<br>
> 2. Re: Revised - Draft Policy ARIN-2019-9: Clarify Interactions<br>
> Between NRPM 4.10 IPv6 Transition Space Requests and NRPM 4.1.8.2<br>
> Unmet Needs Requests (Brian Jones)<br>
><br>
><br>
> ----------------------------------------------------------------------<br>
><br>
> Message: 1<br>
> Date: Tue, 30 Jul 2019 13:33:07 -0400<br>
> From: Kat Hunter <<a href="mailto:takokat81@gmail.com" rel="noreferrer" target="_blank">takokat81@gmail.com</a>><br>
> To: Brian Jones <<a href="mailto:bjones@vt.edu" rel="noreferrer" target="_blank">bjones@vt.edu</a>><br>
> Cc: ARIN-PPML <<a href="mailto:arin-ppml@arin.net" rel="noreferrer" target="_blank">arin-ppml@arin.net</a>><br>
> Subject: Re: [arin-ppml] Revised - Draft Policy ARIN-2019-9: Clarify<br>
> Interactions Between NRPM 4.10 IPv6 Transition Space Requests and<br>
> NRPM<br>
> 4.1.8.2 Unmet Needs Requests<br>
> Message-ID:<br>
> <CAC=<br>
> <a href="mailto:UcieAJ6Vq3YLjRbKzSwHQYN98wHWZA5gQi2Zhzm2aAx6%2BBw@mail.gmail.com" rel="noreferrer" target="_blank">UcieAJ6Vq3YLjRbKzSwHQYN98wHWZA5gQi2Zhzm2aAx6+Bw@mail.gmail.com</a>><br>
> Content-Type: text/plain; charset="utf-8"<br>
><br>
> All- Staff and legal review has been completed for 2019-9. Please take a<br>
> moment to review the comments. For those that supported this, do you still<br>
> support the policy given the staff notes. Additionally, we'd like to hear<br>
> from anyone that this may impact in a negative way.<br>
><br>
> Policy: <a href="https://www.arin.net/participate/policy/drafts/2019_9/" rel="noreferrer noreferrer" target="_blank">https://www.arin.net/participate/policy/drafts/2019_9/</a><br>
> Staff and Legal Review<br>
> <a href="https://www.arin.net/participate/policy/drafts/2019_9/#slr" rel="noreferrer noreferrer" target="_blank">https://www.arin.net/participate/policy/drafts/2019_9/#slr</a><br>
><br>
> "ARIN Staff Comments<br>
><br>
> This policy could be implemented as written. Current policy is that any<br>
> organization on the waiting list that receives IPv4 addresses through a<br>
> transfer are removed from the waiting list, but those receiving an NRPM<br>
> 4.10 (Dedicated IPv4 Block to Facilitate IPv6 Deployment) assignment are<br>
> not removed from the waiting list. The proposed change would result those<br>
> organizations receiving an NRPM 4.10 assignment also being removed from the<br>
> waiting list.<br>
><br>
> Staff notes that adding the ??or an allocation request fulfilled under<br>
> Section 4.10?? may be detrimental to some organizations, as address space<br>
> received per NRPM 4.10 must be used in a manner consistent with IPv6<br>
> translation services and cannot be used for other purposes such as customer<br>
> assignments, shared hosting services, etc.<br>
><br>
> Organizations need IPv4 address space to assign to their customers, and<br>
> many organizations will request a block from the Waiting List to be used<br>
> for their customer assignments but still need some IPv4 space for<br>
> deployment of IPv6 translation services as outlined in section NRPM 4.10.<br>
> Removing organizations from the Waiting List when they receive a NRPM 4.10<br>
> assignment would hinder the existing IPv4 operations & growth of<br>
> organizations, and may provide a disincentive to IPv6 deployment."<br>
><br>
><br>
><br>
> -Kat Hunter<br>
><br>
><br>
> On Mon, Jul 15, 2019 at 1:42 PM Brian Jones <<a href="mailto:bjones@vt.edu" rel="noreferrer" target="_blank">bjones@vt.edu</a>> wrote:<br>
><br>
> > I support this revised version of draft policy ARIN-2019-9 as written.<br>
> ><br>
> > Brian<br>
> ><br>
> ><br>
> > On Thu, May 23, 2019, 12:44 PM ARIN <<a href="mailto:info@arin.net" rel="noreferrer" target="_blank">info@arin.net</a>> wrote:<br>
> ><br>
> >> The following has been revised:<br>
> >><br>
> >> * Draft Policy ARIN-2019-9: Clarify Interactions Between NRPM 4.10 IPv6<br>
> >> Transition Space Requests and NRPM 4.1.8.2 Unmet Needs Requests<br>
> >><br>
> >> Revised text is below and can be found at:<br>
> >> <a href="https://www.arin.net/participate/policy/drafts/2019_9/" rel="noreferrer noreferrer" target="_blank">https://www.arin.net/participate/policy/drafts/2019_9/</a><br>
> >><br>
> >> You are encouraged to discuss all Draft Policies on PPML. The AC will<br>
> >> evaluate the discussion in order to assess the conformance of this Draft<br>
> >> Policy with ARIN's Principles of Internet number resource policy as<br>
> >> stated in the Policy Development Process (PDP). Specifically, these<br>
> >> principles are:<br>
> >><br>
> >> * Enabling Fair and Impartial Number Resource Administration<br>
> >> * Technically Sound<br>
> >> * Supported by the Community<br>
> >><br>
> >> The PDP can be found at:<br>
> >> <a href="https://www.arin.net/participate/policy/pdp/" rel="noreferrer noreferrer" target="_blank">https://www.arin.net/participate/policy/pdp/</a><br>
> >><br>
> >> Draft Policies and Proposals under discussion can be found at:<br>
> >> <a href="https://www.arin.net/participate/policy/drafts/" rel="noreferrer noreferrer" target="_blank">https://www.arin.net/participate/policy/drafts/</a><br>
> >><br>
> >> Regards,<br>
> >><br>
> >> Sean Hopkins<br>
> >> Policy Analyst<br>
> >> American Registry for Internet Numbers (ARIN)<br>
> >><br>
> >><br>
> >><br>
> >> Draft Policy ARIN-2019-9: Clarify Interactions Between NRPM 4.10 IPv6<br>
> >> Transition Space Requests and NRPM 4.1.8.2 Unmet Needs Requests<br>
> >><br>
> >> Problem Statement:<br>
> >><br>
> >> It has been observed that an organization requesting IPv4 resources<br>
> >> under NRPM Section 4.10, Dedicated IPv4 Block To Facilitate IPv6<br>
> >> Deployment, can also request similar or the same resources under Section<br>
> >> 4.2.1.8, Unmet Needs. This proposal aims to remove this potential for<br>
> >> duplicate requests under these sections.<br>
> >><br>
> >> Policy Statement:<br>
> >><br>
> >> Section 4.1.8.2, Unmet Needs:<br>
> >><br>
> >> Current language: Any requests met through a transfer will be considered<br>
> >> fulfilled and removed from the waiting list.<br>
> >><br>
> >> Proposed language:<br>
> >><br>
> >> Any requests met through a transfer or an allocation request fulfilled<br>
> >> under Section 4.10 will be considered fulfilled and removed from the<br>
> >> waiting list.<br>
> >><br>
> >> Timetable for Implementation: Immediate<br>
> >><br>
> >> Anything Else:<br>
> >><br>
> >> Currently, organizations can receive no more than a /24 at a time under<br>
> >> Section 4.10. However, Proposal ARIN-PROP-266, submitted by Chris Tacit<br>
> >> and myself, could potentially allow an org to receive up to a /21 under<br>
> >> that section, widening the potential for abuse by ?double-dipping?<br>
> >> waiting list and transition space requests. As such, this proposal<br>
> >> should be considered in that context.<br>
> >> _______________________________________________<br>
> >> ARIN-PPML<br>
> >> You are receiving this message because you are subscribed to<br>
> >> the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" rel="noreferrer" target="_blank">ARIN-PPML@arin.net</a>).<br>
> >> Unsubscribe or manage your mailing list subscription at:<br>
> >> <a href="https://lists.arin.net/mailman/listinfo/arin-ppml" rel="noreferrer noreferrer" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
> >> Please contact <a href="mailto:info@arin.net" rel="noreferrer" target="_blank">info@arin.net</a> if you experience any issues.<br>
> >><br>
> > _______________________________________________<br>
> > ARIN-PPML<br>
> > You are receiving this message because you are subscribed to<br>
> > the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" rel="noreferrer" target="_blank">ARIN-PPML@arin.net</a>).<br>
> > Unsubscribe or manage your mailing list subscription at:<br>
> > <a href="https://lists.arin.net/mailman/listinfo/arin-ppml" rel="noreferrer noreferrer" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
> > Please contact <a href="mailto:info@arin.net" rel="noreferrer" target="_blank">info@arin.net</a> if you experience any issues.<br>
> ><br>
> -------------- next part --------------<br>
> An HTML attachment was scrubbed...<br>
> URL: <<br>
> <a href="https://lists.arin.net/pipermail/arin-ppml/attachments/20190730/92058f5f/attachment-0001.htm" rel="noreferrer noreferrer" target="_blank">https://lists.arin.net/pipermail/arin-ppml/attachments/20190730/92058f5f/attachment-0001.htm</a><br>
> ><br>
><br>
> ------------------------------<br>
><br>
> Message: 2<br>
> Date: Tue, 30 Jul 2019 15:49:56 -0400<br>
> From: Brian Jones <<a href="mailto:bjones@vt.edu" rel="noreferrer" target="_blank">bjones@vt.edu</a>><br>
> To: Kat Hunter <<a href="mailto:takokat81@gmail.com" rel="noreferrer" target="_blank">takokat81@gmail.com</a>>, ARIN-PPML <<a href="mailto:arin-ppml@arin.net" rel="noreferrer" target="_blank">arin-ppml@arin.net</a>><br>
> Subject: Re: [arin-ppml] Revised - Draft Policy ARIN-2019-9: Clarify<br>
> Interactions Between NRPM 4.10 IPv6 Transition Space Requests and<br>
> NRPM<br>
> 4.1.8.2 Unmet Needs Requests<br>
> Message-ID: <<a href="mailto:EEC96299-415D-46F5-A742-13C7DE06F316@vt.edu" rel="noreferrer" target="_blank">EEC96299-415D-46F5-A742-13C7DE06F316@vt.edu</a>><br>
> Content-Type: text/plain; charset="utf-8"<br>
><br>
> With the clarification that organizations will be removed from the waiting<br>
> list if they receive an allocation for facilitating their IPv6 deployment,<br>
> I no longer support this proposal for the reasons outlined by the ARIN<br>
> staff below. My organization will not be impacted by this but I can<br>
> understand where some could be detrimentally effected by this change.<br>
> Receiving an allocation for deploying IPv6 should not be tied to the<br>
> waiting list for a regular IPv4 assignment IMO.<br>
><br>
> --<br>
> Brian E Jones, CSP-SM, CSP-PO<br>
> NI&S Virginia Tech<br>
> <a href="mailto:bjones@vt.edu" rel="noreferrer" target="_blank">bjones@vt.edu</a><br>
><br>
> > On Jul 30, 2019, at 1:33 PM, Kat Hunter <<a href="mailto:takokat81@gmail.com" rel="noreferrer" target="_blank">takokat81@gmail.com</a>> wrote:<br>
> ><br>
> > All- Staff and legal review has been completed for 2019-9. Please take a<br>
> moment to review the comments. For those that supported this, do you still<br>
> support the policy given the staff notes. Additionally, we'd like to hear<br>
> from anyone that this may impact in a negative way.<br>
> ><br>
> > Policy: <a href="https://www.arin.net/participate/policy/drafts/2019_9/" rel="noreferrer noreferrer" target="_blank">https://www.arin.net/participate/policy/drafts/2019_9/</a> <<br>
> <a href="https://www.arin.net/participate/policy/drafts/2019_9/" rel="noreferrer noreferrer" target="_blank">https://www.arin.net/participate/policy/drafts/2019_9/</a>><br>
> > Staff and Legal Review<br>
> <a href="https://www.arin.net/participate/policy/drafts/2019_9/#slr" rel="noreferrer noreferrer" target="_blank">https://www.arin.net/participate/policy/drafts/2019_9/#slr</a> <<br>
> <a href="https://www.arin.net/participate/policy/drafts/2019_9/#slr" rel="noreferrer noreferrer" target="_blank">https://www.arin.net/participate/policy/drafts/2019_9/#slr</a>><br>
> ><br>
> > "ARIN Staff Comments<br>
> ><br>
> > This policy could be implemented as written. Current policy is that any<br>
> organization on the waiting list that receives IPv4 addresses through a<br>
> transfer are removed from the waiting list, but those receiving an NRPM<br>
> 4.10 (Dedicated IPv4 Block to Facilitate IPv6 Deployment) assignment are<br>
> not removed from the waiting list. The proposed change would result those<br>
> organizations receiving an NRPM 4.10 assignment also being removed from the<br>
> waiting list.<br>
> ><br>
> > Staff notes that adding the ??or an allocation request fulfilled under<br>
> Section 4.10?? may be detrimental to some organizations, as address space<br>
> received per NRPM 4.10 must be used in a manner consistent with IPv6<br>
> translation services and cannot be used for other purposes such as customer<br>
> assignments, shared hosting services, etc.<br>
> ><br>
> > Organizations need IPv4 address space to assign to their customers, and<br>
> many organizations will request a block from the Waiting List to be used<br>
> for their customer assignments but still need some IPv4 space for<br>
> deployment of IPv6 translation services as outlined in section NRPM 4.10.<br>
> Removing organizations from the Waiting List when they receive a NRPM 4.10<br>
> assignment would hinder the existing IPv4 operations & growth of<br>
> organizations, and may provide a disincentive to IPv6 deployment."<br>
> ><br>
> ><br>
> ><br>
> > -Kat Hunter<br>
> ><br>
> ><br>
> > On Mon, Jul 15, 2019 at 1:42 PM Brian Jones <<a href="mailto:bjones@vt.edu" rel="noreferrer" target="_blank">bjones@vt.edu</a> <mailto:<br>
> <a href="mailto:bjones@vt.edu" rel="noreferrer" target="_blank">bjones@vt.edu</a>>> wrote:<br>
> > I support this revised version of draft policy ARIN-2019-9 as written.<br>
> ><br>
> > Brian<br>
> ><br>
> ><br>
> > On Thu, May 23, 2019, 12:44 PM ARIN <<a href="mailto:info@arin.net" rel="noreferrer" target="_blank">info@arin.net</a> <mailto:<a href="mailto:info@arin.net" rel="noreferrer" target="_blank">info@arin.net</a>>><br>
> wrote:<br>
> > The following has been revised:<br>
> ><br>
> > * Draft Policy ARIN-2019-9: Clarify Interactions Between NRPM 4.10 IPv6<br>
> > Transition Space Requests and NRPM 4.1.8.2 Unmet Needs Requests<br>
> ><br>
> > Revised text is below and can be found at:<br>
> > <a href="https://www.arin.net/participate/policy/drafts/2019_9/" rel="noreferrer noreferrer" target="_blank">https://www.arin.net/participate/policy/drafts/2019_9/</a> <<br>
> <a href="https://www.arin.net/participate/policy/drafts/2019_9/" rel="noreferrer noreferrer" target="_blank">https://www.arin.net/participate/policy/drafts/2019_9/</a>><br>
> ><br>
> > You are encouraged to discuss all Draft Policies on PPML. The AC will<br>
> > evaluate the discussion in order to assess the conformance of this Draft<br>
> > Policy with ARIN's Principles of Internet number resource policy as<br>
> > stated in the Policy Development Process (PDP). Specifically, these<br>
> > principles are:<br>
> ><br>
> > * Enabling Fair and Impartial Number Resource Administration<br>
> > * Technically Sound<br>
> > * Supported by the Community<br>
> ><br>
> > The PDP can be found at:<br>
> > <a href="https://www.arin.net/participate/policy/pdp/" rel="noreferrer noreferrer" target="_blank">https://www.arin.net/participate/policy/pdp/</a> <<br>
> <a href="https://www.arin.net/participate/policy/pdp/" rel="noreferrer noreferrer" target="_blank">https://www.arin.net/participate/policy/pdp/</a>><br>
> ><br>
> > Draft Policies and Proposals under discussion can be found at:<br>
> > <a href="https://www.arin.net/participate/policy/drafts/" rel="noreferrer noreferrer" target="_blank">https://www.arin.net/participate/policy/drafts/</a> <<br>
> <a href="https://www.arin.net/participate/policy/drafts/" rel="noreferrer noreferrer" target="_blank">https://www.arin.net/participate/policy/drafts/</a>><br>
> ><br>
> > Regards,<br>
> ><br>
> > Sean Hopkins<br>
> > Policy Analyst<br>
> > American Registry for Internet Numbers (ARIN)<br>
> ><br>
> ><br>
> ><br>
> > Draft Policy ARIN-2019-9: Clarify Interactions Between NRPM 4.10 IPv6<br>
> > Transition Space Requests and NRPM 4.1.8.2 Unmet Needs Requests<br>
> ><br>
> > Problem Statement:<br>
> ><br>
> > It has been observed that an organization requesting IPv4 resources<br>
> > under NRPM Section 4.10, Dedicated IPv4 Block To Facilitate IPv6<br>
> > Deployment, can also request similar or the same resources under Section<br>
> > 4.2.1.8, Unmet Needs. This proposal aims to remove this potential for<br>
> > duplicate requests under these sections.<br>
> ><br>
> > Policy Statement:<br>
> ><br>
> > Section 4.1.8.2, Unmet Needs:<br>
> ><br>
> > Current language: Any requests met through a transfer will be considered<br>
> > fulfilled and removed from the waiting list.<br>
> ><br>
> > Proposed language:<br>
> ><br>
> > Any requests met through a transfer or an allocation request fulfilled<br>
> > under Section 4.10 will be considered fulfilled and removed from the<br>
> > waiting list.<br>
> ><br>
> > Timetable for Implementation: Immediate<br>
> ><br>
> > Anything Else:<br>
> ><br>
> > Currently, organizations can receive no more than a /24 at a time under<br>
> > Section 4.10. However, Proposal ARIN-PROP-266, submitted by Chris Tacit<br>
> > and myself, could potentially allow an org to receive up to a /21 under<br>
> > that section, widening the potential for abuse by ?double-dipping?<br>
> > waiting list and transition space requests. As such, this proposal<br>
> > should be considered in that context.<br>
> > _______________________________________________<br>
> > ARIN-PPML<br>
> > You are receiving this message because you are subscribed to<br>
> > the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" rel="noreferrer" target="_blank">ARIN-PPML@arin.net</a> <mailto:<br>
> <a href="mailto:ARIN-PPML@arin.net" rel="noreferrer" target="_blank">ARIN-PPML@arin.net</a>>).<br>
> > Unsubscribe or manage your mailing list subscription at:<br>
> > <a href="https://lists.arin.net/mailman/listinfo/arin-ppml" rel="noreferrer noreferrer" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a> <<br>
> <a href="https://lists.arin.net/mailman/listinfo/arin-ppml" rel="noreferrer noreferrer" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a>><br>
> > Please contact <a href="mailto:info@arin.net" rel="noreferrer" target="_blank">info@arin.net</a> <mailto:<a href="mailto:info@arin.net" rel="noreferrer" target="_blank">info@arin.net</a>> if you experience<br>
> any issues.<br>
> > _______________________________________________<br>
> > ARIN-PPML<br>
> > You are receiving this message because you are subscribed to<br>
> > the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" rel="noreferrer" target="_blank">ARIN-PPML@arin.net</a> <mailto:<br>
> <a href="mailto:ARIN-PPML@arin.net" rel="noreferrer" target="_blank">ARIN-PPML@arin.net</a>>).<br>
> > Unsubscribe or manage your mailing list subscription at:<br>
> > <a href="https://lists.arin.net/mailman/listinfo/arin-ppml" rel="noreferrer noreferrer" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a> <<br>
> <a href="https://lists.arin.net/mailman/listinfo/arin-ppml" rel="noreferrer noreferrer" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a>><br>
> > Please contact <a href="mailto:info@arin.net" rel="noreferrer" target="_blank">info@arin.net</a> <mailto:<a href="mailto:info@arin.net" rel="noreferrer" target="_blank">info@arin.net</a>> if you experience<br>
> any issues.<br>
><br>
> -------------- next part --------------<br>
> An HTML attachment was scrubbed...<br>
> URL: <<br>
> <a href="https://lists.arin.net/pipermail/arin-ppml/attachments/20190730/57c0ba4b/attachment.htm" rel="noreferrer noreferrer" target="_blank">https://lists.arin.net/pipermail/arin-ppml/attachments/20190730/57c0ba4b/attachment.htm</a><br>
> ><br>
><br>
> ------------------------------<br>
><br>
> Subject: Digest Footer<br>
><br>
> _______________________________________________<br>
> ARIN-PPML mailing list<br>
> <a href="mailto:ARIN-PPML@arin.net" rel="noreferrer" target="_blank">ARIN-PPML@arin.net</a><br>
> <a href="https://lists.arin.net/mailman/listinfo/arin-ppml" rel="noreferrer noreferrer" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
><br>
><br>
> ------------------------------<br>
><br>
> End of ARIN-PPML Digest, Vol 169, Issue 45<br>
> ******************************************<br>
><br>
_______________________________________________<br>
ARIN-PPML<br>
You are receiving this message because you are subscribed to<br>
the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" rel="noreferrer" target="_blank">ARIN-PPML@arin.net</a>).<br>
Unsubscribe or manage your mailing list subscription at:<br>
<a href="https://lists.arin.net/mailman/listinfo/arin-ppml" rel="noreferrer noreferrer" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
Please contact <a href="mailto:info@arin.net" rel="noreferrer" target="_blank">info@arin.net</a> if you experience any issues.<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://lists.arin.net/pipermail/arin-ppml/attachments/20190730/8ced6eaa/attachment.htm" rel="noreferrer noreferrer" target="_blank">https://lists.arin.net/pipermail/arin-ppml/attachments/20190730/8ced6eaa/attachment.htm</a>><br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
ARIN-PPML mailing list<br>
<a href="mailto:ARIN-PPML@arin.net" rel="noreferrer" target="_blank">ARIN-PPML@arin.net</a><br>
<a href="https://lists.arin.net/mailman/listinfo/arin-ppml" rel="noreferrer noreferrer" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
<br>
<br>
------------------------------<br>
<br>
End of ARIN-PPML Digest, Vol 169, Issue 47<br>
******************************************<br>
</blockquote></div></div></div>
_______________________________________________<br>
ARIN-PPML<br>
You are receiving this message because you are subscribed to<br>
the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" target="_blank">ARIN-PPML@arin.net</a>).<br>
Unsubscribe or manage your mailing list subscription at:<br>
<a href="https://lists.arin.net/mailman/listinfo/arin-ppml" rel="noreferrer" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
Please contact <a href="mailto:info@arin.net" target="_blank">info@arin.net</a> if you experience any issues.<br>
</blockquote></div>