Imported from previous forum
[ original email was from Graham Britten - Graham.Britten@helio.demon.co.uk ]
Is the RawData field of necessary?
Considering the BodyLength must be in the range 0-9999 (i.e 10K - space required for other fields) then the amount of data which can be inserted into the RawData field is somewhat limited. Also no content oriented parameters are defined to indicate what the RawData is i.e. Filename, encoding (Compressed), character set (Multibyte, ASCII etc)
The SecureData field if used to encrypt the message body also imposes limits on the space available for the other fields - IMHO encyption should be applied at a higher level so as not to impact the integrity of the message( and simplify processing).
RawData has been and is currently used to support PGP-DES-MD5 encryption. The PGP encrypted block containing the session key and initialization vectors is provided via the RawData field in the Logon.
> Is the RawData field of necessary?
>
> Considering the BodyLength must be in the range 0-9999 (i.e 10K - space required for other fields) then the amount of data which can be inserted into the RawData field is somewhat limited. Also no content oriented parameters are defined to indicate what the RawData is i.e. Filename, encoding (Compressed), character set (Multibyte, ASCII etc)
>
> The SecureData field if used to encrypt the message body also imposes limits on the space available for the other fields - IMHO encyption should be applied at a higher level so as not to impact the integrity of the message( and simplify processing).
>
>
>