DDP segment sequences for Untagged DDP message
"Barry Reinhold" <[email protected]>
| Newsgroups | gmane.ietf.rddp |
|---|---|
| Message-ID | <000601c3dc64$2c913520$467fa8c0@i8600> |
So, is there agreement, for the sequences that follow, that the specified "result" given below is the correct (and desired?) behavior as defined by the 01 draft. Untagged DDP Segment Sequences: 1. QN = 0, MSN = 1, MO = 100 L = 1 Payload = 100 bytes 2. QN = 0, MSN = 1, MO = 0 L = 0 Payload = 100 bytes Result: DDP Message (bytes 0-200) is delivered to ULP 1. QN = 0, MSN = 1, MO = 100, L = 0, Payload = 100 bytes 2. QN = 0, MSN = 1, MO = 0, L = 1, Payload = 100 bytes Result: ULP sent Error type=Untagged Buffer Error, Error Code=Invalid MO 1. QN = 0, MSN = 1, MO = 0, L = 0, Payload = 100 bytes 2. QN = 0, MSN = 1, MO = 0, L = 1, Payload = 100 bytes Result: DDP Message (bytes 0-100) is delivered to ULP 1. QN = 0, MSN = 1, MO = 000, L = 0, Payload = 100 bytes 2. QN = 0, MSN = 1, MO = 200, L = 1, Payload = 100 bytes Result: DDP Message (bytes 0-300) is delivered to ULP 1. QN = 0, MSN = 1, MO = 300, L = 1, Payload = 100 bytes Result: DDP Message (bytes 0-400) is delivered to ULP (This is based on wording in 6.3, MO field. Note that the second sentence simply says that the MO "that references the first octet MUST be set to zero", not that a segment having a zero MO is required) 1. QN = 0, MSN = 1, MO = 100, L = 0, Payload = 100 bytes 2. QN = 0, MSN = 1, MO = 000, L = 1, Payload = 0 bytes Result: ULP sent Error type=Untagged Buffer Error, Error Code = Invalid MO (There is ambiguity between 6.1 L bit field description ( Segment w/ L bit set must have highest MO), and 9.1 (implies that for non-zero length segments the header fields are not validated.) 1. QN = 0, MSN = 1, MO = 000, L = 0, Payload = 100 bytes 2. QN = 0, MSN = 1, MO = 100, L = 1, Payload = 0 bytes Result: DDP Message (bytes 0 - 100) is delivered to ULP 1. QN = 0, MSN = 1, MO = 100, L = 1, Payload = 0 bytes Result: DDP Message (bytes 0 - 100) id delivered to ULP. Barry Reinhold Lamprey Networks [email protected] (603) 868-8411