* Mobility Scenario

There was an agreement that the following functionality is required:

"
A device gets an indication from a LIS whether the returned location can
change. If it could change then the device gets a URI for a subsequent subscription.
"

A mandatory to implement protocol at the LIS for providing the
subscription and notification concept would be SIP. Hence, the LIS would
return a SIP URI and optionally other URIs (e.g., XMPP).

* Identifiers

There seems to be still a lot of confusion regarding the identifier
usage. Many different identifiers are possible, including IP addresses,
MAC addresses, ...

The following requirements were mentioned during the discussion:
* uniquely identifiers the device within the context of the device
* reasonable stable
* difficult for other people to use the identifier

The IP address was seen as a reasonable identifier but some doubts
regarding security were raised.

* Security

Brian and Rohan expressed concerned about the return-routability check
for IP addresses and the usage of TLS with server-side authentication in
context of MITM attacks. Brian mentiones that he wants to send a mail to
the list to express his thoughts in more detail.


Location signing
http://www3.ietf.org/proceedings/05aug/slides/geopriv-3/sld1.htm

* vs. HELD

no notion of context
just location, no PIDF-LO
no location assertion
other identifiers (but none specified)
uses HTTP error codes, not its own
Subscribe URL in response header