This is absolutely correct. RFC3581 sec3
A client, compliant to this specification (clients include UACs and proxies), MAY include an "rport" parameter in the top Via header field value of requests it generates. This parameter MUST have no value; it serves as a flag to indicate to the server that this extension is supported and requested for the transaction. Sec4 If this Via header field value contains an "rport" parameter with no value, it MUST set the value of the parameter to the source port of the request. And 6. Example A client sends an INVITE to a proxy server which looks like, in part: INVITE sip:[EMAIL PROTECTED] SIP/2.0 Via: SIP/2.0/UDP 10.1.1.1:4540;rport;branch=z9hG4bKkjshdyff Regards, -Rockson -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of I?aki Baz Castillo Sent: Wednesday, June 25, 2008 3:40 PM To: sip-implementors@lists.cs.columbia.edu Subject: Re: [Sip-implementors] Bug in RFC 3581 (rport) ? El Wednesday 25 June 2008 03:34:26 Rockson Li (zhengyli) escribió: > I think RFC3581 is primarily used in NAT transversal, Making the > received and rport addition mandatory is to speed up response > delivery This is not against RFC3261, UA compliant with RFC3581 also > is compliant with RFC3261 in this respect. I've realized that some UAS and proxies set the "rport" param but don't add "received" parameter (if it's not necessary). For example: - Request from 1.2.3.4:5080 received from 1.2.3.4:5999 with this "Via": Via: SIP/2.0/UDP 1.2.3.4:5080;rport;branch=qweqweqwe - The reply sent by the UAS/proxy is: Via: SIP/2.0/UDP 1.2.3.4:5080;rport=5999;branch=qweqweqwe Is it incorrect then? is mandatory adding "received" parameter (even if not neccesary in RFC3261) if the UAS/proxy is RFC3581 compliant and the request comes with "rport" parameter? -- Iñaki Baz Castillo [EMAIL PROTECTED] _______________________________________________ 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
