In this paper we describe a new approach to implementing network protocols that enables them to have high performance and high flexibility, while retaining complete conformity to existing application programming interfaces. The key insight behind our work is that an application's interface to the network is distinct and separable from its interface to the operating system. We have separated these interfaces for two protocol implementations, TCP/IP and UDP/IP, running on the Mach 3.0 operating system and UNIX server. Specifically, library code in the application's address space implements the network protocols and transfers data to and from the network, while an operating system server manages the heavyweight abstractions that applications use when manipulating the network through operations other than send and receive. On DECstation 5000/200 This research was sponsored in part by the Advanced Research Projects Agency, Information Science and Technology Office, under the title "Research...

This document presents the recommendation of the IPng Area Directors on what should be used to replace the current version of the Internet Protocol. This recommendation was accepted by the Internet Engineering Steering Group (IESG).

Multimedia communication, with its strong requirements for high speed, assured quality, and reliable networking, is stimulating a great research effort towards the development of real-time protocols. Some protocols of this type have been proposed, which offer communication services with different levels of commitment in providing quality of service guarantees. In this paper we study the feasibility of an extended client interface that allows more flexibility in the client-network interactions. The proposed model improves the utilization of network resources, and increases the network's capability to support multimedia traffic, while continuing to offer a guaranteed quality of service. Keyword Codes: C.2.0; C.2.1; C.2.2 Keywords: Computer-Communication Networks, General; Network Architecture and Design; Network Protocols 1. Introduction Multimedia applications, with their strong requirements for high-speed and high-quality communication services, have stimulated the development of new...

The objective of this paper is to provide a historical account of the design and evolution of the Internet and use it as a concrete starting point for a scientific exploration of the broader issues of robustness in complex systems. To this end, we argue that anyone interested in complex systems should care about the Internet and its workings, and why anyone interested in the Internet should be concerned about complexity, robustness, fragility, and their trade-o#s.

This document was submitted to the IPng Area in response to RFC 1550. Publication of this document does not imply acceptance by the IPng Area of any ideas expressed within. Comments should be submitted to the big-internet@munnari.oz.au mailing list. This RFC specifies criteria related to mobility for consideration in design and selection of the Next Generation of IP.

This RFC describes an open distance vector routing protocol for use at all levels of the internet, from isolated LANs to the major routers of an international commercial network provider.

This document examines the various longer term trends visible within the characteristics of the Internet's BGP table and identifies a number of operational practices and protocol factors that contribute to these trends. The potential impacts of these practices and protocol properties on the scaling properties of the inter-domain routing space are examined.

This memo summarizes issues surrounding the routing and addressing scaling problems in the IP architecture, and it provides a brief background of the ROAD group and related activities in the Internet Engineering Task Force (IETF).

This document was submitted to the IETF IPng area in response to RFC 1550 Publication of this document does not imply acceptance by the IPng area of any ideas expressed within. Comments should be submitted to the big-internet@munnari.oz.au mailing list.

One of the recognised deficiencies of the Internet is that security was not considered in the Internet design early on to the extend it is required today. Although military security was considered when the Internet architecture was designed, the modern security issues are much broader, encompassing commercial requirements as well. Furthermore, experience has shown that it is difficult to add security to a protocol suite unless it is built into the architecture from the beginning. (RFC 1287) Both the experiences made with the Internet as recognized by the IETF community, and the infrastructure dependencies that were created in our societies using the Internet, indicate strongly that this should change in the future: the design of Future Internet has to consider security as one of its chief