idnits 2.17.00 (12 Aug 2021) /tmp/idnits36870/draft-eggert-irtf-rfc2014bis-05.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (November 23, 2018) is 1268 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- -- Obsolete informational reference (is this intentional?): RFC 1603 (Obsoleted by RFC 2418) Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Research Task Force (IRTF) L. Eggert 3 Internet-Draft NetApp 4 Obsoletes: 2014 (if approved) November 23, 2018 5 Intended status: Informational 6 Expires: May 27, 2019 8 IRTF Research Group Guidelines and Procedures 9 draft-eggert-irtf-rfc2014bis-05 11 Abstract 13 The Internet Research Task Force (IRTF) has responsibility for 14 organizing groups to investigate research topics related to the 15 Internet protocols, applications, and technology. IRTF activities 16 are organized into Research Groups. This document describes the 17 guidelines and procedures for formation and operation of IRTF 18 Research Groups. It describes the relationship between IRTF 19 participants, Research Groups, the Internet Research Steering Group 20 (IRSG) and the Internet Architecture Board (IAB). The basic duties 21 of IRTF participants, including the IRTF Chair, Research Group Chairs 22 and IRSG members are defined. 24 This document obsoletes RFC2014. 26 Status of This Memo 28 This Internet-Draft is submitted in full conformance with the 29 provisions of BCP 78 and BCP 79. 31 Internet-Drafts are working documents of the Internet Engineering 32 Task Force (IETF). Note that other groups may also distribute 33 working documents as Internet-Drafts. The list of current Internet- 34 Drafts is at https://datatracker.ietf.org/drafts/current/. 36 Internet-Drafts are draft documents valid for a maximum of six months 37 and may be updated, replaced, or obsoleted by other documents at any 38 time. It is inappropriate to use Internet-Drafts as reference 39 material or to cite them other than as "work in progress." 41 This Internet-Draft will expire on May 27, 2019. 43 Copyright Notice 45 Copyright (c) 2018 IETF Trust and the persons identified as the 46 document authors. All rights reserved. 48 This document is subject to BCP 78 and the IETF Trust's Legal 49 Provisions Relating to IETF Documents 50 (https://trustee.ietf.org/license-info) in effect on the date of 51 publication of this document. Please review these documents 52 carefully, as they describe your rights and restrictions with respect 53 to this document. Code Components extracted from this document must 54 include Simplified BSD License text as described in Section 4.e of 55 the Trust Legal Provisions and are provided without warranty as 56 described in the Simplified BSD License. 58 Table of Contents 60 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 61 1.1. IRTF Approach . . . . . . . . . . . . . . . . . . . . . . 4 62 1.2. IRTF and Intellectual Property Rights . . . . . . . . . . 5 63 2. Research Group Formation . . . . . . . . . . . . . . . . . . 5 64 2.1. Criteria for Formation . . . . . . . . . . . . . . . . . 6 65 2.2. Charter . . . . . . . . . . . . . . . . . . . . . . . . . 7 66 3. Research Group Operation . . . . . . . . . . . . . . . . . . 8 67 3.1. Meeting Planning . . . . . . . . . . . . . . . . . . . . 9 68 3.2. Meeting Venue . . . . . . . . . . . . . . . . . . . . . . 9 69 3.3. Meeting Management . . . . . . . . . . . . . . . . . . . 10 70 4. Research Group Termination . . . . . . . . . . . . . . . . . 10 71 5. Staff Roles . . . . . . . . . . . . . . . . . . . . . . . . . 10 72 5.1. IRTF Chair . . . . . . . . . . . . . . . . . . . . . . . 10 73 5.2. IRSG Member . . . . . . . . . . . . . . . . . . . . . . . 11 74 5.3. Research Group Chair . . . . . . . . . . . . . . . . . . 11 75 5.4. Research Group Editor/Secretary . . . . . . . . . . . . . 13 76 6. Research Group Documents . . . . . . . . . . . . . . . . . . 13 77 6.1. Meeting Documents . . . . . . . . . . . . . . . . . . . . 13 78 6.2. Request For Comments (RFC) . . . . . . . . . . . . . . . 14 79 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 80 8. Security Considerations . . . . . . . . . . . . . . . . . . . 14 81 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 14 82 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 15 83 10.1. Normative References . . . . . . . . . . . . . . . . . . 15 84 10.2. Informative References . . . . . . . . . . . . . . . . . 15 85 Appendix A. Changes from RFC2014 . . . . . . . . . . . . . . . . 16 86 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 17 88 1. Introduction 90 This document defines guidelines and procedures for Internet Research 91 Task Force (IRTF) Research Groups. It obsoletes [RFC2014], which 92 originally documented them. The IRTF focuses on longer term research 93 issues related to the Internet, while its parallel organization, the 94 Internet Engineering Task Force (IETF), focuses on shorter term 95 issues of engineering and standards making. 97 The IRTF is composed of a number of focused, long-term, small 98 Research Groups. These groups work on topics related to Internet 99 protocols, applications, architecture and technology. Research 100 Groups are expected to have the stable, long-term membership needed 101 to promote the development of research collaboration and teamwork in 102 exploring research issues. Participation is by individual 103 contributors, rather than by representatives of organizations. 105 The IRTF is managed by the IRTF Chair in consultation with the 106 Internet Research Steering Group (IRSG). The IRSG membership 107 includes the IRTF Chair, the chairs of the various Research Groups 108 and possibly other individuals ("members-at-large") from the research 109 community. 111 The IRTF Chair is appointed by the Internet Architecture Board (IAB) 112 [RFC2850][IAB], the Research Group chairs are appointed as part of 113 the formation of Research Groups (as detailed below) and the IRSG 114 members-at-large are chosen by the IRTF Chair in consultation with 115 the rest of the IRSG and on approval by the IAB. 117 In addition to managing the Research Groups, the IRSG MAY from time 118 to time hold topical workshops focusing on research areas of 119 importance to the evolution of the Internet, or more general 120 workshops to, for example, discuss research priorities from an 121 Internet perspective. 123 This document defines procedures and guidelines for the formation and 124 operation of Research Groups in the IRTF. The duties of the IRTF 125 Chair, the Research Group Chairs and IRSG members are also described; 126 the first is also described in more detail in [RFC7827]. Except for 127 members-at-large of the IRSG, there is no general participation in 128 the IRTF, only participation in a specific Research Group. However, 129 since around 2010, the IRTF has begun to hold "open meetings" during 130 IETF meetings [IRTFOPEN], and a mailing list was created for 131 discussion of IRTF-wide topics [IRTF-DISCUSS], both allowing the 132 community to engage with the IRTF. 134 [RFC4440] provides additional important background information that 135 the readers of this document should familiarize themselves with. 136 [RFC7418] provides an introduction to the IRTF for IETF participants, 137 focusing on the differences between the two organizations. 139 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 140 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 141 document are to be interpreted as described in [RFC2119]. 143 1.1. IRTF Approach 145 The reader is encouraged to study The Internet Standards Process 146 [RFC2026] to gain a complete understanding of the philosophy, 147 procedures and guidelines of the IETF and its approach to standards 148 making. 150 The IRTF does not set standards, and thus has somewhat different and 151 complementary philosophy and procedures. In particular, an IRTF 152 Research Group is expected to be long-lived, producing a sequence of 153 "products" over time. The products of a Research Group (often 154 abbreviated as "RG") are research results that may be disseminated by 155 publication in scholarly journals and conferences, as white papers 156 for the community, as Informational RFCs, and so on. In addition, it 157 is expected that any concrete technologies developed in a Research 158 Group will be brought to the IETF as input to IETF Working Group(s) 159 or in the form of birds-of-a-feather (BoF) sessions for possible 160 standardization. However, Research Group input carries no more 161 weight than other community input, and goes through the same 162 standards setting process as any other proposal. 164 IRTF Research Groups are formed to encourage research in areas of 165 importance to the evolution of the Internet. Clearly, anyone may 166 conduct such research, whether or not they are members of a Research 167 Group. The expectation is that by sponsoring Research Groups, the 168 IRTF can foster cross-organizational collaboration, help to create 169 "critical mass" in important research areas, and add to the 170 visibility and impact of the work. 172 IRTF Research Groups may have open or closed memberships. Limited 173 membership may be advantageous to the formation of the long term 174 working relationships that are critical to successful collaborative 175 research. However, limited membership MUST be used with care and 176 sensitivity to avoid unnecessary fragmentation of the work of the 177 research community. Allowing limited membership is in stark contrast 178 to IETF Working Groups, which are always open; this contrast reflects 179 the different goals and environments of the two organizations - 180 research vs. standards setting. 182 To ameliorate the effects of closed membership, all Research Groups 183 are REQUIRED to regularly report progress to the community, and are 184 encouraged to hold occasional open meetings (most likely co-located 185 with IETF meetings). In addition, the IRTF may host open plenaries 186 at regular IETF meetings during which research results of interest to 187 the community are presented. Finally, multiple Research Groups 188 working in the same general area may be formed, if appropriate. 190 Even more than the IETF, the work of the IRSG is expected to be 191 marked by informality. The goal is to encourage and foster valuable 192 research, not to add burdensome bureaucracy to the endeavor. 194 1.2. IRTF and Intellectual Property Rights 196 The IRTF follows the IETF Intellectual Property Rights (IPR) 197 disclosure rules, as described in Section 3.2 of [RFC5743]. This is 198 a summary of these rules as they relate to IRTF research group 199 discussions, mailing lists and Internet Drafts: 201 o If a participant includes their own or their employer's IPR in a 202 contribution to an IRTF research group, then they must file an IPR 203 disclosure with the IETF. 205 o If a participant recognizes their own or their employer's IPR in 206 someone else's contribution and they are participating in the 207 discussions in the research group relating to that contribution, 208 then they must file an IPR disclosure with the IETF. Even if they 209 are not participating in the discussion, the IRTF still requests 210 that they file an IPR disclosure with the IETF. 212 o Finally, the IRTF requests that a participant file an IPR 213 disclosure with the IETF if they recognize IPR owned by others in 214 any IRTF contribution. 216 Participants may file an IPR disclosure here: 217 http://www.ietf.org/ipr/file-disclosure 219 See [RFC8179] for definitions of "IPR" and "contribution" and for the 220 detailed rules (substituting "IRTF" for "IETF"). 222 2. Research Group Formation 224 Research Groups are the activity centers in the IRTF. A Research 225 Group is typically created to address a research area related to 226 Internet protocols, applications, architecture or technology area. 227 Research Groups have the stable, long-term membership needed to 228 promote the development of research collaboration and teamwork in 229 exploring research issues. Participation is by individual 230 contributors, rather than by representatives of organizations. 232 A Research Group may be established at the initiative of an 233 individual or group of individuals. Anyone interested in creating an 234 IRTF Research Group MUST submit a charter for the proposed group to 235 the IRTF Chair along with a list of proposed founding members. The 236 charter SHALL be reviewed by the IRSG and then forwarded to the IAB 237 for approval. If approved, the charter is placed on the IRTF Web 238 site. 240 This process allows the IRTF Chair considerable freedom in how to 241 decide to charter new work, and different approaches have been tried. 242 One approach seems to have worked well recently, and is therefore 243 briefly described here as an example: Under this approach, the IRTF 244 Chair permits the proponents of new Research Groups to start a 245 mailing list under the irtf.org domain, schedule meetings during IETF 246 weeks and elsewhere for their new group, and otherwise act as if they 247 were already formally chartered. These RGs are referred to as 248 "Proposed RGs" in the IETF Datatracker, on the meeting agenda, etc. 249 and while they often create a wiki page for themselves, their charter 250 is not posted on the IRTF web site, in order to distinguish them from 251 officially chartered RGs. After roughly a year, the IRTF Chair 252 reviews the progress, activity levels and general operation of the 253 Proposed RG, and decides to formally charter or abandon the effort. 255 2.1. Criteria for Formation 257 In determining whether it is appropriate to create a Research Group, 258 the IRTF Chair, the IRSG and the IAB SHALL consider several issues: 260 o Is the research area that the Research Group plans to address 261 clear and relevant for the Internet community? 263 o Will the formation of the Research Group foster work that would 264 not be done otherwise? For instance, membership drawn from more 265 than a single institution, more than a single country, and so on, 266 is to be encouraged. 268 o Do the Research Group's activities overlap with those of another 269 Research Group? If so, it may still be appropriate to create the 270 Research Group, but this question must be considered carefully 271 since subdividing efforts often dilutes the available technical 272 expertise. 274 o Is there sufficient interest and expertise in the Research Group's 275 topic with at least several people willing to expend the effort 276 that is likely to produce significant results over time? Research 277 Groups require considerable effort, including management of the 278 Research Group process, editing of Research Group documents, and 279 contribution to the document text. 281 The Internet Architecture Board (IAB) SHALL also review the charter 282 of the proposed Research Group to determine the relationship of the 283 proposed work to the overall architecture of the Internet Protocol 284 Suite. 286 2.2. Charter 288 A charter is a contract between a Research Group and the IRTF to 289 conduct research in the designated area. Charters MAY be 290 renegotiated periodically to reflect changes to the current status, 291 organization or goals of the Research Group. 293 The formation of a Research Group requires a charter, which is 294 initially negotiated between a prospective Research Group Chair and 295 the IRTF Chair. When the prospective Chair and the IRTF Chair are 296 satisfied with the charter form and content, it becomes the basis for 297 forming a Research Group. 299 A IRTF Research Group charter consists of five sections: 301 1. Research Group Name 303 A Research Group name SHOULD be reasonably descriptive or 304 identifiable. Additionally, the group SHALL define a short 305 acronym (consisting of printable US-ASCII characters) to 306 reference the group in the IRTF directories, mailing lists, and 307 general documents. The name and acronym MUST NOT conflict with 308 any past or existing IETF or IRTF names and acronyms. It is 309 helpful if the acronym ends with "RG", to help distinguish 310 Research Groups from IETF Working Groups. 312 2. Chair(s) 314 The Research Group may have a small number of Chair(s) to perform 315 the administrative functions of the group. The email address(es) 316 of the Chair(s) SHALL be included. 318 3. Mailing list(s) 320 Each Research Group SHALL have an address (possibly a Chair's) 321 for members of the Internet community to send queries regarding 322 the Research Group. For instance, for requests to join the 323 group. 325 A Research Group, whether limited-membership or open, SHALL have 326 an Internet mailing list open to all interested parties. This 327 list is used for an open discussion of the issues and 328 announcements of results as they become available. Included 329 SHOULD be the address to which an interested party sends a 330 subscription request for the interest list and the procedures to 331 follow when subscribing, and the location of the interest mailing 332 list archive. It is RECOMMENDED that this mailing list be hosted 333 under the irtf.org domain, so its archive will remain available 334 in the future. 336 It is expected that a limited-membership Research Group MAY also 337 have a mailing list limited to the regular meeting participants 338 on which substantial part of the work of a Research Group is 339 likely to be conducted via e-mail. 341 4. Membership Policy 343 The Charter MUST define the membership policy (whether open or 344 limited), and the procedure to apply for membership in the group. 345 While limited membership is permitted, it is in no way encouraged 346 or required. 348 5. Description of Research Group 350 The focus and intent of the group SHALL be set forth briefly. By 351 reading this section alone, an individual should be able to 352 decide whether this group is relevant to their own work. The 353 first paragraph SHOULD give a brief summary of the research area, 354 basis, goal(s) and approach(es) planned for the Research Group. 355 This paragraph will frequently be used as an overview of the 356 Research Group's effort. 358 To facilitate evaluation of the intended work and to provide on- 359 going guidance to the Research Group, the charter SHALL describe 360 the proposed research and SHALL discuss objectives and expected 361 impact with respect to the Internet Architecture. 363 3. Research Group Operation 365 Research Groups are autonomous and each determines most of the 366 details of its own operation with respect to session participation, 367 reaching closure, norms of behavior, etc. Since the products are 368 research results, not Internet standards, consensus of the group is 369 not required. Rather, the measure of success is the quality and 370 impact of the research results. 372 A number of procedural questions and issues will arise over time, and 373 it is the function of the Research Group Chairs to manage the group 374 process, keeping in mind that the overall purpose of the group is to 375 make progress towards realizing the Research Group's goals and 376 objectives. 378 There are few hard and fast rules on organizing or conducting 379 Research Group activities, but a set of guidelines and practices have 380 evolved over time that have proven successful. These are listed 381 here, with actual choices typically determined by the Research Group 382 members and a Chair. 384 3.1. Meeting Planning 386 For coordinated, structured Research Group interactions, a Chair MUST 387 publish to the group mailing list a draft agenda well in advance of 388 the actual meeting. The agenda needs to contain at least: 390 o The items for discussion; 392 o The estimated time necessary per item; and 394 o A clear indication of what documents the participants will need to 395 read before the meeting in order to be well prepared. 397 A Research Group will conduct much of its business via its electronic 398 mail distribution list(s). It is also likely to meet periodically to 399 accomplish those things that are better achieved in more interactive 400 meetings, such as brainstorming, heated altercations, etc. Meetings 401 MAY be scheduled as telephone conference, video teleconference, or 402 face-to-face (physical) meetings. 404 It is REQUIRED that all Research Group meetings be recorded in 405 written minutes, to keep informed members who were not present and 406 the community at large and to document the proceedings for present 407 and future members. These minutes SHOULD include the agenda for the 408 meeting, an account of the high points of the discussion, and a list 409 of attendees. Unless the Research Group chair decides otherwise, the 410 minutes SHOULD be sent to the interest list and made available 411 through other channels, e.g., the IETF proceedings web pages. 413 3.2. Meeting Venue 415 Each Research Group SHALL determine the balance of email and face-to- 416 face meetings that is appropriate for making progress on its goals. 418 Electronic mail permits the easiest and most affordable 419 participation; face-to-face meetings often permit better focus, more 420 productive debate and enhanced working relationships. 422 Face-to-face meetings are encouraged to be held co-located with the 423 regular IETF meetings to minimize travel, since IRTF members are 424 often also active in the IETF, and to encourage the cross- 425 fertilization that occurs during hallway and after-hours 426 interactions. Furthermore, as described above, even limited- 427 membership Research Groups are encouraged to hold occasional open 428 meetings; an IETF meeting would serve as an ideal venue for such an 429 event. 431 Face-to-face meetings that are collocated with academic conferences 432 or workshops have also worked well for some Research Groups, 433 particularly those with substantial academic participation. Such 434 groups are still encouraged to occasionally collocate a meeting with 435 an IETF meeting, in order to facilitate the cross-fertilization 436 between research and engineering that the IRTF is chartered to 437 stimulate. 439 3.3. Meeting Management 441 The challenge of managing Research Group meetings is to balance the 442 need for consideration of the various issues, opinions and approaches 443 against the need to allow forward progress. The Research Group, as a 444 whole, has the final responsibility for striking this balance. 446 4. Research Group Termination 448 If, at some point, it becomes evident that a Research Group is not 449 making progress in the research areas defined in its charter, or 450 fails to regularly report the results of its research to the 451 community, the IRTF Chair can either: 453 1. Require that the group recharter to refocus on a different set of 454 problems, 456 2. Request that the group choose new Chair(s), or 458 3. Disband the group. 460 The IRTF Chair is encouraged to make this decision after consulting 461 with the RG. However, if the RG disagrees with the chair's decision, 462 it MAY appeal to the IAB. 464 5. Staff Roles 466 Research Groups require considerable care and feeding. In addition 467 to general participation, successful Research Groups benefit from the 468 efforts of participants filling specific functional roles. 470 5.1. IRTF Chair 472 The IRTF Chair is responsible for ensuring that Research Groups 473 produce coherent, coordinated, architecturally consistent and timely 474 output as a contribution to the overall evolution of the Internet 475 architecture. In addition to the detailed tasks related to Research 476 Groups outlined below, the IRTF Chair MAY also from time to time 477 arrange for topical workshops attended by the IRSG and perhaps other 478 experts in the field. 480 Planning 482 The IRTF Chair monitors the range of activities. This may include 483 encouraging the formation of Research Groups directly, rather than 484 waiting for proposals from IRTF participants. 486 Coordination of Research Groups 488 The IRTF Chair coordinates the work done by the various Research 489 Groups. 491 Reporting 493 The IRTF Chair reports on IRTF progress to the to the IAB and the 494 wider Internet community. 496 Progress tracking 498 The IRTF Chair tracks and manages the progress of the various 499 Research Groups with the aid of a regular status report on 500 documents and accomplishments from the Research Group Chairs. The 501 resulting reports are made available to the community at large at 502 regular intervals. The IRTF Chair MAY use the IETF Datatracker to 503 manage the status of Internet Drafts authored by the various 504 Research Groups [RFC6322]. 506 5.2. IRSG Member 508 Members of the IRSG are responsible for advising the IRTF Chair on 509 the chartering of new Research Groups and other matters relating to 510 the smooth operation of the IRTF. They are also responsible for 511 helping review documents that are being published on the IRTF Stream 512 [RFC5743]. In addition, most IRSG members are also Research Group 513 chairs. 515 5.3. Research Group Chair 517 A Research Group Chair is concerned with making forward progress in 518 the areas under investigation, and has wide discretion in the conduct 519 of Research Group business. A Chair MUST ensure that a number of 520 tasks are performed, either directly or by others assigned to the 521 tasks. This encompasses at the very least the following: 523 Ensuring the Research Group process and content management 524 A Chair has ultimate responsibility for ensuring that a Research 525 Group achieves forward progress. For some Research Groups, this 526 can be accomplished by having a Chair perform all management- 527 related activities. In other Research Groups - particularly those 528 with large or divisive participation - it is helpful to allocate 529 process and/or secretarial functions to other participants, after 530 approval from the IRTF Chair. Process management pertains 531 strictly to the style of Research Group interaction and not to its 532 content. Research Group Chairs remain responsible for all actions 533 a Secretary performs on their behalf. 535 Moderate the Research Group email list 537 A Chair SHOULD attempt to ensure that the discussions on a list 538 are relevant and do not devolve to "flame" attacks or rat-hole 539 into technical trivia. A Chair SHOULD make sure that discussions 540 on the list are summarized and that the outcome is well documented 541 (to avoid repetition). 543 Organize, prepare and chair face-to-face and on-line formal meetings 545 A Chair SHOULD plan and announce meetings well in advance. (See 546 Section 3.1 for procedures.) 548 Communicate results of meetings 550 A Chair and/or Secretary MUST ensure that minutes of a meeting are 551 taken and published to the participants. 553 Distribute the work 555 It is expected that all Research Group participants will actively 556 contribute to the work of the group. Research Group membership is 557 expected to be a long-term commitment by a set of motivated 558 members of the research community. Of course, at any given time, 559 more of the work is likely to be done by a few participants with 560 particular interests, set of skills and ideas. It is the task of 561 the Chair to motivate enough experts to allow for a fair 562 distribution of the workload. 564 Document development 566 Research Groups produce documents and documents need authors. 567 However, authorship of papers related to the work of a Research 568 Group is one of the primary reasons that researchers become 569 members, so finding motivated authors should not be a problem. It 570 is up to the Research Group to decide the authorship of papers 571 resulting from Research Group activities. In particular, 572 authorship by the entire group is not required. The Research 573 Group Chair MAY use the IETF Datatracker to manage the status of 574 Internet Drafts authored by the group [RFC6322]. 576 Document publication 578 The IRTF Chair, RG Chair and/or Secretary SHALL work with the 579 IESG, IANA and the RFC Editor to ensure documents to be published 580 as RFCs conform with RFC publication requirements, such as the 581 conflict review defined in [RFC5742] and to coordinate any 582 editorial changes suggested by the RFC Editor. 584 The publication process has been changing over the years and is 585 expected to continue to change on occasion. In addition, the IRTF 586 Chair has freedom to decide how IRTF documents are reviewed and 587 approved before being sent onward for publication. For at least the 588 last ten years, the detailed publication process has been documented 589 on a wiki page [IRTF-RFCs]. 591 5.4. Research Group Editor/Secretary 593 Taking minutes and editing jointly-authored Research Group documents 594 often is performed by a specifically-designated participant or set of 595 participants appointed by an RG Chair and approval from the IRTF 596 Chair. 598 6. Research Group Documents 600 6.1. Meeting Documents 602 All relevant documents for a meeting (including the final agenda) 603 SHOULD be published and be made available as Internet Drafts at least 604 two weeks before a meeting starts. If a meeting is collocated with 605 an IETF meeting, the agenda and document submission deadlines 606 communicated for that IETF meeting take precedence. 608 It is strongly RECOMMENDED that a Research Group Chair make sure that 609 all meeting materials are made available via the IETF Datatracker's 610 proceedings system, which also handles "interim" meetings not 611 collocated with IETF meetings. All relevant documents (including the 612 final agenda and the minutes of the meeting) SHOULD be placed there. 613 This has the advantage that all participants can retrieve all files 614 and thus make sure they have all relevant documents. 616 6.2. Request For Comments (RFC) 618 The work of an IRTF Research Group usually results in publication of 619 research papers and other documents, as well as Informational or 620 Experimental Request For Comments (RFCs). The RFC series is the 621 archival publication record for the Internet community. Since 2009, 622 IRTF RFCs have been published on a separate IRTF Document Stream 623 [RFC5743]. A document can be written by individuals in a Research 624 Group, by the group as a whole with a designated Editor, or by others 625 not involved with the IRTF. The designated author(s) need not 626 include the group Chair(s). Initial publication as an Internet Draft 627 is preferred, if only to facilitate review, before asking for RFC 628 publication. 630 NOTE: The RFC series is a publication mechanism only and publication 631 does not determine the status of a document. Status is determined 632 through separate, explicit status labels. In other words, the reader 633 is reminded that all Internet Standards are published as RFCs, but 634 NOT all RFCs specify standards. 636 The RFC's authors are expected to work with the RFC Editor to meet 637 all formatting, review and other requirements that the RFC Editor, 638 IAB or IESG may impose. [RFC5743] describes the approach that 639 Research Groups follow when they want to publish RFCs on the IRTF 640 Stream. In summary, after the group has decided that a given 641 document is ready, a Chair initiates an IRSG Review. After approval 642 by the IRSG, the IESG reviews the document for conflicts with the 643 Internet Standards Process as described in [RFC5742]. After the IESG 644 review concludes, the document undergoes final publication 645 preparation at the RFC Editor. 647 7. IANA Considerations 649 This document has no IANA considerations. 651 8. Security Considerations 653 Security issues are not discussed in this memo. 655 9. Acknowledgments 657 This document is based on the October 1996 RFC "IRTF Research Group 658 Guidelines and Procedures" by A. Weinrib [RFC2014], which in turn 659 was based on the March 1994 RFC "IETF Working Group Guidelines and 660 Procedures" by E. Huizer and D. Crocker [RFC1603]. 662 Lars Eggert has received funding from the European Union's Horizon 663 2020 research and innovation program 2014-2018 under grant agreement 664 No. 644866 ("SSICLOPS"). This document reflects only the authors' 665 views and the European Commission is not responsible for any use that 666 may be made of the information it contains. 668 10. References 670 10.1. Normative References 672 [RFC2014] Weinrib, A. and J. Postel, "IRTF Research Group Guidelines 673 and Procedures", BCP 8, RFC 2014, DOI 10.17487/RFC2014, 674 October 1996, . 676 [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 677 3", BCP 9, RFC 2026, DOI 10.17487/RFC2026, October 1996, 678 . 680 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 681 Requirement Levels", BCP 14, RFC 2119, 682 DOI 10.17487/RFC2119, March 1997, 683 . 685 [RFC5742] Alvestrand, H. and R. Housley, "IESG Procedures for 686 Handling of Independent and IRTF Stream Submissions", 687 BCP 92, RFC 5742, DOI 10.17487/RFC5742, December 2009, 688 . 690 [RFC8179] Bradner, S. and J. Contreras, "Intellectual Property 691 Rights in IETF Technology", BCP 79, RFC 8179, 692 DOI 10.17487/RFC8179, May 2017, 693 . 695 10.2. Informative References 697 [IAB] IAB, "Internet Architecture Board Description", n.d., 698 . 700 [IRTF-DISCUSS] 701 IRTF, "IRTF General and New-Work Discussion List", n.d., 702 . 704 [IRTF-RFCs] 705 IRTF, "IRTF RFC Process", n.d., 706 . 709 [IRTFOPEN] 710 IRTF, "IRTF Open Meeting", n.d., 711 . 713 [RFC1603] Huizer, E. and D. Crocker, "IETF Working Group Guidelines 714 and Procedures", RFC 1603, DOI 10.17487/RFC1603, March 715 1994, . 717 [RFC2850] Internet Architecture Board and B. Carpenter, Ed., 718 "Charter of the Internet Architecture Board (IAB)", 719 BCP 39, RFC 2850, DOI 10.17487/RFC2850, May 2000, 720 . 722 [RFC4440] Floyd, S., Ed., Paxson, V., Ed., Falk, A., Ed., and IAB, 723 "IAB Thoughts on the Role of the Internet Research Task 724 Force (IRTF)", RFC 4440, DOI 10.17487/RFC4440, March 2006, 725 . 727 [RFC5743] Falk, A., "Definition of an Internet Research Task Force 728 (IRTF) Document Stream", RFC 5743, DOI 10.17487/RFC5743, 729 December 2009, . 731 [RFC6322] Hoffman, P., "Datatracker States and Annotations for the 732 IAB, IRTF, and Independent Submission Streams", RFC 6322, 733 DOI 10.17487/RFC6322, July 2011, 734 . 736 [RFC7418] Dawkins, S., Ed., "An IRTF Primer for IETF Participants", 737 RFC 7418, DOI 10.17487/RFC7418, December 2014, 738 . 740 [RFC7827] Eggert, L., "The Role of the IRTF Chair", RFC 7827, 741 DOI 10.17487/RFC7827, March 2016, 742 . 744 Appendix A. Changes from RFC2014 745 +-----+-------------------------------------------------------------+ 746 | Rev | Changes | 747 +-----+-------------------------------------------------------------+ 748 | -05 | More feedback from Niels ten Oever. Fixed typos. RFC5793 -> | 749 | | RFC8179. Converted to kramdown-rfc2629. | 750 | | | 751 | -04 | Addressed feedback from Mat Ford, Niels ten Oever and | 752 | | Martin Thomson. | 753 | | | 754 | -03 | Changed the stream to IRTF and status to Informational, per | 755 | | discussion with the IAB at the Cambridge, MA retreat. Added | 756 | | funding acknowledgment. | 757 | | | 758 | -02 | Added text about and reference to [RFC7418]. Add pointer to | 759 | | IRTF RFC process wiki. More wordsmithing. | 760 | | | 761 | -01 | Use [RFC2119] terms instead of local definitions. Fix | 762 | | idnits (missing IANA section, say that we obsolete | 763 | | [RFC2014], etc.) Update obsoleted references. Update | 764 | | acknowledgments. Remove text about the Internet Monthly | 765 | | Report (IMR). Remove text that says that a RG should have | 766 | | 4-5 members, and that proposed charters should include the | 767 | | names of such "charter members". Add suggestion that RG | 768 | | acronyms end in "RG". Change recommendation that RGs have | 769 | | 1-2 chairs to instead say "a small number", to allow cases | 770 | | where more than two chairs are useful. Update text on IRTF | 771 | | RFC Stream publication [RFC5742][RFC5743]. Add text on IRTF | 772 | | IPR policies. Add pointers and text to [RFC4440] and | 773 | | [RFC6322]. | 774 | | | 775 | -00 | Document contains the entire, unmodified contents of | 776 | | [RFC2014], except for (1) boilerplate and layout changes | 777 | | that are due to the conversion to xml2rfc and (2) changed | 778 | | author information. It is being submitted so that it will | 779 | | be easier to view diffs of the content changes that will be | 780 | | introduced in subsequent versions. | 781 +-----+-------------------------------------------------------------+ 783 Author's Address 785 Lars Eggert 786 NetApp 788 Email: lars@netapp.com 789 URI: https://eggert.org/