| Watson, R., "Timer-based Mechanisms in Reliable Transport Protocol Connection Management", Computer Networks, Vol. 5, 1981. Security Considerations Security issues are not discussed in this memo. |
....information that the server must write. The alternative is to write all information in the connection table to stable storage; this would ensure that the crash causes no erroneous rejections, but would slow down normal processing substantially. 2.5. Comparison with Delta t The Delta t protocol [3] also implements at most once messages without requiring connection setup. It works by defining a system wide bound on the length of time a message can remain in transit. Each message initially contains this bound as one of its fields. When a switching node within the network receives a message, ....
Watson, R.W. '"Timer-Based Mechanisms in Reliable Transport Protocol Connection Management". Computer Networks 5 (1981), 47-56.
....instantiation of a context never changes, but the instance is incremented after each use. This gives the key value the property that it is unique over the uses of the context (since the key is 64 bits wide, the time to wrap also ensures that the key value is unique for a very, very long time (see [10] for details on why the uniqueness of connection identifiers is important) When a user registers with the daemon, the context manager method init context( is called to prepare a context for the user. Within init context( the context manager chooses a quiescent context, calls that context ....
Watson, R. W., "Timer-Based Mechanisms in Reliable Transport Protocol Connection Management," in Computer Networks
....this LAN using a window of only 833 bytes will run at the full 100mbps and can wrap the sequence space in about 3 minutes, very close to the MSL of TCP. Thus, high speed alone can cause a reliability problem with sequence number wrap around, even without extended windows. Watson s Delta T protocol [Watson81] includes network layer mechanisms for precise enforcement of an MSL. In contrast, the IP Jacobson, Braden, Borman [Page 6] RFC 1323 TCP Extensions for High Performance May 1992 mechanism for MSL enforcement is loosely defined and even more loosely implemented in the Internet. Therefore, it is ....
Watson, R., "Timer-based Mechanisms in Reliable Transport Protocol Connection Management", Computer Networks, Vol. 5, 1981.
....Transport protocols are at the heart of any wide area communication network and form the basis for common protocols such as electronic mail, remote procedure call, talk, ftp, and rlogin. A connection management protocol keeps information about the state of a connection in a connection record [30]. Most incarnation management protocols depend on having connection records available after a crash and before opening a new incarnation. But there are costs associated with maintaining connection records. A common technique to retain connection records across a crash is to keep them in stable ....
....FIFO delivery. They are also relevant to data link initialization procedures, which provide a reliable connection between nodes that are physically connected. Connection management has been studied intensively in the practical literature and many ingenious protocols have been suggested (e.g. [8, 9, 24, 25, 27, 30, 31]) All these protocols rely on some combination of timers, packet delay bounds, synchronized clocks and unique incarnation identifiers; it has been argued informally that some combination of these assumptions is necessary [31] Our work complements these protocols by identifying precisely which ....
R. W. Watson, "Timer-based Mechanisms in Reliable Transport Protocol Connection Management, " Computer Networks, Vol. 5, pp. 47--56, 1981.
....to restart is to rely on bounds on message lifetimes, say T . If a node waits for some multiple of T after restarting, it can avoid getting confused by responses to pre crash messages. Such an approach was used in the ARPANET routing protocol [M80] and in the first timer based transport protocol[W81]. A disadvantage is that message lifetimes in a large network are high, leading to a noticeable rebooting delay. Thus, in this paper we assume an asynchronous model in which there are no time bounds on message delay or node computation. This is reasonable when time bounds are either too high or ....
R.W. Watson. Timer based mechanisms in reliable transport protocol connection management. Computer Networks, 5:47--56, February 1981.
No context found.
Watson, R., "Timer-based Mechanisms in Reliable Transport Protocol Connection Management", Computer Networks, Vol. 5, 1981. Security Considerations Security issues are not discussed in this memo.
No context found.
Watson, Richard W. Timer-Based Mechanisms in Reliable Transport Protocol Connection Management. Computer Networks 1981, North-Holland Publishing Company.
No context found.
Watson, R. W., "Timer-based mechanisms in reliable transport protocol connection management", Computer Networks 5, pp. 47-56, 1981.
No context found.
Watson, Richard W., "Timer-Based Mechanisms in Reliable Transport Protocol Connection Management." Computer Networks, N.5 (1981), pp. 4756, Pub. by North-Holland.
No context found.
. R. W. Watson. "Timer-Based Mechanisms in Reliable Transport Protocol Connection Management". Computer Networks, 5 (1981), 47-56, North-Holland Publ., Amsterdam, The Netherlands.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC