[pisa-src] r2422 - docs/protocol_spec/application.tex

From: Hanno Wirtz <Hanno.Wirtz@xxxxxxxxxxxxxxxxxxxxx>
To: pisa-src@xxxxxxxxxxxxx
Date: Mon, 24 Jan 2011 18:42:19 +0100
Author: wirtz
Date: Mon Jan 24 18:42:19 2011
New Revision: 2422

Log:
started naming and definition: Devices

Modified:
   docs/protocol_spec/application.tex

Modified: docs/protocol_spec/application.tex
==============================================================================
--- docs/protocol_spec/application.tex  Mon Jan 24 17:51:33 2011        (r2421)
+++ docs/protocol_spec/application.tex  Mon Jan 24 18:42:19 2011        (r2422)
@@ -55,7 +55,7 @@
 \section{Scenario Description}
 
 As a general scenario description, PISA establishes communication for mobile 
clients over untrusted, isolated access points to stationary services (or 
gateways).
-To this end, an addressing scheme to place clients, access points and services 
(gateways) in a common \emph{virtual} network and a means to establish 
communication in this
+To this end, an addressing scheme to place clients, access points and services 
(gateways) in a common \emph{virtual} }network and a means to establish 
communication in this
 network is necessary.
 
 PISA establishes a uniform, private, managed IPv4 network on top of a 
tunneling mechanism that allows for secure, bi-directional tunneled 
communication between globally routable IPv4 address endpoints.
@@ -66,6 +66,31 @@
 
 \section{Naming and Definitions}
 
+This section shortly introduces the participating devices, their roles in the 
network and the functionality that is provided on/by these devices.
+Beginning with the devices:
+
+\begin{description}
+
+\item[Client]
+Mobile device connected to an access point.
+Distinction between \emph{native} and \emph{legacy} client, with the native 
client providing the tunneling and NAT functionality itself.
+The legacy client relies on the current access point for this.
+\item[AP]
+Privately owned or company/university/city operated access point.
+Running openWRT or LCOS operating system and is able to connect to services or 
infrastructure devices over a HIP/IPsec tunnel.
+Base services running on an AP include HIP and PISA, DNS-relay (?), DHCP (?), 
etc. ...
+\item[Service]
+Service such as i8 localization services, community services by RegioIT.
+\item[Service Gateway]
+Gateway device to incorporate existing services (e.g., in a company network) 
into the PISA network via one central ingress/egress point.
+Logically separated from service but may be physically on the same machine.
+\item[Infrastructure Devices]
+Devices that hold a function for the whole network and are not specific to any 
user, service or client group. Includes timeserver, nameserver, CO, etc.
+Realized in a central fashion or replicated/redundantly at several partners.
+
+\end{description}
+
+
 \paragraph{Difference Connection vs. NAT mapping}
 
 \section{Connections}
@@ -78,17 +103,13 @@
 
 \section{Packet Types}
 
-\paragraph{PISA Header}
 \paragraph{Register}
 \paragraph{Register ACK}
-\paragraph{Heartbeat}
 \paragraph{Heartbeat ACK}
 \paragraph{De-Register}
 \paragraph{De-Register ACK}
 \paragraph{Data}
-Unused, was obsoleted by using two separate UDP-Ports to multiplex control and 
data packets.
 \paragraph{UNKNOWN HIT ?}
-Unused, intention unknown.
 
 \section{Protocol Workflows}
 
-- 
This is the pisa developer mailing list. Please also subscribe to the main pisa 
list at:
//www.freelists.org/list/pisa
[pisa-src] r2422 - docs/protocol_spec/application.tex

Other related posts:
