idnits 2.17.1 draft-ietf-iasa2-rfc2031bis-00.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 (November 28, 2018) is 1969 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == 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 (~~), 2 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 1, 2019 November 28, 2018 8 The Updated IETF-ISOC Relationship 9 draft-ietf-iasa2-rfc2031bis-00 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 1, 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. Main Division of Responsibilities between IETF and ISOC . . . 3 58 3. Philosophical Relationship with 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 . . . . . 4 63 8. Security Considerations . . . . . . . . . . . . . . . . . . . 5 64 9. Privacy Considerations . . . . . . . . . . . . . . . . . . . 5 65 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5 66 11. Changes from Previous Versions . . . . . . . . . . . . . . . 5 67 12. Informative References . . . . . . . . . . . . . . . . . . . 5 68 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6 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 disregarded entity of ISOC. 114 As a result of the the IASA 2.0 structure [I-D.ietf-iasa2-struct] and 115 formation of the IETF LLC, the relationship between the IETF and ISOC 116 has changed. This document summarises the current state of the IETF 117 - ISOC relationship at a high level and replaces [RFC2031]. 119 2. Main Division of Responsibilities between IETF and ISOC 121 The IETF remains responsible for the development and quality of the 122 Internet Standards. The Internet Society will aid the IETF by 123 facilitating legal and organizational issues as described below. 124 Apart from the roles described below, the IETF and ISOC acknowledge 125 that ISOC has no influence whatsoever on the technical content of 126 Internet Standards. 128 3. 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. 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 describes in [RFC2026]. 146 5. The IETF's Role in ISOC 148 The IETF plays a role in the governance of ISOC. Per ISOC's by-laws, 149 the IETF appoints a set of trustees to the ISOC Board. The process 150 by which the IETF makes those appointments is defined in [RFC3677]. 152 6. Legal Relationship with ISOC 154 The IETF LLC was organized as a "disregarded entity" of ISOC. This 155 means it operates as a branch or division of ISOC for tax purposes. 156 ISOC operates as a U.S. 501(c)(3) not-for-profit organization, and 157 was founded to support and promote the development of the Internet as 158 a global technical infrastructure, a resource to enrich people's 159 lives, and a force for good in society. The Limited Liability 160 Company Agreement of IETF Administration LLC, dated August 27 2018, 161 is the Operating Agreement that governs the relationship between the 162 IETF LLC and ISOC. 164 As a result of the creation of the IETF LLC, the IETF now has its own 165 legal umbrella. This IETF LLC structure now covers the IETF 166 standards and IETF standards process, all IETF officers (IAB, IESG, 167 Nomcom, and WG chairs), IETF employees and contractors, the RFC 168 series and RFC editor, etc. 170 The IETF Trust, documented in [RFC5378], and updated in 171 [I-D.ietf-iasa2-trust-rationale] and [I-D.ietf-iasa2-trust-update], 172 provides legal protection for the RFC series of documents and other 173 aspects of the IETF. This includes things such as protection for 174 trademarks, copyrights, and intellectual property rights. As part of 175 the IETF Trust arrangement, IETF standards documents can be freely 176 downloaded, copied, and distributed without financial or other 177 distribution restrictions, though all rights to change these 178 documents lie with the IETF. The IETF Trust also provides legal 179 protection in case of disputes over intellectual property rights and 180 other rights. 182 7. Financial and Administrative Relationship with ISOC 184 Under the terms of the Operating Agreement between ISOC and the IETF, 185 ISOC has agreed to provide some funding support for the IETF (ISOC 186 has historically provided the IETF with significant financial 187 support). The IETF LLC will be responsible for creating and managing 188 an annual operating budget for the IETF, for fund raising, for 189 maintaining a bank account, and so on. The IETF LLC is managed by a 190 board of directors, one of whom is appointed by ISOC. The intention 191 is that ISOC and the IETF LLC operate at arms length. 193 Under the new IASA 2.0 structure, the IETF is solely responsible for 194 its administration via the IETF LLC, IETF Trust, IAB, IESG, IETF 195 working groups, and other IETF processes. A further exploration of 196 this can be found in Section 4 of [I-D.ietf-iasa2-struct]. 198 8. Security Considerations 200 This document introduces no new security considerations. 202 [RFC Editor: Please remove this section upon publication.] 204 9. Privacy Considerations 206 This document introduces no new privacy considerations. 208 [RFC Editor: Please remove this section upon publication.] 210 10. Acknowledgements 212 The authors would like to thank Erik Huizer for his contribution as 213 the author of [RFC2031], which this document replaces. 215 11. Changes from Previous Versions 217 RFC Editor: Please remove this section upon publication. 219 -00: Initial version published 221 12. Informative References 223 [I-D.ietf-iasa2-struct] 224 Haberman, B., Hall, J., and J. Livingood, "Record of 225 Proposed Structure of the IETF Administrative Support 226 Activity (IASA), Version 2.0", draft-ietf-iasa2-struct-06 227 (work in progress), September 2018. 229 [I-D.ietf-iasa2-trust-rationale] 230 Arkko, J., "Discussion of the IASA 2.0 Changes as They 231 Relate to the IETF Trust", draft-ietf-iasa2-trust- 232 rationale-03 (work in progress), October 2018. 234 [I-D.ietf-iasa2-trust-update] 235 Arkko, J. and T. Hardie, "Update to the Process for 236 Selection of Trustees for the IETF Trust", draft-ietf- 237 iasa2-trust-update-02 (work in progress), October 2018. 239 [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 240 3", BCP 9, RFC 2026, DOI 10.17487/RFC2026, October 1996, 241 . 243 [RFC2028] Hovey, R. and S. Bradner, "The Organizations Involved in 244 the IETF Standards Process", BCP 11, RFC 2028, 245 DOI 10.17487/RFC2028, October 1996, 246 . 248 [RFC2031] Huizer, E., "IETF-ISOC relationship", RFC 2031, 249 DOI 10.17487/RFC2031, October 1996, 250 . 252 [RFC2282] Galvin, J., "IAB and IESG Selection, Confirmation, and 253 Recall Process: Operation of the Nominating and Recall 254 Committees", RFC 2282, DOI 10.17487/RFC2282, February 255 1998, . 257 [RFC3677] Daigle, L., Ed. and Internet Architecture Board, "IETF 258 ISOC Board of Trustee Appointment Procedures", BCP 77, 259 RFC 3677, DOI 10.17487/RFC3677, December 2003, 260 . 262 [RFC4071] Austein, R., Ed. and B. Wijnen, Ed., "Structure of the 263 IETF Administrative Support Activity (IASA)", BCP 101, 264 RFC 4071, DOI 10.17487/RFC4071, April 2005, 265 . 267 [RFC4371] Carpenter, B., Ed. and L. Lynch, Ed., "BCP 101 Update for 268 IPR Trust", BCP 101, RFC 4371, DOI 10.17487/RFC4371, 269 January 2006, . 271 [RFC5378] Bradner, S., Ed. and J. Contreras, Ed., "Rights 272 Contributors Provide to the IETF Trust", BCP 78, RFC 5378, 273 DOI 10.17487/RFC5378, November 2008, 274 . 276 [RFC7437] Kucherawy, M., Ed., "IAB, IESG, and IAOC Selection, 277 Confirmation, and Recall Process: Operation of the 278 Nominating and Recall Committees", BCP 10, RFC 7437, 279 DOI 10.17487/RFC7437, January 2015, 280 . 282 Authors' Addresses 283 Gonzalo Camarillo 284 Ericsson 286 Email: Gonzalo.Camarillo@ericsson.com 288 Jason Livingood 289 Comcast 291 Email: jason_livingood@comcast.com