Recommended Draft Policy ARIN-2014-5: Remove 7.2 Lame Delegations
ARIN
info at arin.net
Mon Apr 21 14:43:26 EDT 2014
Recommended Draft Policy ARIN-2014-5
Remove 7.2 Lame Delegations
On 16 April 2014 the ARIN Advisory Council (AC) recommended
ARIN-2014-5 for adoption, making it a Recommended Draft Policy.
ARIN-2014-5 is below and can be found at:
https://www.arin.net/policy/proposals/2014_5.html
You are encouraged to discuss Draft Policy 2014-5 on the PPML prior to
the upcoming ARIN Public Policy Consultation at NANOG 61. Both the
discussion on the list and at the meeting will be used by the ARIN
Advisory Council to determine the community consensus for adopting this
as policy.
The ARIN Policy Development Process can be found at:
https://www.arin.net/policy/pdp.html
Draft Policies and Proposals under discussion can be found at:
https://www.arin.net/policy/proposals/index.html
Regards,
Communications and Member Services
American Registry for Internet Numbers (ARIN)
## * ##
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:
1) 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.
2) 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
1. 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.
2. 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.
3. 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
4. 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:
1) 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.
2) 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:
More information about the Info
mailing list