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
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
|
<pre>Internet Architecture Board (IAB) O. Kolkman, Ed.
Request for Comments: 6635
Obsoletes: <a href="./rfc5620">5620</a> J. Halpern, Ed.
Category: Informational Ericsson
ISSN: 2070-1721 IAB
June 2012
<span class="h1">RFC Editor Model (Version 2)</span>
Abstract
The RFC Editor model described in this document divides the
responsibilities for the RFC Series into three functions: the RFC
Series Editor, the RFC Production Center, and the RFC Publisher.
Internet Architecture Board (IAB) oversight via the RFC Series
Oversight Committee (RSOC) is described, as is the relationship
between the IETF Administrative Oversight Committee (IAOC) and the
RSOC. This document reflects the experience gained with "RFC Editor
Model (Version 1)", documented in <a href="./rfc5620">RFC 5620</a>, and obsoletes that
document.
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. Documents approved for publication by
the IAB are not a candidate for any level of Internet Standard; see
<a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="http://www.rfc-editor.org/info/rfc6635">http://www.rfc-editor.org/info/rfc6635</a>.
Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) 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.
<span class="grey">Kolkman, et al. Informational [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc6635">RFC 6635</a> RFC Editor Model (Version 2) June 2012</span>
Table of Contents
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-3">3</a>
<a href="#section-1.1">1.1</a>. The RFC Editor Function ....................................<a href="#page-3">3</a>
<a href="#section-2">2</a>. RFC Editor Model ................................................<a href="#page-4">4</a>
<a href="#section-2.1">2.1</a>. RFC Series Editor ..........................................<a href="#page-7">7</a>
2.1.1. Strategic Leadership and Management of the
Publication and Production Functions ................<a href="#page-8">8</a>
<a href="#section-2.1.2">2.1.2</a>. Representation of the RFC Series ....................<a href="#page-8">8</a>
<a href="#section-2.1.2.1">2.1.2.1</a>. Representation to the IETF .................<a href="#page-8">8</a>
<a href="#section-2.1.2.1.1">2.1.2.1.1</a>. Volunteerism ....................<a href="#page-9">9</a>
<a href="#section-2.1.2.1.2">2.1.2.1.2</a>. Policy Authority ................<a href="#page-9">9</a>
<a href="#section-2.1.2.2">2.1.2.2</a>. External Representation ....................<a href="#page-9">9</a>
<a href="#section-2.1.3">2.1.3</a>. Development of RFC Production and Publication ......<a href="#page-10">10</a>
<a href="#section-2.1.4">2.1.4</a>. Development of the RFC Series ......................<a href="#page-10">10</a>
<a href="#section-2.1.5">2.1.5</a>. Workload ...........................................<a href="#page-11">11</a>
<a href="#section-2.1.6">2.1.6</a>. Qualifications .....................................<a href="#page-11">11</a>
<a href="#section-2.1.7">2.1.7</a>. Conflict of Interest ...............................<a href="#page-12">12</a>
<a href="#section-2.2">2.2</a>. RFC Production Center .....................................<a href="#page-12">12</a>
<a href="#section-2.3">2.3</a>. RFC Publisher .............................................<a href="#page-13">13</a>
<a href="#section-3">3</a>. Committees .....................................................<a href="#page-14">14</a>
<a href="#section-3.1">3.1</a>. RFC Series Oversight Committee (RSOC) .....................<a href="#page-14">14</a>
<a href="#section-3.1.1">3.1.1</a>. RSOC Composition ...................................<a href="#page-15">15</a>
<a href="#section-4">4</a>. Administrative Implementation ..................................<a href="#page-16">16</a>
4.1. Vendor Selection for the Production and Publisher
Functions .................................................<a href="#page-17">17</a>
<a href="#section-4.2">4.2</a>. Budget ....................................................<a href="#page-17">17</a>
<a href="#section-4.3">4.3</a>. Disagreements among Entities Related to the RFC Editor ....<a href="#page-18">18</a>
<a href="#section-4.4">4.4</a>. Issues with Contractual Impact ............................<a href="#page-19">19</a>
<a href="#section-5">5</a>. IANA Considerations ............................................<a href="#page-19">19</a>
<a href="#section-6">6</a>. Security Considerations ........................................<a href="#page-19">19</a>
<a href="#section-7">7</a>. Acknowledgments ................................................<a href="#page-20">20</a>
<a href="#section-8">8</a>. References .....................................................<a href="#page-21">21</a>
<a href="#section-8.1">8.1</a>. Normative References ......................................<a href="#page-21">21</a>
<a href="#section-8.2">8.2</a>. Informative References ....................................<a href="#page-21">21</a>
<span class="grey">Kolkman, et al. Informational [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc6635">RFC 6635</a> RFC Editor Model (Version 2) June 2012</span>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
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 [<a href="./rfc5620" title=""RFC Editor Model (Version 1)"">RFC5620</a>] was first approved in
October 2008, and our understanding of the model has evolved with our
experience since. During the implementation of version 1 of the
model [<a href="./rfc5620" title=""RFC Editor Model (Version 1)"">RFC5620</a>], it was quickly realized that the role of the RFC
Series Editor (RSE) and the oversight responsibilities needed to be
structured differently. In order to gain experience with "running
code", a transitional RSE was hired who analyzed the managerial
environment and provided recommendations. This was followed by the
appointment of an acting RSE, 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. As such, this document
obsoletes [<a href="./rfc5620" title=""RFC Editor Model (Version 1)"">RFC5620</a>].
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 <a href="#section-3.1">Section 3.1</a>), will continue to monitor
discussions within the community about potential adjustments to the
RFC Editor model and recognize 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 [<a href="./rfc2850" title=""Charter of the Internet Architecture Board (IAB)"">RFC2850</a>] and [<a href="./rfc4071" title=""Structure of the IETF Administrative Support Activity (IASA)"">RFC4071</a>].
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. The RFC Editor Function</span>
The RFC Series is described in [<a href="./rfc4844" title=""The RFC Series and RFC Editor"">RFC4844</a>]. Its <a href="#section-3.1">Section 3.1</a> 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
<span class="grey">Kolkman, et al. Informational [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc6635">RFC 6635</a> RFC Editor Model (Version 2) June 2012</span>
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.
<a href="./rfc4844">RFC 4844</a> does not explore the internal organization of the RFC
Editor. However, <a href="./rfc4844">RFC 4844</a> 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 [<a href="./rfc5620" title=""RFC Editor Model (Version 1)"">RFC5620</a>] 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 <a href="./rfc4844">RFC 4844</a>.
Note that <a href="./rfc4844">RFC 4844</a> 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.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. RFC Editor Model</span>
The RFC Editor model divides the responsibilities for the RFC Series
into the following components:
o RFC Series Editor (RSE)
o RFC Production Center
o RFC Publisher
<span class="grey">Kolkman, et al. Informational [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc6635">RFC 6635</a> RFC Editor Model (Version 2) June 2012</span>
The structure and relationship of the components of the RFC Series
production and process is schematically represented by the figure
below. The picture does not depict oversight and escalation
relations. It does include the streams and their managers (which are
not part of the RFC Series Editor, the RFC Production Center, or
Publisher facilities) in order to more fully show the context in
which the RFC Series Editor operates.
<span class="grey">Kolkman, et al. Informational [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc6635">RFC 6635</a> RFC Editor Model (Version 2) June 2012</span>
+-------------+
| |
+--------------+ IAB <------------+
| | | |
| |=============| |
| | | |
| | RSOC <------------+
| | | |
| +-------+-----+ +-----+-----+
| | | |
| +...........|.........+ | Community |
| . | . | at |
| . +-------V-----+ . | Large |
| . | | . | |
| . | RFC | . +-----+-----+
| . | Series | . |
| . | Editor <------------+
| . | | .
| . +-+---------+-+ .
| . | | .
+-------------+ +-----V-------+ . +--V--+ +--V--+ . +-----+
| | | | . | | | | . | |
| Independent | | Independent | . | RFC | | | . | E |
| Authors +--> Submission +-----> | | | . | n |
| | | Editor | . | P | | | . | d |
| | | | . | r | | RFC | . | |
+-------------+ +-------------+ . | o | | | . | U |
+-------------+ +-------------+ . | d | | P | . | s |
| | | | . | u | | u | . | e |
| IAB +--> IAB +-----> c | | b | . | r |
| | | | . | t | | l | . | s |
+-------------+ +-------------+ . | i +---> i +--------> |
+-------------+ +-------------+ . | o | | s | . | & |
| | | | . | n | | h | . | |
| IRTF +--> IRSG +---->| | | e | . | R |
| | | | . | C | | r | . | e |
+-------------+ +-------------+ . | e | | | . | a |
+-------------+ +-------------+ . | n | | | . | d |
| | | | . | t | | | . | e |
| IETF +--> IESG +-----> e | | | . | r |
| | | | . | r | | | . | s |
+-------------+ +-------------+ . +-----+ +-----+ . +-----+
. .
+..... RFC Editor ....+
Structure of RFC Series Production and Process
Figure 1
<span class="grey">Kolkman, et al. Informational [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc6635">RFC 6635</a> RFC Editor Model (Version 2) June 2012</span>
In this model, documents are produced and approved through multiple
document streams. The stream manager for each stream is responsible
for the content of that stream. The four streams that now exist are
described in [<a href="./rfc4844" title=""The RFC Series and RFC Editor"">RFC4844</a>]. The RFC Editor function is responsible for
the packaging and distribution of the documents. As such, documents
from these streams are edited and processed by the Production Center
and published by the Publisher. The RFC Series Editor will exercise
strategic leadership and management over the activities of the RFC
Publisher and the RFC Production Center (both of which can be seen as
back-office functions) and will be the entity that:
o Represents the RFC Series and the RFC Editor Function within the
IETF and externally.
o Leads the community in the design of improvements to the RFC
Series.
o Is responsible for planning and seeing to the execution of
improvements in the RFC Editor production and access processes.
o Is responsible for the content of the rfc-editor.org web site,
which is operated and maintained by the RFC Publisher.
o Is responsible for developing consensus versions of vision and
policy documents. These documents will be reviewed by the RFC
Series Oversight Committee (<a href="#section-3.1">Section 3.1</a>) and subject to its
approval before final publication.
These responsibilities are defined below, although the specific work
items under them are a matter for the actual employment contract and
its Statement of Work (SOW).
The IAB and IAOC maintain their chartered responsibility as defined
in [<a href="./rfc2850" title=""Charter of the Internet Architecture Board (IAB)"">RFC2850</a>] and [<a href="./rfc4071" title=""Structure of the IETF Administrative Support Activity (IASA)"">RFC4071</a>]. More details on the oversight by the IAB
via the RFC Series Oversight Committee (RSOC) can be found in
<a href="#section-3.1">Section 3.1</a>. For example, the RSE does not have the direct authority
to hire or fire RFC Editor contractors or personnel.
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. RFC Series Editor</span>
The RFC Series Editor is the individual with overall responsibility
for the quality, continuity, and evolution of the RFC Series.
The RSE is appointed by the IAB, but formally hired by the IAOC. The
IAB delegates the direct oversight over the RSE to the RSOC, which it
appoints.
<span class="grey">Kolkman, et al. Informational [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc6635">RFC 6635</a> RFC Editor Model (Version 2) June 2012</span>
The RSE is expected to cooperate closely with the IAOC and the stream
managers.
<span class="h4"><a class="selflink" id="section-2.1.1" href="#section-2.1.1">2.1.1</a>. Strategic Leadership and Management of the Publication and</span>
<span class="h4"> Production Functions</span>
With respect to the RFC Publisher and Production Center functions,
the RSE provides input to the IASA budget, SOWs, and manages vendor
selection processes. The RSE performs annual reviews of the RFC
Production Center and Publisher function, which are then provided to
the RSOC, the IASA, and the community. Normally, private financial
details would not be included in a public version unless the IAOC
concludes it is necessary to make such information public.
The RSE is responsible for the performance of the RFC Production
Center and Publisher. The RSE is responsible for issues that go
beyond the RFC Production Center or Publisher functions, such as
cross-stream coordination of priorities. Issues that require changes
to the budget or contracts shall be brought to the attention of the
IAD by the RSE.
The RSE is also responsible for creating documentation and structures
that will allow for continuity of the RFC Series in the face of
changes in contracts and personnel.
Vendor selection for the RFC Production Center and Publisher
functions is done in cooperation with the streams and under final
authority of the IASA. Details on this process can be found in
<a href="#section-4.1">Section 4.1</a>.
<span class="h4"><a class="selflink" id="section-2.1.2" href="#section-2.1.2">2.1.2</a>. Representation of the RFC Series</span>
The RSE is the primary representative of the RFC Series. This
representation is important both internally, relative to the IETF,
and externally.
<span class="h5"><a class="selflink" id="section-2.1.2.1" href="#section-2.1.2.1">2.1.2.1</a>. Representation to the IETF</span>
The RSE is the primary point of contact to the IETF on matters
relating to the RFC Series in general, or policy matters relating to
specific documents. Issues of practical details in the processing of
specific documents are generally worked through directly with the RFC
Production Center staff.
This includes providing suitable reports to the community at large,
providing email contact for policy questions and inputs, and enabling
and participating in suitable on-line forums for discussion of issues
related to the RFC Series.
<span class="grey">Kolkman, et al. Informational [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc6635">RFC 6635</a> RFC Editor Model (Version 2) June 2012</span>
Due to the history and nature of the interaction between the RSE and
the IETF, certain principles, described in the following subsections,
must be understood and adhered to by the RSE in his or her
interactions with the community. These apply to the representation
function, as well as to the leadership the RSE provides for
production and series development.
<span class="h6"><a class="selflink" id="section-2.1.2.1.1" href="#section-2.1.2.1.1">2.1.2.1.1</a>. Volunteerism</span>
The vast majority of Internet technical community work is led,
initiated, and done by community volunteers, including oversight,
policy making, and direct production of, for example, many software
tools. The RSE, while not a volunteer, is dependent upon these
volunteer participants. Also, the spirit of the community is heavily
focused on and draws from these volunteers. As such, the RSE needs
to support the vitality and effectiveness of volunteer participation.
<span class="h6"><a class="selflink" id="section-2.1.2.1.2" href="#section-2.1.2.1.2">2.1.2.1.2</a>. Policy Authority</span>
All decisions are to be made in the overall interest of the broader
Internet community. The RSE is responsible for identifying
materially concerned interest groups within the Internet community
and reaching out to them. Those interest groups include at least the
IETF community, the IRTF community, the network research community,
and the network operations community. Other interest groups might
also be materially interested.
The RSE must consult with the community on policy issues. The RSE
works with the community to achieve policy that meets the overall
quality, continuity, and evolution goals the RSE is charged with
meeting. As described in <a href="#section-3.1">Section 3.1</a>, the RSE reports the results of
such interactions to the RSOC, including a description of the
outreach efforts and the specific recommendations on policy. This
enables the RSOC to provide the oversight the IAB is required to
apply, as well as to confirm that the Internet community has been
properly consulted and considered in making policy.
<span class="h5"><a class="selflink" id="section-2.1.2.2" href="#section-2.1.2.2">2.1.2.2</a>. External Representation</span>
From time to time, individuals or organizations external to the IETF
need a contact person to talk to about the RFC Series. The RSE, or
the RSE's designate, serves this role.
Over time, the RSE should determine what, if any, means should be
employed to increase end-user awareness of the series, to reinforce
the stature of the series, and to provide the contact point for
outside parties seeking information on the series or the Editor.
<span class="grey">Kolkman, et al. Informational [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc6635">RFC 6635</a> RFC Editor Model (Version 2) June 2012</span>
<span class="h4"><a class="selflink" id="section-2.1.3" href="#section-2.1.3">2.1.3</a>. Development of RFC Production and Publication</span>
Closely related to providing strategic leadership and management to
the RFC Production Center and Publisher functions is the need to
develop and improve those functions. The RSE is responsible for
ensuring that such ongoing development takes place.
This effort must include the dimensions of document quality,
timeliness of production, and accessibility of results. It must also
specifically take into account issues raised by the IETF community,
including all the streams feeding into the RFC Editor function.
<span class="h4"><a class="selflink" id="section-2.1.4" href="#section-2.1.4">2.1.4</a>. Development of the RFC Series</span>
In order to develop the RFC Series, the RSE is expected to develop a
relationship with the Internet technical community. The Editor is
expected to engage with the Internet technical community in a process
of articulating and refining a vision for the series and its
continuous evolution. The RSE is also expected to engage other users
of the RFC Series, in particular, the consumers of these documents,
such as those people who use them to specify products, write code,
test behaviors, or other related activities.
Concretely:
The RSE is responsible for the coordination of discussion on
series evolution among the series' stream participants and the
broader Internet technical community.
In time, the RSE is expected to develop and refine a vision for
the RFC Series, including examining:
* The RFC Series, as it continues to evolve. The RSE is expected
to take a broad view and look for the best ways to evolve the
series for the benefit of the entire Internet community. As
such, the RSE may even consider evolution beyond the historical
'by engineers for engineers' emphasis; and
* Its publication-technical environment, by looking at whether it
should be slowly changing in terms of publishing and archiving
techniques -- particularly to better serve the communities that
produce and depend on the RFC Series. For example, all of
those communities have been slowly changing to include a
significant population of multi-lingual individuals or non-
native speakers of English. Another example is that some of
these constituencies also have shifted to include significant
<span class="grey">Kolkman, et al. Informational [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc6635">RFC 6635</a> RFC Editor Model (Version 2) June 2012</span>
groups whose primary focus is on the constraints and
consequences of network engineering, rather than a primary
interest in the engineering issues themselves.
For this type of responsibility, the RSE cooperates closely with the
community, and operates under oversight of the RSOC: thus,
ultimately, under oversight of the IAB.
<span class="h4"><a class="selflink" id="section-2.1.5" href="#section-2.1.5">2.1.5</a>. Workload</span>
On average, the job is expected to take half of a full-time
equivalent position (FTE, thus approx 20 hrs per week), with the
workload per week nearing full time during IETF weeks. In addition,
the job is expected to take more than 20 hours per week in the first
few months of the engagement and when involved in special projects.
<span class="h4"><a class="selflink" id="section-2.1.6" href="#section-2.1.6">2.1.6</a>. Qualifications</span>
The RFC Series Editor is a senior technology professional. The
following qualifications are desired:
1. Strategic leadership and management experience fulfilling the
requirements outlined in this document, the many aspects of this
role, and the coordination of the overall RFC Editor process.
2. Good understanding of the English language and technical
terminology related to the Internet.
3. Good communication skills.
4. Experience with editorial processes.
5. Ability to develop strong understanding of the IETF and RFC
process.
6. Independent worker.
7. Willingness to, and availability for, travel.
8. The ability to work effectively in a multi-actor and matrixed
environment with divided authority and responsibility similar to
that described in this document.
9. Experience with and ability to participate in, and manage,
activities by email and teleconferences, not just face-to-face
interactions.
<span class="grey">Kolkman, et al. Informational [Page 11]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
<span class="grey"><a href="./rfc6635">RFC 6635</a> RFC Editor Model (Version 2) June 2012</span>
10. Demonstrated experience in strategic planning and the management
of entire operations.
11. Experience as an RFC author.
<span class="h4"><a class="selflink" id="section-2.1.7" href="#section-2.1.7">2.1.7</a>. Conflict of Interest</span>
The RSE is expected to avoid even the appearance of conflict of
interest or judgment in performing these roles. As such, the RSE is
barred from having any ownership, advisory, or other relationship to
the vendors executing the RFC Publisher or Production Center
functions except as specified elsewhere in this document. If
necessary, an exception can be made after public disclosure of those
relationships and with the explicit permission of the IAB and IAOC.
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. RFC Production Center</span>
The RFC Production Center function is performed by a paid contractor,
and the contractor's responsibilities include the following:
1. Editing inputs from all RFC streams to comply with the RFC Style
Manual, under the direction of the RSE;
2. Creating records of edits performed on documents;
3. Identifying where editorial changes might have technical impact
and seeking necessary clarification;
4. Engaging in dialog with authors, document shepherds, IANA,
and/or stream-dependent contacts when clarification is needed;
5. Creating records of dialog with document authors;
6. Requesting advice from the RFC Series Editor as needed;
7. Providing suggestions to the RFC Series Editor as needed;
8. Providing sufficient resources to support reviews of RFC
Publisher performance by the RFC Series Editor and external
reviews of the RFC Editor function initiated by the IAB or IAOC;
9. Coordinating with IANA to ensure correct documentation of IANA-
performed protocol registry actions;
10. Assigning RFC numbers;
<span class="grey">Kolkman, et al. Informational [Page 12]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
<span class="grey"><a href="./rfc6635">RFC 6635</a> RFC Editor Model (Version 2) June 2012</span>
11. Establishing publication readiness of each document through
communication with the authors, document shepherds, IANA, and/or
stream-dependent contacts, and, if needed, with the RFC Series
Editor;
12. Forwarding documents that are ready for publication to the RFC
Publisher;
13. Forwarding records of edits and author dialog to the RFC
Publisher so these can be preserved;
14. Liaising with the streams as needed.
All these activities will be done under the general direction, but
not day-to-day management, of the RSE and need some level of
coordination with various submission streams and the RSE.
The RFC Production Center contractor is to be selected through an
IASA Request for Proposal (RFP) process as described in <a href="#section-4.1">Section 4.1</a>.
<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. RFC Publisher</span>
The RFC Publisher responsibilities include the following:
1. Announcing and providing on-line access to RFCs.
2. Providing an on-line system to submit RFC Errata.
3. Providing on-line access to approved RFC Errata.
4. Providing backups.
5. Providing storage and preservation of records.
6. Authenticating RFCs for legal proceedings.
All these activities will be done under the general direction, but
not day-to-day management, of the RSE and need some level of
coordination with various submission streams and the RSE.
The RFC Publisher contractor is to be selected through an IASA RFP
process as described in <a href="#section-4.1">Section 4.1</a>.
<span class="grey">Kolkman, et al. Informational [Page 13]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
<span class="grey"><a href="./rfc6635">RFC 6635</a> RFC Editor Model (Version 2) June 2012</span>
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Committees</span>
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. RFC Series Oversight Committee (RSOC)</span>
The IAB is responsible for the oversight of the RFC Series and acts
as a body for final conflict resolution, including the process
described in <a href="#section-4.3">Section 4.3</a>.
In order to provide continuity over periods longer than the NomCom
appointment cycle [<a href="./rfc3777" title=""IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall Committees"">RFC3777</a>] and assure that oversight includes
suitable subject matter expertise, the IAB will establish a group
that implements oversight for the IAB, the RFC Series Oversight
Committee (RSOC).
The RSOC will act with authority delegated from the IAB: in general,
it will be the RSOC that will approve consensus policy and vision
documents as developed by the RSE in collaboration with the
community. While it is expected that the IAB will exercise due
diligence in its supervision of the RSOC, the RSOC should be allowed
the latitude to do its job without undue interference from the IAB.
Therefore, it is expected that the IAB will accord RSOC reports and
recommendations the benefit of the doubt.
For all decisions that affect the RSE individually (e.g., hiring and
firing), the RSOC prepares recommendations for the IAB, but the final
decision is the responsibility of the IAB. For instance the RSOC
would do the following:
o perform annual reviews of the RSE and report the result of these
reviews to the IAB.
o manage RSE candidate selection and advise the IAB on candidate
appointment (in other words, select the RSE subject to IAB
approval).
RSOC members are expected to recognize potential conflicts of
interest and behave accordingly.
For the actual recruitment and selection of the RSE, the RSOC will
propose a budget for the search process. It will work with IASA to
refine that budget and develop remuneration criteria and an
employment agreement or contracting plans, as appropriate.
The RSOC will be responsible for ensuring that the RFC Series is run
in a transparent and accountable manner.
The RSOC shall develop and publish its own rules of order.
<span class="grey">Kolkman, et al. Informational [Page 14]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
<span class="grey"><a href="./rfc6635">RFC 6635</a> RFC Editor Model (Version 2) June 2012</span>
The initial RSOC was charged with designing and executing a
solicitation, search, and selection process for the first actual (not
transitional or "acting") RSE appointment. That process involved
iteration on this and related documents and evaluation of various
strategies and options. During the creation of this document, it was
expected that the RSOC would describe the process it ultimately
selected to the community. The RSOC did involve the community in
interim considerations when that was likely to be of value.
Following completion of the selection process, the RSOC will
determine the best way to share information learned and experience
gained with the community and determine how to best preserve that
information for future use.
<span class="h4"><a class="selflink" id="section-3.1.1" href="#section-3.1.1">3.1.1</a>. RSOC Composition</span>
The RSOC will operate under the authority of the IAB, with the IAB
retaining final responsibility. The IAB will delegate authority and
responsibility to the RSOC as appropriate and as RSOC and RSE
relationships evolve. The RSOC will include people who are not
current IAB members. Currently, this is aligned with the IAB program
structure. The IAB will designate the membership of the RSOC with
the following goals: preserving effective stability; keeping it small
enough to be effective, and keeping it large enough to provide
general Internet community expertise, specific IETF expertise,
publication expertise, and stream expertise. Members serve at the
pleasure of the IAB and are expected to bring a balance between
short- and long-term perspectives. Specific input about, and
recommendations of, members will be sought from the streams, the
IASA, and the RSE.
In addition to the members from outside of the IAB appointed to the
RSOC, IAB members may participate as full members of the RSOC. Under
most circumstances, there will be a specific individual IAB member
appointed by the IAB as the program lead, who will be a full member
of the RSOC. This member's role is distinct from any RSOC-internal
organizational roles, such as would be created by the RSOC choosing
to appoint a chair from among its members. Other IAB members may
choose to be full members of the RSOC, with the consent of the IAB.
This consent is primarily concerned with avoiding overpopulating the
RSOC and providing it with relatively stable membership, which will
work best if it is not too large a committee.
The IAOC will appoint an individual to serve as its liaison to the
RSOC. The RSE and the IAOC Liaison will serve as non-voting ex
officio members of the RSOC. Either or both can be excluded from its
discussions if necessary.
<span class="grey">Kolkman, et al. Informational [Page 15]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
<span class="grey"><a href="./rfc6635">RFC 6635</a> RFC Editor Model (Version 2) June 2012</span>
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Administrative Implementation</span>
The exact implementation of the administrative and contractual
activities described here are a responsibility of the IETF
Administrative Oversight Committee (IAOC, [<a href="./rfc4071" title=""Structure of the IETF Administrative Support Activity (IASA)"">RFC4071</a>]) in cooperation
with the RFC Series Editor. The authority structure is described in
Figure 2 below.
+----------------+ +----------------+
| | | |
| IAB | | IAOC |
| | | |
+==========+-----+ +-+--------------+
| | .
| RSOC | .
| | .
+----+-----+ .
| .
| .
| ...................
| . .
+--------V---V----+ .
| | .
| RFC | .
| Series | .
| Editor | .
| | .
+--------+--------+ .
| .
| .................
| . .
+--+----------------+ .
| . | .
| . | .
+---V-----V--+ +--V----V---+
| RFC | | RFC |
| Production | | Publisher |
| Center | | |
+------------+ +-----------+
Authority Structure of the RFC Series
Legend:
------- IAB RFC Series Oversight
....... IAOC Contract/Budget Oversight
Figure 2
<span class="grey">Kolkman, et al. Informational [Page 16]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
<span class="grey"><a href="./rfc6635">RFC 6635</a> RFC Editor Model (Version 2) June 2012</span>
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Vendor Selection for the Production and Publisher Functions</span>
As stated earlier, vendor selection is done in cooperation with the
streams and under the final authority of the IAOC.
The RSE owns and develops the work definition (the SOW) and
participates in the IASA vendor selection process. The work
definition is created within the IASA budget and takes into account
the stream managers and community input.
The process to select and contract for an RFC Production Center, RFC
Publisher, and other RFC-related services, is as follows:
o The IAOC establishes the contract process, including the steps
necessary to issue an RFP when necessary, the timing, and the
contracting procedures.
o The IAOC establishes the Selection Committee, which will consist
of the RSE, the IAD, and other members selected by the RSOC and
the IAOC. The Committee shall be chaired by the RSE.
o The Selection Committee selects the vendor, subject to the
successful negotiation of a contract approved by the IAOC. In the
event that a contract cannot be reached, the matter shall be
referred to the Selection Committee for further action.
o The Selection Committee may select an RFC Publisher either through
the IASA RFP process or, at the Committee's option, the Committee
may select the IETF Secretariat to provide RFC Publisher services,
subject to negotiations in accordance with the IASA procedures.
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Budget</span>
The expenses discussed in this document are not new expenses. They
have been and remain part of the IETF Administrative Support Activity
(IASA, [<a href="./rfc4071" title=""Structure of the IETF Administrative Support Activity (IASA)"">RFC4071</a>]) budget.
The RFC Series portion of the IASA budget shall include entries for
the RSOC, RSE, RFC Production Center, and the RFC Publisher. The
IASA budget shall also include entries for the streams, including the
independent stream.
The IAOC has the responsibility to approve the total RFC Editor
budget (and the authority to deny it). The RSE must work within the
IAOC budgetary process.
<span class="grey">Kolkman, et al. Informational [Page 17]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
<span class="grey"><a href="./rfc6635">RFC 6635</a> RFC Editor Model (Version 2) June 2012</span>
The RSE is responsible for managing the RFC Editor function to
operate within those budgets. If production needs change, the RSE is
responsible for working with the Production Center, and where
appropriate, other RFC Editor component institutions, relevant
streams, and/or the RSOC to determine what the correct response
should be. If they agree that a budgetary change is needed, that
decision needs to be taken to the IAD and the IAOC.
<span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>. Disagreements among Entities Related to the RFC Editor</span>
The RFC Series Editor and the RFC Production Center and Publisher
facilities work with the various streams to produce RFCs.
Disagreements may arise between these entities during the execution
of the RFC Editor operations. In particular, different streams may
disagree with each other, or disagree with the RFC Editor function.
Potentially, even the RSOC or the IAOC could find themselves in
disagreement with some aspect of the RFC Editor operations. Note
that disagreements between an author and the RFC Production Center
are not cross-entity issues, and they are to be resolved by the RSE,
in accordance with the rest of this document.
If such cross-entity disagreements arise, the community would
generally hope that they can be resolved politely and directly.
However, this is not always possible. At that point, any relevant
party would first formally request a review and reconsideration of
the decision. If the party still disagrees after the
reconsideration, that party may ask the RSE to decide or, especially
if the RSE is involved, the party may ask the IAB Chair (for a
technical or procedural matter) to mediate or appoint a mediator to
aid in the discussions, although he or she not is obligated to do so.
All parties should work informally and in good faith to reach a
mutually agreeable conclusion. As noted below, any such issues that
involve contractual matters must be brought to the attention of the
IAOC. If the IAB Chair is asked to assist in resolving the matter,
the Chair may ask for advice or seek assistance from anyone the Chair
deems helpful. The Chair may also alert any appropriate individuals
or organizations to the existence of the issue.
If such a conclusion is not possible through the above less formal
processes, then the matter must be registered with the RFC Series
Oversight Committee. The RSOC may choose to offer advice to the RSE
or more general advice to the parties involved and may ask the RSE to
defer a decision until it formulates its advice. However, if a
timely decision cannot be reached through discussion, mediation, and
mutual agreement, the RSE is expected to make whatever decisions are
needed to ensure the smooth operation of the RFC Editor function;
those decisions are final.
<span class="grey">Kolkman, et al. Informational [Page 18]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
<span class="grey"><a href="./rfc6635">RFC 6635</a> RFC Editor Model (Version 2) June 2012</span>
The RSE may make final decisions unilaterally only to assure the
functioning of the process, and only while there is an evaluation of
current policies to determine whether they are appropriately
implemented in the decision or need adjustment. In particular, it
should be noted that final decisions about the technical content of
individual documents are the exclusive responsibility of the stream
approvers from which those documents originate, as shown in the
illustration in Figure 1.
If informal agreements cannot be reached, then formal RSOC review and
decision making may be required. If so, the RSE must present the
issues involved to the community so that the community is aware of
the situation. The RSE will then report the issue to the RSOC for
formal resolution by the RSOC with confirmation by the IAB in its
oversight capacity.
IAB and community discussion of any patterns of disputes are expected
to inform future changes to RFC Series policies, including possible
updates to this document.
<span class="h3"><a class="selflink" id="section-4.4" href="#section-4.4">4.4</a>. Issues with Contractual Impact</span>
If a disagreement or decision has immediate or future contractual
consequences, it falls under <a href="https://www.rfc-editor.org/bcp/bcp101">BCP 101</a> [<a href="./rfc4071" title=""Structure of the IETF Administrative Support Activity (IASA)"">RFC4071</a>] and IASA; thus, the
RSE must identify the issue and provide his or her advice to the
IAOC; additionally, if the RSOC has provided advice, forward that
advice as well. The IAOC must notify the RSOC and IAB regarding the
action it concludes is required to resolve the issue based on its
applicable procedures and provisions in the relevant contracts.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. IANA Considerations</span>
This document defines several functions within the overall RFC Editor
structure, and it places the responsibility for coordination of
registry value assignments with the RFC Production Center. The IAOC
will facilitate the establishment of the relationship between the RFC
Production Center and IANA.
This document does not create a new registry nor does it register any
values in existing registries, and no IANA action is required.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span>
The same security considerations as those in [<a href="./rfc4844" title=""The RFC Series and RFC Editor"">RFC4844</a>] apply. The
processes for the publication of documents must prevent the
introduction of unapproved changes. Since the RFC Editor maintains
the index of publications, sufficient security must be in place to
prevent these published documents from being changed by external
<span class="grey">Kolkman, et al. Informational [Page 19]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
<span class="grey"><a href="./rfc6635">RFC 6635</a> RFC Editor Model (Version 2) June 2012</span>
parties. The archive of RFC documents, any source documents needed
to recreate the RFC documents, and any associated original documents
(such as lists of errata, tools, and, for some early items, originals
that are not machine readable) need to be secured against any kind of
data storage failure.
The IAOC should take these security considerations into account
during the implementation and enforcement of the RFC Editor component
contracts.
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Acknowledgments</span>
The RFC Editor model was conceived and discussed in hallways and on
mailing lists. The first iteration of the text on which this
document is based was first written by Leslie Daigle, Russ Housley,
and Ray Pelletier. In addition to the members of the IAOC and IAB in
conjunction with those roles, major and minor contributions were made
by (in alphabetical order): Bob Braden, Brian Carpenter, Sandy
Ginoza, Alice Russo, Joel M. Halpern, Alfred Hoenes, Paul Hoffman,
John Klensin, Subramanian Moonesamy, and Jim Schaad.
The IAOC members at the time this RFC Editor model was approved were
(in alphabetical order): Bernard Aboba (ex officio), Eric Burger,
Dave Crocker, Marshall Eubanks, Bob Hinden, Russ Housley (ex
officio), Ole Jacobsen, Ray Pelletier (non-voting), and Lynn St.
Amour (ex officio).
The IAB members at the time the initial RFC Editor model was approved
were (in alphabetical order): Loa Andersson, Gonzalo Camarillo,
Stuart Cheshire, Russ Housley, Olaf Kolkman, Gregory Lebovitz, Barry
Leiba, Kurtis Lindqvist, Andrew Malis, Danny McPherson, David Oran,
Dave Thaler, and Lixia Zhang. In addition, the IAB included two ex
officio members: Dow Street, who was serving as the IAB Executive
Director, and Aaron Falk, who was serving as the IRTF Chair.
The IAB members at the time the this RFC was approved were (in
alphabetical order): Bernard Aboba, Ross Callon, Alissa Cooper,
Spencer Dawkins, Joel Halpern, Russ Housley, David Kessens, Olaf
Kolkman, Danny McPherson, Jon Peterson, Andrei Robachevsky, Dave
Thaler, and Hannes Tschofenig. In addition, at the time of approval,
the IAB included two ex officio members: Mary Barnes who was serving
as the IAB Executive Director, and Lars Eggert, who was serving as
the IRTF Chair.
<span class="grey">Kolkman, et al. Informational [Page 20]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
<span class="grey"><a href="./rfc6635">RFC 6635</a> RFC Editor Model (Version 2) June 2012</span>
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. References</span>
<span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. Normative References</span>
[<a id="ref-RFC4844">RFC4844</a>] Daigle, L. and Internet Architecture Board, "The RFC
Series and RFC Editor", <a href="./rfc4844">RFC 4844</a>, July 2007.
[<a id="ref-RFC4071">RFC4071</a>] Austein, R. and B. Wijnen, "Structure of the IETF
Administrative Support Activity (IASA)", <a href="https://www.rfc-editor.org/bcp/bcp101">BCP 101</a>,
<a href="./rfc4071">RFC 4071</a>, April 2005.
[<a id="ref-RFC2850">RFC2850</a>] Internet Architecture Board and B. Carpenter, "Charter of
the Internet Architecture Board (IAB)", <a href="https://www.rfc-editor.org/bcp/bcp39">BCP 39</a>, <a href="./rfc2850">RFC 2850</a>,
May 2000.
<span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. Informative References</span>
[<a id="ref-RFC5620">RFC5620</a>] Kolkman, O. and IAB, "RFC Editor Model (Version 1)",
<a href="./rfc5620">RFC 5620</a>, August 2009.
[<a id="ref-RFC3777">RFC3777</a>] Galvin, J., "IAB and IESG Selection, Confirmation, and
Recall Process: Operation of the Nominating and Recall
Committees", <a href="https://www.rfc-editor.org/bcp/bcp10">BCP 10</a>, <a href="./rfc3777">RFC 3777</a>, June 2004.
Authors' Addresses
Olaf M. Kolkman (editor)
EMail: olaf@nlnetlabs.nl
Joel M. Halpern (editor)
Ericsson
EMail: joel.halpern@ericsson.com
Internet Architecture Board
EMail: iab@iab.org
Kolkman, et al. Informational [Page 21]
</pre>
|
