1992
DOI: 10.1145/128899.128901
|View full text |Cite
|
Sign up to set email alerts
|

A dynamic network architecture

Abstract: Network software is a critical component of any distributed system. Because of its complexity, network software is commonly layered into a hierarchy of protocols, or more generally, into a protocol graph . Typical protocol graphs—including those standardized in the ISO and TCP/IP network architectures—share three important properties; the protocol graph is simple, the nodes of the graph (protocols) encapsulate complex functionality, and the topology of the graph is relatively static. Th… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
75
0
2

Year Published

1993
1993
2014
2014

Publication Types

Select...
9
1

Relationship

0
10

Authors

Journals

citations
Cited by 161 publications
(77 citation statements)
references
References 13 publications
0
75
0
2
Order By: Relevance
“…In today's networks, complex protocols are organized in layers, building a static protocol stack, sometimes called Protocol Graph (PG) ( [15]). Service oriented network architectures aim at supporting dynamic composition of services, i.e.…”
Section: Service Oriented Network Architecturementioning
confidence: 99%
“…In today's networks, complex protocols are organized in layers, building a static protocol stack, sometimes called Protocol Graph (PG) ( [15]). Service oriented network architectures aim at supporting dynamic composition of services, i.e.…”
Section: Service Oriented Network Architecturementioning
confidence: 99%
“…One approach is to empower the message with the intelligence to decide the path through the stack and the functions necessary in relation to the requirements of the packet [22] [23]. Another approach is to group the functions specific to an application at all layers [24] [25].…”
Section: Reconfigurable Protocol Stacksmentioning
confidence: 99%
“…Perhaps unfortunate examples of this are the various "setsockopt," "fcntl," and "ioctl" calls for tweaking the behavior of network sockets in a small set of predefined ways. Many superior interfaces for asynchronous and copy-free data movement have been proposed Hutchinson and Peterson 1991;Krieger et al 1994;O'Malley and Peterson 1992;Pai et al 1999;Pasquale et al 1994; The Virtual Interface (VI) Architecture 1998; von Eicken et al 1995], though most systems are still not using them. An interface with great potential is NT's "sendfile" system call (now also available in linux and FreeBSD), under which several interesting performance enhancements could be implemented if the internal file system and TCP/IP implementations were reorganized.…”
Section: Related Workmentioning
confidence: 99%