Why does the assumption live that vendors can easily live with changing numbers? It takes a lot of work to say product xyz supports RIPExxxx on each element within the document. A new document will make it required that the check for support is completely redone. In addition it would very good if the context of document RIPExxxx is not-changed with exception of spelling mistakes etc. How otherwise a vendor can say product xyz support RIPExxxxx on 1 Jan 2013 and assume that RIPExxxx is still the same document on 1 Jan 2014? So, if the document content changes then the number should change... but not too frequently as that will reduce the value of the document. G/ -----Original Message----- From: ipv6-wg-bounces@ripe.net [mailto:ipv6-wg-bounces@ripe.net] On Behalf Of Wilhelm Boeddinghaus Sent: 27 May 2013 09:37 To: Peter Koch; ipv6-wg@ripe.net Subject: Re: [ipv6-wg] RIPE 554 Errata Page Am 26.05.2013 23:10, schrieb Peter Koch:
On Sun, May 26, 2013 at 08:50:05PM +0200, Wilhelm Boeddinghaus wrote:
anything in the document without getting a new RIPE document number. But having to many different versions of the document confuses our audience. why is the audience less confused by the same number referencing different content?
-Peter
The audience for this document are the enterprises and public administration. They need help when they set up a tender. The vendors can live with changing document numbers, but not the enterprises and public administration. If major changes have to be made to the document we need a new number. This is also true for new sections or new RFCs. -Wilhelm