Internet DRAFT - draft-klensin-iasa2-2418upd-5377upd

draft-klensin-iasa2-2418upd-5377upd







Network Working Group                                         J. Klensin
Internet-Draft                                          October 22, 2018
Updates: 2418, 5377 (if approved)
Intended status: Informational
Expires: April 25, 2019


            IASA2 Updates for Terminology and Relationships
                 draft-klensin-iasa2-2418upd-5377upd-00

Abstract

   The IASA2 effort changes the terminology associated with several
   roles and the relationships among existing bodies and functions to
   the successors of others.  In some cases, the relevant earlier
   documents address other matters, including ones that are critical to
   IETF processes, and are better dealt with by updating the relevant
   terminology or provisions rather than attempting to replace the
   earlier documents in their entirety.  This document provides those
   updates for RFCs 2418 and 5377 [[and perhaps others in later
   versions]].

Note in Draft

   There has been a recent discussion on the IASA2 list, and partially
   on the IETF one, about the desirability of completely replacing
   important procedural or IETF process definitional documents in order
   to align terminology with the new IASA model.  It has been suggested
   (by this author and others) that such changes are error-prone,
   unnecessary work, may be misleading, and may (presumably
   inadvertently) violate the WG's charter by changing IETF procedures
   for creation, review, and approval of standards for the Internet.

   With the posting deadline for IETF 103 (Bangkok) and awareness of the
   difficulty of holding a WG discussion of a problem with one or more
   documents without a concrete counterproposal in hand, this hastily-
   prepared I-D is provided for the convenience of the WG and the IETF
   community.  Should the WG decide to make use of it, a co-author or
   replacement author should be sought who would take the lead in
   smoothing rough edges, inserting references where needed, adding
   material for other specifications that should be updated, etc.

Status of This Memo

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





Klensin                  Expires April 25, 2019                 [Page 1]

Internet-Draft          IASA2 Terminology Updates           October 2018


   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 April 25, 2019.

Copyright Notice

   Copyright (c) 2018 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
   (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.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Document updates: RFC 2418  . . . . . . . . . . . . . . . . .   3
   4.  Document updates: RFC 5377  . . . . . . . . . . . . . . . . .   4
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   4
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .   4
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   The 2018 transition from the original IETF Administrative Support
   Activity (IASA) to a new model renames a number of roles and tunes
   the relationships among various bodies.  These changes affect the
   terminology associated with existing definitional and procedural
   specifications without actually making substantive changes to the
   procedures or operations involved.  Rather than replacing
   ("obsoleting") the original documents where that is not strictly and



Klensin                  Expires April 25, 2019                 [Page 2]

Internet-Draft          IASA2 Terminology Updates           October 2018


   substantively necessary, potentially creating confusion about
   references to them and risking inadvertent substantive changes, this
   document provides those updates that are required for consistency
   with the new IASA2 approach and clarifies the relationships involved.

   This version of the I-D provides the changes needed to update the
   base specifications for IETF Working Group operations and procedures
   [RFC2418] and advice to the IETF Trust [RFC5377] to reflect the IASA2
   changes.  It does not attempt to address other issues with those
   documents that have arisen as the IETF has evolved or errors have
   been detected.

2.  Overview

   The changes from the original IASA model to the iASA2 one include
   changes that, while important in their own right, affect the
   terminology used in other procedural documents without changing the
   underlining procedures or specifications of those documents.  These
   changes include

   o  Changes of titles, e.g., from "IETF Executive Director" to
      "Managing Director of the IETF Secretariat".  The IASA2
      specifications may change the underlying roles as well, but those
      changes do not affect the documents that are the subject of this
      specification.

   o  Changes of relationships. e.g, the Trustees of the IETF Trust are
      no longer simply the members of what is in principle another body
      (the IAOC, which has been eliminated) but are separately
      appointed.  In part because there is little actual change to the
      structure or responsibilities of the Trustees themselves, the
      documents that are the subject of this specification should be
      updated to eliminate assertions about the previous relationships
      but do not require more substantive chagnes.

3.  Document updates: RFC 2418

   In Section 1, paragraph 6, "The area directors sitting as a body...",
   change

      The IETF Executive Director is...

   to

      The Managing Director of the IETF Secretariat is...

   See above for explanation.




Klensin                  Expires April 25, 2019                 [Page 3]

Internet-Draft          IASA2 Terminology Updates           October 2018


4.  Document updates: RFC 5377

   Section 1, paragraph 1  Drop "made up of the members of the IAOC
      [RFC4371]" after "board of trustees"

   Section 2, last paragraph  Drop "Appeals of the actions of the
      Trustees of the IETF Trust are governed by other documents.  As
      the Trustees are the members of the IAOC, the appeals procedure
      documented in BCP 101 (currently [RFC4371]) is applicable."
      [[CREF1: This is in need of careful checking.  Probably the
      correct change is not this one but would be a reference to
      whatever document lays out the new appeals procedures.]]

   Section 3, first paragraph  Drop ", which is made up of the members
      of the IAOC, as described in [RFC4071] and [RFC4371]".

5.  Acknowledgements

   This document was initiated as a response to perceived issues with
   efforts to replace RFC 2418 and RFC 5377 [[CREF2: Insert references
   in -01]].  It borrows extensively from the changes suggested in those
   drafts and would not have been possible without the work of Rich Salz
   and Joel Halpern in constructing the drafts and their suggested text.

6.  IANA Considerations

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

   This memo includes no requests to or actions for IANA.

7.  Security Considerations

   This specification is about technical updates to IETF procedures.  It
   does not change the security of the Internet and any issues are
   identified in the documents normatively referenced.

8.  Normative References

   [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>.

   [RFC5377]  Halpern, J., Ed., "Advice to the Trustees of the IETF
              Trust on Rights to Be Granted in IETF Documents",
              RFC 5377, DOI 10.17487/RFC5377, November 2008,
              <https://www.rfc-editor.org/info/rfc5377>.





Klensin                  Expires April 25, 2019                 [Page 4]

Internet-Draft          IASA2 Terminology Updates           October 2018


Author's Address

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

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










































Klensin                  Expires April 25, 2019                 [Page 5]