Internet DRAFT - draft-hardie-iaoc-iab-update

draft-hardie-iaoc-iab-update






Network Working Group                                          T. Hardie
Internet-Draft                                               A. Sullivan
Updates: RFC4071 (if approved)                                       Dyn
Intended status: Best Current Practice                        R. Housley
Expires: August 19, 2016                                  Vigil Security
                                                       February 18, 2016

         Updating the ex officio member of the IAB in the  IAOC
                    draft-hardie-iaoc-iab-update-02

Abstract

   This document updates the way in which the ex officio member from the
   IAB who serves on the IAOC is appointed in order to better match the
   skills set out in RFC 4333.

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 http://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 August 19, 2016.

Copyright Notice

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

1.  Introduction





Hardie, Sullivan & HouslExpires August 19, 2016                 [Page 1]

Internet-Draft              IAB IAOC update                February 2016


   [RFC4071] describes the membership of the IAOC and assigns two roles
   to the Internet Architecture Board: appointing a member from the
   community and providing a member from the IAB.  The ex officio member
   provided by the IAB is currently required to be the IAB Chair.
   [RFC4333] sets out selection guidelines for members of the IAOC.
   This document proposes an update to RFC 4071 to allow a different IAB
   member to serve, in order to better meet the criteria set out in RFC
   4333.

2.  Proposed change

   This document proposes to allow the IAB to select from among its
   members the individual who best matches the criteria set out in IAOC
   member selection guidelines RFC 4333.  This might be a different
   person than the person best able to carry out the other duties of the
   IAB Chair.  Should it happen that the IAB Chair is also the best
   person to serve on the IAOC, then the IAB Chair may serve; it is
   simply no longer required.

   The individual named by the IAB will serve a renewable one year term,
   subject to the recall of the IAB by the same means the IAB chair is
   removed (an affirmative vote of two-thirds of the IAB).  All IAB
   members are also subject to recall under the terms of [RFC3777].

   Given the nature of the IAOC responsibilities, it is advantageous
   that the appointment of an IAB member to the IAOC be approximately as
   stable as the appointment of the IAB chair.

   The resulting changes to RFC 4071 are:

   In section 4, where the document on membership currently says "The
   IAB Chair (ex officio);", we propose "An IAB member designated for a
   one-year term."

3.  Security Considerations

   This document describes an administrative change rather than a
   protocol.

4.  IANA Considerations

   This document currently has no actions for IANA.

5.  Acknowledgements

   Olaf Kolkman was kind enough to review and provide suggestions to an
   early version of this document.  Lou Berger, Brian Carpenter, Leslie
   Daigle, Martin Duerst, Bob Hinden, John Klensin, Mike St.  Johns, and
   Suzanne Woolf provided additional comments on version 1.

6.  References

6.1.  Normative References

Hardie, Sullivan & HouslExpires August 19, 2016                 [Page 2]

Internet-Draft              IAB IAOC update                February 2016


   [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, <http://www.rfc-
              editor.org/info/rfc4071>.

   [RFC3777]  Galvin, J., Ed., "IAB and IESG Selection, Confirmation,
              and Recall Process: Operation of the Nominating and Recall
              Committees", RFC 3777, DOI 10.17487/RFC3777, June 2004,
              <http://www.rfc-editor.org/info/rfc3777>.

6.2.  Informative References

   [RFC4333]  Huston, G.Ed.,  and B. Wijnen, Ed., "The IETF
              Administrative Oversight Committee (IAOC) Member Selection
              Guidelines and Process", BCP 113, RFC 4333, DOI 10.17487/
              RFC4333, December 2005, <http://www.rfc-editor.org/info/
              rfc4333>.

Authors' Addresses

   Ted Hardie
   
   Email: ted.ietf@gmail.com


   Andrew Sullivan
   Dyn
   
   Email: asullivan@dyn.com


   Russ Housley
   Vigil Security
   
   Email: housley@vigilsec.com


















Hardie, Sullivan & HouslExpires August 19, 2016                 [Page 3]