IETF Logo Mail Archive

RE: [Sipping-tispan] Re: Feature enhancements

"GARCIN Sebastien RD-CORE-ISS" <sebastien.garcin@francetelecom.com> Wed, 07 September 2005 12:28 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ECz2w-0003Ti-6K; Wed, 07 Sep 2005 08:28:58 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ECz2u-0003TW-DP for sipping-tispan@megatron.ietf.org; Wed, 07 Sep 2005 08:28:56 -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 IAA15799 for <sipping-tispan@ietf.org>; Wed, 7 Sep 2005 08:28:55 -0400 (EDT)
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ECz64-0003tW-4b for sipping-tispan@ietf.org; Wed, 07 Sep 2005 08:32:13 -0400
Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); Wed, 7 Sep 2005 14:28:52 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sipping-tispan] Re: Feature enhancements
Date: Wed, 7 Sep 2005 14:28:51 +0200
Message-ID: <49E7012A614B024B80A7D175CB9A64EC0662FEFF@ftrdmel1.rd.francetelecom.fr>
Thread-Topic: [Sipping-tispan] Re: Feature enhancements
Thread-Index: AcWzkTV7Dxsgv6V/Tou8I5rXSQOfEQAFhOcg
From: "GARCIN Sebastien RD-CORE-ISS" <sebastien.garcin@francetelecom.com>
To: "Miguel Garcia" <Miguel.An.Garcia@nokia.com>, "Schmidt, Christian" <christian-schmidt@siemens.com>
X-OriginalArrivalTime: 07 Sep 2005 12:28:52.0107 (UTC) FILETIME=[B49DADB0:01C5B3A7]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Content-Transfer-Encoding: quoted-printable
Cc: Silvia.Tessa@TILA.COM, 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,

I also support Silvia's view. After we get the TISPAN requirement clarified and we digg into the protocol solutions we can discuss about enhancing the PSTN service (of course keeping the goal of PSTN interworking). 

sebastien

-----Message d'origine-----
De : sipping-tispan-bounces@ietf.org [mailto:sipping-tispan-bounces@ietf.org] De la part de Miguel Garcia
Envoyé : mercredi 7 septembre 2005 11:42
À : Schmidt, Christian
Cc : Silvia.Tessa@TILA.COM; sipping-tispan@ietf.org; Alexeitsev,D
Objet : [Sipping-tispan] Re: Feature enhancements

I am ok with your proposal. Do we have other opinions?

It must be noted that, althought TISPAN has the mandate to provide a compatible service with the existing PSTN service, it is not forbidden to enhance the existing PSTN service.

/Miguel

Schmidt, Christian wrote:

> Sylvia Tessa wrote:
> 
> 
>>I'm getting in trouble here : how are we supposed to proceed ? Do this
> 
> kind of enhancements need to be written as requirements or will they 
> come up through common sense >while dealing with the solution ?
> 
>>Personally I would write in the document only the strict TISPAN
> 
> requirements, then, while elaborating a solution, it will get more 
> advanced and general purpose, but what >do the other ones here say ?
> 
> 
>>Silvia
> 
> 
> I agree with you, that we should restrict the requirements to TISPAN 
> requirements. Nevertheless, I would propose, to include information 
> about plausible feature enhancements in the draft. It would make 
> clear, that these extensions have been studied, but are definitely not 
> required for the basic services. Perhaps you can realize this in some 
> kind of Non-Requirements. Example:
> Non-Req-AoC: The cancelation of a CCBS request by the network must not 
> be reported to the requestor of the service.
> 
> What do you think about?
> 
> Regards,
> Christian
> 

-- 
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 mailing list
Sipping-tispan@ietf.org
https://www1.ietf.org/mailman/listinfo/sipping-tispan

v2.8.7 | Report a Bug | By Email