Policy 2007-25: IPv6 Policy Housekeeping [Archived]

OUT OF DATE?

Here in the Vault, information is published in its final form and then not changed or updated. As a result, some content, specifically links to other pages and other references, may be out-of-date or no longer available.

Status: Adopted - NRPM Section 6.5

Tracking Information

Discussion Tracking

Mailing List:

Formal introduction on PPML on 5 September 2007

Staff assessment - 14 October 2007
Last Call - 23 October through 6 November 2007
Adopted - 11 December 2007Public Policy Mailing List

ARIN Public Policy Meeting:

ARIN XX

ARIN Advisory Council:

30 August 2007
20 September 2007
18 October 2007
15 November 2007
20 December 2007

ARIN Board of Trustees:

11 December 2007

Revisions:

Implementation:

14 February 2008

Author(s):

Leo Bicknell

Policy Proposal 2007-25
IPv6 Policy Housekeeping

Author: Leo Bicknell

Proposal type: modify

Policy term: permanent

Policy statement:

Change I:

In section 6.5.1.1.d, replace the existing statement with the new statement:

“be an existing, known ISP in the ARIN region or have a plan for making at least 200 end-site assignments to other organizations within 5 years.”

Change J:

Remove section 6.5.3 entirely. Update all subsequent sections to have new section numbers (6.5.[n-1]).

Replace part of the text as (new) section 6.5.4.4:

“All /56 and larger assignments to end sites are required to be registered either by the LIR or its subordinate ISPs in such a way that the RIR/NIR can properly evaluate the HD-Ratio when a subsequent allocation becomes necessary.”

Change K:

Section 6.5.8.2, add the following sentence to the end of the first paragraph:

“An HD-Ratio of .94 must be met for all assignments larger than a /48.”

Add to the end of the second paragraph:

“This reservation may be assigned to other organizations later, at ARIN’s discretion.”

Change L:

Section 6.5.8.3, add a sentence between the two existing sentences:

“Justification will be determined based on the .94 HD-Ratio metric.”

Rationale:

When the IPv6 policy was passed, it was considered to be an “interim” policy, and it was intended to be similar in all 5 RIR’s. Since that time it has become clear the policy is no longer interim (and proposal 2007-4 was passed to change just that) and it has also been modified separately in the different RIR’s.

It was brought to the ARIN AC’s attention that there were a number of problems with “Section 6” of the NRPM as a result of this legacy:

* The policy contained a large number of items that were not policy. * The policy contained a few items that were self contradictory. * The added text was redundant in some cases with existing text. * The policy was overly vague in a few areas, leaving ARIN staff to have to make interpretations of what the policy intended. * Policy changes made since the initial IPv6 policy was adopted have not always updated all of the relevant sections due to the complexity of section 6.

The intent of these changes is not to change any existing policy, but rather to remove all non-policy items, and update any ambiguous items with the way that ARIN staff is currently interprets the policy.

Change I:

Proposal 2005-8 amended section 6.5.4.1 to allow /56 and /64 allocations, but section 6.5.1.1.d was never updated to match the change. It is believed the intent of the policy, and ARIN staff’s current interpretation of the policy match the updated text.

Change J:

The first part is not policy, and incorrectly states there is no policy as section 6.5.4 has the policy in it. Take the one useful part and make it part of the 6.5.4 criteria.

Change K:

No metric is currently listed to justify a larger initial assignment. It is believed ARIN staff is currently applying the HD-Ratio similar to the ISP policy, this puts that in writing.

Make it clear that the reservation may not exist in perpetuity.

Change L:

No metric is given to justify additional assignments. It is believed that ARIN staff is currently applying the HD_Ratio similar to the ISP policy, this puts that in writing.

Timetable for implementation: Immediate

OUT OF DATE?

Here in the Vault, information is published in its final form and then not changed or updated. As a result, some content, specifically links to other pages and other references, may be out-of-date or no longer available.