RE: [Sipping] 433 error response format.

["Drage, Keith \(Keith\)" <[e-mail]>]

First draft-ietf-sip-acr-code belongs to SIP, not SIPPING and is in a state of publication requested.
 
To answer your question, the error is not time dependent, and therefore a Retry-After header is irrelevant.
 
The UAC refused to accept the request because certain conditions were not met. A reattempt is always appropriate if the conditions can be met, otherwise they will always produce the same failure. Resolution of the problem lies entirely with the UAC with no further information required from the UAS.
 
regards
 
Keith


________________________________

	From: [e-mail] [mailto:[e-mail]] 
	Sent: Thursday, April 26, 2007 10:47 AM
	To: [e-mail]
	Cc: [e-mail]
	Subject: [Sipping] 433 error response format.
	
	

	Hi All, 
	  I have a query with reference to the following lines from the draft  "draft-ietf-sip-acr-code-04.txt" 
	for 433 error response Section 4. 
	
	4 .UAC Behavior 
	
	   A UAC receiving a 433 (Anonymity Disallowed) MUST NOT retry the 
	   request without anonymity unless it obtains confirmation from the 
	   user that this is desirable.  Such confirmation could be obtained 
	   through the user interface, or by accessing user defined policy.  If 
	   the user has indicated that this is desirable, the UAC MAY retry the 
	   request without requesting anonymity. 
	
	How will the UAS indicate the UAC that it has a desire for the request to 
	be retried. Will this be communicated in some headers like that of Retry-Header. 
	Please throw some light on this issue.
	
	
	Thanks and Regards,
	Preethi..
	------------------------------------------------------------------------------
	Preethi Sadasivan,
	Software Engineer,
	ARICENT ,
	Bangalore.
	tel: [phone]
	------------------------------------------------------------------------------
	
	
	***********************  Aricent-Private   *********************** 
		"DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of 
	the individual to whom it is addressed. It may contain privileged or confidential information and should not be 
	circulated or used for any purpose other than for what it is intended. If you have received this message in error, 
	please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly
	prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for 
	loss or damage arising from the use of the information transmitted by this email including damage from virus."
	
		

_______________________________________________
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