Actually, 3311 does recommend not using UPDATEs in confirmed state (below). Session timers don't use update as a target-refresh...the BCP even now could be not to use UPDATEs outside of reINVITEs 5 UPDATE Handling 5.1 Sending an UPDATE The UPDATE request is constructed as would any other request within an existing dialog, as described in Section 12.2.1 of RFC 3261. It MAY be sent for both early and confirmed dialogs, and MAY be sent by either caller or callee. Although UPDATE can be used on confirmed dialogs, it is RECOMMENDED that a re-INVITE be used instead. This is because an UPDATE needs to be answered immediately, ruling out the possibility of user approval. Such approval will frequently be needed, and is possible with a re-INVITE. ________ ________________________________ From: sipping-bounces@xxxxxxxx [mailto:sipping-bounces@xxxxxxxx] On Behalf Of Elwell, John Sent: Wednesday, February 18, 2009 5:50 AM To: Christer Holmberg; wang.libo@xxxxxxxxxx Cc: sipping@xxxxxxxx Subject: Re: About "rollback of re-Invite" Exactly, I would be concerned about changing RFC 3311. John ________________________________________ From: Christer Holmberg [mailto:christer.holmberg@xxxxxxxxxxxx] Sent: 18 February 2009 10:14 To: Elwell, John; wang.libo@xxxxxxxxxx Cc: sipping@xxxxxxxx Subject: RE: RE: About "rollback of re-Invite" Hi, I don't think we can completely forbid UPDATE outside re-INVITEs. It's just too late for that. Regards, Christer Forever, Sumit "The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man." -- George Bernard Shaw _______________________________________________ Sipping mailing list https://www.ietf.org/mailman/listinfo/sipping This list is for NEW development of the application of SIP Use sip-implementors@xxxxxxxxxxxxxxx for questions on current sip Use sip@xxxxxxxx for new developments of core SIP
