From info at arin.net Thu May 3 08:59:21 2012 From: info at arin.net (ARIN) Date: Thu, 03 May 2012 05:59:21 -0700 Subject: [arin-announce] Maintenance Work Scheduled for Saturday, 5 May Message-ID: <4FA28129.6050509@arin.net> On Saturday, 5 May 2012 ARIN will be conducting maintenance to deploy new functionality in ARIN Online. The work will take place from 6:00 AM until approximately 12:00 PM EDT. ARIN users will experience interruption of three external services while this maintenance is performed. For the duration, you will not be able to log in to your ARIN Online account. Any mail sent to Registration Services will be queued and not immediately acknowledged. Additionally, transactions submitted via ARIN?s RESTful Provisioning service will be rejected with an outage error. Once the systems are back online, you will regain use of your ARIN Online account and queued mail will be processed. You will need to resubmit any RESTful calls sent during the outage so they can be processed. Thank you for your patience and cooperation. All other publicly available services (Whois, IRR, etc.) will be available during this outage. Regards, Mark Kosters Chief Technical Officer American Registry for Internet Numbers (ARIN) From info at arin.net Thu May 3 12:00:43 2012 From: info at arin.net (ARIN) Date: Thu, 03 May 2012 12:00:43 -0400 Subject: [arin-announce] Suggestions Consultation Now Closed Message-ID: <4FA2ABAB.80800@arin.net> ARIN Community, The consultation on open suggestions is now closed and we appreciate the community feedback. You can review the input in the arin-consult list archives at: http://lists.arin.net/pipermail/arin-consult/2012-April/date.html As provided for in the ARIN Consultation and Suggestion Process, within 30 days after the close of ARIN XXIX, or by 25 May, ARIN staff will publish the list of prioritized suggestions based on input received and further staff evaluation. If you have any questions, please contact us at info at arin.net. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Fri May 4 09:02:03 2012 From: info at arin.net (INFO) Date: Fri, 04 May 2012 09:02:03 -0400 Subject: [arin-announce] Joint NRO / ASO AC Response to ASO Review Report Message-ID: <4FA3D34B.4050508@arin.net> In accordance with the Internet Corporation for Assigned Names and Numbers (ICANN) Bylaws, the Number Resource Organization (NRO) undertakes independent periodic reviews of the Address Supporting Organization (ASO). ITEMS International, a consultancy engaged by the NRO to conduct this current review, delivered its report in early 2012. A public comment period closed on 6 April 2012. On 30 April 2012, the NRO submitted its considered response to the 26 recommendations of the report and the one recommendation received during the ICANN public comment period. Its response was formulated with the assistance of the ASO Address Council (ASO AC). The NRO extends its thanks to all of those who have participated in this process. For more information, please see: http://www.nro.net/news/joint-nro-aso-ac-response-to-aso-review-report Kind regards, ASO Secretariat From info at arin.net Fri May 4 11:21:11 2012 From: info at arin.net (ARIN) Date: Fri, 04 May 2012 08:21:11 -0700 Subject: [arin-announce] Registration Services Department Audit Report Message-ID: <4FA3F3E7.9060805@arin.net> As you may know, in the fourth quarter of 2011, Baker Tilley conducted a full review and audit of the Registration Services Department's processes and procedures to ensure consistency with the policies described in the Number Resource Policy Manual (NRPM). ARIN is pleased to announce that the final report for this audit is now available on the ARIN website for community review and can be found at: https://www.arin.net/about_us/corp_docs/registration_audit.pdf The results of the final report were positive and not only highlighted the areas where RSD excelled, but also identified several potential enhancements that could be made to improve consistency and efficiency. The Registration Services Department has already adopted some of these recommendations and will continue to streamline, enhance and improve its operational processes going forward in order to provide the best service possible to the ARIN community. Regards, Leslie Nobile Director, Registration Services American Registry for Internet Numbers (ARIN) From info at arin.net Fri May 4 15:54:44 2012 From: info at arin.net (ARIN) Date: Fri, 04 May 2012 15:54:44 -0400 Subject: [arin-announce] New Policy Proposals on PPML Message-ID: <4FA43404.1080706@arin.net> New policy proposals have recently been posted to the ARIN Public Policy Mailing List for discussion on that list. ARIN-prop-166 Clarify /29 Assignment Identification Requirement ARIN-prop-167 Removal of Renumbering Requirement for Small Multihomers ARIN-prop-168 Promote 4byte ASN Usage ARIN-prop-169 Cleanup IPv6 section 6.5.7 Draft Policies and Proposals under discussion can be found 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 Mailing list subscription information can be found at: https://www.arin.net/mailing_lists/ Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Fri May 4 16:34:11 2012 From: info at arin.net (ARIN) Date: Fri, 04 May 2012 13:34:11 -0700 Subject: [arin-announce] ARIN XXIX Meeting Report Now Available Message-ID: <4FA43D43.40006@arin.net> Thank you to all who attended ARIN XXIX in Vancouver in person or remotely! The official meeting report, which includes presentations, summary notes, transcripts, and webcast of the entire meeting, is now available on the ARIN website at: http://www.arin.net/participate/meetings/reports/ARIN_XXIX/ We thank all the participants who took time out to submit their feedback in the ARIN XXIX Meeting Survey. We value community input as we look for ways to improving future meetings. We hope you plan to join us 24 - 26 October 2012 for ARIN XXX in Dallas, Texas, and take part in this integral part of the Internet number resource policy development process. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Mon May 7 10:30:16 2012 From: info at arin.net (ARIN) Date: Mon, 07 May 2012 07:30:16 -0700 Subject: [arin-announce] Request Reports using Reg-RWS Message-ID: <4FA7DC78.2090802@arin.net> ARIN is pleased to announce that approved users can now request WhoWas reports using ARIN?s RESTful Web Service (Reg-RWS). We have also added the ability to request Reassignments and Associations reports via Reg-RWS. Previous to this release, these three reports could only be requested/retrieved through ARIN Online?s web interface. For detailed instructions on performing these calls, please refer to https://www.arin.net/resources/restful-interfaces.html. Additional refinements to the Reg-RWS system and its documentation have been included in this deployment. We encourage you to explore our improved Reg-RWS User Guide and documentation at: https://www.arin.net/resources/restful-interfaces.html ARIN Online has grown tremendously since its initial deployment in October 2008. To see how far we have come, what is currently being developed, and future goals, visit: https://www.arin.net/features/ And to further help you visualize which actions can be performed via ARIN Online and RESTful Provisioning, we have published an Interacting with ARIN guide, available at: https://www.arin.net/resources/interacting.html Log in today and check out these enhancements, or create your ARIN Online account at: https://www.arin.net Please send any questions, comments, or issues to hostmaster at arin.net. Regards, Mark Kosters Chief Technical Officer American Registry for Internet Numbers (ARIN) From info at arin.net Tue May 8 09:00:31 2012 From: info at arin.net (ARIN) Date: Tue, 08 May 2012 09:00:31 -0400 Subject: [arin-announce] 2012 APNIC Member and Stakeholder Survey Now Open Message-ID: <4FA918EF.1060900@arin.net> ARIN Community, The APNIC secretariat welcomes your participation in their 2012 APNIC Member and Stakeholder Survey. This survey is open to APNIC account holders, Asia Pacific stakeholders and global stakeholders. Global stakeholders may answer questions about APNIC public services, Internet governance, IPv6 deployment and global Internet development. The survey is open now through 31 May. For those interested in participating you will find details and a link to the survey at: http://www.apnic.net/publications/news/2012/survey Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Tue May 8 14:32:28 2012 From: info at arin.net (ARIN) Date: Tue, 08 May 2012 14:32:28 -0400 Subject: [arin-announce] =?windows-1252?q?ICANN_Board_Ratifies_=93Global_P?= =?windows-1252?q?olicy_Proposal_for_Post_Exhaustion_IPV4_Allocation_Mecha?= =?windows-1252?q?nisms_by_the_IANA=94?= Message-ID: <4FA966BC.4080206@arin.net> On 6 May the ICANN Board ratified the global proposal GPP-IPv4-2011, identified in the ARIN region as ARIN-2011-9 (Global Proposal) . You can find the ICANN Board resolution at the following link: http://www.icann.org/en/groups/board/documents/resolutions-06may12-en.htm#1.1 Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Wed May 9 15:04:36 2012 From: info at arin.net (ARIN) Date: Wed, 09 May 2012 15:04:36 -0400 Subject: [arin-announce] ARIN Projects Survey Reminder Message-ID: <4FAABFC4.6060402@arin.net> There is still time to share your feedback on potential new services and improvements at ARIN. In addition to our planned functionality, ARIN keeps track of community and internal recommendations for new services and improvements. These items await prioritization, planning, and approval before work can commence. To gather community input on future upgrades and services, ARIN held a session to go over a list of both planned and unplanned activities at ARIN XXIX, and posted a survey for the community at: https://www.surveymonkey.com/s/ARINFutureProjectsSurvey ARIN management will use this feedback to help prioritize future work, so your input is important! To increase clarity, we have added more details to the descriptions of the items to be prioritized at: https://www.arin.net/features/#tbd The survey will remain open until 15 May, and we are eager to hear from you! We look forward to hearing your thoughts as we set future development and service priorities. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Mon May 14 14:05:15 2012 From: info at arin.net (ARIN) Date: Mon, 14 May 2012 14:05:15 -0400 Subject: [arin-announce] ARIN IPv4 Countdown Plan Message-ID: <4FB1495B.8060702@arin.net> On 23 April 2012 during ARIN XXIX in Vancouver, Leslie Nobile, Director of Registration Services gave a presentation on ARIN?s plan to manage the distribution of its remaining IPv4 address pool. The ARIN community has worked together over the last several years in developing policy to manage how ARIN allocates and assigns IPv4 addresses. ARIN has reviewed and refined its procedures to create an IPv4 Countdown Plan explaining how IPv4 requests will be processed as the remaining IPv4 address pool is distributed. We have posted the details of the plan at: https://www.arin.net/resources/request/ipv4_countdown.html The page includes links to the presentation given by Ms. Nobile at the ARIN meeting, and we invite you to view the webcast archive as well in order to see the presentation and the discussion that ensued. https://www.arin.net/participate/meetings/reports/ARIN_XXIX/webcast/nobile_ipv4_countdown.mov The IPv4 Countdown is a dynamic process and we will keep the community up to date on the status of the ARIN IPv4 address pool. ARIN will be updating and adding more information to the IPv4 Countdown page as we move through this process, so we strongly encourage you to pay attention to announcements and keep track of the current IPv4 inventory by monitoring the counter on the ARIN homepage. Because the IPv4 inventory may fluctuate on a daily basis, it is not intended as a tool to guide the timing of your IPv4 resource requests. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Tue May 15 10:38:52 2012 From: info at arin.net (ARIN) Date: Tue, 15 May 2012 10:38:52 -0400 Subject: [arin-announce] Improved User Documentation for Reg-RWS Message-ID: <4FB26A7C.3000001@arin.net> ARIN is pleased to bring you an updated documentation package for our RESTful Provisioning system (Reg-RWS), including: 1) An overview page (https://www.arin.net/resources/restful-interfaces.html) consisting of: * A comprehensive guide to ARIN's database and registration records in the context of ARIN's operating principles and business rules. * A primer for Reg-RWS users looking to register reallocation/reassignment records or request reports using REST 2) HTML versions of Methods and Payloads documents: * https://www.arin.net/resources/restfulmethods.html * https://www.arin.net/resources/restfulpayloads.html ARIN encourages those participating in Reg-RWS to report any gaps, bugs or other user experience issues via the arin-tech-discuss mailing list. If you have not yet subscribed and are interested in conversations dealing with the ARIN technical staff to discuss Reg-RWS and other technical efforts, join the arin-tech-discuss list at: http://lists.arin.net/mailman/listinfo/arin-tech-discuss We look forward to your feedback. Regards, Mark Kosters Chief Technology Officer American Registry for Internet Numbers (ARIN) From info at arin.net Tue May 15 14:18:00 2012 From: info at arin.net (ARIN) Date: Tue, 15 May 2012 14:18:00 -0400 Subject: [arin-announce] ATTENTION: ARIN Payment Processing Alert Message-ID: <4FB29DD8.30909@arin.net> ARIN's payment processor is experiencing system responsiveness issues. Today, ARIN has received notice of several duplicate invoice payments by some community members. As an interim solution, when using ARIN's website to submit a payment, please be certain to only submit your payment request once, even if the user interface is slow to confirm payment. This will minimize the likelihood of duplicate payments being submitted. If a duplicate payment has been submitted, ARIN will refund the appropriate amount. ARIN has opened anincident ticket with the payment processor and will inform the community when this issue is resolved. Regards, Bob Stratton Chief Financial Officer American Registry for Internet Numbers From info at arin.net Tue May 15 15:06:58 2012 From: info at arin.net (ARIN) Date: Tue, 15 May 2012 15:06:58 -0400 Subject: [arin-announce] LAST CHANCE: ARIN Projects Survey Reminder Message-ID: <4FB2A952.1000501@arin.net> It is the last day to share your feedback on potential new services and improvements at ARIN. To gather community input on future upgrades and services, ARIN held a session to go over a list of both planned and unplanned activities at ARIN XXIX, and posted a survey for the community at: https://www.surveymonkey.com/s/ARINFutureProjectsSurvey ARIN management will use this feedback to help prioritize future work, so your input is important! To increase clarity, we have added more details to the descriptions of the items to be prioritized at: https://www.arin.net/features/#tbd The survey will closes today, and we are eager to hear from you! We look forward to hearing your thoughts as we set future development and service priorities. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Wed May 16 10:07:25 2012 From: info at arin.net (ARIN) Date: Wed, 16 May 2012 10:07:25 -0400 Subject: [arin-announce] =?windows-1252?q?Attention=3A_ARIN_Payment_Proces?= =?windows-1252?q?sing_Alert_=96_Issue_Resolved?= Message-ID: <4FB3B49D.3040809@arin.net> ARIN's payment processor has confirmed resolution of the issue announced yesterday. In the unlikely event, any community members are still experiencing problems, please contact the ARIN Billing Help Desk at 703-227-9886. Regards, Bob Stratton Chief Financial Officer American Registry for Internet Numbers From info at arin.net Tue May 22 15:31:14 2012 From: info at arin.net (ARIN) Date: Tue, 22 May 2012 15:31:14 -0400 Subject: [arin-announce] ARIN Board Adopts Bylaws Changes Message-ID: <4FBBE982.1020807@arin.net> The ARIN Board of Trustees adopted two Bylaws changes at its meeting on 23 April 2012. These changes include: * Allowing a non-candidate Board member to confirm the President's certification of the list of eligible voters. This non-candidate Board member shall be selected by the Board. Previously only the Secretary could confirm the President's review. * Petition signatures can now only be submitted by "eligible voters", which was changed from "General Members in good standing". This change makes the eligibility for signing petitions in sync with the eligibility for voting in the general elections, that only voters (and now petition signers) "of record on January 1st shall be eligible". ARIN's Bylaws are available at: https://www.arin.net/about_us/corp_docs/bylaws.html View these changes in the Bylaws change log at: https://www.arin.net/about_us/corp_docs/bylaws_changelog.html Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Thu May 24 16:02:10 2012 From: info at arin.net (ARIN) Date: Thu, 24 May 2012 16:02:10 -0400 Subject: [arin-announce] Update: Open Suggestions Consultation Message-ID: <4FBE93C2.3040506@arin.net> As required by the ARIN Consultation and Suggestion Process, ARIN held a consultation on a number of open suggestions during the Public Policy Meeting in Vancouver and on the consultation mailing list to gather community feedback. Very little input was received. At the same time, we asked the community to complete a survey ranking the importance of a number of projects awaiting prioritization. These projects are published on the website at https://www.arin.net/features/. We received over forty survey responses. ARIN staff is currently discussing the best way forward given the community feedback, current workload, and remaining projects on the 2012 strategic plan, as well as available financial and staff resources. We will report back to the community on our findings by 15 June 2012. Regards, Nate Davis Chief Operating Officer America Registry for Internet Numbers (ARIN) From info at arin.net Tue May 29 10:46:47 2012 From: info at arin.net (ARIN) Date: Tue, 29 May 2012 10:46:47 -0400 Subject: [arin-announce] ATTENTION: ARIN Payment Processing Alert Message-ID: <4FC4E157.4010608@arin.net> ARIN's payment processor is again experiencing system responsiveness issues. ARIN has received notice of several duplicate invoice payments by some community members. As an interim solution, when using ARIN's website to submit a payment, please be certain to only submit your payment request once, even if the user interface is slow to confirm payment. This will minimize the likelihood of duplicate payments being submitted. If a duplicate payment has been submitted, ARIN will refund the appropriate amount. ARIN has opened an incident ticket with the payment processor and will inform the community when this issue is resolved. Regards, Bob Stratton Chief Financial Officer American Registry for Internet Numbers From info at arin.net Tue May 29 15:04:55 2012 From: info at arin.net (ARIN) Date: Tue, 29 May 2012 15:04:55 -0400 Subject: [arin-announce] Proposed Revision to the ARIN Policy Development Process Message-ID: <4FC51DD7.5070705@arin.net> ARIN is consulting with the community in regards to the attached revised Policy Development Process (PDP) for Internet number resource policy development in the ARIN region. Significant changes in this revision of the PDP include: - Improved definition of the scope of the PDP process - Clarified principles for good number resource policy, i.e. it is fair/impartial, technically sound, and has the support of the community - Clarified Board criteria for ratification of developed policies - Added a role for the ARIN Advisory Council (AC) to perform an initial review of each new policy proposal to confirm that it is clear and in scope of the PDP - Changed the process so all clear, in-scope policy proposals become draft policies upon successful initial review - Added requirement for the AC to provide a full explanation of any policy action taken - One petition per policy action; if successful, petitioners mutually select the presenter of the draft policy at PPM There are three parts: Part One is the goals of the PDP, Part Two is the PDP itself, and Part Three is the PDP Petition Process. The initial consultation posting, including a link to the text of the revised Policy Development Process and a flowchart are available at: https://www.arin.net/participate/acsp/community_consult/05-29-2012_pdp.html Please provide comments to arin-consult at arin.net. You can subscribe to this mailing list at: http://lists.arin.net/mailman/listinfo/arin-consult. Discussion on arin-consult at arin.net will close on 28 June 2012 (30 days). ARIN seeks clear direction through community input, so your feedback is important. If you have any questions, please contact us at info at arin.net. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) ## * ## PART ONE ? ARIN POLICY DEVELOPMENT PROCESS GOALS 1. Purpose This document describes the ARIN Policy Development Process (PDP). The ARIN PDP is the process by which policies for the management of Internet number resources in the ARIN region are developed by the community. These Internet number resource policies are developed in an open and transparent manner that allows anyone to participate in the process. The PDP is designed to bring forth clear, technically sound and useful policies for ARIN to use in the management and administration of Internet number resources. To accomplish this goal, the PDP charges the community-elected ARIN Advisory Council (AC) as the primary policy development body with appropriate checks and balances on its performance in that role. Part One of this document provides the underlying goals for the Policy Development Process (including its purpose, scope, principles, and criteria for policy changes) and Part Two details the specific Policy Development Process used for development of changes to Internet number resource policy. Part Three details the processes for petitioning specific aspects of the Policy Development Process. 2. Definitions Internet Number Resources Internet number resources consist of Internet Protocol version 4 (IPv4) address space, Internet Protocol version 6 (IPv6) address space, and Autonomous System (AS) numbers. Policy Proposal An idea for a policy that is submitted to the Policy Development Process. Members of the ARIN Advisory Council and ARIN staff work with the originator to refine the Policy Proposal so that it contains a clear statement of the existing problem with Internet number resource policy and suggested changes to Internet number resource policy text to address the problem. In cooperation with ARIN staff, the ARIN AC also confirms each Policy Proposal is within scope (per Section 3) of the Policy Development Process. Draft Policy A Policy Proposal that is complete and in scope for the PDP is accepted by the Advisory Council and becomes a Draft Policy. The Advisory Council further develops the Draft Policy, working in cooperation with the policy originator if available. A Draft Policy, once fully developed, consists of a clear problem statement, proposed changes to number resource policy text, and an assessment of the conformance of the Draft Policy to ARIN?s Principles of Internet Number Resource Policy (as specified in Part One, Section 4 of the Policy Development Process.) Recommended Draft Policy A Recommended Draft Policy is the result of a Draft Policy being fully developed (containing clear problem statement, proposed changes to policy text, and an assessment of conformance to the PDP principles) and then being recommended for adoption by action of the ARIN Advisory Council. A Draft Policy becomes a Recommended Draft Policy once the Advisory Council believes with a high likelihood that the Draft Policy satisfies ARIN?s Principles of Internet Number Resource Policy. Recommended Draft Policies must undergo community consultation and a ?Last Call? period before being considered for adoption. Adopted Policy A policy that has been adopted by the ARIN Board of Trustees. Adopted Policies are incorporated into ARIN?s Number Resource Policy Manual (NRPM) as of their effective date. Public Policy Mailing List (PPML) The ARIN public mailing list for discussion of Internet number resource policy. Public Policy Consultation (PPC) An open public discussion held by ARIN of Internet number resource policy that provides for the contemporaneous interaction and polling of in-person and remote participants. These consultations may be held at ARIN?s Public Policy Meetings and at other related forums as approved by the ARIN Board of Trustees. Public Policy Meeting (PPM) A public forum held periodically by ARIN that includes Public Policy Consultations of all Draft and Recommended Draft Policies. Public Policy Meetings are held at least annually, although Public Policy Consultations for individual draft policies may be held in between Public Policy Meetings in similar open forums. Petition An action initiated by any member of the community (including a proposal originator) if they are dissatisfied with the action taken by the Advisory Council regarding a specific Policy Proposal, Draft Policy or Recommended Draft Policy. 3. Scope of Internet Number Resource Policies 3.1. Policies, not Processes, Fees, or Services Internet number resource policies developed through the PDP describe the policies and guidelines to be followed in number resource management, not the procedures that ARIN staff will use to implement the policies. ARIN staff develops appropriate procedures to implement policies after they are adopted. Internet number resource policies are also distinctly separate from ARIN general business practices. ARIN's general business processes, fees, and services are not within the purview of the Policy Development Process, and while policies developed through the PDP may apply to ARIN?s service offering, they cannot define or establish ARIN fees or service offerings. All matters concerning fees and service offerings are part of the fiduciary responsibility of the Board of Trustees. Note that the ARIN Consultation and Suggestion Process (ARIN ACSP) may be used to propose changes in non-policy areas. Changes to policy that are purely editorial in nature are beyond the scope of the Policy Development Process and may only be made with the concurrence of both the ARIN Advisory Council and ARIN Board of Trustees regarding their non-substantial nature. 3.2. Relevant and Applicable within the ARIN Region Policies developed through the PDP are community self-regulatory statements that govern ARIN?s actions in the management of Internet number resources. Policy statements must be applicable to some portion of the community for number resources managed within the ARIN region, and proposals to change policy must address a clearly defined, existing or potential problem with number resource policy in the region. Note that the Policy Development Process for global policies follows a similar process within each RIR region with the additional process of ratification by the Internet Corporation for Assigned Names and Numbers (ICANN). The Global Policy Development Process is separately documented and facilitated by the Address Supporting Organization Address Council (ASO AC), and in these circumstances, the ARIN PDP is also used in the development of number resource policies with global applicability. 4. Principles of Internet Number Resource Policy Internet number resource policy must satisfy three important principles, specifically: 1) enabling fair and impartial number resource administration, 2) technically sound (providing for uniqueness and usability of number resources), and 3) supported by the community. 4.1. Enabling Fair and Impartial Number Resource Administration Internet number resources must be managed with appropriate stewardship and care. Internet number resource policy must provide for fair and impartial management of resources according to unambiguous guidelines and criteria. All policy statements must be clear, complete, and concise, and any criteria that are defined in policy must be simple and obtainable. Policy statements must be unambiguous and not subject to varying degrees of interpretation. 4.2. Technically Sound Policies for Internet number resources management must be evaluated for soundness against three overarching technical requirements: conservation, aggregation and registration. More specifically, policies for managing Internet number resources must: ? Support both conservation and efficient utilization of Internet number resources to the extent feasible. Policy should maximize number resource availability to parties with operational need. ? Support the aggregation of Internet number resources in a hierarchical manner to the extent feasible. Policy should permit the routing scalability that is necessary for continued Internet growth. (Note that neither ARIN, nor its policies, can guarantee routability of any particular Internet number resource as that is dependent on the actions of the individual Internet operators.) ? Support the unique registration of Internet number resources. Policy should prevent to the extent feasible any unknown or duplicate use of Internet number resources that could disrupt Internet communications. Policies must achieve a technically sound balance of these requirements, and support for these technical requirements must be documented in the assessment of the policy change. 4.3. Supported by the Community Changes to policy must be shown to have a strong level of support in the community in order to be adopted. The determination of support is most commonly done via consideration at a Public Policy Consultation (PPC) or via online poll after discussion on the Public Policy Mailing List (PPML). The Policy Development Process, as a consensus-based collaborative development process, encourages incorporation of feedback received from participants where possible with the goal of increasing community support for policy changes. A strong level of community support for a policy change does not mean unanimous; it may be demonstrated by a subset of the community, as long as the policy change enjoys substantially more support than opposition in the community active in the discussion. 5. ARIN Board of Trustees Criteria for Policy Changes In order to maintain fidelity to the duty performed by ARIN on behalf of the Internet community, changes to Internet number resource policy must meet two specific criteria before being adopted by the ARIN Board of Trustees: 1) in compliance with law and ARIN?s mission, and 2) developed via open and transparent processes. 5.1. In Compliance with Law and ARIN?s Mission Policies developed through the PDP must advance ARIN?s mission, not create unreasonable fiduciary or liability risk, and must be consistent with ARIN's Articles of Incorporation, Bylaws, and all applicable laws and regulations. 5.2. Developed by Open & Transparent Processes Changes to policy must be developed via open and transparent processes that provide for participation by all. Policies must be considered in an open, publicly accessible forum as part of the adoption process. Policy discussions in the ARIN region are conducted on the Public Policy Mail List (PPML) and via Public Policy Consultation (PPC). There are no requirements for participation other than adherence to the guidelines of behavior and decorum, and anyone interested in following the process may subscribe to the PPML or may attend a PPC in person or via remote participation methods. All aspects of the PDP are documented and publicly available via the ARIN website. The PPML is archived. The proceedings of each PPM are published. All policies are documented in the Number Resource Policy Manual (NRPM). All Draft Policies are cross referenced to the original Policy Proposal, the archives of the PPML, all related PPC proceedings, and the minutes of the appropriate Advisory Council and the ARIN Board of Trustees meetings. The procedures that are developed to implement the policy are documented, publicly available, and followed by the ARIN staff. The Policy Development Process itself may only be changed by the ARIN Board of Trustees after a public consultation period to consider the proposed changes. PART TWO ? THE POLICY DEVELOPMENT PROCESS This section provides the details of the ARIN Policy Development Process. A graphical flow depiction of the process is provided at Appendix A. All references to ?days? are calendar days. All ARIN Advisory Council decisions on policy matters require an affirmative roll call vote of the majority of the members of the full Advisory Council, unless otherwise specified. 1. The Policy Proposal Policy Proposals may be submitted to the ARIN Policy Development Process by anyone in the global Internet community except for members of the ARIN Board of Trustees or the ARIN staff. Policy Proposals may be submitted any time by sending them to policy at arin.net. Upon recipient of a new Policy Proposal, the ARIN staff assigns it a Policy Proposal number, posts the Policy Proposal to the public web site, and notifies the Advisory Council of a new Policy Proposal available for consideration. The Advisory Council designates one or more members to work with the policy originator as needed. The assigned AC members and ARIN staff will work with the originator as described below to prepare the Policy Proposal for evaluation by the Advisory Council. The assigned members of the Advisory Council work with the proposal originator by providing feedback regarding the clarity and understanding of the Policy Proposal. The merits of the Policy Proposal itself are not considered at this time; the Policy Proposal is revised as needed so that it contains a clear statement of the problem with existing Internet number resource policy, that any suggested changes to Internet number resource policy text are understandable to the ARIN staff and community, and to identify and correct any potential scope considerations of the Policy Proposal. The proposal originator may revise (or not) the Policy Proposal based on the feedback received. Once the originator and assigned members of the Advisory Council are satisfied with the scope and clarity of the Policy Proposal, it is evaluated by the Advisory Council. 2. Policy Proposal Evaluation During Policy Proposal evaluation, the Advisory Council does not evaluate the merits of Policy Proposal other than to confirm that the Policy Proposal is within scope of the Policy Development Process and contains a clear statement of the problem and suggested changes to number resource policy text. Upon submission to the Advisory Council (AC), each Policy Proposal is evaluated in a timely manner to determine if the Policy Proposal is within scope of the Policy Development Process. Policy Proposals which are determined by the Advisory Council to be out of scope (e.g. for not addressing a clearly defined existing or expected problem, or that propose solutions involving other than number resource policy in the region) are rejected at this point, and the Advisory Council announces the rejection of a Policy Proposal along with an explanation of its reasoning on the ARIN Public Policy Mailing List (PPML). The Advisory Council also evaluates whether the Policy Proposal contains a clear statement of the existing problem with Internet number resource policy including suggested changes to number resource policy text to address the problem. Once this has been confirmed, the Advisory Council accepts it as a Draft Policy for further development work with the community. The Advisory Council announces the acceptance of a Policy Proposal as a Draft Policy on the ARIN Public Policy Mailing List (PPML) and encourages community discussion of its merits and concerns. Policy Proposals that are determined by the Advisory Council to lack clarity are remanded back to the originator along with an explanation of the areas needing improvements in clarity. The proposal originator revises the Policy Proposal based on the feedback received, and again offers the revised Policy Proposal for evaluation by the Advisory Council. The Advisory Council maintains a docket of all Policy Proposals. A submitted Policy Proposal that is not rejected upon evaluation as being out of scope remains on the docket as a Policy Proposal until it is withdrawn by originator or accepted by the Advisory Council as a Draft Policy. Remanded Policy Proposals that are not revised by the originator within 60 days are deemed abandoned. 3. Draft Policy Discussion and Development The Advisory Council is responsible for the development of policies to meet ARIN?s Principles of Internet Number Resource Policy (as described in Part One, Section 4). The Advisory Council maintains a docket of all Draft Policies. As part of the policy development effort, the Advisory Council participates in and encourages the discussion of the Draft Policies on the PPML, notes the merits and concerns raised, and then based on its understanding of the relevant issues, the Advisory Council may take various actions including abandoning, revising or merging the Draft Policy with other Draft Policies. To the extent that the policy originators are available and responsive, the Advisory Council includes them in the revision process. The Advisory Council may submit a Draft Policy at any time for a combined staff and legal review (and should do so after significant revisions to a Draft Policy). This review will be completed within 14 days. Upon receipt of the staff and legal review comments, the Advisory Council examines the comments to ensure their understanding and resolve any issues that may have been raised. The Advisory Council announces any actions taken on Draft Policies along with an explanation of its reasoning on the PPML. 4. Recommendation of Draft Policies The Advisory Council develops and refines Draft Policies until they are satisfied that the Draft Policy meets ARIN?s Principles of Internet Number Resource Policy (Part One, Section 4). Specifically, these principles are: ? Enabling Fair and Impartial Number Resource Administration ? Technically Sound ? Supported by the Community Guided by the discussion of the Draft Policy on the PPML, Public Policy Consultations with the community (if any) and its best judgment, the Advisory Council assesses the conformance of each Draft Policy to these principles and documents the result in an assessment section within the Draft Policy. Any specific concerns expressed by a significant portion of the community must be explicitly noted and addressed in the assessment of the policy change. Once a Draft Policy is fully developed and the Advisory Council is satisfied that it meets the principles of Internet number resource policy (including the support of the community based on online discussion that has occurred thus far), the Advisory Council recommends the Draft Policy for adoption. Recommended Draft Policies must undergo community consultation before proceeding to Last Call and being sent for consideration by the ARIN Board of Trustees. 5. Community Consultation and Public Policy Meetings ARIN holds periodic Public Policy Meetings (PPM) where the Advisory Council reports on the status of all Draft Policies and Recommended Draft Policies on its docket for discussion and feedback from the community. The presentation and discussion is referred to as a ?Public Policy Consultation?. Recommended Draft Policies may not be changed in the 30 days prior to its Public Policy Consultation. As each Draft Policy is presented for Public Policy Consultation, members of the Advisory Council will provide the arguments for and against adoption (petitioned items are handled per PDP Part Three: Petition Process). The Advisory Council participates in the discussion during the Public Policy Consultation, and notes significant merits and concerns that were raised in the discussion for inclusion in the policy assessment. Based on the feedback received and its best judgment, the Advisory Council revises the Draft Policy to address concerns raised where it will improve the overall community support for the policy change. Within the 60 days following a Public Policy Consultation on a Recommended Draft Policy, the Advisory Council reviews the result of the discussion (including any polls of support) and decides the appropriate next action. 6. Confirming Community Support for Recommended Draft Policies The Advisory Council confirms community support for Recommended Draft Policies, and this support may be ascertained by a show of hands during a Public Policy Consultation. The Advisory Council should carefully weigh the community support shown for a Recommended Draft Policy. Absence of clear community support is a strong indication that policy abandonment should be considered. A low level of overall support without opposition for a Recommended Draft Policy suggests further discussion of the merits of the policy change or abandonment. A clear split in the community support suggests that the Advisory Council should revise the Recommended Draft Policy to accommodate the concerns raised or further explain its consideration of the matter. A Recommended Draft Policy that has demonstrated clear support (and only relatively low opposition for well-understood reasons) may be advanced to Last Call by the Advisory Council within 60 days of its Public Policy Consultation. All Recommended Draft Policies not advanced to Last Call within 60 days of completion of their Public Policy Consultation will revert to Draft Policy status. 7. Last Call The Advisory Council advances Recommended Draft Policies with clear support to Last Call. Last Call provides an opportunity for final review by the community via discussion on the PPML. The last call period will be for a minimum of 14 days. The Advisory Council may decide that certain Recommended Draft Policies require a longer last call period of review (such as those that were revised based on comments received during Public Policy Consultation). If the Advisory Council sends a Recommended Draft Policy different than the Recommended Draft Policy presented during the Public Policy Consultation, then the Advisory Council will provide a detailed explanation for all changes to the text and these specific changes must have been discussed during the community consultation at the Public Policy Meeting. The Advisory Council will review the results of the Last Call discussion, and will determine if they still recommend adoption by the ARIN Board of Trustees. The Advisory Council may make minor editorial changes to a Recommended Draft Policy and reissue it for Last Call. No other changes may be made while the policy is in Last Call. A Recommended Draft Policy that has undergone a successful Last Call discussion may be sent to the ARIN Board of Trustees for adoption consideration. Decisions to send Recommended Draft Policies to the ARIN Board shall be made by the affirmative roll call vote of the two thirds of the members of the full Advisory Council. The results of the Advisory Council's decisions, and the reasons for them, are announced on the PPML. All recommended policies not sent to the ARIN Board of Trustees for consideration within 60 days of Last Call completion will revert to Draft Policy status. 8. Board of Trustees Review The ARIN Board of Trustees evaluates a Recommended Draft Policy for adoption once it is received from the Advisory Council. In its review, the Board of Trustees evaluates the policy with respect to the Policy Development Goals of the PDP including specifically whether the ARIN Policy Development Process has been followed, and whether the policy is in compliance with law and ARIN?s mission. The Board of Trustees may adopt, reject or remand Recommended Draft Policies to the Advisory Council. All rejections will include an explanation. Remands will explain the need for further development. The Board of Trustees may also seek clarification from the Advisory Council without remanding the recommended policy. The results of the Board of Trustees? decision are announced on the ARIN Public Policy Mailing List (PPML). 9. Implementation The projected implementation date of the policy is announced at the time that adoption of the policy is announced. ARIN staff updates the Number Resource Policy Manual (NRPM) to include the adopted policy and implements and publishes a new version of the manual. 10. Special Policy Actions 10.1 Emergency PDP If urgently necessary pursuant to ARIN?s mission, the Board of Trustees may initiate policy by declaring an emergency and posting a Recommended Draft Policy on the PPML for discussion for a minimum of 14 days. The Advisory Council will review the Recommended Draft Policy within 7 days of the end of the discussion period and make a recommendation to the Board of Trustees. If the Board of Trustees adopts the policy, it will be presented at the next Public Policy Meeting for reconsideration. 10.2 Policy Suspension If, after a policy has been adopted, the Board receives credible information that a policy is flawed in such a way that it may cause significant problems if it continues to be followed, the Board of Trustees may suspend the policy and request a recommendation from the Advisory Council on how to proceed. The recommendation of the Advisory Council will be published for discussion on the PPML for a period of at least 14 days. The Board of Trustees will review the Advisory Council's recommendation and the PPML discussion. If suspended, the policy will be presented at the next scheduled Public Policy Meeting in accordance with the procedures outlined in this document. PART THREE ? PDP PETITION PROCESS This section provides the details of the petitions within the Policy Development Process. Petitions can be made at points where decisions are made in the policy process. Points where petitions are available are depicted on the main PDP flow diagram in Appendix A. All ?days? in the process below are calendar days. 1. Petition Principles 1.1 Available to the community Any member of the community may initiate a petition if they are dissatisfied with a specific action taken by the ARIN Advisory Council (AC) regarding a Policy Proposal, Draft Policy or Recommended Draft Policy. The petitioner does not have to be located in the ARIN region or associated with an organization that is a Member of ARIN; any party (including a Policy Proposal originator) with interest in policy development matters within the ARIN region may initiate a petition. Notwithstanding the above, ARIN Staff and ARIN Board of Trustees members may not initiate or be counted in support of petitions as these individuals already have a formally defined role in the Policy Development Process. 1.2 Petition Initiation and Process A petition may be initiated by sending an email message to the ARIN Public Policy Mailing List (PPML) clearly requesting a petition against a specific action as listed below and including a statement to the community on why the petition is warranted. ARIN Staff will confirm the validity of the petition and then announce the start of the petition period on the PPML mailing list. Until the close of the petition period, members of the community (as allowed to petition per 1.1 above) may be counted in support for an existing petition by sending an email message to the PPML clearly stating their support for the petition. Only one petition will be considered for a given policy action; all subsequent requests to petition for the same action within the petition period shall be considered as support for the original petition. The petition shall remain open for 5 days, at which time the ARIN Staff shall determine if the petition succeeds (a successful petition requires expressions of petition support from at least 10 different people from 10 different organizations unless otherwise specified.) A successful petition will result in a change of status for the Policy Proposal or Draft Policy as specified below. Staff and legal reviews will be conducted and published for Draft Policies that result from successful petitions. Successfully petitioned Draft Policies are presented for Public Policy Consultation at the next Public Policy Meeting by an individual chosen by the petition supporters, with preference given to the proposal originator. If consensus is not achieved in determining the presenter, then the President may facilitate the selection process. 2. Valid Petitions Petitions may be made regarding specific actions against Policy Proposals, Draft Policies, and Recommended Draft Policies as described below. 2.1. Petition against Abandonment or Rejection due to Out of Scope The Advisory Council?s decision to abandon a Policy Proposal, Draft Policy or Recommended Draft Policy may be petitioned. Petitions may be initiated within the 5 days following the announcement date of an Advisory Council abandonment of a specific Policy Proposal or any Draft Policy. For sake of clarity, the ?announcement date? of an action shall be the publication date of the action in the ARIN AC draft minutes. Additionally, Policy Proposals that have not been accepted as a Draft Policy after 90 days may also be considered abandoned and petitioned to Draft Policy status at anytime. For a Policy Proposal that has been rejected due to being out of scope of the PDP, a successful petition will refer the question of whether the Policy Proposal is in scope to the ARIN Board of Trustees for consideration. For a petition against Draft Policy or Recommended Draft Policy abandonment, a successful petition will result in the Draft Policy being placed back on the Advisory Council docket under control of the petitioner and scheduled for public policy consultation at the next PPM. After the public consultation, control returns to the Advisory Council and subsequently may be revised or abandoned per the normal Policy Development Process. 2.2. Petition for Recommended Status Any member of the community may initiate a Petition for Recommended Status if they believe that a Draft Policy (either the original version as proposed or the current version) is fully developed to meet the requirements of Recommended Draft Policy, and the Advisory Council has not advanced the Draft Policy to Recommended Draft Policy status after 90 days as a Draft Policy. A successful petition for Recommended Status requires expressions of petition support from at least 15 different people from 15 different organizations. If successful, the petition will result in the Draft Policy being put under control of the petitioner, advanced to Recommended Draft status, and scheduled for public policy consultation at the next PPM. The resulting Recommended Draft Policy shall be under control of the Advisory Council after the public policy consultation and subsequently may be revised or abandoned per the normal Policy Development Process. 2.3. Petition for Last Call Any member of the community may initiate a Last Call Petition if they are dissatisfied with the Advisory Council?s failure to act within the allotted time (60 days) to advance a Recommended Draft Policy to last call. A successful Petition for Last Call requires expressions of petition support from at least 20 different people from 20 different organizations. If successful, the petition will move the Recommended Draft Policy as presented during its Public Policy Consultation to last call discussion and review by the community on the PPML. The Recommended Draft Policy shall be under the control of the Advisory Council after Last Call. 2.4. Petition for Board of Trustees Consideration Any member of the community may initiate a Board of Trustees Consideration Petition if they are dissatisfied with the Advisory Council?s failure to act within the allotted time (60 days) to send a Recommended Draft Policy in last call to the Board of Trustees for consideration. A successful petition for Board of Trustees Consideration requires expressions of petition support from at least 25 different people from 25 different organizations. If successful, this petition will send the Recommended Draft Policy from last call to the Board of Trustees for consideration. Appendix A - Draft PDP Flowchart The draft PDP text and flowchart are available at: https://www.arin.net/policy/pdp_proposed.html