< draft-iab-streams-headers-boilerplates-03.txt		draft-iab-streams-headers-boilerplates-04.txt >
	Network Working Group L. Daigle, Ed.		Network Working Group L. Daigle, Ed.
	Internet-Draft O. Kolkman, Ed.		Internet-Draft O. Kolkman, Ed.
	Updates: 4844, 2223		Updates: 4844, 2223
	(if approved) Internet Architecture Board		(if approved) Internet Architecture Board
	Intended status: Informational (IAB)		Intended status: Informational (IAB)
	Expires: April 23, 2009 October 20, 2008		Expires: May 29, 2009 November 25, 2008
	On RFC Streams, Headers, and Boilerplates		On RFC Streams, Headers, and Boilerplates
	draft-iab-streams-headers-boilerplates-03		draft-iab-streams-headers-boilerplates-04
	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 36 ¶		skipping to change at page 1, line 36 ¶
	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 April 23, 2009.		This Internet-Draft will expire on May 29, 2009.
	Abstract		Abstract
	RFC documents contain a number of fixed elements such as the title		RFC documents contain a number of fixed elements such as the title
	page header, standard boilerplates and copyright/IPR statements.		page header, standard boilerplates and copyright/IPR statements.
	This document describes them and introduces some updates to reflect		This document describes them and introduces some updates to reflect
	current usage and requirements of RFC publication. In particular,		current usage and requirements of RFC publication. In particular,
	this updated structure is intended to communicate clearly the source		this updated structure is intended to communicate clearly the source
	of RFC creation and review.		of RFC creation and review.
	skipping to change at page 2, line 26 ¶		skipping to change at page 2, line 26 ¶
	6. RFC Editor Considerations . . . . . . . . . . . . . . . . . . 9		6. RFC Editor Considerations . . . . . . . . . . . . . . . . . . 9
	7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10		7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10
	7.1. Normative References . . . . . . . . . . . . . . . . . . . 10		7.1. Normative References . . . . . . . . . . . . . . . . . . . 10
	7.2. Informative References . . . . . . . . . . . . . . . . . . 10		7.2. Informative References . . . . . . . . . . . . . . . . . . 10
	Appendix A. IAB members at time of approval . . . . . . . . . . . 11		Appendix A. IAB members at time of approval . . . . . . . . . . . 11
	Appendix B. Acknowledgements . . . . . . . . . . . . . . . . . . 11		Appendix B. Acknowledgements . . . . . . . . . . . . . . . . . . 11
	Appendix C. Document Editing Details . . . . . . . . . . . . . . 12		Appendix C. Document Editing Details . . . . . . . . . . . . . . 12
	C.1. version 00->01 . . . . . . . . . . . . . . . . . . . . . . 12		C.1. version 00->01 . . . . . . . . . . . . . . . . . . . . . . 12
	C.2. version 01->02 . . . . . . . . . . . . . . . . . . . . . . 13		C.2. version 01->02 . . . . . . . . . . . . . . . . . . . . . . 13
	C.3. version 02->03 . . . . . . . . . . . . . . . . . . . . . . 13		C.3. version 02->03 . . . . . . . . . . . . . . . . . . . . . . 13
			C.4. version 03->04 . . . . . . . . . . . . . . . . . . . . . . 13
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13
	Intellectual Property and Copyright Statements . . . . . . . . . . 14		Intellectual Property and Copyright Statements . . . . . . . . . . 14
	1. Introduction		1. Introduction
	Previously RFCs (e.g. [RFC4844]) contained a number of elements that		Previously RFCs (e.g. [RFC4844]) contained a number of elements that
	were there for historical, practical, and legal reasons. They also		were there for historical, practical, and legal reasons. They also
	contained boilerplate material to clearly indicate the status of the		contained boilerplate material to clearly indicate the status of the
	document and possibly contained "Notes" to indicate how the document		document and possibly contained "Notes" to indicate how the document
	interacts with IETF Standards-Track documents.		interacts with IETF Standards-Track documents.
	skipping to change at page 6, line 27 ¶		skipping to change at page 6, line 27 ¶
	an understanding of how to consider its content.		an understanding of how to consider its content.
	The first paragraph of the Status of this Memo section contains a		The first paragraph of the Status of this Memo section contains a
	single sentence, clearly standing out. It depends on the category of		single sentence, clearly standing out. It depends on the category of
	the document.		the document.
	This memo is an Internet Standards Track document.		This memo is an Internet Standards Track document.
	This memo documents an Internet Best Current Practice		This memo documents an Internet Best Current Practice
	This memo is not an Internet Standards Track specification, <it is		This memo is not an Internet Standards Track specification; <it is
	published for other purposes>.		published for other purposes>.
	For Informational, Experimental, Historic and future categories of		For Informational, Experimental, Historic and future categories of
	RFCs, the RFC editor will maintain an appropriate text for <it is		RFCs, the RFC editor will maintain an appropriate text for <it is
	published for other purposes>. For example, with an Informational		published for other purposes>. For example, with an Informational
	document this could read "it is published for informational		document this could read "it is published for informational
	purposes".		purposes".
	The second paragraph contains text as follows that is specific to the		The second paragraph contains text as follows that is specific to the
	initial category:		initial category:
	skipping to change at page 11, line 35 ¶		skipping to change at page 11, line 35 ¶
	[RFC3978]and[RFC4748]		[RFC3978]and[RFC4748]
	[BCP79] Bradner, S., Ed. and T. Narten, Ed., "Intellectual		[BCP79] Bradner, S., Ed. and T. Narten, Ed., "Intellectual
	Property Rights in IETF Technology", BCP 79, April 2007.		Property Rights in IETF Technology", BCP 79, April 2007.
	[RFC3979]and[RFC4749]		[RFC3979]and[RFC4749]
	[RFC-style]		[RFC-style]
	RFC Editor, "RFC Style Guide",		RFC Editor, "RFC Style Guide",
	<http://www.rfc-editor.org/howtopub.html>.		<http://www.rfc-editor.org/styleguide.html>.
	Appendix A. IAB members at time of approval		Appendix A. IAB members at time of approval
	The IAB members at the time this memo was approved were (in		The IAB members at the time this memo was approved were (in
	alphabetical order): Loa Andersson, Gonzalo Camarillo, Stuart		alphabetical order): Loa Andersson, Gonzalo Camarillo, Stuart
	Cheshire, Russ Housley, Olaf Kolkman, Gregory Lebovitz, Barry Leiba,		Cheshire, Russ Housley, Olaf Kolkman, Gregory Lebovitz, Barry Leiba,
	Kurtis Lindqvist, Andrew Malis, Danny McPherson, David Oran, Dave		Kurtis Lindqvist, Andrew Malis, Danny McPherson, David Oran, Dave
	Thaler, and Lixia Zhang. In addition, the IAB included two ex-		Thaler, and Lixia Zhang. In addition, the IAB included two ex-
	officio members: Dow Street, who was serving as the IAB Executive		officio members: Dow Street, who was serving as the IAB Executive
	Director, and Aaron Falk, who was serving as the IRTF Chair.		Director, and Aaron Falk, who was serving as the IRTF Chair.
	skipping to change at page 12, line 14 ¶		skipping to change at page 12, line 14 ¶
	Various people have made suggestions that improved the document.		Various people have made suggestions that improved the document.
	Among them are: Lars Eggert and Alfred Hoenes.		Among them are: Lars Eggert and Alfred Hoenes.
	This document was produced using the xml2rfc tool [RFC2629].		This document was produced using the xml2rfc tool [RFC2629].
	Appendix C. Document Editing Details		Appendix C. Document Editing Details
	[To Be Removed before publication]		[To Be Removed before publication]
	$Id: draft-iab-streams-headers-boilerplates-03.txt 49 2008-10-20 13:54:58Z olaf $		$Id: headers-boilerplates.xml 53 2008-11-25 14:16:08Z olaf $
	C.1. version 00->01		C.1. version 00->01
	Fixed the header so it appropriately shows that the document updates		Fixed the header so it appropriately shows that the document updates
	RFC 4844, 2223. And added a link to 3932-bis that should appear in		RFC 4844, 2223. And added a link to 3932-bis that should appear in
	tandem with this publication.		tandem with this publication.
	Introduced the "Other structural information in RFCs" section and		Introduced the "Other structural information in RFCs" section and
	moved the ISSN number from the front matter to this section. The		moved the ISSN number from the front matter to this section. The
	"Other structural information in RFCs" intends to give very rough		"Other structural information in RFCs" intends to give very rough
	skipping to change at page 13, line 27 ¶		skipping to change at page 13, line 27 ¶
	references may need to be done by the RFC editor.		references may need to be done by the RFC editor.
	Added text to recognize occurrences of variations of "Obsolete" and		Added text to recognize occurrences of variations of "Obsolete" and
	"Update"		"Update"
	C.3. version 02->03		C.3. version 02->03
	Stray language in the "IAB members at time of approval" section		Stray language in the "IAB members at time of approval" section
	removed.		removed.
			C.4. version 03->04
			Addressed the minor nit from Brian Carpenter.
			Reference to style guide stet to styleguide.html
	Authors' Addresses		Authors' Addresses
	Leslie Daigle (editor)		Leslie Daigle (editor)
	Email: daigle@isoc.org, leslie@thinkingcat.com		Email: daigle@isoc.org, leslie@thinkingcat.com
	Olaf M. Kolkman (editor)		Olaf M. Kolkman (editor)
	Email: olaf@nlnetlabs.nl		Email: olaf@nlnetlabs.nl
End of changes. 8 change blocks.
	6 lines changed or deleted		13 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/