[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Ecrit] comments on LoST

Major:

* LoST doesn't allow for any variability in the format of location information. I wonder if it makes sense to include an indication of the format of the location object, and to allow rejection if the format is not supported. Probably you'd need a baseline for interoperability.

* I dont like how dialstring is added as an attribute of the location response, rather than a type of 'service' that you can query for just like emergency service. Can't the dial strings have their own definitions of regions of coverage that are separate from the region of coverage of a psap, for example?

* Its not clear how the region element actual specifies a region when it is composed of a series of civic addresses. What is the algorithm for determining whether my current address, expressed in civic coordinates, is inside or outside of a region defined that way?

* for dialstrings, suggest perhaps the KPML syntax for digit maps

6.6.  Validated Element

   Each validated element contains a string which is composed by by
   concatenating the elements from the request which have been
   recognized as valid by the server.

Very unclear what this means. I read it several times and couldn't make sense of it.

.7.  text Attribute

   This is a text type suitable for internationalized human readable
   text.


OK - but what is its semantic?


* It'd be nice to be able, in a single lost query, ask for multiple services for the same location

* For list service query: how do I ask for all services? Is it "urn:service"? "urn:"? "*"?

* Security aspects are still really weak. You need to specify basic proceudres as part of the basic client and server processing. Beyond mutual tls I think we want a standard server side authentication mechanism as well, with no client authentication




Minor:

* figure 1 makes it look like there are two queries (one that provides location, one that proviedes a service URN) followed by two responses. I'd suggest a single arrow in each direction

LoST supports a query using geospatial and civic location information
using the findLoSTByCivic and the findLoSTByGeo query. Geospatial
location information uses GML format [9] and civic location
information utilizes the format defined in [10].

you need to specify exactly which xml element you are talking abtou in both cases.

 The type of service desired is specified by the <service> element.
   The emergency identifiers listed in the registry established with [6]
   will be used in this document.


need to be clear that this is the service URN itself

* LoST talks in a bunch of places about 'call time', but this concept is specific to voip and I think LoST has applications beyond just voip. Maybe generalize this.

* is xml:lang being used for freeform text fields? I couldn't tell. Also, you may want to allow multiple text fields, each in a different lanuage, so that client can render the one it understands


Thanks,
Jonathan R.
--
Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
Cisco Fellow                                   Parsippany, NJ 07054-2711
Cisco Systems
jdrosen at cisco.com                              FAX:   (973) 952-5050
http://www.jdrosen.net                         PHONE: (973) 952-5000
http://www.cisco.com

_______________________________________________
Ecrit mailing list
Ecrit at ietf.org
https://www1.ietf.org/mailman/listinfo/ecrit