New subject: 44Net Digest, Vol 2, Issue 20

5 Feb 2013

44net-request(a)hamradio.ucsd.edu wrote:
...
  An example: if I'm the San Diego county
coordinator, and I assign a /24
 to AA6ZZ for a gateway in the Santee city area, he can become the
 coordinator for that /24, and assign addresses from his block of 256
 addresses to the clients of his gateway.

 Likewise:
 44.0.0.0/9 is assigned to the USA, with me as the current USA coordinator,
 44.124.0.0/16 is assigned to Arizona and handled by the AZ coordinator
 44.124.128.0/24 might be assigned to a gateway in Phoenix who would then
 handle address assignments for the clients of that gateway.

 So by registering gateway operators as coordinators for their gateway's
 subnet, we localize the network management to the people who are the
 best situated to handle it. 
But it has the disadvantage that you spread the rarely occurring task over many
people who do it only once and do not have the knowledge and skills to perform
it well.   I'm afraid this will lead to many wrong subnet specifications (already
seen),
strange names in the DNS, questions, etc.

I prefer to handle the task for the entire country and have the system only
administer what has been assigned, not delegate the subassignments. It is
a small country and I get only a couple of requests per year these days.

Rob

Re: [44net] 44Net Digest, Vol 2, Issue 20