AW: [Sipping-tispan] Requirements -02g
"Schmidt, Christian" <christian-schmidt@siemens.com> Wed, 28 September 2005 13:05 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.32)
id 1EKbcy-0005v4-2V; Wed, 28 Sep 2005 09:05:41 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
by megatron.ietf.org with esmtp (Exim 4.32) id 1EKbcs-0005uz-HK
for sipping-tispan@megatron.ietf.org; Wed, 28 Sep 2005 09:05:34 -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 JAA04954
for <sipping-tispan@ietf.org>; Wed, 28 Sep 2005 09:05:33 -0400 (EDT)
Received: from thoth.sbs.de ([192.35.17.2])
by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EKbkK-0004J4-RF
for sipping-tispan@ietf.org; Wed, 28 Sep 2005 09:13:17 -0400
Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14])
by thoth.sbs.de (8.12.6/8.12.6) with ESMTP id j8SD5Vtd029571;
Wed, 28 Sep 2005 15:05:31 +0200
Received: from mhpahx2c.ww002.siemens.net (mhpahx2c.mch.sbs.de [139.25.165.55])
by mail3.siemens.de (8.12.6/8.12.6) with ESMTP id j8SD5TRD014102;
Wed, 28 Sep 2005 15:05: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, 28 Sep 2005 15:04:56 +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] Requirements -02g
Date: Wed, 28 Sep 2005 15:05:12 +0200
Message-ID: <72963DDDF17D7949ABD18DC5DA58E770058420@MCHP7R5A.ww002.siemens.net>
Thread-Topic: [Sipping-tispan] Requirements -02g
Thread-Index: AcXEH6uHurgfEPlpQG+lqFb0Yk6jpAADHubQ
From: "Schmidt, Christian" <christian-schmidt@siemens.com>
To: "Miguel Garcia" <Miguel.An.Garcia@nokia.com>, <sipping-tispan@ietf.org>
X-OriginalArrivalTime: 28 Sep 2005 13:04:56.0625 (UTC)
FILETIME=[3971AA10:01C5C42D]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
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
Hi Miguel, according to previous mail exchange, there was an agreement to skip the override feature for ACR. There are still parts in the draft relatated to this feature. Therefor I propose to delete: - section 3.2 (ACR): "Another case is when the caller has been duly authorized to override... service activated." - section 4 (Security Considerations): "The ACR service described in 3.2 allows authorized users to override ...decision is made." REV-CDIV-4: some typing errors: caleee > callee, availble > available. Regards, Christian -----Ursprüngliche Nachricht----- Von: sipping-tispan-bounces@ietf.org [mailto:sipping-tispan-bounces@ietf.org] Im Auftrag von Miguel Garcia Gesendet: Mittwoch, 28. September 2005 13:26 An: 'sipping-tispan@ietf.org' Cc: Alexeitsev, D Betreff: [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
- AW: [Sipping-tispan] Requirements -02g Schmidt, Christian
- AW: [Sipping-tispan] Requirements -02g Jesske, R
- AW: [Sipping-tispan] Requirements -02g Jesske, R
- Re: AW: [Sipping-tispan] Requirements -02g Miguel Garcia
- Re: AW: [Sipping-tispan] Requirements -02g Paul Kyzivat
- AW: [Sipping-tispan] Requirements -02g Jesske, R