< draft-hartman-mailinglist-experiment-02.txt		draft-hartman-mailinglist-experiment-03.txt >
	Network Working Group S. Hartman		Network Working Group S. Hartman
	Internet-Draft MIT		Internet-Draft MIT
	Expires: November 9, 2006 May 8, 2006		Expires: November 17, 2006 May 16, 2006
	Experimental Procedure for Long Term Suspensions from Mailing Lists		Experimental Procedure for Long Term Suspensions from Mailing Lists
	draft-hartman-mailinglist-experiment-02.txt		draft-hartman-mailinglist-experiment-03.txt
	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 33 ¶
	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 November 9, 2006.		This Internet-Draft will expire on November 17, 2006.
	Copyright Notice		Copyright Notice
	Copyright (C) The Internet Society (2006).		Copyright (C) The Internet Society (2006).
	Abstract		Abstract
	Discussion in the community has begun to question whether RFC 3683		Discussion in the community has begun to question whether RFC 3683
	and RFC 3934 provide the appropriate flexibility for managing IETF		and RFC 3934 provide the appropriate flexibility for managing IETF
	mailing lists. This document is an RFC 3933 experiment designed to		mailing lists. This document is an RFC 3933 experiment designed to
	skipping to change at page 3, line 27 ¶		skipping to change at page 3, line 27 ¶
	individual for an indefinite time period from one list. This		individual for an indefinite time period from one list. This
	suspension can expand to any IETF list without community or IESG		suspension can expand to any IETF list without community or IESG
	involvement. This memo is an RFC 3933[RFC3933] experiment to provide		involvement. This memo is an RFC 3933[RFC3933] experiment to provide
	the IESG with the ability to create additional mechanisms to manage		the IESG with the ability to create additional mechanisms to manage
	IETF mailing lists while the community decides what mailing list		IETF mailing lists while the community decides what mailing list
	guidelines are appropriate. IN particular this experiment allows the		guidelines are appropriate. IN particular this experiment allows the
	IESG to create a level of sanction between RFC 3934 and RFC 3683 for		IESG to create a level of sanction between RFC 3934 and RFC 3683 for
	working group lists and create sanctions other than RFC 3683 for		working group lists and create sanctions other than RFC 3683 for
	non-working-group lists. The goal of this experiment is to improve		non-working-group lists. The goal of this experiment is to improve
	the functioning of IETF mailing lists while keeping the process open		the functioning of IETF mailing lists while keeping the process open
	and fair.		and fair. This experiment is successful if it gives the community
			useful input on how to design mailing list management process. It is
			not expected that this experiment will be adopted in its current form
			as a permanent BCP.
	2. Requirements notation		2. Requirements notation
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this		"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
	document are to be interpreted as described in [RFC2119].		document are to be interpreted as described in [RFC2119].
	3. Definition of IETF Mailing List		3. Definition of IETF Mailing List
	This experiment applies to all IETF mailing lists, including those		This experiment applies to all IETF mailing lists, including those
	skipping to change at page 6, line 25 ¶		skipping to change at page 6, line 25 ¶
	The procedures of this memo MUST NOT be used to suspend the posting		The procedures of this memo MUST NOT be used to suspend the posting
	rights of an individual beyond the period of the experiment. The		rights of an individual beyond the period of the experiment. The
	procedures of this memo MUST NOT be used to limit an individual's		procedures of this memo MUST NOT be used to limit an individual's
	ability to read the contents of a mailing list.		ability to read the contents of a mailing list.
	The IESG MUST inform the community in a public statement of any		The IESG MUST inform the community in a public statement of any
	procedures for mailing list management approved under this		procedures for mailing list management approved under this
	experiment. Such a statement should include the description of the		experiment. Such a statement should include the description of the
	procedure and the description of mailing lists to which it applies or		procedure and the description of mailing lists to which it applies or
	an indication that it applies to all IETF mailing lists. The IESG is		an indication that it applies to all IETF mailing lists. The IESG
	encouraged to last call procedures it is considering approving under		MUST make a public announcement of a new procedure at least 14 days
	this experiment. While such last calls are encouraged, they are not		prior to the procedure taking effect. While the community is
	required. The reason that the last call is not required is that		encouraged to comment on any IESG action, community consensus is not
	under RFC 2418, no last call is required; there seems to be no reason		required to approve such a procedure. All currently active
	to have a procedure more strict than that proposed in RFC 2418.		procedures under this experiment MUST be made public in an
			appropriate, easy-to-find location.
	Sanctions made under this memo may be appealed using the procedures		Sanctions made under this memo may be appealed using the procedures
	outlined in [RFC2026].		outlined in [RFC2026].
	5. How the Experiment may be Used (Informative)		5. How the Experiment may be Used (Informative)
	The IESG could approve a procedure allowing it to suspend an		The IESG could approve a procedure allowing it to suspend an
	individual from one or more mailing lists for a fixed period of time		individual from one or more mailing lists for a fixed period of time
	greater than 30 days.		greater than 30 days.
End of changes. 5 change blocks.
	10 lines changed or deleted		14 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/