AW: [Sipping-tispan] TISPAN requirements, first requiements

"Schmidt, Christian" <christian-schmidt@siemens.com> Wed, 24 August 2005 09:30 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E7raf-00087k-7E; Wed, 24 Aug 2005 05:30:37 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E7rad-00087c-En for sipping-tispan@megatron.ietf.org; Wed, 24 Aug 2005 05:30:35 -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 FAA09200 for <sipping-tispan@ietf.org>; Wed, 24 Aug 2005 05:30:33 -0400 (EDT)
Received: from thoth.sbs.de ([192.35.17.2]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E7rav-00012t-9Q for sipping-tispan@ietf.org; Wed, 24 Aug 2005 05:30:53 -0400
Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11]) by thoth.sbs.de (8.12.6/8.12.6) with ESMTP id j7O9UVVq013940; Wed, 24 Aug 2005 11:30:31 +0200
Received: from mhpahx2c.ww002.siemens.net (mhpahx2c.mch.sbs.de [139.25.165.55]) by mail2.siemens.de (8.12.6/8.12.6) with ESMTP id j7O9UVq9000524; Wed, 24 Aug 2005 11:30:31 +0200
Received: from MCHP7R5A.ww002.siemens.net ([139.25.131.163]) by mhpahx2c.ww002.siemens.net with Microsoft SMTPSVC(6.0.3790.0); Wed, 24 Aug 2005 11:26:40 +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: AW: [Sipping-tispan] TISPAN requirements, first requiements
Date: Wed, 24 Aug 2005 11:30:03 +0200
Message-ID: <72963DDDF17D7949ABD18DC5DA58E7700583E3@MCHP7R5A.ww002.siemens.net>
Thread-Topic: [Sipping-tispan] TISPAN requirements, first requiements
Thread-Index: AcWnxiDDCwj4uWrcTPuv4xQrbMpfwQAwlaiA
From: "Schmidt, Christian" <christian-schmidt@siemens.com>
To: "Miguel Garcia" <Miguel.An.Garcia@nokia.com>, <sipping-tispan@ietf.org>
X-OriginalArrivalTime: 24 Aug 2005 09:26:40.0437 (UTC) FILETIME=[EF0CB650:01C5A88D]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5
Content-Transfer-Encoding: quoted-printable
Cc: "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

Some comments:

2. Overview
"small variations are expected when compared with the equivalent ISTD/PSTN supplementary services"
Can you provide an example for such a variation?

3.1 General Requirements
"the user should receive the service without any degradation"
This seems to be somehow in contradiction with the "variation" passage in the overview section. Or do you mean variation as addon only?

3.2 ACR
- In the first section, you describe ACR, but not the override mechanism. You should add an explanation here.
- ACR2: the term "allowing the callee to receive" is somehow missleading. According to my understanding, the callee cannot influence the delivery of such calls. Proposal: "allowing anonymous calls to be provided to callees, in spite of an activated ACR service."
- "This is needed...". This is not a requirement, it is an explanation and should be part of the service description at the begin of the section.

There should also be a general requirement included:
GEN-3: "SIP UA not providing this simulation service should not be influenced, they are simple not able to provide the related service."

Security Considerations:
Idea:
Threat: Fake override condition
Method: How to avoid, for example with a short description of the planned authentication and authorization methods.

Regards
Christian Schmidt




-----Ursprüngliche Nachricht-----
Von: sipping-tispan-bounces@ietf.org [mailto:sipping-tispan-bounces@ietf.org] Im Auftrag von Miguel Garcia
Gesendet: Dienstag, 23. August 2005 11:35
An: sipping-tispan@ietf.org
Cc: Alexeitsev, D
Betreff: [Sipping-tispan] TISPAN requirements, first requiements


Folks:

Since we are tasked to re-draft the TISPAN requirements adding as much 
clarifications as possible, we would like to start checking with you if 
the requirements related to the Annonymous Communication Rejection (ACR) 
service is OK and understandable by everyone.

So please take a look at the first version of the (much incomplete and 
short) draft in either text or HTML:

http://people.nokia.net/~miguel/drafts/pre/draft-jesske-sipping-tispan-requirements-02a.txt
http://people.nokia.net/~miguel/drafts/pre/draft-jesske-sipping-tispan-requirements-02a.html

The document is fairly short at the moment. Please post your comments here.

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