[ppml] Policy Proposal: Modification to Reverse Mapping Policy

[Brian Dickson]

I support the proposal, although I would like to see a modification of 
the language proposed,
specifically:

Member Services wrote:
> 7.2.1 Lame Delegation
>
> A delegation is defined as being lame if all of the in-addr.arpa zones
> for a given name server of a specific network registration are lame. An
> in- addr.arpa zone is defined as lame when ARIN requests the SOA record
> from the name server registered in whois, but does not receive an answer.
>
>   
This subsection should be about lame *servers*, not delegations.

A delegation is the delegation of a zone, to *multiple* servers, and is 
only lame if *all* servers are lame
for *that* zone.

s/Delegation/Server/
s/delegation/server/

7.2.1 Lame Server

A server is defined as being lame if all of the in-addr.arpa zones
for the specific name server of a specific network registration are lame.
An in-addr.arpa zone is defined as lame when ARIN requests the SOA record
from the name server registered in whois, but does not receive an answer
(within 30s on 3 successive queries).


> 7.2.2 Partially Lame Delegation
>
> A delegation is defined as being partially lame if at least one in-
> addr.arpa zone for a given name server of a specific network
> registration is lame. An in- addr.arpa zone is defined as lame when ARIN
> requests the SOA record from the name server registered in whois, but
> does not receive an answer.
>   
s/Partially Lame Delegation/Lame Zone Delegation/

7.2.2 Lame Zone Delegation

A zone delegation is defined as being lame if the
in-addr.arpa zone of a specific network registration is
lame, for all listed name servers. An in-addr.arpa zone
is defined as lame when ARIN requests the SOA record
from the name server registered in whois, but does not
receive an answer (within 30s on 3 successive queries).

Brian Dickson