Eleven draft policies were discussed, two of which were moved to last call, at the recent ARIN 36 meeting held 8-9 October 2015 in Montréal, Québec.
ARIN 36 attracted over 160 attendees and from the recap, we can see the level of dialogue was high and the attendees’ insightful commentary was a valuable contribution within the ARIN policy development process.
Read our event wrap for NANOG 65 and ARIN 36.
Following the Public Policy and Members Meeting, the ARIN Advisory Council (AC) met and the following statuses were reached for the two policies that moved to last call:
Recommended Draft Policy ARIN-2015-1: Modification to Criteria for IPv6 Initial End-User Assignments proposes an extension of IPv6 assignment criteria to allow end-user organisations that do not qualify under existing policies, to receive a provider independent assignment if they manage a network encompassing at least 13 geographically dispersed sites.
Recommended Draft Policy ARIN-2015-4: Modify 8.2 section to better reflect how ARIN handles reorganizations proposes editorial changes to the ARIN Number Resource Policy Manual to clarify and clearly identify which parts of the Mergers and Acquisitions policies apply to company restructures.
Below is a list of where the 9 other policies stand. You can read the full ARIN 36 Public Policy Meeting Report here.
One draft adopted as a Recommended Draft Policy:
One draft was abandoned:
The ARIN AC continues to work on seven draft policies:
Learn more about ARIN policy
ARIN meetings provide an opportunity for the Internet community to engage in policy discussions to discuss draft Internet number resources policies, network with colleagues, and attend workshops and tutorials. Learn more about ARIN’s policy development process.
The next ARIN policy discussion forums will be at:
- ARIN Public Policy Consultation at NANOG 66 – February 2016, San Diego, California
- ARIN 37 Public Policy and Members Meeting – April 2016, Montego Bay, Jamaica
The views expressed by the authors of this blog are their own and do not necessarily reflect the views of APNIC. Please note a Code of Conduct applies to this blog.