RE: DDP/RDMAP Applicability

These are additional paragraphs that would address the questions raised:


In 6.6 (data integrity implications)

   CRC32c only provides protection against random corruption.  To
   protect against unauthorized alteration or forging of data packets
   security methods must be applied.  Use of IPSEC is supported for 
   both SCTP and MPA/TCP.


In 9.1 (Security Consideratins - Connection/Association Setup)

   Authentication of peers and approval of connections is outside of the
   scope of DDP.  Connections are initiated and accepted by the ULP
   using authentication information as provided by the LLP.  IPSEC is
   usable for both TCP and SCTP.

In 9.2 (Security Considerations - Tagged Buffer Exposure)

   DDP validates that STags are only used by the remote peer to the
   extent authorized by the ULP.  The STag is selects amongst authorized
   buffers; an STag by itself does not authorize access.  Spacing STags
   is more a defense against 'off by one' errors than a cryptographic
   protection.