draft-ietf-nfsv4-minorversion1-PAv7.txt		draft-ietf-nfsv4-minorversion1-PAv8.txt
	NFSv4 S. Shepler		NFSv4 S. Shepler
	Internet-Draft M. Eisler		Internet-Draft M. Eisler
	Intended status: Standards Track D. Noveck		Intended status: Standards Track D. Noveck
	Expires: May 2, 2010 Editors		Expires: June 9, 2010 Editors
	October 29, 2009		December 06, 2009
	NFS Version 4 Minor Version 1		NFS Version 4 Minor Version 1
	draft-ietf-nfsv4-minorversion1-PAv7.txt		draft-ietf-nfsv4-minorversion1-PAv8.txt
	Status of this Memo		Status of this Memo
	This Internet-Draft is submitted to IETF in full conformance with the		This Internet-Draft is submitted to IETF in full conformance with the
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and 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-
	Drafts.		Drafts.
	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 May 2, 2010.		This Internet-Draft will expire on June 9, 2010.
	Copyright Notice		Copyright Notice
	Copyright (c) 2009 IETF Trust and the persons identified as the		Copyright (c) 2009 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	skipping to change at page 264, line 12		skipping to change at page 264, line 12
	by the server in any number of ways, including specification by the		by the server in any number of ways, including specification by the
	administrator or by current protocols for transferring data among		administrator or by current protocols for transferring data among
	replicas and protocols not yet developed. NFSv4.1 only defines how		replicas and protocols not yet developed. NFSv4.1 only defines how
	this information is presented by the server to the client.		this information is presented by the server to the client.
	11.10.1. The fs_locations_server4 Structure		11.10.1. The fs_locations_server4 Structure
	The fs_locations_server4 structure consists of the following items:		The fs_locations_server4 structure consists of the following items:
	o An indication of file system up-to-date-ness (fls_currency) in		o An indication of file system up-to-date-ness (fls_currency) in
	terms of approximate seconds before the present. This value is		seconds. This value is relative to the master copy. A negative
	relative to the master copy. A negative value indicates that the		value indicates that the server is unable to give any reasonably
	server is unable to give any reasonably useful value here. A zero		useful value here. A zero indicates that file system is the
	indicates that file system is the actual writable data or a		actual writable data or a reliably coherent and fully up-to-date
	reliably coherent and fully up-to-date copy. Positive values		copy. Positive values indicate how out-of-date this copy can
	indicate how out-of-date this copy can normally be before it is		normally be before it is considered for update. Such a value is
	considered for update. Such a value is not a guarantee that such		not a guarantee that such updates will always be performed on the
	updates will always be performed on the required schedule but		required schedule but instead serves as a hint about how far the
	instead serve as a hint about how far the copy of the data would		copy of the data would be expected to be behind the most up-to-
	be expected to be behind the most up-to-date copy.		date copy.
	o A counted array of one-byte values (fls_info) containing		o A counted array of one-byte values (fls_info) containing
	information about the particular file system instance. This data		information about the particular file system instance. This data
	includes general flags, transport capability flags, file system		includes general flags, transport capability flags, file system
	equivalence class information, and selection priority information.		equivalence class information, and selection priority information.
	The encoding will be discussed below.		The encoding will be discussed below.
	o The server string (fls_server). For the case of the replica		o The server string (fls_server). For the case of the replica
	currently being accessed (via GETATTR), a zero-length string MAY		currently being accessed (via GETATTR), a zero-length string MAY
	be used to indicate the current address being used for the RPC		be used to indicate the current address being used for the RPC
	skipping to change at page 268, line 8		skipping to change at page 268, line 8
	system has an 8-bit class number. Two file systems belong to the		system has an 8-bit class number. Two file systems belong to the
	same class if both have identical non-zero class numbers. Zero is		same class if both have identical non-zero class numbers. Zero is
	treated as non-matching. Most often, the relevant question for the		treated as non-matching. Most often, the relevant question for the
	client will be whether a given replica is identical-to/		client will be whether a given replica is identical-to/
	continuous-with the current one in a given respect but the		continuous-with the current one in a given respect but the
	information should be available also as to whether two other replicas		information should be available also as to whether two other replicas
	match in that respect as well.		match in that respect as well.
	The following fields specify the file system's class numbers for the		The following fields specify the file system's class numbers for the
	equivalence relations used in determining the nature of file system		equivalence relations used in determining the nature of file system
	transitions. See Section 11.7 for details about how this information		transitions. See Section 11.7 and its various subsections for
	is to be used. Servers may assign these values as they wish, so long		details about how this information is to be used. Servers may assign
	as file system instances that share the same value have the specified		these values as they wish, so long as file system instances that
	relationship to one another, conversely file systems which have the		share the same value have the specified relationship to one another,
	specified relationship to one another share a common class value. As		conversely file systems which have the specified relationship to one
	each instance entry is added, the relationships of this instance to		another share a common class value. As each instance entry is added,
	previously entered instances can be consulted and if one is found		the relationships of this instance to previously entered instances
	that bears the specified relationship, that entry's class value can		can be consulted and if one is found that bears the specified
	be copied to the new entry. When no such previous entry exists, a		relationship, that entry's class value can be copied to the new
	new value for that byte index, not previously used can be selected,		entry. When no such previous entry exists, a new value for that byte
	most likely by increment the value of the last class value assigned		index, not previously used can be selected, most likely by
	for that index.		incrementing the value of the last class value assigned for that
			index.
	o The field with byte index FSLI4BX_CLSIMUL defines the		o The field with byte index FSLI4BX_CLSIMUL defines the
	simultaneous-use class for the file system.		simultaneous-use class for the file system.
	o The field with byte index FSLI4BX_CLHANDLE defines the handle		o The field with byte index FSLI4BX_CLHANDLE defines the handle
	class for the file system.		class for the file system.
	o The field with byte index FSLI4BX_CLFILEID defines the fileid		o The field with byte index FSLI4BX_CLFILEID defines the fileid
	class for the file system.		class for the file system.
	skipping to change at page 618, line 28		skipping to change at page 618, line 28
	Jari Arkko, David Black, Scott Bradner, Lisa Dusseault, Lars Eggert,		Jari Arkko, David Black, Scott Bradner, Lisa Dusseault, Lars Eggert,
	Chris Newman, and Tim Polk provided valuable review and guidance.		Chris Newman, and Tim Polk provided valuable review and guidance.
	Olga Kornievskaia found several errors in the SSV specification.		Olga Kornievskaia found several errors in the SSV specification.
	Ricardo Labiaga found several places where the use of RPCSEC_GSS was		Ricardo Labiaga found several places where the use of RPCSEC_GSS was
	underspecified.		underspecified.
	Those who provided miscellaneous comments include: Andy Adamson,		Those who provided miscellaneous comments include: Andy Adamson,
	Sunil Bhargo, Alex Burlyga, Pranoop Erasani, Vadim Finkelstein, Jason		Sunil Bhargo, Alex Burlyga, Pranoop Erasani, Bruce Fields, Vadim
	Goldschmidt, Vijay K. Gurbani, Sergey Klyushin, Ricardo Labiaga,		Finkelstein, Jason Goldschmidt, Vijay K. Gurbani, Sergey Klyushin,
	James Lentini, Anshul Madan, Daniel Muntz, Daniel Picken, Archana		Ricardo Labiaga, James Lentini, Anshul Madan, Daniel Muntz, Daniel
	Ramani, Jim Rees, Mahesh Siddheshwar, Tom Talpey, and Peter Varga.		Picken, Archana Ramani, Jim Rees, Mahesh Siddheshwar, Tom Talpey, and
			Peter Varga.
	Appendix B. RFC Editor Notes		Appendix B. RFC Editor Notes
	[RFC Editor: please remove this section prior to publishing this		[RFC Editor: please remove this section prior to publishing this
	document as an RFC]		document as an RFC]
	[RFC Editor: prior to publishing this document as an RFC, please		[RFC Editor: prior to publishing this document as an RFC, please
	replace all occurrences of RFCTBD10 with RFCxxxx where xxxx is the		replace all occurrences of RFCTBD10 with RFCxxxx where xxxx is the
	RFC number of this document]		RFC number of this document]
End of changes. 6 change blocks.
	30 lines changed or deleted		32 lines changed or added
This html diff was produced by rfcdiff 1.35. The latest version is available from http://tools.ietf.org/tools/rfcdiff/