<p dir="ltr">I support this policy as AC recommends.<br>
RD</p>
<div class="gmail_quote">On May 1, 2015 6:01 PM, <<a href="mailto:arin-ppml-request@arin.net">arin-ppml-request@arin.net</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send ARIN-PPML mailing list submissions to<br>
<a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lists.arin.net/mailman/listinfo/arin-ppml" target="_blank">http://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">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">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. LAST CALL: Recommended Draft Policy ARIN-2014-21:<br>
Modification to CI Pool Size per Section 4.4 (ARIN)<br>
2. Re: LAST CALL: Recommended Draft Policy ARIN-2014-6: Remove<br>
Operational Reverse DNS Text (Michael Peddemors)<br>
3. Re: LAST CALL: Recommended Draft Policy ARIN-2014-21:<br>
Modification to CI Pool Size per Section 4.4 (ARIN)<br>
4. Weekly posting summary for <a href="mailto:ppml@arin.net">ppml@arin.net</a> (Thomas Narten)<br>
5. Re: Advisory Council Meeting Results - April 2015 (ARIN)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Mon, 27 Apr 2015 12:06:10 -0400<br>
From: ARIN <<a href="mailto:info@arin.net">info@arin.net</a>><br>
To: <a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a><br>
Subject: [arin-ppml] LAST CALL: Recommended Draft Policy ARIN-2014-21:<br>
Modification to CI Pool Size per Section 4.4<br>
Message-ID: <<a href="mailto:553E5E72.6060605@arin.net">553E5E72.6060605@arin.net</a>><br>
Content-Type: text/plain; charset=utf-8; format=flowed<br>
<br>
The ARIN Advisory Council (AC) met on 15 April 2015 and decided to<br>
send the following to last call:<br>
<br>
Recommended Draft Policy ARIN-2014-21: Modification to CI Pool Size<br>
per Section 4.4<br>
<br>
Feedback is encouraged during the last call period. All comments should<br>
be provided to the Public Policy Mailing List. This last call will<br>
expire on 11 May 2015. After last call the AC will conduct their<br>
last call review.<br>
<br>
The draft policy text is below and available at:<br>
<a href="https://www.arin.net/policy/proposals/" target="_blank">https://www.arin.net/policy/proposals/</a><br>
<br>
The ARIN Policy Development Process is available at:<br>
<a href="https://www.arin.net/policy/pdp.html" target="_blank">https://www.arin.net/policy/pdp.html</a><br>
<br>
Regards,<br>
<br>
Communications and Member Services<br>
American Registry for Internet Numbers (ARIN)<br>
<br>
<br>
## * ##<br>
<br>
<br>
Recommended Draft Policy ARIN-2014-21<br>
Modification to CI Pool Size per Section 4.4<br>
<br>
Date: 25 November 2014<br>
<br>
AC's assessment of conformance with the Principles of Internet Number<br>
Resource Policy:<br>
<br>
This proposal enables fair and impartial number resource administration<br>
by ensuring IPv4 resources are available for critical infrastructure and<br>
Internet Exchanges in particular after IPv4 resources are no longer<br>
readily available from the ARIN free pool. This benefits more than just<br>
the individual organizations receiving these resources; it benefits the<br>
entire Internet Community by contributing to the stability and<br>
scalability of the Internet as a whole. This proposal is technically<br>
sound and is supported by the community.<br>
<br>
Problem Statement:<br>
<br>
At the time that this section of policy was written, IXP growth in North<br>
America was stagnant. Efforts of late have increased significantly<br>
within the IXP standards and other communities to improve critical<br>
infrastructure in North America. This effort is paying dividends and we<br>
project that a /16 will not be enough to continue to improve global<br>
interconnect conditions and support needed IXP CI infrastructure.<br>
<br>
Policy statement:<br>
<br>
Change to text in section 4.4 Micro Allocations:<br>
<br>
Current text:<br>
<br>
ARIN will place an equivalent of a /16 of IPv4 address space in a<br>
reserve for Critical Infrastructure, as defined in section 4.4. If at<br>
the end of the policy term there is unused address space remaining in<br>
this pool, ARIN staff is authorized to utilize this space in a manner<br>
consistent with community expectations.<br>
<br>
Proposed text to replace current text entirely:<br>
<br>
ARIN will place an equivalent of a /15 of IPv4 address space in a<br>
reserve for Critical Infrastructure, as defined in section 4.4.<br>
<br>
Timetable for implementation: Immediate<br>
<br>
#####<br>
<br>
ARIN STAFF ASSESSMENT<br>
<br>
Draft Policy ARIN-2014-21: Modification to CI Pool Size per Section 4.4<br>
Date of Assessment: 14 January 2015<br>
<br>
1. Summary (Staff Understanding)<br>
<br>
This policy changes one section of existing NRPM policy 4.4 to extend<br>
the current reservation size for critical infrastructure and exchange<br>
points from a /16 equivalent to a /15 equivalent.<br>
<br>
<br>
2. Comments<br>
<br>
A. ARIN Staff Comments<br>
<br>
??? For informational purposes:<br>
??? A total of 35 /24s have been issued from the reserved /16 equivalent<br>
for CI and IXPs since the policy was amended and implemented on 20 March<br>
2013, leaving 221 /24s available in this reserved block.<br>
<br>
??? There are currently 381 free /24s remaining in the two /8 ranges<br>
used for CI and IXP micro-allocations.<br>
<br>
??? This policy could be implemented as written.<br>
<br>
<br>
B. ARIN General Counsel - Legal Assessment<br>
<br>
This proposal does not create any material legal issue.<br>
<br>
3. Resource Impact<br>
<br>
This policy would have minimal resource impact from an implementation<br>
aspect. It is estimated that implementation would occur within 3 months<br>
after ratification by the ARIN Board of Trustees. The following would be<br>
needed in order to implement:<br>
?? Updated guidelines and internal procedures<br>
?? Staff training<br>
<br>
4. Proposal/Draft Policy Text Assessed<br>
Draft Policy ARIN-2014-21???Modification to CI Pool Size per Section 4.4<br>
Date: 25 November 2014<br>
Problem Statement:<br>
At the time that this section of policy was written, IXP growth in North<br>
America was stagnant. Efforts of late have increased significantly<br>
within the IXP standards and other communities to improve critical<br>
infrastructure in North America. This effort is paying dividends and we<br>
project that a /16 will not be enough to continue to improve global<br>
interconnect conditions and support needed IXP CI infrastructure.<br>
Policy statement:<br>
Change to text in section 4.4 Micro Allocations:<br>
Current text:<br>
ARIN will place an equivalent of a /16 of IPv4 address space in a<br>
reserve for Critical Infrastructure, as defined in section 4.4. If at<br>
the end of the policy term there is unused address space remaining in<br>
this pool, ARIN staff is authorized to utilize this space in a manner<br>
consistent with community expectations.<br>
Proposed text to replace current text entirely:<br>
ARIN will place an equivalent of a /15 of IPv4 address space in a<br>
reserve for Critical Infrastructure, as defined in section 4.4.<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Mon, 27 Apr 2015 09:42:24 -0700<br>
From: Michael Peddemors <<a href="mailto:michael@linuxmagic.com">michael@linuxmagic.com</a>><br>
To: <a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a><br>
Subject: Re: [arin-ppml] LAST CALL: Recommended Draft Policy<br>
ARIN-2014-6: Remove Operational Reverse DNS Text<br>
Message-ID: <<a href="mailto:553E66F0.9040000@linuxmagic.com">553E66F0.9040000@linuxmagic.com</a>><br>
Content-Type: text/plain; charset=utf-8; format=flowed<br>
<br>
Vote against..<br>
<br>
In my opinion, the granting of a public IPv4 (or IPv6) address space<br>
SHOULD come alone with some responsibility, including<br>
'rwhois/SWIP/routing/rDNS obligations'.<br>
<br>
I would rather have more work done by the community at large to reach<br>
consensus on those things, even IF ARIN has little enforcement mandate<br>
at this time, we should be able to reference it in discussions.<br>
<br>
I suggest abandoning "Recommended Draft Policy ARIN-2014-6" and work on<br>
better language.<br>
<br>
On 15-04-27 09:05 AM, ARIN wrote:<br>
> The ARIN Advisory Council (AC) met on 15 April 2015 and decided to<br>
> send the following to last call:<br>
><br>
> Recommended Draft Policy ARIN-2014-6: Remove Operational Reverse DNS<br>
> Text<br>
><br>
> Feedback is encouraged during the last call period. All comments should<br>
> be provided to the Public Policy Mailing List. This last call will<br>
> expire on 11 May 2015. After last call the AC will conduct their<br>
> last call review.<br>
><br>
> The draft policy text is below and available at:<br>
> <a href="https://www.arin.net/policy/proposals/" target="_blank">https://www.arin.net/policy/proposals/</a><br>
><br>
> The ARIN Policy Development Process is available at:<br>
> <a href="https://www.arin.net/policy/pdp.html" target="_blank">https://www.arin.net/policy/pdp.html</a><br>
><br>
> Regards,<br>
><br>
> Communications and Member Services<br>
> American Registry for Internet Numbers (ARIN)<br>
><br>
><br>
> ## * ##<br>
><br>
><br>
> Recommended Draft Policy ARIN-2014-6<br>
> Remove Operational Reverse DNS Text (was: Remove 7.1)<br>
><br>
> Date: 21 January 2014<br>
><br>
> AC's assessment of conformance with the Principles of Internet Number<br>
> Resource Policy:<br>
><br>
> 2014-6 enables fair and impartial number resource administration by<br>
> removing technical statements that are not related to number policy from<br>
> the NRPM. It is technically sound to remove operational practice from<br>
> the NRPM; indeed this act serves as a forcing function for a best<br>
> practices document that is both more detailed and more approachable than<br>
> the policy statement that was removed. Discussion of the previous<br>
> revision of 2014-6 centered around "why are you fixing this for IPv4 and<br>
> not IPv6", and the most recent changes reflect that community feedback.<br>
> There has not been notable opposition to the notion of removing<br>
> operational language from the NRPM.<br>
><br>
> Problem Statement:<br>
><br>
> 7.1 attempts to assert rules on rDNS management at ARIN. It fails to do<br>
> so because it only addresses in-addr.arpa (missing equally important<br>
> rules in ip6.arpa). It's also not based on any RFC; it's an arbitrary<br>
> decision made by ARIN technical staff. We should remove this text from<br>
> policy, as it represents operational practice rather than ARIN number<br>
> policy.<br>
><br>
> In feedback received at public policy meetings and on the PPML mailing<br>
> list, the Community expressed a desire for IPv4 and IPv6 policy on<br>
> reverse DNS to be congruent (that is to say, it makes no sense to remove<br>
> 7.1 without addressing 6.5.6 which is similarly operationally<br>
> prescriptive) and bring this proposal forward again.<br>
><br>
> Policy statement:<br>
><br>
> Remove 7.1<br>
><br>
> Remove 6.5.6<br>
><br>
> Comments:<br>
><br>
> a.Timetable for implementation: Immediate<br>
><br>
> b.Anything else:<br>
> 7.1. Maintaining IN-ADDRs<br>
><br>
> All ISPs receiving one or more distinct /16 CIDR blocks of IP addresses<br>
> from ARIN will be responsible for maintaining all IN-ADDR.ARPA domain<br>
> records for their respective customers. For blocks smaller than /16, and<br>
> for the segment of larger blocks smaller than /16, ARIN can maintain<br>
> IN-ADDRs.<br>
><br>
> 6.5.6. Reverse lookup<br>
><br>
> When an RIR delegates IPv6 address space to an organization, it also<br>
> delegates the responsibility to manage the reverse lookup zone that<br>
> corresponds to the allocated IPv6 address space. Each organization<br>
> should properly manage its reverse lookup zone. When making an address<br>
> assignment, the organization must delegate to an assignee organization,<br>
> upon request, the responsibility to manage the reverse lookup zone that<br>
> corresponds to the assigned address.<br>
><br>
> #####<br>
><br>
> ARIN STAFF & LEGAL ASSESSMENT<br>
><br>
> Draft Policy ARIN-2014-6<br>
> Remove Operational Reverse DNS Text<br>
><br>
> Date of Assessment: March 17, 2015<br>
><br>
> 1. Summary (Staff Understanding)<br>
> This proposal would remove 6.5.6 and 7.1, thus removing reverse DNS<br>
> language from the NRPM.<br>
><br>
> 2. Comments<br>
> A. ARIN Staff Comments<br>
> This change to NRPM will not change the DNS service that ARIN performs.<br>
> This proposal can be implemented as written.<br>
><br>
> ARIN registration services staff occasionally receives a telephone or<br>
> email inquiry asking how reverse DNS services can be set up for a<br>
> company. In the cases the company is a downstream customer of an ISP who<br>
> has received a direct allocation from ARIN, staff explains this service<br>
> can be set up for them by their service provider. On rare occasion, the<br>
> company presses for a reference that states this is done by their ISP,<br>
> and not ARIN. In those cases staff will refer them to the language<br>
> currently in the NRPM.<br>
><br>
> In the case the language is removed from NRPM, ARIN staff will create a<br>
> resource for the ARIN public website that describes how ARIN's Reverse<br>
> DNS services are provided; including who is able to establish Reverse<br>
> DNS service for different types of registration records.<br>
><br>
> B. ARIN General Counsel ??? Legal Assessment<br>
> The policy does not create legal concerns.<br>
><br>
> 3. Resource Impact<br>
> This policy would have minimal impact from an implementation standpoint.<br>
> It is estimated implementation would occur within 3 months after<br>
> ratification by the ARIN Board of Trustees. The following tasks will be<br>
> completed for implementation:<br>
> Versioned change to NRPM<br>
> Updated guidelines on ARIN website describing reverse DNS services (to<br>
> act as general information resource and serve as new reference point for<br>
> situation described in staff comments).<br>
> Staff training<br>
><br>
> 4. Proposal / Draft Policy Text Assessed<br>
><br>
> Draft Policy ARIN-2014-6<br>
> Remove Operational Reverse DNS Text (was: Remove 7.1)<br>
><br>
> Date: 21 January 2015<br>
><br>
> Problem Statement:<br>
><br>
> 7.1 attempts to assert rules on rDNS management at ARIN. It fails to do<br>
> so because it only addresses in-addr.arpa (missing equally important<br>
> rules in ip6.arpa). It's also not based on any RFC; it's an arbitrary<br>
> decision made by ARIN technical staff. We should remove this text from<br>
> policy, as it represents operational practice rather than ARIN number<br>
> policy.<br>
><br>
> In feedback received at public policy meetings and on the PPML mailing<br>
> list, the Community expressed a desire for IPv4 and IPv6 policy on<br>
> reverse DNS to be congruent (that is to say, it makes no sense to remove<br>
> 7.1 without addressing 6.5.6 which is similarly operationally<br>
> prescriptive) and bring this proposal forward again.<br>
><br>
> Policy statement:<br>
><br>
> Remove 7.1<br>
><br>
> Remove 6.5.6<br>
><br>
> Comments:<br>
><br>
> a.Timetable for implementation: Immediate<br>
><br>
> b.Anything else:<br>
><br>
> 7.1. Maintaining IN-ADDRs<br>
><br>
> All ISPs receiving one or more distinct /16 CIDR blocks of IP addresses<br>
> from ARIN will be responsible for maintaining all IN-ADDR.ARPA domain<br>
> records for their respective customers. For blocks smaller than /16, and<br>
> for the segment of larger blocks smaller than /16, ARIN can maintain<br>
> IN-ADDRs.<br>
><br>
> 6.5.6. Reverse lookup<br>
><br>
> When an RIR delegates IPv6 address space to an organization, it also<br>
> delegates the responsibility to manage the reverse lookup zone that<br>
> corresponds to the allocated IPv6 address space. Each organization<br>
> should properly manage its reverse lookup zone. When making an address<br>
> assignment, the organization must delegate to an assignee organization,<br>
> upon request, the responsibility to manage the reverse lookup zone that<br>
> corresponds to the assigned address.<br>
> _______________________________________________<br>
> 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">ARIN-PPML@arin.net</a>).<br>
> Unsubscribe or manage your mailing list subscription at:<br>
> <a href="http://lists.arin.net/mailman/listinfo/arin-ppml" target="_blank">http://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
> Please contact <a href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.<br>
<br>
<br>
<br>
--<br>
"Catch the Magic of Linux..."<br>
------------------------------------------------------------------------<br>
Michael Peddemors, President/CEO LinuxMagic Inc.<br>
Visit us at <a href="http://www.linuxmagic.com" target="_blank">http://www.linuxmagic.com</a> @linuxmagic<br>
------------------------------------------------------------------------<br>
A Wizard IT Company - For More Info <a href="http://www.wizard.ca" target="_blank">http://www.wizard.ca</a><br>
"LinuxMagic" a Registered TradeMark of Wizard Tower TechnoServices Ltd.<br>
------------------------------------------------------------------------<br>
<a href="tel:604-682-0300" value="+16046820300">604-682-0300</a> Beautiful British Columbia, Canada<br>
<br>
This email and any electronic data contained are confidential and intended<br>
solely for the use of the individual or entity to which they are addressed.<br>
Please note that any views or opinions presented in this email are solely<br>
those of the author and are not intended to represent those of the company.<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Mon, 27 Apr 2015 15:14:40 -0400<br>
From: ARIN <<a href="mailto:info@arin.net">info@arin.net</a>><br>
To: <a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a><br>
Subject: Re: [arin-ppml] LAST CALL: Recommended Draft Policy<br>
ARIN-2014-21: Modification to CI Pool Size per Section 4.4<br>
Message-ID: <<a href="mailto:553E8AA0.3080001@arin.net">553E8AA0.3080001@arin.net</a>><br>
Content-Type: text/plain; charset=utf-8; format=flowed<br>
<br>
The ARIN Advisory Council provided an updated assessment of 2014-21:<br>
<br>
"This proposal is technically sound, enables fair and impartial number<br>
resource administration by ensuring IPv4 resources are available for<br>
critical infrastructure and Internet exchanges in particular after IPv4<br>
resources are no longer readily available from the ARIN free pool. This<br>
benefits more than just the individual organizations receiving these<br>
resources; it benefits the entire Internet community by contributing to<br>
the stability and scalability of the Internet as a whole. Although a<br>
portion of the community believes the current reservation is sufficient<br>
and that expanding it will unnecessarily impact those that would have<br>
otherwise received the resources, the majority of the community polled<br>
concluded the reservation is justified and supports the proposal."<br>
<br>
Regards,<br>
<br>
Communications and Member Services<br>
American Registry for Internet Numbers (ARIN)<br>
<br>
On 4/27/15 12:06 PM, ARIN wrote:<br>
> The ARIN Advisory Council (AC) met on 15 April 2015 and decided to<br>
> send the following to last call:<br>
><br>
> Recommended Draft Policy ARIN-2014-21: Modification to CI Pool Size<br>
> per Section 4.4<br>
><br>
> Feedback is encouraged during the last call period. All comments should<br>
> be provided to the Public Policy Mailing List. This last call will<br>
> expire on 11 May 2015. After last call the AC will conduct their<br>
> last call review.<br>
><br>
> The draft policy text is below and available at:<br>
> <a href="https://www.arin.net/policy/proposals/" target="_blank">https://www.arin.net/policy/proposals/</a><br>
><br>
> The ARIN Policy Development Process is available at:<br>
> <a href="https://www.arin.net/policy/pdp.html" target="_blank">https://www.arin.net/policy/pdp.html</a><br>
><br>
> Regards,<br>
><br>
> Communications and Member Services<br>
> American Registry for Internet Numbers (ARIN)<br>
><br>
><br>
> ## * ##<br>
><br>
><br>
> Recommended Draft Policy ARIN-2014-21<br>
> Modification to CI Pool Size per Section 4.4<br>
><br>
> Date: 25 November 2014<br>
><br>
> AC's assessment of conformance with the Principles of Internet Number<br>
> Resource Policy:<br>
><br>
> This proposal enables fair and impartial number resource administration<br>
> by ensuring IPv4 resources are available for critical infrastructure and<br>
> Internet Exchanges in particular after IPv4 resources are no longer<br>
> readily available from the ARIN free pool. This benefits more than just<br>
> the individual organizations receiving these resources; it benefits the<br>
> entire Internet Community by contributing to the stability and<br>
> scalability of the Internet as a whole. This proposal is technically<br>
> sound and is supported by the community.<br>
><br>
> Problem Statement:<br>
><br>
> At the time that this section of policy was written, IXP growth in North<br>
> America was stagnant. Efforts of late have increased significantly<br>
> within the IXP standards and other communities to improve critical<br>
> infrastructure in North America. This effort is paying dividends and we<br>
> project that a /16 will not be enough to continue to improve global<br>
> interconnect conditions and support needed IXP CI infrastructure.<br>
><br>
> Policy statement:<br>
><br>
> Change to text in section 4.4 Micro Allocations:<br>
><br>
> Current text:<br>
><br>
> ARIN will place an equivalent of a /16 of IPv4 address space in a<br>
> reserve for Critical Infrastructure, as defined in section 4.4. If at<br>
> the end of the policy term there is unused address space remaining in<br>
> this pool, ARIN staff is authorized to utilize this space in a manner<br>
> consistent with community expectations.<br>
><br>
> Proposed text to replace current text entirely:<br>
><br>
> ARIN will place an equivalent of a /15 of IPv4 address space in a<br>
> reserve for Critical Infrastructure, as defined in section 4.4.<br>
><br>
> Timetable for implementation: Immediate<br>
><br>
> #####<br>
><br>
> ARIN STAFF ASSESSMENT<br>
><br>
> Draft Policy ARIN-2014-21: Modification to CI Pool Size per Section 4.4<br>
> Date of Assessment: 14 January 2015<br>
><br>
> 1. Summary (Staff Understanding)<br>
><br>
> This policy changes one section of existing NRPM policy 4.4 to extend<br>
> the current reservation size for critical infrastructure and exchange<br>
> points from a /16 equivalent to a /15 equivalent.<br>
><br>
><br>
> 2. Comments<br>
><br>
> A. ARIN Staff Comments<br>
><br>
> ??? For informational purposes:<br>
> ??? A total of 35 /24s have been issued from the reserved /16 equivalent<br>
> for CI and IXPs since the policy was amended and implemented on 20 March<br>
> 2013, leaving 221 /24s available in this reserved block.<br>
><br>
> ??? There are currently 381 free /24s remaining in the two /8 ranges<br>
> used for CI and IXP micro-allocations.<br>
><br>
> ??? This policy could be implemented as written.<br>
><br>
><br>
> B. ARIN General Counsel - Legal Assessment<br>
><br>
> This proposal does not create any material legal issue.<br>
><br>
> 3. Resource Impact<br>
><br>
> This policy would have minimal resource impact from an implementation<br>
> aspect. It is estimated that implementation would occur within 3 months<br>
> after ratification by the ARIN Board of Trustees. The following would be<br>
> needed in order to implement:<br>
> ?? Updated guidelines and internal procedures<br>
> ?? Staff training<br>
><br>
> 4. Proposal/Draft Policy Text Assessed<br>
> Draft Policy ARIN-2014-21???Modification to CI Pool Size per Section 4.4<br>
> Date: 25 November 2014<br>
> Problem Statement:<br>
> At the time that this section of policy was written, IXP growth in North<br>
> America was stagnant. Efforts of late have increased significantly<br>
> within the IXP standards and other communities to improve critical<br>
> infrastructure in North America. This effort is paying dividends and we<br>
> project that a /16 will not be enough to continue to improve global<br>
> interconnect conditions and support needed IXP CI infrastructure.<br>
> Policy statement:<br>
> Change to text in section 4.4 Micro Allocations:<br>
> Current text:<br>
> ARIN will place an equivalent of a /16 of IPv4 address space in a<br>
> reserve for Critical Infrastructure, as defined in section 4.4. If at<br>
> the end of the policy term there is unused address space remaining in<br>
> this pool, ARIN staff is authorized to utilize this space in a manner<br>
> consistent with community expectations.<br>
> Proposed text to replace current text entirely:<br>
> ARIN will place an equivalent of a /15 of IPv4 address space in a<br>
> reserve for Critical Infrastructure, as defined in section 4.4.<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Fri, 01 May 2015 00:53:03 -0400<br>
From: Thomas Narten <<a href="mailto:narten@us.ibm.com">narten@us.ibm.com</a>><br>
To: <a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a><br>
Subject: [arin-ppml] Weekly posting summary for <a href="mailto:ppml@arin.net">ppml@arin.net</a><br>
Message-ID: <<a href="mailto:201505010453.t414r38B016393@rotala.raleigh.ibm.com">201505010453.t414r38B016393@rotala.raleigh.ibm.com</a>><br>
Content-Type: text/plain; charset=us-ascii<br>
<br>
Total of 6 messages in the last 7 days.<br>
<br>
script run at: Fri May 1 00:53:03 EDT 2015<br>
<br>
Messages | Bytes | Who<br>
--------+------+--------+----------+------------------------<br>
66.67% | 4 | 65.54% | 39225 | <a href="mailto:info@arin.net">info@arin.net</a><br>
16.67% | 1 | 23.01% | 13773 | <a href="mailto:michael@linuxmagic.com">michael@linuxmagic.com</a><br>
16.67% | 1 | 11.45% | 6851 | <a href="mailto:narten@us.ibm.com">narten@us.ibm.com</a><br>
--------+------+--------+----------+------------------------<br>
100.00% | 6 |100.00% | 59849 | Total<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Fri, 01 May 2015 18:01:05 -0400<br>
From: ARIN <<a href="mailto:info@arin.net">info@arin.net</a>><br>
To: <a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a><br>
Subject: Re: [arin-ppml] Advisory Council Meeting Results - April 2015<br>
Message-ID: <<a href="mailto:5543F7A1.7010301@arin.net">5543F7A1.7010301@arin.net</a>><br>
Content-Type: text/plain; charset=windows-1252; format=flowed<br>
<br>
> The AC abandoned 2014-1, 2014-14 and 2014-22. Anyone dissatisfied with<br>
> these decisions may initiate a petition. The deadline to begin a<br>
> petition will be five business days after the AC's draft meeting minutes<br>
> are published.<br>
<br>
The minutes from the ARIN Advisory Council's 19 February meeting have<br>
been published:<br>
<a href="https://www.arin.net/about_us/ac/ac2015_0415.html" target="_blank">https://www.arin.net/about_us/ac/ac2015_0415.html</a><br>
<br>
The petition deadline is 8 May 2015.<br>
<br>
For more information on starting and participating in petitions, see PDP<br>
Petitions at: <a href="https://www.arin.net/policy/pdp_petitions.html" target="_blank">https://www.arin.net/policy/pdp_petitions.html</a><br>
<br>
The ARIN Policy Development Process can be found at:<br>
<a href="https://www.arin.net/policy/pdp.html" target="_blank">https://www.arin.net/policy/pdp.html</a><br>
<br>
Draft Policy and Proposal texts are available at:<br>
<a href="https://www.arin.net/policy/proposals/index.html" target="_blank">https://www.arin.net/policy/proposals/index.html</a><br>
<br>
Regards,<br>
<br>
Communications and Member Services<br>
American Registry for Internet Numbers (ARIN)<br>
<br>
<br>
<br>
On 4/27/15 12:05 PM, ARIN wrote:<br>
> In accordance with the ARIN Policy Development Process (PDP), the ARIN<br>
> Advisory Council (AC) met on 15 April 2015.<br>
><br>
> The AC moved the following to last call (to be posted separately to last<br>
> call):<br>
><br>
> Recommended Draft Policy ARIN-2014-6: Remove Operational Reverse DNS<br>
> Text<br>
> Recommended Draft Policy ARIN-2014-21: Modification to CI Pool Size<br>
> per Section 4.4<br>
><br>
> The AC abandoned the following:<br>
><br>
> Recommended Draft Policy ARIN-2014-1: Out of Region Use<br>
> Recommended Draft Policy ARIN-2014-14: Removing Needs Test from Small<br>
> IPv4 Transfers<br>
> Recommended Draft Policy ARIN-2014-22: Removal of Minimum in Section<br>
> 4.10<br>
><br>
> The AC provided the following statements:<br>
><br>
> Regarding ARIN-2014-1: Out of Region Use:<br>
><br>
> "After taking into careful consideration feedback from the ARIN<br>
> community, both on PPML and at ARIN 35, the AC voted to abandon 2014-1.<br>
><br>
> The AC's consensus is that more work is needed in clarifying and<br>
> resolving issues in this area and that a new proposal is more likely to<br>
> yield favorable results than continued efforts to tweak the existing<br>
> proposal, which has morphed considerably from the original author's<br>
> intent. To that end, there are AC members currently working to craft a<br>
> new proposal in this problem space."<br>
><br>
> Regarding ARIN-2014-14: Removing Needs Test from Small IPv4 Transfers:<br>
><br>
> "In its meeting on April 15th, 2015 following ARIN35, the ARIN advisory<br>
> council voted to abandon Draft Policy 2014-14 due to lack of support in<br>
> the community, as expressed in the Public Policy Meeting and on PPML."<br>
><br>
> Regarding ARIN-2014-22: Removal of Minimum in Section 4.10:<br>
><br>
> "The ARIN Advisory Council, based on input from the community, has voted<br>
> to abandon ARIN 2014-22 Removal of Minimum in Section 4.10.<br>
><br>
> The primary goal of Section 4.10 is to provide small blocks of IPv4<br>
> space to new entrants for IPv6. The removal of the minimum would have<br>
> significantly reduced the number of blocks available.<br>
><br>
> While blocks smaller than /24 are not widely routable today, the<br>
> Advisory Council believes the change would be premature.<br>
><br>
> As a first step to address routability concerns, the AC also recommends<br>
> that ARIN take additional measures to increase awareness of the specific<br>
> /10 netblock reserved for assignments under 4.10."<br>
><br>
> ==<br>
><br>
> The AC is continuing to work on:<br>
><br>
> Draft Policy ARIN-2015-1: Modification to Criteria for IPv6 Initial<br>
> End-User Assignments<br>
><br>
> The AC found the revisions to the ARIN NRPM Section 5 (as posted to PPML<br>
> on 24 February 2015) to be editorial in nature and recommended they be<br>
> adopted by the ARIN Board of Trustees.<br>
><br>
> The AC abandoned 2014-1, 2014-14 and 2014-22. Anyone dissatisfied with<br>
> these decisions may initiate a petition. The deadline to begin a<br>
> petition will be five business days after the AC's draft meeting minutes<br>
> are published. For more information on starting and participating in<br>
> petitions, see PDP Petitions at:<br>
> <a href="https://www.arin.net/policy/pdp_petitions.html" target="_blank">https://www.arin.net/policy/pdp_petitions.html</a><br>
><br>
> Draft Policy and Proposal texts are available at:<br>
> <a href="https://www.arin.net/policy/proposals/index.html" target="_blank">https://www.arin.net/policy/proposals/index.html</a><br>
><br>
> The ARIN Policy Development Process can be found at:<br>
> <a href="https://www.arin.net/policy/pdp.html" target="_blank">https://www.arin.net/policy/pdp.html</a><br>
><br>
> Regards,<br>
><br>
> Communications and Member Services<br>
> American Registry for Internet Numbers (ARIN)<br>
<br>
<br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
ARIN-PPML mailing list<br>
<a href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a><br>
<a href="http://lists.arin.net/mailman/listinfo/arin-ppml" target="_blank">http://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
<br>
End of ARIN-PPML Digest, Vol 119, Issue 1<br>
*****************************************<br>
</blockquote></div>