Network Working Group L. Lynch (ed) Internet-Draft ISOC Updates: 2028, 2418, 3005, 3710, January 18, 2007 3777, 3929, 3979 (if approved) Intended status: Best Current Practice Expires: July 22, 2007 Tasks previously assigned to the IETF Executive Director draft-lynch-execd-tasks-00 Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. 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." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on July 22, 2007. Copyright Notice Copyright (C) The IETF Trust (2007). Abstract This document identifies jobs originally assigned to the IETF Executive Director in existing IETF processes, and in most cases re- assigns them formally to the IETF Secretariat. It updates RFC 2028, 2418, 3005, 3710, 3777, 3929, and 3979. Lynch (ed) Expires July 22, 2007 [Page 1]
Internet-Draft Tasks previously assigned to the ExecD January 2007 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Updated Task Assignments . . . . . . . . . . . . . . . . . . . 3 2.1. RFC2028: The Organizations Involved in the IETF Standards Process . . . . . . . . . . . . . . . . . . . . . 3 2.2. RFC2418: IETF Working Group Guidelines and Procedures . . . 4 2.3. RFC3005: IETF Discussion List Charter . . . . . . . . . . . 4 2.4. RFC3710: An IESG charter . . . . . . . . . . . . . . . . . 4 2.5. RFC3777: IAB and IESG Selection, Confirmation, and Recall Process . . . . . . . . . . . . . . . . . . . . . . 5 2.6. RFC3929: Alternative Decision Making Processes for Consensus-Blocked Decisions in the IETF . . . . . . . . . . 5 2.7. RFC3979: Intellectual Property Rights in IETF Technology . . . . . . . . . . . . . . . . . . . . . . . . 6 3. Security Considerations . . . . . . . . . . . . . . . . . . . . 6 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 7 6. Change log [RFC Editor: please remove this section] . . . . . . 7 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7 7.1. Normative References . . . . . . . . . . . . . . . . . . . 7 7.2. Informative References . . . . . . . . . . . . . . . . . . 8 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 8 Intellectual Property and Copyright Statements . . . . . . . . . . 9 Lynch (ed) Expires July 22, 2007 [Page 2]
Internet-Draft Tasks previously assigned to the ExecD January 2007 1. Introduction BCP 101 [RFC4071] requires the IETF Administrative Oversight Committee to "designate, in consultation with the IAB and the IESG, the person or people who carry out the tasks that other IETF process documents say are carried out by the IETF Executive Director." The purpose of this document is to document the agreed designations. The RFCs updated by this document are all those that have not already been obsoleted which assign tasks to the IETF Executive Director (sometimes abbreviated as ExecD). Note that there is no relationship to the IAB Executive Director. In general the tasks concerned are well defined and closely linked to other duties of the IETF Secretariat. Therefore, in what follows, almost all of them are re-assigned to the Secretariat. It is expected that they will normally be performed by the person occupying the role of Head of Secretariat. 2. Updated Task Assignments 2.1. RFC2028: The Organizations Involved in the IETF Standards Process Original text: 3.3 IETF Secretariat The administrative functions necessary to support the activities of the IETF are performed by a Secretariat consisting of the IETF Executive Director and his or her staff. The IETF Executive Director is the formal point of contact for matters concerning any and all aspects of the Internet standards process, and is responsible for maintaining the formal public record of the Internet standards process [B]. Replaced by: 3.3 IETF Secretariat The administrative functions necessary to support the activities of the IETF are performed by a Secretariat, which is the formal point of contact for matters concerning any and all aspects of the Internet standards process, and is responsible for maintaining the formal public record of the Internet standards process [B]. Lynch (ed) Expires July 22, 2007 [Page 3]
Internet-Draft Tasks previously assigned to the ExecD January 2007 2.2. RFC2418: IETF Working Group Guidelines and Procedures Original text The area directors sitting as a body, along with the IETF Chair, comprise the Internet Engineering Steering Group (IESG). The IETF Executive Director is an ex-officio participant of the IESG, as are the IAB Chair and a designated Internet Architecture Board (IAB) liaison. Replaced by: The area directors sitting as a body, along with the IETF Chair, comprise the Internet Engineering Steering Group (IESG). The IAB Chair and a designated Internet Architecture Board (IAB) liaison are ex-officio participants in the IESG. Secretariat staff participate in IESG business as needed. 2.3. RFC3005: IETF Discussion List Charter Original text The IETF Chair, the IETF Executive Director, or a sergeant-at-arms appointed by the Chair is empowered to restrict posting by a person, or of a thread, when the content is inappropriate and represents a pattern of abuse. In this case, the reference to the Executive Director is simply deleted. It is not appropriate to involve a staff person in posting rights decisions. 2.4. RFC3710: An IESG charter This is an Informational RFC. Original text: Lynch (ed) Expires July 22, 2007 [Page 4]
Internet-Draft Tasks previously assigned to the ExecD January 2007 2. The Composition of the IESG The IESG has the following members: o The IETF Chair, who also functions as the General Area Director when this area is active o The Area Directors (ADs) for the IETF Areas o The Internet Architecture Board (IAB) Chair and the IETF Executive Director, as ex-officio members of the IESG The IETF Chair and the Area Directors are selected by the IETF NomCom according to the procedures of BCP 10 [3] (Nomcom procedures). The IETF Executive Director is the person charged with running the IETF Secretariat. The references to the Executive Director are deleted. The final sentence becomes: Secretariat staff participate in IESG business as needed. 2.5. RFC3777: IAB and IESG Selection, Confirmation, and Recall Process Original text: 1. The IETF Executive Director informs the nominating committee of the IESG and IAB positions to be reviewed. The IESG and IAB are responsible for providing summary of the expertise desired of the candidates selected for their respective open positions to the Executive Director. Both occurrences of "Executive Director" are replaced by "Head of Secretariat." 2.6. RFC3929: Alternative Decision Making Processes for Consensus- Blocked Decisions in the IETF This is an Experimental RFC. Original text: Lynch (ed) Expires July 22, 2007 [Page 5]
Internet-Draft Tasks previously assigned to the ExecD January 2007 Volunteers to serve on the review team send their names to the IETF executive director. ... Each qualified volunteer sends her or his name to the working group chair and the IETF Executive Director within three weeks of the announcement sent to the IETF-announce mailing list. The IETF Executive Director then uses the selection procedures described in [RFC3797] to select a single volunteer from the list. The references to the Executive Director are replaced by the IETF Chair, who is free to delegate the actual selection procedure to an Area Director. 2.7. RFC3979: Intellectual Property Rights in IETF Technology Original text: (C) Where Intellectual Property Rights have been disclosed for IETF Documents as provided in Section 6 of this document, the IETF Executive Director shall request from the discloser of such IPR, a written assurance... The working group proposing the use of the technology with respect to which the Intellectual Property Rights are disclosed may assist the IETF Executive Director in this effort. ... The results will, however, be recorded by the IETF Executive Director,... ... 6.4.2. If a disclosure was made on the basis of a patent application (either published or unpublished), then, if requested to do so by the IESG or by a working group chair, the IETF Executive Director can request a new disclosure All four occurrences of "Executive Director" are replaced by "Head of Secretariat." 3. Security Considerations This document is not believed to affect the security of the Internet. 4. IANA Considerations This document requests no IANA actions. Lynch (ed) Expires July 22, 2007 [Page 6]
Internet-Draft Tasks previously assigned to the ExecD January 2007 5. Acknowledgements This document was developed by the IETF Administrative Oversight Committee. Its members at the time of writing were: Lucy Lynch (Chair) Kurtis Lindqvist Fred Baker Brian Carpenter Leslie Daigle Lynn St.Amour Jonne Soininen Ed Juskevicius Ray Pelletier, IETF Administrative Director Helpful comments were received from Ted Hardie. This document was produced using the xml2rfc tool [RFC2629]. 6. Change log [RFC Editor: please remove this section] draft-lynch-execd-tasks-00: original version, 2007-01-18. 7. References 7.1. Normative References [RFC2028] Hovey, R. and S. Bradner, "The Organizations Involved in the IETF Standards Process", BCP 11, RFC 2028, October 1996. [RFC2418] Bradner, S., "IETF Working Group Guidelines and Procedures", BCP 25, RFC 2418, September 1998. [RFC3005] Harris, S., "IETF Discussion List Charter", BCP 45, RFC 3005, November 2000. [RFC3777] Galvin, J., "IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall Committees", BCP 10, RFC 3777, June 2004. [RFC3979] Bradner, S., "Intellectual Property Rights in IETF Technology", BCP 79, RFC 3979, March 2005. [RFC4071] Austein, R. and B. Wijnen, "Structure of the IETF Administrative Support Activity (IASA)", BCP 101, RFC 4071, April 2005. Lynch (ed) Expires July 22, 2007 [Page 7]
Internet-Draft Tasks previously assigned to the ExecD January 2007 7.2. Informative References [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, June 1999. [RFC3710] Alvestrand, H., "An IESG charter", RFC 3710, February 2004. [RFC3929] Hardie, T., "Alternative Decision Making Processes for Consensus-Blocked Decisions in the IETF", RFC 3929, October 2004. Author's Address Lucy Lynch (ed) Internet Society 1775 Wiehle Ave., Suite 102 Reston, Virginia, 20190 USA Phone: +1 703 326 9880 Email: llynch@civil-tongue.net Lynch (ed) Expires July 22, 2007 [Page 8]
Internet-Draft Tasks previously assigned to the ExecD January 2007 Full Copyright Statement Copyright (C) The IETF Trust (2007). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Intellectual Property The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org. Acknowledgment Funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA). Lynch (ed) Expires July 22, 2007 [Page 9]