Re: [Sipping-tispan] Requirements -02g

"ZhouQing(Justin)" <zhouqing@huawei.com> Tue, 11 October 2005 02:05 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EP9Wc-00060N-Po; Mon, 10 Oct 2005 22:05:54 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EP9WY-0005w7-Jf for sipping-tispan@megatron.ietf.org; Mon, 10 Oct 2005 22:05:53 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA08238 for <sipping-tispan@ietf.org>; Mon, 10 Oct 2005 22:05:48 -0400 (EDT)
Received: from szxga01-in.huawei.com ([61.144.161.53] helo=huawei.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EP9gY-0000Cq-GV for sipping-tispan@ietf.org; Mon, 10 Oct 2005 22:16:12 -0400
Received: from huawei.com (szxga01-in [172.24.2.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0IO600MTCBH2XX@szxga01-in.huawei.com> for sipping-tispan@ietf.org; Tue, 11 Oct 2005 10:12:38 +0800 (CST)
Received: from szxml01-in ([172.24.1.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0IO600F6YBH17U@szxga01-in.huawei.com> for sipping-tispan@ietf.org; Tue, 11 Oct 2005 10:12:38 +0800 (CST)
Received: from z45678 ([10.76.176.93]) by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTPA id <0IO600L4JBP7PD@szxml01-in.huawei.com>; Tue, 11 Oct 2005 10:17:31 +0800 (CST)
Date: Tue, 11 Oct 2005 10:06:11 +0800
From: "ZhouQing(Justin)" <zhouqing@huawei.com>
Subject: Re: [Sipping-tispan] Requirements -02g
To: Miguel Garcia <Miguel.An.Garcia@nokia.com>
Message-id: <007701c5ce08$5a4bbb60$5db04c0a@huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
X-Mailer: Microsoft Outlook Express 5.50.4807.1700
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <5ce1635c9ea3.5c9ea35ce163@huawei.com> <4341218A.8060609@nokia.com> <017601c5cbbc$69307240$5db04c0a@huawei.com> <434A6C12.9060606@nokia.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Content-Transfer-Encoding: 7BIT
Cc: sipping-tispan@ietf.org, "Alexeitsev, D" <D.Alexeitsev@t-com.net>
X-BeenThere: sipping-tispan@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussion of requirements for SIP introduced by ETSI TISPAN <sipping-tispan.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping-tispan>, <mailto:sipping-tispan-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/sipping-tispan>
List-Post: <mailto:sipping-tispan@ietf.org>
List-Help: <mailto:sipping-tispan-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping-tispan>, <mailto:sipping-tispan-request@ietf.org?subject=subscribe>
Sender: sipping-tispan-bounces@ietf.org
Errors-To: sipping-tispan-bounces@ietf.org

Hi Miguel,

Thanks for your clarification.

As our discussion in the past, there is a requirement as followed:
It must be possible for the callee and network intermediaries to be informed
that the communication was diverted.

It is a new requirement and is not included in the last draft, so we need to add it.

I suggest to add a requirement REQ-CDIV-XX as followed::
It must be possible for the callee, and network intermediaries to be informed that the communication was diverted. 

It is similar with REQ-CDIV-1, can we combine these 2 requirements? or include it in the exist requirements, eg. REQ-CDIV-3? 
You have more experiences, so I think maybe you have a better way to add it.

Regards,
Justin

----- Original Message ----- 
From: "Miguel Garcia" <Miguel.An.Garcia@nokia.com>
To: "ZhouQing(Justin)" <zhouqing@huawei.com>
Cc: <sipping-tispan@ietf.org>rg>; "Alexeitsev, D" <D.Alexeitsev@t-com.net>
Sent: Monday, October 10, 2005 9:26 PM
Subject: Re: [Sipping-tispan] Requirements -02g


> Hi Justin:
> 
> Inline.
> 
> ZhouQing(Justin) wrote:
> 
> > Hi Miguel,
> > 
> > I have a holiday last week and sorry for the delay.
> > 
> > Thanks for your detail, it is clear and reasonable, it makes me 
> > agree with you that the callee and the network intermediaries
> > may not have the requirements obviously to be aware that "something 
> > is going on right here right now". 
> > 
> > As we seem, it has requirement for the network intermediaries to be 
> > aware that "something went on" (-3 and -4), so I think that the network 
> > intermediaries have the requirements to be aware that the communication 
> > was diverted or not, so that the network intermediaries(eg. voice mail 
> > server) can provide personalized services according to the communication
> > diverted information.
> > 
> > Do you think we have the requirements for the callee and the network
> > intermediaries to be aware that the communication was diverted? 
> > Thank you. 
> > 
> 
> Yes, we discussed this in the past, and some use cases were explained...
>  like a voicemail type of intermediary... So I think we have the
> requirements.
> 
> /Miguel
> 
> > Justin
> > 
> > 
> > ----- Original Message ----- 
> 
> 
> -- 
> Miguel A. Garcia           tel:+358-50-4804586
> sip:miguel.an.garcia@openlaboratory.net
> Nokia Research Center      Helsinki, Finland
> 

_______________________________________________
Sipping-tispan mailing list
Sipping-tispan@ietf.org
https://www1.ietf.org/mailman/listinfo/sipping-tispan