[arin-ppml] Petition for advancement of Policy Proposal #168

[ARIN]

This petition did not receive the required 10 statements of support and 
was therefore not successful. ARIN-prop-168 is closed.

Regards,

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


On 7/19/12 5:51 PM, ARIN wrote:
> ARIN-prop-168 Promote 4byte ASN Usage
>
> The message below started a petition regarding the ARIN Advisory
> Council's decision to abandon ARIN-prop-168. The AC's decision was
> posted by ARIN staff to PPML on 26 June 2012.
>
> If successful, this petition will change ARIN-prop-168 into a Draft
> Policy which will be published for adoption discussion on the PPML and
> at the Public Policy Meeting in October 2012. If the petition fails,
> the proposal will be closed.
>
> For this petition to be successful, the petition needs statements of
> support from at least 10 different people from 10 different
> organizations. If you wish to support this petition, post a statement
> of support to PPML on this thread.
>
> The duration of the petition is five business days; it ends on 26 July
> 2012. ARIN staff will post the result of the petition to PPML.
>
> For more information on starting and participating in petitions, see
> PDP Petitions at:
> https://www.arin.net/policy/pdp_petitions.html
>
> The proposal text is below and at:
> https://www.arin.net/policy/proposals/index.html
>
> The ARIN Policy Development Process can be found at:
> https://www.arin.net/policy/pdp.html
>
> Regards,
>
> Communications and Member Services
> American Registry for Internet Numbers (ARIN)
>
>
> #####
>
>
>> -----Original Message-----
>> From: Joe Maimon <jmaimon at chl.com>
>> Date: Thu, 19 Jul 2012 15:26:48 -0400
>> To: "ppml >> \"ppml at arin.net\"" <ppml at arin.net>
>> Subject: [arin-ppml]  Petition for advancement of Policy Proposal #168
>>
>> All,
>>
>> Policy Proposal #168 Promote 4byte ASN Usage, was intended to deal with
>> the lack of uptake of 4byte ASN as well as the continued demand for
>> 2byte ASN.
>>
>> It does so by expanding on the capabilities of both the community and
>> ARIN with regards to ASN policy.
>>
>> I believe that more discussion on this topic is warranted. ARIN Staff
>> said as much at previous PPM and I was hoping that this proposal would
>> help do that.
>>
>> As such, the AC's abandonment of this proposal was disappointing to me.
>>
>> While it may not be as compelling and controversial as some of the
>> topics swirling through the list these days, ASN policy is important,
>> disproportionately so, to the newcomers of our community.
>>
>> I formally petition you, the members of this community, for your support
>> in advancing to draft policy status the proposal and for it to be
>> discussed at an upcoming ARIN Public Policy meeting.
>>
>> I ask you for statements in support of this petition.
>>
>> The full policy proposal text is available at
>>
>> http://lists.arin.net/pipermail/arin-ppml/2012-May/024892.html
>>
>> Best and my thanks,
>>
>> Joe
>>
>>
>>
>> _______________________________________________
>> PPML
>> 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:
>> http://lists.arin.net/mailman/listinfo/arin-ppml
>> Please contact info at arin.net if you experience any issues.
>
> ARIN-prop-168 Promote 4byte ASN Usage
>
> Proposal Originator: Joe Maimon
>
> Proposal Version: 1.1
>
> Date: 18 May 2012
>
> Proposal type: Modify
>
> Policy term: Temporary
>
> Policy statement:
>
> Add section 5.2
>
> 5.2 Guidelines
>
> ARIN will issue AS Numbers under the following guidelines.
>
> 5.2.1 Unused
>
> ARIN will attempt to assign to the organization an AS Number which has
> neither been previously assigned nor publicly used, as available.
>
> 5.2.2 Requests
>
> An organization may request from ARIN either a specific AS Number or
> type of AS Number, if available to ARIN. The organization must document
> to ARIN's satisfaction technical or real world justification for its
> request. ARIN may review the data directly with all involved parties.
>
> 5.2.3 Rectification
>
> ARIN may reuse the provided documentation in such public and private
> forums as it deems appropriate and useful to promote the rectification
> of issues documented via 5.2.2 request justification.
>
> 5.2.4 Restrictions
>
> Assignments received via 5.2.2 requests are additionally restricted from
> 8.3 transfers for a period of 24 months post assignment.
>
> 5.2.5 Release
>
> An organization can exchange the 5.2.2 number for a 5.2.1 number, after
> which time the restriction on transferring the assignment will be
> released.
>
> 5.2.6 Publication
>
> Section 5.2 neither requires nor recommends that ARIN publicize its
> available AS Numbers.
>
> 5.2.7 Expiration
>
> ARIN may retire section 5.2 anytime during a period of more than 24
> calendar months that have gone by without any completed 5.2.2 requests.
>
>
> Rationale:
>
> Changes from V1.0
>
> 5.2.1 "used" ->  "publicly used"
>
> 5.2.2 "must provide" ->  "must document"
>
> 5.2.2 "technical justification " ->  "technical or real world
> justification"
>
> 5.2.3 strike "with suitable privacy considerations in place"
>
> 5.2.3 "public forums" ->  "public or private forums"
>
> 5.2.3 "necessary to promote" ->  "appropriate and useful to promote"
>
> 5.2.3 "rectification of documented causes" ->  "rectification of issues
> documented via 5.2.2 request justification"
>
> 5.2.4 "being transferred" ->  "from 8.3 transfers"
>
> 5.2.7 "after a period of" ->  "during a period of more than"
>
> Unless otherwise requested, providing an ASN with no baggage or history
> should be preferential to both the organization and to ARIN.
>
> The restrictions and clauses regarding technical justification are
> designed for the promotion of 4byte ASN uptake and preservation of 2byte
> ASN's for those who truly need them. Additionally, this may help to
> assist in resolving apparently pervasive obstacles in the ARIN region to
> using 4byte ASN's.
>
> Further, if an organization does have a valid technical justification
> for a specific AS Number that is available, for example, when a network
> was built with an ASN that was subsequently reclaimed due to accidental
> negligence or other similar cases, there is little benefit to ARIN
> refusing to provide the organization what it can show it needs.
>
> ARIN need not publicize available ASNs but it may choose to do so if it
> is the most efficient and prudent method of implementation.
>
> Should this policy become a relic (we hope), ARIN is expressly
> authorized to excise it.
>
> Timetable for implementation: Immediate.
>
>
>