Bandwidth Management and Monitoring for IP Network Traffic: An

Total Page:16

File Type:pdf, Size:1020Kb

Bandwidth Management and Monitoring for IP Network Traffic: An Bandwidth Management and Monitoring for IP Network Traffic: An Investigation Barry Vivian William Irwin Submitted in fulfilment of the requirements for the Master of Science in the Department of Computer Science Rhodes University January 2001 Abstract Bandwidth management is a topic which is often discussed, but on which rela- tively little work has been done with regard to compiling a comprehensive set of techniques and methods for managing traffic on a network. What work has been done has concentrated on higher end networks, rather than the low bandwidth links which are commonly available in South Africa and other areas outside the United States. With more organisations increasingly making use of the Internet on a daily basis, the demand for bandwidth is outstripping the ability of providers to upgrade their infrastructure. This resource is therefore in need of management. In addition, for Internet access to become economically viable for widespread use by schools, NGOs and other academic institutions, the associated costs need to be controlled. Bandwidth management not only impacts on direct cost control, but encompasses the process of engineering a network and network resources in order to ensure the provision of as optimal a service as possible. Included in this is the provision of user education. Software has been developed for the implementation of traffic quotas, dynamic firewalling and visualisation. The research investigates various methods for monitoring and management of IP traffic with particular applicability to low bandwidth links. Several forms of visualisation for the analysis of historical and near-realtime traffic data are also discussed, including the use of three-dimensional landscapes. A number of band- width management practices are proposed, and the advantages of their combina- tion, and complementary use are highlighted. By implementing these suggested policies, a holistic approach can be taken to the issue of bandwidth management on Internet links. Preface The writer would like to acknowledge the help and assistance given by a number of individuals during the course of this research. My first thanks are to my supervi- sor, Mr George Wells for his input and for allowing me to follow my own ideas. I also wish to thank three fellow students for their contribution to this work; David Siebörger and Fred Fourie for their assistance in the development of the three- dimensional visualisation tools, in particular the animation sequences, and Guy Halse and David Siebörger for intellectual debate and discussions relating to the topic under study, often in the small hours. My appreciation also goes to Kevan Watkins and ‘Jaco’ Jacot-Guillarmod of the Rhodes University Information Tech- nology Division for their willingness to facilitate my data collection and testing. My appreciation also goes to the the Department of Computer Science at Rhodes University for the facilities and equipment without which this research would not have been possible. Finally, a very special thanks is expressed to my parents, for their support of this research, particularly for their critical discussion of the style and for proofreading. i Contents Preface i Table of Contents ii List of Figures vii List of Tables ix 1 Introduction 1 1.1 Aims . 2 1.2 Document Layout . 2 2 TCP Evolution and performance evaluation 4 2.1 Standards Process . 5 2.2 TCP Evolution . 6 2.2.1 Early developments . 6 2.2.2 TCP for Transactions (T/TCP) . 13 2.2.3 Selective Acknowledgement . 14 2.3 The Integration of Quality of Service . 14 2.4 Packet Sizing . 16 2.5 Future Development . 17 2.6 Summation . 18 ii CONTENTS iii 3 Monitoring and Visualisation 20 3.1 Monitoring . 20 3.1.1 Active monitoring . 21 3.1.2 Case Study 1: Bandwidth Probe . 21 3.1.3 Passive monitoring . 24 3.1.4 Case Study 2: Internet Traffic Monitor . 24 3.1.5 Suitability of monitoring . 27 3.1.6 Passive Monitoring Tools . 28 3.1.6.1 Tcpdump . 28 3.1.6.2 IP Flow meter (ipfm) . 29 3.1.6.3 Trafshow . 30 3.1.6.4 NTOP . 30 3.1.6.5 SNMP . 31 3.1.7 Sniffer Placement . 31 3.1.8 Active Tools . 33 3.1.8.1 Ping . 33 3.1.8.2 Bing . 33 3.1.8.3 Tcpblast . 35 3.1.8.4 Netperf . 35 3.2 Data Storage . 35 3.3 Visualisation . 37 3.3.1 The need for visualisation . 37 3.3.2 Visualisation types . 39 3.3.2.1 Simple Graphing . 39 3.3.2.2 Layered Graphs . 41 CONTENTS iv 3.3.2.3 Colour Maps . 44 3.3.2.4 Three-Dimensional Landscapes . 47 3.4 Other Interpretation Methods . 54 3.5 Summation . 54 4 Bandwidth Management Strategies 56 4.1 The ying-yang of bandwidth management . 57 4.2 Traffic Accounting Strategies . 59 4.2.1 Sub-Network Accounting . 59 4.2.2 Host Accounting . 59 4.2.3 User Accounting . 60 4.3 Quota Systems . 61 4.3.1 Running Quota Systems . 62 4.3.1.1 Calculation . 64 4.3.1.2 Quota Renewal . 64 4.3.2 Case Study 3: RUCUS Proxy Web and FTP Quotas . 68 4.3.3 Case Study 4: Quota based shaping on Cisco Routers . 71 4.4 Traffic Shaping . 76 4.4.1 Application Level . 78 4.4.2 IP Level . 79 4.4.2.1 DummyNet . 79 4.4.3 Case Study 5: Implementation of traffic shaping in the Squid Caching Web Proxy . 80 4.4.4 Case Study 6: Dummynet as a bandwidth management tool . 83 4.4.5 Hybrid Systems . 86 CONTENTS v 4.5 Traffic queues and Quality of Service . 87 4.5.1 Quality of Service . 89 4.5.1.1 First In First Out (FIFO) . 90 4.5.1.2 Priority Queueing (PQ) . 90 4.5.1.3 Fair Queueing (FQ) . 90 4.5.1.4 Stochastic Fairness Queueing (SFQ) . 91 4.5.1.5 Token Bucket Filter (TBF) . 91 4.5.1.6 Custom Queueing (CQ) . 91 4.5.1.7 Weighted Fair Queueing (WFQ) . 92 4.5.1.8 RSVP . 92 4.5.2 Congestion Avoidance . 93 4.5.2.1 Random Early Detection (RED) . 93 4.5.2.2 Gentle Random Early Detection (GRED) . 94 4.5.2.3 Weighted Random Early Detection (WRED) . 94 4.5.3 Type Of Service and Differentiated Service bits . 94 4.6 Active Content Control . 95 4.6.1 Case Study 7: ‘Ad-banner’ filtering and content filtering as a means of bandwidth saving. 96 4.7 Limitation of Services . 102 4.7.1 Implementing dynamic filtering as a means of traffic man- agement . 103 4.7.2 Case Study 8: A dynamic firewalling mechanism . 105 4.8 Threshold management . 109 4.9 Caching Proxy Servers . 110 4.10 Compression . 114 4.11 Network Address Translation . 116 CONTENTS vi 4.12 Satellite Connections . 117 4.13 User Education . 117 4.14 Summation . 119 5 Conclusion 120 Glossary 125 References 130 Appendicies 147 A Example Configurations 147 A.1 Squid . 147 A.1.1 Example User and host lists . 155 A.1.2 Content Type Blocklists . 156 A.1.3 Example proxy.pac . 157 A.2 IPFW Example . 158 A.2.1 Traffic Shaping . 158 A.2.2 Traffic Accounting . 159 A.3 Cisco Router Configuration . 162 A.3.1 Traffic Accounting . 163 A.3.2 Delay Configuration . 164 B An analysis of IP traffic on the Rhodes University network 167 B.1 TCP Traffic . 168 B.1.1 Source Ports . 168 B.1.2 Destination Ports . 168 CONTENTS vii B.2 UDP Traffic . 171 B.2.1 Source Ports . 171 B.2.2 Destination Ports . 172 B.3 ICMP . 172 B.4 Ranges of port usage . 174 B.5 Type of Service Field . 174 C Visualisation Tools and Techniques 175 C.1 Simple Graphing . 175 C.2 Layered Graphs . 175 C.3 Colour Maps . 176 C.4 Three-Dimensional Landscapes . 177 D Software Developed 179 D.1 Squid Quota Management . 179 D.2 Dynamic firewalling . 180 E CD-ROM Contents 181 List of Figures 2.1 The 4.3BSD Tahoe slow start algorithm . 8 3.1 Route between rucus.ru.ac.za and linux.moria.org . 22 3.2 Example output from the Bandwidth Probe . 23 3.3 Rhodes Internet link utilisation . 25 3.4 Logical layout of the traffic monitoring system . 25 3.5 Example output from monitor system . 26 3.6 Example tcpdump output illustrating decoding of four packets . 29 3.7 Example trafshow output of network traffic . 30 3.8 Placement options for a sniffer on a network . 32 3.9 Data Storage Methods vs Space Requirements . 38 3.10 Example MRTG and RRDTool Output . 40 3.11 Layered graphs . 43 3.12 Example Colour Maps . 46 3.13 Contour map . ..
Recommended publications
  • Cisco SCA BB Protocol Reference Guide
    Cisco Service Control Application for Broadband Protocol Reference Guide Protocol Pack #60 August 02, 2018 Cisco Systems, Inc. www.cisco.com Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco website at www.cisco.com/go/offices. THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
    [Show full text]
  • “Napster” Is Released (At Northeastern University) • 04/04/00
    • 03/07/97 - “Hotline” is released • 09/09/99 - “Napster” is released (at NorthEastern University) • 04/04/00 - “Gnutella 0.56” is released • 01/04/00 - “Napster” reaches 10 million downloads, but still has no revenue • 01/05/00 - Cable internet provider threaten to discontinue contracts with users that use “Napster” • 01/05/00 - Universal and Sony start to develop “Duet”, a “Napster” clone to be released 4/01 • 01/08/00 - AT&T start to develop “Publius”, a P2P network publishing system • 03/08/00 - Intel, HP and IBM create the “P2P Working Group” • 16/11/00 - Bertelsmann buys Napster; invests millions • 08/12/00 - Sun says it is working on a Java Peer-to-Peer platform • 18/01/01 - Microsoft initiates “Farsite” (“Federated, Available and Reliable Storage for an Incompletely Trusted Environment”) project [email protected] 24.1.01/UBIComp 1/44 • Background Etzard Stolte – History: P2P Networking IKS Group/ETH – A P2P Definition [email protected] – Merging technologies • What is out there? – File Sharing – Distributed Computing – Instant Messaging – Collaboration – Web Services • Summary • Discussion – Will P2P remain? – Will P2P be a profitable business concept? [email protected] 24.1.01/UBIComp 2/44 • Peer-to-Peer (P2P) has a specific meaning in many fields, e.g. – Literature (e.g. P2P review) – Psychology (e.g. counceling) – Education e.g. (peer groups) • In computer science P2P used to describe – A small network without dedicated server – Files and peripherals are shared – Some access control • What are then these P2P tools my younger sister talks about? – Isn’t the internet just a peer-to-peer network (e.g.
    [Show full text]
  • Diapositiva 1
    TRANSFERENCIA O DISTRIBUCIÓN DE ARCHIVOS ENTRE IGUALES (peer-to-peer) Características, Protocolos, Software, Luis Villalta Márquez Configuración Peer-to-peer Una red peer-to-peer, red de pares, red entre iguales, red entre pares o red punto a punto (P2P, por sus siglas en inglés) es una red de computadoras en la que todos o algunos aspectos funcionan sin clientes ni servidores fijos, sino una serie de nodos que se comportan como iguales entre sí. Es decir, actúan simultáneamente como clientes y servidores respecto a los demás nodos de la red. Las redes P2P permiten el intercambio directo de información, en cualquier formato, entre los ordenadores interconectados. Peer-to-peer Normalmente este tipo de redes se implementan como redes superpuestas construidas en la capa de aplicación de redes públicas como Internet. El hecho de que sirvan para compartir e intercambiar información de forma directa entre dos o más usuarios ha propiciado que parte de los usuarios lo utilicen para intercambiar archivos cuyo contenido está sujeto a las leyes de copyright, lo que ha generado una gran polémica entre defensores y detractores de estos sistemas. Las redes peer-to-peer aprovechan, administran y optimizan el uso del ancho de banda de los demás usuarios de la red por medio de la conectividad entre los mismos, y obtienen así más rendimiento en las conexiones y transferencias que con algunos métodos centralizados convencionales, donde una cantidad relativamente pequeña de servidores provee el total del ancho de banda y recursos compartidos para un servicio o aplicación. Peer-to-peer Dichas redes son útiles para diversos propósitos.
    [Show full text]
  • P2P Protocols
    CHAPTER 1 P2P Protocols Introduction This chapter lists the P2P protocols currently supported by Cisco SCA BB. For each protocol, the following information is provided: • Clients of this protocol that are supported, including the specific version supported. • Default TCP ports for these P2P protocols. Traffic on these ports would be classified to the specific protocol as a default, in case this traffic was not classified based on any of the protocol signatures. • Comments; these mostly relate to the differences between various Cisco SCA BB releases in the level of support for the P2P protocol for specified clients. Table 1-1 P2P Protocols Protocol Name Validated Clients TCP Ports Comments Acestream Acestream PC v2.1 — Supported PC v2.1 as of Protocol Pack #39. Supported PC v3.0 as of Protocol Pack #44. Amazon Appstore Android v12.0000.803.0C_642000010 — Supported as of Protocol Pack #44. Angle Media — None Supported as of Protocol Pack #13. AntsP2P Beta 1.5.6 b 0.9.3 with PP#05 — — Aptoide Android v7.0.6 None Supported as of Protocol Pack #52. BaiBao BaiBao v1.3.1 None — Baidu Baidu PC [Web Browser], Android None Supported as of Protocol Pack #44. v6.1.0 Baidu Movie Baidu Movie 2000 None Supported as of Protocol Pack #08. BBBroadcast BBBroadcast 1.2 None Supported as of Protocol Pack #12. Cisco Service Control Application for Broadband Protocol Reference Guide 1-1 Chapter 1 P2P Protocols Introduction Table 1-1 P2P Protocols (continued) Protocol Name Validated Clients TCP Ports Comments BitTorrent BitTorrent v4.0.1 6881-6889, 6969 Supported Bittorrent Sync as of PP#38 Android v-1.1.37, iOS v-1.1.118 ans PC exeem v0.23 v-1.1.27.
    [Show full text]
  • Network Defense Tools: Perimeter and Internal Defenses This Lecture
    CS 155 Spring 2006 Perimeter and Internal Defenses Network Defense Tools: Commonly deployed defenses Firewalls, Traffic shapers, and Perimeter defenses – Firewall, IDS Protect local area network and hosts Intrusion Detection Keep external threats from internal network Internal defenses – Virus scanning Protect hosts from threats that get through the perimeter defenses John Mitchell Extend the “perimeter” –VPN Common practices, but could be improved Internal threats are significant Unhappy employees Compromised hosts 2 This lecture Basic Firewall Concept Standard perimeter defense mechanisms Separate local area net from internet Firewall Packet filter (stateless, stateful) Application layer proxies Firewall Traffic shaping Intrusion detection Local network Internet Anomaly and misuse detection Methods applicable to network or host Router Future lectures Virus and malware Worm propagation and detection All packets between LAN and internet routed through firewall 3 4 Firewall goals Two Separable Topics Prevent malicious attacks on hosts Arrangement of firewall and routers Port sweeps, ICMP echo to broadcast addr, syn flooding, … Several different network configurations Worm propagation Separate internal LAN from external Internet Exploit buffer overflow in program listening on network Wall off subnetwork within an organization Prevent general disruption of internal network Intermediate zone for web server, etc. External SMNP packets Personal firewall on end-user machine Provide defense in depth How the firewall
    [Show full text]
  • Title: P2P Networks for Content Sharing
    Title: P2P Networks for Content Sharing Authors: Choon Hoong Ding, Sarana Nutanong, and Rajkumar Buyya Grid Computing and Distributed Systems Laboratory, Department of Computer Science and Software Engineering, The University of Melbourne, Australia (chd, sarana, raj)@cs.mu.oz.au ABSTRACT Peer-to-peer (P2P) technologies have been widely used for content sharing, popularly called “file-swapping” networks. This chapter gives a broad overview of content sharing P2P technologies. It starts with the fundamental concept of P2P computing followed by the analysis of network topologies used in peer-to-peer systems. Next, three milestone peer-to-peer technologies: Napster, Gnutella, and Fasttrack are explored in details, and they are finally concluded with the comparison table in the last section. 1. INTRODUCTION Peer-to-peer (P2P) content sharing has been an astonishingly successful P2P application on the Internet. P2P has gained tremendous public attention from Napster, the system supporting music sharing on the Web. It is a new emerging, interesting research technology and a promising product base. Intel P2P working group gave the definition of P2P as "The sharing of computer resources and services by direct exchange between systems". This thus gives P2P systems two main key characteristics: • Scalability: there is no algorithmic, or technical limitation of the size of the system, e.g. the complexity of the system should be somewhat constant regardless of number of nodes in the system. • Reliability: The malfunction on any given node will not effect the whole system (or maybe even any other nodes). File sharing network like Gnutella is a good example of scalability and reliability.
    [Show full text]
  • Investigating the User Behavior of Peer-To-Peer File Sharing Software
    www.ccsenet.org/ijbm International Journal of Business and Management Vol. 6, No. 9; September 2011 Investigating the User Behavior of Peer-to-Peer File Sharing Software Shun-Po Chiu (Corresponding author) PhD candidate, Department of Information Management National Central University, Jhongli, Taoyuan, Taiwan & Lecture, Department of Information Management Vanung University, Jhongli, Taoyuan, Taiwan E-mail: [email protected] Huey-Wen Chou Professor, Department of Information Management National Central University, Jhongli, Taoyuan, Taiwan E-mail: [email protected] Received: March 26, 2011 Accepted: May 10, 2011 doi:10.5539/ijbm.v6n9p68 Abstract In recent years, peer-to-peer file sharing has been a hotly debated topic in the fields of computer science, the music industry, and the movie industry. The purpose of this research was to examine the user behavior of peer-to-peer file-sharing software. A methodology of naturalistic inquiry that involved qualitative interviews was used to collect data from 21 university students in Taiwan. The results of the study revealed that a substantial amount of P2P file-sharing software is available to users. The main reasons for using P2P file-sharing software are to save money, save time, and to access files that are no longer available in stores. A majority of respondents use P2P file-sharing software to download music, movies, and software, and the respondents generally perceive the use of such software as neither illegal nor unethical. Furthermore, most users are free-riders, which means that they do not contribute files to the sharing process. Keywords: Peer to peer, File sharing, Naturalistic inquiry 1. Introduction In recent years, Peer-to-Peer (P2P) network transmission technology has matured.
    [Show full text]
  • Public Peer-To-Peer Filesharing Networks’ Evaluation
    PUBLIC PEER-TO-PEER FILESHARING NETWORKS’ EVALUATION J. Lloret Mauri1, B. Molina Moreno2, C. Palau Salvador3, M. Esteve Domingo4 Department of Communications, Polytechnic University of Valencia Camino Vera s/n, Valencia, Spain [email protected], [email protected], [email protected], [email protected] ABSTRACT • Download speed: some internal P2P network, due to Since the recent appearance of P2P file-sharing networks, its internal behaviour, are optimal for downloading many Internet users have chosen this technology to search files of reduced size. Others, however, use for programs, films, songs, etc. Their number of users is multisplitting mechanisms and permit the download growing every day due to the attractive and interesting from multiple sources, making them suitable for content type that can be found and downloaded over these obtaining larger files. networks. In this article six public architectures are analyzed, Gnutella, FastTrack, Opennap, Edonkey, MP2P These parameters are responsible for an architecture and Soulseek, tracking their evolution during a week in becoming very popular or, on the other hand, terms of connected users, number of files and size of disappearing. The above factors can make a P2P network shared files per hour. The results will be compared and more attractive to users of a specific nation due to the discussed with previous measurements taken a year ago. utilization of a specific language or even social trends [7]. These data can be used to design new network models, to It is also interesting to distinguish between a P2P network calculate their performance or to optimize new network and P2P client, the development of which must not be parameters.
    [Show full text]
  • Paul Collins Status Name/Startup Item Command Comments X System32
    SYSINFO.ORG STARTUP LIST : 11th June 2006 (c) Paul Collins Status Name/Startup Item Command Comments X system32.exe Added by the AGOBOT-KU WORM! Note - has a blank entry under the Startup Item/Name field X pathex.exe Added by the MKMOOSE-A WORM! X svchost.exe Added by the DELF-UX TROJAN! Note - this is not the legitimate svchost.exe process which is always located in the System (9x/Me) or System32 (NT/2K/XP) folder and should not normally figure in Msconfig/Startup! This file is located in the Winnt or Windows folder X SystemBoot services.exe Added by the SOBER-Q TROJAN! Note - this is not the legitimate services.exe process which is always located in the System (9x/Me) or System32 (NT/2K/XP) folder and should not normally figure in Msconfig/Startup! This file is located in a HelpHelp subfolder of the Windows or Winnt folder X WinCheck services.exe Added by the SOBER-S WORM! Note - this is not the legitimate services.exe process which is always located in the System (9x/Me) or System32 (NT/2K/XP) folder and should not normally figure in Msconfig/Startup! This file is located in a "ConnectionStatusMicrosoft" subfolder of the Windows or Winnt folder X Windows services.exe Added by the SOBER.X WORM! Note - this is not the legitimate services.exe process which is always located in the System (9x/Me) or System32 (NT/2K/XP) folder and should not normally figure in Msconfig/Startup! This file is located in a "WinSecurity" subfolder of the Windows or Winnt folder X WinStart services.exe Added by the SOBER.O WORM! Note - this is not the legitimate
    [Show full text]
  • When Worlds Collide the Intersection of Constructivism, Learning Objects, and Peer-To-Peer Networking Technologies
    When Worlds Collide The intersection of constructivism, learning objects, and peer-to-peer networking technologies David Wiley (and hopefully others soon) v1.3, November 6, 2000 The current conception of learning objects There is a vision. A vision in which the creation of instruction can be automated; in which a computer program is capable of inspecting, selecting, and assembling learning objects in order to instantiate an instructional design. And why not? From automobiles to computer processors, humans have succeeded in automating some pretty complex assembly processes. Historically, the success of automation has relied on two factors. The first is an understanding of the assembly process, first discovered and performed by hand, then captured, studied, and expressed in a technology. The second factor is the standardization of component properties. The standardization of component properties creates a marketplace in which many vendors can create components competitively. The broad availability of inexpensive standardized components makes assembly processes easier to express in concrete terms. For example, once standard building construction components such as bricks and two-by-fours were widely available, it became easier to create detailed building plans. The construction metaphor is an apt one for the current discussion, as the current term “learning objects” is borrowed from the 1994 CEdMA working group entitled “Learning Architectures and Learning Objects” (LALO), in which the Architecture is the expression of the construction or assembly process (the blueprint), and the Objects are the standardized components (bricks and boards). But our concern is the facilitation of learning. In our case, the assembly plans are probabilistic instructional design theories and models, prescriptive methods likely to facilitate learning.
    [Show full text]
  • Praktische Untersuchung Und Vergleich Von Gnutella, Kazaa, Edonkey Und Soulseek
    Universität Karlsruhe (TH) Praktische Untersuchung und Vergleich von Gnutella, KaZaA, eDonkey und SoulSeek Studienarbeit am Institut für Telematik Prof. Dr.rer.nat. Martina Zitterbart Fakultät für Informatik Universität Karlsruhe (TH) von cand. inform. Christian Wagner Betreuer: Prof. Dr.rer.nat. Martina Zitterbart Dr.rer.nat Thomas Fuhrmann Dipl.-Ing. Kendy Kutzner Tag der Anmeldung: 21. Juli 2003 Tag der Abgabe: 1. Dezember 2003 Institut für Telematik Ich erkläre hiermit, dass ich die vorliegende Arbeit selbstständig verfasst und keine anderen als die angegebenen Quellen und Hilfsmittel verwendet habe. Karlsruhe, den 1. Dezember 2003 Inhaltsverzeichnis 1. Einleitung ..................... 1.1 Gliederung der Arbeit....................................................................................... 1 " #to-Peer Netze ............................................................................. & 2.1 Geschichte ........................................................................................................ 3 2.2 Definition.......................................................................................................... 4 2.3 Modelle von P2P-Netzen.................................................................................. 5 2.3.1 P2P-Systeme mit einem zentralen Server................................................. 5 2.3.2 Dezentrale P2P-Systeme........................................................................... 7 2.3.3 Hybride P2P-Systeme..............................................................................
    [Show full text]
  • Omnix: an Open Peer-To-Peer Middleware Framework
    Omnix: An Open Peer-to-Peer Middleware Framework Engineering Topology- and Device-Independent Peer-to-Peer Systems Ph.D. Thesis Roman Kurmanowytsch DISSERTATION Omnix: An Open Peer-to-Peer Middleware Framework Engineering Topology- and Device-Independent Peer-to-Peer Systems ausgefuhrt¨ zum Zwecke der Erlangung des akademischen Grades eines Doktors der technischen Wissenschaften unter der Leitung von o.Univ.-Prof. Dipl.-Ing. Dr.techn. Mehdi Jazayeri Institut fur¨ Informationssysteme Abteilung fur¨ Verteilte Systeme (E184-1) eingereicht an der Technischen Universitat¨ Wien Fakultat¨ fur¨ Informatik von Univ.-Ass. Dipl.-Ing. Roman Kurmanowytsch [email protected] Matrikelnummer: 9327324 Brunnerstr. 28/12 A-1230 Wien, Osterreich¨ Wien, im Februar 2004 Omnix: An Open Peer-to-Peer Middleware Framework Engineering Topology- and Device-Independent Peer-to-Peer Systems Ph.D. Thesis at Vienna University of Technology submitted by Dipl.-Ing. Roman Kurmanowytsch Distributed Systems Group, Information Systems Institute, Technical University of Vienna Argentinierstr. 8/184-1 A-1040 Vienna, Austria 1st February 2004 c Copyright 2004 by Roman Kurmanowytsch Advisor: o. Univ.-Prof. Dr. Mehdi Jazayeri Second Advisor: a.o. Univ.-Prof. Dr. Gabriele Kotsis Abstract In this thesis, we present Omnix, a Peer-to-Peer (P2P) middleware framework. P2P mid- dleware provides an abstraction between the application and the underlying network by pro- viding higher-level functionality such as distributed P2P searches and direct communication among peers. P2P networks build an overlay network, a network on the network. The central idea of this dissertation is to apply the well-established ISO OSI layered model on P2P middleware systems. A layered P2P architecture helps to identify separate parts of a complex system, allows changes to the system without affecting other layers and makes maintenance easier due to modularization.
    [Show full text]