idnits 2.17.1 draft-ietf-iasa2-rfc2031bis-02.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 (January 2, 2019) is 1940 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Outdated reference: A later version (-11) exists of draft-ietf-iasa2-rfc4071bis-03 == Outdated reference: A later version (-03) exists of draft-ietf-iasa2-trust-update-02 -- 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 (~~), 3 warnings (==), 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: July 6, 2019 January 2, 2019 8 The IETF-ISOC Relationship 9 draft-ietf-iasa2-rfc2031bis-02 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 July 6, 2019. 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 . . . . . . . . . . 3 60 5. The IETF's Role in ISOC . . . . . . . . . . . . . . . . . . . 4 61 6. Legal Relationship with ISOC . . . . . . . . . . . . . . . . 4 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 Engineering Task Force (IETF) is the body that is 74 responsible for the development and maintenance of the Internet 75 Standards. The IETF is primarily a volunteer organization. Its 76 driving force is a group of dedicated high-quality engineers from all 77 over the world. In a structure of working groups, these engineers 78 exchange ideas and experience, and through discussion and 79 collaboration (both electronically and face-to-face) they strive to 80 achieve rough consensus and implement the standards through running 81 code. 83 The growth of the Internet over several decades also led to the 84 growth of the IETF. More and more people, organizations, and 85 companies rely on Internet Standards. Non-technical issues, such as 86 legal, administrative, and financial issues had long been an 87 undesirable but unavoidable part of the IETF. To address these 88 issues in 1995 the IETF established the Poised95 Working Group. Its 89 goal was to structure and document the IETF processes in order to 90 maximize the flexibility and freedom of IETF engineers so that they 91 could work in the way the IETF had always been most successful and to 92 honour the IETF credo: "Rough consensus and running code". 94 The Poised95 Working Group concluded that the Internet Society 95 (ISOC), which was formed in 1992, was the best organization to handle 96 all of these legal, administrative, and financial tasks on behalf of 97 and in close cooperation with the IETF. This led to documenting 98 things such as the IETF standards process [RFC2026], the IETF 99 organizational structure [RFC2028], the IETF Nominating Committee 100 (NomCom) procedures [RFC2282], and the IETF-ISOC relationship 101 [RFC2031]. 103 As time passed and operational experience accumulated, additional 104 structure was necessary. As a result, the Internet Administrative 105 Support Activity (IASA) was defined in 2005 and documented in 106 [RFC4071] and [RFC4371]. 108 In 2018, the IASA was revised under a new "IASA 2.0" structure by the 109 IASA2 Working Group, which made significant revisions to the IETF's 110 administrative, legal, and financial structure. One critical outcome 111 was the formation, in close cooperation between the IETF and ISOC, of 112 the IETF Administration Limited Liability Company (IETF LLC) as a 113 subsidiary of ISOC. 115 As a result of the the IASA 2.0 structure [I-D.ietf-iasa2-rfc4071bis] 116 and formation of the IETF LLC, the relationship between the IETF and 117 ISOC has changed. This document summarises the current state of the 118 IETF - ISOC relationship at a high level and replaces [RFC2031]. 120 2. Philosophical Relationship with ISOC 122 ISOC and the IETF have historically been philosophically aligned. 123 ISOC's connection with the IETF community has always played an 124 important role in its policy work. ISOC has always been an advocate 125 for multistakeholder processes, which include the technical 126 community. Open standards are an explicit part of one of the focus 127 areas in ISOC's mission: Advancing the development and application of 128 Internet infrastructure, technologies, and open standards. 130 3. Main Division of Responsibilities between IETF and ISOC 132 The IETF remains responsible for the development and quality of the 133 Internet Standards. The Internet Society will aid the IETF by 134 facilitating legal and organizational issues as described below. 135 Apart from the roles described below, the IETF and ISOC acknowledge 136 that ISOC has no influence whatsoever on the technical content of 137 Internet Standards. 139 4. ISOC's Role in the IETF Standards Process 141 ISOC plays a small role in the IETF standards process. In 142 particular, ISOC assists the standards process by appointing the IETF 143 NomCom chair and by confirming IAB candidates who are put forward by 144 the IETF NomCom, as described in [RFC7437], and by acting as the last 145 resort in the appeals process, as described in [RFC2026]. 147 ISOC maintains liaison relationships and memberships in other 148 Standards Development Organizations (SDOs) and related organizations, 149 which directly benefits the IETF. For example, ISOC is a Sector 150 Member of the ITU-T. As a result, ISOC delegates are afforded the 151 same rights as other ITU-T Sector Members [RFC6756]. 153 ISOC also supports the IETF standards process more indirectly (e.g., 154 by promoting it in relevant communities) through several programmes. 155 For example, ISOC's Policymakers Programme to the IETF (usually 156 referred to simply as ISOC's policy fellows programme) gives policy 157 experts an opportunity to interact directly with the IETF technical 158 community. ISOC also performs technical work using the standards 159 developed in the IETF as its basis. An example of that is ISOC's 160 Deploy360 program, which helps encourage and support the deployment 161 of critical new IETF standards like DNSSEC [RFC4033] and IPv6 162 [RFC8200]. 164 Otherwise, the involvement of ISOC's employees in the IETF standards 165 process (e.g., as document editors or in leadership positions) is as 166 individual contributors rather than on institutional grounds. 168 5. The IETF's Role in ISOC 170 The IETF plays a role in the governance of ISOC. Per ISOC's by-laws, 171 the IETF appoints a set of trustees to the ISOC Board. The process 172 by which the IETF makes those appointments is defined in [RFC3677]. 174 The charter of the IAB (Internet Architecture Board) [RFC2850] states 175 that "the IAB acts as a source of advice and guidance to the Board of 176 Trustees and Officers of the Internet Society concerning technical, 177 architectural, procedural, and (where appropriate) policy matters 178 pertaining to the Internet and its enabling technologies". This 179 connection between the IAB and ISOC ensures that ISOC's proposals in 180 the policy area are based on a sound understanding of the relevant 181 technologies and architectures. ISOC's strong connection to the 182 Internet technical community has always been one of its main 183 strengths. 185 6. Legal Relationship with ISOC 187 The IETF LLC was created as a subsidiary of ISOC. Specifically, the 188 IETF LLC is a single-member Limited Liability Company created in 189 Delaware (USA) in August 2018. The member (i.e., its legal owner) is 190 ISOC. The IETF LLC is managed separately, makes a budget, can sign 191 contracts, can pay and receive money, can sue and be sued, and has a 192 board. ISOC operates as a U.S. 501(c)(3) not-for-profit 193 organization, and was founded to support and promote the development 194 of the Internet as a global technical infrastructure, a resource to 195 enrich people's lives, and a force for good in society. The Limited 196 Liability Company Agreement of IETF Administration LLC, dated August 197 27 2018, is the Operating Agreement [OpAgreement] that governs the 198 relationship between the IETF LLC and ISOC (while this document is 199 intended as a summary of the agreement, please note that only the 200 agreement is authoritative). 202 The IETF LLC provides the IETF with a separate legal existence. The 203 IETF LLC structure now covers the IETF standards and IETF standards 204 process, all IETF officers (IAB, IESG, Nomcom, and WG chairs), IETF 205 employees and contractors, the RFC series and RFC editor, and all of 206 the IETF's other business operations. 208 For tax purposes, the IETF LLC is considered a part of ISOC, known as 209 a "disregarded entity". This means that the IETF LLC shares ISOC's 210 tax exempt status as a not-for-profit charity, and contributions to 211 the LLC are tax deductible under U.S. law as they would be if they 212 were made to ISOC. 214 The IETF Trust, documented in [RFC5378], and updated in 215 [I-D.ietf-iasa2-trust-rationale] and [I-D.ietf-iasa2-trust-update], 216 provides legal protection for the RFC series of documents and other 217 aspects of the IETF. This includes things such as protection for 218 trademarks, copyrights, and intellectual property rights. As part of 219 the IETF Trust arrangement, IETF standards documents can be freely 220 downloaded, copied, and distributed without financial or other 221 distribution restrictions, though all rights to change these 222 documents lie with the IETF. The IETF Trust also provides legal 223 protection in case of disputes over intellectual property rights and 224 other rights. The creation of the IETF LLC has changed the way that 225 the IETF Trust's trustees are selected but did not change the purpose 226 or operation of the Trust. One of the IETF Trust's trustees is 227 appointed by the ISOC's board of trustees. 229 7. Financial and Administrative Relationship with ISOC 231 Under the terms of the Operating Agreement [OpAgreement] between ISOC 232 and the IETF, ISOC has agreed to provide some funding support for the 233 IETF (ISOC has historically provided the IETF with significant 234 financial support). In particular, among other things, the IETF LLC 235 will be responsible for creating and managing an annual operating 236 budget for the IETF; for negotiating, signing, and overseeing 237 contracts; for fund raising; for maintaining a bank account; and for 238 liability insurance. The IETF LLC is managed by a board of 239 directors, one of whom is appointed by the ISOC's board of trustees. 240 The intention is that ISOC and the IETF LLC operate at arms length. 242 The IETF LCC establishes contracts with third parties to provide 243 different types of services to the IETF. Note that it is possible 244 that some of those services are provided by ISOC or involve ISOC 245 staff. 247 Under the new IASA 2.0 structure, the IETF is solely responsible for 248 its administration via the IETF LLC, IETF Trust, IAB, IESG, IETF 249 working groups, and other IETF processes. A further exploration of 250 this can be found in Section 4 of [I-D.ietf-iasa2-rfc4071bis]. 252 8. IANA Considerations 254 This document introduces no new IANA considerations. 256 9. Security Considerations 258 This document introduces no new security considerations. 260 10. Privacy Considerations 262 This document introduces no new privacy considerations. 264 11. Acknowledgements 266 The authors would like to thank Erik Huizer for his contribution as 267 the author of [RFC2031], which this document replaces. 269 12. Changes from Previous Versions 271 RFC Editor: Please remove this section upon publication. 273 -00: Initial version published 275 -01: Several key updates to prepare WGLC based on WG feedback 277 -02: Fixed nits identified by Brian Carpenter on 12-21-2018, and text 278 on the tax status from John Levine. 280 13. Informative References 282 [I-D.ietf-iasa2-rfc4071bis] 283 Haberman, B., Hall, J., and J. Livingood, "Structure of 284 the IETF Administrative Support Activity, Version 2.0", 285 draft-ietf-iasa2-rfc4071bis-03 (work in progress), 286 December 2018. 288 [I-D.ietf-iasa2-trust-rationale] 289 Arkko, J., "Discussion of the IASA 2.0 Changes as They 290 Relate to the IETF Trust", draft-ietf-iasa2-trust- 291 rationale-03 (work in progress), October 2018. 293 [I-D.ietf-iasa2-trust-update] 294 Arkko, J. and T. Hardie, "Update to the Process for 295 Selection of Trustees for the IETF Trust", draft-ietf- 296 iasa2-trust-update-02 (work in progress), October 2018. 298 [OpAgreement] 299 "Limited Liability Company Agreement of IETF 300 Administration LLC", August 2018. 302 [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 303 3", BCP 9, RFC 2026, DOI 10.17487/RFC2026, October 1996, 304 . 306 [RFC2028] Hovey, R. and S. Bradner, "The Organizations Involved in 307 the IETF Standards Process", BCP 11, RFC 2028, 308 DOI 10.17487/RFC2028, October 1996, 309 . 311 [RFC2031] Huizer, E., "IETF-ISOC relationship", RFC 2031, 312 DOI 10.17487/RFC2031, October 1996, 313 . 315 [RFC2282] Galvin, J., "IAB and IESG Selection, Confirmation, and 316 Recall Process: Operation of the Nominating and Recall 317 Committees", RFC 2282, DOI 10.17487/RFC2282, February 318 1998, . 320 [RFC2850] Internet Architecture Board and B. Carpenter, Ed., 321 "Charter of the Internet Architecture Board (IAB)", 322 BCP 39, RFC 2850, DOI 10.17487/RFC2850, May 2000, 323 . 325 [RFC3677] Daigle, L., Ed. and Internet Architecture Board, "IETF 326 ISOC Board of Trustee Appointment Procedures", BCP 77, 327 RFC 3677, DOI 10.17487/RFC3677, December 2003, 328 . 330 [RFC4033] Arends, R., Austein, R., Larson, M., Massey, D., and S. 331 Rose, "DNS Security Introduction and Requirements", 332 RFC 4033, DOI 10.17487/RFC4033, March 2005, 333 . 335 [RFC4071] Austein, R., Ed. and B. Wijnen, Ed., "Structure of the 336 IETF Administrative Support Activity (IASA)", BCP 101, 337 RFC 4071, DOI 10.17487/RFC4071, April 2005, 338 . 340 [RFC4371] Carpenter, B., Ed. and L. Lynch, Ed., "BCP 101 Update for 341 IPR Trust", BCP 101, RFC 4371, DOI 10.17487/RFC4371, 342 January 2006, . 344 [RFC5378] Bradner, S., Ed. and J. Contreras, Ed., "Rights 345 Contributors Provide to the IETF Trust", BCP 78, RFC 5378, 346 DOI 10.17487/RFC5378, November 2008, 347 . 349 [RFC6756] Trowbridge, S., Ed., Lear, E., Ed., Fishman, G., Ed., and 350 S. Bradner, Ed., "Internet Engineering Task Force and 351 International Telecommunication Union - Telecommunication 352 Standardization Sector Collaboration Guidelines", 353 RFC 6756, DOI 10.17487/RFC6756, September 2012, 354 . 356 [RFC7437] Kucherawy, M., Ed., "IAB, IESG, and IAOC Selection, 357 Confirmation, and Recall Process: Operation of the 358 Nominating and Recall Committees", BCP 10, RFC 7437, 359 DOI 10.17487/RFC7437, January 2015, 360 . 362 [RFC8200] Deering, S. and R. Hinden, "Internet Protocol, Version 6 363 (IPv6) Specification", STD 86, RFC 8200, 364 DOI 10.17487/RFC8200, July 2017, 365 . 367 Authors' Addresses 369 Gonzalo Camarillo 370 Ericsson 372 Email: Gonzalo.Camarillo@ericsson.com 374 Jason Livingood 375 Comcast 377 Email: jason_livingood@comcast.com