This should be shown as:
1. QN = 0, MSN = 1, MO = 100 L = 1 Payload = 100 bytes
Result: DDP Message (bytes 0-200) is delivered to ULP
2. QN = 0, MSN = 1, MO = 0 L = 0 Payload = 100 bytes
Result: Error is reported Invalid MSN - MSN range is not valid
This is a fatal error so there will be a teardown.
Pat
-----Original Message-----
From: Caitlin Bestler [mailto:[email protected]]
Sent: Friday, January 16, 2004 4:42 PM
To: RDDP
Cc: Barry Reinhold
Subject: Re: [rddp] DDP segment sequences for Untagged DDP message
On Jan 16, 2004, at 1:08 PM, Barry Reinhold wrote:
>
> 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
>
Did you mean to set the 'L' bit on message 1?
If so, that is a sender violation, which as explained in Paul's
response may or may not be caught by the receiver.
If Msg 1 is completed *before* Msg 2 is placed, Msg 2 will
be rejected as having an invalid MSN (it would be taken as
being 2**32-1 ahead of the current location).
In either case a 200 byte receive will be reported to the ULP.
The question is whether the Stream is almost immediately
thereafter torn down.
--
Caitlin Bestler - [email protected] - http://asomi.com/
http://asomi.com/CaitlinBestlerPublicPgpKey.html
_______________________________________________
rddp mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/rddp
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.