< draft-hardie-iaoc-iab-update-00.txt   draft-hardie-iaoc-iab-update-01.txt >
Network Working Group T. Hardie Network Working Group T. Hardie
Internet-Draft Internet-Draft
Intended status: Best Current Practice A. Sullivan Updates: RFC4071 (if approved) A. Sullivan
Expires: August 5, 2016 Dyn Intended status: Best Current Practice Dyn
R. Housley Expires: August 8, 2016 R. Housley
Vigil Security Vigil Security
February 02, 2016 February 05, 2016
Updating the ex-officio member of the IAB in the IAOC Updating the ex officio member of the IAB in the IAOC
draft-hardie-iaoc-iab-update-00 draft-hardie-iaoc-iab-update-01
Abstract Abstract
At the time the IETF Administrative Oversight Committee was set up At the time the IETF Administrative Oversight Committee was set up
the Internet Architecture Board had an internal structure the Internet Architecture Board had an internal structure
significantly different from its current structure. This document significantly different from its current structure. This document
aims to update the ex officio member from the IAB who serves on the aims to update the way in which the ex officio member from the IAB
IAOC in order to better account for that change and better match the who serves on the IAOC is appointed, in order to better account for
skills set out in RFC 4333. that change and better match the skills set out in RFC 4333. After
community discussion, it is likely that this document will be split
into two distinct parts: one which updates the IAOC membership
section of the relevant BCP and another which describes the IAB's
program.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 5, 2016. This Internet-Draft will expire on August 8, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
1. Introduction 1. Introduction
At the time of the administrative restructuring of the IETF which At the time of the administrative restructuring of the IETF which
gave rise to the IAOC[RFC4071], the IAB made very little use of long- gave rise to the IAOC, the IAB made very little use of long-lived
lived programs. In part because of the adjustments to the RFC Editor programs. In part because of the adjustments to the RFC Editor
model[RFC6635], the IAB now makes extensive use of such programs, and model[RFC6635], the IAB now makes extensive use of such programs, and
the IAB structures much of its long-lived efforts as programs. This the IAB structures much of its long-lived efforts as programs. This
document proposes to set up one such program, and to have the IAB document proposes to set up one such program and to have the IAB
member that leads that program serve as the IAB's ex officio member member that leads that program serve as the IAB's ex officio member
of the IAOC instead of the IAB chair serving in this role. of the IAOC instead of the IAB chair serving in this role.
2. IAOC Review Program Structure 2. IAOC Review Program Structure
While many IAB programs include invited experts, the intent is for While many IAB programs include invited experts, the intent is for
this program to be composed of a small number of sitting IAB members, this program to be composed of a small number of sitting IAB members,
possibly including the Executive Director, if one has been appointed. possibly including the Executive Director, if one has been appointed.
The program members will be responsible to review all public The IAB shall designate one sitting IAB member to serve as program
correspondence of the IAOC to the community. This would include lead. The program lead shall act as the ex officio as a member of
reviews of requests for proposals at that point at which they are the IAOC, as the IAB chair did under Section 4 of [RFC4071].
made public, along with the public minutes of the IAOC meetings and
any other reports which the IAOC may be produced.
In addition, the IAB shall designate one sitting IAB member to serve Other program members will be available to advise the ex officio IAB
as program lead. The program lead shall act as the ex officio as a member of the IAOC, should the member request it. In order to
member of the IAOC, as the IAB chair does now. Other program members provide that advice, program members will keep up to date on all
are available to advise the ex officio IAB member of the IAOC, should public correspondence of the IAOC to the community. This will
the member request it. include reviewing public minutes of the IAOC meetings, any reports
produced by the IAOC, and any requests for proposals which have been
made public.
Note that the ex officio member also serves as a Trustee of the IETF Note that the ex officio member also serves as a Trustee of the IETF
Trust, since its members are defined as being the members of the Trust, since its members are defined as being the members of the
IAOC. IAOC.
3. Reasoning 3. Reasoning
While there are clearly advantages to having a single individual While there are clearly advantages to having a single individual
share state as IAB Chair, IESG member, and IAOC member, this also share state as IAB Chair, IESG member, and IAOC member, this also
weighs significantly on the time of the selected individual. Moving weighs significantly on the time of the selected individual. Moving
skipping to change at page 3, line 13 skipping to change at page 3, line 18
manage the work of the IAB, adapting it to this purpose seems a manage the work of the IAB, adapting it to this purpose seems a
logical approach to adjusting the current working methods. Having a logical approach to adjusting the current working methods. Having a
dedicated set of reviewers for RFPs, minutes, and other dedicated set of reviewers for RFPs, minutes, and other
correspondence will also increase the input provided to the IAOC and correspondence will also increase the input provided to the IAOC and
the understanding of that state in the IAB as a whole. the understanding of that state in the IAB as a whole.
This also allows the IAB to select from among its members the This also allows the IAB to select from among its members the
individual who best matches the criteria set out in IOAC member individual who best matches the criteria set out in IOAC member
selection guidelines[RFC4333] while simultaneously serving on one of selection guidelines[RFC4333] while simultaneously serving on one of
the IAOC's customer organizations. This might be a different person the IAOC's customer organizations. This might be a different person
than the person best able to carry the other duties of the IAB Chair. than the person best able to carry out the other duties of the IAB
Should it happen that the IAB Chair is also the best person to serve Chair. Should it happen that the IAB Chair is also the best person
on the IAOC, then the IAB Chair may serve as lead of the program. to serve on the IAOC, then the IAB Chair may serve as lead of the
program.
4. Security Considerations 4. Security Considerations
This document describes an administrative change rather than a This document describes an administrative change rather than a
protocol. There is a possibility that this administrative change protocol. There is a possibility that this administrative change
might result in less information flowing between the IAB and IAOC, might result in less information flowing between the IAB and IAOC,
but the existence of a larger program mitigates this risk. but the existence of a larger program mitigates this risk.
5. IANA Considerations 5. IANA Considerations
This document currently has no actions for IANA. This document currently has no actions for IANA.
6. Acknowledgements 6. Acknowledgements
Olaf Kolkman was kind enough to review and provide suggestions to an Olaf Kolkman was kind enough to review and provide suggestions to an
early version of this document. early version of this document. Lou Berger, Brian Carpenter, Leslie
Daigle, Martin Duerst, Bob Hinden, John Klensin, and Mike St. Johns
provided additional comments.
7. References 7. References
7.1. Normative References 7.1. Normative References
[RFC4071] Austein, R., Ed. and B. Wijnen, Ed., "Structure of the [RFC4071] Austein, R., Ed. and B. Wijnen, Ed., "Structure of the
IETF Administrative Support Activity (IASA)", BCP 101, IETF Administrative Support Activity (IASA)", BCP 101,
RFC 4071, DOI 10.17487/RFC4071, April 2005, RFC 4071, DOI 10.17487/RFC4071, April 2005,
<http://www.rfc-editor.org/info/rfc4071>. <http://www.rfc-editor.org/info/rfc4071>.
 End of changes. 11 change blocks. 
27 lines changed or deleted 34 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/