Clarification on intent of requirement

Clause 5 item 4 of draft-ietf-rddp-ddp-01 states:

   4.  The LLP MUST preserve DDP Segment and Message boundaries at the 
       Data Sink. 

For the LLP to preserve the DDP segment boundary I would expect that the
LLP (MPA/SCTP) would, in some virtual API, provides an indication that
the DDP segment is available (i.e. the full DDP segment is available in
some buffer and is without error). Given an API this could be tested.

I am not clear on what the LLP is supposed to do with a DDP message
boundary. A DDP message boundary is defined by a bit in a DDP header and
the semantics associated with processing a DDP message do not seem to be
appropriate for the LLP. In what way is the LLP supposed to "preserve" a
DDP message? 



Barry Reinhold
Lamprey Networks
[email protected]
(603) 868-8411