[arin-ppml] ARIN- 2014-21

Fri May 1 19:00:23 EDT 2015

I support this policy as AC recommends.
RD
On May 1, 2015 6:01 PM, <arin-ppml-request at arin.net> wrote:

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