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

David Huberman David.Huberman at microsoft.com
Thu Mar 27 13:24:15 EDT 2014

Hello John,

Ah ok - that explains why I didn't recall seeing a discussion, thank you.

Will the policy author please reveal themselves and talk to us about
what's going on?  Unless my reading comprehension is poor, I'm
not understanding what's really going on here.


David R Huberman
Microsoft Corporation
Senior IT/OPS Program Manager (GFS)

From: Sweeting, John <john.sweeting at twcable.com>
Sent: Thursday, March 27, 2014 6:20 AM
To: David Huberman; arin-ppml at arin.net
Subject: Re: [arin-ppml] Draft Policy ARIN-2014-12: Anti-hijack Policy

Hi David,

Draft Policies only get posted to PPML once they are moved forward in the
process to that state. That being said it was just posted as a DP this
week, Tuesday. Discussions need to begin and it will also be presented and
discussed at the PPM in Chicago. This is in accordance with the current
PDP. Hope that helps.


On 3/26/14, 10:55 PM, "David Huberman" <David.Huberman at microsoft.com>

>Can someone show me where in the mailing list archives this policy was
>actively discussed on PPML? I can't find it.
>Alternatively, can the policy author or someone who strongly supports
>this policy please either post to the list or email me privately and clue
>me in?  I issued and managed almost every experimental assignment for
>almost 10 years from 2003 to 2013, and I am lost as to what this policy
>is saying.  I would like to be educated so I can support, or not support,
>the efforts that have been made here.
>Thank you!
>David R Huberman
>Microsoft Corporation
>Senior IT/OPS Program Manager (GFS)
>-----Original Message-----
>From: arin-ppml-bounces at arin.net [mailto:arin-ppml-bounces at arin.net] On
>Behalf Of ARIN
>Sent: Tuesday, March 25, 2014 11:28 AM
>To: arin-ppml at arin.net
>Subject: [arin-ppml] Draft Policy ARIN-2014-12: Anti-hijack Policy
>On 20 March 2014 the ARIN Advisory Council (AC) accepted
>"ARIN-prop-202 Anti-hijack Policy" as a Draft Policy.
>Draft Policy ARIN-2014-12 is below and can be found at:
>You are encouraged to discuss the merits and your concerns of Draft
>Policy 2014-12 on the Public Policy Mailing List.
>The AC will evaluate the discussion in order to assess the conformance of
>this draft policy with ARIN's Principles of Internet Number Resource
>Policy as stated in the PDP. Specifically, these principles are:
>   * Enabling Fair and Impartial Number Resource Administration
>   * Technically Sound
>   * Supported by the Community
>The ARIN Policy Development Process (PDP) can be found at:
>Draft Policies and Proposals under discussion can be found at:
>Communications and Member Services
>American Registry for Internet Numbers (ARIN)
>## * ##
>Draft Policy ARIN-2014-12
>Anti-hijack Policy
>Date: 25 March 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 and prohibit LOA's
>without allocations.
>11.7 Resource Allocation Guidelines
>The Numbering Resources requested come from the global Internet Resource
>space, do not overlap previously 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. ARIN will not issue a
>Letter of Authority (LOA) to route a research prefix unless the
>allocation is properly registered in whois.
>a. Timetable for implementation: Immediate b. Anything else:
>You are receiving this message because you are subscribed to the ARIN
>Public Policy Mailing List (ARIN-PPML at arin.net).
>Unsubscribe or manage your mailing list subscription at:
>Please contact info at arin.net if you experience any issues.
>You are receiving this message because you are subscribed to
>the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
>Unsubscribe or manage your mailing list subscription at:
>Please contact info at arin.net if you experience any issues.

This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.

More information about the ARIN-PPML mailing list