[Standards] LAST CALL: XEP-0255 (Location Query)

Dave Cridland dave at cridland.net
Tue May 4 15:16:25 UTC 2010

On Tue May  4 15:18:23 2010, XMPP Extensions Editor wrote:
> 1. Is this specification needed to fill gaps in the XMPP protocol  
> stack or to clarify an existing protocol?

My impression is that it fills gaps, and provides a XMPP-based  
network service which provides a valuable task, in support of clients  
wishing to perform XEP-0080 for example.

In particular, I suspect this represents a key component in making  
XEP-0080 usable for the majority of systems.

> 2. Does the specification solve the problem stated in the  
> introduction and requirements?

Partially - in particular, it's not entirely clear what the latter  
portion of the second paragraph of §1 actually means in practise. It  
does imply a substantial data retention and analysis capability on  
the location server, which in turn has ramifications for  

> 3. Do you plan to implement this specification in your code? If  
> not, why not?

I have often been tempted to implement it in a number of cases, but  
haven't yet - it certainly strikes me that it would make a valuable  
addition on a number of clients, assuming the existence of a suitable  

> 4. Do you have any security concerns related to this specification?

The existing §8 covers the most obvious cases of privacy. It might  
need to be expanded somewhat to highlight that this should cover data  
in flight in both directions, as well as any data retained by the  
location service.

It's not clear to me how the "publish" option might work in practise,  
however, so this may result in further security considerations.

> 5. Is the specification accurate and clearly written?
The "publish" option appears somewhat underspecified.

It implies that the location server has proxy-authorization  
capability, which is alarming - I see no direct need for this, but  
instead one assumes that the location server could be granted a  
Publisher affiliation on the PEP node, and hence be capable of simple  

It's not clear to me if this should be a distinct, optional, feature  
or not - which brings me onto a second point.

There is no XEP-0030 category or type specified for a location  
service, which means that a client wishing to discover a location  
server recommended by the server operator is  somewhat out of luck.  
I'd have thought that this would be generally useful, even if current  
implementations can have this server hardcoded.

Dave Cridland - mailto:dave at cridland.net - xmpp:dwd at dave.cridland.net
  - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
  - http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade

More information about the Standards mailing list