1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
|
Internet Architecture Board (IAB) N. Brownlee, Ed.
Request for Comments: 8730 The University of Auckland
Obsoletes: 6548 R. Hinden, Ed.
Category: Informational Check Point Software
ISSN: 2070-1721 February 2020
Independent Submission Editor Model
Abstract
This document describes the function and responsibilities of the RFC
Independent Submission Editor (ISE). The Independent Submission
stream is one of the stream producers that create draft RFCs, with
the ISE as its stream approver. The ISE is overall responsible for
activities within the Independent Submission stream, working with
draft editors and reviewers, and interacts with the RFC Production
Center and Publisher, and the RFC Series Editor (RSE). The ISE is
appointed by the IAB, and also interacts with the IETF Administration
Limited Liability Company (LLC).
This version obsoletes RFC 6548 to replace all references to the
Internet Administrative Support Activity (IASA) and related
structures with those defined by the IASA 2.0 structure.
Status of This Memo
This document is not an Internet Standards Track specification; it is
published for informational purposes.
This document is a product of the Internet Architecture Board (IAB)
and represents information that the IAB has deemed valuable to
provide for permanent record. It represents the consensus of the
Internet Architecture Board (IAB). Documents approved for
publication by the IAB are not candidates for any level of Internet
Standard; see Section 2 of RFC 7841.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
https://www.rfc-editor.org/info/rfc8730.
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document.
Table of Contents
1. Introduction
2. Independent Submission Editor
2.1. Qualifications
2.2. Responsibilities
3. Independent Submission Editorial Board
4. Security Considerations
5. References
5.1. Normative References
5.2. Informative References
IAB Members at the Time of Approval
Acknowledgements
Authors' Addresses
1. Introduction
The RFC Editor Model [RFC8728] defines a set of streams that produce
draft RFCs, which are submitted for publication. This document
defines the management function for the Independent Submission
stream, specifically the role of Independent Submission Editor (ISE).
The previous version of this document [RFC6548] is a derivative of
[RFC5620], Section 3.2, and was separated out from [RFC6635].
This document updates the Independent Submission Editor Model to
align it with the IASA 2.0 structure [RFC8711] that creates the IETF
Administration Limited Liability Company ("LLC") managed by a board
of directors ("LLC Board"). This document obsoletes [RFC6548].
2. Independent Submission Editor
The ISE is an individual who is responsible for the Independent
Submission stream of RFCs, as defined by [RFC8729]. The Independent
Submission stream and the ISE are not under the authority or
direction of the RSE or the RFC Series Oversight Committee (RSOC)
(see [RFC8728]). As noted below, the ISE is appointed by and is
responsible directly to the IAB.
2.1. Qualifications
The ISE is a senior position for which the following qualifications
are desired:
1. Technical competence, i.e., broad technical experience and
perspective across a wide range of Internet technologies and
applications, and also the ability to work effectively with
portions of that spectrum in which they have no personal
expertise.
2. Thorough familiarity with the RFC series.
3. An ability to define and constitute advisory and document review
arrangements. If those arrangements include an Editorial Board
similar to the current one or some equivalent arrangement, the
ability to assess the technical competence of potential Editorial
Board members (see Section 3).
4. Good standing in the technical community, in and beyond the IETF.
5. Demonstrated editorial skills, good command of the English
language, and demonstrated history of being able to work
effectively with technical documents and materials created by
others.
6. The ability to work effectively in a multi-actor environment with
divided authority and responsibility similar to that described in
[RFC6635].
2.2. Responsibilities
The ISE is an individual who may have assistants and who is
responsible for:
1. Maintaining technical quality of the Independent Submission
stream.
2. Reviewing, approving, and processing Independent Submissions.
3. Forwarding draft RFCs in the Independent Submission stream to the
RFC Production Center.
4. Defining and developing the scope of the Independent Submission
stream as a part of the overall RFC Editor function [RFC6635].
5. Reviewing and approving RFC errata for Independent Submissions.
6. Coordinating work and conforming to general RFC Series policies
as specified by the IAB and RSE.
7. Providing statistics and documentation as requested by the RSE
and/or LLC.
The ISE may choose to select individuals to participate in an
Advisory Board for assistance in special topics as the ISE deems
appropriate. Such an Advisory Board exists at the pleasure of the
ISE, and its members serve at the pleasure of the ISE.
The individual with the listed qualifications is selected by the IAB
after input has been collected from the community.
While the ISE itself is considered a volunteer function, the IAB
considers maintaining the Independent Submission stream part of the
IAB's supported activities. Therefore, the LLC should include these
costs in the IASA budget.
3. Independent Submission Editorial Board
The ISE is supported by an Editorial Board for the review of
Independent Submission stream documents. This board is known as the
Independent Submission Editorial Board. This volunteer Editorial
Board exists at the pleasure of the ISE, and its members serve at the
pleasure of the ISE. The existence of this board is simply noted
within this model, and additional discussion of such is considered
out of scope of this document.
4. Security Considerations
This document has no specific security implications, however the same
security considerations as those in [RFC4846] and [RFC8729] apply.
5. References
5.1. Normative References
[RFC4846] Klensin, J., Ed. and D. Thaler, Ed., "Independent
Submissions to the RFC Editor", RFC 4846,
DOI 10.17487/RFC4846, July 2007,
<https://www.rfc-editor.org/info/rfc4846>.
[RFC6548] Brownlee, N., Ed. and IAB, "Independent Submission Editor
Model", RFC 6548, DOI 10.17487/RFC6548, June 2012,
<https://www.rfc-editor.org/info/rfc6548>.
[RFC8711] Haberman, B., Hall, J., and J. Livingood, "Structure of
the IETF Administrative Support Activity, Version 2.0",
BCP 101, RFC 8711, DOI 10.17487/RFC8711, February 2020,
<https://www.rfc-editor.org/info/rfc8711>.
[RFC8728] Kolkman, O., Ed., Halpern, J., Ed., and R. Hinden, Ed.,
"RFC Editor Model (Version 2)", RFC 8728,
DOI 10.17487/RFC8728, February 2020,
<https://www.rfc-editor.org/info/rfc8728>.
[RFC8729] Housley, R., Ed. and L. Daigle, Ed., "The RFC Series and
RFC Editor", RFC 8729, DOI 10.17487/RFC8729, February
2020, <https://www.rfc-editor.org/info/rfc8729>.
5.2. Informative References
[RFC5620] Kolkman, O., Ed. and IAB, "RFC Editor Model (Version 1)",
RFC 5620, DOI 10.17487/RFC5620, August 2009,
<https://www.rfc-editor.org/info/rfc5620>.
[RFC6635] Kolkman, O., Ed., Halpern, J., Ed., and IAB, "RFC Editor
Model (Version 2)", RFC 6635, DOI 10.17487/RFC6635, June
2012, <https://www.rfc-editor.org/info/rfc6635>.
IAB Members at the Time of Approval
The IAB members at the time of approval of [RFC6548] were: Bernard
Aboba, Ross Callon, Alissa Cooper, Joel Halpern, Spencer Dawkins,
Russ Housley, David Kessens, Olaf Kolkman, Danny McPherson, Jon
Peterson, Andrei Robachevsky, Dave Thaler, and Hannes Tschofenig.
The IAB members at the time of approval of this document (RFC 8730)
were: Jari Arkko, Alissa Cooper, Stephen Farrell, Wes Hardaker, Ted
Hardie, Christian Huitema, Zhenbin Li, Erik Nordmark, Mark
Nottingham, Melinda Shore, Jeff Tantsura, Martin Thomson, and Brian
Trammell.
Acknowledgements
Generous thanks to Joel Halpern for all his help with this document,
and for all his work on [RFC6635]. Thanks also to the IAB members,
whose comments and suggestions were both welcome and useful.
Bob Hinden served as document editor for this RFC to align it with
the IASA 2.0 structure.
Authors' Addresses
Nevil Brownlee (editor)
The University of Auckland
Email: n.brownlee@auckland.ac.nz
Robert M. Hinden (editor)
Check Point Software
959 Skyway Road
San Carlos, CA 94070
United States of America
Email: bob.hinden@gmail.com
|
