IMO, if a UA is given a URI to call, it generally has no business
messing with it in any way. Removing the port is altering the URI, and
should only be done by something in the domain of the URI that is
familiar with the policies for construction of URIs within that domain.
If the UA is *constructing* the URI, based on some policy rules known to
it for such construction, then it can construct one URI with the port
(for the R-URI) and one without (for the to-uri.)
Messing with URIs from other domains is like modifying a postal address
for a recipient in a foreign country. You likely don't know the
conventions for formatting postal addresses in that place and have a
good chance of rendering your mail undeliverable.
Thanks,
Paul
On 1/4/2011 10:39 AM, Iñaki Baz Castillo wrote:
> 2011/1/4 Brett Tate<br...@broadsoft.com>:
>> I'm not sure how the SIP working group intended RFC 3261 section 19.1 Table
>> 1 paragraph indicating "SHOULD ignore any disallowed components" to apply to
>> section 19.1.4's URI comparison rules.
>
> Fuly unclear. We could give our opinnion here, and any other person
> could have his own opinnion :)
>
>
>> However it might be problematic if you drop received To/From ports when
>> sending requests within dialog.
>
> IMHO it's much better just to ignore port in From/To URI when comparing URI's.
>
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
