Basic SLoP Architectural Considerations

1
Basic SLoP Architectural Considerations

• 48th IETF Meeting Pittsburgh, PA
• SPATIAL BOF
• draft-loughney-spatial-arch-00.txt
• John A. Loughney

2
Outline

• Introduction
• Architecture
• Security
• What to Do Next
• Items for Future Study

3
Why?

• Spatial Location is an interesting parameter.
• Lots of potential services can be enabled.
• Lots of competing solutions, most proprietary.

4
Definitions

• Client the 'caller'
• Target the 'callee'
• Server entity which supplies the location of the
  target to the client. One end of the protocol.
• SLoP Spatial Location Protocol
• TAD Target record Accessing ID
• TID Target information ID

5
Basic Assumptions

• The way which the client and target learn the
  spatial location information is outside of the
  scope of this architecture.
• One format for spatial location information is
  used.
• Declare one default value.
• Allow for format negotiation,
• Allow extra information to be carried by the
  protocol (i.e. - zip code, country, etc). ??
• How formats are translated is outside of the
  scope of this architecture (initially).

6
Basic Architecture

• ---------- ----------
  ----------
• 
  
• client -------- server -------
  target
• 
  
• ---------- ----------
  ----------
• --------
• / \
• slop
• ---- policy --
• db
• \ /
• --------
• Red indicates within SLoP scope.

7
Broker Architecture

• 
  ----------
• 
  
• ------------- server
  1
• 
  
• 
  ----------
• ---------- ----------
  ----------
• slop
  
• client -------- broker ------- server
  2
• 
  
• ---------- ----------
  ----------
• 
  ----------
• 
  
• ------------- server
  3
• 
  
• 
  ----------

8
SLoP Server Proxying

• -------- --------
• SLoP SLoP ------ target
• client serv
• -------- -------- --- target
• SLoP SLoP
• -------- -------- --- target
• trans trans
• prot prot ---- target
• -------- --------
• IP IP
• -------- --------
• ----------------
• SLoP server / client application
• transport protocol UDP / TCP / SCTP (to be
  decided)

9
Security Issues

• Underlying Security Support
• Basic end-to-end IPSEC
• Hop-By-Hop Security
• Secure Proxying
• useful, but needs studying
• Payload encryption
• define standard encryption method

10
What To Do Next

• Security Architecture needs lots of work.
• Add section on basic assumptions.
• Add section on SLoP proxying.
• Rework roaming support.
• Policy architecture section.

11
For Future Study

• Roaming Support
• Broker support
• Server Discovery
• Authentication support
• Architecture for pushing own location

12
Multiple SLoP Server Architecture

• ---------- ----------
  ---------- ----------
• 
  home
• client -------- server -------
  server ------- target
• 
  
• ---------- ----------
  ---------- ----------