RE: [Sipping] Should we define target refresh response? Clarification required on draft-ietf-sipping-dialogusage

["Christer Holmberg \(JO/LMF\)" <[e-mail]>]

Hi Tina,
 
The rule can be applied for middle dialog request, since UPDATE (and
re-INVITE) are mid-dialog requests.
 
Regards,
 
Christer


________________________________

	From: Tina TSOU [mailto:[e-mail]] 
	Sent: 22. syyskuuta 2006 11:51
	To: [e-mail]
	Subject: [Sipping] Should we define target refresh response?
Clarification required on draft-ietf-sipping-dialogusage
	
	
	Hi all,
	In draft draft-ietf-sipping-dialogusage, it had mentioned that
INVITE, UPDATE, SUBSCRIBE and NOTIFY and REFER are target refresh
request, but 200 class response of these requests are target refresh
response if Contact is present? 
	 
	In RFC3261 section 12.2.1.2 Para 4, it said 200 class response
of target refresh request can update remote target URI.
	 
	When a UAC receives a 2xx response to a target refresh request,
it
	   MUST replace the dialog's remote target URI with the URI from
the
	   Contact header field in that response, if present.
	 
	So, can the same rule be applied to UPDATE, SUBSCRIBE and NOTIFY
and REFER? Even for middle dialog request?
	 
	Many thanks in advance:)
	
	B. R.
	Tina
	Messengers: 
	MSN: [e-mail]   Yahoo: tina_tsou    Skype: tinaTSOU
Jabber: [e-mail]

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use [e-mail] for questions on current sip
Use [e-mail] for new developments of core SIP