El Jueves, 30 de Octubre de 2008, Francois Audet escribió: > Guys, > > Instead of using a SUBSCRIBE or even INFO, it seems appropriate > to use OPTIONS. > > By definition, OPTIONS is intended to be routed the same way > as an INVITE, and therefore would be more likly to end-up at the > right place.
Any *current* SIP device already implementing RFC 4235 already implements this draft. But if it would be handled by other request (i.e. OPTIONS) then no one of the current implementations would support this draft now, and they would need to be modified. Also, why sending dialog info into an OPTIONS while a SUBSCRIBE (Event: dialog;call-id=xxxx;to-tag=xxx) already defines it? Sending that info into an OPTIONS would require a new kind of headers or XML body. -- Iñaki Baz Castillo _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use [EMAIL PROTECTED] for questions on current sip Use [EMAIL PROTECTED] for new developments on the application of sip
