Re: Wrong Message Length Field.

Aditya,

As long as the message is correct within the advertised length, there is no
need to send an error.  If it is too short in the header, it is because a
parameter is too long.

--brian

Aditya wrote:                                                                                                 (Tue, 17 Oct 2006 03:38:48)
> 
>    Hi all,
>    If  a M3ua Peer receive a M3UA message with message length (in Header)
>    less  than  the  actual length (but a multiple of 4) [say for example;
>    ASP  Active Ack message received with Length in the Header field as 8;
>    whereas  the actual length is 16.]; then does RFC 3332 mandate sending
>    an  error  message.  The  missing 8 bytes are not padding bytes (can't
>    be).
>    My question is also for the reverse case : actual message len is 8 but
>    the length field in the header specify it as 16.
>    All I could find was
>    Section 3.8.1
>       The "Parameter Field Error" would be sent if a message is received
>       with a parameter having a wrong length field.
>    but this talks about "parameter" and not the header.
>    Appreciate your help,
>    Aditya
> 
>    ----------------------------------------------------------------------
>    -----X----------------------------------------------------
> 
>    Don't take life too seriously...
>    Nobody comes out alive anyway
>      _________________________________________________________________
> 
>    How  low  will  we  go? Check out Yahoo! Messengers low [1]PC-to-Phone
>    call rates.
> 
> References
> 
>    1. http://us.rd.yahoo.com/mail_us/taglines/postman8/*http://us.rd.yahoo.com/evt=39663/*http://voice.yahoo.com

-- 
Brian F. G. Bidulock
[email protected]
http://www.openss7.org/