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
|
<pre>Internet Architecture Board (IAB) L. Eggert
Request for Comments: 7827 NetApp
Category: Informational March 2016
ISSN: 2070-1721
<span class="h1">The Role of the IRTF Chair</span>
Abstract
This document briefly describes the role of the Chair of the Internet
Research Task Force (IRTF), discusses its duties, and outlines the
skill set a candidate for the role should ideally have.
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 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/rfc7827">http://www.rfc-editor.org/info/rfc7827</a>.
Copyright Notice
Copyright (c) 2016 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">Eggert Informational [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc7827">RFC 7827</a> The Role of the IRTF Chair March 2016</span>
Table of Contents
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-2">2</a>. Duties . . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-2.1">2.1</a>. Strategic . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-2.2">2.2</a>. Administrative . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-2.3">2.3</a>. IAB Membership . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-3">3</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-4">4</a>. Informative References . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
The Internet Research Task Force (IRTF) focuses on longer-term
research issues related to the Internet, while its sister
organization, the Internet Engineering Task Force (IETF), focuses on
the shorter-term issues of engineering and standards making.
The IRTF consists of a number of topical and long-term Research
Groups (RGs). These groups work on issues related to Internet
protocols, applications, architecture, and technology. RGs have the
stable long-term membership that is needed to promote the development
of research collaboration and teamwork in exploring research issues.
Individual contributors participate in the IRTF, rather than
representatives of organizations.
[<a id="ref-RFC2014">RFC2014</a>] details the procedures by which RGs operate. [<a href="./rfc4440" title=""IAB Thoughts on the Role of the Internet Research Task Force (IRTF)"">RFC4440</a>]
discusses a view from the Internet Architecture Board (IAB) on the
IRTF and its relationship to the IETF. The RFC Editor publishes
documents from the IRTF and its RGs in the IRTF Stream [<a href="./rfc5743" title=""Definition of an Internet Research Task Force (IRTF) Document Stream"">RFC5743</a>].
The IRTF Chair is appointed by the IAB [<a href="./rfc2014" title=""IRTF Research Group Guidelines and Procedures"">RFC2014</a>] for two-year terms
and manages the IRTF in consultation with the Internet Research
Steering Group (IRSG) and -- for some types of decisions -- the IAB.
The IRSG membership includes the IRTF Chair, the chairs of the
various RGs, and other individuals ("members at large") from the
research community selected by the IRTF Chair.
There is no general appeals process defined for the IRTF. However,
[<a href="./rfc2014" title=""IRTF Research Group Guidelines and Procedures"">RFC2014</a>] states that when an RG disagrees with the IRTF Chair's
decision to close the group, it can appeal to the IAB. Since the
IRTF Chair serves at the discretion of the IAB, it has been current
practice to generalize this special case in [<a href="./rfc2014" title=""IRTF Research Group Guidelines and Procedures"">RFC2014</a>]: any grievances
related to the IRTF Chair can be taken to the IAB, and it takes
appropriate measures.
<span class="grey">Eggert Informational [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc7827">RFC 7827</a> The Role of the IRTF Chair March 2016</span>
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Duties</span>
This section discusses the various duties of the IRTF Chair and
outlines the skill set a candidate for the role should ideally have.
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Strategic</span>
Arguably, the most important part of the duties of the IRTF Chair is
strategic and concerns shaping the purpose and scope of the IRTF, by
making decisions about which RGs to charter, which RGs to terminate,
and which other activities or efforts the IRTF should organize or
affiliate itself with in order to further its charter and increase
the interaction and collaboration between network research,
engineering, operations, and standardization.
For some new RGs, the research and engineering community brings a
proposal to the IRTF Chair for discussion. However, it is common for
the IRTF Chair to identify a new area of research that is considered
of importance to the Internet, actively motivate people in the
research and engineering community to consider the formation of an
RG, and help them navigate the process for doing so.
In order to be able to fulfill this duty, it is important for the
IRTF Chair to be involved in both the academic research community as
well as engineering or operational communities. Without a
demonstrated history of participation in these often somewhat
isolated communities, it will be very difficult to identify areas of
academic research that are suitable for being brought into the IRTF.
A good network of contacts in these communities will be very helpful
in identifying and motivating potential RG chairs and participants.
Involvement in the academic research community can be demonstrated in
various ways -- a publication record, membership in conference
program and organizational committees, participation in publicly
funded collaborative research projects, etc.
In addition to chartering new RGs, it is equally important for the
IRTF to end RGs that have run out of energy, are focused on issues no
longer considered important for the Internet, or are otherwise not
operating well. Careful communication and good people skills are
essential in order to explain the reasons for concluding an RG. The
same skill set is also useful when explaining to proponents of a new
RG why their request is being denied.
The Applied Networking Research Prize (ANRP) is a joint award of the
Internet Society (ISOC) and an example of a strategic initiative that
since its inception in 2011 has turned into more of an administrative
duty. The IRTF Chair and an ISOC representative pick and chair the
<span class="grey">Eggert Informational [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc7827">RFC 7827</a> The Role of the IRTF Chair March 2016</span>
ANRP selection committee, which advertises the ANRP, encourages
community nominations for the prizes, and reviews nominations and
selects prize winners. The IRTF Chair and the ISOC representative
also mentor the ANRP winners, who are often IETF newcomers, and
introduce them to other attendees who may have an interest in their
work.
Chairmanship of the ANRP selection committee also relies on strong
ties to the academic research community, to identify suitable
selection committee members and to encourage nominations for suitable
work that is published in a given year. The selection committee
operates similar to a program committee for an academic conference
(more specifically, it performs a function similar to the selection
of a best paper award). It is therefore useful if the IRTF Chair has
firsthand experience serving on program committees, and ideally,
chairing them.
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. Administrative</span>
A good fraction of the duties of the IRTF Chair are administrative.
Some of them may be permanently or temporarily delegated to other
IRSG members, but they ultimately always remain the IRTF Chair's
responsibility.
Some of those are related to publishing RFCs on the IRTF Stream, such
as ensuring sufficient review, so that documents published are of
good quality; scheduling the required Internet Engineering Steering
Group (IESG) review [<a href="./rfc5742" title=""IESG Procedures for Handling of Independent and IRTF Stream Submissions"">RFC5742</a>]; and following up with the IESG, IANA,
and the RFC Editor during and after the publication process.
Other administrative duties include reviewing and approving requests
from the RGs for time slots during IETF meetings or interim meetings
elsewhere, ensuring that meeting materials are submitted on schedule,
maintaining the IRTF web site, and -- in cooperation with the RG
chairs -- ensuring that the IETF Datatracker correctly reflects the
status of the various IRTF-related documents.
The IRTF Chair appoints, replaces, and manages the RG chairs and the
IRSG, and follows the research work of the chartered and proposed RGs
to a degree that is sufficient to let them develop an understanding
on whether they are generally operating well.
The IRTF Chair also defines the operational procedures for the IRTF
(in the boundaries defined by [<a href="./rfc2014" title=""IRTF Research Group Guidelines and Procedures"">RFC2014</a>]) and the IRSG. At the
moment, these procedures are captured as a set of wiki pages
[<a href="#ref-IRTF-WIKI">IRTF-WIKI</a>], and it is the duty of the IRTF Chair to refine and
update these descriptions as procedures evolve. When process
questions on the IRSG or in an RG arise (e.g., on IPR, liaison
<span class="grey">Eggert Informational [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc7827">RFC 7827</a> The Role of the IRTF Chair March 2016</span>
statements, consensus procedures, copyright, plagiarism, document
publication, etc.), the IRTF Chair is frequently consulted and needs
to have sufficient familiarity in the area to provide a definitive
answer, or at least be able to identify an external party for further
consultation.
The IRSG tries to schedule a working dinner during each IETF meeting,
and the IRTF Chair is responsible for organizing the agenda and a
suitable venue.
The IRTF Chair provides a status report on the IRTF to the IAB on a
monthly basis and also writes a regular column for the IETF Journal
[<a href="#ref-IETF-JOURNAL">IETF-JOURNAL</a>] on recent IRTF-related events.
During each IETF meeting, the IRTF Chair is responsible for
organizing and chairing the "IRTF Open Meeting", during which topics
related to the IRTF are presented and discussed. This includes a
report by the IRTF Chair on the status of the IRTF and its RGs (an
abbreviated version of this report is also usually given during the
IETF technical plenary) as well as other presentations from RGs, ANRP
prize winners, individuals wishing to propose new RGS, or others.
These administrative duties are very similar to part of the duties of
an Area Director (AD) in the IETF and require the same set of
organizational and communication skills [<a href="#ref-IESG-EXP" title=""Generic IESG Member Expertise"">IESG-EXP</a>]. They also
require a regular time commitment throughout the year, the ability to
attend most of the IETF meetings in person, as well as some other
related travel.
The IRTF Chair regularly interacts with the ADs and the IESG for
document reviews, planning IETF meeting agendas, and providing input
on various IETF efforts and topics. The IRTF Chair also regularly
interacts with the IETF Administrative Oversight Committee (IAOC) and
the IETF Secretariat for meeting planning, budgeting, and other
organizational purposes. In addition, the IRTF Chair also interacts
with the Tools Team to provide input on how IETF tools can best
support the operation of the IRTF. Finally, the IRTF Chair is the
owner of the IRTF Stream of RFCs and is hence part of the group that
reviews the RFC Editor's performance and operation; also, the IRTF
Chair engages with the Independent Submission Editor in cases where
submissions on the Independent Stream have relationships to the IRTF.
A good understanding of the purpose and procedures of these different
bodies and a good working relationship with the individuals serving
on them are important.
<span class="grey">Eggert Informational [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc7827">RFC 7827</a> The Role of the IRTF Chair March 2016</span>
<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. IAB Membership</span>
The IRTF Chair serves as an "ex officio" member of the IAB [<a href="./rfc2850" title=""Charter of the Internet Architecture Board (IAB)"">RFC2850</a>]
and is expected to participate in IAB discussions and activities
alongside the NomCom-appointed IAB members.
This duty benefits from expertise that is similar to those of full
IAB members [<a href="#ref-IAB-EXP" title=""Desired Expertise: Member of the Internet Architecture Board"">IAB-EXP</a>] and requires a similar time and travel
commitment, for example, to attend IAB retreats, relevant IAB
workshops, as well as other meetings the IAB is participating in or
organizing. Per [<a href="#ref-IAB-EXP" title=""Desired Expertise: Member of the Internet Architecture Board"">IAB-EXP</a>], "it is desirable for IAB members to have
technical leadership experience, operational management backgrounds,
research or academic backgrounds, implementation experience, and
experience in other bodies involved in Internet governance."
The IRTF Chair frequently provides input to "birds of a feather"
(BoF) sessions, either as an ex officio IAB member (i.e., as a "BoF
shepherd") or because it may be unclear whether a proposed effort
should be started as an IETF WG or an IRTF RG.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Security Considerations</span>
This document raises no security considerations.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Informative References</span>
[<a id="ref-IAB-EXP">IAB-EXP</a>] NomCom 2015, "Desired Expertise: Member of the Internet
Architecture Board", 2015,
<<a href="https://datatracker.ietf.org/nomcom/2015/requirements/#iab-member">https://datatracker.ietf.org/nomcom/2015/</a>
<a href="https://datatracker.ietf.org/nomcom/2015/requirements/#iab-member">requirements/#iab-member</a>>.
[<a id="ref-IESG-EXP">IESG-EXP</a>] NomCom 2015, "Generic IESG Member Expertise", August 2015,
<<a href="http://trac.tools.ietf.org/group/iesg/trac/wiki/GenericExpertise?version=18">http://trac.tools.ietf.org/group/iesg/trac/wiki/</a>
<a href="http://trac.tools.ietf.org/group/iesg/trac/wiki/GenericExpertise?version=18">GenericExpertise?version=18</a>>.
[<a id="ref-IETF-JOURNAL">IETF-JOURNAL</a>]
Internet Society, "The IETF Journal",
<<a href="http://www.internetsociety.org/publications/ietf-journal">http://www.internetsociety.org/publications/</a>
<a href="http://www.internetsociety.org/publications/ietf-journal">ietf-journal</a>>.
[<a id="ref-IRTF-WIKI">IRTF-WIKI</a>]
Internet Research Task Force, "IRTF Wiki",
<<a href="http://trac.tools.ietf.org/group/irtf/trac/wiki">http://trac.tools.ietf.org/group/irtf/trac/wiki</a>>.
[<a id="ref-RFC2014">RFC2014</a>] Weinrib, A. and J. Postel, "IRTF Research Group Guidelines
and Procedures", <a href="https://www.rfc-editor.org/bcp/bcp8">BCP 8</a>, <a href="./rfc2014">RFC 2014</a>, DOI 10.17487/RFC2014,
October 1996, <<a href="http://www.rfc-editor.org/info/rfc2014">http://www.rfc-editor.org/info/rfc2014</a>>.
<span class="grey">Eggert Informational [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc7827">RFC 7827</a> The Role of the IRTF Chair March 2016</span>
[<a id="ref-RFC2850">RFC2850</a>] Internet Architecture Board and B. Carpenter, Ed.,
"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>, DOI 10.17487/RFC2850, May 2000,
<<a href="http://www.rfc-editor.org/info/rfc2850">http://www.rfc-editor.org/info/rfc2850</a>>.
[<a id="ref-RFC4440">RFC4440</a>] Floyd, S., Ed., Paxson, V., Ed., Falk, A., Ed., and IAB,
"IAB Thoughts on the Role of the Internet Research Task
Force (IRTF)", <a href="./rfc4440">RFC 4440</a>, DOI 10.17487/RFC4440, March 2006,
<<a href="http://www.rfc-editor.org/info/rfc4440">http://www.rfc-editor.org/info/rfc4440</a>>.
[<a id="ref-RFC5742">RFC5742</a>] Alvestrand, H. and R. Housley, "IESG Procedures for
Handling of Independent and IRTF Stream Submissions",
<a href="https://www.rfc-editor.org/bcp/bcp92">BCP 92</a>, <a href="./rfc5742">RFC 5742</a>, DOI 10.17487/RFC5742, December 2009,
<<a href="http://www.rfc-editor.org/info/rfc5742">http://www.rfc-editor.org/info/rfc5742</a>>.
[<a id="ref-RFC5743">RFC5743</a>] Falk, A., "Definition of an Internet Research Task Force
(IRTF) Document Stream", <a href="./rfc5743">RFC 5743</a>, DOI 10.17487/RFC5743,
December 2009, <<a href="http://www.rfc-editor.org/info/rfc5743">http://www.rfc-editor.org/info/rfc5743</a>>.
Acknowledgments
Robert Sparks, Brian Trammell, Stephen Farrell, Niels ten Oever, Dirk
Kutscher, Aaron Falk, Jana Iyengar, Mat Ford, Adrian Farrel, Barry
Leiba, and Dave Thaler provided suggestions that improved this
document.
Lars Eggert has received funding from the European Union's Horizon
2020 research and innovation program 2014-2018 under grant agreement
No. 644866 ("SSICLOPS"). This document reflects only the author's
views, and the European Commission is not responsible for any use
that may be made of the information it contains.
Author's Address
Lars Eggert
NetApp
Sonnenallee 1
Kirchheim bei Muenchen 85551
Germany
Phone: +49 151 120 55791
Email: lars@netapp.com
Eggert Informational [Page 7]
</pre>
|
