In the case of a response, if either (1) the message body is larger then the Content-Length header field (causing bytes to be discarded prior to sending) or (2) the transport packet ends before the message body (causing message to be discarded), are these 2 conditions considered "parameter problem errors" and handled by the following paragraph in section 18.4 "Error Handling".
If the transport user asks for a message to be sent over an unreliable transport, and the result is an ICMP error, the behavior depends on the type of ICMP error. Host, network, port or protocol unreachable errors, or parameter problem errors SHOULD cause the transport layer to inform the transport user of a failure in sending. Source quench and TTL exceeded ICMP errors SHOULD be ignored. Note, in the first condition the message is still sent (albeit a bit shorter to match the Content-Length header field). Is that still considered an error. I believe the fact that the message is still sent differs from the implied text meaning in the above paragraph of "failure in sending" (i.e. all of the error conditions mentioned in this paragraph indicate that the message is not sent). ----------- In addition, some typo's in the draft - Sec 16.12.1.3; "PI" -> "P1" s/U2 sends this 200 (OK) back to PI:/U2 sends this 200 (OK) back to P1: Sec 17.1.1.2; "r" -> "a" s/The formal definition of r transmit/ The formal definition of a transmit Sec 18.2.1; "received" -> "receive" s/A server SHOULD be prepared to received requests on any IP address,/A server SHOULD be prepared to receive requests on any IP address, "a" -> "" s/request or a any redirect response/request or any redirect response ---------- Thanks Ken _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
