Re: [Sip-implementors] UPDATE RFC and dialog state inconsistency?

2008-11-06 Thread Victor Pascual Ávila
On Wed, Nov 5, 2008 at 6:03 PM, Robert Sparks <[EMAIL PROTECTED]> wrote: > You are correct. > > I think 3311 was talking about "early" vs "confirmed" when it said "state > of the dialog", but clearly the text > could be improved to avoid conflation with "dialog state" (meaning call-id, > cseqs, ta

Re: [Sip-implementors] UPDATE RFC and dialog state inconsistency?

2008-11-05 Thread Robert Sparks
You are correct. I think 3311 was talking about "early" vs "confirmed" when it said "state of the dialog", but clearly the text could be improved to avoid conflation with "dialog state" (meaning call-id, cseqs, targets, routeset, etc.) I'll capture this as a bug for future clarification. I

Re: [Sip-implementors] UPDATE RFC and dialog state inconsistency?

2008-11-05 Thread Romel Khan
UPDATE RFC3311 mentions it does not affect dialog state (eg in Abstract: "has no impact on the state of a dialog"). But the RFC later mentions that UPDATE can update remote target (eg quote: "UPDATE is a target refresh request. As specified in RFC 3261 [1], this means that it can update the remote

[Sip-implementors] UPDATE RFC and dialog state

2008-10-30 Thread Romel Khan
UPDATE RFC3311 mentions it does not affect dialog state (eg in Abstract: "has no impact on the state of a dialog"). But the RFC later mentions that UPDATE can update remote target (eg quote: "UPDATE is a target refresh request. As specified in RFC 3261 [1], this means that it can update the remote