This list has been closed. All email regarding the RDDP protocols should be directed to the storm WG mailing list, firstname.lastname@example.org.
Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made within the context of an IETF activity is considered an "IETF Contribution". Such statements include oral statements in IETF sessions, as well as written and electronic communications made at any time or place, which are addressed to:
# The IETF plenary session,
# Any IETF working group or portion thereof.
# The IESG or any member thereof on behalf of the IESG.
# The IAB or any member thereof on behalf of the IAB.
# Any IETF mailing list, including the IETF list itself, any working group
or design team list, or any other list functioning under IETF auspices.
# The RFC Editor or the Internet-Drafts function.
All IETF Contributions are subject to the rules of RFC 5378 and RFC 3979 (updated by RFC 4879).
Statements made outside of an IETF session, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not IETF Contributions in the context of this notice.
Please consult RFC 5378 and RFC 3979 for details.
A participant in any IETF activity is deemed to accept all IETF rules of process, as documented in Best Current Practices RFCs and IESG Statements.
A participant in any IETF activity acknowledges that written, audio and video records of meetings may be made and may be available to the public.
This is the mailing list of the former IETF rddp Working Group, which has been closed. The original description of this WG's activity was the following:
The purpose of the IETF rddp WG is to enable Remote Direct Data Placement (rddp) capabilities with IP transport protocols, in particular with SCTP. RDDP capabilities refer to the ability to place data directly from the NIC into application buffers, without intensive CPU usage. This strategy avoids the costs of data copying and enables using IP as a method for high speed buffer to buffer transfer, allowing IP to replace special purpose networks currently in use. Remote Direct Memory Access (RDMA) is an example of this concept.
Conceptually, RDDP functionality can be viewed as consisting of two layers. First the direct data placement capability, which is accomplished through a tag and a lookup table on the NIC. Above this core functionality, an RDDP control protocol is needed to specify how the direct data placement can be used, for example READ and WRITE
To see the collection of prior postings to the list,
visit the rddp
Subscribe to rddp by filling out the following
This is a closed list, which means your subscription
will be held for approval. You will be notified of the list
moderator's decision by email. This is also a hidden list, which means that the
list of members is available only to the list administrator.