RFC 5040 on A Remote Direct Memory Access Protocol Specification

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

        
        RFC 5040

        Title:      A Remote Direct Memory Access 
                    Protocol Specification 
        Author:     R. Recio, B. Metzler,
                    P. Culley, J. Hilland,
                    D. Garcia
        Status:     Standards Track
        Date:       October 2007
        Mailbox:    [email protected], 
                    [email protected], 
                    [email protected], [email protected], 
                    [email protected]
        Pages:      66
        Characters: 142247
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-rddp-rdmap-07.txt

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

This document defines a Remote Direct Memory Access Protocol
(RDMAP) that operates over the Direct Data Placement Protocol (DDP
protocol).  RDMAP provides read and write services directly to
applications and enables data to be transferred directly into
Upper Layer Protocol (ULP) Buffers without intermediate data
copies.  It also enables a kernel bypass implementation.  
[STANDARDS TRACK]

This document is a product of the Remote Direct Data Placement
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 list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to [email protected].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [email protected].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [email protected] with the message body 

help: ways_to_get_rfcs. For example:

        To: [email protected]
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email protected].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
[email protected].  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...