70 likes | 248 Views
IFT. iWARP Framing for TCP. Keep It Simple. Assumes Data received in order from TCP and delivered in order to DDP Provide length information for record marking and DDP buffer size Provide CRC for data integrity Separate header CRC Allows verification of placement info for partial PDU
E N D
IFT iWARP Framing for TCP
Keep It Simple • Assumes Data received in order from TCP and delivered in order to DDP • Provide length information for record marking and DDP buffer size • Provide CRC for data integrity • Separate header CRC • Allows verification of placement info for partial PDU • Allows payload verification while placing data
PDU Format header_size payload_size DDP Header Header CRC DDP Payload Payload CRC
Open Issues: CRC • Two CRCs or one? • General agreement (I think??) • two CRCs make sense assuming non-aligned PDUs as in IFT/TCP • One CRC makes sense assuming aligned PDUs as in SCTP or MPA/TCP
Open Issues: Markers • Don’t think we can make progress on this until the admissibility of MPA is resolved one way or the other.
IFT Other Details • Don’t think there can be progress here either for same reason.
Future Direction • Chair and AD need to define direction that IETF will allow. • Does TCP need to be “fixed”? • Does TCP with in order placement plus SCTP cover the needs of RDDP?