>Greg Troxel [mailto:gdt@fnord.ir.bbn.com] wrote:
>But even in the 'needed' case, there is some fuzz in what is
>'necessary'. I have used a number of geographic search services, and
>almost never given the right location. Usually I pick some round
>number that is more or less close, and some wide enough radius, and
>then filter the results on my end.
Well, maybe what we need to include is a way for a server to express what
degree of precision it needs to get in the request, to be able to deliver
its services to the user/agent.
>To reconcile these, location objects should have one or more
>distinguished values representing "location not available", perhaps in
>various flavors.
I like that. A 'null' value for location.
>A legal requirement to send location on emergency calls can be viewed
>not as a protocol issue, but a requirement for policy configuration to
>be done a certain way.
I think this is important; we need to distinguish 'protocol' issues from
'configuration' issues.
>is ok to provide support for various possible policies in a
>policy negotiation system, but not to contort a protocol or do
>something technicall broken to meet some particular law
I agree too.
Kind regards,
Dante
Dante Castiglione
dantec@amc.com.ar
15-4992-3446
Received on Thu Aug 30 20:32:19 2001
This archive was generated by hypermail 2.1.8 : Thu Jan 22 2004 - 12:32:22 EST