[arin-ppml] Draft Policy ARIN-2014-12: Anti-hijack Policy

David Farmer farmer at umn.edu
Mon May 5 20:28:43 EDT 2014


I also realized that "and prohibit LOA's without allocations" needed to 
be removed from the description of the policy statement, for much the 
same reason as #2 below.  The annotated text below has been modified to 
strike-through this text as well.  There are no changes to the policy 
text that would go in the NRPM.  Also included below is a final clean 
version of the text.

If there are any comments, please get them in soon, otherwise I'll 
assume continued support for this draft as modified.

Thanks.

On 4/18/14, 17:38 , David Farmer wrote:
>
> Draft Policy ARIN-2014-12 "Anti-hijack Policy," was discussed at ARIN 
> 33 in Chicago this week, it was generally supported. However, there 
> were two modifications to the Policy Text suggested;
>
> 1.  In the first paragraph; change "previously" to "currently".
>
> 2.  Remove the last sentence of the second paragraph;  This sentence 
> implies that ARIN should issue an LOA, where as ARIN should NOT issue 
> any LOA at all, expect for resources assigned to ARIN for its 
> operational use. ARIN should record the allocation to the receiving 
> organization in its public database, then the organization with the 
> allocation may issue any LOA necessary.
>
> Are there any additional comments or suggestions for the AC to consider?
>
> Otherwise, the AC will consider the advancement of the modified text 
> to Recommended Draft Policy status.
>
> -----
>
> Draft Policy ARIN-2014-12
> Anti-hijack Policy
>
> 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 and prohibit 
> LOA's without allocations.
>
> Annotated text
>
> 11.7 Policy Text for NRPM
> Original 2014-12 Policy Text
> Proposed Changes to 2014-12 Policy Text
>
> 11.7 Resource Allocation SizeGuidelines
>
>
> The Numbering Resources requested come from the global Internet 
> Resource space, do not overlap previouslycurrentlyassigned 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. ARIN will not issue a 
> Letter of Authority (LOA) to route a research prefix unless the 
> allocation is properly registered in whois.

Here is the final clean version of the text;

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

Date: 5 May 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:

-- 
================================================
David Farmer               Email: farmer at umn.edu
Office of Information Technology
University of Minnesota
2218 University Ave SE     Phone: 1-612-626-0815
Minneapolis, MN 55414-3029  Cell: 1-612-812-9952
================================================

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20140505/3edfeecc/attachment.html>


More information about the ARIN-PPML mailing list