See comments inline. -Rockson
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Joseph Selvaraj Sent: Thursday, June 26, 2008 8:53 PM To: [email protected] Subject: [Sip-implementors] Query on OPTIONS response wrt ETSI testplan Hi, I have a query regarding OPTIONS handling with respect to a testcase in ETSI test plan (ETSI TS102 027-2 V 3.1.1, http://www.ipt.etsi.org/STF295-ph1/IPTlib/SIP/Documents/ts_102027_2v0301 01.htm <http://www.ipt.etsi.org/STF295-ph1/IPTlib/SIP/Documents/ts_102027_2v030 101.htm> ) ETSI: ETSI Test Spec states that "Ensure that the IUT on receipt of an OPTIONS request with a TAG set on the To header, sends a Success (200 OK) including the same URI and the same TAG for the To header." The particular test spec is given below for reference: TPId: SIP_QC_TE_ V _004 Status: Mandatory Ref: RFC 3261 <http://www.ipt.etsi.org/STF295-ph1/iptLib/BaseDocs/rfc3261.htm> [1] sections 11.2 and 8.2.6.2. Purpose: Ensure that the IUT on receipt of an OPTIONS request with a TAG set on the To header, sends a Success (200 OK) including the same URI and the same TAG for the To header. Here, no pre condition is mentioned for sending the OPTIONS request. RFC 3261: According to RFC 3261, an OPTIONS request would contain a To Tag only when sent inside of a dialog. Also Section 11.2 of RFC 3261, Para 1, states that an UAS can return 200OK or 486 depending upon the UAS status. "The response to an OPTION is constructed using the standard rules for a SIP response as discussed in Section 8.2.6. The response code chosen MUST be the same that would have been chosen had the request been an INVITE. That is, a 200 (OK) would be returned if the UAS is ready to accept a call, a 486 (Busy Here) would be returned if the UAS is busy, etc." Hence for the above testcase, a call already needs to be established, and the UAS could send either 200 or 486 depending upon its support for single call/multiple calls. Query: Should the UAC expect either 200 or 486, but check only if the same To TAG is present? Is this the real objective of this test case or does it mean something else? [Rockson] I think its objective is testing if the same To tag is returned to UAC. Whether it's 200 or 486. If IUT is a UAS, it definitely need follow 8.2.6.2 Headers and Tags If a request contained a To tag in the request, the To header field in the response MUST equal that of the request. However, the exception might be if the IUT is not a UAS, say PROXY and The OPTIONS is intended to the proxy, it may not follow sec 8 when constructing the response, Which means the to tag might not retained. Please provide your comments on this. Thanks in advance, Joseph S DISCLAIMER: ------------------------------------------------------------------------ ----------------------------------------------- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any mail and attachments please check them for viruses and defect. ------------------------------------------------------------------------ ----------------------------------------------- _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
