[On request, splitting my previous question in separate emails,
and this is the last.]
Greetings fellow SIPers!
I've got a few questions regarding how I should interpret a few things
in rfc3263, and related text in 3261.
===========
Question 3.
===========
The annoying 503 Response and "Retry-After:"...
I have read the archive and the fairly new RFC on congestion-handling,
but neither seems to clarify, or even mention that the text in 3261,
(that is referred to in rfc5390) is completely self-contradicting,
to me at least...
The discussion is always on how long you should blacklist, and wether
to use this for overload protection or not..
3261:
If no Retry-After is given, the client MUST act as if it had
> received a 500 (Server Internal Error) response.
A client (proxy or UAC) receiving a 503 (Service Unavailable)
SHOULD attempt to forward the request to an alternate server.
It SHOULD NOT forward any other requests to that server for the
> duration specified in the Retry-After header field, if present.
To me, this says that any 503 response without R-A, is NOT a 503.
So how can the text in the next paragraph, say that if you receive any
kind
of 503(even without Retry-After, since it says "if present") you SHOULD
retry somewhere else??
And then we have 3263, which generically says "if you receive a 503, you
should retry the next dns-rr". But since I always see 3261 as the
master-of-all-rules, I intepret this as you should ONLY perform this
retry,
IF the 503 you just got, HAD a Retry-After.
Since we've already defined that a 503 w/o R-A, is not, in fact,
a 503 but a 500.....or have we? :-@
So. If my proxy receives a 503 without R-A, should I, according to
3261/3
fetch the next RR and retry?
I'd be very interessted, and thankful for whatever feedback you folks
can provide.
Thanks in advanced
Regards
Taisto Qvist
IP-Solutions AB
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
