draft-ietf-nfsv4-federated-fs-dns-srv-namespace-12.txt		draft-ietf-nfsv4-federated-fs-dns-srv-namespace-13.txt
	Network Working Group C. Everhart		Network Working Group C. Everhart
	Internet-Draft W. Adamson		Internet-Draft W. Adamson
	Intended status: Standards Track NetApp		Intended status: Standards Track NetApp
	Expires: September 1, 2012 J. Zhang		Expires: September 9, 2012 J. Zhang
	Google		Google
	February 29, 2012		March 8, 2012
	Using DNS SRV to Specify a Global File Name Space with NFS version 4		Using DNS SRV to Specify a Global File Name Space with NFS version 4
	draft-ietf-nfsv4-federated-fs-dns-srv-namespace-12.txt		draft-ietf-nfsv4-federated-fs-dns-srv-namespace-13.txt
	Abstract		Abstract
	The NFS version 4 protocol provides a mechanism for a collection of		The NFS version 4 protocol provides a mechanism for a collection of
	NFS file servers to collaborate in providing an organization-wide		NFS file servers to collaborate in providing an organization-wide
	file name space. The DNS SRV RR allows a simple way for an		file name space. The DNS SRV RR allows a simple way for an
	organization to publish the root of its filesystem name space, even		organization to publish the root of its filesystem name space, even
	to clients that might not be intimately associated with such an		to clients that might not be intimately associated with such an
	organization. The DNS SRV RR can be used to join these organization-		organization. The DNS SRV RR can be used to join these organization-
	wide file name spaces together to allow construction of a global,		wide file name spaces together to allow construction of a global,
	skipping to change at page 1, line 39		skipping to change at page 1, line 39
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at http://datatracker.ietf.org/drafts/current/.		Drafts is at http://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	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."
	This Internet-Draft will expire on September 1, 2012.		This Internet-Draft will expire on September 9, 2012.
	Copyright Notice		Copyright Notice
	Copyright (c) 2012 IETF Trust and the persons identified as the		Copyright (c) 2012 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 5, line 21		skipping to change at page 5, line 21
	name space published by that organization.		name space published by that organization.
	The DNS SRV resource record type [RFC2782] is used to locate "domain		The DNS SRV resource record type [RFC2782] is used to locate "domain
	root" file servers. The format of the DNS SRV record is as follows:		root" file servers. The format of the DNS SRV record is as follows:
	_Service._Proto.Name TTL Class SRV Priority Weight Port Target		_Service._Proto.Name TTL Class SRV Priority Weight Port Target
	The Service name used is "_nfs-domainroot", in conformance with RFC		The Service name used is "_nfs-domainroot", in conformance with RFC
	6335 [RFC6335]. The Protocol name used is "_tcp", for NFS service		6335 [RFC6335]. The Protocol name used is "_tcp", for NFS service
	over TCP. Future NFS services using other protocols MUST use another		over TCP. Future NFS services using other protocols MUST use another
	Protocol name. The Target fields give the domain names of the NFS		Protocol name. The "_udp" label MUST NOT be used to imply use of UDP
	servers that export filesystems for the domain's root. An NFS client		with NFSv4, as neither RFC 3530 [RFC3530] nor RFC 5661 [RFC5661]
	may then interpret any of the exported root filesystems as the root		defines NFSv4 over UDP. The Target fields give the domain names of
	of the filesystem published by the organization with the given domain		the NFS servers that export filesystems for the domain's root. An
	name.		NFS client may then interpret any of the exported root filesystems as
			the root of the filesystem published by the organization with the
			given domain name.
	The domain root service is not useful for NFS versions prior to v4,		The domain root service is not useful for NFS versions prior to v4,
	as the fs_locations attribute was introduced only in NFSv4 (as		as the fs_locations attribute was introduced only in NFSv4 (as
	described in Section 2). The "_nfs" Service name is not limited to		described in Section 2).
	NFSv4; it is possible to use that prefix in naming additional
	Services (and their SRV records) that are also applicable to other
	versions of NFS (e.g., NFSv3 [RFC1813].
	In order to allow the NFSv4 servers so given to export a variety of		In order to allow the NFSv4 servers so given to export a variety of
	filesystems, those file servers MUST export the given domain's root		filesystems, those file servers MUST export the given domain's root
	filesystems at "/.domainroot/{Name}" within their pseudo-filesystems,		filesystems at "/.domainroot/{Name}" within their pseudo-filesystems,
	where the "{Name}" is the name of the organization as used in the SRV		where the "{Name}" is the name of the organization as used in the SRV
	RR.		RR.
	As an example, suppose a client wished to locate the root of the		As an example, suppose a client wished to locate the root of the
	filesystem published by organization example.net. The DNS servers		filesystem published by organization example.net. The DNS servers
	for the domain would publish records like		for the domain would publish records like
End of changes. 6 change blocks.
	13 lines changed or deleted		12 lines changed or added
This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/