Re: [sip-overload] draft-ietf-soc-overload-control-07 section 6.3 algorithm

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

On 03/08/2012 12:30 PM, Adam Roach wrote:
> No, now I'm even more confused. I have a rather long list of things I
> think need to change here, but I don't want to throw them all out for
> fear of them being confused with each other.
>
> Let's start simple, with the most fundamentally important question:
> where is "get_sip_msg()" getting a message from?
>
> (a) Some internal queue of outgoing SIP messages to be sent to the network
> (b) A network interface (or some abstraction thereof) representing
> incoming SIP messages
> (c) Somewhere else

So I fail to see the need to pin down exactly where it is getting
these messages from?  From the processing point of view, the
algorithm (being executed at a client upstream of the overloaded
server) gets a SIP message and it has to decide if it is a
request or response.  The host executing this algorithm could be a
UAC, in which case it is getting SIP responses from the network
and it is getting SIP requests from its TU.  Or, that host could be a
proxy, in which case it is getting (in a sense) both requests and
responses from the network.

If a response, the algorithm extracts the oc parameters and creates the
oc context for the server that filled in the oc parameters.  If it is
a request, it decides whether the request is destined to server
that indicated oc before.

We can chat over the phone if that will make the convergence process
faster?

- 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/