RFC 3581 implies that these two are for UDP, though not explicitly called out.
>-----Original Message----- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] On >Behalf Of Iñaki Baz Castillo >Sent: Wednesday, July 23, 2008 5:11 PM >To: sip-implementors@lists.cs.columbia.edu >Subject: [Sip-implementors] Is "received" and "rport" used in SIP TCP? > >Hi, I'm realizing that "received" and "rport" are completely >useless in SIP >TCP: > >- The client MUST reply using the existing conecction that >creates the incoming request. So for now "received" and >"rport" are not used at all. > >- If the connection fails during the reply then the UAS/proxy >must perform steps in RFC3263 as failover, and those steps >mean sending the response to "sent-by". So again "received" >and "rport" is not used. > >- Also take in mind that when a UAC establishes a TCP >connection with UAS it uses an arbitrary source port so if the >connection fails the UAS cannot open a new connection to that >original source port (except using "alias" extension that it's >not relevant now). > >So, the conclusion is: "received" and "rport" parameters are >completely useless in SIP TCP, is it? > >Thanks for any comment. > > >-- >Iñaki Baz Castillo > >_______________________________________________ >Sip-implementors mailing list >Sip-implementors@lists.cs.columbia.edu >https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
