[sipcore] About O/A rules in RFC3261:

gao.yang2@zte.com.cn Wed, 07 April 2010 03:41 UTC

To: sipcore@ietf.org, Gonzalo.Camarillo@ericsson.com
MIME-Version: 1.0
Message-ID: <OFE7586C91.FFEBAA87-ON482576FE.000EC077-482576FE.00143AA3@zte.com.cn>
From: gao.yang2@zte.com.cn
Date: Wed, 07 Apr 2010 11:39:18 +0800
Content-Type: multipart/alternative; boundary="=_alternative 00143AA1482576FE_="
Subject: [sipcore] About O/A rules in RFC3261:
Precedence: list

Hi,

While considering one problem in our productions' interoperability 
testing, I re-read some parts of offeranswer draft and correlative part of 
RFC3261. And I find a potential description problem in RFC3261 
incidentally.

//correlative part of RFC3261
o  If the initial offer is in an INVITE, the answer MUST be in a
         reliable non-failure message from UAS back to UAC which is
         correlated to that INVITE.  For this specification, that is
         only the final 2xx response to that INVITE.  That same exact
         answer MAY also be placed in any provisional responses sent
         prior to the answer.  The UAC MUST treat the first session
         description it receives as the answer, and MUST ignore any
         session descriptions in subsequent responses to the initial
         INVITE.

As the text allow UAS send SDP before the final answer, the first session 
description UAC receives can not be treated as answer in such cases. And 
the current text defines that UAC MUST ignore any SDP in subsequent 
responses to the initial INVITE. whick may make the UAC ignore the real 
answer in some case.

I think the description should be: 
The UAC MUST treat the first session description which is in a reliable 
non-failure message it receives as the answer, and MUST ignore any session 
descriptions in subsequent responses to the initial INVITE.

And if the problem is exist, where should be the correction's location?
I think draft-ietf-sipcore-reinvite-03 is not proper, as it aims for 
Re-INVITE. And a new draft for such tiny *potential* problem is also not 
proper.

Thanks,

Gao

===================================
 Zip    : 210012
 Tel    : 87211
 Tel2   :(+86)-025-52877211
 e_mail : gao.yang2@zte.com.cn
===================================

--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail is solely property of the sender's organization. This mail communication is confidential. Recipients named above are obligated to maintain secrecy and are not permitted to disclose the contents of this communication to others.
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the originator of the message. Any views expressed in this message are those of the individual sender.
This message has been scanned for viruses and Spam by ZTE Anti-Spam system.

[sipcore] About O/A rules in RFC3261: gao.yang2