*From:* Roman Shpount [mailto:ro...@telurix.com] *Sent:* Sunday, May 17, 2015 10:11 PM *To:* Brett Tate *Cc:* Sip-implementors@lists.cs.columbia.edu *Subject:* Re: [Sip-implementors] RFC 7118: impacts of transport=ws on mid-dialog requests
On Sun, May 17, 2015 at 10:39 AM, Brett Tate <br...@broadsoft.com> wrote: > Does this matter if SIP Outbound (RFC 5626) and GRUU (RFC 5627) are used? As far as I know, yes. Is there something within RFC 5626 which indicates that the client can disregard the Record-Route entry (such as address, port, and transport) added by the edge device? Yes, I think RFC 5626 describes something along this ( https://tools.ietf.org/html/rfc5626#section-3.2): When the proxy goes to forward a request to a given target, it looks and finds the flows over which it received the registration. The proxy then forwards the request over an existing flow, instead of resolving the Contact URIusing the procedures in [RFC3263 <https://tools.ietf.org/html/rfc3263>] and trying to form a new flow to that contact. So, essentially flow mechanism from RFC 5626 overwrites the actual address to which the SIP message is sent and the transport used. One other comment that I had was that "sips" URI with transport parameter set to "ws" should imply requests sent over secure web sockets. I do not think there is an explicit need for "wss" URI transport. _____________ Roman Shpount _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
