[ppml] Policy Proposal 2005-3: Lame Delegations
ARIN welcomes feedback and discussion about this policy proposal in the
weeks leading to the ARIN Public Policy Meeting in Orlando, Florida,
scheduled for April 18-20, 2005.
The policy proposal text is below and can be found at
Note that the author revised the text so that it is not specific to a
According to the ARIN Internet Resource Policy Evaluation Process the
ARIN Advisory Council will evaluate policy proposals after the Public
Policy Meeting. The feedback and discussion of policy proposals on the
Public Policy Mailing List will be included in the AC's evaluation.
Subscription information for the ARIN Public Policy Mailing List can be
found at http://www.arin.net/mailing_lists/index.html.
The ARIN Internet Resource Policy Evaluation Process can be found at
ARIN's Policy Proposal Archive can be found at
American Registry for Internet Numbers (ARIN)
### * ###
Policy Proposal 2005-3: Lame Delegations
Author name: Paul Andersen on behalf of the ARIN AC
Policy term: permanent
Policy statement: This policy proposal replaces section 7.2 of the ARIN
ARIN will actively identify lame DNS name server(s) for reverse address
delegations associated with address blocks allocated, assigned or
administered by ARIN. Upon identification of a lame delegation, ARIN
shall attempt to contact the POC for that resource and resolve the
issue. If, following due diligence, ARIN is unable to resolve the lame
delegation, ARIN will update the WHOIS database records resulting in the
removal of lame servers.
Rationale: The policy as stated could not be implemented without placing
an undue burden on ARIN staff resources. The procedures mandated in the
policy require a shifting of registration service resources from such
activities as IP Analyst support for on-going registration actions as
well as the telephonic and email help desks. Removing the procedures
from the policy allows the Director of Registration Services the
flexibility of meeting all registration services needs and managing the
identification, notification, and removal of lame delegations.
Timetable for implementation: 90 days after adoption