! Aware > default selections > Activity specific > Software Development > Protocol Development >

Protocol Development

Theory and techniques for developing communications protocols.
Subsets on this page: - #Articles - #Info -
Search ! Aware:

  By ANN

Search all pages


By activity
Professions, Sciences, Humanities, Business, ...

User Interface
Text-based, GUI, Audio, Video, Keyboards, Mouse, Images,...

Text Strings
Conversions, tests, processing, manipulation,...

Integer, Floating point, Matrix, Statistics, Boolean, ...

Algorithms, Memory, Process control, Debugging, ...

Stored Data
Data storage, Integrity, Encryption, Compression, ...

Networks, protocols, Interprocess, Remote, Client Server, ...

Hard World
Timing, Calendar and Clock, Audio, Video, Printer, Controls...

File System
Management, Filtering, File & Directory access, Viewers, ...

Information and Publications: Showing

RFC1644 T/TCP -- TCP Extensions for Transactions Functional Specification. [c. 1994/07/01]

RFC1693 An Extension to TCP : Partial Order Service. [c. 1994/11/01]

RFC2416 When TCP Starts Up With Four Packets Into Only Three Buffers. [c. 1998/09/01]

RFC1819 Internet Stream Protocol Version 2 (ST2) Protocol Specification - Version ST2+. [c. 1995/08/01]

RFC2415 Simulation Studies of Increased Initial TCP Window Size. [c. 1998/09/01]

RFC2414 Increasing TCP's Initial Window. [c. 1998/09/01]

RFC2372 Transaction Internet Protocol - Requirements and Supplemental Information. [c. 1998/07/01]

RFC2371 Transaction Internet Protocol Version 3.0. [c. 1998/07/01]

RFC2244 ACAP -- Application Configuration Access Protocol. [c. 1997/11/01]

RFC2188 AT&T/Neda's Efficient Short Remote Operations (ESRO) Protocol Specification Version 1.2. [c. 1997/09/01]

RFC1715 The H Ratio for Address Assignment Efficiency. [c. 1994/11/01]

RFC1710 Simple Internet Protocol Plus White Paper. [c. 1994/10/01]

RFC1707 CATNIP: Common Architecture for the Internet. [c. 1994/10/01]

RFC1287 Towards the Future Internet Architecture. [c. 1991/12/01]

RFC1692 Transport Multiplexing Protocol (TMux). [c. 1994/08/01]

RFC1475 TP/IX: The Next Internet. [c. 1993/06/01]

RFC1622 Pip Header Processing. [c. 1994/05/01]

RFC1621 Pip Near-term Architecture. [c. 1994/05/01]

RFC1560 The MultiProtocol Internet. [c. 1993/12/01]

RFC1527 What Should We Plan Given the Dilemma of the Network?. [c. 1993/09/01]

RFC1454 Comparison of Proposals for Next Version of IP. [c. 1993/05/01]

RFC1379 Extending TCP for Transactions -- Concepts. [c. 1992/11/01]

RFC1363 A Proposed Flow Specification. [c. 1992/09/01]

RFC1326 Mutual Encapsulation Considered Dangerous. [c. 1992/05/01]

RFC1323 TCP Extensions for High Performance. [c. 1992/05/01]

RFC1263 TCP Extensions Considered Harmful. [ 1991/10/01]

RFC1257 Isochronous applications do not require jitter-controlled networks. [ 1991/09/01]

RFC1237 Guidelines for OSI NSAP Allocation in the Internet. [ 1991/07/01]

RFC1241 Scheme for an internet encapsulation protocol: Version 1. [ 1991/07/01]

RFC1254 Gateway Congestion Control Survey. [ 1991/07/01]

RFC1240 OSI connectionless transport services on top of UDP: Version 1. [ 1991/06/01]

RFC1221 Host Access Protocol (HAP) specification: Version 2. [ 1991/04/01]

RFC1202 Directory Assistance service. [ 1991/02/01]

RFC1151 Version 2 of the Reliable Data Protocol (RDP). [ 1990/04/01]

RFC1077 Critical issues in high bandwidth networking. [ 1988/11/01]

RFC1030 On testing the NETBLT Protocol over divers networks. [ 1987/11/01]

RFC1017 Network requirements for scientific research: Internet task force on scientific computing. [ 1987/08/01]

RFC1018 Some comments on SQuID. [ 1987/08/01]

RFC1016 Something a host could do with source quench: The Source Quench Introduced Delay (SQuID). [ 1987/07/01]

RFC1006 ISO transport services on top of the TCP: Version 3. [ 1987/05/01]

RFC0992 On communication support for fault tolerant process groups. [ 1986/11/01]

RFC0979 PSN End-to-End functional specification. [ 1986/03/01]

RFC0970 On packet switches with infinite storage. [ 1985/12/01]

RFC0962 TCP-4 prime. [ 1985/11/01]

RFC0955 Towards a transport service for transaction processing applications. [ 1985/09/01]

RFC0938 Internet Reliable Transaction Protocol functional and interface specification. [ 1985/02/01]

RFC0935 Reliable link layer protocols. [ 1985/01/01]

RFC0902 ARPA Internet Protocol policy. [ 1984/07/01]

RFC0893 Trailer encapsulations. [ 1984/04/01]

RFC0871 Perspective on the ARPANET reference model. [ 1982/09/01]

RFC0874 Critique of X.25. [ 1982/09/01]

RFC0875 Gateways, architectures, and heffalumps. [ 1982/09/01]

RFC0824 CRONUS Virtual Local Network. [ 1982/08/25]

RFC0817 Modularity and efficiency in protocol implementation. [ 1982/07/01]

RFC0794 Pre-emption. [ 1981/09/01]

RFC0787 Connectionless data transmission survey/tutorial. [ 1981/07/01]

Articles: Showing

Agent Communication Languages: Rethinking the Principles ( Munindar P. Singh ; IEEE Computer Magazine 1998-12)

- Agent communication languages have been used for years in proprietary multiagent systems. Yet agents from different vendorsóor even different research projectsócannot communicate with each other. The author looks at the underlying reasons and proposes a conceptual shift from individual agent representations to social interaction.

Codesign of Communication Protocols ( Alan S. Wenban, John W. O'Leary, Geoffrey M. Brown ; IEEE Computer Magazine 1993-12)

- A codesign process using Promela, a concurrent programming language, is under development. A description is given of Promela, the software compiler, and the hardware compiler. As an example, the method is applied to a simple communication system using the alternating bit protocol.

Formal Models of Communication Services: A Case Study ( Alan Feteke ; IEEE Computer Magazine 1993-08)

- Formal methods can play an important role in exploring new communication systems services. The telecommunications and data communications communities have long accepted the need for formally describing protocols, but only recently have they considered formally describing a service by abstracting specifications from a particular protocol that provides that service. Specifying a service at an abstract level meets two important needs: standardization and customization. The author presents a simplified atomic multicast as an example service and input/output automata for the formal model. He shows how to represent the service specification, a protocol, and implementations of that protocol. He also sketches how to prove the correctness of the protocol and implementation, that is, how to show that the specified service is actually provided.

The Programmable Network Prototyping System ( Randy Cieslak, Ayman Fawaz, Sonia Sachs, Pravin Varaiya, Jean Warland, Albert Li ; IEEE Computer Magazine 1989-05)

- The programmable network prototyping system (PNPS) uses a collection of reusable hardware modules that implement generic communications functions such as transmission, reception, signal propagation, and pattern matching. These modules are interconnected and configured to emulate a variety of communication networks whose behavior can be monitored under different load conditions. The user specifies a network as a set of interacting components using available software tools. These tools are accessible within a prototyping environment that includes a control system for configuring the hardware modules and interconnecting them according to the component specifications. Previously designed components are stored in a library and can be used to specify new networks. Although PNPS is designed to provide a prototyping environment for communication networks, some of the basic ideas can be useful in other contexts.

Related Subjects (default selections)

(The following links to subjects at this site retain your personalized selections.)

Up to Activity specific - Gateway topic to software used in specific activities. (application software, business, professional, science, education, etc.)

Up to Software Development - Tools and utilities for software development

(There may be additional related subject pages listed here)


Use our system: Bring Rapid Knowledge Transfer and Awareness to your company website!

Rapid-Links: Search | About | Comments | Submit Path: RocketAware > Activity specific > Software Development > Protocol Development >
RocketAware.com is a service of Mib Software
Copyright 2002, Forrest J. Cavalier III. All Rights Reserved.
We welcome submissions and comments