Re: [sipcore] Dialog state - Scope in draft-ietf-sipcore-reinvite //Request for other people's following up.

gao.yang2@zte.com.cn Mon, 12 July 2010 09:35 UTC

Return-Path: <gao.yang2@zte.com.cn>
X-Original-To: sipcore@core3.amsl.com
Delivered-To: sipcore@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 98D513A6914 for <sipcore@core3.amsl.com>; Mon, 12 Jul 2010 02:35:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.206
X-Spam-Level:
X-Spam-Status: No, score=-98.206 tagged_above=-999 required=5 tests=[AWL=0.573, BAYES_20=-0.74, HTML_MESSAGE=0.001, J_CHICKENPOX_54=0.6, J_CHICKENPOX_63=0.6, RCVD_DOUBLE_IP_LOOSE=0.76, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3XVU2+ZgFs86 for <sipcore@core3.amsl.com>; Mon, 12 Jul 2010 02:35:00 -0700 (PDT)
Received: from mx5.zte.com.cn (mx6.zte.com.cn [63.218.89.70]) by core3.amsl.com (Postfix) with ESMTP id 070E53A68CB for <sipcore@ietf.org>; Mon, 12 Jul 2010 02:34:58 -0700 (PDT)
Received: from [10.30.17.100] by mx5.zte.com.cn with surfront esmtp id 383431727820181; Mon, 12 Jul 2010 17:34:08 +0800 (CST)
Received: from [10.30.3.19] by [192.168.168.16] with StormMail ESMTP id 95274.2980680612; Mon, 12 Jul 2010 17:27:30 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse2.zte.com.cn with ESMTP id o6C98IuB003958; Mon, 12 Jul 2010 17:08:18 +0800 (CST) (envelope-from gao.yang2@zte.com.cn)
To: sipcore@ietf.org
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 7.0.1 January 17, 2006
Message-ID: <OF86F72DEF.A8F9C33E-ON4825775E.00310620-4825775E.00321A9D@zte.com.cn>
From: gao.yang2@zte.com.cn
Date: Mon, 12 Jul 2010 17:04:12 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 6.5.4|March 27, 2005) at 2010-07-12 17:08:08, Serialize complete at 2010-07-12 17:08:08
Content-Type: multipart/alternative; boundary="=_alternative 00321A984825775E_="
X-MAIL: mse2.zte.com.cn o6C98IuB003958
Subject: Re: [sipcore] Dialog state - Scope in draft-ietf-sipcore-reinvite //Request for other people's following up.
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Jul 2010 09:35:01 -0000

Maybe my last week's comments was a little too expanding. So, I request 
other people to focus on Gonzalo's original suggestion and following up 
with comments. I think we can make things which has been clear to go on in 
the standard process.

Thanks,

Gao


From: gao.yang2 at zte.com.cn 
To: Gonzalo Camarillo <Gonzalo.Camarillo at ericsson.com> 
Cc: SIPCORE <sipcore at ietf.org> 
Date: Mon, 5 Jul 2010 17:11:57 +0800 
In-reply-to: <4C317D02.2030307 at ericsson.com> 

Hi Gonzalo, 

Fisrt, I am glad to hear about this suggestion. And I once proposed the 
similar idea, as putting things which has been cleared forward, and make 
the basic rules(such as *in use* way for O/A usage, and notify way for 
remote target) as reference for other *dialog state* usages, in separate 
drafts. 

Second, I once do one proposal for the other *dialog state* usages in one 
previous mail: 
http://www.ietf.org/mail-archive/web/sipcore/current/msg02850.html 
I think we might need several months's discussion for such topics. 

Third, I suggest one expert(Gonzalo, Paul, or Robert?) to draft out one 
draft, to collect requirments for the remaining topics(the other *dialog 
state* usages's) which still need normative definition/clarification. This 
memo would have the following meanings: 
1. To figure out current status of all SIP Core standard; 
2. As memo of conclusions for points. 
3. If someday, we need 3261bis, this might be a not bad start. 

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.