Recommended Draft Policy ARIN-2014-5: Remove 7.2 Lame Delegations [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: Implemented 17 September 2014
Tracking Information
Discussion Tracking
Mailing List:
Formal introduction on PPML on 29 January 2014
Origin - ARIN-prop-197
Draft Policy - 29 January 2014
Recommended Draft Policy - 21 April 2014
Last Call 24 June 2014 through 8 July 2014
AC moved to Board - 22 July 2014
Adopted, to be implemented - 13 August 2014
Implemented - 17 September 2014
ARIN Public Policy Meeting:
ARIN Advisory Council:
AC Shepherds:
Stacy Hughes, Robert Seastrom
ARIN Board of Trustees:
Revisions:
Implementation:
Recommended Draft Policy ARIN-2014-5
Remove 7.2 Lame Delegations
21 April 2014
AC’s assessment of conformance with the Principles of Internet Number Resource Policy:
“ARIN-2014-5: Remove 7.2 Lame Delegations enables fair and impartial number resource administration by removing a no-longer-relevant section of the NRPM. All of the changes in this draft policy have proven uncontroversial thus far, with substantially more hands for the policy than against.”
Problem Statement:
Section 7.2, asking ARIN to resolve Lame Delegations in in-addr.arpa, was established almost 10 years ago. While there may be real lameness problems in the in-addr.arpa tree, this should no longer be part of ARIN policy for two reasons:
- NRPM should primarily be used to determine when requestors do, and do not, qualify for number resources because that’s what ARIN’s purpose is relevant to. ARIN is not an operational technical body, and its policy should only regulate activities ARIN is designed to participate in.
1a) We don’t put text about how to operate Whois or RWhois or IRR in NRPM, so we should not put in text about how to operate DNS.
- ARIN has never effectively implemented this. If there’s still a need, it should be addressed directly with ARIN management and staff for prioritization.
Policy statement:
Remove section 7.2
Comments:
a.Timetable for implementation: Immediate
b.Anything else:
7.2. Lame Delegations in IN-ADDR.ARPA
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.
##########
ARIN Staff and Legal Assessment
ARIN-prop-2014-5 – “Remove 7.2 Lame Delegations”
Date of Assessment: 04 Mar 2014
- Summary (Staff Understanding)
This proposal would remove NRPM section 7.2 because it is out of scope for ARIN and because ARIN has never effectively implemented this policy.
- Comments
A. ARIN Staff Comments
· This proposal would not change current operational practice. When ARIN switched over to per-zone DNS management, we ran into some significant issues with lame detection and remediation and as a result, lame delegation testing was suspended.
o Issues included the lack of a clear definition of what a lame DNS server was, and the potential risk of removing misconfigured, but working reverse DNS servers.
· This proposal could be implemented as written.
B. ARIN General Counsel - Legal Assessment
The policy does not create legal concerns.
- Resource Impact
This policy would have minimal resource impact from an implementation aspect. It is estimated that implementation would occur within 3 months after ratification by the ARIN Board of Trustees. The following would be needed in order to implement:
· Updated guidelines
- Proposal Text
Problem Statement:
Section 7.2, asking ARIN to resolve Lame Delegations in in-addr.arpa, was established almost 10 years ago. While there may be real lameness problems in the in-addr.arpa tree, this should no longer be part of ARIN policy for two reasons:
- NRPM should primarily be used to determine when requestors do, and do not, qualify for number resources because that’s what ARIN’s purpose is relevant to. ARIN is not an operational technical body, and its policy should only regulate activities ARIN is designed to participate in.
1a) We don’t put text about how to operate Whois or RWhois or IRR in NRPM, so we should not put in text about how to operate DNS.
- ARIN has never effectively implemented this. If there’s still a need, it should be addressed directly with ARIN management and staff for prioritization.
Policy statement:
Remove section 7.2
Comments: a.Timetable for implementation: Immediate b.Anything else:
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.