[Sipping-tispan] AW: TIP/TIR requirements
"Schmidt, Christian" <christian-schmidt@siemens.com> Thu, 08 September 2005 07:28 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.32)
id 1EDGpp-0006j9-4l; Thu, 08 Sep 2005 03:28:37 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
by megatron.ietf.org with esmtp (Exim 4.32) id 1EDGpn-0006il-DE
for sipping-tispan@megatron.ietf.org; Thu, 08 Sep 2005 03:28:35 -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 DAA04706
for <sipping-tispan@ietf.org>; Thu, 8 Sep 2005 03:28:33 -0400 (EDT)
Received: from thoth.sbs.de ([192.35.17.2])
by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EDGt6-0002uK-4p
for sipping-tispan@ietf.org; Thu, 08 Sep 2005 03:32:02 -0400
Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14])
by thoth.sbs.de (8.12.6/8.12.6) with ESMTP id j887SVX3017442;
Thu, 8 Sep 2005 09:28:31 +0200
Received: from mhpahx0c.ww002.siemens.net (mhpahx0c.ww020.siemens.net
[139.25.165.42] (may be forged))
by mail1.siemens.de (8.12.6/8.12.6) with ESMTP id j887SUI6003384;
Thu, 8 Sep 2005 09:28:30 +0200
Received: from MCHP7R5A.ww002.siemens.net ([139.25.131.163]) by
mhpahx0c.ww002.siemens.net with Microsoft SMTPSVC(6.0.3790.211);
Thu, 8 Sep 2005 09:26:54 +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="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 8 Sep 2005 09:27:57 +0200
Message-ID: <72963DDDF17D7949ABD18DC5DA58E7700583F7@MCHP7R5A.ww002.siemens.net>
Thread-Topic: TIP/TIR requirements
Thread-Index: AcWzgvYpknBtAJMORHS1/6kYcxQn8QAwPOcQ
From: "Schmidt, Christian" <christian-schmidt@siemens.com>
To: "Miguel Garcia" <Miguel.An.Garcia@nokia.com>
X-OriginalArrivalTime: 08 Sep 2005 07:26:54.0640 (UTC)
FILETIME=[B02D5B00:01C5B446]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Content-Transfer-Encoding: quoted-printable
Cc: sipping-tispan@ietf.org, "Alexeitsev, D" <D.Alexeitsev@t-com.net>
Subject: [Sipping-tispan] AW: TIP/TIR requirements
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, some more comments inline Regards Christian > Some comments / questions concerning the TIP/TIR requirements: > > - What happens, when the caller is in PSTN and the callee provides a SIP > URI as identity? Will it be translated at the gateway to a E.164 number? I don't know what people want to do in this scenario, but in my opinion the responsibility lies in the calee, so if the callee offers only a SIP URI, and not both a SIP URI and TEL URL, then the network shouldn't be doing this type of translations. Remember that this is not an asserted identity, so this should be end-to-end information Christian: So your proposal is to drop the information in this case. That is ok for me. Should this information be included in the requirement spec? Proposed extension: REQ-TIP-2: The identity mentioned in REQ-TIP-1 must be formatted as a SIP URI [2] or TEL URL [3]. A translation between SIP URI and E.164 number by the network is not requested. > - How to handle identity restriction from PSTN/ISDN side? Sould the > gateway delete both identity information and restriction information in > this case? If we build on the trust model, and if we consider that the PSTN Gateway trusts the IMS network, then I would say no, delete at the trusted/not-trusted boundary. Christian: Then we would need a method to transport identity restriction information between PSTN Gateway and trusted/non-trusted boundary. This is not included in the requirements now. Proposed requirement: REQ-TIP-4: It must be possible to indicate in a SIP response the information, that the callee has requested identity restriction for this call. _______________________________________________ Sipping-tispan mailing list Sipping-tispan@ietf.org https://www1.ietf.org/mailman/listinfo/sipping-tispan
- [Sipping-tispan] AW: TIP/TIR requirements Schmidt, Christian