A pair of sharp eyes caught a couple of related issues
in the RDDP Architecture RFC:
http://www.rfc-editor.org/errata_search.php?eid=136In summary, the first prototype for rdma_read is:
rdma_read(socket_t s, ddp_addr_t s, ddp_addr_t d);
and the second prototype doesn't match:
rdma_read(socket_t s, ddp_addr_t s, length_t l, ddp_addr_t d)
plus the second prototype has two arguments that are both
named "s". Oops ...
I believe that the correct fix is that the length argument
from the second prototype needs to be in both prototypes,
and the DDP buffer argument "s" (source) should be renamed
to "rs" (remote source) in both prototypes in order to
avoid a name conflict with the socket argument.
If anyone disagrees, please respond.
Assuming this approach is ok, I propose to carry it out
as follows:
- I will file a new erratum with the above two changes
- I will then ask the RFC Editor to reject the original
erratum, as it contains a correction for only one
of the two problems that it identifies.
Thanks,
--David
----------------------------------------------------
David L. Black, Distinguished Engineer
EMC Corporation, 176 South St., Hopkinton, MA 01748
+1 (508) 293-7953 FAX: +1 (508) 293-7786
black_david@... Mobile: +1 (978) 394-7754
----------------------------------------------------
_______________________________________________
rddp mailing list
rddp@...
https://www.ietf.org/mailman/listinfo/rddp
