2.1.18 Spatial Location (spatial) bof

Current Meeting Report

Spatial Location BOF Meeting Report
IETF-48, Pittsburgh, PA, USA
Monday 31st July 2000, 19:30 - 22:00
Chairs: Haitao Tang and James M. Polk

Minutes reported by: Jussi Ruutu and Mari Korkea-aho


Agenda Bashing

The agenda was accepted as shown above.

Scope of the BOF by Haitao Tang

The purpose of this effort is to have a standard protocol, called Spatial Location Protocol (SLoP), for an application to acquire the spatial location of an identifiable resource over or represented on the Internet in a reliable, secure and scalable manner.

The basic model for SLoP includes three components:

The scope of the SLOP BOF/WG is to define

The way how the location is determined is out of the scope of SLoP.

Q: This kind of approach is useful also for a number of other protocols, not just for spatial location.
A: Yes

Q: Does this SLoP also include moving targets
A: Yes.

Q: Is the server assumed to be static?
A: No.
C: To standardize the way of add location information into existing protocols.

Individual presentations

Spatial Location Protocol Requirements by Brian Rosen

Document contains requirements for the SLoP. Document written by a small team and it contains seven sections.

Document includes:

Q: There are other activities at other places. Do you know?
A: We are aware but want to focus

The protocol must define one default location representation. Protocol must also permit as a minimum certain values to be included in a report, such as used location type, geocentric position, accuracy, exactness, time stamp, etc. Multiple representations must be supported in a single report. Protocol must
be also extendible.

Q: Is authentication included?
A: It is in the next part. Authenticate first and check what you can do next. IPsec is most possibly used.

A Simple Text Format for the Spatial Location Protocol by Rohan Mahy

Main part of the presentation on the philosophy and motivation of the draft.

Single question:
What is the location of the target? This is the basic question that is most often needed. Single reference system; Geocentric (near Earth) location. This is practical now.

What use is the simple text format: Common geocentric exchange format; If I know my geocentric location it is convertible to WGS84

How do I get my location
Fixed configuration
Global Positioning System
Inertial Navigation
Dead Reckoning

Example models include:

1) Target and server are physically the same (Where am I?)

2) Proxy is between target/Server and client. Simple coordinates can be used between client and proxy. Target is IP device.
3) Target is non IP device.

Simple means:

Q: Is time required?
A: No.

Still flexible:

Out of scope:

What next?
Correct altitude terminology

Is this sufficient for default SLoP format?

Target Naming Scheme by Haitao Tang

This is an individual contribution.

This contains target record name and server info

TID - Target information ID

Contains target profile and owner/server profile

Basic SLoP Architectural Considerations by John Loughney

Serves as input for future architectural IDs

Basic Assumptions

Broker architecture is going to be needed since the number of SLoP servers may be huge. Broker is positioned between client and server(s)

Security issues:

Future study

Louis Hecht, OGC consortium

OGC's Comments:

Charter Bashing (James Polk)

Seven focus areas within current charter

Spatial location representations

C: We seem to have lots of good reasons for somebody in IETF to worry about location.
Q: Three big problems/questions addressed in BOF. Go just down to one?
C: Split the transport and representation issues of the charter. Take naming, privacy... away.

The BOF consensus:

Meeting closed.


Target Naming Scheme
Spatial Location Charter
Basic SLoP Architectural Considerations