RE: AW: AW: AW: [Sipping-tispan] TISPAN requirements, first requiements
"Michael Hammer \(mhammer\)" <mhammer@cisco.com> Fri, 26 August 2005 17:39 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.32)
id 1E8iAi-0004fK-8A; Fri, 26 Aug 2005 13:39:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
by megatron.ietf.org with esmtp (Exim 4.32) id 1E8iAg-0004f1-6E
for sipping-tispan@megatron.ietf.org; Fri, 26 Aug 2005 13:39:18 -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 NAA03477
for <sipping-tispan@ietf.org>; Fri, 26 Aug 2005 13:39:17 -0400 (EDT)
Received: from sj-iport-5.cisco.com ([171.68.10.87])
by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E8iBR-0006VW-W6
for sipping-tispan@ietf.org; Fri, 26 Aug 2005 13:40:06 -0400
Received: from sj-core-3.cisco.com (171.68.223.137)
by sj-iport-5.cisco.com with ESMTP; 26 Aug 2005 10:39:06 -0700
X-IronPort-AV: i="3.96,144,1122879600";
d="scan'208"; a="207857865:sNHT36455978"
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
[64.102.31.102])
by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id j7QHcuZ3019375;
Fri, 26 Aug 2005 10:38:59 -0700 (PDT)
Received: from xmb-rtp-20b.amer.cisco.com ([64.102.31.53]) by
xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
Fri, 26 Aug 2005 13:39:02 -0400
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="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: AW: AW: AW: [Sipping-tispan] TISPAN requirements,
first requiements
Date: Fri, 26 Aug 2005 13:39:01 -0400
Message-ID: <072C5B76F7CEAB488172C6F64B30B5E37C5633@xmb-rtp-20b.amer.cisco.com>
Thread-Topic: AW: AW: AW: [Sipping-tispan] TISPAN requirements,
first requiements
Thread-Index: AcWqM7e2W69ixRqfQ1SxtRUbpH2SwAAMTCcQ
From: "Michael Hammer \(mhammer\)" <mhammer@cisco.com>
To: "Miguel Garcia" <Miguel.An.Garcia@nokia.com>,
"Jesske, R" <R.Jesske@t-com.net>
X-OriginalArrivalTime: 26 Aug 2005 17:39:02.0449 (UTC)
FILETIME=[0C498210:01C5AA65]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
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
My concern over what gets put into the message, is that those indicators could potentially be leaked to the UAS because some intermediate node was not updated with the latest RFC, and according to SIP merely passed on what it did not understand. Mike > -----Original Message----- > From: sipping-tispan-bounces@ietf.org > [mailto:sipping-tispan-bounces@ietf.org] On Behalf Of Miguel Garcia > Sent: Friday, August 26, 2005 7:44 AM > To: Jesske, R > Cc: sipping-tispan@ietf.org; Alexeitsev, D > Subject: Re: AW: AW: AW: [Sipping-tispan] TISPAN > requirements, first requiements > > Hi Roland: > > If you don't have a P-Asserted-Identity in the signalling, is > because the trust relationship has been broken at some point, > in which case, you shouldn't trust also the role parameter > independently of the header where you put it. > > The nice property of adding a role parameter to the > P-Asserted-Identity header is that you get the trust for > free, which is the expected behaviour for this service. > > /Miguel > > Jesske, R wrote: > > >>>I think it might be worth considering adding role parameters to > >>>P-Asserted-ID. > >> > >>That is OK with me and solves most of the problems. > >> > > > > > > > > Paul, > > I have to revice my proposal. > > I thought that is the solution to bind it to the > P-Asserted-Id. But in the case were we have a anonymous > communication restricted by the network. We usually have no > Calling Party number. And therefore also no P-Asserted-Identity. > > So we cannot bind this to the P-Asserted-Identity. > > > > Perhaps we can bind it to the privacy header? > > > > Or any other? > > > > Best Regards. > > > > Roalnd > > > > _______________________________________________ > > 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 > _______________________________________________ Sipping-tispan mailing list Sipping-tispan@ietf.org https://www1.ietf.org/mailman/listinfo/sipping-tispan
- RE: AW: AW: AW: [Sipping-tispan] TISPAN requireme… Michael Hammer (mhammer)
- Re: AW: AW: AW: [Sipping-tispan] TISPAN requireme… Miguel Garcia
- RE: AW: AW: AW: [Sipping-tispan] TISPAN requireme… GARCIN Sebastien RD-CORE-ISS
- RE: AW: AW: AW: [Sipping-tispan] TISPAN requireme… Michael Hammer (mhammer)
- Re: AW: AW: AW: [Sipping-tispan] TISPAN requireme… Miguel Garcia
- Re: AW: AW: AW: [Sipping-tispan] TISPAN requireme… Tom-PT Taylor
- Re: AW: AW: AW: [Sipping-tispan] TISPAN requireme… Miguel Garcia