27 May
2013
27 May
'13
12:07 a.m.
Hi Peter,
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?
This is about 'same content, but with typo's fixed', not about completely new content. If the content changes then I agree we need a new number. Otherwise we end up with references like 'RIPE-554, the version just before they replaced RFC xxxx with RFC yyyy'. Companies must still be able to say things like 'our products comply to RIPE-554' without any confusion. Cheers, Sander