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