On Wed, 2005-11-02 at 09:31 -0500, Paul Kyzivat wrote: > IMO REFER is a very troublesome method. It looks like a single request > with a bunch of options. But it doesn't say much about what the > recipient should do. For example, when using REFER with the INVITE > method, the recipient must do an INVITE. But there is [no? --DRW] explicit > indication about how the recipient should manage its end of the invite - > what media should be offered, how they should be connected to media > handling resources in the UA, etc.
It's not even clear how the REFER should modify the existing set of dialogs (much less the media streams). At one point I counted that there were three semantically different (but syntactically identical) uses of REFER in various RFCs and I-Ds. These could be distinguished by context, but what disturbed me was that nobody seemed to be aware that they were semantically different and were actually three different standards. Dale _______________________________________________ Sip-implementors mailing list [email protected] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
