On 7/25/07 1:49 PM, Dean Willis wrote:
It seems to me that we have a quandary -- if we accept the "Add a new
method type for each application" model, then we should deprecate RFC
3265, instead adding new SIP methods like SUBSCRIBE-KPML and NOTIFY-KPML.
No, not really.
In pursuing such a model, you're effectively arguing that INVITE should
be split into INVITE-AUDIO, INVITE-VIDEO, INVITE-AUDIO-VIDEO, etc. Why
didn't we? Because pretty much all the SIP protocol semantics are
identical regardless of what kind of INVITE session you're setting up.
Identically, just about all of the SIP protocol semantics are identical
for SUBSCRIBE and NOTIFY, _regardless_ of the event package being used.
/a
_______________________________________________
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
