< draft-ietf-problem-process-03.txt   draft-ietf-problem-process-04.txt >
Problem Statement E. Davies, Ed. Problem Statement E. Davies, Ed.
Internet-Draft Nortel Networks Internet-Draft Nortel Networks
Expires: April 25, 2004 J. Hofmann, Ed. Expires: July 9, 2004 J. Hofmann, Ed.
Wissenschaftszentrum Berlin Wissenschaftszentrum Berlin
October 26, 2003 January 9, 2004
IETF Problem Resolution Process IETF Problem Resolution Process
draft-ietf-problem-process-03.txt draft-ietf-problem-process-04.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that other Task Force (IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet-Drafts. groups may also distribute working documents as Internet-Drafts.
skipping to change at page 1, line 32 skipping to change at page 1, line 32
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."
The list of current Internet-Drafts can be accessed at http:// The list of current Internet-Drafts can be accessed at http://
www.ietf.org/ietf/1id-abstracts.txt. www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on April 25, 2004. This Internet-Draft will expire on July 9, 2004.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2004). All Rights Reserved.
Abstract Abstract
This document suggests processes to address some of the problems This document suggests processes to address some of the problems
identified in the IETF Problem Statement. identified in the IETF Problem Statement.
This document decomposes each of the problems described in the This document decomposes each of the problems described in the
problem statement into a few areas for improvement, categorizes them problem statement into a few areas for improvement, categorizes them
either as problems affecting the routine processes used to create either as problems affecting the routine processes used to create
standards or problems affecting the fundamental structure and standards or problems affecting the fundamental structure and
practices of the IETF, and suggests ways to address the problems with practices of the IETF, and suggests ways to address the problems with
the routine processes that can be implemented as soon as possible the routine processes that can be implemented as soon as possible
without disrupting other areas of the IETF processes. without disrupting other areas of the IETF processes.
A number of ways to handle development of solutions for the structure A number of ways to handle development of solutions for the structure
and practices problems have been proposed in previous versions of and practices problems have been proposed in Internet drafts, on the
this draft, on the 'problems' mailing list and at an IETF 57 plenary Problems WG mailing list and at an IETF 57 plenary session in Vienna
session in Vienna during July 2003. This draft lists the various during July 2003. This draft lists the various solutions that have
solutions that have been proposed but neither the working group nor been proposed but neither the working group nor the wider IETF has
the wider IETF has reached consensus on a recommendation for any of reached consensus on a recommendation for any of the proposals.
the proposals.
In this situation, this draft has no alternative but to suggest that In this situation, this draft has no alternative but to suggest that
the search for structure and practices solutions is handed back to the search for structure and practices solutions is handed back to
the control of the IESG. the control of the IESG.
Status of the Content of this Memo
This Informational memo is being released to record the history of
discussions by the Problem WG in 2003. While there was working group
consensus on the portions of the document describing processes for
short-term and medium term improvements, there was no working group
consensus on the proposals for longer-term improvements. Those are
included in the document as a matter of record but must not be
regarded as recommendations from the working group.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 3 1.1 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4
1.2 Major Changes between Versions 01 and 02 . . . . . . . . . . 4 1.2 Major Changes between Versions 01 and 02 . . . . . . . . . . 5
1.3 Major Changes between Versions 02 and 03 . . . . . . . . . . 4 1.3 Major Changes between Versions 02 and 03 . . . . . . . . . . 5
2. IETF Purpose and Core Values . . . . . . . . . . . . . . . . 5 1.4 Changes between Versions 03 and 04 . . . . . . . . . . . . . 6
2.1 Non-Core Values . . . . . . . . . . . . . . . . . . . . . . 5 2. IETF Purpose and Core Values . . . . . . . . . . . . . . . . 6
3. Building on our Success . . . . . . . . . . . . . . . . . . 6 2.1 Non-Core Values . . . . . . . . . . . . . . . . . . . . . . 6
4. Problem Decomposition . . . . . . . . . . . . . . . . . . . 7 3. Building on our Success . . . . . . . . . . . . . . . . . . 7
4.1 Decomposition of Mission Problem . . . . . . . . . . . . . . 7 4. Problem Decomposition . . . . . . . . . . . . . . . . . . . 8
4.2 Decomposition of the Engineering Practices Problem . . . . . 8 4.1 Decomposition of Mission Problem . . . . . . . . . . . . . . 9
4.3 Decomposition of the Complex Problems Problem . . . . . . . 9 4.2 Decomposition of the Engineering Practices Problem . . . . . 9
4.4 Decomposition of the Standards Hierarchy Problem . . . . . . 9 4.3 Decomposition of the Complex Problems Problem . . . . . . . 10
4.5 Decomposition of the Engagement Problem . . . . . . . . . . 10 4.4 Decomposition of the Standards Hierarchy Problem . . . . . . 10
4.6 Decomposition of the Management Scaling Problem . . . . . . 10 4.5 Decomposition of the Engagement Problem . . . . . . . . . . 11
4.7 Decomposition of the Working Group Practices Problem . . . . 12 4.6 Decomposition of the Management Scaling Problem . . . . . . 12
4.8 Decomposition of the Preparedness Problem . . . . . . . . . 12 4.7 Decomposition of the Working Group Practices Problem . . . . 13
5. Process Recommendations . . . . . . . . . . . . . . . . . . 12 4.8 Decomposition of the Preparedness Problem . . . . . . . . . 13
5.1 Improvements to Routine Processes . . . . . . . . . . . . . 13 5. Process Recommendations . . . . . . . . . . . . . . . . . . 14
5.1.1 Suggestions to Improve WG Quality Processes . . . . . . . . 14 5.1 Improvements to Routine Processes . . . . . . . . . . . . . 14
5.1.2 Suggestions to Increase the Use of Tools . . . . . . . . . . 15 5.1.1 Suggestions to Improve WG Quality Processes . . . . . . . . 16
5.1.3 Suggestions to Improve Training . . . . . . . . . . . . . . 15 5.1.2 Suggestions to Increase the Use of Tools . . . . . . . . . . 16
5.1.4 Suggestions to Increase WG Chair Communication . . . . . . . 15 5.1.3 Suggestions to Improve Training . . . . . . . . . . . . . . 16
5.1.5 Suggestions to Improve Maintenance of Standards . . . . . . 16 5.1.4 Suggestions to Increase WG Chair Communication . . . . . . . 16
5.2 Changing the Structure and Practices of the IETF . . . . . . 16 5.1.5 Suggestions to Improve Maintenance of Standards . . . . . . 17
6. Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . 18 5.2 Changing the Structure and Practices of the IETF . . . . . . 17
7. Security Considerations . . . . . . . . . . . . . . . . . . 18 6. Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . 19
Normative References . . . . . . . . . . . . . . . . . . . . 19 7. Security Considerations . . . . . . . . . . . . . . . . . . 20
Informative References . . . . . . . . . . . . . . . . . . . 19 Normative References . . . . . . . . . . . . . . . . . . . . 20
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 20 Informative References . . . . . . . . . . . . . . . . . . . 20
Intellectual Property and Copyright Statements . . . . . . . 21 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 21
Intellectual Property and Copyright Statements . . . . . . . 22
1. Introduction 1. Introduction
This document suggests processes to address several problems facing This document suggests processes to address several problems facing
the Internet Engineering Task Force (IETF) that have been described the Internet Engineering Task Force (IETF) that have been described
in the IETF Problem Statement [1]. in the IETF Problem Statement [1].
This document begins with an outline of what are currently thought to This document begins with an outline of what are currently thought to
be the purpose and core values of the IETF, and it offers a reminder be the purpose and core values of the IETF, and it offers a reminder
of the good things about the IETF that we don't want to lose in the of the good things about the IETF that we don't want to lose in the
skipping to change at page 5, line 5 skipping to change at page 6, line 5
appropriate to emphasize that immediate action can be taken. appropriate to emphasize that immediate action can be taken.
1.3 Major Changes between Versions 02 and 03 1.3 Major Changes between Versions 02 and 03
The draft now lists the various suggestions that have been floated as The draft now lists the various suggestions that have been floated as
ways forward for the structural changes problems, documents the ways forward for the structural changes problems, documents the
inability of the community to achieve consensus around any of these inability of the community to achieve consensus around any of these
proposals and suggests that the problem is remitted to the control of proposals and suggests that the problem is remitted to the control of
the IESG. the IESG.
1.4 Changes between Versions 03 and 04
Added note to head matter indicating the status of the content of the
draft. Modified the abstract slightly to avoid referring to this memo
as a draft.
2. IETF Purpose and Core Values 2. IETF Purpose and Core Values
As we consider how to address the problems with the IETF processes As we consider how to address the problems with the IETF processes
and organizational structure, it is important to keep in mind the and organizational structure, it is important to keep in mind the
things about the IETF that we don't want to change -- our sense of things about the IETF that we don't want to change -- our sense of
purpose, and the core values that give the IETF its unique identity. purpose, and the core values that give the IETF its unique identity.
At two IESG plenary meetings in 2002, the chair of the IETF, gave At two IESG plenary meetings in 2002, the chair of the IETF, gave
presentations outlining his view of the purpose and core values of presentations outlining his view of the purpose and core values of
the IETF which may serve as a useful basis for focusing on our the IETF which may serve as a useful basis for focusing on our
skipping to change at page 21, line 29 skipping to change at page 22, line 29
be obtained from the IETF Secretariat. be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF Executive
Director. Director.
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2004). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
 End of changes. 10 change blocks. 
42 lines changed or deleted 58 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/