[Docs] [txt|pdf|xml|html] [Tracker] [WG] [Email] [Diff1] [Diff2] [Nits]

Versions: (draft-klensin-iasa2-2418upd-5377upd) 00 01 02 03 04 05 06 07 Draft is active
In: MissingRef
IASA2                                                    J. Klensin, Ed.
Internet-Draft                                            March 11, 2019
Updates: 2028, 2418, 3005, 3710, 3929,
         4633, 6702 (if approved)
Intended status: Best Current Practice
Expires: September 12, 2019


    Consolidated IASA 2.0 Updates of IETF Administrative Terminology
                  draft-ietf-iasa2-consolidated-upd-07

Abstract

   In 2018, the IETF began the transition to a new administrative
   structure and updated its IETF Administrative Support Activity (IASA)
   to a new "IASA 2.0" structure.  In addition to more substantive
   changes that are described in other documents, the transition to the
   2018 IETF Administrative Support structure changes several position
   titles and organizational relationships that are referenced
   elsewhere.  Rather than reissue those referencing documents
   individually, this specification provides updates to them and
   deprecates some now-obsolete documents to ensure that there is no
   confusion due to these changes.

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 documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents 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 September 12, 2019.

Copyright Notice

   Copyright (c) 2019 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



Klensin                Expires September 12, 2019               [Page 1]


Internet-Draft         IASA2 Consolidated Updates             March 2019


   (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.  Where Appropriate, Replacement of the IETF Executive Director
       position with the Managing Director, IETF Secretariat . . . .   3
   3.  Remove the IETF Executive Director as an Option . . . . . . .   4
   4.  Deprecated Documents  . . . . . . . . . . . . . . . . . . . .   4
     4.1.  Documents Whose Context is Changed by This Specification    4
     4.2.  General Description of the IETF Adminstrative Model . . .   5
   5.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   5
   6.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .   5
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   7
   Appendix A.  Change Log . . . . . . . . . . . . . . . . . . . . .   7
     A.1.  Changes from version -00 (2018-11-15) to -01  . . . . . .   7
     A.2.  Changes from version -01 (dated 2018-12-06 but
           posted 2012-12-07) to -02 . . . . . . . . . . . . . . . .   8
     A.3.  Changes from version -02 (2018-12-07) to -03  . . . . . .   8
     A.4.  Changes from version -03 (2018-12-12) to -04  . . . . . .   8
     A.5.  Changes from version -04 (2019-01-17) to -05  . . . . . .   9
     A.6.  Changes from version -05 (2019-01-31) to -06  . . . . . .   9
     A.7.  Changes from version -06 (2019-03-06) to -07  . . . . . .  10
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   In 2018, the IETF began the transition to a new administrative
   structure, and updated its IETF Administrative Support Activity
   (IASA) to a new "IASA 2.0" structure [RFC-Struct].  Key IASA 2.0
   changes have been specified in a series of documents, including
   changes to the IETF Trust [RFC-trust-update], the rationale for it
   [RFC-trust-rationale], a new defining document for the IETF
   Administration LLC [LLC-Agreement] (informally called the "IETF LLC"
   or just "the LLC" in places in this document and elsewhere) and
   adjustments to the procedures for nominations and selections for
   relevant positions [RFC-7437bis].




Klensin                Expires September 12, 2019               [Page 2]


Internet-Draft         IASA2 Consolidated Updates             March 2019


   In addition to more substantive changes that are described in those
   and other documents, the IASA 2.0 structure changes several position
   titles and organizational relationships that are referenced in other
   documents.  Rather than reissue those documents individually, this
   document provides a unified update to them.

   This document updates RFCs 2028, 2418, 3005, 3710, 3929, 4633, and
   6702 (citations in context below) to make those terminology and
   related changes.  In addition, with the authorization of the IAB, it
   requests that the Informational RFC 3716 be made Historic (see
   Section 4).  The sections that follow identify the details of the
   relevant documents and the required changes.

2.  Where Appropriate, Replacement of the IETF Executive Director
    position with the Managing Director, IETF Secretariat

   Under the IASA 2.0 structure, most of the responsibilities of the
   former position of IETF Executive Director been assigned to a new
   position (or at least title) of Managing Director of the IETF
   Secretariat.  An "Executive Director" title is now associated with
   different, and largely new, responsibilities as an Officer of the
   IETF Administration LLC.  These changes are described in the
   description of the new structural arrangements [RFC-Struct].

   This document applies that change to the following:

   o  RFC 2028, The Organizations Involved in the IETF Standards Process
      [RFC2028], Section 3.3.

   o  RFC 2418, IETF Working Group Guidelines and Procedures [RFC2418],
      Section 1.

   o  RFC 3710, An IESG Charter, Section 2 [RFC3710].

   o  RFC 3929, Alternative Decision Making Processes for Consensus-
      Blocked Decisions in the IETF [RFC3929], Sections 4.1.1 and 4.3
      (twice).

   o  RFC 4633, Experiment in Long-Term Suspensions From Internet
      Engineering Task Force (IETF) Mailing Lists [RFC4633], Section 1.

   o  RFC 6702, Promoting Compliance with Intellectual Property Rights
      (IPR) Disclosure Rules, Section 5 [RFC6702].

   Note that the current description of the Internet Standards Process
   [RFC2026] does not require an update by this document for this
   purpose because the reference to the IETF Executive Director in RFC




Klensin                Expires September 12, 2019               [Page 3]


Internet-Draft         IASA2 Consolidated Updates             March 2019


   2026 was replaced by a document that precedes the current effort
   [RFC3979] and that was, in turn, obsoleted by RFC 8179 [RFC8179].

3.  Remove the IETF Executive Director as an Option

   In a few cases, it is no longer appropriate for either the Managing
   Director, IETF Secretariat (former IETF Executive Director position)
   or the new IETF Executive Director (for the LLC) to perform a
   particular historical function.  The relevant documents are updated
   to remove the IETF Executive Director from the list of people with
   specific responsibilities or authority.  Those documents will not be
   updated to use "Managing Director, IETF Secretariat" but, instead,
   the mention of the position will simply be dropped.

   This document applies that change to the following:

   o  RFC 3005, IETF Discussion List Charter [RFC3005], section titled
      "Charter for the IETF Discussion List".  This document is modified
      to remove the authorization for the IETF Executive Director to
      restrict people from posting, etc.

4.  Deprecated Documents

   [[CREF1: Note to the WG, IESG, and RFC Editor: I hope this section
   correctly reflects the conclusions of discussions in and with the WG.
   If it does not, the issues should certainly be identified and fixed.
   However, details of some of the actions are the responsibility of the
   RFC Editor and RFC 3716 is an IAB document containing the report of
   an IAB Advisory Committee.  If that text, especially the phrasing of
   various actions, is not quite right, I hope those involved can sort
   the language out with the RFC Editor rather than requiring that the
   WG iterate on the draft. --JcK, editor.  RFC Editor: should this
   paragraph reach you, please remove it.]]

4.1.  Documents Whose Context is Changed by This Specification

   Both of the documents that follow were obsoleted in 2017 by RFC 8179
   [RFC8179], which changed mentions of the IETF Executive Director to
   point to the IETF Secretariat more generally.

   o  RFC 3979 [RFC3979].

   o  RFC 4879 [RFC4879].








Klensin                Expires September 12, 2019               [Page 4]


Internet-Draft         IASA2 Consolidated Updates             March 2019


4.2.  General Description of the IETF Adminstrative Model

   RFC 3716 [RFC3716] is a report of an IAB Advisory Committee that
   served as a starting point for the work that led to the original IASA
   structure.  That report is an IAB document rather than an IETF one.
   The IAB approved a proposal to move RFC 3716 to Historic on March 6,
   2019.

5.  Acknowledgments

   Brian Carpenter's careful checking and identification of documents
   that did, and did not, require consideration was essential to the
   draft in its current form.  He also made several other significant
   contributions.  Bob Hinden also gave the document a careful reading
   and made useful suggestions.  In additional to the above, Alissa
   Cooper, Eliot Lear, Heather Flanagan (the RFC Series Editor), and the
   current membership to the IAB helped sort out the handing of RFC
   3716.

6.  Contributors

   Jason Livingood did the hard work of identifying the documents that
   required updating and supplied considerable text used in this
   document.

7.  IANA Considerations

   [[CREF2: RFC Editor: Please remove this section before publication.]]

   This memo includes no requests to or actions for IANA.

8.  Security Considerations

   The changes specified in this document are matters of terminology and
   organizational structure derived from documents it references.  It
   should have no effect on Internet security.

9.  References

9.1.  Normative References

   [LLC-Agreement]
              IETF Administration LLC, "Limited Liability Company
              Agreement of IETF Administration LLC", August 2018,
              <https://www.ietf.org/documents/180/
              IETF-LLC-Agreement.pdf>.





Klensin                Expires September 12, 2019               [Page 5]


Internet-Draft         IASA2 Consolidated Updates             March 2019


   [RFC-7437bis]
              Kucherawy, M., Ed., Hinden, R., Ed., and J. Livingood,
              Ed., "IAB, IESG, and IETF LLC Selection, Confirmation, and
              Recall Process: Operation of the IETF Nominating and
              Recall Committees", 2018,
              <https://datatracker.ietf.org/doc/
              draft-ietf-iasa2-rfc7437bis/>.

   [RFC-Struct]
              Haberman, B., Hall, J., and J. Livingood, "Structure of
              the IETF Administrative Support Activity, Version 2.0",
              December 2018, <https://datatracker.ietf.org/doc/
              draft-ietf-iasa2-rfc4071bis/>.

   [RFC-trust-rationale]
              Arkko, J., "Discussion of the IASA 2.0 Changes as They
              Relate to the IETF Trust", 2018,
              <https://datatracker.ietf.org/doc/
              draft-ietf-iasa2-trust-rationale/>.

   [RFC-trust-update]
              Arkko, J. and T. Hardie, "Update to the Process for
              Selection of Trustees for the IETF Trust", 2018,
              <https://datatracker.ietf.org/doc/
              draft-ietf-iasa2-trust-update/>.

   [RFC2028]  Hovey, R. and S. Bradner, "The Organizations Involved in
              the IETF Standards Process", BCP 11, RFC 2028,
              DOI 10.17487/RFC2028, October 1996,
              <https://www.rfc-editor.org/info/rfc2028>.

   [RFC2418]  Bradner, S., "IETF Working Group Guidelines and
              Procedures", BCP 25, RFC 2418, DOI 10.17487/RFC2418,
              September 1998, <https://www.rfc-editor.org/info/rfc2418>.

   [RFC3005]  Harris, S., "IETF Discussion List Charter", BCP 45,
              RFC 3005, DOI 10.17487/RFC3005, November 2000,
              <https://www.rfc-editor.org/info/rfc3005>.

   [RFC3710]  Alvestrand, H., "An IESG charter", RFC 3710,
              DOI 10.17487/RFC3710, February 2004,
              <https://www.rfc-editor.org/info/rfc3710>.

   [RFC6702]  Polk, T. and P. Saint-Andre, "Promoting Compliance with
              Intellectual Property Rights (IPR) Disclosure Rules",
              RFC 6702, DOI 10.17487/RFC6702, August 2012,
              <https://www.rfc-editor.org/info/rfc6702>.




Klensin                Expires September 12, 2019               [Page 6]


Internet-Draft         IASA2 Consolidated Updates             March 2019


9.2.  Informative References

   [RFC2026]  Bradner, S., "The Internet Standards Process -- Revision
              3", BCP 9, RFC 2026, DOI 10.17487/RFC2026, October 1996,
              <https://www.rfc-editor.org/info/rfc2026>.

   [RFC3716]  IAB Advisory Committee, "The IETF in the Large:
              Administration and Execution", RFC 3716,
              DOI 10.17487/RFC3716, March 2004,
              <https://www.rfc-editor.org/info/rfc3716>.

   [RFC3929]  Hardie, T., "Alternative Decision Making Processes for
              Consensus-Blocked Decisions in the IETF", RFC 3929,
              DOI 10.17487/RFC3929, October 2004,
              <https://www.rfc-editor.org/info/rfc3929>.

   [RFC3979]  Bradner, S., Ed., "Intellectual Property Rights in IETF
              Technology", RFC 3979, DOI 10.17487/RFC3979, March 2005,
              <https://www.rfc-editor.org/info/rfc3979>.

   [RFC4633]  Hartman, S., "Experiment in Long-Term Suspensions From
              Internet Engineering Task Force (IETF) Mailing Lists",
              RFC 4633, DOI 10.17487/RFC4633, August 2006,
              <https://www.rfc-editor.org/info/rfc4633>.

   [RFC4879]  Narten, T., "Clarification of the Third Party Disclosure
              Procedure in RFC 3979", RFC 4879, DOI 10.17487/RFC4879,
              April 2007, <https://www.rfc-editor.org/info/rfc4879>.

   [RFC8179]  Bradner, S. and J. Contreras, "Intellectual Property
              Rights in IETF Technology", BCP 79, RFC 8179,
              DOI 10.17487/RFC8179, May 2017,
              <https://www.rfc-editor.org/info/rfc8179>.

Appendix A.  Change Log

   RFC Editor: Please remove this appendix before publication.

A.1.  Changes from version -00 (2018-11-15) to -01

   o  Removed RFCs 3979 and 4879 from the "obsoletes" list because they
      had already been obsoleted (by 8179).  It also removes RFC 8179
      from the "updates" list because 8179 uses "IETF Secretariat"
      terminology rather than "IETF Executive Director".

      [[CREF3: Note in Draft: That suggests an idea which might
      considerably mitigate the name confusion issue: Instead of
      singling out the Managing Director of the Secretariat as a named



Klensin                Expires September 12, 2019               [Page 7]


Internet-Draft         IASA2 Consolidated Updates             March 2019


      individual, perhaps we should be referring to the Secretariat
      itself, leaving the contact point or address up to them as an
      internal administrative matter.  Just a thought. --JcK]]

   o  Added text to explain why RFC 2026 is not on the hit list.

   o  Added an acknowledgment to Brian Carpenter.  If he catches another
      batch of errors and supplies text, he gets promoted to
      Contributor.

   o  Adjusted reference [RFC-Struct] to point to 4071bis.

   o  Minor editorial corrections and changes.

A.2.  Changes from version -01 (dated 2018-12-06 but posted 2012-12-07)
      to -02

   I accidentally omitted RFC 4844 from the document header "updates"
   list in Version 01 and noticed that in response to an unrelated
   question almost immediately after posting.  The correction seemed
   important enough to justify almost immediate re-posting.  Changes are
   only that header, the document file name, and the date.  --JcK

A.3.  Changes from version -02 (2018-12-07) to -03

   o  Removed discussion and pointers to RFC 7500 - IAB will publish
      separately.

   o  Added text to describe (very superficially) RFC 3716.  That
      document was obsoleted in the previous version but not described.

   o  Removed rant about titles and responsibilities from Section 2 and
      a subsequent editorial note I hope it is no longer needed --JcK.
      In additional, several blocks of text that were commented out in
      earlier versions of the XML have been removed entirely.

A.4.  Changes from version -03 (2018-12-12) to -04

   o  Removed RFC 4844 from the update list and discussion because the
      consensus in the WG seemed to be that it (and the RFC Editor)
      should be handled separately.

   o  Removed RFC 5377 from the update list and discussion because it
      involves the Trust.

   o  Editor's note in draft:





Klensin                Expires September 12, 2019               [Page 8]


Internet-Draft         IASA2 Consolidated Updates             March 2019


         The above changes and the earlier removal of RFC 7500 so the
         IAB could publish it own document completely eliminate the
         earlier Sections 2 and 3.  That may call for a revision of the
         Introduction and/or Abstract, but I have not done a review for
         this iteration of whether such changes are needed.

         As documents and references are shuffled in and out of this
         one, it occurred to me that having a non-normative appendix
         somewhere that would identify all of the documents containing
         changes to reflect the IASA 1.x to 2.0 transition would be of
         great help to any future historian trying to understand what we
         did and probably helpful to the IETF if some of these changes
         don't work out and/or require further tuning.  After a brief
         discussion, Jason and I concluded that appendix did not belong
         in this iteration of this document.

A.5.  Changes from version -04 (2019-01-17) to -05

   o  Changed title from "Consolidated IASA2-Related Document Updates"
      to "Consolidated IASA 2.0 Updates of IETF Administrative
      Terminology" per suggestions from Brian Carpenter and Bob Hinden
      and 2019-01-31 WG decision.

   o  Removed CREF from Section 1 (should have been done in -04).  The
      only remaining CREFs are the one in this section (above) that
      should probably be preserved through IETF Last Call and notes to
      the RFC Editor.

   o  Updated acknowledgments.

A.6.  Changes from version -05 (2019-01-31) to -06

   o  Changes to text about documents that are updated and made
      historic, per advice from RFC Editor, WG Chairs, and IAB.  This
      includes a statement about IAB action of 2019-03-06 that requests
      that the RFC Editor move RFC 3716 to Historic but does not
      obsolete that Informational report.  When minimal changes were
      attempted, Section 4 became very hard to read and hence was
      restructured and somewhat rewritten (and then further modified to
      work around an xml2rfc glitch).  Special attention should be paid
      to the note at the beginning of that section.

   o  Updated the Acknowledgments section.








Klensin                Expires September 12, 2019               [Page 9]


Internet-Draft         IASA2 Consolidated Updates             March 2019


A.7.  Changes from version -06 (2019-03-06) to -07

   o  Moved RFCs 3929 and 4633 from "obsoleted" to "updated" and
      stripped text requested that they be made Historic at the
      direction of the IETF Chair, WG Co-chair, and an author.

   o  Added a section number for a document listed in Section 2 that was
      missing.

   o  Added some notes to the RFC Editor and others.

   o  Updated the acknowledgments.

Author's Address

   John C Klensin (editor)
   1770 Massachusetts Ave, Ste 322
   Cambridge, MA  02140
   USA

   Phone: +1 617 245 1457
   Email: john-ietf@jck.com





























Klensin                Expires September 12, 2019              [Page 10]


Html markup produced by rfcmarkup 1.129c, available from https://tools.ietf.org/tools/rfcmarkup/