The Session Layer provides the mechanism for opening, closing and managing a session between end-user application processes, i.e. a semi-permanent dialogue. Communication sessions consist of requests and responses that occur between applications. Session Layers are commonly used in application environments that make use of remote procedure calls (RPCs).
An example of a Session Layer protocol is the OSI protocol suite Session Layer Protocol, also known as X.225 or ISO 8327. In case of a connection loss this protocol may try to recover the connection. If a connection is not used for a long period, the Session Layer protocol may close it and re-open it. It provides for either full duplex or half-duplex operation and provides synchronization points in the stream of exchanged messages.
Other examples of session-layer implementations include Zone Information Protocol (ZIP) – the AppleTalk protocol that coordinates the name binding process; and Session Control Protocol (SCP) – the DECnet Phase IV Session Layer protocol.
In brief: the Session Layer establishes, manages and terminates connections (sessions) among cooperating applications. It also adds traffic flow information.
The OSI model also made the Session Layer responsible for session checkpointing and recovery, which is not usually used in the Internet protocols suite. However, there are a few applications layer protocols where the concept is useful. The idea is to allow information on different streams, perhaps originating from different sources, to be properly combined. In particular, it deals with synchronization issues, and ensuring nobody ever sees inconsistent versions of data, and similar things.
One application which is intuitively fairly clear is web conferencing. Here, we want to make sure that the streams of audio and video match up - or in other words, that we do not have lip synch problems. We may also want to do floor control - ensuring that the person displayed on screen and whose words are relayed is the one selected by the speaker, or by some other criteria.
Another application is in live TV programs, where streams of audio and video need to be seamlessly merged from one to the other so that we do not have half a second of blank airtime, or half a second when we transmit two pictures simultaneously.
Can X.25 overcome its past? X.25's promise has always exceeded its performance. Is there a place for X.25 in a fast-packet/ frame relay world?
Aug 01, 1991; The International Standards Organization (ISO) made headlines in 1976 by announcing its Basic References Model for Open Systems...