[Sip-implementors] stream-oriented extra bytes in body ?

[Lau Jason-A13484]

Title: Message

Hi,

    For a stream-oriented transport (eg. TCP), should the SIP entity ignore extra bytes in the msg body ?

(eg. if the Content-Length says 100 bytes but if there's 120 bytes, the remaining 20 bytes are ignored/discarded)

 

    For message-oriented transport, I believe RFC3261 is pretty explicit that extra bytes in the msg body MUST be ignored. But I don't see explicit text indicating the same for stream-oriented transport ....

 

    Would appreciate your feedback. Thanks !

Regards,

    Jason

 

 

Quote: RFC3261

18.3 Framing

In the case of message-oriented transports (such as UDP), if the

message has a Content-Length header field, the message body is

assumed to contain that many bytes. If there are additional bytes in

the transport packet beyond the end of the body, they MUST be

discarded. If the transport packet ends before the end of the

message body, this is considered an error. If the message is a

response, it MUST be discarded. If the message is a request, the

element SHOULD generate a 400 (Bad Request) response. If the message

has no Content-Length header field, the message body is assumed to

end at the end of the transport packet.

In the case of stream-oriented transports such as TCP, the Content-

Length header field indicates the size of the body. The Content-

Length header field MUST be used with stream oriented transports.

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