ACM Home Page
Please provide us with feedback. Feedback
A verified connection management protocol for the transport layer
Full text PdfPdf (1.64 MB)
Source ACM SIGCOMM Computer Communication Review archive
Volume 17 ,  Issue 5  (Oct./Nov. 1987) table of contents
Pages: 110 - 125  
Year of Publication: 1987
ISSN:0146-4833
Also published in ...
Authors
S. L. Murphy  Univ. of Maryland, College Park
A. U. Shankar  Univ. of Maryland, College Park
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 7,   Downloads (12 Months): 33,   Citation Count: 5
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues   peer to peer  

Tools and Actions: Review this Article  
Save this Article to a Binder    Display Formats: BibTex  EndNote ACM Ref   
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/55483.55495
What is a DOI?

ABSTRACT

We specify and verify a connection management protocol for use between entities connected by channels that can lose, reorder, and duplicate messages. The protocol is symmetric. Each entity is in one of the following states: closed, listen, open, active opening, passive opening, or closing. The first three are stable states to be exited only by user request, while the last three are transient states. Each entity maintains a local incarnation number at all times, and a remote incarnation number only when opening, open, and closing. Our protocol employs the 3-way handshake used in TCP and ISO Transport Protocol (Class 4). We verify the safety property that when an entity is open, its remote incarnation number matches the remote entity's local incarnation number. This ensures that data messages from past connection instances are not delivered to the user. We verify the following progress properties: an actively opening entity will eventually establish a connection, provided that the remote entity is willing to communicate or is itself actively opening; the states of active opening, passive opening, and closing are transient; if the entities remain closed, the channels will eventually become empty, assuming messages have a maximum lifetime. This protocol specification can be immediately combined with the data transfer protocol specifications presented in [SHAN1, SHAN2, SHAN3] to provide a transport layer protocol with the functions of connection management and two-way data transfer. The verifications too can be immediately combined to provide a hierarchical verification of the multi-function protocol. The specifications and verifications can be combined because the connection management and data transfer protocols are images of the multi-function protocol. This illustrates the power of protocol projections in constructing multi-function protocols.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

COUR
CHAN
 
DIJK
 
DoD
Transmission Control Protocol, DDN Protocol Handbook: DoD Military Standard Protocols, DDN Network Information Center, SRI, MILSTI)1778, Aug 1983.
 
ISO
International Organization for Standardization, Information Processing Systems- Open Systems Interconnection - Transport Protocol Specification, ISO DIS 8073, 1985.
JUR1
 
JUR2
W. Jurgensen and S. T. Vuong, "CSP and CSP Nets: A Dual Model for Protocol Specification and Verification", Protocol Specification, Testing, and Verification IV, ed. Y. Yemini, R. Strom, and S. Yemini, 1984.
 
KUR
 
LAM
S.S. Lam and A. U. Shankar, "Protocol verification via projections," IEEE Trans. on Soft. Eng., Vol. SE-10, No. 4, July 1984, pp. 325-342.
LIN
 
SHAN0
SHAN1
 
SHAN2
A. U. Shankar, "Verified data transfer protocols with variable flow control", CS-TR-1746, Dept. of Computer Science, University of Maryland, Mar 1987.
 
SHAN3
 
SUN
C.A. Sunshine and Y. K. Dalal, "Connection Management in Transport Protocols", Computer Networks, Vol.2(5), Dec 1978.


Collaborative Colleagues:
S. L. Murphy: colleagues
A. U. Shankar: colleagues

Peer to Peer - Readers of this Article have also read: