14 Jan
2016
14 Jan
'16
1:05 p.m.
Why can't an automated system be tailored to particular allocation schemes?
Or have the policies for individual coordinators posted so that people
ask for the correct subnet the first time (and still reject requests
that don't match the pattern)?
Having a set of defined requirements from the existing coordinators
should make it possible to create automation that covers a large
percentage of the requests automatically, leaving the sticky situations
to be handled manually by the coordinators. Coordinators would still be
able (and encouraged!) to contact new users to help them with their
issues, but those that don't need the help would get running faster.
Win-win.
And yes, I'm willing to help produce the necessary automation.
Orchestrating automation is one of the facets of my day job. ;-)
- Richard, VE7CVS
On 1/13/16 11:10 PM, Marius Petrescu wrote:
(Please trim inclusions from previous messages)
_______________________________________________
The reason is simple why not to allow automatic requests:
The coordinators may have a certain IP allocation scheme in there
minds. Maybe regional, maybe some other criteria.
That means that not every request out of the blue fits that scheme.
So an IP range may be unallocated, but it does not fit the allocation
scheme.
An coordinator would change the requested one allocate the right one,
which would not happen in an automated system.
e.g. in YO, I allocate IP ranges based on regions, so that the first
number in the block fits the requestors region number (the same as in
the callsign).
I had requests like "please allocate 44.182.35.xx to me", the user
being in region 8.
It resulted in allocating the first unused 44.182.8x.xx /24 subnet to
him, and not the original requested one.
This would not have been possible in an automated system.
Marius, YO2LOJ