Paul,
I don't see any reason why *proxy* middle boxes need to know anything
about this. B2BUAs will need to know, but then they will know.
There are (as always) subtle differences. NOTIFY for SUBSCRIBE is needed
to handle forking (proxies pass at most 1 2xx response for SUBSCRIBE),
while NOTIFY for INVITE would not be needed for this reason. Proxies
Record-Route NOTIFY due to the above reason, they could avoid doing that
for INVITE-NOTIFYs. Record-Routing INFO is useless and somewhat
wasteful, so well designed proxies don't do that.
Also, I assume there will be no need to "immediately send NOTIFY" for
INVITE-based events.
All in all, IMO using INFO instead of NOTIFY here is preferrable (also
given that existing implementations already use INFO within INVITE
dialogs).
Regards,
Jeroen
_______________________________________________
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
