Last Modified: 2003-10-20
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 commands.
The work of the WG is to accomplish four items:
1) A (transport independent) protocol core to support direct data placement from the NIC into specified memory, usually application buffers.
2) A (transport independent) protocol core layered on top of the direct data placement protocol that specifies control of RDDP.
3) A mapping of the direct data placement protocol onto SCTP, for standards track, including a clear applicability statement of the expected service from the mapping.
4) A mapping of the direct data placement protocol onto TCP, for informational, because TCP's service is a less good match to RDDP, including an applicability statement of the issues regarding the service available from the mapping.
The working group will ensure that the resulting technology will be secure and will not enable new attacks on systems supporting RDDP. The WG will not modify existing Internet transport protocols, but may forward issues it discovers in such transport protocols that are not full Internet Standards to the appropriate IETF WGs for their consideration.
| Done | Submit Internet-Draft including problem statement and architecture | |
| Done | Submit Initial draft of Remote Direct Data Placement protocol (RDDP) | |
| Done | Submit Initial draft of RDMA control protocol, to be named. | |
| Done | Initial draft mapping the RDDP core and control onto SCTP including A/S | |
| Done | Submit problem statement and architecture drafts to IESG for consideration as informational publications | |
| Done | Initial draft of security considerations for RDDP | |
| Done | Initial draft of informational mapping of the RDDP core and control onto TCP | |
| Done | Initial draft of applicability statement covering both the SCTP and TCP mappings | |
| Dec 03 | Submit RDMA control protocol (named TBD) to IESG for consideration as a Proposed Standard | |
| Dec 03 | Submit Remote Data Placement Protocol (RDDP) to IESG for consideration as a Proposed Standard | |
| Dec 03 | Submit RDDP security considerations draft to IESG | |
| Mar 04 | Consult Area Directors about any additional work the WG should undertake | |
| Mar 04 | Submit to IESG: - mapping of the RDDP core and RDMA control protocols onto SCTP for consideration as proposed standard; - mapping of the RDDP core and RDMA control protocols onto TCP for consideration as informational publications; - applicability statement for RDDP core and RDMA control protocols over both SCTP and TCP for consideration as an informational publication |
claim.Minneapolis IETF Meeting November 10-14, 2003 -------------------- Remote Direct Data Placement WG (rddp) CHAIR: David L. Black <Black_David@emc.com> The RDDP WG works on Remote Direct Data Placement and Remote Direct Memory Access functionality. For more information, please refer to the rddp charter at: http://www.ietf.org/html.charters/rddp-charter.html Letters in square brackets (e.g., [C]) are first letter of file name of corresponding presentation. TUESDAY, November 11, 2003, 0900-1130 ------------------------------------- - Agenda Bashing and Administrivia (5 min) [A] - Blue Sheets - NOTE WELL - Status of drafts (5 min) [B] - Applicability Statement (10 min) [C] (draft-ietf-rddp-applicability-01.txt) Mostly a status update. - DDP and RDMAP drafts (10 min) [D - presentation covers DDP only] (draft-ietf-rddp-ddp-01.txt, draft-ietf-rddp-rdmap-01.txt) Mostly a status update. These drafts are close to done and are likely to go to WG Last Call before the end of the year. - SCTP Mapping (10 min) (draft-ietf-rddp-sctp-00.txt) Despite the -00 version number, this is the fourth version of this draft, and it is relatively mature. There are open issues in startup model consistency with the TCP Mapping (e.g., Active/Active vs. Active/Passive). - TCP mapping (30 min) [E] (draft-ietf-rddp-mpa-00.txt) Newly adopted as a WG draft in Vienna, this draft is also on its fourth major version, but there are open issues in the area of connection initiation/startup. - Security (75 min) [F] (draft-ietf-rddp-security-00.txt) Time allocated reflects the importance of progress on this draft. - iSER/DA drafts (5 min) [G] (draft-ko-iwarp-iser-00.txt, draft-chadalapaka-iwarp-da-00.txt) These two individual submissions concern iSCSI extensions for use of RDMA. The authors would like this work to be pursued by the IETF. This time slot provides for a quick description of what these drafts cover; those interested should follow up with the authors directly (e.g., over lunc |