IAB, IESG, and IAOC Selection, Confirmation, and Recall Process: IAOC Advisor for the Nominating Committee
draft-dawkins-iesg-nomcom-advisor-iaoc-03

Document Type Active Internet-Draft (individual in gen area)
Last updated 2017-12-04 (latest revision 2017-09-02)
Stream IETF
Intended RFC status Best Current Practice
Formats plain text xml pdf html bibtex
Reviews
Stream WG state (None)
Document shepherd Spencer Dawkins
Shepherd write-up Show (last changed 2017-10-09)
IESG IESG state RFC Ed Queue
Consensus Boilerplate Yes
Telechat date
Responsible AD Alexey Melnikov
Send notices to Spencer Dawkins <spencerdawkins.ietf@gmail.com>
IANA IANA review state IANA OK - No Actions Needed
IANA action state No IC
RFC Editor RFC Editor state EDIT
IESG                                                          S. Dawkins
Internet-Draft                                            Wonder Hamster
Updates: 7437 (if approved)                            September 2, 2017
Intended status: Best Current Practice
Expires: March 6, 2018

    IAB, IESG, and IAOC Selection, Confirmation, and Recall Process:
               IAOC Advisor for the Nominating Committee
             draft-dawkins-iesg-nomcom-advisor-iaoc-03.txt

Abstract

   This specification formalizes an ad hoc practice used to provide
   advice to the IETF Nominating Committee about the operations of the
   IETF Administrative Oversight Committee.

   This document updates RFC 7437.

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 March 6, 2018.

Copyright Notice

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

Dawkins                   Expires March 6, 2018                 [Page 1]
Internet-Draft           IAOC Advisor for Nomcom          September 2017

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Discussion Venue  . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Background on 'IAOC Liaisons' to Nominating Committees  . . .   2
   4.  BCP Text Changes  . . . . . . . . . . . . . . . . . . . . . .   3
     4.1.  Change to Section 4.3, 'Structure'  . . . . . . . . . . .   3
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   4
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .   4
   Appendix A.  Discussion Points  . . . . . . . . . . . . . . . . .   5
     A.1.  Why is this Role an Advisor?  . . . . . . . . . . . . . .   5
     A.2.  Why is this Role not a Liaison? . . . . . . . . . . . . .   5
     A.3.  Why is this Role not required to be a Sitting IAOC
           Member? . . . . . . . . . . . . . . . . . . . . . . . . .   7
     A.4.  Why Does the Nominating Committee Request an IAOC
           Advisor?  . . . . . . . . . . . . . . . . . . . . . . . .   7
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   This specification formalizes an ad hoc practice used to provide
   advice to the IETF Nominating Committee about the operations of the
   IETF Administrative Oversight Committee (IAOC) (described in
   [RFC4071]).

   This document updates [RFC7437].

2.  Discussion Venue

   Please direct questions and comments to the IETF Discussion mailing
   list, at https://www.ietf.org/mailman/listinfo/ietf.

   Please note that background on discussion points that have come up
   previously on the public IETF Nomcom discussion mailing list, at
   https://www.ietf.org/mailman/listinfo/ietf-nomcom, during review is
   provided in Appendix A.

3.  Background on 'IAOC Liaisons' to Nominating Committees

   When RFC 7437 [RFC7437] was approved, it explicitly charged the
   Nominating Committee with selecting and reviewing certain members of
   the IAOC.  However, [RFC7437] did not provide for the IAOC to send a
   liaison to the Nominating Committee.

Dawkins                   Expires March 6, 2018                 [Page 2]
Internet-Draft           IAOC Advisor for Nomcom          September 2017

   This was not thought to be an obstacle, because [RFC7437] allowed any
   committee member to propose a liaison from the IAOC:

      Any committee member may propose the addition of a liaison from
      other unrepresented organizations to participate in some or all of
      the deliberations of the committee.  The addition must be approved
      by the committee according to its established voting mechanism.
Show full document text