Draft Policy ARIN-2011-7: Compliance Requirement [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.
Formal introduction on PPML on 24 May 2011
Origin - ARIN-prop-126
Draft Policy - 24 May 2011 (with staff assessment)
Remains on the AC’s docket - 19 October 2011
Remains on the AC’s docket - 22 November 2011
Revised - 22 February 2012 (with staff assessment)
Abandoned by the AC - 30 April 2012
ARIN Public Policy Meeting:
ARIN Advisory Council:
Chris Grundemann and Owen DeLong
- 19 May 2011
- 23 June 2011
- 21 July 2011
- 18 August 2011
- 15 September 2011
- 14 October 2011
- 16 November 2011
- 15 December 2011
- 20 January 2012
- 16 February 2012
- 8 March 2012
- 25 April 2012
ARIN Board of Trustees:
Draft Policy ARIN-2011-7
Date: 22 February 2012
In section 12.4, replace:
Organizations found by ARIN to be materially out of compliance with current ARIN policy shall be requested or required to return resources as needed to bring them into (or reasonably close to) compliance.
Organizations found by ARIN to be out of compliance with current ARIN policy shall be required to update reassignment information or return resources as needed to bring them into (or reasonably close to) compliance.
(Leave paragraph 12.4.a. and 12.4.b. unchanged)
Replace section 12.5 with:
Except in cases of fraud when immediate action can be taken, an organization shall be given thirty (30) days to respond. If an organization fails to respond within thirty (30) days, ARIN may cease providing reverse DNS services to that organization. If progress of resource returns or record corrections has not occurred within sixty (60) days after ARIN initiated contact, ARIN shall cease providing reverse DNS services for the resources in question. ARIN shall negotiate a longer term with the organization if ARIN believes the organization is working in good faith to restore compliance and has a valid need for additional time.
Replace section 12.6 with:
At any time ninety (90) days after initial ARIN contact, ARIN may initiate the revocation of any resources issued by ARIN as required to bring the organization into overall compliance. Except in cases of fraud, or violations of policy, an organization shall be given a minimum of six months to effect a return. ARIN shall negotiate a longer term with the organization if ARIN believes the organization is working in good faith to restore compliance and has a valid need for additional time to renumber out of the affected blocks. ARIN shall follow the same guidelines for revocation that are required for voluntary return in paragraph 12.4.b. above.
Version 5 further addresses PPML and AC feedback since the last PPM.
Version 4 addresses all feedback received at the ARIN PPM in Philadelphia. Mostly small textual changes - does re-introduce the 6 month window for resource revocations (it now remains in section 12.6).
Version 3 addresses remaining legal concerns with specific wording.
Version 2 addresses several staff and legal concerns with the original text of this policy by clarifying the language and making it more concrete.
To date the community has not documented or firmly established use of an effective enforcement mechanism. This policy will support current policy and compel those who are allocated ARIN resources to maintain the proper WHOIS records in accordance with ARIN NRPM. While it is recognized this is not an absolute solution to ensure compliance, it is the best method under current ARIN policies.
Timetable for implementation: Immediate