Remote Procedure Call (RPC) Security Version 3
RFC 7861
| Document | Type |
RFC - Proposed Standard
(November 2016; No errata)
Updates RFC 5403
|
|
|---|---|---|---|
| Authors | Andy Adamson , Nicolás Williams | ||
| Last updated | 2016-11-10 | ||
| Stream | IETF | ||
| Formats | plain text html pdf htmlized bibtex | ||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Spencer Shepler | ||
| Shepherd write-up | Show (last changed 2015-09-10) | ||
| IESG | IESG state | RFC 7861 (Proposed Standard) | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Spencer Dawkins | ||
| Send notices to | (None) | ||
| IANA | IANA review state | Version Changed - Review Needed | |
| IANA action state | RFC-Ed-Ack | ||
Internet Engineering Task Force (IETF) W. Adamson
Request for Comments: 7861 NetApp
Updates: 5403 N. Williams
Category: Standards Track Cryptonector
ISSN: 2070-1721 November 2016
Remote Procedure Call (RPC) Security Version 3
Abstract
This document specifies version 3 of the Remote Procedure Call (RPC)
security protocol (RPCSEC_GSS). This protocol provides support for
multi-principal authentication of client hosts and user principals to
a server (constructed by generic composition), security label
assertions for multi-level security and type enforcement, structured
privilege assertions, and channel bindings. This document updates
RFC 5403.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7861.
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
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.
Adamson & Williams Standards Track [Page 1]
RFC 7861 NFSv4 RPC Security November 2016
Table of Contents
1. Introduction and Motivation .....................................2
1.1. Requirements Language ......................................3
1.2. Added Functionality ........................................4
1.3. XDR Code Extraction ........................................5
2. The RPCSEC_GSSv3 Protocol .......................................6
2.1. Compatibility with RPCSEC_GSSv2 ............................6
2.2. Version Negotiation ........................................6
2.3. New Reply Verifier .........................................7
2.4. XDR Code Preliminaries .....................................8
2.5. RPCSEC_GSS_BIND_CHANNEL Operation .........................10
2.6. New auth_stat Values ......................................10
2.7. New Control Procedures ....................................10
2.7.1. New Control Procedure - RPCSEC_GSS_CREATE ..........12
2.7.2. New Control Procedure - RPCSEC_GSS_LIST ............20
2.8. Extensibility .............................................21
3. Operational Recommendation for Deployment ......................21
4. Security Considerations ........................................21
5. IANA Considerations ............................................22
5.1. New RPC Authentication Status Numbers .....................22
5.2. Structured Privilege Name Definitions .....................23
5.2.1. Initial Registry ...................................24
5.2.2. Updating Registrations .............................24
6. References .....................................................25
6.1. Normative References ......................................25
6.2. Informative References ....................................26
Acknowledgments ...................................................26
Authors' Addresses ................................................26
1. Introduction and Motivation
The original Remote Procedure Call (RPC) security protocol
(RPCSEC_GSS) [RFC2203] provided for authentication of RPC clients and
servers to each other using the Generic Security Service Application
Programming Interface (GSS-API) [RFC2743]. The second version of
RPCSEC_GSS [RFC5403] added support for channel bindings [RFC5056].
Existing GSS-API mechanisms are insufficient for communicating
certain authorization and authentication information to a server.
The GSS-API and its mechanisms certainly could be extended to address
this shortcoming. However, it is addressed here at the application
layer, i.e., in RPCSEC_GSS.
A major motivation for version 3 of RPCSEC_GSS (RPCSEC_GSSv3) is to
Show full document text