Atul,
I disagree with your answer here.
You quote section 4.3 on Proxy Behavior, but the question was about the
behavior of the subscribing UA. For that, section 4.4.1 applies. It is a
revision to 3265, and clarifies that it is the first NOTIFY that
establishes the dialog. So then section 12.1.1 of 3261 specifies what
should happen in the response to the NOTIFY.
Thanks,
Paul
On 3/20/13 10:36 PM, Atul Thosar wrote:
> Hi Andreas,
> IMHO, UAC should not mirror "Record-Route" in 200 OK response to NOTIFY
> request. Here is the reference from RFC 6665 -
>
> 4.3. Proxy Behavior
>
> Proxies need no additional behavior beyond that described in
> [RFC3261] to support SUBSCRIBE and NOTIFY transactions. If a proxy
> wishes to see all of the SUBSCRIBE and NOTIFY requests for a given
> dialog, it MUST add a "Record-Route" header field to the initial
> SUBSCRIBE request and all NOTIFY requests. It MAY choose to include
> "Record-Route" in subsequent SUBSCRIBE requests; however, these
> requests cannot cause the dialog's route set to be modified.
>
> Proxies that did not add a "Record-Route" header field to the initial
> SUBSCRIBE request MUST NOT add a "Record-Route" header field to any
> of the associated NOTIFY requests.
>
> So once the dialog is created when UAC receives 200 OK response to
> SUBSCRIBE, UAC builds the route set. This route set do not changed by
> subsequent in-dialog NOTIFY requests as per RFC 3261 -
>
> 12.2 Requests within a Dialog
> Requests within a dialog MAY contain Record-Route and Contact header
> fields. However, these requests do not cause the dialog's route set
> to be modified, although they may modify the remote target URI.
>
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
