Multiple NFSv4 Domain Namespace Deployment Requirements
draft-ietf-nfsv4-multi-domain-fs-reqs-10

The information below is for an old version of the document
Document Type Active Internet-Draft (nfsv4 WG)
Last updated 2016-09-01 (latest revision 2016-08-29)
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Spencer Shepler
Shepherd write-up Show (last changed 2016-05-08)
IESG IESG state Approved-announcement to be sent::Revised I-D Needed
Consensus Boilerplate Yes
Telechat date
Responsible AD Spencer Dawkins
Send notices to (None)
IANA IANA review state IANA OK - No Actions Needed
IANA action state None
NFSv4 Working Group                                           W. Adamson
Internet-Draft                                                    NetApp
Intended status: Standards Track                             N. Williams
Expires: March 2, 2017                                      Cryptonector
                                                         August 29, 2016

        Multiple NFSv4 Domain Namespace Deployment Requirements
                draft-ietf-nfsv4-multi-domain-fs-reqs-10

Abstract

   This document presents requirements on the deployment of the NFSv4
   protocols for the construction of an NFSv4 file name space in
   environments with multiple NFSv4 Domains.  To participate in an NFSv4
   multi-domain file name space, the server must offer a multi-domain
   capable file system and support RPCSEC_GSS for user authentication.
   In most instances, the server must also support identity mapping
   services.

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 March 2, 2017.

Copyright Notice

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

Adamson & Williams        Expires March 2, 2017                 [Page 1]
Internet-Draft             Multi NFSv4 Domain                August 2016

   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.  Federated File System . . . . . . . . . . . . . . . . . . . .   5
   4.  Identity Mapping  . . . . . . . . . . . . . . . . . . . . . .   5
   4.1.  NFSv4 Server Identity Mapping . . . . . . . . . . . . . . .   5
   4.2.  NFSv4 Client Identity Mapping . . . . . . . . . . . . . . .   6
   5.  Stand-alone NFSv4 Domain Deployment Examples  . . . . . . . .   7
   5.1.  AUTH_SYS with Stringified UID/GID . . . . . . . . . . . . .   7
   5.2.  AUTH_SYS with name@domain . . . . . . . . . . . . . . . . .   8
   5.3.  RPCSEC_GSS with name@domain . . . . . . . . . . . . . . . .   8
   6.  Multi-domain Constraints to the NFSv4 Protocol  . . . . . . .   9
   6.1.  Name@domain Constraints . . . . . . . . . . . . . . . . . .   9
   6.1.1.  NFSv4 Domain and DNS Services . . . . . . . . . . . . . .   9
   6.1.2.  NFSv4 Domain and Name Services  . . . . . . . . . . . . .  10
   6.2.  RPC Security Constraints  . . . . . . . . . . . . . . . . .  10
   6.2.1.  NFSv4 Domain and Security Services  . . . . . . . . . . .  11
   7.  Stand-alone Examples in an NFSv4 Multi-domain Deployment  . .  11
   8.  Resolving Multi-domain Authorization Information  . . . . . .  12
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  13
   10. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  14
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  14
   11.1.  Normative References . . . . . . . . . . . . . . . . . . .  14
   11.2.  Informative References . . . . . . . . . . . . . . . . . .  15
   Appendix A.  Acknowledgments  . . . . . . . . . . . . . . . . . .  16
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  16

1.  Introduction

   The NFSv4 protocols NFSv4.0 [RFC7530], NFSv4.1 [RFC5661], NFSv4.2
   [I-D.NFSv4.2] introduce the concept of an NFS Domain.  An NFSv4
   Domain is defined as a set of users and groups using the NFSv4
   name@domain user and group identification syntax with the same
   specified @domain.

   Previous versions of the NFS protocol, such as NFSv3 [RFC1813], use
   the UNIX-centric user identification mechanism of numeric user and
Show full document text