idnits 2.17.1 draft-ietf-iasa2-rfc2031bis-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 : ---------------------------------------------------------------------------- -- The draft header indicates that this document obsoletes RFC2031, but the abstract doesn't seem to directly say this. It does mention RFC2031 though, so this could be OK. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (July 1, 2019) is 1762 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- -- Obsolete informational reference (is this intentional?): RFC 2028 (Obsoleted by RFC 9281) -- Obsolete informational reference (is this intentional?): RFC 2031 (Obsoleted by RFC 8712) -- Obsolete informational reference (is this intentional?): RFC 2282 (Obsoleted by RFC 2727) -- Obsolete informational reference (is this intentional?): RFC 4071 (Obsoleted by RFC 8711) -- Obsolete informational reference (is this intentional?): RFC 4371 (Obsoleted by RFC 8714) -- Obsolete informational reference (is this intentional?): RFC 7437 (Obsoleted by RFC 8713) Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 8 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 IETF Administrative Support Activity 2 G. Camarillo 3 Internet-Draft Ericsson 4 Obsoletes: 2031 (if approved) J. Livingood 5 Intended status: Informational Comcast 6 Expires: January 2, 2020 July 1, 2019 8 The IETF-ISOC Relationship 9 draft-ietf-iasa2-rfc2031bis-05 11 Abstract 13 This document summarises the Internet Engineering Task Force (IETF) - 14 Internet Society (ISOC) relationship, following a major revision to 15 the structure of the IETF Administrative Support Activity (IASA) in 16 2018. The IASA was revised under a new "IASA 2.0" structure by the 17 IASA2 Working Group, which changed the IETF's administrative, legal, 18 and financial structure. As a result, it also changed the 19 relationship between the IETF and ISOC, which made it necessary to 20 revise RFC 2031. 22 Status of This Memo 24 This Internet-Draft is submitted in full conformance with the 25 provisions of BCP 78 and BCP 79. 27 Internet-Drafts are working documents of the Internet Engineering 28 Task Force (IETF). Note that other groups may also distribute 29 working documents as Internet-Drafts. The list of current Internet- 30 Drafts is at https://datatracker.ietf.org/drafts/current/. 32 Internet-Drafts are draft documents valid for a maximum of six months 33 and may be updated, replaced, or obsoleted by other documents at any 34 time. It is inappropriate to use Internet-Drafts as reference 35 material or to cite them other than as "work in progress." 37 This Internet-Draft will expire on January 2, 2020. 39 Copyright Notice 41 Copyright (c) 2019 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal 45 Provisions Relating to IETF Documents 46 (https://trustee.ietf.org/license-info) in effect on the date of 47 publication of this document. Please review these documents 48 carefully, as they describe your rights and restrictions with respect 49 to this document. Code Components extracted from this document must 50 include Simplified BSD License text as described in Section 4.e of 51 the Trust Legal Provisions and are provided without warranty as 52 described in the Simplified BSD License. 54 Table of Contents 56 1. Introduction and History . . . . . . . . . . . . . . . . . . 2 57 2. Philosophical Relationship with ISOC . . . . . . . . . . . . 3 58 3. Main Division of Responsibilities between IETF and ISOC . . . 3 59 4. ISOC's Role in the IETF Standards Process . . . . . . . . . . 4 60 5. The IETF's Role in ISOC . . . . . . . . . . . . . . . . . . . 4 61 6. Legal Relationship with ISOC . . . . . . . . . . . . . . . . 5 62 7. Financial and Administrative Relationship with ISOC . . . . . 5 63 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 64 9. Security Considerations . . . . . . . . . . . . . . . . . . . 6 65 10. Privacy Considerations . . . . . . . . . . . . . . . . . . . 6 66 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 67 12. Changes from Previous Versions . . . . . . . . . . . . . . . 6 68 13. Informative References . . . . . . . . . . . . . . . . . . . 6 69 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 71 1. Introduction and History 73 The Internet Society provides a corporate home for the administrative 74 entity that supports the Internet Engineering Task Force (IETF), the 75 Internet Architecture Board (IAB), and the Internet Research Task 76 Force (IRTF), and supports the work of these groups through a variety 77 of programs. 79 The Internet Engineering Task Force (IETF) is the body that is 80 responsible for the development and maintenance of the Internet 81 Standards. The IETF is primarily a volunteer organization. Its 82 driving force is a group of dedicated high-quality engineers from all 83 over the world. In a structure of working groups, these engineers 84 exchange ideas and experience, and through discussion and 85 collaboration (both electronically and face-to-face) they strive to 86 achieve rough consensus and implement the standards through running 87 code. 89 The growth of the Internet over several decades also led to the 90 growth of the IETF. More and more people, organizations, and 91 companies rely on Internet Standards. Non-technical issues, such as 92 legal, administrative, and financial issues had long been an 93 undesirable but unavoidable part of the IETF. To address these 94 issues in 1995 the IETF established the Poised95 Working Group. Its 95 goal was to structure and document the IETF processes in order to 96 maximize the flexibility and freedom of IETF engineers so that they 97 could work in the way the IETF had always been most successful and to 98 honour the IETF credo: "Rough consensus and running code". 100 The Poised95 Working Group concluded that the Internet Society 101 (ISOC), which was formed in 1992, was the best organization to handle 102 all of these legal, administrative, and financial tasks on behalf of 103 and in close cooperation with the IETF. This led to documenting 104 things such as the IETF standards process [RFC2026], the IETF 105 organizational structure [RFC2028], the IETF Nominating Committee 106 (NomCom) procedures [RFC2282], and the IETF-ISOC relationship 107 [RFC2031]. 109 As time passed and operational experience accumulated, additional 110 structure was necessary. As a result, the Internet Administrative 111 Support Activity (IASA) was defined in 2005 and documented in 112 [RFC4071] and [RFC4371]. 114 In 2018, the IASA was revised under a new "IASA 2.0" structure by the 115 IASA2 Working Group, which made significant revisions to the IETF's 116 administrative, legal, and financial structure. One critical outcome 117 was the formation, in close cooperation between the IETF and ISOC, of 118 the IETF Administration Limited Liability Company (IETF LLC) as a 119 subsidiary of ISOC. 121 As a result of the the IASA 2.0 structure [I-D.ietf-iasa2-rfc4071bis] 122 and formation of the IETF LLC, the relationship between the IETF and 123 ISOC has changed. This document summarises the current state of the 124 IETF - ISOC relationship at a high level and replaces [RFC2031]. 126 2. Philosophical Relationship with ISOC 128 ISOC and the IETF have historically been philosophically aligned. 129 ISOC's connection with the IETF community has always played an 130 important role in its policy work. ISOC has always been an advocate 131 for multistakeholder processes, which include the technical 132 community. Open standards are an explicit part of one of the focus 133 areas in ISOC's mission: Advancing the development and application of 134 Internet infrastructure, technologies, and open standards. 136 3. Main Division of Responsibilities between IETF and ISOC 138 The IETF remains responsible for the development and quality of the 139 Internet Standards. Apart from the roles described below, the IETF 140 and ISOC acknowledge that ISOC has no influence whatsoever on the 141 technical content of Internet Standards. 143 4. ISOC's Role in the IETF Standards Process 145 ISOC plays a small role in the IETF standards process. In 146 particular, ISOC assists the standards process by appointing the IETF 147 NomCom chair and by confirming IAB candidates who are put forward by 148 the IETF NomCom, as described in [RFC7437], and by acting as the last 149 resort in the appeals process, as described in [RFC2026]. 151 ISOC maintains liaison relationships and memberships in other 152 Standards Development Organizations (SDOs) and related organizations, 153 which directly benefits the IETF. For example, ISOC is a Sector 154 Member of the ITU-T. As a result, ISOC delegates are afforded the 155 same rights as other ITU-T Sector Members [RFC6756]. 157 ISOC also supports the IETF standards process more indirectly (e.g., 158 by promoting it in relevant communities) through several programmes. 159 For example, ISOC's Policymakers Programme to the IETF (usually 160 referred to simply as ISOC's policy fellows programme) gives policy 161 experts an opportunity to interact directly with the IETF technical 162 community. ISOC also performs technical work using the standards 163 developed in the IETF as its basis. An example of that is ISOC's 164 Deploy360 program, which helps encourage and support the deployment 165 of IETF standards like DNSSEC [RFC4033] and IPv6 [RFC8200]. 167 Otherwise, the involvement of ISOC's employees in the IETF standards 168 process (e.g., as document editors or in leadership positions) is as 169 individual contributors rather than on institutional grounds. 171 5. The IETF's Role in ISOC 173 The IETF plays a role in the governance of ISOC. Per ISOC's by-laws, 174 the IETF appoints a set of trustees to the ISOC Board. The process 175 by which the IETF makes those appointments is defined in [RFC3677]. 177 The charter of the IAB (Internet Architecture Board) [RFC2850] states 178 that "the IAB acts as a source of advice and guidance to the Board of 179 Trustees and Officers of the Internet Society concerning technical, 180 architectural, procedural, and (where appropriate) policy matters 181 pertaining to the Internet and its enabling technologies". This 182 connection between the IAB and ISOC ensures that ISOC's proposals in 183 the policy area are based on a sound understanding of the relevant 184 technologies and architectures. ISOC's strong connection to the 185 Internet technical community has always been one of its main 186 strengths. 188 6. Legal Relationship with ISOC 190 The IETF LLC is a disregarded Limited Liability Company (LLC) of The 191 Internet Society - established to provide a corporate legal framework 192 for facilitating current and future activities related to the IETF, 193 IAB, and IRTF. It was established by the ISOC/IETF LLC Agreement 194 [OpAgreement] on August 27, 2018, and governs the relationship 195 between the IETF LLC and ISOC. 197 The IETF Trust, documented in [RFC5378], and updated in 198 [I-D.ietf-iasa2-trust-rationale] and [I-D.ietf-iasa2-trust-update], 199 provides legal protection for the RFC series of documents and other 200 aspects of the IETF. This includes things such as protection for 201 trademarks, copyrights, and intellectual property rights. As part of 202 the IETF Trust arrangement, IETF standards documents can be freely 203 downloaded, copied, and distributed without financial or other 204 distribution restrictions, though all rights to change these 205 documents lie with the IETF. The IETF Trust also provides legal 206 protection in case of disputes over intellectual property rights and 207 other rights. The creation of the IETF LLC has changed the way that 208 the IETF Trust's trustees are selected but did not change the purpose 209 or operation of the Trust. One of the IETF Trust's trustees is 210 appointed by the ISOC's board of trustees. 212 7. Financial and Administrative Relationship with ISOC 214 Under the terms of the Operating Agreement [OpAgreement] between ISOC 215 and the IETF, ISOC has agreed to provide some funding support for the 216 IETF (ISOC has historically provided the IETF with significant 217 financial support). In particular, among other things, the IETF LLC 218 is responsible for creating and managing an annual operating budget 219 for the IETF; for negotiating, signing, and overseeing contracts; for 220 fund raising; for maintaining bank accounts; and for liability 221 insurance. The IETF LLC is managed by a board of directors, one of 222 whom is appointed by the ISOC's board of trustees. The intention is 223 that ISOC and the IETF LLC operate at arms length. 225 The IETF LCC establishes contracts with third parties to provide 226 different types of services to the IETF. Note that it is possible 227 that some of those services are provided by ISOC or involve ISOC 228 staff. 230 Under the new IASA 2.0 structure, the IETF is solely responsible for 231 its administration, including the IETF Trust, IAB, IESG, IETF working 232 groups, and other IETF processes. A further exploration of this can 233 be found in Section 4 of [I-D.ietf-iasa2-rfc4071bis]. 235 8. IANA Considerations 237 This document introduces no new IANA considerations. 239 9. Security Considerations 241 This document introduces no new security considerations. 243 10. Privacy Considerations 245 This document introduces no new privacy considerations. 247 11. Acknowledgements 249 The authors would like to thank Erik Huizer for his contribution as 250 the author of [RFC2031], which this document replaces. 252 12. Changes from Previous Versions 254 RFC Editor: Please remove this section upon publication. 256 -00: Initial version published 258 -01: Several key updates to prepare WGLC based on WG feedback 260 -02: Fixed nits identified by Brian Carpenter on 12-21-2018, and text 261 on the tax status from John Levine. 263 -03: As we entered IESG review, added a short description of what 264 ISOC does (in relation to the IETF) that can be used in external 265 material by both the IETF and ISOC. 267 -04: Clarification adding text to Section 6 on legal issue. 269 -05: Fix nits 271 13. Informative References 273 [I-D.ietf-iasa2-rfc4071bis] 274 Haberman, B., Hall, J., and J. Livingood, "Structure of 275 the IETF Administrative Support Activity, Version 2.0", 276 draft-ietf-iasa2-rfc4071bis-11 (work in progress), April 277 2019. 279 [I-D.ietf-iasa2-trust-rationale] 280 Arkko, J., "Discussion of the IASA 2.0 Changes as They 281 Relate to the IETF Trust", draft-ietf-iasa2-trust- 282 rationale-03 (work in progress), October 2018. 284 [I-D.ietf-iasa2-trust-update] 285 Arkko, J. and T. Hardie, "Update to the Process for 286 Selection of Trustees for the IETF Trust", draft-ietf- 287 iasa2-trust-update-03 (work in progress), February 2019. 289 [OpAgreement] 290 "Limited Liability Company Agreement of IETF 291 Administration LLC", August 2018. 293 [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 294 3", BCP 9, RFC 2026, DOI 10.17487/RFC2026, October 1996, 295 . 297 [RFC2028] Hovey, R. and S. Bradner, "The Organizations Involved in 298 the IETF Standards Process", BCP 11, RFC 2028, 299 DOI 10.17487/RFC2028, October 1996, 300 . 302 [RFC2031] Huizer, E., "IETF-ISOC relationship", RFC 2031, 303 DOI 10.17487/RFC2031, October 1996, 304 . 306 [RFC2282] Galvin, J., "IAB and IESG Selection, Confirmation, and 307 Recall Process: Operation of the Nominating and Recall 308 Committees", RFC 2282, DOI 10.17487/RFC2282, February 309 1998, . 311 [RFC2850] Internet Architecture Board and B. Carpenter, Ed., 312 "Charter of the Internet Architecture Board (IAB)", 313 BCP 39, RFC 2850, DOI 10.17487/RFC2850, May 2000, 314 . 316 [RFC3677] Daigle, L., Ed. and Internet Architecture Board, "IETF 317 ISOC Board of Trustee Appointment Procedures", BCP 77, 318 RFC 3677, DOI 10.17487/RFC3677, December 2003, 319 . 321 [RFC4033] Arends, R., Austein, R., Larson, M., Massey, D., and S. 322 Rose, "DNS Security Introduction and Requirements", 323 RFC 4033, DOI 10.17487/RFC4033, March 2005, 324 . 326 [RFC4071] Austein, R., Ed. and B. Wijnen, Ed., "Structure of the 327 IETF Administrative Support Activity (IASA)", BCP 101, 328 RFC 4071, DOI 10.17487/RFC4071, April 2005, 329 . 331 [RFC4371] Carpenter, B., Ed. and L. Lynch, Ed., "BCP 101 Update for 332 IPR Trust", BCP 101, RFC 4371, DOI 10.17487/RFC4371, 333 January 2006, . 335 [RFC5378] Bradner, S., Ed. and J. Contreras, Ed., "Rights 336 Contributors Provide to the IETF Trust", BCP 78, RFC 5378, 337 DOI 10.17487/RFC5378, November 2008, 338 . 340 [RFC6756] Trowbridge, S., Ed., Lear, E., Ed., Fishman, G., Ed., and 341 S. Bradner, Ed., "Internet Engineering Task Force and 342 International Telecommunication Union - Telecommunication 343 Standardization Sector Collaboration Guidelines", 344 RFC 6756, DOI 10.17487/RFC6756, September 2012, 345 . 347 [RFC7437] Kucherawy, M., Ed., "IAB, IESG, and IAOC Selection, 348 Confirmation, and Recall Process: Operation of the 349 Nominating and Recall Committees", BCP 10, RFC 7437, 350 DOI 10.17487/RFC7437, January 2015, 351 . 353 [RFC8200] Deering, S. and R. Hinden, "Internet Protocol, Version 6 354 (IPv6) Specification", STD 86, RFC 8200, 355 DOI 10.17487/RFC8200, July 2017, 356 . 358 Authors' Addresses 360 Gonzalo Camarillo 361 Ericsson 363 Email: Gonzalo.Camarillo@ericsson.com 365 Jason Livingood 366 Comcast 368 Email: jason_livingood@comcast.com