Multiple NFSv4 Domain Namespace Deployment Guidelines
draft-ietf-nfsv4-multi-domain-fs-reqs-03

The information below is for an old version of the document
Document Type Active Internet-Draft (nfsv4 WG)
Last updated 2015-08-07
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Reviews
Stream WG state In WG Last Call
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
NFSv4 Working Group                                           W. Adamson
Internet-Draft                                                    NetApp
Intended status: Standards Track                             N. Williams
Expires: February 8, 2016                                   Cryptonector
                                                          August 7, 2015

         Multiple NFSv4 Domain Namespace Deployment Guidelines
                draft-ietf-nfsv4-multi-domain-fs-reqs-03

Abstract

   This document describes administrative constraints to the deployment
   of the NFSv4 protocols required for the construction of an NFSv4 file
   system namespace supporting the use of multiple NFSv4 domains and
   utilizing multi-domain capable file systems.  Also described are
   administrative constraints to name resolution and security services
   appropriate to such a system.  Such a namespace is a suitable way to
   enable a Federated File System supporting the use of multiple NFSv4
   domains.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on February 8, 2016.

Adamson & Williams      Expires February 8, 2016                [Page 1]
Internet-Draft             Multi NFSv4 Domain                August 2015

Copyright Notice

   Copyright (c) 2015 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  NFSv4 Server Identity Mapping . . . . . . . . . . . . . . . .   5
   4.  Stand-alone NFSv4 Domain Deployment Examples  . . . . . . . .   5
   4.1.  AUTH_SYS with Stringified UID/GID . . . . . . . . . . . . .   6
   4.2.  AUTH_SYS with name@domain . . . . . . . . . . . . . . . . .   6
   4.3.  RPCSEC_GSS with name@domain . . . . . . . . . . . . . . . .   7
   5.  Multi-domain Constraints to the NFSv4 Protocol  . . . . . . .   7
   5.1.  Name@domain Constraints . . . . . . . . . . . . . . . . . .   7
   5.1.1.  NFSv4 Domain and DNS Services . . . . . . . . . . . . . .   8
   5.1.2.  NFSv4 Domain, Name Service, and Domain Aware File Systems   8
   5.2.  RPC Security Constraints  . . . . . . . . . . . . . . . . .   9
   5.2.1.  NFSv4 Domain and Security Services  . . . . . . . . . . .  10
   6.  Resolving Multi-domain Authorization Information  . . . . . .  10
   7.  Stand-alone Examples and Multiple NFSv4 Domain Namespaces . .  11
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  12
   9.  Normative References  . . . . . . . . . . . . . . . . . . . .  13
   Appendix A.  Acknowledgments  . . . . . . . . . . . . . . . . . .  14
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  14

1.  Introduction

   An NFSv4 domain is defined as a set of users, groups and computers
   running NFSv4 protocols (NFSv4.0 [RFC7530], NFSv4.1 [RFC5661], and
   NFSv4.2 [I-D.NFSv4.2] as of this writing) identified by an NFSv4
   domain name.

   The Federated File System (FedFS) [RFC5716] describes the
   requirements and administrative tools to construct a uniform NFSv4
   file server based namespace that is capable of spanning a whole
   enterprise and that is easy to manage.

Adamson & Williams      Expires February 8, 2016                [Page 2]
Internet-Draft             Multi NFSv4 Domain                August 2015

   The FedFS is the standardized method of constructing and
   administrating an enterprise wide NFSv4 filesystem, and so is
   referenced in this document.  The issues with multiple NFSv4 domain
Show full document text