Re: [Sipping-tispan] Requirements 02e
Miguel Garcia <Miguel.An.Garcia@nokia.com> Wed, 21 September 2005 06:37 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.32)
id 1EHyEB-00084R-TN; Wed, 21 Sep 2005 02:37:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
by megatron.ietf.org with esmtp (Exim 4.32) id 1EHyE9-00083z-Vi
for sipping-tispan@megatron.ietf.org; Wed, 21 Sep 2005 02:37:10 -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 CAA29621
for <sipping-tispan@ietf.org>; Wed, 21 Sep 2005 02:37:08 -0400 (EDT)
Received: from mgw-ext04.nokia.com ([131.228.20.96])
by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EHyK7-0007qA-VJ
for sipping-tispan@ietf.org; Wed, 21 Sep 2005 02:43:20 -0400
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
by mgw-ext04.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id
j8L6YwLZ010999; Wed, 21 Sep 2005 09:35:03 +0300
Received: from esebh003.NOE.Nokia.com ([172.21.138.82]) by
esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830);
Wed, 21 Sep 2005 09:37:02 +0300
Received: from [127.0.0.1] ([172.21.35.78]) by esebh003.NOE.Nokia.com with
Microsoft SMTPSVC(5.0.2195.6881); Wed, 21 Sep 2005 09:37:02 +0300
Message-ID: <4330FF8E.6050403@nokia.com>
Date: Wed, 21 Sep 2005 09:37:02 +0300
From: Miguel Garcia <Miguel.An.Garcia@nokia.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en, es-es
MIME-Version: 1.0
To: Rocky Wang <rocky.wang@huawei.com>
Subject: Re: [Sipping-tispan] Requirements 02e
References: <000001c5bdbd$20592970$11b04c0a@china.huawei.com>
In-Reply-To: <000001c5bdbd$20592970$11b04c0a@china.huawei.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 Sep 2005 06:37:02.0303 (UTC)
FILETIME=[DFF9B6F0:01C5BE76]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8f374d0786b25a451ef87d82c076f593
Content-Transfer-Encoding: 7bit
Cc: sipping-tispan@ietf.org
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 Rocky:
inline discussion.
Rocky Wang wrote:
> But I have some more doubts on TIP:
> REQ-TIP-1: In addition to any network asserted identity, it must be
> possible for the callee to indicate in a SIP response an
> additional identity where he is reachable for future
> direct communications.
> Does it mean the back identifier must be something like gruu? The one
> who answers the call from one endpoint does not always mean the caller
> should make a call to this endpoint directly later.
As far as I understand, there is not a requirement for this to be a
GRUU. This is just another URI that would lead to the same person, but
not necessarily to the same terminal.
>
> REQ-TIP-3: The identity mentioned in REQ-TIP-1 is considered an end
> user supplied information that is not asserted by the
> network.
> Does it mean the network equipments just transfer the called party's
> identifier provided by the called party endpoint? It must be also
> asserted, I think. Or, it will cause some security problem.
It means that the network does not verify the validity of this URI. It
is up to the user to put something meaningful there. This is the
requirement.
BR,
Miguel
>
> Regards,
> Rocky Wang
>
>
> -----Original Message-----
> From: Miguel Garcia [mailto:Miguel.An.Garcia@nokia.com]
> Sent: 2005?9?20? 14:46
> To: Rocky Wang
> Cc: sipping-tispan@ietf.org
> Subject: Re: [Sipping-tispan] Requirements 02e
>
>
> Hi Rocky:
>
> Yes, I think we agreed that this is a missing requirement, but we want
> to write it down when we have finished the other requirements, because
> it may happen that the calling part categories requirements help us in
> creating a proper dependency.
>
> So this is not forgotten, it will be added at a later time.
>
> BR,
>
> Miguel
>
> Rocky Wang wrote:
>
>
>>Hi, Migues,
>>As I considered, the requirement of overrding ACR service must be
>>there as a formal requirement. Maybe there are some ways that the
>>called AS to get enough information to determine that it can or cannot
>
>
>>override the ACR, but there are some cases the simulation service must
>
>
>>be overrided, including the case you listed in the 02a version. It can
>
>
>>be like this: 1. The originating network shall be able to take enough
>>calling party's information to the terminating network to help to
>>override the callee's ACR service. 2. The terminating network shall be
>
>
>>able to override the callee's ACR simulation service if the caller is
>>authorized to do this based on the caller's information.
>>
>>Rocky Wang
>>
>>
>>
>>-----Original Message-----
>>From: sipping-tispan-bounces@ietf.org
>>[mailto:sipping-tispan-bounces@ietf.org] On Behalf Of Miguel Garcia
>>Sent: 2005?9?9? 20:57
>>To: 'sipping-tispan@ietf.org'
>>Subject: [Sipping-tispan] Requirements 02e
>>
>>
>>Hi:
>>
>>I have another working copy of the TISPAN requirements, now version
>>02e:
>>
>>http://people.nokia.net/~miguel/drafts/pre/draft-jesske-sipping-tispan
>>-r
>>equirements-02e.html
>>
>
> http://people.nokia.net/~miguel/drafts/pre/draft-jesske-sipping-tispan-r
>
>>equirements-02e.txt
>>
>>And a diff version with respect 02d:
>>http://people.nokia.net/~miguel/drafts/pre/draft-jesske-sipping-tispan
>>-r
>>equirements-02d-to-e.html
>>
>>The main changes this time are:
>>
>>- Rewording of the CCBS/CCNR requirements as per our discussion. I
>>have
>>added a few definitions and try to reorder them sequentially, so that
>>they are a bit easier to understand.
>>- Clarification that the TIP requirements are for an additional (to
>
> the
>
>>asserted) identity.
>>- Addition of the Communication Waiting requirements
>>
>>Please feel free to comment, but bear in mind that due to the TISPAN
>>meeting next week most of the TISPANers will have limited time to
>>discuss.
>>
>>/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
- [Sipping-tispan] Requirements 02e Miguel Garcia
- RE: [Sipping-tispan] Requirements 02e Rocky Wang
- Re: [Sipping-tispan] Requirements 02e Miguel Garcia
- RE: [Sipping-tispan] Requirements 02e Rocky Wang
- Re: [Sipping-tispan] Requirements 02e Miguel Garcia
- RE: [Sipping-tispan] Requirements 02e Rocky Wang
- Re: [Sipping-tispan] Requirements 02e Miguel Garcia
- Re: [Sipping-tispan] Requirements 02e Paul Kyzivat
- RE: [Sipping-tispan] Requirements 02e mhammer
- Re: [Sipping-tispan] Requirements 02e Miguel Garcia
- [Sipping-tispan] Question on the AoC Requirements zhouqing
- Re: [Sipping-tispan] Requirements 02e Miguel Garcia
- Re: [Sipping-tispan] Question on the AoC Requirem… Miguel Garcia
- Re: [Sipping-tispan] Requirements 02e Paul Kyzivat
- Re: [Sipping-tispan] Requirements 02e Miguel Garcia
- RE: [Sipping-tispan] Requirements 02e Bemmel, Jeroen van (Jeroen)
- RE: [Sipping-tispan] Requirements 02e Bemmel, Jeroen van (Jeroen)
- RE: [Sipping-tispan] Requirements 02e Bemmel, Jeroen van (Jeroen)
- Re: [Sipping-tispan] Requirements 02e Paul Kyzivat