2008/9/8, Rockson Li (zhengyli) <[EMAIL PROTECTED]>:
> Inaki,
>
> Actually, I think this the essence of SIP proxy, have you ever imagined why
> mid-dialog req get passed through proxy?
> IMO, after proxy populates the target(s) (usually, proxy would not
> responsible for the uri,since it's remote peer's contact uri,
> the target is just the same as req-uri), so proxy would just forward the req
> based on top route if any, or req-uri.
Yes, of course, but in that case the proxy is not responsible for the
domain of RURI as you said.
> The forwarding-on-top-route policy ensure the routeset get traversed
> one-by-one.
>
> Most of proxies would have no idea of dialog, it just follow the steps to
> handle mid-dialog/out-of-dialog requests.
But they are full capable of knowing if a request is in-dialog by
examining if it has "To tag".
AFAIK, to avoid security risks a proxy usually forbids in-dialog
requests ("To tag") with a Route URI different of the proxy itself.
> And normally, there would no route header left when out-of-dialog arrives at
> proxy,
> the preloaded routeset is just a recommended way of RFC3261 to specify
> outbound proxy.
Well, but however it is a risk, isn't it?
Does make sense that a UAC or proxy adds a Route header but instead of
routing based on it, routes to a different host?
Thanks.
--
Iñaki Baz Castillo
<[EMAIL PROTECTED]>
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
