I've followed up with a call to auDA this morning. 

The response I got was basically that anyone concerned with the WHOIS
policy (or any other policy) should sent an
opinion/submission/suggestion to the Policy Manager at auDA via email,
at any time.

The WHOIS Policy is being reviewed this year, which is a great step. I
just hope everyone which has any concern with the current policy of
publishing email addresses in the way they are currently published
(and any other issue) will submit when its reviewed. In fact, you may
as well email the Policy Manager and submit your view now.

Regards,

Michael Purse

On 7/21/05, Michael Purse <pursey&#167;gmail.com> wrote:
> Yeah, I actually called auDA and spoke with Adam at about 10am this
> morning. Adam of course, couldnt tell me much as it isnt his job to.
> Unfortunately I was away from my home at the time when Jo returned my
> call, and haven't spoken to them again yet.
> 
> I'll follow this up in the morning, because its something I noticed a
> little while back.
> 
> Cheers,
> 
> Michael
> 
> On 7/21/05, Jason Allen <jallen&#167;pobox.com> wrote:
> > Marty Drill - Domain Candy wrote:
> >
> > >  auDA have confirmed today that there will be a Whois policy at some point
> > > this year. Possibly later in the year.
> > >
> > > I suggest it will be open for Public comments and opinions can be submitted
> > > at that time.
> >
> > Did they also let you know why it will be 12 months overdue? According
> > to the WHOIS policy, it is to be reviewed every 12 months, with the last
> > one being in Aug '03. Seems auDA aren't doing they're job?
> >
> > --
> > Cheers,
> > Jason
> >
> > --
> > This e-mail was scanned with a private,
> > non-commercial version of AntiVir MailGate.
> > See http://www.antivir.de for details.
> >
> > ---------------------------------------------------------------------------
> > List policy, unsubscribing and archives => http://dotau.org/
> > Please do not retransmit articles on this list without permission of the
> > author, further information at the above URL.
> >
> >
>