Frank Shearar wrote: > draft-ietf-sipping-cc-transfer section 5 tells us that we can use GRUUs to > associate an out-of-dialog REFER to an INVITE dialog usage.
That's not correct, actually. A GRUU is used to ensure that an out-of-dialog REFER reaches the UA which is the endpoint of the INVITE dialog usage (because the AOR used in the INVITE may not route to the same UA now). The Target-Dialog header in the REFER is used by the transferee UA to associate the REFER with the correct dialog usage. (See items 1-3 in section 5, and the paragraph following.) Using a GRUU alone to determine the target dialog usage is impossible, as that GRUU could be participating in many dialogs. "Paul Kyzivat" <[EMAIL PROTECTED]> wrote: > I think somewhere there was a 3pcc case where it made some sense to tell > a remote user to do a BYE on some session it had. In that case I think > it was proposed to use a REFER where the the Refer-To [URI] had a > [method]=BYE [parameter]. Either in 3pcc or the conferencing I-Ds. And the concept was that the UA that received the REFER would be directed to send a BYE within the target-dialog, thus terminating the dialog. From: "Frank Shearar" <[EMAIL PROTECTED]> wrote: > this is a big wide world and someone somewhere WILL send my stack an > out-of-dialog BYE, and what should I do about it. I can't imagine anything other than an error, as BYE only operates on the INVITE dialog usage of the dialog the BYE is within. Dale _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
