[Sipping-tispan] Feature enhancements

"Schmidt, Christian" <christian-schmidt@siemens.com> Tue, 06 September 2005 14:19 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ECeHw-0000BC-S7; Tue, 06 Sep 2005 10:19:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ECeHv-0000B7-04 for sipping-tispan@megatron.ietf.org; Tue, 06 Sep 2005 10:19:03 -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 KAA00103 for <sipping-tispan@ietf.org>; Tue, 6 Sep 2005 10:19:01 -0400 (EDT)
Received: from thoth.sbs.de ([192.35.17.2]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ECeKs-0006VZ-S4 for sipping-tispan@ietf.org; Tue, 06 Sep 2005 10:22:08 -0400
Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14]) by thoth.sbs.de (8.12.6/8.12.6) with ESMTP id j86EJ0q5000927; Tue, 6 Sep 2005 16:19:00 +0200
Received: from mhpahx2c.ww002.siemens.net (mhpahx2c.mch.sbs.de [139.25.165.55]) by mail3.siemens.de (8.12.6/8.12.6) with ESMTP id j86EIxpH013293; Tue, 6 Sep 2005 16:18:59 +0200
Received: from MCHP7R5A.ww002.siemens.net ([139.25.131.163]) by mhpahx2c.ww002.siemens.net with Microsoft SMTPSVC(6.0.3790.0); Tue, 6 Sep 2005 16:15:16 +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="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 6 Sep 2005 16:18:48 +0200
Message-ID: <72963DDDF17D7949ABD18DC5DA58E7700583F5@MCHP7R5A.ww002.siemens.net>
Thread-Topic: Feature enhancements
Thread-Index: AcWu08MVKEhOQ1AnSRecFOoFHksOogABM9yQAQSMamAAAFVMsA==
From: "Schmidt, Christian" <christian-schmidt@siemens.com>
To: <Silvia.Tessa@TILA.COM>, "Miguel Garcia" <Miguel.An.Garcia@nokia.com>
X-OriginalArrivalTime: 06 Sep 2005 14:15:16.0921 (UTC) FILETIME=[67D93A90:01C5B2ED]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Content-Transfer-Encoding: quoted-printable
Cc: sipping-tispan@ietf.org, "Alexeitsev, D" <D.Alexeitsev@t-com.net>
Subject: [Sipping-tispan] Feature enhancements
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

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 


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