This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[ipv6-wg] RIPE 554 Errata Page
- Previous message (by thread): [ipv6-wg] RIPE 554 Errata Page
- Next message (by thread): [ipv6-wg] RIPE 554 Errata Page
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
MarcoH
marcoh at marcoh.net
Mon May 27 10:15:42 CEST 2013
> On 5/26/13 8:50 PM, Wilhelm Boeddinghaus wrote: >> Dear colleagues, >> >> as shortly discussed in Dublin I suggest to set up an errata page for the RIPE 554 document. Errors have been found, and we cannot change anything in the document without getting a new RIPE document number. But having to many different versions of the document confuses our audience. >> >> A errata page would make it possible to document minor but important changes of the content of the document. >> >> If the group says "yes" we could ask RIPE to help with a page like this. It should be easily reachable from the download page of RIPE554. > We need to make RIPE-554 a "living-document" of some sort, as we need to be able to correct typos, fix the newly found flaws and update the RFC numbers as they evolve. It should not be a "living document" IMHO, it should provide a stable anchor for people to reference. Any major change should actually result in a new document and to me that includes new or updated RFCs. Now with typos that is something different, mistakes happen and I agree that releasing a new reference to correct a comma or two swapped numbers (as is the case), we might need an errata list instead of pushing for a complete new document. > If that's achieved through an errata - I'm fine with that :) This has also been raised with the Working Group chair collective as it means a small but important change from the way RIPE Documents are currently handled. Community feedback on this issue is really important as there are different ways to handle these issues, while maintaining a consistent document series of outstanding quality, Marco Hogewoning Co-chair of the IPv6 working group
- Previous message (by thread): [ipv6-wg] RIPE 554 Errata Page
- Next message (by thread): [ipv6-wg] RIPE 554 Errata Page
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]