|
|
1.1 ! root 1: % run this through LaTeX with the appropriate wrapper ! 2: ! 3: \section {Changes to RFC983}\label{changes} ! 4: The current version, version~2, of the protocol described in this paper ! 5: incorporates four minor changes to RFC983\cite{TSAP.on.TCP.old}. ! 6: These are: ! 7: \begin{itemize} ! 8: \item ``Infinite'' length TSDUs are supported\\ ! 9: The original protocol supported transport service data unit (TSDU) lengths ! 10: of no more than approximately 65K octets. ! 11: This restriction was removed. ! 12: From the performance standpoint, ! 13: it turns out that a TSDU with length on the order of 65K octets (or less) can ! 14: be handled very efficiently by most implementations. ! 15: If a user of transport services requires a larger TSDU size, ! 16: the current protocol will support this, ! 17: but any implementations of the protocol will most likely do this less ! 18: efficiently. ! 19: ! 20: \item More correct use TSAP IDs\\ ! 21: The original protocol mistakenly placed entities other than OSI session ! 22: on top of the TSAP. ! 23: This has been corrected. ! 24: ! 25: \item Negotiation of Expedited Data\\ ! 26: The original protocol mistakenly aborted the connection establishment attempt ! 27: if there was a mismatch in the proposed use of expedited data. ! 28: This has been corrected: ! 29: the use of expedited data is negotiated downwards, as per the ISO specification. ! 30: ! 31: \item Handling of Expedited Data\\ ! 32: As described earlier, ! 33: RFC983 tried to manage two TCP connections, ! 34: one for expedited TSDUs and the second for all other traffic. ! 35: Although intuitively natural, ! 36: this method could not guarantee the semantics of the expedited data service ! 37: in the TP without a complex buffer management scheme. ! 38: Hence, currently only a single connection is employed. ! 39: Owing to the properties of the TCP, ! 40: the expedited data semantics of the TP are handled properly. ! 41: \end{itemize} ! 42: ! 43: Although all of these changes were rather small, ! 44: regretably version~2 of the protocol is incompatible with the original ! 45: protocol found in RFC983.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.