[arin-ppml] LAST CALL: Recommended Draft Policy ARIN-2014-12: Anti-hijack Policy
info at arin.net
Tue Jun 24 16:16:19 EDT 2014
The ARIN Advisory Council (AC) met on 19 June 2014 and decided to
send the following to an extended last call:
Recommended Draft Policy ARIN-2014-12: Anti-hijack Policy
The text has been revised. The AC provided the following:
"ARIN-2014-12 has been modified since the ARIN Advisory Council (AC)
recommended this policy on 15 May 2014, in the following ways;
1. The second and third sentences of the policy text were modified to
clarify the original policy intent regarding deviation from the minimum
allocation size, either smaller or larger as discussed on PPML. These
changes are considered editorial in nature and do not change the intent
of the policy.
2. A sentence was added to the policy statement reflecting the changes
to the policy text as discussed above."
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 15 July 2014. After last call the AC will conduct their
last call review.
The draft policy text is below and available at:
The ARIN Policy Development Process is available at:
Communications and Member Services
American Registry for Internet Numbers (ARIN)
## * ##
Recommended Draft Policy ARIN-2014-12
Date: 17 June 2014
AC's assessment of conformance with the Principles of Internet Number
ARIN-2014-12: Anti-hijack Policy enables fair, impartial, and
technically sound number resource administration by updating the
guidelines for the allocation of experimental resources to ensure all
such allocation are documented in Whois, noting their experimental
status, and provides these allocations may not overlap any other
allocations. Additionally, part of the original policy text has been
clarified through editorial changes.
ARIN should not give research organizations permission to hijack
prefixes that have already been allocated. Research organizations
announcing lit aggregates may receive sensitive production traffic
belonging to live networks during periods of instability.
Section 11.7 describes more than allocation size therefore updating the
section heading to something more accurate is appropriate.
Modify the section 11.7 heading to be more accurate. Modify the first
sentence to prohibit overlapping assignments. Add text at the end to
define how research allocations should be designated.
Modify the second and third sentences to clarify the original policy
intent regarding deviation from the minimum allocation size, smaller or
larger as discussed on PPML.
11.7 Resource Allocation Guidelines
The Numbering Resources requested come from the global Internet Resource
space, do not overlap currently assigned space, and are not from private
or other non-routable Internet Resource space. The allocation size shall
be consistent with the existing ARIN minimum allocation sizes, unless
smaller allocations are intended to be explicitly part of the
experiment. If an organization requires more resources than stipulated
by the minimum allocation size in force at the time of its request, the
request must clearly describe and justify why a larger allocation is
All research allocations must be registered publicly in whois. Each
research allocation will be designated as a research allocation with a
comment indicating when the allocation will end.
a. Timetable for implementation: Immediate
b. Anything else:
More information about the ARIN-PPML