[rfc-i] comments on draft-rfc-editor-errata-process-00

[Henrik Levkowetz]

On 2008-01-21 23:09 Danny McPherson said the following:
> On Dec 4, 2007, at 12:58 PM, Turner, Sean P. wrote:
...
>> 3. I know RFCs never change, but with errata they kind of do - so  
>> should we add a link/note in to the boilerplate either at the  
>> beginning or at the end of the RFC.
>>
> 
> This is somewhat akin to what BRC suggested and W3C employs today,
> as outlined in the text in Appendix A.
> 
>     1.  Brian Carpenter has suggested an approach similar to that  
> used by
>         W3C: Add a URL to every published RFC that points to its errata
>         (if any).
> 
>           For W3C examples, see:
> 
>              http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/ and
> 
>              http://www.w3.org/TR/2006/REC-xml-names-20060816
> 
>           They include the text:
> 
>              "Please refer to the <errata> for this document, which may
>               include some normative corrections."
> 
>           where <errata> is a hyperlink to the list of all errata or a
>           page that says:
> 
>              "There are no errata to this document yet."
> 
>         Similarly, a URL could be added to all (future) RFCs pointing to
>         where the relevant errata are posted.

An example of how this could look is the errata link which exists for
all RFCs with errata in their htmlized form at http://tools.ietf.org/html/,
e.g., http://tools.ietf.org/html/rfc4954 -- see the top right-hand corner
of the added header, under the standard-level indication.


	Henrik

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 155 bytes
Desc: OpenPGP digital signature
Url : http://mailman.rfc-editor.org/pipermail/rfc-interest/attachments/20080122/dcb0bcab/signature.bin