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

The information below is for an old version of the document
Document Type Active Internet-Draft (nfsv4 WG)
Last updated 2013-10-17
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists (IESG: Dead)
Telechat date
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: April 20, 2014                                     Cryptonector
                                                        October 17, 2013

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

Abstract

   This document specifies version 3 of the Remote Procedure Call (RPC)
   security protocol (RPCSEC_GSS).  This protocol provides for compound
   authentication of client hosts and users 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 April 20, 2014.

Copyright Notice

   Copyright (c) 2013 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 April 20, 2014                 [Page 1]
Internet-Draft                    NFSv4                     October 2013

   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 . . . . . . . . . . . . . . . . . . . . . . . . .  3
     1.1.  Applications of RPCSEC_GSSv3 . . . . . . . . . . . . . . .  4
   2.  The RPCSEC_GSSv3 protocol  . . . . . . . . . . . . . . . . . .  5
     2.1.  New auth_stat values . . . . . . . . . . . . . . . . . . .  9
     2.2.  RPC message credential and verifier  . . . . . . . . . . . 10
     2.3.  Control Messages . . . . . . . . . . . . . . . . . . . . . 10
       2.3.1.  Create request . . . . . . . . . . . . . . . . . . . . 11
       2.3.2.  Destruction request  . . . . . . . . . . . . . . . . . 15
       2.3.3.  List request . . . . . . . . . . . . . . . . . . . . . 16
       2.3.4.  Extensibility  . . . . . . . . . . . . . . . . . . . . 16
     2.4.  Data Messages  . . . . . . . . . . . . . . . . . . . . . . 17
   3.  Security Considerations  . . . . . . . . . . . . . . . . . . . 17
   4.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 18
   5.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 19
     5.1.  Normative References . . . . . . . . . . . . . . . . . . . 19
     5.2.  Informative References . . . . . . . . . . . . . . . . . . 19
   Appendix A.  Acknowledgments . . . . . . . . . . . . . . . . . . . 20
   Appendix B.  RFC Editor Notes  . . . . . . . . . . . . . . . . . . 20
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 20

Adamson & Williams       Expires April 20, 2014                 [Page 2]
Internet-Draft                    NFSv4                     October 2013

1.  Introduction

   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
   certain aspects of a client's authority to a server.  The GSS-API and
Show full document text