Skip to main content

Re: SIP services adjustment - 16.7 Response Processing

2 replies [Last post]
ivelin
Offline
Joined: 2003-07-13
Points: 0

>
> 16.7 Process Response
> 16.7.1 - Find response context - IES = Call-ID + ?

Its only a concern for stateful proxies so no need to worry about it for now.

> 16.7.2 - Update C-Timer =???

Looks like a concern for stateful proxies only.

>
> 16.7.4-6 - DOnt fully understand those points. It not
> said straight but:
> - if some response comes proxy waits for all other
> CTx to receive response

Section 16.11 "Stateless Proxy" seems to simplify things quite a bit for the interpretation of 16.7. 16.11 reads:

"Response processing as described in Section 16.7 does not apply to a proxy behaving statelessly. When a response arrives at a stateless proxy, the proxy MUST inspect the sent-by value in the first (topmost) Via header field value. If that address matches the proxy, (it equals a value this proxy has inserted into previous requests) the proxy MUST remove that header field value from the response and forward the result to the location indicated in the next Via header field value. The proxy MUST NOT add to, modify, or remove the message body. Unless specified otherwise, the proxy MUST NOT remove any other header field values. If the address does not match the proxy, the message MUST be silently discarded."

Does this still leave open questions for 16.7?

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
mranga
Offline
Joined: 2003-06-06
Points: 0

> >
> > 16.7 Process Response
> > 16.7.1 - Find response context - IES = Call-ID + ?
>
> Its only a concern for stateful proxies so no need to
> worry about it for now.
>
> > 16.7.2 - Update C-Timer =???
>
> Looks like a concern for stateful proxies only.
>
> >
> > 16.7.4-6 - DOnt fully understand those points. It
> not
> > said straight but:
> > - if some response comes proxy waits for all other
> > CTx to receive response
>
> Section 16.11 "Stateless Proxy" seems to simplify
> things quite a bit for the interpretation of 16.7.
> 16.11 reads:
>
> "Response processing as described in Section 16.7
> does not apply to a proxy behaving statelessly. When
> a response arrives at a stateless proxy, the proxy
> MUST inspect the sent-by value in the first (topmost)
> Via header field value. If that address matches the
> proxy, (it equals a value this proxy has inserted
> into previous requests) the proxy MUST remove that
> header field value from the response and forward the
> result to the location indicated in the next Via
> header field value. The proxy MUST NOT add to,
> modify, or remove the message body. Unless specified
> otherwise, the proxy MUST NOT remove any other header
> field values. If the address does not match the
> proxy, the message MUST be silently discarded."
>
>
> Does this still leave open questions for 16.7?

Ivelin, Not sure why you are starting new threads.

I agree that stateless proxy server is the way to go. Now I am wondering about the SIP RA. The SIP RA does not support stateless operation. There is no message activity. So how can we address that? I think stateless proxying is a very important use case that the SIP RA should address. After all JSIP does support that. Why restrict the possibility in JSIP RA ?

Ranga

ivelin
Offline
Joined: 2003-07-13
Points: 0

>
> Ivelin, Not sure why you are starting new threads.
>

there are multiple separate sub-topics involved. the original thread grew fast to a point where it wasn't easy to follow the discussions.