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

5 Feb 2013

44net-request(a)hamradio.ucsd.edu wrote:
...
   >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.  That's just a learning curve
which is easily fixed. 
I think it is better to have the learning curve once and not for every user.
It is already very unclear to me (as an expert in IP addressing and a long-time
co-ordinator)
what the system will exactly do when I perform certain actions, and I think it will be
nothing
short of a mystery to those that just want an address and have no idea how IP addresses
are structured, what subnets are, and how DNS fits in.

...

  >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.  The
system is flexible, if that is how you want to administer the subnet you are responsible
for, then go ahead, all your allocations will therefore be to end users instead of
regional co-ordinators and it will be your responsibility to keep the portal up to date
and if there are any problems, you will be the point of contact to respond and fix the
problem. It's more work for you, but if that is how you prefer to manage your subnet I
don't see a problem.

 I guess what we need is a facility for co-ordinators to enter allocations to end users
manually, I can sort that out.

 Regards,
 Chris
 I don't mind if users can submit requests for subnets via the system, as long
as that does not automatically
mean that they become the co-ordinator for that subnet.  They get the adressing space,
submit the
requests for names within that space, and I validate them.  That is how it has always
worked, and
it has served well to prevent silly stuff like non-callsign entries directly under
ampr.org from appearing
within the 44.137 subnet.

For single adresses, it would be preferable if there is a single request form that
supplies both the name
and desired subnet, and leaves the assignment of the address to the co-ordinator, who
approves
the entire request in a single action.
But if that is too much programming work and it is more convenient to leave the separation
between
address assignment and DNS mapping, that is not a real problem because of the current rate
of
requests.

Rob

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