Demo Data from EDBT 2026 / reviewers in the wild / expert
David R. Boggs
dblp:98/5887
· DBLP profile ↗
3ranked-venue papers
2as first author
0since 2021 · last 1988
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Computer networks · 2 · 2 first-authorSoftware engineering, systems software and programming languages · 1
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 · 81% Transport protocols and congestion control · 10% Network optimization and economics · 9% | |
| Computer architecture, parallel and distributed computing, and storage systems
1 paper |
Storage systems · 100% |
Topics — the 7 heaviest of 8, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Internet architecture and protocols › local area network
ethernet |
0.0 | 1 | 1988 | Measured capacity of an Ethernet: myths and reality · SIGCOMM 1988 |
Internet architecture and protocols
local area network |
0.0 | 1 | 1988 | Measured capacity of an Ethernet: myths and reality · SIGCOMM 1988 |
Transport protocols and congestion control › transport protocols
end-to-end protocols |
0.0 | 1 | 1980 | Pup: An Internetwork Architecture · IEEE Trans. Commun. 1980 |
Internet architecture and protocols › network architecture design
internet architecture |
0.0 | 1 | 1980 | Pup: An Internetwork Architecture · IEEE Trans. Commun. 1980 |
Internet architecture and protocols › network interconnection
internetwork protocol |
0.0 | 1 | 1980 | Pup: An Internetwork Architecture · IEEE Trans. Commun. 1980 |
Network optimization and economics › resource allocation › bandwidth allocation
fair bandwidth allocation |
0.0 | 1 | 1988 | Measured capacity of an Ethernet: myths and reality · SIGCOMM 1988 |
Storage systems › file systems
distributed file system |
0.0 | 1 | 1979 | WFS: A Simple Shared File System for a Distributed Environment · SOSP 1979 |
Methods — techniques the papers use, named apart from their topics
empirical measurement · 0.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 1988 | Measured capacity of an Ethernet: myths and realityabstractEthernet, a 10 Mbit/sec CSMA/CD network, is one of the most successful LAN technologies. Considerable confusion exists as to the actual capacity of an Ethernet, especially since some theoretical studies have examined operating regimes that are not characteristic of actual networks. Based on measurements of an actual implementation, we show that for a wide class of applications, Ethernet is capable of carrying its nominal bandwidth of useful traffic, and allocates the bandwidth fairly. We discuss how implementations can achieve this performance, describe some problems that have arisen in existing implementations, and suggest ways to avoid future problems. David R. Boggs, Jeffrey C. Mogul, Christopher A. Kent |
SIGCOMM | 1 |
| 1980 | Pup: An Internetwork ArchitectureabstractPup is the name of an internet packet format (PARC Universal Packet), a hierarchy of protocols, and a style of internetwork communication. The fundamental abstraction is an end-to-end media-in dependent internetwork datagram. Higher levels of functionality are achieved by end-to-end protocols that are strictly a matter of agreement among the communicating end processes. This report explores important design issues, sets forth principles that have guided the Pup design, discusses the present implementation in moderate detail, and summarizes experience with an operational internetwork. This work serves as the basis for a functioning internetwork system that provides service to about 1000 computers, on 25 networks of 5 different types, using 20 internetwork gateways. David R. Boggs, John F. Shoch, Edward A. Taft, Robert Metcalfe |
IEEE Trans. Commun. | 1 |
| 1979 | WFS: A Simple Shared File System for a Distributed EnvironmentabstractWFS is a shared file server available to a large network community. WFS responds to a carefully limited repertoire of commands that client programs transmit over the network. The system does not utilize connections, but instead behaves like a remote disk and reacts to page-level requests. The design emphasizes reliance upon client programs to implement the traditional facilities (stream IO, a directory system, etc.) of a file system. The use of atomic commands and connectionless protocols nearly eliminates the need for WFS to maintain transitory state information from request to request. Various uses of the system are discussed and extensions are proposed to provide security and protection without violating the design principles. Daniel C. Swinehart, Gene McDaniel, David R. Boggs |
SOSP | 3 |