-----BEGIN PGP SIGNED MESSAGE-----

At 2:49 +1000 22/7/97, Kevin Dinn wrote:

>>>I asked the same question at the ADNA board meeting and Peter gave me some
>>>insight into the staff load at Melb IT for processing requests. To
>>>roughly quote Peter - to be able to run a ".com.au" sized DNA he
>>>considered five staff a minimum considering the policy constrainsts of
>>>".com.au".
>>
>>Sure, but in a world where there are (say) 10 com.au DNA's operational,
>>would that still be true? One could argue that this would then only need
>>0.2 people-hours per week per operator, or one could argue that it would
>>actually get worse than Peter's existing level due to growth rates and
>>inter-DNA issues.
>>
>>Why try to guess this - why specify it at all, because reality just won't
>>match that number very well.
>
>Well, I could leave the clause out altogether I suppose (it's down to: "2.
>Must have at 1 full time employee or equivalent to devote to DN
>applications") what do people think?


I think it is worth using the existing .AU 2LDs as a guide to what is a
suitable staffing level.

In the case of .COM.AU, Peter has suggested that 5 full-time staff (or
equivalent) is a suitable number. Since COM.AU seems to currently be
functioning quite well, 5 is probably a good estimate.

However in the case of .ASN.AU and .GOV.AU, the situation is different. So
far as I know, these domains are run by one or two part-time staff. These
domains also function very well... certainly on a par with .COM.AU.

There may be justification for a new 2LD which, along the lines of .ASN.AU,
only has a limited number of potential registrants, and which does not
require the services of a full-time staff member. Similarly, there will
almost certainly be new 2LDs registered for which the requirement for one
full-time employee would be woefully inadequate.

I suggest that this requirement should also be moved to the Code of Conduct
under a new section regarding quality of service. I like Stephen's idea of
publishing registration request processing times. This should probably also
be extended to cover response time for queries as well.

Richard.

-----BEGIN PGP SIGNATURE-----
Version: 2.6.3i
Charset: noconv
Comment: Public Key: <http://interdomain.net.au/~rha/pgpkey.txt>

iQCUAwUBM9MXkDXPU7enfNnZAQEp5wP3Sj4GdIKnHDRP0po2e3bPhETg/qzifuVt
HYHO8zgkRKdDupgovxiEdIFcoYA0K0+AE3jguccW8d6bqArjgTfXvFau5L1WuLiE
svIMkMzyNPHqNVMYGnX2boYZGmvI0QDSbRrKSNbB7TPA1gUUadUtvQZR52Yz29Gm
i0/rV2KTOA==
=Idr5
-----END PGP SIGNATURE-----