Wouldn't the best approach be to supersede the INFO RFC with one which
takes care of issues, i.e. with these additional headers.
We can't get people to change the old implementations, but at least the
for new usages if the additional work required is a smaller delta (from
base INFO, as compared to having to implement SUBSCRIBE/NOTIFY), they
might be more amenable to use the new EVENT based INFO mechanism.
Frankly, I think what we are discussing would be better applied using
NOTIFY in the INVITE dialog. We would then be devising a new means to
negotiate event packages that will share the invite dialog, but using
the same NOTIFY messages to carry the data, not INFO.
Paul
FWIW, I agree with Paul here.
Thanks,
Spencer
_______________________________________________
Sip mailing list https://www1.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
