[rfc-dist] RFC 5666 on Remote Direct Memory Access Transport for Remote Procedure Call

rfc-editor at rfc-editor.org rfc-editor at rfc-editor.org
Thu Jan 14 23:08:16 PST 2010


A new Request for Comments is now available in online RFC libraries.

        
        RFC 5666

        Title:      Remote Direct Memory Access Transport 
                    for Remote Procedure Call 
        Author:     T. Talpey, B. Callaghan
        Status:     Standards Track
        Date:       January 2010
        Mailbox:    tmtalpey at gmail.com, 
                    brentc at apple.com
        Pages:      34
        Characters: 83728
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-nfsv4-rpcrdma-09.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5666.txt

This document describes a protocol providing Remote Direct Memory Access
(RDMA) as a new transport for Remote Procedure Call (RPC).  The
RDMA transport binding conveys the benefits of efficient, bulk-data
transport over high-speed networks, while providing for minimal
change to RPC applications and with no required revision of the
application RPC protocol, or the RPC protocol itself.  [STANDARDS TRACK]

This document is a product of the Network File System Version 4 Working Group of the IETF.

This is now a Proposed Standard Protocol.

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 Internet
Official Protocol Standards (STD 1) 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
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute




More information about the rfc-dist mailing list