Re: [Sipping] Draft: Essential correction for re-INVITE rollback in RFC3261

["Christer Holmberg" <christer.holmberg at ericsson.com>]

Hi, 


>1. 
>In "draft-ietf-sipping-sip-offeranswer-08.txt ", there is a use case: 
>The case of 
>adding a new media (like adding video to audio only session) which 
>requires permission from the peer through some user interaction is 
>one example. 
>From the user's viewpoint, he(or she) just reject the modification of session, so 
>the offer/answer should be rollback. 
>So, "any session
>parameters that have been sucessfully changed during the duration of
>the re-INVITE transaction MUST remain unchanged" is not reasonable for all 
>application use case. 


We have agreed that we cannot define different rules for different use-cases. We need to have a generic rule, and implementors shall then use that.

There was a long discussion on which solution to go for, and the text now reflects the agreed solution (which we also informed 3GPP about).

Regards,

Christer


	
	
	2. 
	There are nested transactions concept in application level above of offer/answer 
	which use a offer/answer pair as a sub-transaction. So, commit/rollback is not just 
	offer/answer issue, it is a application issue(such as precondition may have more than 
	one offer/answer pairs).And application level usage of offer/answer should be open for 
	the future extension. 
	
	3. 
	I just submitted a draft talking about session state 2009-01-08: 
	
	https://datatracker.ietf.org/idst/status.cgi?submission_id=11690 
	
	the document URL: 
	
	http://www.ietf.org/proceedings/staging/draft-gaoyang-sipping-session-state-criterion-00.txt 
	
	(the URL "http://www.ietf.org/proceedings/staging/draft-gaoyang-sipping-session-state-criterion-01.txt"; 
	is not available, but the 00.txt is the current one) 
	
	
	
	
	
	"Christer Holmberg" <christer.holmberg at ericsson.com> 
	发件人:  sipping-bounces at ietf.org 

	2009-01-09 17:32 

		
		收件人
		"sipping LIST" <sipping at ietf.org> 
		抄送
		
		主题
		[Sipping] Draft: Essential correction for re-INVITE rollback in        RFC3261

		





	Hi, 

	I've put together the first version of the draft related to the re-INVITE follback fix, based on the agreed solution. 

	I had some problems with the IETF submission tool, but the draft can be found at: 

	http://users.piuha.net/cholmber/drafts/draft-holmberg-sipping-reinvite-rollback-00.txt <http://users.piuha.net/cholmber/drafts/draft-holmberg-sipping-reinvite-rollback-00.txt>  

	Regards, 

	Christer _______________________________________________
	Sipping mailing list  https://www.ietf.org/mailman/listinfo/sipping
	This list is for NEW development of the application of SIP
	Use sip-implementors at cs.columbia.edu for questions on current sip
	Use sip at ietf.org for new developments of core SIP 

	
	
	--------------------------------------------------------
	ZTE Information Security Notice: The information contained in this mail is solely property of the sender's organization. This mail communication is confidential. Recipients named above are obligated to maintain secrecy and are not permitted to disclose the contents of this communication to others.
	This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the originator of the message. Any views expressed in this message are those of the individual sender.
	This message has been scanned for viruses and Spam by ZTE Anti-Spam system.
	

_______________________________________________
Sipping mailing list  https://www.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors at cs.columbia.edu for questions on current sip
Use sip at ietf.org for new developments of core SIP