Re: AW: [Sipping-tispan] draft-jesske-sipping-tispan-requirements-02c

"Philip Mart" <Philip.Mart@marconi.com> Thu, 01 September 2005 09:40 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EAlZ2-0000Z9-QM; Thu, 01 Sep 2005 05:40:56 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EAlZ0-0000YP-B4; Thu, 01 Sep 2005 05:40:54 -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 FAA07197; Thu, 1 Sep 2005 05:40:52 -0400 (EDT)
Received: from smtpoutuk01.marconi.com ([128.87.251.112]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EAlau-0007Lu-Fc; Thu, 01 Sep 2005 05:42:54 -0400
Received: from cvdgwy01.uk.marconicomms.com (cvis26.uk.marconicomms.com [128.87.251.109]) by smtpoutuk01.marconi.com (8.12.11/8.12.11) with ESMTP id j819ecek017045; Thu, 1 Sep 2005 10:40:38 +0100 (envelope-from Philip.Mart@marconi.com)
Subject: Re: AW: [Sipping-tispan] draft-jesske-sipping-tispan-requirements-02c
To: "Miguel Garcia <Miguel.An.Garcia" <Miguel.An.Garcia@nokia.com>
X-Mailer: Lotus Notes Release 5.0.12 February 13, 2003
Message-ID: <OF54BBC26A.9FA15DBB-ON8025706F.0034A0AA-8025706F.00352A1C@uk.marconicomms.com>
From: "Philip Mart" <Philip.Mart@marconi.com>
Date: Thu, 1 Sep 2005 10:40:41 +0100
X-MIMETrack: Serialize by Router on CVDGWY01/S/EXT/MC1(5012HF354 | August 26, 2003) at 01/09/2005 10:40:34
MIME-Version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: quoted-printable
X-Spam-Score: 2.4 (++)
X-Scan-Signature: 87a3f533bb300b99e2a18357f3c1563d
Content-Transfer-Encoding: quoted-printable
Cc: sipping-tispan-bounces@ietf.org, "Alexeitsev, D" <D.Alexeitsev@t-com.net>, 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

Miguel,

I believe that we can just drop the override feature, there are ways of
handling the issues that just don't need to be in the protocol
specification.

Therefore I support the use of the description proposed by Christian. I
note in passing that the requirment REQ-ACR-2 is actually stronger than the
equivalent text in EN 300 798 where the presence of a note significantly
weakens it, but it seems a perfectly reasonable and socially useful
requirement to maintain.

Phil


                                                                                                                                          
                      Miguel Garcia                                                                                                       
                      <Miguel.An.Garcia@no        To:       "Schmidt, Christian" <christian-schmidt@siemens.com>                          
                      kia.com>                    cc:       sipping-tispan@ietf.org, "Alexeitsev, D" <D.Alexeitsev@t-com.net>             
                      Sent by:                    Subject:  Re: AW: [Sipping-tispan] draft-jesske-sipping-tispan-requirements-02c         
                      sipping-tispan-bounc                                                                                                
                      es@ietf.org                                                                                                         
                                                                                                                                          
                                                                                                                                          
                      01/09/2005 10:00                                                                                                    
                                                                                                                                          
                                                                                                                                          




This is ok, but can we remove the "override" feature?

/Miguel

Schmidt, Christian wrote:

> Hi,
>
> if the override request is skipped, we can simplify the ACR requirements
to
>
> "This service allows a callee to instruct the network to automatically
reject
> incoming communications when the caller has requested anonymity.  The ACR
> supplementary service is described in ETSI EN 300 798 [13].
>
> ACR is a regulatory service.
>
> REQ-ACR-1: The originating network shall be able to indicate to the
>            terminating network, that the caller has requested anonymity.
>
> REQ-ACR-2: The ACR simulation service requires the caller to be
>            informed that the communication was rejected because the
>            SIP request was anonymous and the callee had the ACR
>            service activated."
>
> What do you think about?
> Christian
>
>
>
>
>
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: sipping-tispan-bounces@ietf.org
[mailto:sipping-tispan-bounces@ietf.org] Im Auftrag von Miguel Garcia
> Gesendet: Donnerstag, 1. September 2005 09:50
> An: sipping-tispan@ietf.org
> Cc: Alexeitsev, D
> Betreff: [Sipping-tispan] draft-jesske-sipping-tispan-requirements-02c
>
>
> Hi:
>
> I have put a new working copy of the requirements draft.
>
>
http://people.nokia.net/~miguel/drafts/pre/draft-jesske-sipping-tispan-requirements-02c.txt

>
http://people.nokia.net/~miguel/drafts/pre/draft-jesske-sipping-tispan-requirements-02c.html

>
> Changes with respect the previous version.
>
> - ACR: added a second requirement (REQ-ACR-2) that was discussed here in
> the list, but I kept the old REQ-ACR-2 that now becomes -3.
>
> - I have added CCBS/CCNR, combined into a single set of requirements.
>
> I will start a separate thread , per topic, on both requirements, I
> think we need more changes. Please comment on these or any other service
> as you wish.
>
> /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