Re: [sipcore] I-D Action: draft-ietf-sipcore-sip-push-23.txt

[Christer Holmberg <[e-mail]>]

Hi Paul,


Please see inline.



 >In section 5.3:
 >
 >   5.3.  SIP URI Comparison Rules
 >
 >   When a SIP proxy compares two SIP URIs, the proxy uses the URI
 >   comparison rules defined in [RFC3261], with the following addition:
 >   the pn-prid, pn-provider and pn-param SIP URI parameters MUST also
 >   match in order for the comparison to be successful.
 >
 >   If only the pn- SIP URI parameters listed above match, but other
 >   parts of the compared URIs do not match, a proxy MAY still consider
 >   the comparison successful, based on local policy.  This can occur in
 >   a race condition, if a UA modified some parts of the Contact URI in
 >   the most recent REGISTER request, but the Request-URI of a SIP
 >   request addressed towards the UA still contains the old parts.
 >
 > I *presume* you only intend these extended matching rules to be applied
 > in certain contexts. But you don't say anything about that. Someone
 > might read this as applying to all the places in 3261 where matching is
 > used.

Good point. I do refer to the URI comparison section in the procedure sections, but it would be good to add a few words in the URI comparison section itself.

 > Please add a few more words clarifying those circumstances when these
> extended matching rules apply.

What about modifying the 1st paragraph in the following way:

"As described in the SIP proxy procedures in this specification, there are cases where the proxy will compare the Contact header field URI of a 2xx response to a REGISTER request with the Request-URI of the SIP requests in the SIP Request Push Queue (Section 5.2). In those cases, when the proxy compares two SIP URIs, the proxy uses the URI
comparison rules defined in [RFC3261], with the following addition: the pn-prid, pn-provider and pn-param SIP URI parameters MUST also match in order for the comparison to be successful."

Regards,

Christer