Remark on 193.in-addr.arpa procedures

Folks,

please have a read of the remark below. We sort of feel he Hakan has a point
here. Did we miss something ? If not, then I will change the procedures to
reflect this remark.

-Marten

------- Forwarded Message

Date:     Thu, 8 Apr 93 12:57:15 +0200
From:     hh at tip.net (Hakan Hansson)
To:       Marten.Terpstra at ripe.net
cc:       staff at tip.net
Subject:  Reachability of reverse servers.
	  

>			Guidelines for the delegation
>		   of zones in the 193.in-addr.arpa domain
...
>4. All reverse servers for blocks must be reachable from the whole of
>the Internet.  In short, all servers must meet similar connectivity
>requirements as top-level domain servers. 
...
>Procedures for the delegation of individual network zones
...
>3. At least two reverse servers must be reachable from the whole of the
>Internet.  In short, these servers must meet similar connectivity
>requirements as top-level domain servers. 

Marten,

I've been thinking about the above guidelines.
I fully agree with the statements in item 4 for block delegation, but I
now realize I don't agree on item 3 for individual networks.
I can't see why at least two reverse servers should be reachable from the
whole of Internet. It must be enough that they are equally reachable as the
actual network they are reverse serving for, or?
If a network doesn't have NSFnet connectivity (that is what we are talking
about, and should be mentioned in your document!), there is no need for
anyone at NSF to lookup the reverse zone for that network either.
These requriements don't apply to 192 networks, so why for 193?

Regards,
Hakan Hansson
 
== Unisource Business Networks Sverige AB
== Unidata IP Services * TIPnet NCC * Sweden
== phone +46-31-7708072 * fax +46-31-114664


------- End of Forwarded Message