Increasing the portability and re-usability of protocol code

Bobby Krupczak; Kenneth L. Calvert; Mostafa H. Ammar

doi:10.1109/90.649455

Increasing the portability and re-usability of protocol code

Bobby Krupczak, Kenneth L. Calvert, Mostafa H. Ammar

Research output: Contribution to journal › Article › peer-review

6 Scopus citations

Abstract

Deploying protocols is an expensive and time-consuming process today. One reason is the high cost of developing, testing, and installing protocol implementations. To reduce this difficulty, protocols are developed and executed within environments called protocol subsystems, and protocol software is often ported instead of being coded from scratch. Unfortunately, today a variety of protocol subsystems offer a plethora of features, functionality, and drawbacks; the differences among them often reduce the portability and reusability of protocol code, and therefore present barriers to the deployment of new protocols. In this paper, we consider differences in subsystems and their effect on the portability and reusability of protocols and protocol implementations. We then propose two different approaches, each optimized for a different situation, that allow protocol code implemented in one subsystem to be used without modification within other subsystems, and thus reduce the barriers to protocol deployment. We relate our experiences designing, implementing, and measuring the performance of each approach using, as a baseline, an AppleTalk protocol stack we have developed.

Original language	English
Pages (from-to)	445-459
Number of pages	15
Journal	IEEE/ACM Transactions on Networking
Volume	5
Issue number	4
DOIs	https://doi.org/10.1109/90.649455
State	Published - 1997

Bibliographical note

Funding Information:
Manuscript received December 12, 1995; revised February 21, 1997 and March 27, 1997; approved by IEEE/ACM TRANSACTIONS ON NETWORKING Editor D. Lee. This research was supported by grants from the National Science Foundation under Grant NCR-9305115 and Grant NCR-9628397, and by the TRANSOPEN project of the Army Research Lab (formerly AIRMICS) under Contract no. DAKF11-91-D-0004.

Keywords

Portability
Protocol deployment
Protocol implementation
Protocol subsystem

ASJC Scopus subject areas

Software
Computer Science Applications
Computer Networks and Communications
Electrical and Electronic Engineering

Access to Document

10.1109/90.649455

Cite this

@article{925151500e20474fb4ad064070779c95,

title = "Increasing the portability and re-usability of protocol code",

abstract = "Deploying protocols is an expensive and time-consuming process today. One reason is the high cost of developing, testing, and installing protocol implementations. To reduce this difficulty, protocols are developed and executed within environments called protocol subsystems, and protocol software is often ported instead of being coded from scratch. Unfortunately, today a variety of protocol subsystems offer a plethora of features, functionality, and drawbacks; the differences among them often reduce the portability and reusability of protocol code, and therefore present barriers to the deployment of new protocols. In this paper, we consider differences in subsystems and their effect on the portability and reusability of protocols and protocol implementations. We then propose two different approaches, each optimized for a different situation, that allow protocol code implemented in one subsystem to be used without modification within other subsystems, and thus reduce the barriers to protocol deployment. We relate our experiences designing, implementing, and measuring the performance of each approach using, as a baseline, an AppleTalk protocol stack we have developed.",

keywords = "Portability, Protocol deployment, Protocol implementation, Protocol subsystem",

author = "Bobby Krupczak and Calvert, {Kenneth L.} and Ammar, {Mostafa H.}",

note = "Funding Information: Manuscript received December 12, 1995; revised February 21, 1997 and March 27, 1997; approved by IEEE/ACM TRANSACTIONS ON NETWORKING Editor D. Lee. This research was supported by grants from the National Science Foundation under Grant NCR-9305115 and Grant NCR-9628397, and by the TRANSOPEN project of the Army Research Lab (formerly AIRMICS) under Contract no. DAKF11-91-D-0004.",

year = "1997",

doi = "10.1109/90.649455",

language = "English",

volume = "5",

pages = "445--459",

number = "4",

}

TY - JOUR

T1 - Increasing the portability and re-usability of protocol code

AU - Krupczak, Bobby

AU - Calvert, Kenneth L.

AU - Ammar, Mostafa H.

N1 - Funding Information: Manuscript received December 12, 1995; revised February 21, 1997 and March 27, 1997; approved by IEEE/ACM TRANSACTIONS ON NETWORKING Editor D. Lee. This research was supported by grants from the National Science Foundation under Grant NCR-9305115 and Grant NCR-9628397, and by the TRANSOPEN project of the Army Research Lab (formerly AIRMICS) under Contract no. DAKF11-91-D-0004.

PY - 1997

Y1 - 1997

N2 - Deploying protocols is an expensive and time-consuming process today. One reason is the high cost of developing, testing, and installing protocol implementations. To reduce this difficulty, protocols are developed and executed within environments called protocol subsystems, and protocol software is often ported instead of being coded from scratch. Unfortunately, today a variety of protocol subsystems offer a plethora of features, functionality, and drawbacks; the differences among them often reduce the portability and reusability of protocol code, and therefore present barriers to the deployment of new protocols. In this paper, we consider differences in subsystems and their effect on the portability and reusability of protocols and protocol implementations. We then propose two different approaches, each optimized for a different situation, that allow protocol code implemented in one subsystem to be used without modification within other subsystems, and thus reduce the barriers to protocol deployment. We relate our experiences designing, implementing, and measuring the performance of each approach using, as a baseline, an AppleTalk protocol stack we have developed.

AB - Deploying protocols is an expensive and time-consuming process today. One reason is the high cost of developing, testing, and installing protocol implementations. To reduce this difficulty, protocols are developed and executed within environments called protocol subsystems, and protocol software is often ported instead of being coded from scratch. Unfortunately, today a variety of protocol subsystems offer a plethora of features, functionality, and drawbacks; the differences among them often reduce the portability and reusability of protocol code, and therefore present barriers to the deployment of new protocols. In this paper, we consider differences in subsystems and their effect on the portability and reusability of protocols and protocol implementations. We then propose two different approaches, each optimized for a different situation, that allow protocol code implemented in one subsystem to be used without modification within other subsystems, and thus reduce the barriers to protocol deployment. We relate our experiences designing, implementing, and measuring the performance of each approach using, as a baseline, an AppleTalk protocol stack we have developed.

KW - Portability

KW - Protocol deployment

KW - Protocol implementation

KW - Protocol subsystem

UR - http://www.scopus.com/inward/record.url?scp=0031206787&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=0031206787&partnerID=8YFLogxK

U2 - 10.1109/90.649455

DO - 10.1109/90.649455

M3 - Article

AN - SCOPUS:0031206787

SN - 1063-6692

VL - 5

SP - 445

EP - 459

JO - IEEE/ACM Transactions on Networking

JF - IEEE/ACM Transactions on Networking

IS - 4

ER -

Increasing the portability and re-usability of protocol code

Abstract

Bibliographical note

Keywords

ASJC Scopus subject areas

Access to Document

Other files and links

Fingerprint

Cite this