Recommended Draft Policy ARIN-2014-12: Anti-hijack Policy

[ARIN]

Recommended Draft Policy ARIN-2014-12
Anti-hijack Policy

On 15 May 2014 the ARIN Advisory Council (AC) recommended
ARIN-2014-12 for adoption, making it a Recommended Draft Policy.

ARIN-2014-12 is below and can be found at:
https://www.arin.net/policy/proposals/2014_12.html

You are encouraged to discuss Draft Policy 2014-12 on the PPML prior to
the upcoming ARIN Public Policy Consultation at NANOG 61. Both the 
discussion on the list and at the meeting will be used by the ARIN 
Advisory Council to determine the community consensus for adopting this 
as policy.

The ARIN Policy Development Process can be found at:
https://www.arin.net/policy/pdp.html

Draft Policies and Proposals under discussion can be found at:
https://www.arin.net/policy/proposals/index.html

Regards,

Communications and Member Services
American Registry for Internet Numbers (ARIN)


## * ##


Recommended Draft Policy ARIN-2014-12
Anti-hijack Policy

Date: 19 May 2014

AC's assessment of conformance with the Principles of Internet Number 
Resource Policy:

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.  This policy appears strongly supported and non-controversial.

Problem Statement:

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.

Policy statement:

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.

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 
should be consistent with the existing ARIN minimum allocation sizes, 
unless small allocations are intended to be explicitly part of the 
experiment. If an organization requires more resource than stipulated by 
the minimum allocation sizes in force at the time of their request, 
their experimental documentation should have clearly described and 
justified why this is required.

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.

Comments:

a. Timetable for implementation: Immediate

b. Anything else:

#####

ARIN STAFF ASSESSMENT

Assessment of: Draft Policy ARIN-2014-12: Anti-hijack Policy

Date of Assessment:

1. Summary (Staff Understanding)

This  policy would clarify expectations for experimental allocations by 
requiring that all experimental allocations come from ARIN's Internet 
Resource space,  do not overlap any existing registrations, not be 
private or otherwise un-routable space, and be registered in Whois with 
a designation indicating that the registration is experimental with a 
comment indicating the end date of the experiment.

2. Comments

A.    ARIN Staff Comments

This policy could be implemented as written.

B.    ARIN General Counsel - Legal Assessment

The policy poses no significant legal issues.

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-12: Anti-hijack Policy

Date: 18 April 2014

Problem Statement:

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.


Policy statement:

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.


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

should be consistent with the existing ARIN minimum allocation sizes,

unless small allocations are intended to be explicitly part of the

experiment. If an organization requires more resource than stipulated by

the minimum allocation sizes in force at the time of their request,

their experimental documentation should have clearly described and

justified why this is required.


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.


Comments:

a. Timetable for implementation: Immediate

b. Anything else: