Service List Boundary (RFC 6197)

Problem: a LoST client (RFC 5222) does not know when available services changes when moving. So the following question arises: when should a client perform a new listServicesByLocation? Every time he moves for 10cm? Every 4 seconds?

Note that the problem of having the location based service list is independent of location based mapping of a particular service!

Without knowing the services for a particular location, the client cannot configure the emergency dialstrings which are necessary in order to detect an emergency call by the client. Hence, without the correct location dependant service list, the client might not be able to detect emergency calls. The serviceListBoundary tells the client when to update the service list.

Main Goal of serviceListBoundary: NEVER miss a change in the service list (and therefore being able to detect all emergency calls by the dialstring).

Further Information:

• Presentation at IETF 75
• The RFC is available at: http://tools.ietf.org/html/rfc6197