Your IP address could not be determined at this time.

Draft Policies and Proposals

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

Implemented 17 September 2014

 
Discussion Tracking
Mailing List:
Formal introduction on PPML on 4 March 2014

Origin - ARIN-prop-202

Draft Policy - 25 March 2014

Recommended Draft Policy - 19 May 2014

Last Call 24 June 2014 through 15 July 2014

AC moved to Board - 22 July 2014

Adopted, to be implemented - 13 August 2014

Implemented - 17 September 2014

 

 

Public Policy Mailing List
ARIN Public Policy Meeting:

ARIN 33

ARIN PPC at NANOG 61

ARIN Advisory Council:

AC Shepherds:
David Farmer, Cathy Aronson

ARIN Board of Trustees: 18 July 2014
Revisions Implementation
Previous version(s) 17 September 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:
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-12
Anti-hijack Policy

Date: 17 June 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. Additionally, part of the original policy text has been
clarified through editorial changes.

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.

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 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:

#####

Older version

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:

Advanced Search

Relevant Links