Re:Re: [Sipping-tispan] Requirements -02g
zhouqing 45678 <zhouqing@huawei.com> Sun, 02 October 2005 09:24 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.32)
id 1EM04v-0006xf-OI; Sun, 02 Oct 2005 05:24:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
by megatron.ietf.org with esmtp (Exim 4.32) id 1EM04t-0006xX-Fz
for sipping-tispan@megatron.ietf.org; Sun, 02 Oct 2005 05:24:15 -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 FAA03259
for <sipping-tispan@ietf.org>; Sun, 2 Oct 2005 05:24:13 -0400 (EDT)
Received: from usaga01-in.huawei.com ([12.129.211.51] helo=huawei.com)
by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EM0D8-0002V4-Bm
for sipping-tispan@ietf.org; Sun, 02 Oct 2005 05:32:46 -0400
Received: from huawei.com (usaga01-in [172.18.4.6])
by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
(built Mar
3 2004)) with ESMTP id <0INP002H6WWVX7@usaga01-in.huawei.com> for
sipping-tispan@ietf.org; Sat, 01 Oct 2005 22:36:31 -0700 (PDT)
Received: from huawei.com ([172.17.1.188])
by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
(built Mar
3 2004)) with ESMTP id <0INP009A8WWT3I@usaga01-in.huawei.com> for
sipping-tispan@ietf.org; Sat, 01 Oct 2005 22:36:31 -0700 (PDT)
Received: from [172.24.1.3] (Forwarded-For: [220.187.68.230])
by szxmc01-in.huawei.com (mshttpd); Sun, 02 Oct 2005 13:39:59 +0800
Date: Sun, 02 Oct 2005 13:39:59 +0800
From: zhouqing 45678 <zhouqing@huawei.com>
Subject: Re:Re: [Sipping-tispan] Requirements -02g
To: Miguel Garcia <Miguel.An.Garcia@nokia.com>
Message-id: <5ce1635c9ea3.5c9ea35ce163@huawei.com>
MIME-version: 1.0
X-Mailer: iPlanet Messenger Express 5.2 HotFix 1.25 (built Mar 3 2004)
Content-type: text/plain; charset=gb2312
Content-language: zh-CN
Content-transfer-encoding: quoted-printable
Content-disposition: inline
X-Accept-Language: zh-CN
Priority: normal
X-Spam-Score: 0.1 (/)
X-Scan-Signature: f2728948111f2edaaf8980b5b9de55af
Content-Transfer-Encoding: quoted-printable
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, As I understood, REQ-CDIV-1 is the basic of REQ-CDIV-3 and REQ-CDIV-4, if the callee and the network intermediaries do not know the communication is deverted, the reason for the redirection and the identity of the caller is not useful for them. In previous example, the voice mail server is also required to know the communication is deverted, Only when the call is deverted, the voice mail server can provide the personalized services according to the redirection reason and the caller identity. Best Regards, Justin ----- 原邮件 ----- 从: Miguel Garcia <Miguel.An.Garcia@nokia.com> 日期: 星期五, 九月 30日, 2005 下午4:04 主题: Re: [Sipping-tispan] Requirements -02g > Hi Justin: > > Thanks for your comments, inline discussion. > > ZhouQing(Justin) wrote: > > Hi Migule, > > > > In case CDIV, I think it's better to change REQ-CDIV-1 as > followed to make it consistent with REQ-CDIV-3 and REQ-CDIV-4, > > From: > > It must be possible that the caller is informed that a > communication is being diverted. > > To: > > It must be possible for the caller, the callee, and network > intermediaries to be informed that a communication is being > diverted. > > How do you think? > > > > I think we don't have such requirements. REQ-CDIV-3 and -4 > indicate that > thue network intermediaries (e.g., the voice mail server where my > calls > are diverted) need to u. I think requirements are ok if you want to > provide personalized services, like a different welcome message in > the > voice mail server, depending on the reason why the call ended up > in the > voice mail server. For example, the callee is busy will have a > different > welcome message than when a telemarketer is my black list. > > But, in case of REQ-CDIV-1, I wonder whether we have a requirement > to > inform the callee that the call is being diverted. And I don't see > either for network intermediaries. > > > A short tiping error in REQ-CDIV-4, callee instead of caleee. > > Fixed. > > Regards, > > Miguel > > > > Regards, > > Justin > > > > ----- Original Message ----- > > From: "Miguel Garcia" <Miguel.An.Garcia@nokia.com> > > To: <sipping-tispan@ietf.org> > > Cc: "Alexeitsev, D" <D.Alexeitsev@t-com.net> > > Sent: Wednesday, September 28, 2005 7:25 PM > > Subject: [Sipping-tispan] Requirements -02g > > > > > > > >>Hi: > >> > >>I have this working copy of the requirements, version -02g: > >> > >>http://people.nokia.net/~miguel/drafts/pre/draft-jesske-sipping- > tispan-requirements-02g.txt > >>http://people.nokia.net/~miguel/drafts/pre/draft-jesske-sipping- > tispan-requirements-02g.html > >> > >>And a diff version with respect -02f: > >> > >>http://people.nokia.net/~miguel/drafts/pre/draft-jesske-sipping- > tispan-requirements-02f-to-g.html > >> > >>The changes in this version are: > >>- Grouping of the CCBS/CCNR requirements for better understing > >>- A few clarifications to the CDIV requirements > >>- Addition of the Calling Party Category requirements. > >> > >>Now, I have a few questions. > >> > >>- The Calling Party Category requirements do not constitute a > service by > >> itself. In my opinion, they should be General requirements > listed a > >>REQ-GEN-4 and REQ-GEN-5. Does anyone oppose to move them to the > General > >>section? > >> > >>- We had a pending action point to revisit the ACR requirements > once we > >>have drafted the Calling Party Category requirements. Now we > have > >>achieved this state, and my opinion is that we don't need to add > any > >>extra wording to ACR, since the Calling Party Category > requirements > >>cover the use case we have been discussing (police anonymously > call a > >>user with ACR activated). > >> > >>Last, but not least, WE ARE ALMOST DONE with the requirements. > So please > >>take a look at this draft and comment on any pending issue. I > would like > >>to solve issues as soon as possible and submit the draft for > publication.>> > >>Regards, > >> > >> Miguel > >> > >>-- > >>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 > > -- > 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
- Re:Re: [Sipping-tispan] Requirements -02g zhouqing 45678
- Re: [Sipping-tispan] Requirements -02g Miguel Garcia
- Re: [Sipping-tispan] Requirements -02g ZhouQing(Justin)
- Re: [Sipping-tispan] Requirements -02g Miguel Garcia
- Re: [Sipping-tispan] Requirements -02g ZhouQing(Justin)
- Re: [Sipping-tispan] Requirements -02g Miguel Garcia
- Re: [Sipping-tispan] Requirements -02g ZhouQing(Justin)