Demo Data from EDBT 2026 / reviewers in the wild / expert
Binita Gupta
dblp:89/1774
· DBLP profile ↗
1ranked-venue papers
0as first author
0since 2021 · last 2003
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Computer networks · 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
1 paper |
Routing and switching · 87% Wireless networking · 13% | |
| Software engineering, system software, and programming languages
1 paper |
Operating systems · 100% |
Topics — the 3 heaviest of 4, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Routing and switching
ad hoc network routing |
0.0 | 1 | 2003 | System Services for Ad-Hoc Routing: Architecture, Implementation and Experiences · MobiSys 2003 |
Routing and switching › routing protocol
reactive routing protocol |
0.0 | 1 | 2003 | System Services for Ad-Hoc Routing: Architecture, Implementation and Experiences · MobiSys 2003 |
Wireless networking
mobile ad hoc networks |
0.0 | 1 | 2003 | System Services for Ad-Hoc Routing: Architecture, Implementation and Experiences · MobiSys 2003 |
Methods — techniques the papers use, named apart from their topics
shared user-space library · 0.1kernel module · 0.1
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2003 | System Services for Ad-Hoc Routing: Architecture, Implementation and ExperiencesabstractThis work explores several system issues regarding the design and implementation of routing protocols for ad-hoc wireless networks. We examine the routing architecture in current operating systems and find it insufficient on several counts, especially for supporting on-demand or reactive routing protocols. Examples include lack of mechanisms for queuing outstanding packets awaiting route discovery and mechanisms for communicating route usage information from kernel to userspace. We propose an architecture and a generic API for any operating system to augment the current routing architecture. Implementing the API may normally require kernel modifications, but we provide an implementation for Linux using only the standard Linux 2.4 kernel facilities. The API is provided as a shared user-space library called the Ad-hoc Support Library (ASL), which uses a small loadable kernel module. To prove the viability of our framework, we provide a full-fledged implementation of the AODV protocol using ASL, and a design for the DSR protocol. Through this study, we also reinforce our belief that it is profoundly important to consider system issues in ad-hoc routing protocol design. 1 Vikas Kawadia, Yongguang Zhang, Binita Gupta |
MobiSys | 3 |