draft-ietf-nfsv4-rpcsec-gssv3-01.txt   draft-ietf-nfsv4-rpcsec-gssv3-02.txt 
NFSv4 T. Haynes NFSv4 T. Haynes
Internet-Draft NetApp Internet-Draft NetApp
Intended status: Standards Track N. Williams Intended status: Standards Track N. Williams
Expires: May 17, 2012 Cryptonector Expires: October 25, 2012 Cryptonector
November 14, 2011 April 23, 2012
Remote Procedure Call (RPC) Security Version 3 Remote Procedure Call (RPC) Security Version 3
draft-ietf-nfsv4-rpcsec-gssv3-01.txt draft-ietf-nfsv4-rpcsec-gssv3-02.txt
Abstract Abstract
This document specifies version 3 of the Remote Procedure Call (RPC) This document specifies version 3 of the Remote Procedure Call (RPC)
security protocol (RPCSEC_GSS). This protocol provides for: compound security protocol (RPCSEC_GSS). This protocol provides for: compound
authentication of client hosts and users to server (constructed by authentication of client hosts and users to server (constructed by
generic composition), channel binding, security label assertions for generic composition), channel binding, security label assertions for
multi-level and type enforcement, privilege assertions and identity multi-level and type enforcement, privilege assertions, and identity
assertions. assertions.
Requirements Language Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [1]. document are to be interpreted as described in RFC 2119 [1].
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF). Note that other groups may also distribute
other groups may also distribute working documents as Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at This Internet-Draft will expire on October 25, 2012.
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on May 17, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the BSD License. described in the Simplified BSD License.
This document may contain material from IETF Documents or IETF This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this 10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process. modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other it for publication as an RFC or to translate it into languages other
than English. than English.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1. Motivation . . . . . . . . . . . . . . . . . . . . . . . . 4 1.1. Motivation . . . . . . . . . . . . . . . . . . . . . . . . 5
1.2. Applications of RPCSEC_GSSv3 . . . . . . . . . . . . . . . 5 1.2. Applications of RPCSEC_GSSv3 . . . . . . . . . . . . . . . 6
2. The RPCSEC_GSSv3 protocol . . . . . . . . . . . . . . . . . . 5 2. The RPCSEC_GSSv3 protocol . . . . . . . . . . . . . . . . . . 6
2.1. Control messages . . . . . . . . . . . . . . . . . . . . . 11 2.1. Control messages . . . . . . . . . . . . . . . . . . . . . 12
2.1.1. New auth_stat values . . . . . . . . . . . . . . . . . 11 2.1.1. New auth_stat values . . . . . . . . . . . . . . . . . 12
2.1.2. Create request . . . . . . . . . . . . . . . . . . . . 11 2.1.2. Create request . . . . . . . . . . . . . . . . . . . . 12
2.1.3. Context handle destruction . . . . . . . . . . . . . . 17 2.1.3. Context handle destruction . . . . . . . . . . . . . . 18
2.1.4. List request . . . . . . . . . . . . . . . . . . . . . 17 2.1.4. List request . . . . . . . . . . . . . . . . . . . . . 18
2.1.5. Extensibility . . . . . . . . . . . . . . . . . . . . 17 2.1.5. Extensibility . . . . . . . . . . . . . . . . . . . . 18
3. Privileges and identity representation for NFSv4 . . . . . . . 18 3. Privileges and identity representation for NFSv4 . . . . . . . 19
4. Security Considerations . . . . . . . . . . . . . . . . . . . 19 4. Security Considerations . . . . . . . . . . . . . . . . . . . 20
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21
6. Normative References . . . . . . . . . . . . . . . . . . . . . 20 6. Normative References . . . . . . . . . . . . . . . . . . . . . 21
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 21 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 22
Appendix B. RFC Editor Notes . . . . . . . . . . . . . . . . . . 21 Appendix B. RFC Editor Notes . . . . . . . . . . . . . . . . . . 22
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 21 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 22
1. Introduction 1. Introduction
The original RPCSEC_GSS protocol [2] provided for authentication of The original RPCSEC_GSS protocol [2] provided for authentication of
RPC clients and servers to each other using the Generic Security RPC clients and servers to each other using the Generic Security
Services Application Programming Interface (GSS-API) [3]. The second Services Application Programming Interface (GSS-API) [3]. The second
version of RPCSEC_GSS [4] added support for channel binding [5]. version of RPCSEC_GSS [4] added support for channel binding [5].
We find that GSS-API mechanisms are insufficient for communicating We find that GSS-API mechanisms are insufficient for communicating
certain aspects of a client's identity and authority to a server. certain aspects of a client's identity and authority to a server.
 End of changes. 9 change blocks. 
34 lines changed or deleted 28 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/