Juha Heinanen wrote:
so you are going to make a change to rfc3261 just like that? if so,
what is the motivation for it? [...]
> Basically, the R-R has to be modified in the 200 OK response so that the
> Route set seen by the caller will be different than the Route set seen
> by the callee...
why?
So, please read the the draft, I cannot reword it with a smaller number
of words in the mailing list...
> So, I voluntarily omitted to discuss the "transport=TLS" use case since
> http://www.ietf.org/internet-drafts/draft-ietf-sip-sips-03.txt already
> take care of it,
> so "sips:" scheme should be used and double RR is also to be recommended
> when transiting from "sip:" to "sips:", it is described in the sip/sips
> document.
what you describe in above has nothing to do with my example where
request comes in to proxy over udp using sip uri scheme and my proxy has
an agreement with the next hop proxy that tls is used for all
communication between the two proxies.
so please tell me exactly what my proxy has to do regarding record routing.
from sip/sips document: "[RFC3261]/26.2.2 makes it clear that the use of
the "transport=tls" URI transport parameter in SIPS or SIP URIs has
been deprecated.
So, normative change recommended by this document is the following:
" Since the transport=tls URI parameter has been deprecated, it MUST NOT
be used in Route, Record-Route or Path headers, and MUST be ignored."
To be compatible with that statement, in your use case,
I think you should use double RR, on the UDP side, use a RR header with
transport=UDP or NO transport parameter (that was my question: do we
allow to put
this transport parameter in some circumstances?),
on the TLS side, do not use any transport parameter, but use the sips
scheme on RR.
Does it answer your question?
Thomas
_______________________________________________
Sip mailing list https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [EMAIL PROTECTED] for questions on current sip
Use [EMAIL PROTECTED] for new developments on the application of sip
