[Gzz-commits] gzz/Documentation/misc/hemppah-progradu mastert...

[Hermanni Hyytiälä]

CVSROOT:        /cvsroot/gzz
Module name:    gzz
Changes by:     Hermanni Hyytiälä <address@hidden>      02/11/28 09:01:46

Modified files:
        Documentation/misc/hemppah-progradu: masterthesis.tex 

Log message:
        history finalized

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/gzz/Documentation/misc/hemppah-progradu/masterthesis.tex.diff?tr1=1.14&tr2=1.15&r1=text&r2=text

Patches:
Index: gzz/Documentation/misc/hemppah-progradu/masterthesis.tex
diff -u gzz/Documentation/misc/hemppah-progradu/masterthesis.tex:1.14 
gzz/Documentation/misc/hemppah-progradu/masterthesis.tex:1.15
--- gzz/Documentation/misc/hemppah-progradu/masterthesis.tex:1.14       Thu Nov 
28 07:52:52 2002
+++ gzz/Documentation/misc/hemppah-progradu/masterthesis.tex    Thu Nov 28 
09:01:45 2002
@@ -87,7 +87,7 @@
 Many defitions of P2P have been proposed in P2P community. The Intel P2P 
Working Group \cite{p2pworkinggroup} 
 defines P2P as "the sharing of computer resources and services by direct 
exchange between systems". Ross Lee 
 Graham \cite{graham02lecture} defines P2P through three requirements: 1) 
System has an operational computer 
-of server quality; 2) System has an addressing system independent of DNS 
\cite{rfc1101}; 3) System is able 
+of server quality; 2) System has an addressing system independent of DNS; 3) 
System is able 
 to cope with variable connectivity. O'Reilly's Clay Shirky proposes that "P2P 
is a class of applications 
 that takes advantage of resources - storage, cycles, content, human presence - 
available at the edges 
 of the Internet. Because accessing the decentralized resources means operating 
in a environment of unstable 
@@ -113,7 +113,7 @@
 [Figure 1. Insert picture]
 
 However, more detailed comparison of P2P systems and client-server approach is 
significantly more complex 
-along many dimensions: "There is no clear border between a client-server and a 
P2P model. Both models can be 
+because: "There is no clear border between a client-server and a P2P model. 
Both models can be 
 built on a spectrum of level of characteristics, functionality, organizations, 
components, protocols etc. Furthermore, 
 one mode can be built on top of the other or parts of the components can be 
realized in one or the other model. Finally, 
 both models can execute on different types of platforms and both can server as 
an underlying base for traditional 
@@ -123,23 +123,39 @@
 
 \subsection{A brief history}
 
-The Internet has been originally established in the late 1960s 
\cite{oram01harnessingpower}. 
-The aim of the ARPANET-project was to share computers' resources around the 
-United States. The most challenging purpose of ARPANET was to integrate 
different kinds of 
-existing network technologies with one common network architecture. The 
ARPANET connected 
-the first few hosts together not in client/server relationship, but rather as 
+The Internet has been originally established in the late 1960s. The objective 
of the ARPANET-project was to 
+share computers' resources around the United States. The most challenging 
purpose of ARPANET was to 
+integrate different kinds of existing network technologies with one common 
network architecture. The 
+ARPANET connected the first few hosts together not in client/server 
relationship, but rather as 
 equal networking peers. This could be seen as starting point both of P2P 
systems and 
-Internet [REFERENCE NEEDED!!!].
+Internet \cite{oram01harnessingpower}.
 
-While most early distributed applications can be considered P2P, e-mail 
systems and Usenet 
-News were probably the most extensively used. In both cases, local server 
created connections to 
-other peer servers to deliver messages into the user's mail box or into a 
spool box 
-containing messages from the newsgroups. The File Transfer Protocol (FTP) can 
be considered as a 
-predecessor to today's file-sharing P2P systems. Eventually, the Archie 
indexing system, was developed to 
+While most early distributed applications can be considered P2P, file transfer 
protocol (FTP), Usenet and Telnet 
+systems were probably the most extensively used. A Telnet client logged into a 
server, and 
+an FTP client downloaded and sent data to a file server. In the case of 
Usenet, peer servers connected 
+to other peers to deliver messages into the user's mail box or into a spool 
box containing messages from 
+the newsgroups. Altough  single application could be seen as was client/server 
relationship, the usage model as a 
+whole were symmetric. Every computer on the ARPANET could create connections 
to any other computer and use 
+each other's resources. The symmetry is what made the ARPANET so novel. As a 
implication, early ARPANET 
+made possible to create more complex systems as DNS \cite{rfc1101}. 
+
+In subsequent years, the Internet has become more restricted to client/server 
based applications. In 
+recent years, however, P2P systems have emerged a significant social and 
technical phenomenon. It could 
+be possible the Internet could revert to its initial symmetrical form. At the 
end, FTP can be considered as 
+a predecessor to today's file-sharing P2P systems. The Archie, global indexing 
system, was developed to 
 provide a central search infrastructure over existing FTP servers. Napster 
\cite{napsterurl} is a good 
 example of this kind of approach in modern P2P file-sharing systems.
 
 \subsection{Characteristics of P2P}
+
+Decentralization
+Scalability and adapion
+Anonymity and Autonomy
+Self-organization
+Cost Of ownership
+ad-hoc connectivity
+accountability
+reputation
 
 \subsection{Adaptations of P2P}