´╗┐

Internet Engineering Task Force (IETF)                          J. Arkko
Internet-Draft
Request for Comments: 8714                                      Ericsson
Obsoletes: 4371 (if approved)
BCP: 101                                                       T. Hardie
Intended status:
Obsoletes: 4371                                             January 2020
Category: Best Current Practice                  February 4, 2019
Expires: August 8, 2019
ISSN: 2070-1721

   Update to the Process for Selection of Trustees for the IETF Trust
                    draft-ietf-iasa2-trust-update-03

Abstract

   This memo updates the process for selection of trustees Trustees for the IETF
   Trust.  Previously, the Internet IETF Administrative Oversight Committee
   (IAOC) members also acted as trustees, Trustees, but the IAOC has been
   eliminated as part of an update of to the structure of the Internet IETF
   Administrative Support Activity (IASA).  This memo specifies that the
   trustees
   Trustees shall be selected separately.

   This memo obsoletes RFC 4371.  The changes relate only to the
   selection of trustees. Trustees.  All other aspects of the IETF Trust remain as
   they are today.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working memo documents an Internet Best Current Practice.

   This document is a product of the Internet Engineering Task Force
   (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list  It represents the consensus of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid the IETF community.  It has
   received public review and has been approved for a maximum publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   BCPs is available in Section 2 of RFC 7841.

   Information about the current status of six months this document, any errata,
   and how to provide feedback on it may be updated, replaced, or obsoleted by other documents obtained at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on August 8, 2019.
   https://www.rfc-editor.org/info/rfc8714.

Copyright Notice

   Copyright (c) 2019 2020 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info)
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  IETF Trust  . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Selection of Trustees . . . . . . . . . . . . . . . . . . . .   3
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   4
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     7.1.
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   4
     7.2.
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Appendix A.  Changes from Previous Versions . . . . . . . . . . .   5
   Acknowledgements
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   This memo updates the process for selection of trustees Trustees for the IETF
   Trust.  Previously, the Internet IETF Administrative Oversight Committee
   (IAOC) members also acted as trustees, Trustees, but the IAOC has been
   eliminated as part of an update of to the structure of the Internet IETF
   Administrative Support Activity (IASA).  This memo specifies that the
   trustees
   Trustees shall be selected separately.  See Section 3.

   This memo obsoletes RFC 4371. [RFC4371].  The changes relate only to the
   selection of trustees. Trustees.  All other aspects of the IETF Trust remain as
   they are today.  Section 2 copies the definition as it was in RFC
   4371,
   [RFC4371], only leaving out the part about trustee Trustee selection and
   adding a reference to the IETF Trust website.

   For a discussion of why this change is needed and a rationale for
   these specific changes, see [I-D.ietf-iasa2-trust-rationale]. [RFC8715].

2.  IETF Trust

   A Trust ("the IETF Trust") has been formed for the purpose of
   acquiring, holding, maintaining, and licensing certain existing and
   future intellectual property and other property used in connection
   with the administration of the IETF.  The Trust was formed by the
   signatures of its Settlors and initial Trustees.  The Settlors, who
   contributed initial intellectual property to the Trust, were ISOC and
   the Corporation for National Research Initiatives.  The Beneficiary
   of the IETF Trust is the IETF as a whole.

   Further details of the IETF Trust may be found at the IETF Trust's
   website, <https://trustee.ietf.org/>.

3.  Selection of Trustees

   This document revises the original Trustee selection procedures
   defined in [RFC4071] and [RFC4371], [RFC4371] to eliminate the requirement that
   trustees
   Trustees be drawn from the members of the IAOC.

   In this newly revised IETF Trust structure, there will be five
   Trustees.  Three shall be appointed by the IETF Nominating Committee
   (NomCom) and confirmed by the Internet Engineering Steering Group
   (IESG), one shall be appointed by the IESG, and one shall be
   appointed by the Internet Society (ISOC) Board of Trustees.  The
   appointments by the IESG and the ISOC Board of Trustees do not
   require confirmation.

   The IETF Trust Chair informs the nominating committee of the Trustee
   positions to be reviewed.  The IETF Trust will provide a summary of
   the expertise desired of the Trustee candidates to each appointing
   body.

   A change to the Trust Agreement is required to put this change into
   effect, and this document requests that the current Trustees make
   this change at the earliest convenient time and no later than the end
   of the 104th IETF meeting in March 2019.

   The terms of the appointed trustees Trustees from the IETF NomCom shall be
   three years.  The initial selection shall be one, two, and three year
   terms in order to initially stagger the terms.  The other
   appointments by the IESG and the ISOC Board of Trustees shall be two
   year terms, with the initial terms being one and two years,
   respectively.  The goal of the staggered initial terms is to minimize
   potential Trustee turnover in any single year.  To maintain the
   staggered terms, each appointing body may may, at its discretion discretion, appoint
   Trustees for shorter terms as needed in exceptional situations, e.g.,
   for mid-term vacancies or when an appointment is not ready by the
   time of the first IETF meeting of the year.

   Once the initial trustee Trustee selections according to the procedures in
   this document are complete, and at each subsequent annual meeting of
   the IETF Trust once (once new trustees Trustees are seated, seated), the trustees Trustees shall
   elect
   by a majority vote of the IETF Trust one trustee Trustee to serve as IETF Trust Chair.

   The processes regarding NomCom appointments and recalls Chair by a majority vote of
   the IETF Trust.

   Trustees
   for appointed by the IETF Trust follow those NomCom may be recalled according to
   the recall process described in
   [I-D.ietf-iasa2-rfc7437bis].  For [BCP10].  Trustees appointed by the
   IESG or by the ISOC Board of Directors may be recalled by the
   appointing body.  For appointments made by the IESG, the IESG is
   expected to run an open selection process and to consider the
   necessary skill set and conflicts of interest as part of that
   process.

4.  Security Considerations

   This memo has no security implications for the Internet.

5.  IANA Considerations

   This memo requests document has no action from IANA. IANA actions.

6.  Acknowledgements

   The authors would like to thank members of the earlier IASA 2.0
   design team who were Brian Haberman, Eric Rescorla, Jari Arkko, Jason  References

6.1.  Normative References

   [BCP10]    Kucherawy, M., Ed., Hinden, R., Ed., and J. Livingood, Joe Hall,
              Ed., "IAB, IESG, IETF Trust, and Leslie Daigle.  The authors would also like
   to thank Alissa Cooper, Andrew Sullivan, Brian Carpenter, Lucy Lynch,
   and John Levine for interesting discussions in this problem space.
   The authors would also like to thank Russ Housley, Bob Hinden, Scott
   Mansfield, Alexey Melnikov, Suresh Krishnan, Mirja Kuhlewind, Ben
   Campbell, Spencer Dawkins, Martin Vigoreux, Benjamin Kaduk, and
   Adrian Farrel for careful review.  Finally, the authors would like to
   thank the authors of [RFC4371], as the text from that RFC remains in
   this document.

7.  References

7.1.  Normative References

   [I-D.ietf-iasa2-rfc7437bis]
              Kucherawy, M., Hinden, R., and J. Livingood, "IAB, IESG,
              IETF Trust and IETF LLC Selection, Confirmation, IETF LLC Selection,
              Confirmation, and Recall Process: Operation of the IETF
              Nominating and Recall Committees", draft-ietf-iasa2-rfc7437bis-05 (work
              in progress), BCP 10, RFC 8713,
              January 2019. 2020, <https://rfc-editor.org/info/bcp10>.

   [RFC4071]  Austein, R., Ed. and B. Wijnen, Ed., "Structure of the
              IETF Administrative Support Activity (IASA)", BCP 101,
              RFC 4071, DOI 10.17487/RFC4071, April 2005,
              <https://www.rfc-editor.org/info/rfc4071>.

   [RFC4371]  Carpenter, B., Ed. and L. Lynch, Ed., "BCP 101 Update for
              IPR Trust", BCP 101, RFC 4371, DOI 10.17487/RFC4371,
              January 2006, <https://www.rfc-editor.org/info/rfc4371>.

7.2.

6.2.  Informative References

   [I-D.ietf-iasa2-trust-rationale]

   [RFC8715]  Arkko, J., "Discussion of the IASA 2.0 Changes as They
              Relate to the IETF Trust", draft-ietf-iasa2-trust-
              rationale-03 (work in progress), October 2018.

Appendix A.  Changes from Previous Versions RFC Editor: Please remove this section upon publication. 8715, DOI 10.17487/RFC8715,
              January 2020, <https://rfc-editor.org/info/rfc8715>.

Acknowledgements

   The -03pre1b version replaced updates of RFCs 4071 and 4371 with
   obsoletion authors would like to thank members of RFC 4371, and updated the reference to RFC 7437 to its
   newer bis version.  It earlier IASA 2.0
   design team: Brian Haberman, Eric Rescorla, Jari Arkko, Jason
   Livingood, Joe Hall, and Leslie Daigle.  The authors would also copied the one remaining paragraph from
   RFC 4371 like
   to this document.

   The version draft-itef-iasa2-trust-update-02.txt made some editorial
   corrections, as well as clarifying that no confirmation is needed in
   the cases other than the nomcom appointment, specified how IETF Trust
   chair is chosen, thank Alissa Cooper, Andrew Sullivan, Brian Carpenter, Lucy Lynch,
   and required that an open process be used by the
   IESG John Levine for the selections.

   The version draft-ietf-iasa2-trust-update-01.txt has taken into
   account last call comments. interesting discussions in this problem space.
   The changes are: 1) Clarification of the
   role of the IETF Trust Chair authors would also like to indicate which trustee positions are
   up thank Russ Housley, Bob Hinden, Scott
   Mansfield, Alexey Melnikov, Suresh Krishnan, Mirja K├╝hlewind, Ben
   Campbell, Spencer Dawkins, Martin Vigoreux, Benjamin Kaduk, and
   Adrian Farrel for selection, similar to how RFC 7437 requires careful review.  Finally, the IETF Executive
   Director authors would like to do it. 2) The addition of empty security and IANA
   consideration sections. 3) The clarification
   thank the authors of [RFC4371], as the staggering rules
   for NomCom selections. 4) Updated text regarding the application of
   rules from that RFC 7437. 5) Update draft title to be correct in terms of
   specifying a process rather than the actual persons.  6) Update the
   text regarding desirable expertise to use the same language as remains in RFC
   7437 instead of the "list of desired qualifications".

   The version draft-ietf-iasa2-trust-update-00.txt corrected the
   desired document status to BCP, and made several editorial and
   language updates.  This version also updated the wording for the
   request for the current trustees to adopt
   this change, from "earliest
   convenience" to "earliest convenient time".

   The version draft-arkko-iasa2-trust-update-00.txt was the initial
   version. document.

Authors' Addresses

   Jari Arkko
   Ericsson
   FI-02700 Kauniainen  02700
   Finland

   Email: jari.arkko@piuha.net

   Ted Hardie

   Email: ted.ietf@gmail.com