RE: [Sipping-tispan] Requirements -02g
"Hans Erik van Elburg (RY/ETM)" <hanserik.van.elburg@ericsson.com> Fri, 30 September 2005 11:36 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.32)
id 1ELJC8-0007nG-N7; Fri, 30 Sep 2005 07:36:52 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
by megatron.ietf.org with esmtp (Exim 4.32) id 1ELJC6-0007nB-QO
for sipping-tispan@megatron.ietf.org; Fri, 30 Sep 2005 07:36:50 -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 HAA05634
for <sipping-tispan@ietf.org>; Fri, 30 Sep 2005 07:36:50 -0400 (EDT)
Received: from mailgw3.ericsson.se ([193.180.251.60])
by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ELJJx-0002xh-En
for sipping-tispan@ietf.org; Fri, 30 Sep 2005 07:44:58 -0400
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122])
by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 43C1E5B3;
Fri, 30 Sep 2005 13:36:29 +0200 (CEST)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.175]) by
esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211);
Fri, 30 Sep 2005 13:36:16 +0200
Received: from esealmw109.eemea.ericsson.se ([153.88.200.2]) by
esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211);
Fri, 30 Sep 2005 13:36: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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sipping-tispan] Requirements -02g
Date: Fri, 30 Sep 2005 13:36:15 +0200
Message-ID: <CAC481363DB73049924DDDCFC1AC60A6EE45CA@esealmw109.eemea.ericsson.se>
Thread-Topic: [Sipping-tispan] Requirements -02g
Thread-Index: AcXFe2Eyd0zukzT3SeaeHatBsy6JVwAN3q0g
From: "Hans Erik van Elburg (RY/ETM)" <hanserik.van.elburg@ericsson.com>
To: "Jesske, R" <R.Jesske@t-com.net>, <Miguel.An.Garcia@nokia.com>
X-OriginalArrivalTime: 30 Sep 2005 11:36:16.0088 (UTC)
FILETIME=[2AFBA580:01C5C5B3]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25eb6223a37c19d53ede858176b14339
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
Roland, WG3, The requirement as it is now does not mention authorities at all! Then you say there is a case where ACR needs to be overridden: The only thing is what we need is that a originating user where the communication is network restricted can be bypassed, because he did not anonymised his call. So we need a requirement right? Since there is no network-restricted indication in SIP? Then you refer to WG3 mail list discussion, which is not known to me maybe you can point out the mail to me so that i can refresh myself. Or outline the solution you have in mind for the network-restricted case. Does rephrasing help?: REQ-ACR-3: The originating network shall be able to indicate to the terminating network that an anonymous communication is authorized to bypass the ACR service at the callee's network. Because this expresses that there is some property of the communication that allows it to bypass ACR and not some property of the caller. Best Regards, /Hans Erik P.S. I cant follow a thread where people say: "We need this (network-restricted->bypass), but we dont need a requirement for it because we dont need something else (police->bypass)." -----Original Message----- From: Jesske, R [mailto:R.Jesske@t-com.net] Sent: Friday, September 30, 2005 6:57 AM To: Hans Erik van Elburg (RY/ETM); Miguel.An.Garcia@nokia.com Cc: christian-schmidt@siemens.com; thomas.belling@siemens.com Subject: AW: [Sipping-tispan] Requirements -02g Dear Eric, within the TISPAN list we discussed the override for ACR. It was realises that there is no requirement for overriding calls because of the originating user. That includes Police, Fire force... There was the idea within the discussion that if people like we could use the CPC. So the Assumption is that we do not need an override regarding a special originating party. The only thin is what we need is that a originating user where the communication is network restricted can be bypassed, because he did not anonymised his call. Best Regards Roland > -----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: Freitag, 30. September 2005 01:55 > An: Miguel Garcia; sipping-tispan@ietf.org > Betreff: RE: [Sipping-tispan] Requirements -02g > > > Hi, > > Since the calling parties category is not suitable nor ment > for the case in which override of ACR is needed. And it was > said that we would come back to this requirement once it is > time to discuss Calling Party's Category. > > There is currently no TISPAN service that requires calling > parties category, but it has been added for interworking > reasons (basic call) and to allow services to (as a network > option) act on this. Follows that there is no relation with > ACR whatsoever. > > We propose to unhide the requirement that allows certain > calls to bypass the ACR service. I think the last formulation > of that requirement read: > > REQ-ACR-3: The originating network shall be able to > indicate to the > terminating network that the caller of an anonymous > communication is > authorized to bypass the ACR service at the callee's network. > > Which was somewhere around > http://www1.ietf.org/mail-archive/web/sipping-tispan/current/m > sg00070.html > in the mailing list. > > Best Regards, > > /Hans Erik > > -----Original Message----- > From: sipping-tispan-bounces@ietf.org > [mailto:sipping-tispan-bounces@ietf.org]On Behalf Of Miguel Garcia > Sent: Wednesday, September 28, 2005 1:26 PM > To: 'sipping-tispan@ietf.org' > Cc: Alexeitsev, D > Subject: [Sipping-tispan] Requirements -02g > > > Hi: > > I have this working copy of the requirements, version -02g: > > http://people.nokia.net/~miguel/drafts/pre/draft-jesske-sippin > g-tispan-requirements-02g.txt > http://people.nokia.net/~miguel/drafts/pre/draft-jesske-sippin > g-tispan-requirements-02g.html > > And a diff version with respect -02f: > > http://people.nokia.net/~miguel/drafts/pre/draft-jesske-sippin g-tispan-requirements-02f-to-g.html The changes in this version are: - Grouping of the CCBS/CCNR requirements for better understing - A few clarifications to the CDIV requirements - Addition of the Calling Party Category requirements. Now, I have a few questions. - The Calling Party Category requirements do not constitute a service by itself. In my opinion, they should be General requirements listed a REQ-GEN-4 and REQ-GEN-5. Does anyone oppose to move them to the General section? - We had a pending action point to revisit the ACR requirements once we have drafted the Calling Party Category requirements. Now we have achieved this state, and my opinion is that we don't need to add any extra wording to ACR, since the Calling Party Category requirements cover the use case we have been discussing (police anonymously call a user with ACR activated). Last, but not least, WE ARE ALMOST DONE with the requirements. So please take a look at this draft and comment on any pending issue. I would like to solve issues as soon as possible and submit the draft for publication. Regards, 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 _______________________________________________ Sipping-tispan mailing list Sipping-tispan@ietf.org https://www1.ietf.org/mailman/listinfo/sipping-tispan
- [Sipping-tispan] Requirements -02g Miguel Garcia
- Re: [Sipping-tispan] Requirements -02g Paul Kyzivat
- Re: [Sipping-tispan] Requirements -02g Miguel Garcia
- Re: [Sipping-tispan] Requirements -02g ZhouQing(Justin)
- RE: [Sipping-tispan] Requirements -02g Hans Erik van Elburg (RY/ETM)
- Re: [Sipping-tispan] Requirements -02g Miguel Garcia
- RE: [Sipping-tispan] Requirements -02g Hans Erik van Elburg (RY/ETM)
- Re: [Sipping-tispan] Requirements -02g Paul Kyzivat