[ipv6-wg] RIPE 554 Errata Page

[disclaimer: I work for the RIPE NCC]
[claimer: I co-authored a lot of RIPE documents]

Let us learn from prior art. The IETF has a lot of hard learned experience with maintaining a very successful series of consensus documents. We should learn from how the RFC series evolved and avoid repeating the mistakes in that history as much as possible.

For the most important lessons for the RIPE document series at this point in time are:

- Published RIPE documents should never change at all. Reason: The texts are cached in thousands of places an a great variety of  media. This cache needs to be consistent.

- Typos and real errata should be published separately. IETF practice:

http://www.rfc-editor.org/errata.php

"Published RFCs never change. Although every published RFC has been submitted to careful proofreading by the RFC Editor and the author(s), errors do sometimes go undetected. Use the form on this page to query the errata database for entries related to an RFC. Errata are for the RFCs as available from rfc-editor.org. Search results from the RFC search engine will include hyperlinks to any corresponding errata entries."

I also strongly believe we should look into adding a "RIPE Document Editor" function that has the responsibility for the editorial quality of documents and exercises it in a well defined and transparent process that stays clear of any perception of giving anyone undue influence on the content of documents.

Daniel