A Simpler Mechanism For Organizing FedFS NSDBs
draft-cel-nfsv4-federated-fs-nce-06

Document Type Active Internet-Draft (individual)
Last updated 2016-10-25
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network File System Version 4                                   C. Lever
Internet-Draft                                                    Oracle
Intended status: Standards Track                                S. Sorce
Expires: April 28, 2017                                          Red Hat
                                                        October 25, 2016

             A Simpler Mechanism For Organizing FedFS NSDBs
                  draft-cel-nfsv4-federated-fs-nce-06

Abstract

   This document describes a new, simpler mechanism for searching FedFS
   NSDBs (Name Space Data Bases) for FedFS records.  This mechanism
   replaces the mechanism described in existing FedFS Proposed
   Standards.

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 April 28, 2017.

Copyright Notice

   Copyright (c) 2016 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

Lever & Sorce            Expires April 28, 2017                 [Page 1]
Internet-Draft           FedFS NSDB Organization            October 2016

   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
     1.1.  Altering rootDSEs Considered Hazardous  . . . . . . . . .   3
   2.  Simplifying NCE Discovery . . . . . . . . . . . . . . . . . .   5
     2.1.  NSDB Configuration  . . . . . . . . . . . . . . . . . . .   5
     2.2.  fedfsNsdbContainerEntry . . . . . . . . . . . . . . . . .   7
     2.3.  NSDB Container Entry (NCE) Enumeration  . . . . . . . . .   7
   3.  Backwards Compatibility . . . . . . . . . . . . . . . . . . .   8
     3.1.  NSDB server compatibility . . . . . . . . . . . . . . . .   8
     3.2.  NSDB client compatibility . . . . . . . . . . . . . . . .   8
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
     5.1.  LDAP Descriptor Deprecation . . . . . . . . . . . . . . .   9
     5.2.  LDAP Descriptor Registration  . . . . . . . . . . . . . .   9
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .  10
     6.2.  Informative References  . . . . . . . . . . . . . . . . .  10
   Appendix A.  Acknowledgements . . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   A FedFS junction is an object stored on a fileserver that redirects
   file-access clients to other fileserver shares.  Using junctions,
   multiple fileserver shares on many fileservers can be joined into a
   single filename namespace.  Think of a junction as a symlink that
   points to the root directory of a share stored on another fileserver.

   The target locations of these remote shares are not stored in FedFS
   junctions.  Instead, a junction contains a reference to a set of
   location information stored in an LDAP directory.  The LDAP directory
   is referred to as a Name Space Data Base, or NSDB.

   The fundamental and most frequent operation performed with an NSDB is
   "FSN resolution," described in section 5.2.2 of [RFC7532].  This is
   the act of reading the reference stored in a junction, retrieving the
   referenced location information from an NSDB, and forming a
Show full document text