Catenet

Abstract: Within a restricted area such as a single building, or a small cluster of buildings, high-speed (greater than 1 Mbit/s) data transmission is available at a small fraction of the cost of obtaining comparable longhaul service from a tariffed common carrier. Local area networks use this low-east, high-speed transmission capabality as the basis for a general-purpose data transfer network. There are two basic issues in local area network design. First, how should the hardware realizing the network be organized to provide reliable high-speed communication at minimum cost? With the low cost of the raw transmission capability, care is required to keep the associated hardware costs correspondingly low. Second, what protocols should be used for the operation of the network? While many protocol problems are common to local area networks and long-haul networks such as the ARPANET, new protocols are required to exploit the extended capabilities of local area networks. This paper addresses these two basic issues. It also considers the interconnection of local area networks and long-haul networks and presents a case study which describes in detail the host computer interface hard-ware required for a typical local area network.

Abstract: Armies of spiders could not weave a wider web networks are everywhere. Networks span continents and oceans; tie office buildings in iiles of wire, fiber, and other nerse media; reach into land, air, and space vehicles; and confront microcomputers as well as large maint'rame computers. Someii networks are incredibly fast and others are pragmatically slow; some work better than others, and some do not work well at all. However, despite the present abundance, new networks are still being developed coinstantly to challeinge the competitioni. If' we had a way to initerconnect various networks, many problems could be solved. For example, a user may want to comiimuilicate with a site that is not on the same public network as the host computer. Perhaps there are sev eral hosts but no single network to which they will all coinnect. In some cases, the cost of coninection will be a factor; coninecting 100 hosts on a coaxial local net is more cost-effective than putting them all on a public net, but running 1000 miles of coaxial cable to the 101st host is ab.surd. In other cases, pragmatics or the basic laws of nature apply; for example, radio-based networks are about the only choice if mobility is needed. A network technology that supports a maximum of 256 hosts becomies a problenm when you acquire the 257th. G,iven that all hosts caninot be put on a single network, the next best option is to interconniect networks.

Abstract: : The Internet Protocol is designed for use in interconnected systems of packet-switched computer communication networks. Such as system has been called a 'catenet'. The internet protocol provides for transmitting blocks of data called datagrams from sources to destinations, where sources and destinations are hosts identified by fixed length addresses. The internet protocol also provides for fragmentation and reassembly of long datagrams, if necessary, for transmission through 'small packet' networks. This document is based on five earlier editions of the ARPA Internet Protocol Specification, and the present text draws heavily from them. There have been many contributors to this work both in terms of concepts and in terms of text. This edition revises the details security, compartmentation, and precedence features of the internet protocol. (Author)

Abstract: There is an increasing trend to integrate sensor networks into the Internet, eventually resulting in an Internet of Things. Recent efforts of porting IPv6 to sensor networks turn sensor nodes into equitable Internet peers and RESTful Web Services on sensor nodes allow a distribution of the application logic among sensor nodes and more powerful Internet nodes. The touching point between a sensor network and the Internet is the gateway which translates between the link-layer protocols used in the Internet (Ethernet, Wi-Fi) and sensor networks (IEEE 802.15.4). So far, the functionality of those gateways was fixed and simple. We propose to turn these gateways into smart gateways by enabling them to execute application code. As only the gateway has full knowledge of and control over both the sensor network and the Internet, smart gateways can act as performance-enhancing proxies and intelligent caches to preserve the limited resources of the sensor network. Also, the smart gateway can perform application-specific protocol conversion between highly optimized but non-standard protocols in the sensor network and standardized, but less efficient protocols in the Internet. In this paper we present the design of a middleware for smart gateways that allows the execution of application code on the gateway by offering simplified interfaces to the sensor network and the Internet. We also report preliminary performance results for key functions of the middleware.