In my previous posting (about Antony's FAQ), djk wrote:

] IMHO assumptions like these contributed to the speed of progress made
] by ADNA.

I don't think there has yet been a post mortem on ADNA, but if you want
to follow the same path it took, while the body is still warm(ish), then
I think it would be appropriate to spend some time thinking about how
to avoid the same mistakes.

Personally I would rather follow the sort of path asn.au is taking
(bite-sized acheivable chunks for which you can demonstrate tangible
progress, rather than trying to solve all the country's problems at once).

Once you have some runs on the board, it gives you credibility and makes
it much more likely that important people will take you seriously and
join the next stage of your effort.

I think after the top-down approach (ADNA) has failed, it is now time
to look at a bottom-up approach.

So to be concrete about this, I suggest
(1) Identify things that are "broken" in *.AU DNS, and which might be
    fixed by changes in governance or policy.
(2) Out of that list (which may never be complete), pick one or two
    things which are broadly considered to be broken, and where there
    is rough agreement about what direction to go.  Fixing these are
    our short-term objectives for now.
(3) Some people start working on the things picked in (2).  As they
    find pre-requisites for fixing their things that aren't already done
    (a common dispute resolution procedure might be an example), identify
    them to the DNS list, and try to get someone working on them also.

The idea is rather than coming up with a laundry list of "nice to haves"
and doing a little bit of each one, we focus on some specific objectives/
outcomes which seem acheivable in the short term.

As we find infrastructure and policy that needs to be addressed for
those specific objectives to be acheived, we work on those too.
In Unix terms, rather than having a big statically linked program,
we do dynamic loading of modules as we need them, so that we can
keep each component a managable size. 

This is not to say we should never work on a top-down approach, or
tackle the bigger issues.  But we should recognise that they take
time, and we should still be able to make progress at the coal-face
while the big issues are being tackled.
__________________________________________________________________________
 David Keegel <djk&#167;cyber.com.au>  URL: http://www.cyber.com.au/users/djk/
Cybersource P/L: Unix Systems Administration and TCP/IP network management