[Sipping] 433 error response format.

Preethi.Sadasivan@aricent.com Thu, 26 April 2007 09:47 UTC

Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hh0Zg-0000w6-CP; Thu, 26 Apr 2007 05:47:40 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43) id 1Hh0Zf-0000w1-4I for sipping-confirm+ok@megatron.ietf.org; Thu, 26 Apr 2007 05:47:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hh0Ze-0000vt-OS for sipping@ietf.org; Thu, 26 Apr 2007 05:47:38 -0400
Received: from [203.187.132.25] (helo=tapal.aricent.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hh0Zd-0003Oh-17 for sipping@ietf.org; Thu, 26 Apr 2007 05:47:38 -0400
Received: from tapal.aricent.com (localhost [127.0.0.1]) by tapal.aricent.com (8.13.8/8.13.8) with ESMTP id l3Q9kGP9030417 for <sipping@ietf.org>; Thu, 26 Apr 2007 15:16:16 +0530
Received: from pragati.blr.hss.hns.com (pragati.blr.hss.hns.com [10.203.193.22])by tapal.aricent.com (8.13.8/8.13.8) with ESMTP id l3Q9kGiY030414for <sipping@ietf.org>; Thu, 26 Apr 2007 15:16:16 +0530
To: sipping@ietf.org
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.5 November 30, 2005
Message-ID: <OF6934D3A1.1CC2A5F1-ON652572C9.0034FFBD-652572C9.0035F075@flextronicssoftware.com>
From: Preethi.Sadasivan@aricent.com
Date: Thu, 26 Apr 2007 15:17:29 +0530
X-MIMETrack: Serialize by Router on Pragati/BLR/HSS(Release 6.5.5|November 30, 2005) at04/26/2007 03:13:43 PM,Serialize complete at 04/26/2007 03:13:43 PM
X-imss-version: 2.046
X-imss-result: Passed
X-imss-scanInfo: M:B L:N SM:2
X-imss-tmaseResult: TT:1 TS:-15.5478 TC:1F TRN:53 TV:3.6.1039(15138.002)
X-imss-scores: Clean:100.00000 C:0 M:0 S:0 R:0
X-imss-settings: Baseline:2 C:1 M:1 S:1 R:1 (0.0000 0.0000)
X-Spam-Score: 0.3 (/)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Cc: Preethi.Sadasivan@aricent.com
Subject: [Sipping] 433 error response format.
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1975704558=="
Errors-To: sipping-bounces@ietf.org

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: +91-80-41069118
------------------------------------------------------------------------------


***********************  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 sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP