2011-7 Previous Version [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.
View the current policy proposal text.
The following version was archived on 22 February 2011.
Draft Policy ARIN-2011-7
Compliance Requirement
Date: 22 September 2011
Policy statement:
Resource Review
Update the following NRPM Sections:
12.4 - Update to:
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.
- The degree to which an organization may remain out of compliance shall be based on the reasonable judgment of the ARIN staff and shall balance all facts known, including the organization’s utilization rate, available address pool, and other factors as appropriate so as to avoid forcing returns which will result in near-term additional requests or unnecessary route de-aggregation.
- To the extent possible, entire blocks should be returned. Partial address blocks shall be returned in such a way that the portion retained will comprise a single aggregate block.
(leave 12.5 as is)
12.6 - Update to:
Except in cases of fraud when immediate action can be taken, an organization shall be given a minimum of 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. At any time ninety (90) days after initial ARIN contact, ARIN may initiate resource
revocation as allowed in paragraph 12.5. ARIN may permit a longer period of time to come into compliance, if ARIN believes the organization is working in good faith to restore compliance with policy and has a valid need for additional time to comply, including but not limited to renumbering out of the affected blocks.
Rationale:
This version addresses remaining legal concerns with specific wording.
An earlier version addressed 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
The following version was archived on 22 September 2011.
Draft Policy ARIN-2011-7
Compliance Requirement
Date/version: 24 May 2011
Policy statement:
Resource Review
Update the following NRPM Sections:
12.4 - Update to:
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.
-
The degree to which an organization may remain out of compliance shall be based on the reasonable judgment of the ARIN staff and shall balance all facts known, including the organization’s utilization rate, available address pool, and other factors as appropriate so as to avoid forcing returns which will result in near-term additional requests or unnecessary route de-aggregation.
-
To the extent possible, entire blocks should be returned. Partial address blocks shall be returned in such a way that the portion retained will comprise a single aggregate block.
(leave 12.5 as is)
12.6 - Update to:
Except in cases of fraud, an organization shall be given a minimum of thirty (30) days to respond. If an organization does not respond within those thirty (30) days, ARIN may cease providing reverse DNS services to that organization. If progress of resource returns or record corrections is not visible within sixty (60) days after correspondence with ARIN began, ARIN will cease providing reverse DNS services for the resources in question. At any time after ninety (90) days have passed, ARIN may initiate resource revocation as allowed
in paragraph 12.5. ARIN shall negotiate a longer term with the organization if ARIN believes the organization is working in good faith to substantially restore compliance and has a valid need for additional time to renumber out of the affected blocks.
Rationale:
This version 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
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.