| < draft-ietf-iasa2-rfc2031bis-05.txt | draft-ietf-iasa2-rfc2031bis-06.txt > | |||
|---|---|---|---|---|
| IETF Administrative Support Activity 2 G. Camarillo | IETF Administrative Support Activity 2 G. Camarillo | |||
| Internet-Draft Ericsson | Internet-Draft Ericsson | |||
| Obsoletes: 2031 (if approved) J. Livingood | Obsoletes: 2031 (if approved) J. Livingood | |||
| Intended status: Informational Comcast | Intended status: Informational Comcast | |||
| Expires: January 2, 2020 July 1, 2019 | Expires: February 22, 2020 August 21, 2019 | |||
| The IETF-ISOC Relationship | The IETF-ISOC Relationship | |||
| draft-ietf-iasa2-rfc2031bis-05 | draft-ietf-iasa2-rfc2031bis-06 | |||
| Abstract | Abstract | |||
| This document summarises the Internet Engineering Task Force (IETF) - | This document summarises the Internet Engineering Task Force (IETF) - | |||
| Internet Society (ISOC) relationship, following a major revision to | Internet Society (ISOC) relationship, following a major revision to | |||
| the structure of the IETF Administrative Support Activity (IASA) in | the structure of the IETF Administrative Support Activity (IASA) in | |||
| 2018. The IASA was revised under a new "IASA 2.0" structure by the | 2018. The IASA was revised under a new "IASA 2.0" structure by the | |||
| IASA2 Working Group, which changed the IETF's administrative, legal, | IASA2 Working Group, which changed the IETF's administrative, legal, | |||
| and financial structure. As a result, it also changed the | and financial structure. As a result, it also changed the | |||
| relationship between the IETF and ISOC, which made it necessary to | relationship between the IETF and ISOC, which made it necessary to | |||
| skipping to change at page 1, line 38 ¶ | skipping to change at page 1, line 38 ¶ | |||
| Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
| Task Force (IETF). Note that other groups may also distribute | Task Force (IETF). Note that other groups may also distribute | |||
| working documents as Internet-Drafts. The list of current Internet- | working documents as Internet-Drafts. The list of current Internet- | |||
| Drafts is at https://datatracker.ietf.org/drafts/current/. | Drafts is at https://datatracker.ietf.org/drafts/current/. | |||
| Internet-Drafts are draft documents valid for a maximum of six months | Internet-Drafts are draft documents valid for a maximum of six months | |||
| and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
| time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
| material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
| This Internet-Draft will expire on January 2, 2020. | This Internet-Draft will expire on February 22, 2020. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2019 IETF Trust and the persons identified as the | Copyright (c) 2019 IETF Trust and the persons identified as the | |||
| document authors. All rights reserved. | document authors. All rights reserved. | |||
| This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
| Provisions Relating to IETF Documents | Provisions Relating to IETF Documents | |||
| (https://trustee.ietf.org/license-info) in effect on the date of | (https://trustee.ietf.org/license-info) in effect on the date of | |||
| publication of this document. Please review these documents | publication of this document. Please review these documents | |||
| skipping to change at page 2, line 23 ¶ | skipping to change at page 2, line 23 ¶ | |||
| 3. Main Division of Responsibilities between IETF and ISOC . . . 3 | 3. Main Division of Responsibilities between IETF and ISOC . . . 3 | |||
| 4. ISOC's Role in the IETF Standards Process . . . . . . . . . . 4 | 4. ISOC's Role in the IETF Standards Process . . . . . . . . . . 4 | |||
| 5. The IETF's Role in ISOC . . . . . . . . . . . . . . . . . . . 4 | 5. The IETF's Role in ISOC . . . . . . . . . . . . . . . . . . . 4 | |||
| 6. Legal Relationship with ISOC . . . . . . . . . . . . . . . . 5 | 6. Legal Relationship with ISOC . . . . . . . . . . . . . . . . 5 | |||
| 7. Financial and Administrative Relationship with ISOC . . . . . 5 | 7. Financial and Administrative Relationship with ISOC . . . . . 5 | |||
| 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 | 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 | |||
| 9. Security Considerations . . . . . . . . . . . . . . . . . . . 6 | 9. Security Considerations . . . . . . . . . . . . . . . . . . . 6 | |||
| 10. Privacy Considerations . . . . . . . . . . . . . . . . . . . 6 | 10. Privacy Considerations . . . . . . . . . . . . . . . . . . . 6 | |||
| 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 | 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 | |||
| 12. Changes from Previous Versions . . . . . . . . . . . . . . . 6 | 12. Changes from Previous Versions . . . . . . . . . . . . . . . 6 | |||
| 13. Informative References . . . . . . . . . . . . . . . . . . . 6 | 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 | |||
| 13.1. Normative References . . . . . . . . . . . . . . . . . . 6 | ||||
| 13.2. Informative References . . . . . . . . . . . . . . . . . 7 | ||||
| Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 | Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 | |||
| 1. Introduction and History | 1. Introduction and History | |||
| The Internet Society provides a corporate home for the administrative | The Internet Society provides a corporate home for the administrative | |||
| entity that supports the Internet Engineering Task Force (IETF), the | entity that supports the Internet Engineering Task Force (IETF), the | |||
| Internet Architecture Board (IAB), and the Internet Research Task | Internet Architecture Board (IAB), and the Internet Research Task | |||
| Force (IRTF), and supports the work of these groups through a variety | Force (IRTF), and supports the work of these groups through a variety | |||
| of programs. | of programs. | |||
| skipping to change at page 3, line 13 ¶ | skipping to change at page 3, line 15 ¶ | |||
| maximize the flexibility and freedom of IETF engineers so that they | maximize the flexibility and freedom of IETF engineers so that they | |||
| could work in the way the IETF had always been most successful and to | could work in the way the IETF had always been most successful and to | |||
| honour the IETF credo: "Rough consensus and running code". | honour the IETF credo: "Rough consensus and running code". | |||
| The Poised95 Working Group concluded that the Internet Society | The Poised95 Working Group concluded that the Internet Society | |||
| (ISOC), which was formed in 1992, was the best organization to handle | (ISOC), which was formed in 1992, was the best organization to handle | |||
| all of these legal, administrative, and financial tasks on behalf of | all of these legal, administrative, and financial tasks on behalf of | |||
| and in close cooperation with the IETF. This led to documenting | and in close cooperation with the IETF. This led to documenting | |||
| things such as the IETF standards process [RFC2026], the IETF | things such as the IETF standards process [RFC2026], the IETF | |||
| organizational structure [RFC2028], the IETF Nominating Committee | organizational structure [RFC2028], the IETF Nominating Committee | |||
| (NomCom) procedures [RFC2282], and the IETF-ISOC relationship | (NomCom) procedures <BCP10>, and the IETF-ISOC relationship | |||
| [RFC2031]. | [RFC2031]. | |||
| As time passed and operational experience accumulated, additional | As time passed and operational experience accumulated, additional | |||
| structure was necessary. As a result, the Internet Administrative | structure was necessary. As a result, the Internet Administrative | |||
| Support Activity (IASA) was defined in 2005 and documented in | Support Activity (IASA) was defined in 2005 and documented in | |||
| [RFC4071] and [RFC4371]. | [RFC4071] and [RFC4371]. | |||
| In 2018, the IASA was revised under a new "IASA 2.0" structure by the | In 2018, the IASA was revised under a new "IASA 2.0" structure by the | |||
| IASA2 Working Group, which made significant revisions to the IETF's | IASA2 Working Group, which made significant revisions to the IETF's | |||
| administrative, legal, and financial structure. One critical outcome | administrative, legal, and financial structure. One critical outcome | |||
| was the formation, in close cooperation between the IETF and ISOC, of | was the formation, in close cooperation between the IETF and ISOC, of | |||
| the IETF Administration Limited Liability Company (IETF LLC) as a | the IETF Administration Limited Liability Company (IETF LLC) as a | |||
| subsidiary of ISOC. | subsidiary of ISOC. | |||
| As a result of the the IASA 2.0 structure [I-D.ietf-iasa2-rfc4071bis] | As a result of the IASA 2.0 structure [I-D.ietf-iasa2-rfc4071bis] and | |||
| and formation of the IETF LLC, the relationship between the IETF and | formation of the IETF LLC, the relationship between the IETF and ISOC | |||
| ISOC has changed. This document summarises the current state of the | has changed. This document summarises the current state of the IETF- | |||
| IETF - ISOC relationship at a high level and replaces [RFC2031]. | ISOC relationship at a high level and replaces [RFC2031]. | |||
| 2. Philosophical Relationship with ISOC | 2. Philosophical Relationship with ISOC | |||
| ISOC and the IETF have historically been philosophically aligned. | ISOC and the IETF have historically been philosophically aligned. | |||
| ISOC's connection with the IETF community has always played an | ISOC's connection with the IETF community has always played an | |||
| important role in its policy work. ISOC has always been an advocate | important role in its policy work. ISOC has always been an advocate | |||
| for multistakeholder processes, which include the technical | for multistakeholder processes, which include the technical | |||
| community. Open standards are an explicit part of one of the focus | community. Open standards are an explicit part of one of the focus | |||
| areas in ISOC's mission: Advancing the development and application of | areas in ISOC's mission: Advancing the development and application of | |||
| Internet infrastructure, technologies, and open standards. | Internet infrastructure, technologies, and open standards <ISOC- | |||
| Mission>. | ||||
| 3. Main Division of Responsibilities between IETF and ISOC | 3. Main Division of Responsibilities between IETF and ISOC | |||
| The IETF remains responsible for the development and quality of the | The IETF remains responsible for the development and quality of the | |||
| Internet Standards. Apart from the roles described below, the IETF | Internet Standards. Apart from the roles described below, the IETF | |||
| and ISOC acknowledge that ISOC has no influence whatsoever on the | and ISOC acknowledge that ISOC as an organization has no direct | |||
| technical content of Internet Standards. | influence whatsoever on the technical content of Internet Standards | |||
| (though ISOC employees may independently continue to make technical | ||||
| contributuins as individuals). | ||||
| 4. ISOC's Role in the IETF Standards Process | 4. ISOC's Role in the IETF Standards Process | |||
| ISOC plays a small role in the IETF standards process. In | ISOC plays a small role in the IETF standards process. In | |||
| particular, ISOC assists the standards process by appointing the IETF | particular, ISOC assists the standards process by appointing the IETF | |||
| NomCom chair and by confirming IAB candidates who are put forward by | NomCom chair and by confirming IAB candidates who are put forward by | |||
| the IETF NomCom, as described in [RFC7437], and by acting as the last | the IETF NomCom, as described in [RFC7437], and by acting as the last | |||
| resort in the appeals process, as described in [RFC2026]. | resort in the appeals process, as described in [RFC2026]. | |||
| ISOC maintains liaison relationships and memberships in other | ISOC maintains liaison relationships and memberships in other | |||
| skipping to change at page 5, line 7 ¶ | skipping to change at page 5, line 7 ¶ | |||
| architectural, procedural, and (where appropriate) policy matters | architectural, procedural, and (where appropriate) policy matters | |||
| pertaining to the Internet and its enabling technologies". This | pertaining to the Internet and its enabling technologies". This | |||
| connection between the IAB and ISOC ensures that ISOC's proposals in | connection between the IAB and ISOC ensures that ISOC's proposals in | |||
| the policy area are based on a sound understanding of the relevant | the policy area are based on a sound understanding of the relevant | |||
| technologies and architectures. ISOC's strong connection to the | technologies and architectures. ISOC's strong connection to the | |||
| Internet technical community has always been one of its main | Internet technical community has always been one of its main | |||
| strengths. | strengths. | |||
| 6. Legal Relationship with ISOC | 6. Legal Relationship with ISOC | |||
| The IETF LLC is a disregarded Limited Liability Company (LLC) of The | The IETF LLC is a disregarded Limited Liability Company (LLC) of the | |||
| Internet Society - established to provide a corporate legal framework | Internet Society - established to provide a corporate legal framework | |||
| for facilitating current and future activities related to the IETF, | for facilitating current and future activities related to the IETF, | |||
| IAB, and IRTF. It was established by the ISOC/IETF LLC Agreement | IAB, and IRTF. It was established by the ISOC/IETF LLC Agreement | |||
| [OpAgreement] on August 27, 2018, and governs the relationship | [OpAgreement] on August 27, 2018, and governs the relationship | |||
| between the IETF LLC and ISOC. | between the IETF LLC and ISOC. | |||
| The IETF Trust, documented in [RFC5378], and updated in | The IETF Trust, documented in [RFC5378], and updated in | |||
| [I-D.ietf-iasa2-trust-rationale] and [I-D.ietf-iasa2-trust-update], | [I-D.ietf-iasa2-trust-rationale] and [I-D.ietf-iasa2-trust-update], | |||
| provides legal protection for the RFC series of documents and other | provides legal protection for the RFC series of documents and other | |||
| aspects of the IETF. This includes things such as protection for | aspects of the IETF. This includes things such as protection for | |||
| trademarks, copyrights, and intellectual property rights. As part of | trademarks, copyrights, and intellectual property rights. As part of | |||
| the IETF Trust arrangement, IETF standards documents can be freely | the IETF Trust arrangement, IETF standards documents can be freely | |||
| downloaded, copied, and distributed without financial or other | downloaded, copied, and distributed without financial or other | |||
| distribution restrictions, though all rights to change these | distribution restrictions, though all rights to change these | |||
| documents lie with the IETF. The IETF Trust also provides legal | documents lie with the IETF. The IETF Trust also provides legal | |||
| protection in case of disputes over intellectual property rights and | protection in case of disputes over intellectual property rights and | |||
| other rights. The creation of the IETF LLC has changed the way that | other rights. The creation of the IETF LLC has changed the way that | |||
| the IETF Trust's trustees are selected but did not change the purpose | the IETF Trust's trustees are selected but did not change the purpose | |||
| or operation of the Trust. One of the IETF Trust's trustees is | or operation of the Trust. One of the IETF Trust's trustees is | |||
| appointed by the ISOC's board of trustees. | appointed by the ISOC's Board of Trustees. | |||
| 7. Financial and Administrative Relationship with ISOC | 7. Financial and Administrative Relationship with ISOC | |||
| Under the terms of the Operating Agreement [OpAgreement] between ISOC | Under the terms of the Operating Agreement [OpAgreement] between ISOC | |||
| and the IETF, ISOC has agreed to provide some funding support for the | and the IETF, ISOC has agreed to provide significant funding support | |||
| IETF (ISOC has historically provided the IETF with significant | for the IETF. In particular, among other things, the IETF LLC is | |||
| financial support). In particular, among other things, the IETF LLC | responsible for creating and managing an annual operating budget for | |||
| is responsible for creating and managing an annual operating budget | the IETF; for negotiating, signing, and overseeing contracts; for | |||
| for the IETF; for negotiating, signing, and overseeing contracts; for | fundraising; for maintaining bank accounts; and for liability | |||
| fund raising; for maintaining bank accounts; and for liability | insurance. The IETF LLC is managed by a Board of Directors, one of | |||
| insurance. The IETF LLC is managed by a board of directors, one of | whom is appointed by the ISOC's Board of Trustees. The intention is | |||
| whom is appointed by the ISOC's board of trustees. The intention is | that ISOC and the IETF LLC operate at arm's length. | |||
| that ISOC and the IETF LLC operate at arms length. | ||||
| The IETF LCC establishes contracts with third parties to provide | The IETF LLC establishes contracts with third parties to provide | |||
| different types of services to the IETF. Note that it is possible | different types of services to the IETF. Note that it is possible | |||
| that some of those services are provided by ISOC or involve ISOC | that some of those services are provided by ISOC or involve ISOC | |||
| staff. | staff. | |||
| Under the new IASA 2.0 structure, the IETF is solely responsible for | Under the new IASA 2.0 structure, the IETF LLC is solely responsible | |||
| its administration, including the IETF Trust, IAB, IESG, IETF working | for its administration, including the IETF Trust, IAB, IESG, IETF | |||
| groups, and other IETF processes. A further exploration of this can | working groups, and other IETF processes. A further exploration of | |||
| be found in Section 4 of [I-D.ietf-iasa2-rfc4071bis]. | this can be found in Section 4 of [I-D.ietf-iasa2-rfc4071bis]. | |||
| 8. IANA Considerations | 8. IANA Considerations | |||
| This document introduces no new IANA considerations. | This document introduces no new IANA considerations. | |||
| 9. Security Considerations | 9. Security Considerations | |||
| This document introduces no new security considerations. | This document introduces no new security considerations. | |||
| 10. Privacy Considerations | 10. Privacy Considerations | |||
| skipping to change at page 6, line 41 ¶ | skipping to change at page 6, line 41 ¶ | |||
| on the tax status from John Levine. | on the tax status from John Levine. | |||
| -03: As we entered IESG review, added a short description of what | -03: As we entered IESG review, added a short description of what | |||
| ISOC does (in relation to the IETF) that can be used in external | ISOC does (in relation to the IETF) that can be used in external | |||
| material by both the IETF and ISOC. | material by both the IETF and ISOC. | |||
| -04: Clarification adding text to Section 6 on legal issue. | -04: Clarification adding text to Section 6 on legal issue. | |||
| -05: Fix nits | -05: Fix nits | |||
| 13. Informative References | -06: Fix nits and other changes from IESG review | |||
| 13. References | ||||
| 13.1. Normative References | ||||
| [I-D.ietf-iasa2-rfc4071bis] | [I-D.ietf-iasa2-rfc4071bis] | |||
| Haberman, B., Hall, J., and J. Livingood, "Structure of | Haberman, B., Hall, J., and J. Livingood, "Structure of | |||
| the IETF Administrative Support Activity, Version 2.0", | the IETF Administrative Support Activity, Version 2.0", | |||
| draft-ietf-iasa2-rfc4071bis-11 (work in progress), April | draft-ietf-iasa2-rfc4071bis-11 (work in progress), April | |||
| 2019. | 2019. | |||
| 13.2. Informative References | ||||
| [BCP10] "BCP10", <https://www.rfc-editor.org/refs/ref-bcp10.txt>. | ||||
| [I-D.ietf-iasa2-trust-rationale] | [I-D.ietf-iasa2-trust-rationale] | |||
| Arkko, J., "Discussion of the IASA 2.0 Changes as They | Arkko, J., "Discussion of the IASA 2.0 Changes as They | |||
| Relate to the IETF Trust", draft-ietf-iasa2-trust- | Relate to the IETF Trust", draft-ietf-iasa2-trust- | |||
| rationale-03 (work in progress), October 2018. | rationale-03 (work in progress), October 2018. | |||
| [I-D.ietf-iasa2-trust-update] | [I-D.ietf-iasa2-trust-update] | |||
| Arkko, J. and T. Hardie, "Update to the Process for | Arkko, J. and T. Hardie, "Update to the Process for | |||
| Selection of Trustees for the IETF Trust", draft-ietf- | Selection of Trustees for the IETF Trust", draft-ietf- | |||
| iasa2-trust-update-03 (work in progress), February 2019. | iasa2-trust-update-03 (work in progress), February 2019. | |||
| [ISOC-Mission] | ||||
| "ISOC Mission", | ||||
| <https://www.internetsociety.org/mission/>. | ||||
| [OpAgreement] | [OpAgreement] | |||
| "Limited Liability Company Agreement of IETF | "Limited Liability Company Agreement of IETF | |||
| Administration LLC", August 2018. | Administration LLC", August 2018, | |||
| <https://www.ietf.org/documents/180/ | ||||
| IETF-LLC-Agreement.pdf>. | ||||
| [RFC2026] Bradner, S., "The Internet Standards Process -- Revision | [RFC2026] Bradner, S., "The Internet Standards Process -- Revision | |||
| 3", BCP 9, RFC 2026, DOI 10.17487/RFC2026, October 1996, | 3", BCP 9, RFC 2026, DOI 10.17487/RFC2026, October 1996, | |||
| <https://www.rfc-editor.org/info/rfc2026>. | <https://www.rfc-editor.org/info/rfc2026>. | |||
| [RFC2028] Hovey, R. and S. Bradner, "The Organizations Involved in | [RFC2028] Hovey, R. and S. Bradner, "The Organizations Involved in | |||
| the IETF Standards Process", BCP 11, RFC 2028, | the IETF Standards Process", BCP 11, RFC 2028, | |||
| DOI 10.17487/RFC2028, October 1996, | DOI 10.17487/RFC2028, October 1996, | |||
| <https://www.rfc-editor.org/info/rfc2028>. | <https://www.rfc-editor.org/info/rfc2028>. | |||
| [RFC2031] Huizer, E., "IETF-ISOC relationship", RFC 2031, | [RFC2031] Huizer, E., "IETF-ISOC relationship", RFC 2031, | |||
| DOI 10.17487/RFC2031, October 1996, | DOI 10.17487/RFC2031, October 1996, | |||
| <https://www.rfc-editor.org/info/rfc2031>. | <https://www.rfc-editor.org/info/rfc2031>. | |||
| [RFC2282] Galvin, J., "IAB and IESG Selection, Confirmation, and | ||||
| Recall Process: Operation of the Nominating and Recall | ||||
| Committees", RFC 2282, DOI 10.17487/RFC2282, February | ||||
| 1998, <https://www.rfc-editor.org/info/rfc2282>. | ||||
| [RFC2850] Internet Architecture Board and B. Carpenter, Ed., | [RFC2850] Internet Architecture Board and B. Carpenter, Ed., | |||
| "Charter of the Internet Architecture Board (IAB)", | "Charter of the Internet Architecture Board (IAB)", | |||
| BCP 39, RFC 2850, DOI 10.17487/RFC2850, May 2000, | BCP 39, RFC 2850, DOI 10.17487/RFC2850, May 2000, | |||
| <https://www.rfc-editor.org/info/rfc2850>. | <https://www.rfc-editor.org/info/rfc2850>. | |||
| [RFC3677] Daigle, L., Ed. and Internet Architecture Board, "IETF | [RFC3677] Daigle, L., Ed. and Internet Architecture Board, "IETF | |||
| ISOC Board of Trustee Appointment Procedures", BCP 77, | ISOC Board of Trustee Appointment Procedures", BCP 77, | |||
| RFC 3677, DOI 10.17487/RFC3677, December 2003, | RFC 3677, DOI 10.17487/RFC3677, December 2003, | |||
| <https://www.rfc-editor.org/info/rfc3677>. | <https://www.rfc-editor.org/info/rfc3677>. | |||
| End of changes. 18 change blocks. | ||||
| 35 lines changed or deleted | 48 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||