Thesis (M.S. in Computer Science)--Naval Postgraduate School, March 2004. / Thesis advisor(s): Geoffrey Xie. Includes bibliographical references (p. 155-156). Also available online.

Thesis (Ph. D.) University of Missouri-Columbia, 2006. / The entire dissertation/thesis text is included in the research.pdf file; the official abstract appears in the short.pdf file (which also appears in the research.pdf); a non-technical general description, or public abstract, appears in the public.pdf file. Title from title screen of research.pdf file (viewed on July 31, 2007) Includes bibliographical references.

Thesis (M.S. in Computer Science)--Naval Postgraduate School, March 2004. / Thesis advisor(s): Wen Su, John Gibson. Includes bibliographical references (p. 189). Also available online.

published_or_final_version / abstract / Electrical and Electronic Engineering / Doctoral / Doctor of Philosophy

This paper discusses current network technologies and protocols and presents a simulation study of the most common networking protocol used today, TCP/IP. The TCP/IP protocol stack has many inherent problems that will be shown through this simulation study. Using the SimpleScalar Toolset, the significance of the data copying and checksumming performed in TCP/IP will be shown along with the architecture needed to support the processing of TCP/IP. Solutions for these TCP/IP pitfalls including a zero-copy protocol and a design for an intelligent network interface card will also be presented. / Graduation date: 2000

Thesis (Ph. D.)--University of Hong Kong, 2006. / Title proper from title frame. Also available in printed format.

abstract / Computer Science / Doctoral / Doctor of Philosophy

Yuen Ka-nang. / Thesis (M.Phil.)--Chinese University of Hong Kong, 2001. / Includes bibliographical references (leaves 133-135). / Abstracts in English and Chinese. / Abstract --- p.i / Acknowledgement --- p.iii / Chapter 1. --- INTRODUCTION --- p.1 / Chapter 1.1. --- Background --- p.1 / Chapter 1.2. --- Objectives --- p.1 / Chapter 1.3. --- Overview of Thesis --- p.2 / Chapter 2. --- NETWORK ASPECT OF THE VOIP TECHNOLOGY --- p.3 / Chapter 2.1. --- VoIP Overview --- p.3 / Chapter 2.2. --- Elements in VoIP --- p.3 / Chapter 2.2.1. --- Call Setup --- p.3 / Chapter 2.2.2. --- Media Capture/Playback --- p.4 / Chapter 2.2.3. --- Media Encoding/Decoding --- p.4 / Chapter 2.2.4. --- Media Transportation --- p.5 / Chapter 2.3. --- Performance Factors Affecting VoIP --- p.6 / Chapter 2.3.1. --- Network Bandwidth --- p.6 / Chapter 2.3.2. --- Latency --- p.6 / Chapter 2.3.3. --- Packet Loss --- p.7 / Chapter 2.3.4. --- Voice Quality --- p.7 / Chapter 2.3.5. --- Quality of Service (QoS) --- p.7 / Chapter 2.4. --- Different Requirements of Intranet VoIP and Internet VoIP --- p.8 / Chapter 2.4.1. --- Packet Loss/Delay/Jitter --- p.8 / Chapter 2.4.2. --- Interoperability --- p.9 / Chapter 2.4.3. --- Available Bandwidth --- p.9 / Chapter 2.4.4. --- Security Requirement --- p.10 / Chapter 2.5. --- Some Feasibility Investigations --- p.10 / Chapter 2.5.1. --- Bandwidth Calculation --- p.10 / Chapter 2.5.2. --- Simulation --- p.12 / Chapter 2.5.3. --- Conclusion --- p.17 / Chapter 2.5.4. --- Simulation Restrictions --- p.17 / Chapter 3. --- SOFTWARE ASPECT OF THE VOIP TECHNOLOGY --- p.19 / Chapter 3.1. --- VoIP Client in JMF --- p.19 / Chapter 3.1.1. --- Architecture --- p.20 / Chapter 3.1.2. --- Incoming Voice Stream Handling --- p.23 / Chapter 3.1.3. --- Outgoing Voice Stream Handling --- p.23 / Chapter 3.1.4. --- Relation between Incoming/Outgoing Voice Stream Handling --- p.23 / Chapter 3.1.5. --- Areas for Further Improvement --- p.25 / Chapter 3.2. --- Capture/Playback Enhanced VoIP Client --- p.26 / Chapter 3.2.1. --- Architecture --- p.27 / Chapter 3.2.2. --- Native Voice Playback Mechanism --- p.29 / Chapter 3.2.3. --- Native Voice Capturing Mechanism --- p.31 / Chapter 3.3. --- Win32 C++ VoIP Client --- p.31 / Chapter 3.3.1. --- Objectives --- p.32 / Chapter 3.3.2. --- Architecture --- p.33 / Chapter 3.3.3. --- Problems and Solutions in Implementation --- p.37 / Chapter 3.4. --- Win32 DirectSound C++ VoIP Client --- p.38 / Chapter 3.4.1. --- Architecture --- p.39 / Chapter 3.4.2. --- DirectSound Voice Playback Mechanism --- p.40 / Chapter 3.4.3. --- DirectSound Voice Capturing Mechanism --- p.44 / Chapter 3.5. --- Testing VoIP Clients --- p.45 / Chapter 3.5.1. --- Setup of Experiment --- p.45 / Chapter 3.5.2. --- Experiment Results --- p.47 / Chapter 3.5.3. --- Experiment Conclusion --- p.48 / Chapter 3.6. --- Real-time Voice Stream Mixing Server --- p.48 / Chapter 3.6.1. --- Structure Overview --- p.48 / Chapter 3.6.2. --- Experiment --- p.53 / Chapter 3.6.3. --- Conclusion --- p.54 / Chapter 4. --- EXPERIMENTAL STUDIES --- p.55 / Chapter 4.1. --- Pure IP-side VoIP-based Call Center ´ؤ VoIP in Education --- p.55 / Chapter 4.1.1. --- Architecture --- p.55 / Chapter 4.1.2. --- Client Structure --- p.56 / Chapter 4.1.3. --- Client Applet User Interface --- p.58 / Chapter 4.1.4. --- Observations --- p.63 / Chapter 4.2. --- A Simple PBX Experiment --- p.63 / Chapter 4.2.1. --- Structural Overview --- p.63 / Chapter 4.2.2. --- PSTN Gateway Server Program --- p.64 / Chapter 4.2.3. --- Problems and Solutions in Implementation --- p.66 / Chapter 4.2.4. --- Experiment 1 --- p.66 / Chapter 4.2.5. --- Experiment 2 --- p.68 / Chapter 5. --- A COMPREHENSIVE VOIP PROJECT 一 GRADUATE SECOND PHONE (GSP) --- p.72 / Chapter 5.1. --- Overview --- p.72 / Chapter 5.1.1. --- Background --- p.72 / Chapter 5.1.2. --- Architecture --- p.76 / Chapter 5.1.3. --- Technologies Used --- p.78 / Chapter 5.1.4. --- Major Functions --- p.80 / Chapter 5.2. --- Client --- p.84 / Chapter 5.2.1. --- Structure Overview --- p.85 / Chapter 5.2.2. --- Connection Procedure --- p.89 / Chapter 5.2.3. --- User Interface --- p.91 / Chapter 5.2.4. --- Observations --- p.92 / Chapter 5.3. --- Gateway --- p.94 / Chapter 5.3.1. --- Structure Overview --- p.94 / Chapter 5.3.2. --- Connection Procedure --- p.97 / Chapter 5.3.3. --- Caller ID Simulator --- p.97 / Chapter 5.3.4. --- Observations --- p.98 / Chapter 5.4. --- Server --- p.101 / Chapter 5.4.1. --- Structure Overview --- p.101 / Chapter 5.5. --- Details of Major Functions --- p.103 / Chapter 5.5.1. --- Secure Local Voice Message Box --- p.104 / Chapter 5.5.2. --- Call Distribution --- p.106 / Chapter 5.5.3. --- Call Forward --- p.112 / Chapter 5.5.4. --- Call Transfer --- p.115 / Chapter 5.6. --- Experiments --- p.116 / Chapter 5.6.1. --- Secure Local Voice Message Box --- p.117 / Chapter 5.6.2. --- Call Distribution --- p.118 / Chapter 5.6.3. --- Call Forward --- p.121 / Chapter 5.6.4. --- Call Transfer --- p.122 / Chapter 5.6.5. --- Dial Out --- p.124 / Chapter 5.7. --- Observations --- p.125 / Chapter 5.8. --- Outlook --- p.126 / Chapter 5.9. --- Alternatives --- p.127 / Chapter 5.9.1. --- Netmeeting --- p.127 / Chapter 5.9.2. --- OpenH323 --- p.128 / Chapter 6. --- CONCLUSIONS --- p.129 / Bibliography --- p.133

Instant Messaging (IM) has grown rapidly among network users. It has even become a very important tool for the industry around the world. It is used in scheduling meetings, exchanging business information and clients information, and so on. Instant Messaging has been developed by private sectors or providers such as America Online Instant Messenger (AIM), MSN, and Yahoo; however, in 1998 a new protocol has seen the light as an open source Instant Messaging protocol and had the name of Jabber and thanks to Jeremie Miller the founder of the Jabber protocol. The project gathered wide public attention when it was discussed on the popular developer discussion website Slashdot in January 1999. In May 2000, the core Jabber protocols were released as open source reference server and it have not been changed to this day. Jabber uses client-server architecture, not a direct peer-to-peer architecture as some other messaging systems do. It is actually an Extensible Markup Language (XML) messaging protocol. It relies on XML document format in every aspect of the communication. [1] Jabber Protocol have gone a long way to be one of the most attractive protocol because of its open source and extensibility. Anyone can build or extend the jabber protocol functionality without actually modifying the core protocol and still maintain interoperability with other IM clients such as Yahoo and MSN. Moreover, as the usage of Jabber Instant Messaging technology increases, the need for information protection in the Jabber messaging medium also increases. This thesis will explore the Jabber protocol and the ability to secure a Jabber based communication over the network using third party cryptographic libraries. / Graduation date: 2003

Thesis (M.S.)--Worcester Polytechnic Institute. / Keywords: Loss; TFRC; AIMD; TCP. Includes bibliographical references (p. 147-155).