JPPP specification ver0.２
(Lastupdate 2001/2/21)
Introduction
The intention behind JPPP is to build a practical p2p protocol for dynamic
wireless networks, that will operate in the face of shifting topologies.
JPPP has following features;
■fully decentralized
JPPP is intended for fully decentralized operation, avoiding the use of
central servers of the "client-server" framework. Central server
based systems such as Napster, or MojoNation's metatracker try to guarantee
some degree of traffic quality, an assumption that cannot be made in wireless
networks where connection to some central locus of control may not be possible.
■ad-hoc network
In wireless networks nodes (=devices ) are potentially mobile, opening
up the possibility that the network topology will change over time, with
nodes disappearing and appearing as they move in and out of broadcast range.
Because of this we can make certain assumptions:
・A static node tables will not be able to cover the whole network.
・The network position of the node cannot be guessed from terminal
specific information, such as a device ID.
・Effective routes will potentially change suddenly and dramatically.
JPPP is a protocol intended to address these issues and support reliable
network routing under these assumptions.
Please give me your feedbacks and questions to umeda@jnutella.org.
Moreover, specification decision of this protocol is performed by JnudevML.
U Join us?
日本語はこちら |
