The topic is more fully discussed within draft-ietf-sipcore-reinvite. > -----Original Message----- > From: [email protected] [mailto:sip- > [email protected]] On Behalf Of Sachin Rastogi > Sent: Saturday, January 09, 2010 8:56 AM > To: hanifa.mohammed > Cc: sip-implementors > Subject: Re: [Sip-implementors] Updating the remote target set! > > Hi Hanifa, > As refer *section 12.2.2 UAS Behavior of Rfc 3261* > > " Requests sent within a dialog, as any other requests, are atomic. > *If* > * a particular request is accepted by the UAS, all the state changes* > * associated with it are performed. If the request is rejected, > none* > * of the state changes are performed.* > > Note that some requests, such as INVITEs, affect several pieces > of > state. > --------------- > -------- > ------- > When a UAS receives a target refresh request, it MUST replace the > dialog's remote target URI with the URI from the Contact header > field > in that request, if present. > " > And as per *section 12 Dialogs of rfc 3261,* A Dialog state consist of > the > dialog > ID, a local sequence number , a remote sequence number , a local > URI, a > remote URI, remote target, a boolean flag called "secure", and a > route > set. > > Please also refer *section 5.4. Target Refresh Requests of rfc 5057* > which > says > > "Target refresh requests *update the remote target of a dialog when* > * they are successfully processed*. The currently defined target > refresh requests are INVITE, UPDATE, SUBSCRIBE, NOTIFY, and REFER > [7])." > > > So your assumption is correct as per my understanding of above rfcs > that remote > target set should be updated only when 2xx is sent, whether the request > is reINVITE or UPDATE. > > Best Regards, > Sachin Rastogi
_______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
