Hi,
     I had a query with respect to section 16.9 of bis-09
which talks about how proxies must handle transport errors.
This section states that any transport layer errors (like
ICMP errors) must be interpreted as equal to receiving a
400 Bad Request. But is this the correct response code that
a network error must be equated to ? Because in this case,
neither is the request malformed, nor is it a client error.
I would assume that the correct interpretation in this case
should be a 503. Interestingly, the 503 interpretation is
prescribed for user agents as the following line from the
"General User Agent Behaviour" section shows:

Line 1162:
"If a fatal transport error is reported by the transport
layer (generally, due to fatal ICMP errors in UDP or
connection failures in TCP), the condition MUST be treated
as a 503 (Service Unavailable) status code."

     Why is this difference of interpretation between UA's
and proxies. Shouldn't it be interpreted as a 503 at proxies
as well ? Was there some discussion/open-issue on this which
concluded that proxies must interpret network errors as 400 ?

Thanks in advance
Subhash Nayak.
Hughes Software Systems
http://www.hssworld.com







This message is proprietary to Hughes Software Systems Limited (HSS) and is
intended solely for the use of the individual to whom it is addressed.  It
may contain privileged or confidential information and should not be
circulated or used for any purpose other than for what it is intended.  If
you have received this message in error, please notify the originator
immediately.  If you are not the intended recipient, you are notified that
you are strictly prohibited from using, copying, altering, or disclosing
the contents of this message.  HSS accepts no responsibility for loss or
damage arising from the use of the information transmitted by this email
including damage from virus.


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

Reply via email to