[Sipping-tispan] ACR Requirements
"Jesske, R" <R.Jesske@t-com.net> Mon, 29 August 2005 12:05 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.32)
id 1E9iOG-0002tf-Ns; Mon, 29 Aug 2005 08:05:28 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
by megatron.ietf.org with esmtp (Exim 4.32) id 1E9iOD-0002rv-Jy
for sipping-tispan@megatron.ietf.org; Mon, 29 Aug 2005 08:05:25 -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 IAA04063
for <sipping-tispan@ietf.org>; Mon, 29 Aug 2005 08:05:24 -0400 (EDT)
Received: from tcmail33.telekom.de ([217.6.95.240])
by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E9iPU-0005bi-AV
for sipping-tispan@ietf.org; Mon, 29 Aug 2005 08:06:45 -0400
Received: from s4de8psaans.mitte.t-com.de by tcmail31.dmz.telekom.de with
ESMTP; Mon, 29 Aug 2005 14:05:02 +0200
Received: by S4DE8PSAANS.blf.telekom.de with Internet Mail Service
(5.5.2653.19) id <R5Y03PRQ>; Mon, 29 Aug 2005 14:05:02 +0200
Message-Id: <E7666D92C64C2845AEF12636FF94F95202319EBE@S4DE8PSAAGQ.blf.telekom.de>
From: "Jesske, R" <R.Jesske@t-com.net>
To: sipping-tispan@ietf.org, TISPAN_WG3@list.etsi.org
Date: Mon, 29 Aug 2005 14:04:55 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.6 (/)
X-Scan-Signature: b22590c27682ace61775ee7b453b40d3
Cc:
Subject: [Sipping-tispan] ACR Requirements
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>
Content-Type: multipart/mixed; boundary="===============0370985061=="
Sender: sipping-tispan-bounces@ietf.org
Errors-To: sipping-tispan-bounces@ietf.org
Dear all, After several discussions I had the last days regarding the ACR requirements I would like to propose the following: 1. To define a requirement that marks a communication where the ID is network restricted. The rest with regard to ACR is the definition how the service will use such a network restricted information. E.G [ACR-2] To avoid that the ACR rejects communications that have no originating Identity due to the fact that this was restricted by the network and not by a privacy service initiated or initiated on behalf by the originator of the communication a indication is needed to mark that communication as a network restricted communication. 2. To delete the by-pass requirement for authorities. Due to the bypass of ACR several issues were discussed. Fact is it is not clear if this is required by regulation or not. It was mentioned that a originating identification is needed. Due to the fact that there is an other requirement ([REQ-CAT-1] For service applicability to special groups and interoperability with the PSTN/ISDN an indication of the originating party category is needed. This is needed due to the fact that some services apply a special behaviour to special user groups (e.g., like Pay-Phones). And [REQ-CAT-2] The originating party category referred to in REQ-CAT-1 must be inserted by a trusted entity. ) it is proposed to use this functionality then if a bypass is needed. This requirement is independent from the ACR bypass, because a originating user indication (Calling Party's Category) is needed anyway. I hope we can go such a way and solve the network restricted problem. Best Regards Roland Deutsche Telekom AG T-Com Zentrale Roland Jesske, TE332-2 Section TE33; Signalling, Gateways and Switching Systems Am Kavalleriesand 3, 64295 Darmstadt, Germany Phone: +49 6151 83-5940 Fax: +49 6151 83-4577 email: r.jesske@t-com.net
_______________________________________________ Sipping-tispan mailing list Sipping-tispan@ietf.org https://www1.ietf.org/mailman/listinfo/sipping-tispan
- [Sipping-tispan] ACR Requirements Jesske, R
- Re: [Sipping-tispan] ACR Requirements Paul Kyzivat
- RE: [Sipping-tispan] ACR Requirements Hans Erik van Elburg (RY/ETM)
- RE: [Sipping-tispan] ACR Requirements GARCIN Sebastien RD-CORE-ISS