Re: RE: [Geopriv] Consensus on changes to location-conveyance
Hannes Tschofenig <[email protected]>
| Newsgroups | gmane.ietf.sip,gmane.ietf.geopriv |
|---|---|
| Message-ID | <[email protected]> |
Hi Jeroen,
in past discussions we concluded that we don't want to have a special
encoding for location-based routing.
I agree with Henning that the level of granularity might, in some cases,
be different depending on the consumer of the PIDF-LO. This is, however,
more a location-based scenario rather than an emergency calling
scenario. The problem is that the end host does not necessarily know the
service boundary ahead of time and hence you don't know the required
granularity of the location object. If you omit too many elements from
the PIDF-LO then LoST might just return incorrect information.
Ciao
Hannes
Jeroen van Bemmel wrote:
> Hi Henning,
>
> Yes, it was intended as a new angle. And you are right that 'zip' is
> probably not enough to cover all cases, my intention in providing the
> 'geo' feature tree as example was to suggest that GEOPRIV might define
> other feature parameters in this space ("country","state" etc are some
> obvious candidates, and "geo.lat" and "geo.lon" perhaps?)
>
> To me, the "emergency calling" use case should indeed be viewed as a
> scenario in which "location conveyance" and "location based routing" are
> combined.
>
> Regards,
>
> Jeroen
>
> ----- Original Message ----- From: "Henning Schulzrinne"
> <[email protected]>
> To: "Jeroen Van Bemmel" <[email protected]>
> Cc: "IETF SIP List" <[email protected]>; "GEOPRIV" <[email protected]>
> Sent: Sunday, July 30, 2006 3:01 PM
> Subject: Re: [Sip] RE: [Geopriv] Consensus on changes to
> location-conveyance
>
>
>>> LBR is better handled using caller prefs/callee capabilities (eg
>>> define +geo.zip, not using PIDF at all for simplicity)
>>>
>>
>> This is completely new suggestion; emergency calling is nothing but a
>> special case of location-based routing. I agree that it is useful to
>> separate location information for routing from that shown to end
>> systems, as they often have different resolution needs. (To route to
>> the right branch of your pizza delivery franchiser, you may only need
>> a zip code, but for delivery, you need the full street address. The
>> practical problem is that such boundaries don't always agree with zip
>> codes or any other higher-level geographic unit, such as state,
>> county or town.)
>>
>> Henning
>
>
>
> _______________________________________________
> Geopriv mailing list
> [email protected]
> https://www1.ietf.org/mailman/listinfo/geopriv
>
>
_______________________________________________
Sip mailing list https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [email protected] for questions on current sip
Use [email protected] for new developments on the application of sip