< draft-davies-pesci-initial-considerations-02.txt		draft-davies-pesci-initial-considerations-03.txt >
	Network Working Group E. Davies, Ed.		Network Working Group E. Davies, Ed.
	Internet-Draft Folly Consulting		Internet-Draft Folly Consulting
	Expires: December 15, 2006 June 13, 2006		Intended status: Informational October 23, 2006
			Expires: April 26, 2007
	Moving Forwards with IETF Process Evolution		Moving Forwards with IETF Process Evolution
	draft-davies-pesci-initial-considerations-02		draft-davies-pesci-initial-considerations-03
	Status of this Memo		Status of this Memo
	By submitting this Internet-Draft, each author represents that any		By submitting this Internet-Draft, each author represents that any
	applicable patent or other IPR claims of which he or she is aware		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		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.		aware will be disclosed, in accordance with Section 6 of BCP 79.
	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		Task Force (IETF), its areas, and its working groups. Note that
	skipping to change at page 1, line 33 ¶		skipping to change at page 1, line 34 ¶
	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		The list of current Internet-Drafts can be accessed at
	http://www.ietf.org/ietf/1id-abstracts.txt.		http://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 December 15, 2006.		This Internet-Draft will expire on April 26, 2007.
	Copyright Notice		Copyright Notice
	Copyright (C) The Internet Society (2006).		Copyright (C) The Internet Society (2006).
	Abstract		Abstract
	This document provides a summary of previously identified problems		This document provides a summary of previously identified problems
	with the Internet Engineering Task Force (IETF) process for		with the Internet Engineering Task Force (IETF) process for
	developing standards and other specifications; and then identifies a		developing standards and other specifications; and then identifies a
	skipping to change at page 2, line 22 ¶		skipping to change at page 2, line 22 ¶
	3. Short problem analysis . . . . . . . . . . . . . . . . . . . . 6		3. Short problem analysis . . . . . . . . . . . . . . . . . . . . 6
	4. Goals and Guidelines for IETF Process Change Activities . . . 7		4. Goals and Guidelines for IETF Process Change Activities . . . 7
	4.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . . . 8		4.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . . . 8
	4.2. Guidelines for Process Change Activities . . . . . . . . . 8		4.2. Guidelines for Process Change Activities . . . . . . . . . 8
	5. Next Steps . . . . . . . . . . . . . . . . . . . . . . . . . . 9		5. Next Steps . . . . . . . . . . . . . . . . . . . . . . . . . . 9
	6. Security Considerations . . . . . . . . . . . . . . . . . . . 9		6. Security Considerations . . . . . . . . . . . . . . . . . . . 9
	7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9		7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
	8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 10		8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 10
	9. Informative References . . . . . . . . . . . . . . . . . . . . 10		9. Informative References . . . . . . . . . . . . . . . . . . . . 10
	Appendix A. PESCI Announcement . . . . . . . . . . . . . . . . . 11		Appendix A. PESCI Announcement . . . . . . . . . . . . . . . . . 11
	Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 14		Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 13
	Intellectual Property and Copyright Statements . . . . . . . . . . 15		Intellectual Property and Copyright Statements . . . . . . . . . . 15
	1. Introduction		1. Introduction
	This document provides a summary of previously identified problems		This document provides a summary of previously identified problems
	with the Internet Engineering Task Force (IETF) process for		with the Internet Engineering Task Force (IETF) process for
	developing standards and other specifications (referred to as the		developing standards and other specifications (referred to as the
	IETF standards development process in this document); and then		IETF standards development process in this document); and then
	identifies a set of goals to aim at, and guidelines that should be		identifies a set of goals to aim at, and guidelines that should be
	followed during any activity seeking to revise and update this		followed during any activity seeking to revise and update this
	process. It also provides a reading list of the diverse material		process. It also provides a reading list of the diverse material
	that currently defines and discusses the various parts of this		that currently defines and discusses the various parts of this
	process. It does not propose specific changes to the process, which		process. It does not propose specific changes to the process, which
	should be the subject of future documents. It has been produced by a		should be the subject of future documents. It has been produced by a
	design team (the PESCI design team) selected by the IETF Chair and is		design team (the PESCI design team) selected by the IETF Chair and is
	submitted to the IETF community for discussion, modification, and		submitted to the IETF community for discussion.
	hopefully approval.
	The IETF almost continually debates its own process and this is in		The IETF almost continually debates its own process and this is in
	many ways a healthy sign of its openness. However, the debate is		many ways a healthy sign of its openness. However, the debate is
	often inconclusive. The goals and guidelines set out in this		often inconclusive. The goals and guidelines set out in this
	document represent an application of the IETF's Principles on		document represent an application of the IETF's Principles on
	specification development and decision making appropriate to making		specification development and decision making appropriate to making
	changes to the IETF standards development process.		changes to the IETF standards development process.
	1.1. Guidelines and Goals		1.1. Guidelines and Goals
	skipping to change at page 5, line 26 ¶		skipping to change at page 5, line 21 ¶
	This document was produced by the PESCI design team selected by the		This document was produced by the PESCI design team selected by the
	IETF Chair and is published here as a record of discussion. PESCI		IETF Chair and is published here as a record of discussion. PESCI
	stands for Process Evolution Committee of the IETF and is in the		stands for Process Evolution Committee of the IETF and is in the
	IETF's naming tradition as a successor of the earlier POISSON working		IETF's naming tradition as a successor of the earlier POISSON working
	group. The membership of the design team is listed in the		group. The membership of the design team is listed in the
	Acknowledgements and the original announcement of PESCI is given as		Acknowledgements and the original announcement of PESCI is given as
	an Appendix. PESCI had no special status in the IETF process; it was		an Appendix. PESCI had no special status in the IETF process; it was
	simply the group of people who produced this document under the		simply the group of people who produced this document under the
	leadership of the IETF Chair.		leadership of the IETF Chair.
	Discussion of this draft is welcomed on the pesci-discuss@ietf.org
	list (join via https://www1.ietf.org/mailman/listinfo/pesci-discuss).
	2. Background reading		2. Background reading
	The primary objective of the IETF process is to support the IETF		The primary objective of the IETF process is to support the IETF
	Mission Statement, [RFC3935]. Readers should be familiar with that		Mission Statement, [RFC3935]. Readers should be familiar with that
	document.		document.
	The early phase of the current round of process discussions led to a		The early phase of the current round of process discussions led to a
	problem statement [RFC3774]. A general overview of current and draft		problem statement [RFC3774]. A general overview of current and draft
	process documents can be found in [I-D.carpenter-procdoc-roadmap].		process documents can be found in [I-D.carpenter-procdoc-roadmap].
	At the time of writing, two process related working groups exist:		At the time of writing, two process related working groups exist:
	skipping to change at page 8, line 23 ¶		skipping to change at page 8, line 18 ¶
	process needs to have a well-defined aim of ameliorating some part of		process needs to have a well-defined aim of ameliorating some part of
	the problems set out in Section 3 or identified subsequently. The		the problems set out in Section 3 or identified subsequently. The
	activity should also aim to satisfy a number of goals identified here		activity should also aim to satisfy a number of goals identified here
	that should allow the changes to provide maximum improvement with		that should allow the changes to provide maximum improvement with
	minimum disruption.		minimum disruption.
	When designing new processes, it should be borne in mind that process		When designing new processes, it should be borne in mind that process
	changes that require major structural changes within the IETF may		changes that require major structural changes within the IETF may
	have wide-scale impact on the operation of the IETF: evolutionary		have wide-scale impact on the operation of the IETF: evolutionary
	change may be more effective than revolutionary change.		change may be more effective than revolutionary change.
	G1. Ameliorate a well-defined part of the process problem space.		G1. Ameliorate a well-defined part of the process problem space.
	G2. Preserve those parts of the process that work reasonably well		G2. Preserve those parts of the process that work reasonably well
	today, unless they block other necessary changes.		today, unless they block other necessary changes.
	G3. Make changes that seem certain to improve those parts of the		G3. Make changes that seem certain to improve those parts of the
	process that work less well.		process that work less well.
	G4. Avoid changes that would require unrealistic resources or		G4. Avoid changes that would require unrealistic resources or
	behaviours.		behaviours.
	G5. Protect the continuity of ongoing IETF work.		G5. Protect the continuity of ongoing IETF work.
	G6. As far as possible, minimize simultaneous changes that may		G6. As far as possible, minimize simultaneous changes that may
	interfere with each other.		interfere with each other.
	G7. Avoid "thrashing" by repeated changes in the same area.		G7. Avoid "thrashing" by repeated changes in the same area.
	G8. Try to explicitly estimate the impact of changes before making		G8. Try to explicitly estimate the impact of changes before making
	them, and try to measure whether the expectations were met after		them, and try to measure whether the expectations were met after
	making the change.		making the change.
	G9. Acknowledge that some refinement of the initial proposals may be		G9. Acknowledge that some refinement of the initial proposals may be
	needed after trials. To this end try to work expeditiously to		needed after trials. To this end try to work expeditiously to
	provide a nearly right solution that delivers most of the gains		provide a nearly right solution that delivers most of the gains
	rather than refining the solutions endlessly before any		rather than refining the solutions endlessly before any
	implementation (in line with the IETF's usual way of developing		implementation (in line with the IETF's usual way of developing
	standards).		standards).
	4.2. Guidelines for Process Change Activities		4.2. Guidelines for Process Change Activities
	Any activity for developing, approving and implementing changes to		Any activity for developing, approving and implementing changes to
	IETF standards development process needs to operate in line with the		IETF standards development process needs to operate in line with the
	general principles of the IETF. This section presents a number of		general principles of the IETF. This section presents a number of
	guidelines developed from these principles that should apply to any		guidelines developed from these principles that should apply to any
	such activity. They deal with how any proposed changes to the IETF		such activity. They deal with how any proposed changes to the IETF
	processes for developing standards and other specifications should be		processes for developing standards and other specifications should be
	developed and authorized by the IETF community. These guidelines		developed and authorized by the IETF community. These guidelines
	appear to be broadly in line with our current process for development		appear to be broadly in line with our current process for development
	activities, and similar principles should be true of any future		activities, and similar principles should be true of any future
	process.		process.
	P1. Changes to the IETF process must themselves be agreed by an open		P1. Changes to the IETF process must themselves be agreed by an open
	process approved by the IETF community.		process approved by the IETF community.
	P2. The process for developing and agreeing these changed processes		P2. The process for developing and agreeing these changed processes
	must itself be the subject of IETF rough consensus.		must itself be the subject of IETF rough consensus.
	P3. The development process must incorporate taking advice from		P3. The development process must incorporate taking advice from
	* the IESG, the IAB, the IAOC, and the Working Group chairs		* the IESG, the IAB, the IAOC, and the Working Group chairs
	* legal advisors		* legal advisors
	P4. When the proposed changes have been fully documented, "buy-in" or		P4. When the proposed changes have been fully documented, "buy-in"
	more formal assent to the changed processes needs to be obtained		or more formal assent to the changed processes needs to be
	as follows:		obtained as follows:
	* Any negative comments from the Working Group chairs must be		* Any negative comments from the Working Group chairs must be
	seriously considered.		seriously considered.
	* Formal consent must be obtained from the IESG, the IAB, and		* Formal consent must be obtained from the IESG, the IAB, and
	the IAOC.		the IAOC.
	* Acceptance must be obtained from the ISOC board.		* Acceptance must be obtained from the ISOC board.
	P5. The development and authorisation of the changed processes must		P5. The development and authorisation of the changed processes must
	ensure that the IESG is not required itself to develop the new		ensure that the IESG is not required itself to develop the new
	processes.		processes.
	5. Next Steps		5. Next Steps
	The remit of the PESCI design team did not extend to determining what		The remit of the PESCI design team did not extend to determining what
	IETF standards development process activities should be undertaken.		IETF standards development process activities should be undertaken.
	However the team encourages members of the community to produce		However the team encourages members of the community to produce
	proposals for such activities in line with the above goals and		proposals for such activities in line with the above goals and
	guidelines.		guidelines.
	6. Security Considerations		6. Security Considerations
	skipping to change at page 10, line 25 ¶		skipping to change at page 10, line 23 ¶
	Elwyn Davies		Elwyn Davies
	Adrian Farrel		Adrian Farrel
	Michael Richardson		Michael Richardson
	This document was produced using the xml2rfc tool[RFC2629] and edited		This document was produced using the xml2rfc tool[RFC2629] and edited
	with the xxe editor plug-in.		with the xxe editor plug-in.
	9. Informative References		9. Informative References
	[I-D.carpenter-procdoc-roadmap]		[I-D.carpenter-procdoc-roadmap]
	Carpenter, B., "The IETF Process: a Roadmap",		Carpenter, B., "The IETF Process: an Informal Guide",
	draft-carpenter-procdoc-roadmap-04 (work in progress),		draft-carpenter-procdoc-roadmap-05 (work in progress),
	February 2006.		August 2006.
	[RFC2014] Weinrib, A. and J. Postel, "IRTF Research Group Guidelines		[RFC2014] Weinrib, A. and J. Postel, "IRTF Research Group Guidelines
	and Procedures", BCP 8, RFC 2014, October 1996.		and Procedures", BCP 8, RFC 2014, October 1996.
	[RFC2026] Bradner, S., "The Internet Standards Process -- Revision		[RFC2026] Bradner, S., "The Internet Standards Process -- Revision
	3", BCP 9, RFC 2026, October 1996.		3", BCP 9, RFC 2026, October 1996.
	[RFC2028] Hovey, R. and S. Bradner, "The Organizations Involved in		[RFC2028] Hovey, R. and S. Bradner, "The Organizations Involved in
	the IETF Standards Process", BCP 11, RFC 2028,		the IETF Standards Process", BCP 11, RFC 2028,
	October 1996.		October 1996.
	skipping to change at page 15, line 5 ¶		skipping to change at page 15, line 5 ¶
	Elwyn Davies (editor)		Elwyn Davies (editor)
	Folly Consulting		Folly Consulting
	Soham,		Soham,
	UK		UK
	Phone: +44 7889 488 335		Phone: +44 7889 488 335
	Fax:		Fax:
	Email: elwynd@dial.pipex.com		Email: elwynd@dial.pipex.com
	URI:		URI:
	Intellectual Property Statement		Full Copyright Statement
			Copyright (C) The Internet Society (2006).
			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 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		The IETF takes no position regarding the validity or scope of any
	Intellectual Property Rights or other rights that might be claimed to		Intellectual Property Rights or other rights that might be claimed to
	pertain to the implementation or use of the technology described in		pertain to the implementation or use of the technology described in
	this document or the extent to which any license under such rights		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		might or might not be available; nor does it represent that it has
	made any independent effort to identify any such rights. Information		made any independent effort to identify any such rights. Information
	on the procedures with respect to rights in RFC documents can be		on the procedures with respect to rights in RFC documents can be
	found in BCP 78 and BCP 79.		found in BCP 78 and BCP 79.
	skipping to change at page 15, line 29 ¶		skipping to change at page 15, line 45 ¶
	such proprietary rights by implementers or users of this		such proprietary rights by implementers or users of this
	specification can be obtained from the IETF on-line IPR repository at		specification can be obtained from the IETF on-line IPR repository at
	http://www.ietf.org/ipr.		http://www.ietf.org/ipr.
	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 that may cover technology that may be required to implement		rights that may cover technology that may be required to implement
	this standard. Please address the information to the IETF at		this standard. Please address the information to the IETF at
	ietf-ipr@ietf.org.		ietf-ipr@ietf.org.
	Disclaimer of Validity
	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 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.
	Copyright Statement
	Copyright (C) The Internet Society (2006). 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.
	Acknowledgment		Acknowledgment
	Funding for the RFC Editor function is currently provided by the		Funding for the RFC Editor function is provided by the IETF
	Internet Society.		Administrative Support Activity (IASA).
End of changes. 12 change blocks.
	67 lines changed or deleted		64 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/