Re: [Sipping-tispan] Requirements version -02d

Miguel Garcia <Miguel.An.Garcia@nokia.com> Wed, 07 September 2005 07:39 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ECuWy-0004BT-Ut; Wed, 07 Sep 2005 03:39:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ECuWv-0004Ag-Du for sipping-tispan@megatron.ietf.org; Wed, 07 Sep 2005 03:39:38 -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 DAA02719 for <sipping-tispan@ietf.org>; Wed, 7 Sep 2005 03:39:36 -0400 (EDT)
Received: from mgw-ext01.nokia.com ([131.228.20.93]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ECua2-0004Cx-GA for sipping-tispan@ietf.org; Wed, 07 Sep 2005 03:42:52 -0400
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211]) by mgw-ext01.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id j877dV4x022414; Wed, 7 Sep 2005 10:39:31 +0300
Received: from esebh001.NOE.Nokia.com ([172.21.138.28]) by esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 7 Sep 2005 10:39:30 +0300
Received: from [127.0.0.1] ([172.21.35.78]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); Wed, 7 Sep 2005 10:39:30 +0300
Message-ID: <431E9932.6090308@nokia.com>
Date: Wed, 07 Sep 2005 10:39:30 +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: GARCIN Sebastien RD-CORE-ISS <sebastien.garcin@francetelecom.com>
Subject: Re: [Sipping-tispan] Requirements version -02d
References: <49E7012A614B024B80A7D175CB9A64EC065D8AEF@ftrdmel1.rd.francetelecom.fr>
In-Reply-To: <49E7012A614B024B80A7D175CB9A64EC065D8AEF@ftrdmel1.rd.francetelecom.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
X-OriginalArrivalTime: 07 Sep 2005 07:39:30.0383 (UTC) FILETIME=[4838D5F0:01C5B37F]
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by mgw-ext01.nokia.com id j877dV4x022414
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2beba50d0fcdeee5f091c59f204d4365
Content-Transfer-Encoding: quoted-printable
Cc: TISPAN_WG3@LIST.ETSI.ORG, 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

Sebastien, some inline comments.


GARCIN Sebastien RD-CORE-ISS wrote:

> Hi,
> 
> Yes please delete it, this adds unecessary complexity to the service. 
> 
> Also I don't fully agree with CCBS-4 which-4 talks about sending a notification when the caller is busy at the time the calle. If we are talking about sending this notification to the call,  this is again something new and not required here. We don't need to explain what happens when this case occurs we are providing a service descripion only protocol requirements. I hence propose to remove the last sentence as follows: 
>  
>  REQ-CCBS/CCNR-4:  The entity providing the CCBS/CCNR service needs to
>                      know the status of the caller at the time of
>                      allocating a initiating the CCBS/CCNR request. 
>      

So it seems that in the PSTN in the case the network cancels the 
CCBS/CCNR service request, the caller is never informed. I found this 
awful from the user's experience point of view. So if we want to limit 
to mimic the PSTN service and not adding a single bit of improvement, 
than we can safely delete the sentence as you mention.

In addition to that, if you think of the solution, and if you think that 
this will most likely be implemented as an event package, when the 
network decides to terminate the subscription, it sends a NOTIFY request 
to the subscriber, including a Subscription-State header with the value 
set set to "terminated". The notifier can also include a "reason" 
parameter including the reason for termination.

So honestly speaking, if you think of the solution, the presence or 
absence of this requirement has no changes in the protocol.

> CCBS-6 does not seem to require anything from a protocol perspective, again it seems that we are trying to describe the service. If we feel that something is missing from SIP we need to be more explicit or else delete the requirement.

Probably, I don't know if it requires protocol development or not, but 
if you take a look at the discussion on the list, probably you will 
agree with me that CCBS is not an easy-to-understand service, so we have 
been requested to add a few clarifications of how the service works.


/Miguel


> 
> Regards
> sebastien
> 
> 
> 
> -----Message d'origine-----
> De : Miguel Garcia [mailto:Miguel.An.Garcia@nokia.com] 
> Envoyé : mercredi 7 septembre 2005 08:29
> À : GARCIN Sebastien RD-CORE-ISS
> Cc : sipping-tispan@ietf.org; TISPAN_WG3@LIST.ETSI.ORG
> Objet : Re: [Sipping-tispan] Requirements version -02d
> 
> Sebastien,
> 
> Certainly it is not the intention of this work to fit new requirements, but just to reword the TISPAN requirements. As such, if you think that
> CCBS-7 is not a requirement for TISPAN we can safely delete it.
> 
> /Miguel
> 
> GARCIN Sebastien RD-CORE-ISS wrote:
> 
> 
>>Miguel, all,
>>
>>Looking at this new version of the tispan-requirements draft, I have the clear impression that the activity is getting out of the scope that it was granted both by the TISPAN and IETF SIPPING management. 
>>
>>The new version contains a number of new requirements (for example CCBS-7) which have never been discussed in TISPAN. 
>>
>>This mailing list activity does not have the mandate the add new requirements, only to clarify the vocabulary and adapt it so that a non-telecom reader is able to understand them.   
>>
>>As a TISPAN member, I see those changes as "IETF proposed" changes that will need to be further reviewed and agreed upon in TISPAN by WG3 (at our next week meeting). As a result of this review TISPAN could come up with a new "agreed" draft version to be submitted to IETF.
>>
>>Best regards,
>>sebastien
>>
>>-----Message d'origine-----
>>De : sipping-tispan-bounces@ietf.org 
>>[mailto:sipping-tispan-bounces@ietf.org] De la part de Miguel Garcia 
>>Envoyé : mardi 6 septembre 2005 15:07 À : 'sipping-tispan@ietf.org'
>>Objet : [Sipping-tispan] Requirements version -02d
>>
>>Hi:
>>
>>I have placed a working copy of the requirements, just to summarize where we are today.
>>
>>http://people.nokia.net/~miguel/drafts/pre/draft-jesske-sipping-tispan
>>-requirements-02d.html 
>>http://people.nokia.net/~miguel/drafts/pre/draft-jesske-sipping-tispan
>>-requirements-02d.txt
>>
>>Besides the discussion around ACR and CCBS/CCNR, I have added the MCID requirements. Please indicate if you still have concerns, and perhaps propose text.
>>
>>A diff version containing revision marks is also available:
>>
>>http://people.nokia.net/~miguel/drafts/pre/draft-jesske-sipping-tispan
>>-requirements-02c-to-d.html
>>
>>/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