|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] R2TDataSN> R2TDataSN > ---------- > Sec 6.7.1 has some new content on how to handle lost R2Ts using > SACKs. But I noticed that the SACK request (Sec 2.16) has not > changed to indicate whether the DataSN is a R2T DataSN or just > a Read PDU DataSN (D bit) > So do we demux on the read/write operation type? > And how does this affect PDU loss in bidirectional commands ? > +++ SACK is ascking for data (DataSN) the target knows > Julian, Regarding the R2TDataSN, I have a comments and a question. I think that when a PDU header fails a CRC/checksum check etc, it is a problem to depend on any information in the header (including length fields), thereby making any further processing on the connection unreliable. What scenarios do you envision where the R2TDataSN is useful. IN Orlando I think there was clear consensus that application do not try to transfer very large amounts of data using a single command. Thanks, Somesh _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
Home Last updated: Tue Sep 04 01:05:27 2001 6315 messages in chronological order |