[pisa-src] r2425 - docs/protocol_spec/application.tex
- From: Thomas Jansen <mithi@xxxxxxxxx>
- To: pisa-src@xxxxxxxxxxxxx
- Date: Wed, 26 Jan 2011 14:44:58 +0100
Author: tjansen
Date: Wed Jan 26 14:44:58 2011
New Revision: 2425
Log:
minor corrections, question in a comment
Modified:
docs/protocol_spec/application.tex
Modified: docs/protocol_spec/application.tex
==============================================================================
--- docs/protocol_spec/application.tex Tue Jan 25 19:28:15 2011 (r2424)
+++ docs/protocol_spec/application.tex Wed Jan 26 14:44:58 2011 (r2425)
@@ -99,14 +99,14 @@
As a \emph{native client}, the client device directly constitutes the
communication endpoint in the PISA network.
This means, it holds an IPv4 address out of the PISA IP address range and
establishes HIP tunnels as well as PISA tunnels itself.
The currently associated access point serves just as a forwarder of routable
IP packets.
-More specifically, all PISA tasks such as NAT mappings, routing and especially
handovers are performed by the client
+More specifically, all PISA tasks such as NAT mappings, routing and especially
handovers are performed by the client.
As a \emph{legacy client}, all PISA services are performed by the associated
access point.
A legacy client is "defined" as an unmodified 802.11-capable wireless device
and thus handles only 802.11 tasks itself, according to its implementation.
PISA tasks such as establishing NAT mappings, tunnels, look-ups etc. are
performed by the associated access point.
The access points thus holds all the state for the client to participate in
the network, all PISA and HIP related aspects of the network such as tunneling,
anonymity and security only hold until the access point relays network traffic
as pure 802.11 frames to the client.
Especially, handovers, whether involuntarily or not, are triggered by the
client's wifi driver implementation, no further involvement (until now) by the
network is possible/takes place.
-Once the client associates with a new access point, this access point needs to
update it's NAT mappings, establish tunnels to the services the clients talks
to and, by sending a data packet or signaling packet, update the NAT mapping of
the communication endpoint.
+Once the client associates with a new access point, this access point needs to
update its NAT mappings, establish tunnels to the services the clients talks to
and, by sending a data packet or signaling packet, update the NAT mapping of
the communication endpoint.
\item[Service relay]
@@ -119,7 +119,7 @@
\item[DNS server]
-\item[Certificate Authority]
+\item[Certificate Authority] % Sollte das nicht eher Community Operator heißen
oder was unterschiedest du da?
\end{description}
--
This is the pisa developer mailing list. Please also subscribe to the main pisa
list at:
//www.freelists.org/list/pisa
Other related posts:
- » [pisa-src] r2425 - docs/protocol_spec/application.tex - Thomas Jansen
