RE: [Sipping-tispan] Requirements -02g

"Hans Erik van Elburg (RY/ETM)" <hanserik.van.elburg@ericsson.com> Thu, 29 September 2005 23:57 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EL8Gx-0005Fd-SL; Thu, 29 Sep 2005 19:57:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EL8Gw-0005FY-It for sipping-tispan@megatron.ietf.org; Thu, 29 Sep 2005 19:57:06 -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 TAA24257 for <sipping-tispan@ietf.org>; Thu, 29 Sep 2005 19:57:04 -0400 (EDT)
Received: from mailgw3.ericsson.se ([193.180.251.60]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EL8Oh-0004MA-1t for sipping-tispan@ietf.org; Thu, 29 Sep 2005 20:05:07 -0400
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 2E6AFCA4; Fri, 30 Sep 2005 01:56:56 +0200 (CEST)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.173]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); Fri, 30 Sep 2005 01:55:14 +0200
Received: from esealmw109.eemea.ericsson.se ([153.88.200.2]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); Fri, 30 Sep 2005 01:55:14 +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 01:55:13 +0200
Message-ID: <CAC481363DB73049924DDDCFC1AC60A6EE45C5@esealmw109.eemea.ericsson.se>
Thread-Topic: [Sipping-tispan] Requirements -02g
Thread-Index: AcXEH5/fPpiaHb56SWOQjhQRW/mSgABLg2GA
From: "Hans Erik van Elburg (RY/ETM)" <hanserik.van.elburg@ericsson.com>
To: "Miguel Garcia" <Miguel.An.Garcia@nokia.com>, <sipping-tispan@ietf.org>
X-OriginalArrivalTime: 29 Sep 2005 23:55:14.0399 (UTC) FILETIME=[3C433EF0:01C5C551]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168
Content-Transfer-Encoding: quoted-printable
Cc:
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,

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/msg00070.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-sipping-tispan-requirements-02g.txt
http://people.nokia.net/~miguel/drafts/pre/draft-jesske-sipping-tispan-requirements-02g.html

And a diff version with respect -02f:

http://people.nokia.net/~miguel/drafts/pre/draft-jesske-sipping-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