draft-ietf-ipr-3978-incoming-02.txt		draft-ietf-ipr-3978-incoming-03.txt
	Network Working Group S. Bradner		Network Working Group S. Bradner
	Internet-Draft Harvard University		Internet-Draft Harvard University
	Jorge Contreras		Jorge Contreras
	WilmerHale		WilmerHale
	Editors		Editors
	17 October 2007		13 November 2007
	Rights Contributors provide to the IETF Trust		Rights Contributors provide to the IETF Trust
	<draft-ietf-ipr-3978-incoming-02.txt>		<draft-ietf-ipr-3978-incoming-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
	other groups may also distribute working documents as Internet-		other groups may also distribute working documents as Internet-
	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 17, 2008.		This Internet-Draft will expire on May 13, 2008.
	Copyright (C) IETF Trust (2007).		Copyright (C) The IETF Trust (2007).
	Abstract		Abstract
	The IETF policies about rights in Contributions to the IETF are		The IETF policies about rights in Contributions to the IETF are
	designed to ensure that such Contributions can be made available to		designed to ensure that such Contributions can be made available to
	the IETF and Internet communities while permitting the authors to		the IETF and Internet communities while permitting the authors to
	retain as many rights as possible. This memo details the IETF		retain as many rights as possible. This memo details the IETF
	policies on rights in Contributions to the IETF. It also describes		policies on rights in Contributions to the IETF. It also describes
	the objectives that the policies are designed to meet. This memo		the objectives that the policies are designed to meet. This memo
	obsoletes RFC 3978 and 4748 and, with RFC 3979 and RFC xxx		obsoletes RFC 3978 and 4748 and, with RFC 3979 and RFC xxx
	(-outgoing), replaces Section 10 of RFC 2026.		(-outgoing), replaces Section 10 of RFC 2026.
	skipping to change at page 11, line 13		skipping to change at page 11, line 13
	hereby acknowledges that the copyright in any RFC in which such		hereby acknowledges that the copyright in any RFC in which such
	Contribution is included, other than an RFC that is an RFC Editor		Contribution is included, other than an RFC that is an RFC Editor
	Contribution, shall be owned by the IETF Trust. Such Contributor		Contribution, shall be owned by the IETF Trust. Such Contributor
	shall be deemed to assign to the IETF Trust such Contributor's		shall be deemed to assign to the IETF Trust such Contributor's
	copyright interest in the collective work constituting such RFC upon		copyright interest in the collective work constituting such RFC upon
	the submission of such RFC for publication, and acknowledges that a		the submission of such RFC for publication, and acknowledges that a
	copyright notice acknowledging the IETF Trust's ownership of the		copyright notice acknowledging the IETF Trust's ownership of the
	copyright in such RFC will be included in the published RFC.		copyright in such RFC will be included in the published RFC.
	5.10. Contributors retention of rights		5.10. Contributors retention of rights
	[THIS SECTION IS STILL UNDER DISCUSSION] Notwithstanding any terms in		Although contributors provide specific rights to the IETF, it is not
	this document to the contrary, in addition to any rights under		intended that this should deprive them of any rights in their
	copyright retained by Contributor and in addition to any rights		contributions. To underwrite this principle, the IETF Trust is
	generally granted by the IETF trust, Contributor retains, and grants		requested to issue a form of license to contributors which ensures
	to each Co-Contributor to an RFC in which such Contributor's		that they may each make use of their contributed material as
	Contribution, or a derivative work thereof may appear, the right:		published in an RFC in any way they wish, subject only to the
	(A) to copy, publish, display, and distribute any RFC that includes		restriction that no contributor has the right to represent any
	the Contribution, in whole or in part,		document as an RFC, or equivalent to an RFC, if it is not a full and
	(B) to prepare translations of such RFCs into languages other than		complete copy or translation of the published RFC.
	English, in whole or in part, and to copy, publish, display, and
	distribute such translations or portions thereof,
	(C) to make derivative works from such RFCs, and to copy, publish,
	display, and distribute such derivative works thereof, and
	(D) to reproduce any trademarks, service marks or trade names which
	are included in such RFCs solely in connection with the
	reproduction, distribution or publication of the RFC thereof as
	permitted by this Section 5.10, provided that when reproducing
	RFCs, trademark and service mark identifiers used in the RFC,
	including TM and (R), will be preserved.
	Notwithstanding the above rights, the Contributor does not have the
	right to represent any document as an RFC, or equivalent to an RFC,
	if it is not a full and complete copy or translation of the published
	RFC.
	6. Legends, Notices and Other Standardized Text in IETF Documents		6. Legends, Notices and Other Standardized Text in IETF Documents
	The IETF requires that certain standardized text be reproduced		The IETF requires that certain standardized text be reproduced
	verbatim in certain IETF Documents (including copies, derivative		verbatim in certain IETF Documents (including copies, derivative
	works and translations of IETF Documents). Some of this standardized		works and translations of IETF Documents). Some of this standardized
	text may be mandatory (e.g., copyright notices and disclaimers that		text may be mandatory (e.g., copyright notices and disclaimers that
	must be included in all RFCs) and some may be optional (e.g.,		must be included in all RFCs) and some may be optional (e.g.,
	limitations on the right to make derivative works). The text itself,		limitations on the right to make derivative works). The text itself,
	as well as the rules that explain when and how it must be used, are		as well as the rules that explain when and how it must be used, are
	contained in the Legend Instructions. The Legend Instructions may be		contained in the Legend Instructions. The Legend Instructions may be
	skipping to change at page 13, line 19		skipping to change at page 13, line 6
	EMail: sob@harvard.edu		EMail: sob@harvard.edu
	Jorge L. Contreras		Jorge L. Contreras
	WilmerHale		WilmerHale
	1875 Pennsylvania Avenue NW		1875 Pennsylvania Avenue NW
	Washington, DC 20006 USA		Washington, DC 20006 USA
	Phone: +1 202 663 6872		Phone: +1 202 663 6872
	Email: jorge.contreras@wilmerhale.com		Email: jorge.contreras@wilmerhale.com
	Full Copyright Statement		Full Copyright Statement
	Copyright (C) IETF Trust (2007). This document is subject to the		Copyright (C) The IETF Trust (2007). This document is subject to the
	rights, licenses and restrictions contained in BCP 78, and except as		rights, licenses and restrictions contained in BCP 78, and except as
	set forth therein, the authors retain all their rights. This		set forth therein, the authors retain all their rights. This
	document and the information contained herein are provided on an "AS		document and the information contained herein are provided on an "AS
	IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTSOR		IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTSOR
	IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND		IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
	THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS		THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
	OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF		OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
	THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED		THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
	WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.		WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
	skipping to change at page 14, line 21		skipping to change at page 14, line 6
	reorder 3.2		reorder 3.2
	moved sentence about translations within sec 3.3		moved sentence about translations within sec 3.3
	reorder 5.3 (C)		reorder 5.3 (C)
	added section 5.10		added section 5.10
	removed "an Informational RFC" from section 5.9		removed "an Informational RFC" from section 5.9
	added text about assigning rights and acknowledging that a		added text about assigning rights and acknowledging that a
	copyright notice will be added to section 5.9		copyright notice will be added to section 5.9
	added 2nd pp to section 3.6 from RFC 3978		added 2nd pp to section 3.6 from RFC 3978
	added pp on multiple copyright notices to sec 6		added pp on multiple copyright notices to sec 6
	??		version 02 ->03
			replaced the text in section 5.10
	??
	??
	??
	US1DOCS 6241323v2
End of changes. 7 change blocks.
	29 lines changed or deleted		14 lines changed or added
This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/