Re: AW: [Sipping-tispan] TISPAN requirements, first requiements

Miguel Garcia <Miguel.An.Garcia@nokia.com> Wed, 24 August 2005 09:50 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E7rtZ-0005G7-Jp; Wed, 24 Aug 2005 05:50:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E7rtW-0005Dh-VH for sipping-tispan@megatron.ietf.org; Wed, 24 Aug 2005 05:50:07 -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 FAA10038 for <sipping-tispan@ietf.org>; Wed, 24 Aug 2005 05:50:04 -0400 (EDT)
Received: from mgw-ext04.nokia.com ([131.228.20.96]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E7rtn-0001eZ-2e for sipping-tispan@ietf.org; Wed, 24 Aug 2005 05:50:25 -0400
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143]) by mgw-ext04.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id j7O9m723013686; Wed, 24 Aug 2005 12:48:08 +0300
Received: from esebh001.NOE.Nokia.com ([172.21.138.28]) by esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 24 Aug 2005 12:48:49 +0300
Received: from [127.0.0.1] ([172.21.36.151]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); Wed, 24 Aug 2005 12:48:50 +0300
Message-ID: <430C4280.5060406@nokia.com>
Date: Wed, 24 Aug 2005 12:48:48 +0300
From: Miguel Garcia <Miguel.An.Garcia@nokia.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en, es-es
MIME-Version: 1.0
To: "Jesske, R" <R.Jesske@t-com.net>, pkyzivat@cisco.com
Subject: Re: AW: [Sipping-tispan] TISPAN requirements, first requiements
References: <E7666D92C64C2845AEF12636FF94F95202319E77@S4DE8PSAAGQ.blf.telekom.de>
In-Reply-To: <E7666D92C64C2845AEF12636FF94F95202319E77@S4DE8PSAAGQ.blf.telekom.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
X-OriginalArrivalTime: 24 Aug 2005 09:48:50.0222 (UTC) FILETIME=[07A9CCE0:01C5A891]
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by mgw-ext04.nokia.com id j7O9m723013686
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 22bbb45ef41b733eb2d03ee71ece8243
Content-Transfer-Encoding: quoted-printable
Cc: sipping-tispan@ietf.org, "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

Paul, once Roland has explained the issue, what is your proposal for 
clarification of the existing text? Do you think something is missing?

/Miguel

Jesske, R wrote:

> Paul,
> With regard to this feature it must be based on trust relationship as defined within RFC3325 for the P-Asserted-Identity.
> So the indication that this is a authorised user is included by a network entity like it is done for the P-Asserted-Identiy.
> So the network entity knows it via a database that this registered user is a authorised one.
> 
> With regard to the PSTN/ISDN this was solved via a indication that the Calling Party Number is restricted by the network. The network included this indication in three cases:
> 1. The call was originated within a network that cannot provide a originating number (e.G.) analogue.
> 2. The call has no originated number due to interworking with international networks
> 3. The call was send from a authorised user (e.G. police). This indication was then set by the network. This feature is especially used in UK.
> 
> So with the requirement proposed by Miguel we hope to find a solution to cover the 3 above mentioned cases.
> 
> With regard to trust we want to have such a indication bind to a trust relationship as it is described within RFC3325.
> So trust for interconnection to an other network is based on bilateral agreement.
> 
> 
> Best Regards
> 
> Roland
> 
> 
>>-----Ursprüngliche Nachricht-----
>>Von: sipping-tispan-bounces@ietf.org 
>>[mailto:sipping-tispan-bounces@ietf.org] Im Auftrag von Paul Kyzivat
>>Gesendet: Mittwoch, 24. August 2005 05:07
>>An: Miguel Garcia
>>Cc: sipping-tispan@ietf.org; Alexeitsev, Denis
>>Betreff: Re: [Sipping-tispan] TISPAN requirements, first requiements
>>
>>
>>
>>
>>Miguel Garcia wrote:
>>
>>>Folks:
>>>
>>>Since we are tasked to re-draft the TISPAN requirements 
>>
>>adding as much 
>>
>>>clarifications as possible, we would like to start checking 
>>
>>with you if 
>>
>>>the requirements related to the Annonymous Communication 
>>
>>Rejection (ACR) 
>>
>>>service is OK and understandable by everyone.
>>>
>>>So please take a look at the first version of the (much 
>>
>>incomplete and 
>>
>>>short) draft in either text or HTML:
>>>
>>>
>>
>>http://people.nokia.net/~miguel/drafts/pre/draft-jesske-sippin
> 
> g-tispan-requirements-02a.txt 
> 
>>http://people.nokia.net/~miguel/drafts/pre/draft-jesske-sipping-tispan-requirements-02a.html 
>>
>>
>>The document is fairly short at the moment. Please post your comments here.
> 
> 
> Regarding REQ-ACR-2:
> 
> 
>>   REQ-ACR-2: It must be possible that authorized callers are not
>>              subject to the ACR service, thus, allowing the callee to
>>              receive anonymous requests from authorized callers.  This
>>              effectively requires a mechanism to override the ACR
>>              service depending on the identity and authorization of the
>>              caller.  This is needed, e.g., when a police officer or
>>              any other authority is anonymously calling to a user
>>              having the ACR simulation service activated.
> 
> 
> How is a caller authorized? Is the mechanism for determining and 
> conveying this authorization in scope for this service? There is mention 
> specifically of Police Officers, among others, as being authorized. Are 
> there a list of attributes like that which must be used to characterize 
> a caller and that are used to determine the authorization?
> 
> How is this affected by peering and PSTN interconnect? Is an 
> authorization on one side to be conveyed to the other side and then 
> trusted their?
> 
> 	Thanks,
> 	Paul
> 
> _______________________________________________
> Sipping-tispan mailing list
> Sipping-tispan@ietf.org
> https://www1.ietf.org/mailman/listinfo/sipping-tispan
> 

-- 
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