[rfc-i] What, never!?

Dave CROCKER dhc2 at dcrocker.net
Tue Feb 16 12:13:48 PST 2010


Sounds like the policy for the way to handle detecting an encoding error, when 
transmiting from paper to online, is retransmission of the correct bits.

Sound policy.


On 2/16/2010 10:59 AM, Bob Braden wrote:
> As you know, RFCs never change once published. However, the RFC-online
> process, that has been re-entering the "lost" early RFCs, brings up an
> exception.
> We recently got an Errata report for RFC 68, an RFC-online document that
> has been restored. We have generally tried hard to avoid NEW errors
> creeping into the restored documents, but in the case of RFC 68 we failed.
> Policy: an errata report for an error that existed in the original
> version of a restored RFC will be retained as an erratum and the error
> will be left in the repository. However, if the errata report specifies
> a transcription error that was added during restoration of the document
> online, then the RFC Editor will change the restored document to remove
> the transcription error.
> Thus, the RFC Editor will fix RFC 68 and delete the corresponding errata
> report.
> Bob Braden
> Acting RFC Series Editor
> Gilbert & Sullivan: "What, never!? No, never! What, never!? ..."
> _______________________________________________
> rfc-interest mailing list
> rfc-interest at rfc-editor.org
> http://mailman.rfc-editor.org/mailman/listinfo/rfc-interest


   Dave Crocker
   Brandenburg InternetWorking

More information about the rfc-interest mailing list