datatracker.ietf.org
Sign in
Version 5.6.2.p2, 2014-07-24
Report a bug

Remote Procedure Call (RPC) Security Version 3
draft-ietf-nfsv4-rpcsec-gssv3-08

Document type: Active Internet-Draft (nfsv4 WG)
Document stream: IETF
Last updated: 2014-07-07
Intended RFC status: Proposed Standard
Other versions: plain text, xml, pdf, html

IETF State: WG Document
Document shepherd: No shepherd assigned

IESG State: AD is watching
Responsible AD: Martin Stiemerling
Send notices to: nfsv4-chairs@tools.ietf.org, draft-ietf-nfsv4-rpcsec-gssv3@tools.ietf.org

NFSv4                                                         W. Adamson
Internet-Draft                                                    NetApp
Intended status: Standards Track                             N. Williams
Expires: December 29, 2014                                  Cryptonector
                                                           June 27, 2014

             Remote Procedure Call (RPC) Security Version 3
                  draft-ietf-nfsv4-rpcsec-gssv3-08.txt

Abstract

   This document specifies version 3 of the Remote Procedure Call (RPC)
   security protocol (RPCSEC_GSS).  This protocol provides for multi-
   principal authentication of client hosts and user principals to
   server (constructed by generic composition), security label
   assertions for multi-level and type enforcement, structured privilege
   assertions, and channel bindings.

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 RFC 2119 [1].

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 December 29, 2014.

Copyright Notice

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

Adamson & Williams      Expires December 29, 2014               [Page 1]
Internet-Draft                    NFSv4                        June 2014

   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 and Motivation  . . . . . . . . . . . . . . . . .  3
   2.  The RPCSEC_GSSv3 Protocol  . . . . . . . . . . . . . . . . . .  4
     2.1.  Compatibility with RPCSEC_GSSv2  . . . . . . . . . . . . .  5
     2.2.  Version Negotiation  . . . . . . . . . . . . . . . . . . .  5
     2.3.  New REPLY verifier . . . . . . . . . . . . . . . . . . . .  5
     2.4.  New Version Number . . . . . . . . . . . . . . . . . . . .  6
     2.5.  New auth_stat Values . . . . . . . . . . . . . . . . . . .  8
     2.6.  New Control Procedures . . . . . . . . . . . . . . . . . .  8
       2.6.1.  New Control Procedure - RPCSEC_GSS_CREATE  . . . . . .  9
       2.6.2.  New Control Procedure - RPCSEC_GSS_LIST  . . . . . . . 15
     2.7.  Extensibility  . . . . . . . . . . . . . . . . . . . . . . 16
   3.  Operational Recommendation for Deployment  . . . . . . . . . . 17
   4.  Security Considerations  . . . . . . . . . . . . . . . . . . . 17
   5.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 18
   6.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 18
     6.1.  Normative References . . . . . . . . . . . . . . . . . . . 18
     6.2.  Informative References . . . . . . . . . . . . . . . . . . 19
   Appendix A.  Acknowledgments . . . . . . . . . . . . . . . . . . . 19
   Appendix B.  RFC Editor Notes  . . . . . . . . . . . . . . . . . . 19
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 19

Adamson & Williams      Expires December 29, 2014               [Page 2]
Internet-Draft                    NFSv4                        June 2014

1.  Introduction and Motivation

   The original RPCSEC_GSS protocol [2] provided for authentication of
   RPC clients and servers to each other using the Generic Security
   Services Application Programming Interface (GSS-API) [3].  The second
   version of RPCSEC_GSS [4] added support for channel bindings [5].

   We find that GSS-API mechanisms are insufficient for communicating

[include full document text]