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.
but that is how the portal works already, you don't *have* to be the co-ordinator for a subnet, the person reviewing the request can set the allocation as a sub-coordinator or as an end user. I.e. the person requesting the subnet does not automatically become co-ordinator for the subnet.
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.
then I guess we don't have a problem after all :-)
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.
again, the portal already does this (although we haven't activated the DNS functionality yet).
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.
the DNS functionality is a separate module and is not tied to the name of the IP/subnet, not everyone uses their callsign as the DNS name, and the functionality should exist to allow users to change their DNS entries, albeit with their co-ordinator overviewing the changes.
Chris