Re: [rsab] [IAB] Heads-up: errata processing for RFC related documents

[Alvaro Retana <[e-mail]>]

Hi!

All the RFCs below (except rfc8700) concern RFC production: requirements,
format, etc.  I agree with the proposal.

rfc8700 is not about producing RFCs or related policies; it is a
retrospective that includes personal points of view.  Will a future version
(even if 20 years away — for the 75th anniversary) be published in the
editorial stream?  Would it be developed/approved by the RSWG or the RSAB?
It seems any of that would be out of scope.  I realize this discussion is
only about errata handling, but it seems to me that it would be better to
leave it with the IAB.

My 1c,

Alvaro.

On March 13, 2024 at 11:41:24 AM, Mirja Kuehlewind (IETF) (
[e-mail]) wrote:

Hi all,

I’m discussing with the RPC the best process to handle future errata for
RFC Editor related documents. These documents have been published on the
IAB stream, and therefore the IAB (chair) is currently responsible for the
errata processing. However, future versions of these RFCs would/will be
published in the editorial stream and the RSAB (chair) will then be
responsible for errata process for these.

I suggest and still discussing some details with the RPC (Sandy in cc) that
the IAB makes an official decision to hand the errata processing for these
current IAB documents to the RSAB and note that officially down in the
minutes of the next formal business meeting (on Sunday).

In preparation for this, here is the current list of RFCs that are under
consideration:

RFC 5620 <https://www.rfc-editor.org/info/rfc5620> RFC Editor Model
(Version 1)
RFC 7669 <https://www.rfc-editor.org/info/rfc7669> Assigning Digital Object
Identifiers to RFCs
RFC 8728 <https://www.rfc-editor.org/info/rfc8728> RFC Editor Model
(Version 2)
RFC 9280 <https://www.rfc-editor.org/info/rfc9280> RFC Editor Model
(Version 3)
RFC 8729 <https://www.rfc-editor.org/info/rfc8729> The RFC Series and RFC
Editor
RFC 6949 <https://www.rfc-editor.org/info/rfc6949> RFC Series Format
Requirements and Future Development
RFC 7749 <https://www.rfc-editor.org/info/rfc7749> The "xml2rfc" Version 2
Vocabulary
RFC 7990 <https://www.rfc-editor.org/info/rfc7990> RFC Format Framework
RFC 7991 <https://www.rfc-editor.org/info/rfc7991> The "xml2rfc" Version 3
Vocabulary
RFC 7992 <https://www.rfc-editor.org/info/rfc7992> HTML Format for RFCs
RFC 7993 <https://www.rfc-editor.org/info/rfc7993> Cascading Style Sheets
(CSS) Requirements for RFCs
RFC 7994 <https://www.rfc-editor.org/info/rfc7994> Requirements for
Plain-Text RFCs
RFC 7995 <https://www.rfc-editor.org/info/rfc7995> PDF Format for RFCs
RFC 7996 <https://www.rfc-editor.org/info/rfc7996> SVG Drawings for RFCs:
SVG 1.2 RFC
RFC 7997 <https://www.rfc-editor.org/info/rfc7997> The Use of Non-ASCII
Characters in RFCs
RFC 7998 <https://www.rfc-editor.org/info/rfc7998> "xml2rfc" Version 3
Preparation Tool Description
RFC 8153 <https://www.rfc-editor.org/info/rfc8153> Digital Preservation
Considerations for the RFC Series
RFC 7322 <https://www.rfc-editor.org/info/rfc7322> RFC Style Guide
RFC 5741 <https://www.rfc-editor.org/info/rfc5741> RFC 7841
<https://www.rfc-editor.org/info/rfc7841> RFC Streams, Headers, and
Boilerplates
RFC 8700 <https://www.rfc-editor.org/info/rfc8700> Fifty Years of RFCs

Mirja