On 7/06/2011 9:31 p.m., Jonathan Brewer wrote:

Here's an easy one:

> . No stated archive of old versions of the document. ��The entire
> document could change over time and it might not be possible to see when
> this was done.

It looks to me like the document is authored in Word or OpenOffice, then PDFs published to the website. The policy document should be entered into a document management system or code repository. The community should be able to do diffs all the way back to version 0.1.

Should there also be a policy of change notifications?

Should document changes be sent to this mailing list as an archive?�� ...and in a plain text format so that interested parties can perform diffs quickly?

In suggesting this I considered,

Q: Do you want the Network Operators List to be used as an archive?��

A: Yes.�� The list goes out to many known and unknown parties with off line systems that are not controlled by NZRS, so we can be assured that the historic information can't be tampered with and many parties can archive and compare the content if need arises.��

Q: Why not just create a NZRS list for such change announcements?��

A:�� I'm on dozens of lists and some of them eventually go to /dev/null�� Some things need to come to industry as a whole without the need to subscribe to every list under the sun.�� However I also agree that I don't want every 'seemingly important' thing thrown at me each day on this list either, and I'm sure there are many many others who are much more busy that I am.�� How important is this DNSSEC stuff to the community? - I can't answer that alone, we have to answer that one individually as a community.

D

-- 
Don Gould
31 Acheson Ave
Mairehau
Christchurch, New Zealand
Ph: + 64 3 348 7235
Mobile: + 64 21 114 0699
www.thinkdesignprint.co.nz