[ppml] Policy Proposal 2005-3: Lame Delegations

[Glenn Wiltse]

 I still have many concerns about this policy, as currently written and
proposed. However in the interest of trying to help get something changed
now, that may help ARIN staff actualy do what policy intends without
overly burdening the current staff, I will suggest the following that
would make this proposal less objectionable to me.

 I think at the very minimum there should be some statement that
indicates how long a lame delegation has been known to be 'lame'
before that lame delegation is to be removed. Say, something like
the following...

"After attempting to contact the domain holder and confirming that the
lame delegation persists for a minimum of 45 days, ARIN will update
the database that will result in a removal of the lame delegation."

 A statment simmilar to that, would at least give some clarity to
what would minimaly take place before any removal of delegations would
occur, and I think this would be a good thing.

 FYI -  I took most of those words directly from the APNIC's policy, which
incedentaly is even more detailed then ARIN's currently is...

http://www.apnic.net/services/rev-del/index.html


Glenn Wiltse

On Fri, 18 Mar 2005, Member Services wrote:
> 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
> NRPM.
>
> 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