idnits 2.17.1 draft-ietf-iasa2-rfc2031bis-06.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 (August 21, 2019) is 1700 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: 'BCP10' is defined on line 289, but no explicit reference was found in the text == Unused Reference: 'ISOC-Mission' is defined on line 301, but no explicit reference was found in the text -- 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 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 (~~), 3 warnings (==), 7 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: February 22, 2020 August 21, 2019 8 The IETF-ISOC Relationship 9 draft-ietf-iasa2-rfc2031bis-06 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 February 22, 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. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 69 13.1. Normative References . . . . . . . . . . . . . . . . . . 6 70 13.2. Informative References . . . . . . . . . . . . . . . . . 7 71 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 73 1. Introduction and History 75 The Internet Society provides a corporate home for the administrative 76 entity that supports the Internet Engineering Task Force (IETF), the 77 Internet Architecture Board (IAB), and the Internet Research Task 78 Force (IRTF), and supports the work of these groups through a variety 79 of programs. 81 The Internet Engineering Task Force (IETF) is the body that is 82 responsible for the development and maintenance of the Internet 83 Standards. The IETF is primarily a volunteer organization. Its 84 driving force is a group of dedicated high-quality engineers from all 85 over the world. In a structure of working groups, these engineers 86 exchange ideas and experience, and through discussion and 87 collaboration (both electronically and face-to-face) they strive to 88 achieve rough consensus and implement the standards through running 89 code. 91 The growth of the Internet over several decades also led to the 92 growth of the IETF. More and more people, organizations, and 93 companies rely on Internet Standards. Non-technical issues, such as 94 legal, administrative, and financial issues had long been an 95 undesirable but unavoidable part of the IETF. To address these 96 issues in 1995 the IETF established the Poised95 Working Group. Its 97 goal was to structure and document the IETF processes in order to 98 maximize the flexibility and freedom of IETF engineers so that they 99 could work in the way the IETF had always been most successful and to 100 honour the IETF credo: "Rough consensus and running code". 102 The Poised95 Working Group concluded that the Internet Society 103 (ISOC), which was formed in 1992, was the best organization to handle 104 all of these legal, administrative, and financial tasks on behalf of 105 and in close cooperation with the IETF. This led to documenting 106 things such as the IETF standards process [RFC2026], the IETF 107 organizational structure [RFC2028], the IETF Nominating Committee 108 (NomCom) procedures , and the IETF-ISOC relationship 109 [RFC2031]. 111 As time passed and operational experience accumulated, additional 112 structure was necessary. As a result, the Internet Administrative 113 Support Activity (IASA) was defined in 2005 and documented in 114 [RFC4071] and [RFC4371]. 116 In 2018, the IASA was revised under a new "IASA 2.0" structure by the 117 IASA2 Working Group, which made significant revisions to the IETF's 118 administrative, legal, and financial structure. One critical outcome 119 was the formation, in close cooperation between the IETF and ISOC, of 120 the IETF Administration Limited Liability Company (IETF LLC) as a 121 subsidiary of ISOC. 123 As a result of the IASA 2.0 structure [I-D.ietf-iasa2-rfc4071bis] and 124 formation of the IETF LLC, the relationship between the IETF and ISOC 125 has changed. This document summarises the current state of the IETF- 126 ISOC relationship at a high level and replaces [RFC2031]. 128 2. Philosophical Relationship with ISOC 130 ISOC and the IETF have historically been philosophically aligned. 131 ISOC's connection with the IETF community has always played an 132 important role in its policy work. ISOC has always been an advocate 133 for multistakeholder processes, which include the technical 134 community. Open standards are an explicit part of one of the focus 135 areas in ISOC's mission: Advancing the development and application of 136 Internet infrastructure, technologies, and open standards . 139 3. Main Division of Responsibilities between IETF and ISOC 141 The IETF remains responsible for the development and quality of the 142 Internet Standards. Apart from the roles described below, the IETF 143 and ISOC acknowledge that ISOC as an organization has no direct 144 influence whatsoever on the technical content of Internet Standards 145 (though ISOC employees may independently continue to make technical 146 contributuins as individuals). 148 4. ISOC's Role in the IETF Standards Process 150 ISOC plays a small role in the IETF standards process. In 151 particular, ISOC assists the standards process by appointing the IETF 152 NomCom chair and by confirming IAB candidates who are put forward by 153 the IETF NomCom, as described in [RFC7437], and by acting as the last 154 resort in the appeals process, as described in [RFC2026]. 156 ISOC maintains liaison relationships and memberships in other 157 Standards Development Organizations (SDOs) and related organizations, 158 which directly benefits the IETF. For example, ISOC is a Sector 159 Member of the ITU-T. As a result, ISOC delegates are afforded the 160 same rights as other ITU-T Sector Members [RFC6756]. 162 ISOC also supports the IETF standards process more indirectly (e.g., 163 by promoting it in relevant communities) through several programmes. 164 For example, ISOC's Policymakers Programme to the IETF (usually 165 referred to simply as ISOC's policy fellows programme) gives policy 166 experts an opportunity to interact directly with the IETF technical 167 community. ISOC also performs technical work using the standards 168 developed in the IETF as its basis. An example of that is ISOC's 169 Deploy360 program, which helps encourage and support the deployment 170 of IETF standards like DNSSEC [RFC4033] and IPv6 [RFC8200]. 172 Otherwise, the involvement of ISOC's employees in the IETF standards 173 process (e.g., as document editors or in leadership positions) is as 174 individual contributors rather than on institutional grounds. 176 5. The IETF's Role in ISOC 178 The IETF plays a role in the governance of ISOC. Per ISOC's by-laws, 179 the IETF appoints a set of trustees to the ISOC Board. The process 180 by which the IETF makes those appointments is defined in [RFC3677]. 182 The charter of the IAB (Internet Architecture Board) [RFC2850] states 183 that "the IAB acts as a source of advice and guidance to the Board of 184 Trustees and Officers of the Internet Society concerning technical, 185 architectural, procedural, and (where appropriate) policy matters 186 pertaining to the Internet and its enabling technologies". This 187 connection between the IAB and ISOC ensures that ISOC's proposals in 188 the policy area are based on a sound understanding of the relevant 189 technologies and architectures. ISOC's strong connection to the 190 Internet technical community has always been one of its main 191 strengths. 193 6. Legal Relationship with ISOC 195 The IETF LLC is a disregarded Limited Liability Company (LLC) of the 196 Internet Society - established to provide a corporate legal framework 197 for facilitating current and future activities related to the IETF, 198 IAB, and IRTF. It was established by the ISOC/IETF LLC Agreement 199 [OpAgreement] on August 27, 2018, and governs the relationship 200 between the IETF LLC and ISOC. 202 The IETF Trust, documented in [RFC5378], and updated in 203 [I-D.ietf-iasa2-trust-rationale] and [I-D.ietf-iasa2-trust-update], 204 provides legal protection for the RFC series of documents and other 205 aspects of the IETF. This includes things such as protection for 206 trademarks, copyrights, and intellectual property rights. As part of 207 the IETF Trust arrangement, IETF standards documents can be freely 208 downloaded, copied, and distributed without financial or other 209 distribution restrictions, though all rights to change these 210 documents lie with the IETF. The IETF Trust also provides legal 211 protection in case of disputes over intellectual property rights and 212 other rights. The creation of the IETF LLC has changed the way that 213 the IETF Trust's trustees are selected but did not change the purpose 214 or operation of the Trust. One of the IETF Trust's trustees is 215 appointed by the ISOC's Board of Trustees. 217 7. Financial and Administrative Relationship with ISOC 219 Under the terms of the Operating Agreement [OpAgreement] between ISOC 220 and the IETF, ISOC has agreed to provide significant funding support 221 for the IETF. In particular, among other things, the IETF LLC is 222 responsible for creating and managing an annual operating budget for 223 the IETF; for negotiating, signing, and overseeing contracts; for 224 fundraising; for maintaining bank accounts; and for liability 225 insurance. The IETF LLC is managed by a Board of Directors, one of 226 whom is appointed by the ISOC's Board of Trustees. The intention is 227 that ISOC and the IETF LLC operate at arm's length. 229 The IETF LLC establishes contracts with third parties to provide 230 different types of services to the IETF. Note that it is possible 231 that some of those services are provided by ISOC or involve ISOC 232 staff. 234 Under the new IASA 2.0 structure, the IETF LLC is solely responsible 235 for its administration, including the IETF Trust, IAB, IESG, IETF 236 working groups, and other IETF processes. A further exploration of 237 this can be found in Section 4 of [I-D.ietf-iasa2-rfc4071bis]. 239 8. IANA Considerations 241 This document introduces no new IANA considerations. 243 9. Security Considerations 245 This document introduces no new security considerations. 247 10. Privacy Considerations 249 This document introduces no new privacy considerations. 251 11. Acknowledgements 253 The authors would like to thank Erik Huizer for his contribution as 254 the author of [RFC2031], which this document replaces. 256 12. Changes from Previous Versions 258 RFC Editor: Please remove this section upon publication. 260 -00: Initial version published 262 -01: Several key updates to prepare WGLC based on WG feedback 264 -02: Fixed nits identified by Brian Carpenter on 12-21-2018, and text 265 on the tax status from John Levine. 267 -03: As we entered IESG review, added a short description of what 268 ISOC does (in relation to the IETF) that can be used in external 269 material by both the IETF and ISOC. 271 -04: Clarification adding text to Section 6 on legal issue. 273 -05: Fix nits 275 -06: Fix nits and other changes from IESG review 277 13. References 279 13.1. Normative References 281 [I-D.ietf-iasa2-rfc4071bis] 282 Haberman, B., Hall, J., and J. Livingood, "Structure of 283 the IETF Administrative Support Activity, Version 2.0", 284 draft-ietf-iasa2-rfc4071bis-11 (work in progress), April 285 2019. 287 13.2. Informative References 289 [BCP10] "BCP10", . 291 [I-D.ietf-iasa2-trust-rationale] 292 Arkko, J., "Discussion of the IASA 2.0 Changes as They 293 Relate to the IETF Trust", draft-ietf-iasa2-trust- 294 rationale-03 (work in progress), October 2018. 296 [I-D.ietf-iasa2-trust-update] 297 Arkko, J. and T. Hardie, "Update to the Process for 298 Selection of Trustees for the IETF Trust", draft-ietf- 299 iasa2-trust-update-03 (work in progress), February 2019. 301 [ISOC-Mission] 302 "ISOC Mission", 303 . 305 [OpAgreement] 306 "Limited Liability Company Agreement of IETF 307 Administration LLC", August 2018, 308 . 311 [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 312 3", BCP 9, RFC 2026, DOI 10.17487/RFC2026, October 1996, 313 . 315 [RFC2028] Hovey, R. and S. Bradner, "The Organizations Involved in 316 the IETF Standards Process", BCP 11, RFC 2028, 317 DOI 10.17487/RFC2028, October 1996, 318 . 320 [RFC2031] Huizer, E., "IETF-ISOC relationship", RFC 2031, 321 DOI 10.17487/RFC2031, October 1996, 322 . 324 [RFC2850] Internet Architecture Board and B. Carpenter, Ed., 325 "Charter of the Internet Architecture Board (IAB)", 326 BCP 39, RFC 2850, DOI 10.17487/RFC2850, May 2000, 327 . 329 [RFC3677] Daigle, L., Ed. and Internet Architecture Board, "IETF 330 ISOC Board of Trustee Appointment Procedures", BCP 77, 331 RFC 3677, DOI 10.17487/RFC3677, December 2003, 332 . 334 [RFC4033] Arends, R., Austein, R., Larson, M., Massey, D., and S. 335 Rose, "DNS Security Introduction and Requirements", 336 RFC 4033, DOI 10.17487/RFC4033, March 2005, 337 . 339 [RFC4071] Austein, R., Ed. and B. Wijnen, Ed., "Structure of the 340 IETF Administrative Support Activity (IASA)", BCP 101, 341 RFC 4071, DOI 10.17487/RFC4071, April 2005, 342 . 344 [RFC4371] Carpenter, B., Ed. and L. Lynch, Ed., "BCP 101 Update for 345 IPR Trust", BCP 101, RFC 4371, DOI 10.17487/RFC4371, 346 January 2006, . 348 [RFC5378] Bradner, S., Ed. and J. Contreras, Ed., "Rights 349 Contributors Provide to the IETF Trust", BCP 78, RFC 5378, 350 DOI 10.17487/RFC5378, November 2008, 351 . 353 [RFC6756] Trowbridge, S., Ed., Lear, E., Ed., Fishman, G., Ed., and 354 S. Bradner, Ed., "Internet Engineering Task Force and 355 International Telecommunication Union - Telecommunication 356 Standardization Sector Collaboration Guidelines", 357 RFC 6756, DOI 10.17487/RFC6756, September 2012, 358 . 360 [RFC7437] Kucherawy, M., Ed., "IAB, IESG, and IAOC Selection, 361 Confirmation, and Recall Process: Operation of the 362 Nominating and Recall Committees", BCP 10, RFC 7437, 363 DOI 10.17487/RFC7437, January 2015, 364 . 366 [RFC8200] Deering, S. and R. Hinden, "Internet Protocol, Version 6 367 (IPv6) Specification", STD 86, RFC 8200, 368 DOI 10.17487/RFC8200, July 2017, 369 . 371 Authors' Addresses 373 Gonzalo Camarillo 374 Ericsson 376 Email: Gonzalo.Camarillo@ericsson.com 377 Jason Livingood 378 Comcast 380 Email: jason_livingood@comcast.com