Bernard's Review

[Bernard_Aboba@…]

Abstract

" The RFC Editor performs a number of functions that may be carried out

by various people or entities."

[BA] Since the paragraph reads just as well without this sentence, I'd suggest that it be deleted.

" The Internet Architecture Board (IAB)

oversight by way of delegation to the RFC Series Oversight Committee
(RSOC) is described,"

[BA] Suggest this be simplified to:

"Internet Architecture Board (IAB) oversight via the RFC Series Oversight Committee (RSOC) is described,"

Section 1

Recommend this be re-organized as follows:

"1. Introduction

The IAB, on behalf of the Internet technical community, is concerned
with ensuring the continuity of the RFC Series, orderly RFC Editor
succession, RFC quality, and RFC document accessibility.
The IAB is also sensitive to the concerns of the IETF Administrative
Oversight Committee (IAOC) about providing the necessary services in
a cost effective and efficient manner.

The contemporary RFC Editor model [RFC5620] was first approved in
October 1, 2008 and our understanding of the model has evolved with
our experience since then. During the implementation of version 1 of
the model [RFC5620] it was quickly realized that the role of the RSE
and the oversight responsibilities needed to be structured
differently. In order to gain experience with 'running code' a
transitional RFC Series Editor was hired who analyzed the managerial
environment and provided recommendations. This was followed by the
appointment of an acting RFC Series Editor, who ably managed the
series while work was undertaken to select and hire a permanent RSE.
This version of the model is based on the recommendations of both
temporary RFC Series Editors and the extensive discussion in the IETF
community, on the rfc-interest list and within the IAB. A such, this
document obsoletes [RFC5620].

The RFC series is described in [RFC4844]. Its Section 3.1 defines
"RFC Editor":

Originally, there was a single person acting as editor of the RFC
Series (the RFC Editor). The task has grown, and the work now
requires the organized activity of several experts, so there are
RFC Editors, or an RFC Editor organization. In time, there may be
multiple organizations working together to undertake the work
required by the RFC Series. For simplicity's sake, and without
attempting to predict how the role might be subdivided among them,
this document refers to this collection of experts and
organizations as the "RFC Editor".

The RFC Editor is an expert technical editor and series editor,
acting to support the mission of the RFC Series. As such, the RFC
Editor is the implementer handling the editorial management of the
RFC Series, in accordance with the defined processes. In addition,
the RFC Editor is expected to be the expert and prime mover in
discussions about policies for editing, publishing, and archiving
RFCs.

RFC 4844 does not explore the internal organization of the RFC
Editor. However, RFC 4844 envisions changes in the RFC Editor
organizational structure. There have been several iterations on
efforts to improve and clarify this structure. These have been led
by the IAB, in consultation with the community and many leadership
bodies within the community. This first resulted in the publication
of [RFC5620], and then in further discussions leading to this
document. Some of the details on this evolution can be found below.
In undertaking this evolution, the IAB considered changes that
increase flexibility and operational support options, provide for the
orderly succession of the RFC Editor, and ensure the continuity of
the RFC series, while maintaining RFC quality, maintaining timely
processing, ensuring document accessibility, reducing costs, and
increasing cost transparency. The model set forth below describes
the internal organization of the RFC Editor, while remaining
consistent with RFC 4844.

Note that RFC 4844 uses the term "RFC Editor function" or "RFC
Editor" as the collective set of responsibilities for which this memo
provides a model for internal organization. This memo defines the
term "RFC Series Editor" or "Series Editor" for one of the
organizational components.

The document, and the resulting structures, will be modified as
needed through normal procedures. The RSE, and the IAB, through the
RFC Oversight Committee (see Section 3.1), will continue to monitor
discussions within the community about potential adjustments to the
RFC Editor model and recognizes that the process described in this
document may need to be adjusted to align with any changes that
result from such discussions, hence the version number in the title.

The IAB and IAOC maintain their chartered responsibility as defined
in [RFC2850] and [RFC4071]."

[Bernard_Aboba@…]

Abstract

" The RFC Editor performs a number of functions that may be carried out

by various people or entities."

[BA] Without introducing the RFC 4844 of "RFC Editor", this sentence is a bit jarring. Since the paragraph reads just as well without this sentence, I'd suggest that it be deleted from the abstract.

" The Internet Architecture Board (IAB) oversight by way of delegation to the RFC Series Oversight Committee (RSOC) is described,"

[BA] Since the RSOC is an IAB Program I'd suggest this be simplified to:

"Internet Architecture Board (IAB) oversight via the RFC Series Oversight Committee (RSOC) is described,"

Section 1

Recommend this be re-organized as follows:

"1. Introduction

The IAB, on behalf of the Internet technical community, is concerned
with ensuring the continuity of the RFC Series, orderly RFC Editor
succession, RFC quality, and RFC document accessibility.
The IAB is also sensitive to the concerns of the IETF Administrative
Oversight Committee (IAOC) about providing the necessary services in
a cost effective and efficient manner.

The contemporary RFC Editor model [RFC5620] was first approved in
October 1, 2008 and our understanding of the model has evolved with
experience since then. During the implementation of version 1 of
the model [RFC5620] it was quickly realized that the role of the RSE
and the oversight responsibilities needed to be structured
differently. In order to gain experience with 'running code' a
transitional RFC Series Editor was hired who analyzed the managerial
environment and provided recommendations. This was followed by the
appointment of an acting RFC Series Editor, who ably managed the
series while work was undertaken to select and hire a permanent RSE.
This version of the model is based on the recommendations of both
temporary RFC Series Editors and the extensive discussion in the IETF
community, on the rfc-interest list and within the IAB. A such, this
document obsoletes [RFC5620].

This document, and the resulting structures, will be modified as
needed through normal procedures. The RSE, and the IAB, through the
RFC Oversight Committee (see Section 3.1), will continue to monitor
discussions within the community about potential adjustments to the
RFC Editor model and recognizes that the process described in this
document may need to be adjusted to align with any changes that
result from such discussions, hence the version number in the title.

The IAB and IAOC maintain their chartered responsibility as defined
in [RFC2850] and [RFC4071].

1.1 The RFC Editor Function

The RFC series is described in [RFC4844]. Its Section 3.1 defines
"RFC Editor":

Originally, there was a single person acting as editor of the RFC
Series (the RFC Editor). The task has grown, and the work now
requires the organized activity of several experts, so there are
RFC Editors, or an RFC Editor organization. In time, there may be
multiple organizations working together to undertake the work
required by the RFC Series. For simplicity's sake, and without
attempting to predict how the role might be subdivided among them,
this document refers to this collection of experts and
organizations as the "RFC Editor".

The RFC Editor is an expert technical editor and series editor,
acting to support the mission of the RFC Series. As such, the RFC
Editor is the implementer handling the editorial management of the
RFC Series, in accordance with the defined processes. In addition,
the RFC Editor is expected to be the expert and prime mover in
discussions about policies for editing, publishing, and archiving
RFCs.

RFC 4844 does not explore the internal organization of the RFC
Editor. However, RFC 4844 envisions changes in the RFC Editor
organizational structure. There have been several iterations on
efforts to improve and clarify this structure. These have been led
by the IAB, in consultation with the community and many leadership
bodies within the community. This first resulted in the publication
of [RFC5620], and then in further discussions leading to this
document. Some of the details on this evolution can be found below.
In undertaking this evolution, the IAB considered changes that
increase flexibility and operational support options, provide for the
orderly succession of the RFC Editor, and ensure the continuity of
the RFC series, while maintaining RFC quality, maintaining timely
processing, ensuring document accessibility, reducing costs, and
increasing cost transparency. The model set forth below describes
the internal organization of the RFC Editor, while remaining
consistent with RFC 4844.

Note that RFC 4844 uses the term "RFC Editor function" or "RFC
Editor" as the collective set of responsibilities for which this memo
provides a model for internal organization. This memo defines the
term "RFC Series Editor" or "Series Editor" for one of the
organizational components.