[nfsv4] RFC 8166 on Remote Direct Memory Access Transport for Remote Procedure Call Version 1
rfc-editor@rfc-editor.org Fri, 30 June 2017 22:52 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: nfsv4@ietfa.amsl.com
Delivered-To: nfsv4@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 914ED129B95; Fri, 30 Jun 2017 15:52:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level:
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2SmkEYsiVqRy; Fri, 30 Jun 2017 15:52:20 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 037CE128CFF; Fri, 30 Jun 2017 15:52:20 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 8776BB813D0; Fri, 30 Jun 2017 15:51:48 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, nfsv4@ietf.org
Message-Id: <20170630225148.8776BB813D0@rfc-editor.org>
Date: Fri, 30 Jun 2017 15:51:48 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/X-jQ4VqdHvfKKJq9RNFs6t0W2k4>
Subject: [nfsv4] RFC 8166 on Remote Direct Memory Access Transport for Remote Procedure Call Version 1
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nfsv4/>
List-Post: <mailto:nfsv4@ietf.org>
List-Help: <mailto:nfsv4-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jun 2017 22:52:21 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8166
Title: Remote Direct Memory Access Transport
for Remote Procedure Call Version 1
Author: C. Lever, Ed.,
W. Simpson,
T. Talpey
Status: Standards Track
Stream: IETF
Date: June 2017
Mailbox: chuck.lever@oracle.com,
william.allen.simpson@gmail.com,
ttalpey@microsoft.com
Pages: 55
Characters: 123019
Obsoletes: RFC 5666
I-D Tag: draft-ietf-nfsv4-rfc5666bis-11.txt
URL: https://www.rfc-editor.org/info/rfc8166
DOI: 10.17487/RFC8166
This document specifies a protocol for conveying Remote Procedure
Call (RPC) messages on physical transports capable of Remote Direct
Memory Access (RDMA). This protocol is referred to as the RPC-over-
RDMA version 1 protocol in this document. It requires no revision to
application RPC protocols or the RPC protocol itself. This document
obsoletes RFC 5666.
This document is a product of the Network File System Version 4 Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC