AW: [Sipping-tispan] Prioritization of TISPAN requirements in IETF

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

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E7tvR-0001bB-9m; Wed, 24 Aug 2005 08:00:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E7tvP-0001b6-RF for sipping-tispan@megatron.ietf.org; Wed, 24 Aug 2005 08:00:11 -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 IAA15845 for <sipping-tispan@ietf.org>; Wed, 24 Aug 2005 08:00:11 -0400 (EDT)
Received: from goliath.siemens.de ([192.35.17.28]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E7tvh-0005cy-4O for sipping-tispan@ietf.org; Wed, 24 Aug 2005 08:00:31 -0400
Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by goliath.siemens.de (8.12.6/8.12.6) with ESMTP id j7OC03Sf010945; Wed, 24 Aug 2005 14:00:03 +0200
Received: from mhpahx0c.ww002.siemens.net (mhpahx0c.ww002.siemens.net [139.25.165.42]) by mail1.siemens.de (8.12.6/8.12.6) with ESMTP id j7OC0132025380; Wed, 24 Aug 2005 14:00:02 +0200
Received: from MCHP7R5A.ww002.siemens.net ([139.25.131.163]) by mhpahx0c.ww002.siemens.net with Microsoft SMTPSVC(6.0.3790.211); Wed, 24 Aug 2005 13:58:34 +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] Prioritization of TISPAN requirements in IETF
Date: Wed, 24 Aug 2005 13:59:56 +0200
Message-ID: <72963DDDF17D7949ABD18DC5DA58E7700583E6@MCHP7R5A.ww002.siemens.net>
Thread-Topic: [Sipping-tispan] Prioritization of TISPAN requirements in IETF
Thread-Index: AcWoiqs7SoqfKz2GTY6/quDzH0WyUAAFmxkw
From: "Schmidt, Christian" <christian-schmidt@siemens.com>
To: "Hans Erik van Elburg \(RY/ETM\)" <hanserik.van.elburg@ericsson.com>
X-OriginalArrivalTime: 24 Aug 2005 11:58:34.0187 (UTC) FILETIME=[274499B0:01C5A8A3]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6ffdee8af20de249c24731d8414917d3
Content-Transfer-Encoding: quoted-printable
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 Hans Erik,

can you please provide some additional information
- What are the meaning of the numbers for example in (ACR, 3029)?
- What are the regulatory boddies involved? Are the regulatory papers public available?
- Are the attached requirements sufficient, necessary or only helpful to meet the regulatory issues?
- Is it possible to change requirements, but to still be in line with the regulations?
- What are the provisioning date requirements of these boddies, related to the different services?

Regards,
Christian Schmidt

PS: REQ-GEN-2 is missing, I assume it it non-regulatory as well.




-----Ursprüngliche Nachricht-----
Von: sipping-tispan-bounces@ietf.org [mailto:sipping-tispan-bounces@ietf.org] Im Auftrag von Hans Erik van Elburg (RY/ETM)
Gesendet: Mittwoch, 24. August 2005 11:03
An: TISPAN_WG3@LIST.ETSI.ORG; sipping-tispan@ietf.org
Betreff: [Sipping-tispan] Prioritization of TISPAN requirements in IETF


	Hi,

	In order to speed up the advancement f the TISPAN requirements in IETF we think it would be best to prioritize the requirements. One split we think should be uncontroversial is to split the requirements in those that are induced by regulatory requirements and those that are not. And to prioritize the regulatory requirements in IETF.

	We believe that the following TISPAN simulation services are Regulatory:

	Regulatory Services
	===============
	- Originating Identity Presentation/ Originating Identity Presentation Restriction (OIP/OIR, 3025)
	- OIR override (, 3025)
	- Terminating Identity Presentation/ Terminating Identity Presentation Restriction (TIP/TIR, 3026)
	- Anonymous Communication Rejection (ACR, 3029)
	- Malicious Communication Identification (MCID, 3036)


	Follows that splitting the requirements in one group of regulatory and one group of non-regulatory leads to the following split.

	Proposed grouping of TISPAN-IETF simulation service requirements
	=================================================
	(http://www.ietf.org/internet-drafts/draft-jesske-sipping-tispan-requirements-01.txt)

	Regulatory Requirements:
	- [REQ-ACR-1]
	- [REQ-ACR-2]
	- [REQ-TIP-1]
	- [REQ-TIP-2]
	- [REQ-MCID-1]
	- [REQ-MCID-2]

	Non-Regulatory Requirements:
	- [REQ-GEN-1]
	- [REQ-CCBS-1]
	- [REQ-CCBS-2]
	- [REQ-CCBS-3]
	- [REQ-CCBS-4]
	- [REQ-CCNR-1]
	- [REQ-CCNR-2]
	- [REQ-CW-1]
	- [REQ-CW-2]
	- [REQ-CDIV-1]
	- [REQ-CDIV-2]
	- [REQ-CDIV-3]
	- [REQ-CDIV-4]
	- [REQ-CAT-1] 
	- [REQ-CAT-2] 

	Whether the grouping can best be reflected in one draft or in multiple drafts shall be made dependent on whether advancement of the TISPAN R1 release is held up by a requirements draft that is not fully appoved or not.

	Best Regards,

Hans Erik van Elburg
System Engineer
Technology Strategies

Ericsson Telecommunicatie B.V.
Research and Development
P.O. Box 8, 5120AA  Rijen
The Netherlands

Tel. +31 161 249889, Fax. +31 161 249904
sip:hanserik.van.elburg@tas.uab.ericsson.se
Email: HansErik.van.Elburg@ericsson.com, Internet: http://www.ericsson.nl

This communication is confidential and intended solely for the addressee(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you.
E-mail including attachments is susceptible to data corruption, interruption, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof.



_______________________________________________
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