Hi,
I have same thought about it as yours.
But in Ganzalo's draft, the new dialog state MUST be discarded by 4xx of
Re-INVITE.
The main branching is about the relationship of Re-INVITE and UPDATE. I have
seen your supporting of view 2. Abd we need more people to show their
standpoint.
Gao
From: [email protected]
To: [email protected]; [email protected]; [email protected]
Date: Thu, 12 Mar 2009 04:57:06 -0700
Subject: Re: [Sipping] [Sip] One chart //"UPDATE during Re-INVITE" discussion
Data (like Contact, Session-Expires, and etcetera) that was successfully
updated by F3/F4 still apply after F7. Thus F8 data should reflect (and can
attempt to modify) adjustments made during F3/F4.
From: [email protected] [mailto:[email protected]] On Behalf Of
[email protected]
Sent: Wednesday, March 11, 2009 11:47 PM
To: SIP; SIPPING
Cc: Gonzalo Camarillo; Christer Holmberg
Subject: [Sip] One chart //"UPDATE during Re-INVITE" discussion
UAC UAS
| session established |
|<===================>|
| |
| F1 re-INVITE (SDP) |
|-------------------->|
| F2 1xx-rel (SDP) |
|<--------------------|
| F3 UPDATE |
|<--------------------| Target refreshing
| F4 2xx UPT |
|-------------------->|
| |
| F5/6 Cancel/200OK |
|-------------------->|
| F7 487 INV |
|<--------------------|
| F7 ACK |
|-------------------->|
| F8 re-INVITE (SDP) |
|-------------------->| Using which dialog state
F3/F4 is about target refreshing.
And if UAC sends Cancel， UAS sends 487. The first Re-INVITE is discarded.
But if UAC sends another Re-INVITE, which dialog state should it use?
I think is the one refreshed by F3. That's the merit of regarding
UPDATE/200OK's atomicity.
_________________________________________________________________
MSN 表情魔法书，改变你的对话时代！
http://im.live.cn/emoticons/_______________________________________________
Sip mailing list https://www.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
