Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page
Demo Data from EDBT 2026 / reviewers in the wild / expert

Evelyn Moy

dblp:62/3365 · DBLP profile ↗
← Back
2ranked-venue papers
0as first author
0since 2021 · last 1993
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Computer networks · 2

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Computer networks
2 papers
Internet architecture and protocols · 70% Transport protocols and congestion control · 30%
Software engineering, system software, and programming languages
2 papers
Operating systems · 100%
Computer architecture, parallel and distributed computing, and storage systems
1 paper
Distributed systems · 100%

Topics — the 3 heaviest of 6, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Internet architecture and protocols › protocol implementation
user-level protocol implementation		 0.021993
Implementing network protocols at user level · IEEE/ACM Trans. Netw. 1993
Implementing Network Protocols at User Level · SIGCOMM 1993
Transport protocols and congestion control
transport protocols		 0.011993
Implementing network protocols at user level · IEEE/ACM Trans. Netw. 1993
Operating systems
network stack		 0.011993
Implementing Network Protocols at User Level · SIGCOMM 1993

Methods — techniques the papers use, named apart from their topics

user-level libraries · 0.0performance evaluation · 0.0implementation · 0.0user-level library · 0.0
YearPublicationVenuePosition
1993 Implementing Network Protocols at User Level
abstract
Traditionally, network software has been structured in a monolithic fashion with all protocol stacks executing either within the kernel or in a single trusted user-level server. This organization is motivated by performance and security concerns. However, considerations of code maintenance, ease of debugging, customization, and the simultaneous existence of multiple protocols argue for separating the implementations into more manageable user-level libraries of protocols. This paper describes the design and implementation of transport protocols as user-level libraries.We begin by motivating the need for protocol implementations as user-level libraries and placing our approach in the context of previous work. We then describe our alternative to monolithic protocol organization, which has been implemented on Mach workstations connected not only to traditional Ethernet, but also to a more modern network, the DEC SRC ANI. Based on our experience, we discuss the implications for host-network interface design and for overall system structure to support efficient user-level implementations of network protocols.
Chandramohan A. Thekkath, Thu D. Nguyen, Evelyn Moy, Edward D. Lazowska
 SIGCOMM3
1993 Implementing network protocols at user level
abstract
Traditionally, network software has been structured in a monolithic fashion with all protocol stacks executing either within the kernel or in a single trusted user-level server. This organization is motivated by performance and security concerns. However, considerations of code maintenance, ease of debugging, customization, and the simultaneous existence of multiple protocols argue for separating the implementations into more manageable user-level libraries of protocols. The present paper describes the design and implementation of transport protocols as user-level libraries. The authors begin by motivating the need for protocol implementations as user-level libraries and placing their approach in the context of previous work. They then describe their alternative to monolithic protocol organization, which has been implemented on Mach workstations connected not only to traditional Ethernet, but also to a more modern network, the DEC SRC AN1. Based on the authors' experience, they discuss the implications for host-network interface design and for overall system structure to support efficient user-level implementations of network protocols.>
Chandramohan A. Thekkath, Thu D. Nguyen, Evelyn Moy, Edward D. Lazowska
 IEEE/ACM Trans. Netw.3