Hi,

In ETSI TS 102 027-2 V4.1.1 (2006-07), test case SIP_CC_PR_TR_SE_V_014, it
mentioned :

<Quote>
TPId:   SIP_CC_PR_TR_SE_V_014

Status: PICS: A.77/3.2

Ref:    RFC 3261 [1] sections 17.2.2 and 17.2.3.

Purpose: Ensure that the IUT in a server BYE Proceeding state, on receipt of
a BYE request, including a Via header set with a different branch parameter
without the magic cookie "z9hG4bK" but with the Request-URI, To tag, From
tag, Call-ID, CSeq and top Via header identical as in the first BYE request,
repeats its last response.
</Quote>

But as per Via header comparison rule defined in RFC3261 20.42 Via, 

<Quote>
   Two Via header fields are equal if their sent-protocol and sent-by
   fields are equal, both have the same set of parameters, and the
   values of all parameters are equal.
</Quote>

So that one Via with different branch value, so second BYE with a different
branch parameter will never the transaction create by the first BYE, so it
shall not repeats its last response. so the test case is wrong.

Does I miss sth?

Thanks,
Lavis 




----------------------------------------------------------------------------
---------------------------------------------------------
本邮件及其附件含有华为公司的保密信息,仅限于发送给上面地址中列出的个人或群
组。禁
止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、复制、或散发)本邮
件中
的信息。如果您错收了本邮件,请您立即电话或邮件通知发件人并删除本邮件!
This e-mail and its attachments contain confidential information from
HUAWEI, which 
is intended only for the person or entity whose address is listed above. Any
use of the 
information contained herein in any way (including, but not limited to,
total or partial 
disclosure, reproduction, or dissemination) by persons other than the
intended 
recipient(s) is prohibited. If you receive this e-mail in error, please
notify the sender by 
phone or email immediately and delete it!




_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [EMAIL PROTECTED] for questions on current sip
Use [EMAIL PROTECTED] for new developments on the application of sip

Reply via email to