Re: AW: [Sipping-tispan] TISPAN requirements, first requiements
Paul Kyzivat <pkyzivat@cisco.com> Fri, 26 August 2005 05:02 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.32)
id 1E8WMc-0007to-NQ; Fri, 26 Aug 2005 01:02:50 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
by megatron.ietf.org with esmtp (Exim 4.32) id 1E8WMb-0007sB-0Q
for sipping-tispan@megatron.ietf.org; Fri, 26 Aug 2005 01:02:49 -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 BAA13540
for <sipping-tispan@ietf.org>; Fri, 26 Aug 2005 01:02:48 -0400 (EDT)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
id 1E8WNG-0007tG-0j
for sipping-tispan@ietf.org; Fri, 26 Aug 2005 01:03:30 -0400
Received: from sj-core-5.cisco.com (171.71.177.238)
by sj-iport-1.cisco.com with ESMTP; 25 Aug 2005 22:02:40 -0700
X-IronPort-AV: i="3.96,142,1122879600";
d="scan'208"; a="656882725:sNHT33019594"
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
[128.107.191.100])
by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id j7Q52Tow004946;
Thu, 25 Aug 2005 22:02:37 -0700 (PDT)
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
Thu, 25 Aug 2005 22:02:36 -0700
Received: from cisco.com ([10.89.16.93]) by xfe-sjc-211.amer.cisco.com with
Microsoft SMTPSVC(6.0.3790.211); Thu, 25 Aug 2005 22:02:35 -0700
Message-ID: <430EA26A.5030801@cisco.com>
Date: Fri, 26 Aug 2005 01:02:34 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Miguel Garcia <Miguel.An.Garcia@nokia.com>
Subject: Re: AW: [Sipping-tispan] TISPAN requirements, first requiements
References: <E7666D92C64C2845AEF12636FF94F95202319E77@S4DE8PSAAGQ.blf.telekom.de>
<430C4280.5060406@nokia.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
X-OriginalArrivalTime: 26 Aug 2005 05:02:35.0540 (UTC)
FILETIME=[5F94CD40:01C5A9FB]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6640e3bbe8a4d70c4469bcdcbbf0921d
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id BAA13540
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
Miguel, Yes, I think something is missing, having to do with how callers entitled to override of ACR are determined. But I still don't know what that requirement should say. Paul Miguel Garcia wrote: > 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 >> > _______________________________________________ Sipping-tispan mailing list Sipping-tispan@ietf.org https://www1.ietf.org/mailman/listinfo/sipping-tispan
- AW: [Sipping-tispan] TISPAN requirements, first r… Jesske, R
- AW: [Sipping-tispan] TISPAN requirements, first r… Schmidt, Christian
- Re: AW: [Sipping-tispan] TISPAN requirements, fir… Miguel Garcia
- Re: AW: [Sipping-tispan] TISPAN requirements, fir… Miguel Garcia
- RE: AW: [Sipping-tispan] TISPAN requirements, fir… Michael Hammer (mhammer)
- Re: AW: [Sipping-tispan] TISPAN requirements, fir… Paul Kyzivat
- RE: AW: [Sipping-tispan] TISPAN requirements, fir… Elwell John
- RE: AW: [Sipping-tispan] TISPAN requirements, fir… Elwell John
- RE: AW: [Sipping-tispan] TISPAN requirements, fir… GARCIN Sebastien RD-CORE-ISS
- Re: AW: [Sipping-tispan] TISPAN requirements, fir… Paul Kyzivat
- RE: AW: [Sipping-tispan] TISPAN requirements, fir… Michael Hammer (mhammer)
- Re: AW: [Sipping-tispan] TISPAN requirements, fir… Paul Kyzivat