[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Sip] draft-ietf-sip-location-conveyance - Question about potential usage of the Geolocation header
Yes, I have, namely the P-Access-Network-Info header.
There are two problems with it:
1. I cannot included called (B) party cell-id in it.
2. RFC says that proxy cannot insert this header, however I guess 3GPP allows P-CSCF to do it. Anyway in my case it will be an IMS AS retrieving location, acting as a proxy.
So I doubt it would be a suited solution.
Bartek
-----Original Message-----
From: Dean Willis [mailto:dean.willis at softarmor.com]
Sent: Monday, August 18, 2008 7:00 PM
To: Bartłomiej Kołakowski
Cc: draft-ietf-sip-location-conveyance at tools.ietf.org; sip at ietf.org
Subject: Re: [Sip] draft-ietf-sip-location-conveyance - Question about potential usage of the Geolocation header
On Aug 13, 2008, at 9:03 AM, Bartłomiej Kołakowski wrote:
> Hello,
>
> I have got such concern regarding location conveyance in SIP
> messages: I am designing IMS Appilcation Server, acting as a proxy,
> that would query neFrom sip-bounces at ietf.org Wed Aug 20 10:57:25 2008
Return-Path: <sip-bounces at ietf.org>
X-Original-To: sip-archive at optimus.ietf.org
Delivered-To: ietfarch-sip-archive at core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id 006953A69CE;
Wed, 20 Aug 2008 10:57:25 -0700 (PDT)
X-Original-To: sip at core3.amsl.com
Delivered-To: sip at core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id D760128C19B
for <sip at core3.amsl.com>; Tue, 19 Aug 2008 06:20:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.04
X-Spam-Level: *
X-Spam-Status: No, score=1.04 tagged_above=-999 required=5 tests=[AWL=1.254,
BAYES_00=-2.599, HELO_EQ_PL=1.135, HOST_EQ_PL=1.95,
MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32])
by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id FJGV2PPQx93O for <sip at core3.amsl.com>;
Tue, 19 Aug 2008 06:20:54 -0700 (PDT)
Received: from plusmx1.polkomtel.com.pl (plusmx1.polkomtel.com.pl
[212.2.96.51]) by core3.amsl.com (Postfix) with ESMTP id B25C128C197
for <sip at ietf.org>; Tue, 19 Aug 2008 06:20:52 -0700 (PDT)
Received: from mswwaw3.corp.plusnet (plus-96-163.polkomtel.com.pl
[212.2.96.163])
by plusmx1.polkomtel.com.pl (Postfix) with ESMTP id E1DBA33A6E1
for <sip at ietf.org>; Tue, 19 Aug 2008 15:20:59 +0200 (CEST)
Received: from E2K2.corp.plusnet (MCSGEO2N4B.corp.plusnet) by
mswwaw3.corp.plusnet
(Content Technologies SMTPRS 4.3.20) with ESMTP id
<T88e7f53a8d0a0b4d0e9b8 at mswwaw3.corp.plusnet>;
Tue, 19 Aug 2008 15:19:20 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 19 Aug 2008 14:58:48 +0200
Message-ID: <31CB570C7D71214790963DB8A02D07A810A412B1 at E2K2.corp.plusnet>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sip] draft-ietf-sip-location-conveyance - Question about
potential usage of the Geolocation header
Thread-Index: AckBU+tjCLRbRghpRhWoBMv3OANJwQAdrvug
References: <31CB570C7D71214790963DB8A02D07A810A41295 at E2K2.corp.plusnet>
<DCAC6416-D565-4DA3-8D81-CD43DEB3E32C at softarmor.com>
From: =?iso-8859-2?Q?Bartłomiej_Kołakowski?= <b.kolakowski at plus.pl>
To: "Dean Willis" <dean.willis at softarmor.com>
X-Mailman-Approved-At: Wed, 20 Aug 2008 10:57:23 -0700
Cc: sip at ietf.org, draft-ietf-sip-location-conveyance at tools.ietf.org
Subject: Re: [Sip] draft-ietf-sip-location-conveyance - Question about
potential usage of the Geolocation header
X-BeenThere: sip at ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
<mailto:sip-request at ietf.org?subject=unsubscribe>
List-Post: <mailto:sip at ietf.org>
List-Help: <mailto:sip-request at ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
<mailto:sip-request at ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable
Sender: sip-bounces at ietf.org
Errors-To: sip-bounces at ietf.org
Yes, I have, namely the P-Access-Network-Info header.
There are two problems with it:
1. I cannot included called (B) party cell-id in it.
2. RFC says that proxy cannot insert this header, however I guess 3GPP allows P-CSCF to do it. Anyway in my case it will be an IMS AS retrieving location, acting as a proxy.
So I doubt it would be a suited solution.
Bartek
-----Original Message-----
From: Dean Willis [mailto:dean.willis at softarmor.com]
Sent: Monday, August 18, 2008 7:00 PM
To: Bartłomiej Kołakowski
Cc: draft-ietf-sip-location-conveyance at tools.ietf.org; sip at ietf.org
Subject: Re: [Sip] draft-ietf-sip-location-conveyance - Question about potential usage of the Geolocation header
On Aug 13, 2008, at 9:03 AM, Bartłomiej Kołakowski wrote:
> Hello,
>
> I have got such concern regarding location conveyance in SIP
> messages: I am designing IMS Appilcation Server, acting as a proxy,
> that would query network eltwork elements for location information. As you
> wrote proxies cannot insert message body, so the only way is to
> provide location by reference. This requires appling SUBSCRIBE- NOTIFY
> mechanism, which makes the architecture of the solution quit complex.
>
> In order to make it simpler I thought about including location
> information as locationValue inside the Geolocation header. In fact we
> do not need location represented with coordinates, but with cell- id
> (that's mobile network). PIDF-LO does not support it, but maybe inside
> a header that would be possible? There would be also an issue in
> indicating loaction target whose location is included (we plan to
> include both A and B parties location). Geolocation header would look
> like this:
>
> Geolocation: {cell-id-3gpp} ;location-target="bob at plus.pl";inserted-
> by="las at plus.pl"
>
> What do you think about souch a usage of Geolocation header, maybe you
> could give us some other solution?
>
have you looked at RC 3455? This defines IMS headers for cell-ID based
location.
--
Dean
_______________________________________________
Sip mailing list https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors at cs.columbia.edu for questions on current sip
Use sipping at ietf.org for new developments on the application of sip
ements for location information. As you
> wrote proxies cannot insert message body, so the only way is to
> provide location by reference. This requires appling SUBSCRIBE- NOTIFY
> mechanism, which makes the architecture of the solution quit complex.
>
> In order to make it simpler I thought about including location
> information as locationValue inside the Geolocation header. In fact we
> do not need location represented with coordinates, but with cell- id
> (that's mobile network). PIDF-LO does not support it, but maybe inside
> a header that would be possible? There would be also an issue in
> indicating loaction target whose location is included (we plan to
> include both A and B parties location). Geolocation header would look
> like this:
>
> Geolocation: {cell-id-3gpp} ;location-target="bob at plus.pl";inserted-
> by="las at plus.pl"
>
> What do you think about souch a usage of Geolocation header, maybe you
> could give us some other solution?
>
have you looked at RC 3455? This defines IMS headers for cell-ID based
location.
--
Dean
_______________________________________________
Sip mailing list https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors at cs.columbia.edu for questions on current sip
Use sipping at ietf.org for new developments on the application of sip