Re: [sip-overload] WG Last Call for draft-ietf-soc-overload-control-12

["Vijay K. Gurbani" <[e-mail]>]

On 02/11/2013 02:59 AM, [e-mail] wrote:
> I just have one comment:
>
> Section 5.10.2 says that the response sent by a SIP server to
> non-participants clients in case of overload is a 503 without the
> Retry-After header. I did not find any text about the response sent by
> participating clients when they have to reject a request. I assume they
> should send a 503 without the Retry-After header as well. I would
> suggest adding the following sentence at the end of 5.10, after “it will
> need to reject these requests”: In such cases, the SIP client shall
> reply to the requests with a 503 response without the Retry-After header.

Bruno: Sorry for the delay.  Catching up with pending email on SOC.

I had a look at Section 5.10.2 and Section 5.10 where you propose to add
the above sentence.

S5.10 talks about a "SIP client" --- I am trying to figure out if we
meant a UAC or a proxy.

If this is a proxy, then the behaviour of that is already enumerated in
S5.10.2 using the same sentence you specify above.

If this is a UAC and it supports overload control, then it has already
received overload control feedback from the downstream overloaded
server.  It will act accordingly.

If this is a UAC and it does not support overload control, then it will
simply wait for a final response from the downstream server.  The UAC,
since it does not support overload control, will unfortunately keep
sending requests downstream.

As such, I am not sure if we need to add anything at all.  But I am open
to suggestions.

Thanks,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
Email: vkg@{bell-labs.com,acm.org} / [e-mail]
Web:   http://ect.bell-labs.com/who/vkg/