RFC 5041 on Direct Data Placement over Reliable Transports
[email protected] Wed, 31 Oct 2007 15:53:31 -0700 (PDT)
| Newsgroups | gmane.ietf.rddp |
|---|---|
| Message-ID | <[email protected]> |
A new Request for Comments is now available in online RFC libraries.
RFC 5041
Title: Direct Data Placement over Reliable
Transports
Author: H. Shah, J. Pinkerton,
R. Recio, P. Culley
Status: Standards Track
Date: October 2007
Mailbox: [email protected],
[email protected],
[email protected], [email protected]
Pages: 38
Characters: 84642
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-rddp-ddp-07.txt
URL: http://www.rfc-editor.org/rfc/rfc5041.txt
The Direct Data Placement protocol provides information to Place the
incoming data directly into an upper layer protocol's receive buffer
without intermediate buffers. This removes excess CPU and memory
utilization associated with transferring data through the
intermediate buffers. [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
...