Hello and thanks for the response.

The issues are:

1. If the message is text and there is no CRLF required at the end of the
   body, there could be cascading errors caused by a single incorrectly
   specified content-length header (there is no way to synchronize).

2. SDP requires that there be a CRLF terminating each line
   and blank lines are not allowed in the SDP part. I have
   come across some implementations that leave out the trailing CRLF
   after the SDP body (and compute the content-length accordingly) so
   there is no way to distinguish between message boundaries other than
   through the content-length header. I want to know if I should
   accept or reject such messages.

3. If the body is not required to be encoded into text, this makes it quite
   difficult to deal with for stream-oriented processing where you have
   to know the content-length to know how much of the body follows the
   message. (And besides, it deviates from the text-only goal of SIP.)


Thanks

Ranga.



On Wed, 8 Aug 2001, Ranjit K A wrote:

> Hi
>
>     See my comments inline.....
>
>
> Regards
> Ranjit
>
>  -----Original Message-----
> From:         M. Ranganathan [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, August 08, 2001 9:27 AM
> To:   [EMAIL PROTECTED]
> Subject:      [Sip-implementors] Question: Content-Length computation and binary
> data bodies.
>
>
> Hello!
>
> This might appear to be a nitpicky question but is of importance to TCP
> impementations interoperability:
>
>
> Does the content-length computation include the CRLF at the end of a
> message
> body?
>
>             Usually content length is the total number of bytes . it is
> independent of what bytes
>                represent be it CRLF, or  anything else to terminate lines.
>
>
> Second, is the body of the message always encoded as text (for example
> using
> base-64 encoding) or can it be binary data?
>
>             I think both are possible.
>
> Thanks.
>
> Ranga.
>
>
> --
> M. Ranganathan
> Advanced Networking Technologies Divsion
> National Institute of Standards and Technology (NIST)
> 100 Bureau Drive, Stop 8920, Gaithersburg, MD 20899.
> Tel: 301 975 3664 ; Fax: 301 590 0932
>
> Advanced Networking Technologies For the People!
>
>
> _______________________________________________
> Sip-implementors mailing list
> [EMAIL PROTECTED]
> http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
>
> _______________________________________________
> Sip-implementors mailing list
> [EMAIL PROTECTED]
> http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
>

-- 
M. Ranganathan
Advanced Networking Technologies Divsion
National Institute of Standards and Technology (NIST)
100 Bureau Drive, Stop 8920, Gaithersburg, MD 20899.
Tel: 301 975 3664 ; Fax: 301 590 0932

Advanced Networking Technologies For the People!


_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors

Reply via email to