draft-ietf-nfsv4-rfc1832bis-04.txt		draft-ietf-nfsv4-rfc1832bis-05.txt
	Network Working Group M. Eisler		Network Working Group M. Eisler
	Internet-Draft Editor		Internet-Draft Editor
	Document: draft-ietf-nfsv4-rfc1832bis-04.txt Network Appliance, Inc.		Document: draft-ietf-nfsv4-rfc1832bis-05.txt Network Appliance, Inc.
	June 2004		February 2005
	XDR: External Data Representation Standard		XDR: External Data Representation Standard
	Status of this Memo		Status of this Memo
	By submitting this Internet-Draft, I certify that any applicable		By submitting this Internet-Draft, I certify that any applicable
	patent or other IPR claims of which I am aware have been disclosed,		patent or other IPR claims of which I am aware have been disclosed,
	or will be disclosed, and any of which I become aware will be		or will be disclosed, and any of which I become aware will be
	disclosed, in accordance with RFC 3668.		disclosed, in accordance with RFC 3668.
	skipping to change at page 24, line 37		skipping to change at page 24, line 37
	14. Editor's Address		14. Editor's Address
	Mike Eisler		Mike Eisler
	5765 Chase Point Circle		5765 Chase Point Circle
	Colorado Springs, CO 80919		Colorado Springs, CO 80919
	USA		USA
	Phone: 719-599-9026		Phone: 719-599-9026
	EMail: mike@eisler.com		EMail: mike@eisler.com
			Please address comments to: nfsv4@ietf.org
	15. Acknowledgements		15. Acknowledgements
	Bob Lyon was Sun's visible force behind ONC RPC in the 1980s. Sun		Bob Lyon was Sun's visible force behind ONC RPC in the 1980s. Sun
	Microsystems, Inc. is listed as the author of RFC1014, which RFC1832		Microsystems, Inc. is listed as the author of RFC1014, which RFC1832
	was heavily derived from. Raj Srinivasan in turn edited RFC1014 into		was heavily derived from. Raj Srinivasan in turn edited RFC1014 into
	RFC1832. Raj and the rest of the old ONC RPC working group produced		RFC1832. Raj and the rest of the old ONC RPC working group produced
	RFC1832 from which this document is derived. Mike Eisler and Bill		RFC1832 from which this document is derived. Mike Eisler and Bill
	Janssen submitted the implementation reports for this standard. Kevin		Janssen submitted the implementation reports for this standard. Kevin
	Coffman and Benny Halevy reviewed this document and gave feedback.		Coffman and Benny Halevy reviewed this document and gave feedback.
	Peter Astrand and Bryan Olson pointed out several errors in RFC1832		Peter Astrand and Bryan Olson pointed out several errors in RFC1832
	skipping to change at page 25, line 29		skipping to change at page 25, line 30
	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.
	17. Copyright Notice		17. Copyright Notice
	Copyright (C) The Internet Society (2004). This document is subject		Copyright (C) The Internet Society (2005). This document is subject
	to the rights, licenses and restrictions contained in BCP 78, and		to the rights, licenses and restrictions contained in BCP 78, and
	except as set forth therein, the authors retain all their rights.		except as set forth therein, the authors retain all their rights.
	This document and the information contained herein are provided on an		This document and the information contained herein are provided on an
	"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS		"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
	OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET		OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
	ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,		ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
	INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE		INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
	INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED		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.
End of changes.
This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/